Razer Phone 2 Unroot Step by step. - Razer Phone 2 Guides, News, & Discussion

Unroot Razer Phone 2
This is the method that I used, I bought a phone that was rooted (little did I know) custom recovery was not installed on my device, but bootloader was unlocked and the phone was rooted. Disclaimer:I am no expert, i just used this method last night (2/2/2019) the Razer guides weren't the best at step by step so I am compiling what I learned from doing this. I am not responsible if you brick or bootloop your phone. You should also do independent research on XDA etc before you attempt this process so you understand the risks. I invite others that know more than me to correct what I may have missed and I will updated the OP.
Step 1
You need a USB C to A cord similar to the one that came with the phone, but Razer says that they don't recommend you use that one because it is designed for quick charge not data transfer so I used one that I bought on Amazon years Ago.
Step 2 you need to download 3 things:
The stock image that can be found here:https://developer.razer.com/razer-phone-dev-tools/factory-images/
You need to download Android SDK
https://developer.android.com/studio/releases/platform-tools.html
You need to download the drivers:
https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip
Also open this https://developer.razer.com/razer-p...02.1384856067.1549140743-333350818.1549140743
Unzip all of these files to a new folder on your desktop call it Razer Phone 2 or whatever.
I also went into the phone tapped build number repeatedly to enable developer options and turned on USB debugging.
On the device, go to Settings > About <device>.
Tap the Build number seven times to make Settings > Developer options available.
Then enable the USB Debugging option.
Step 3 you need to Open this PDF courtesy of Razer:
https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf
This document loosely tells you how to install the drivers follow through all of the steps they give you
It should be noted you see a reference to “Download Mode” there is no such thing also the easiest way to get to this screen is to turn the phone off plug the USB into the computer with the phone not plugged in then hold volume down and plug the phone into the computer and press the power button holding volume down you should be taken to a screen that looks like this (aka download mode): see the image I attached.
I had an issue when I got to the Have Disk portion once I got to the step I had to drill all the way down to the android_winusb.inf file located inside the usb_driver folder. Once i got that it finally showed me the Android ADB Interface and the following dialogue screens. (if you are scrolling through a screen of Manufacturer -Models looking for something then you are doing it wrong) Once it is installed the device Should not have the Android with a ? on the device manager screen it should now say Android ADB Interface. (this part took me almost 2 hours I got frustrated and had to walk away for a bit so dont give up)
You can test that the drivers have been installed correctly like they say in the document but they left a step out for the not as tech savvy people. The way to do it is to open up a command prompt. You will see the directory that is is pointing to is likely C:\Users\[Insert user Name]. We need to change the directory it is looking at by typing.
Cd C:\Users\[insertusername]\Desktop\razer phone 2\platform-tools
(the command cd changes the directory)
You should see the directory change to be looking specifically at that folder now. Now simply type fastboot devices. The command should run and you should see the serial number of your device in the command prompt. If it does not return this then the drivers are not installed correctly.
(some other guides said you should also run the command adb devices, but I never got that to return anything all it ever told me when i ran it was “List of devices attached” with nothing else.
Step 4
Setting the Environment
Once i got to this step I was a little scared because I have never dealt with this before this allows you to call the ADB commands from the command prompt without having to specify the specific folder these ADB commands are located.
Follow the document referenced above until you get to the step that says click New
Instead we are going to look in the section titled “User Variables for [InsertUsername]
Under this section you will see a variable called PATH click on PATH and click edit. A box should pop up and on the right side it should say New, Edit, Browse, Delete, Move Up, Move Down.
Click on New and specify the folder called platform-tools mine looked like this
C:\Users\[username]\Desktop\razer phone 2\platform-tools
Click on ok the box will close and then click on ok again all the boxes pertaining to the environment variables will close.
Step 5
Test that the environment is set up correctly.
You might remember in step 4 we had to open a command prompt and tell it to look specifically at the platform-tools folder to run the ADB commands. With the environment now set we no longer have to specify the folder to run these commands, we can call them from any directory. To test this open a new command prompt it will likely be pointing to
C:\Users\[Insert user Name]
With the phone still plugged in and in “download mode” and without changing the directory, type
fastboot devices it should return the serial number of the phone if the environment has been properly setup if it has not been properly setup then it will return this error.
fastboot' is not recognized as an internal or external command,
operable program or batch file.
Step 6 (im not sure if this is necessary)
Because I bought my phone used I used rootchecker app to ensure the phone was indeed rooted and “download mode” told me the bootloader was unlocked. I wasnt sure if I needed to unlock the critical partitions, but you will notice in the razer instructions right above flash system image they call for them to be unlocked. I simply opened a command prompt and typed:
fastboot flashing unlock_critical
It said they were already unlocked so I moved forward with flashing the system image.
Step 7
Install the system image
From here I followed the razer instructions when i got to the step:
“Navigate to the unzipped system image directory” you open a command prompt and type
Cd C:\Users\[insertusername]\Desktop\razer phone 2\aura-o-global-2009
What this allows you to do is run the flash_all script.
The flash all script uses the command fastboot which if you remember is in the platform-tools folder this is why we had to add the environment in the previous steps so that once we got to this step the flash_all script could find and run that command. I ran this and had no issues the phone will continue to restart and in the command prompt you will see it pushing all the files to the phone. After about 3-4 minutes the phone was at the Wizard. I continued following the guide to lock the bootloader

Reserved

Duplicate post

my phone is not detected in bootloader mode now. i just want to relock my bootloader and i am stuck now

thank you so much! I was almost giving up trying to fix my phone till i saw your post

LordCandyAndy said:
thank you so much! I was almost giving up trying to fix my phone till i saw your post
Click to expand...
Click to collapse
Same here this post was a god send.

The only issues I keep having is that it keeps saying waiting on device, I have uninstalled and removed everything and then reinstalled everything step by step and I keep getting waiting for device in cmd and ps.
any help would be great.

Thanks for the guide.
flash_all kept failing for me because it wouldn't allow fastboot from the ROM's folder. Copying the contents of my platform-tools (adb) folder into the ROM's folder fixed this issue for me. I'm assuming this is because I didn't set up the environment variables correctly.

Darkann said:
The only issues I keep having is that it keeps saying waiting on device, I have uninstalled and removed everything and then reinstalled everything step by step and I keep getting waiting for device in cmd and ps.
any help would be great.
Click to expand...
Click to collapse
I am having the same issue any help

Related

No instant root for Hero under 2.1?

There was an application called instantroot that roots HTC hero running 1.5 but until the software was upgraded nothing was done for the instantroot application. Do you have information about that? Is the developer still working on it?
rapsass said:
There was an application called instantroot that roots HTC hero running 1.5 but until the software was upgraded nothing was done for the instantroot application. Do you have information about that? Is the developer still working on it?
Click to expand...
Click to collapse
Not heard of it for a while, but this method at http://forum.xda-developers.com/showthread.php?t=726118 works on 2.1 fine with little issues.
Thanks but I'm still looking for a very easy way to do the root. I don't know why(may be I'm afraid) but I still hesitate to root my hero. I'll think about it again, thank again.
Following that link pulser gave will give the easiest way to root your hero.
Its thanks to that I'm able to root it with no problems whatsoever.
Good Luck!! Don't let yourself stay unrooted!!!
Ok. I'll try later as the villainrom web site is not reachable now.
rapsass said:
Ok. I'll try later as the villainrom web site is not reachable now.
Click to expand...
Click to collapse
Hmm. Are you having trouble too getting onto the site?
Here's the instructions as posted.
Hi all,
I believe I have managed to find a way to root the 2.1 RUU for GSM Hero, completely using the work of wag3slav3 over at XDA (http://forum.xda-developers.com/showthread.php?t=724741), so thanks to him
I took his Droid Eris root and used the correct files for our Hero, and thanks to daentech on IRC, we tested the process and it worked. Here are the conditions used in the test:
1) GSM HTC Hero installed with the 2.1 ROM based on RUU (on this occasion an update.zip was used, as the user involved didn't want to lose root obviously). That zip is unrooted and stock, taken straight from the RUU and converted to update.zip.
2) Booted into ROM, and enabled USB debugging. ADB was installed and set up on this machine, as per this guide - http://www.villainrom.co.uk/viewtopic.php?f=46&t=1735
3) Then downloaded this file: http://www.villainrom.co.uk/uploads/GSMRoot.zip
4) Extract it to a folder on your computer. Open the command prompt using Start > Run > cmd.exe (and press enter)
5) use cd to get into the folder you stored the extracted files.
6) Run the command "runindos.bat"
(If you use linux, put adb in your path folder, and then download this shell script: http://www.villainrom.co.uk/uploads/runinlinuxadb.sh and execute it as normal. Rest will be same as in windows. )
7) Ideally, the phone should sit there for a bit, with some things appearing on screen like
Files copied and permissions set, rebooting HTC Andriod 2.1
Your phone will now reboot into normal mode, then reboot into recovery mode
If it does not reboot the second time, wait 10 minutes and manually reboot and begin again
Your phone is now rebooting in Rooted Recovery mode, do a backup and load yourROMs
Click to expand...
Click to collapse
And it will reboot a couple of times. You will hopefully end up sitting in recovery with a blue 'care bear' in the background
If so, you now have a custom recovery installed. Do a nandroid, and flash a custom ROM like VillainROM 12 or whatever. You should now have root.
8) To further enhance the usefulness of recovery flash VR 12 from here: http://villainrom.co.uk/viewtopic.php?f=95&t=1807 which includes a modified recovery that wipes better than the stock Amon-Ra
If you don't get it to work, please post any errors or details of what happens, and copy and paste your entire command prompt window contents into a
Code:
[/quote] box in the forum window so we can see what's happening.
Hope this works
[size=3]PS. Here are some ROM links for you.
http://villainrom.co.uk/viewtopic.php?f=95&t=1807 - VillainROM 12 (Full Sense 2.1 ROM)
http://www.villainrom.co.uk/viewtopic.php?f=45&t=2844 - FroydVillain 1.1.0 (Vanilla 2.2 Froyo ROM)[/size]
[/quote]
If you can't download the file, get it from http://dl.dropbox.com/u/7618177/GSMRoot.zip
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Oh man thank you. I wonder if I must install ADB to root my phone. I ask this because I still can't reach villainrom web site to check this guide http://www.villainrom.co.uk/viewtopic.php?f=46&t=1735
rapsass said:
Oh man thank you. I wonder if I must install ADB to root my phone. I ask this because I still can't reach villainrom web site to check this guide http://www.villainrom.co.uk/viewtopic.php?f=46&t=1735
Click to expand...
Click to collapse
If you find the user btdag, his signature has the same guide, as he wrote it on both sites. I just use that link as it's easier to find.
pulser_g2 said:
If you find the user btdag, his signature has the same guide, as he wrote it on both sites. I just use that link as it's easier to find.
Click to expand...
Click to collapse
I would love to take credit for that guide but the user ante0 created it (such a simple method I overlooked). Here is it quoted. It is missing pictures but should make enough sense (i hope). It is highly recommended to have the latest HTC Sync installed (link in my sig) for this guide.
Tools needed:
Android SDK (Links below)
HTC Sync (Links below)
Winrar - to extract Android's SDK files.
Patience and time.
1. Getting ADB (Android Debug Bridge)
Okay. You now need to get ADB, which is a part of android's SDK. It can be obtained here http://developer.android.com/sdk/downlo ... indows.zip
or if it's updated when you read this you can go here http://developer.android.com/sdk/index.html and download it. Get the Windows version if you use a windows PC.
Next we need to "install" it. This is done by simply extracting it to your harddrive (Install WinRar, then rightclick on the zip file). I chose C:\android-sdk-windows\. (Actually I chose C:\, the folder in the zip is named android-sdk-windows, so it goes there by default.)
After that is done we are now done with the "installing" part.
2. Setting up environment variables (access adb from outside of \sdk\tools directory.)
Now that we have extracted all files we need to set up environment variables to make our lives easier.
I always do this, because if you don't you need to be in the sdk\tools folder at all times...
Okay, so here we go...
Windows XP:
Rightclick on "My computer" and select "Properties".
click on the "Advanced" tab in the box that appears, looks like the pic below.
Image
Click on the button named "Environment Variables".
Now, doubleclick on the text entry named "Path" in the lower list box.
at the end of it, enter "might\have\other\entries\before\;C:\Path\To\SDK\Tools".
In my "path" it looks like this ";C:\android-sdk-windows\tools\".
(";" is required at the start so windows knows it's a new entry.)
Click on OK to exit out of the dialog, then OK again to get out of My computer's properties.
Now we have it set up.
Windows 7/Vista:
This is similar to Windows XP's setup of environment variables.
Rightclick on "My computer" and select Properties.
In the System window that appears click on "Advanced System settings" located in the left list.
Click on the Advanced tab in the box that appears, then on the "environment variables" button.
Same thing here. Doubleclick on "Path" located in the lower list box.
At the end of it, enter "might\have\other\entries\before\;C:\Path\To\SDK\Tools".
In my "path" it looks like this ";C:\android-sdk-windows\tools\".
(";" is required at the start so windows knows it's a new entry.)
Now click on OK, then OK again to exit.
Alright, all set up!
3. Making sure USB works...
Use this guide: viewtopic.php?f=15&t=379
4. Using ADB
I won't list all commands you can use here. I will only list some examples...
Remember to plug your phone in your usb cable (I've forgotten sometimes... lol)
Start by opening a command prompt.
This is done by opening up the startmenu then click on "Run..." (Alternative way: Windowskey + R).
In the "Run..." box, enter "cmd" without quotes.
If you have some knowledge of using a cmd prompt you don't need to read the next part.
To navigate you mainly use the commands CD and DIR.
Here's an image of what it looks like
Image
C:\Documents and settings\jwork> tells you what your current working folder is.
To get out of it, use the command "cd ..".
This will go back one folder, so your new location will be C:\Documents and settings>
One more "cd .." will take you to C:\.
Now, lets say you have a folder named Images in C:\. To enter it you use "cd Images".
If you want to list all files in that folder, enter the command "dir".
Now you might have a image named image01.jpg in that folder, that you want to get to your phone.
Use the command adb push image01.jpg /sdcard/
It should notify you now if the push was successful.
You can check if the image is on your sdcard by using the command "adb shell ls /sdcard/".
That should conclude this guide...
One more thing, if you just enter "adb" it will show a list of all commands with descriptions.
Click to expand...
Click to collapse
Have you ever heard of Universal Androot? It is only one click away to root your hero2.1.
It's working on my hero.
Universal Androot? Never heard of it. But it looks great and easy. Can I also install another firmware after I root my device with it?
Can I install another firmware like FroydVillain 1.2.2 OTA on my hero after rooted it with this application?
If it installs a custom recovery image then yes you should be able to. If not try installing ClockworkMod and then installing AmonRA - once you have root.
You are the best. Thank you.
Application thread in the Nexus forum. Worked on my Hero 2.1 for instant root.
http://forum.xda-developers.com/showthread.php?t=747598

[GUIDE]Install Android SDK and upgrade Marketplace to 2.2.6

FIRST OF ALL, I CAN NOT BE HELD RESPONSIBLE FOR ANY DAMAGE YOU DO TO YOUR DEVICE! PROCEED AT YOUR OWN RISK!!!​
Now that we got that out of the way...
I have noticed that some people`s Marketplaces simply refuse to update by themselves (exactly what happened in my case) and as most of the people visiting this forums are not tech-savvy and simply want a step-by-step guide to get things working, I decided no harm can be done by me posting this info.
Installing Android SDK revision 8
First of all, you will need to have Android SDK (and ADB of course) installed with the drivers ready to go. In order to get the SDK installed go to the official Android website and download the latest revision (r08 at the time I posted this). You can download any of those files, but I prefer using the executable installer so I can make sure everything is at its place. Now, there are two major flaws with this whole process which have almost made me quit the whole process several times, but I got them sorted out and will help you solve them aswell.
FLAW #1: After beginning the installation process, the installer will prompt you to download a JDK (Java Developer Kit) in order to continue installation. Hit the "Visit sun.java.com" button and download the latest Java SE (currently this one). But before proceeding be sure to download the 32 bit one, as the Android SDK only recognises this version. I know it`s not a big deal, but I spent about two hours trying to figure out what the heck went wrong and it became quite frustrating.
Install the JDK, then the SDK. Once Android SDK is done, simply go ahead and launch SDK Manager (you can find it in Program Files\Android\android-sdk-windows\) and when you get to choose the packages to install, simply check "Accept All" and click "Install". Once it`s done, it`s time to download the drivers. Click "Available packages", tick "Third party Add-ons" and under "Google Inc. add-ons" you should find "Google Usb Driver package". Tick it and click "Install". IF YOU GET AN ERROR SAYING THAT PERMISSION WAS DENIED AND YOU ARE UNDER WINDOWS 7, COPY THE WHOLE "Android" FOLDER CONTAINING THE SDK TO YOUR DESKTOP (OR ANY OTHER PLACE) AND REPEAT THE STEPS ABOVE. I know it`s quite rudimentary, but it does its job. Once it`s done, a folder named "google-usb_driver" will be created under Android. Be sure to correctly copy it to the original location in case you had permission issues.
FLAW #2: Ever since Android SDK r08, Google decided to remove the ADB files so now they have to be manually placed in the folder. I have uploaded them for you, so click here to download them. Once downloaded, extract the archive to the "Android\android-sdk-windows\tools" folder.
OPTIONAL: Go to Start Menu, right click on Computer, click Properties. The System window will appear, where you need to go to "Advanced system settings". Once there, click on "Environment variables" and where it says "System variables", look for PATH. Once found, highlight it and click "Edit..." then add the line "C:\Program Files\Android\android-sdk-windows\tools;" at the end. Click "Ok", "Ok" and "Ok", then restart your computer.
Right now everything should be working as expected. Connect your HD2 to the PC via USB and hope for the best. If the drivers are working and it is recognized as a HTC device, open a command prompt and type "adb devices". If you get anything such as "List of devices attached" followed by some code such as "0123456789ABCDEF device", everything is working well. Good job, you just correctly and completely installed Android SDK on your PC!
If not...
Check your device manager and if you see any devices related to your HD2 having problems, simply right click on them and update the drivers with the ones downloaded earlier in the "google-usb_driver" folder then reboot your computer.
We`re all set! ...What now?
The whole process is actually quite simple. First of all, download the new 2.2.6 Marketplace and put it somewhere accessible, such as your desktop. Open a command prompt and enter the following:
Code:
adb remount
adb shell
rm /system/app/Vending.apk
This will basically delete the old Marketplace from your device.
Now go to the folder where you placed the new Marketplace, hold down Shift, right-click and select "Open command window here". A command prompt should pop up at the exact location. Now execute the following command:
Code:
adb push Vending.apk /system/app
And that is it! Now restart your device and try to run your Marketplace, it will load for half a minute or so then it will start normally. Enjoy!
I know this is rather a tutorial for installing the SDK, but I figured it would be useful to let everyone know how I managed to solve my problem. In case I skipped any steps or you notice anything wrong/wish to add anything, please feel free to do so!
If you feel my post has helped you in any way, do not hesitate to hit the "Thank" button!
Reserved post for further mini-tutorials.
At least on my r08 install if you install the platform tools component then adb will be available under the platform-tools directory (moved from the tools directory).
@OP
Did you test this on a non sense build?
This procedure will most likely not work with Cyanogenmod ROMs. That and I'd suggest you give the newest market version (2.2.7) instead. I'm not willing to destroy my ROM again by trying it on CM.

OUTDATED[Guide] Setting up/using adb/fastboot-unlock, flash custom recovery & root

OUTDATED[Guide] Setting up/using adb/fastboot-unlock, flash custom recovery & root
Below is a great guide to rooting, from several sources, (mostly taken from pingvinen's "An Idiot's Guide to Flashing the Xoom" and a guide by publicanimal. and I hope it helps. You can find the links to all of the files referenced below in the Xoom Heaven thread (thanks StrifeSoldierVII!)[/I]
(New thread in General Section by Jack207407 will have all the updated links for flashing
http://forum.xda-developers.com/showthread.php?t=1443110
One Stop For ROM's, MOD's, and Root Wifi-Only and 3G/4G Models)
"What you need to do can be encompassed in these following short steps (will be detailed later on) in the following order. Each step is required before you can proceed to the next one. However, make sure that you are very very careful and don't try to take any shortcuts. That may soft-brick your device, and you may have a difficult time to explain that to your wife ... You have been warned.
HERE'S THE USUAL DISCLAIMER--I AM NOT RESPONSIBLE FOR ANY HARM THAT MAY COME TO YOUR DEVICE IF YOU FOLLOW ANY PART OF THIS GUIDE--ANY RISK IS ON THE USER!
I strongly recommend you to read the entire guide before trying. In fact, read it twice to ensure that you have understood everything. If there is weird stuff that you don't understand, don't hesitate to ask. The reason for me writing this down is that I like to document what I have learned. This is to me an excellent way to ensure that I will remember what I just did. Another reason was that I could not find a single thread that encompassed all steps required. There are many different threads, but no one (that I could find) that really guides you from start to goal. So enjoy and good luck!
I would like to thank LandMaster and cam30era for helping out with advice during my initial trail-and-error session. I soft-bricked my device once and had big problems to get by point 4.3 (avoid overwriting of CWM), but with their encouragement I finally succeeded.
Just a note before we begin: the different Xoom. Models that are able to use this guide are the following:
MZ600 - stingray_cdma - Motorola US 3g Xoom (technically this device is stingray as well, but I will be using stingray_cdma as the two devices have incompatible software)
MZ601 - utms_everest - Motorola EU 3g Xoom
MZ602 - stingray - Motorola US 4g Xoom
MZ604 - wingray - Motorola Wifi Xoom
(thanks solarnz!)
___________
Overview of the 6 required steps
1. Install Motorola USB drivers for your computers (for USB connectivity) 2. Install Java SDK and Android SDK tools (for adb and fastboot commands) 3. Unlock the device for flashing (allowing replacement of recovery and boot images) 4. Install a modified recovery image (ClockWorkMod recovery for Android) 5. Root the device (Allow r/w access to the device filesystem) 6. Flash a kernel that supports overclocking etc.
Steps 1, 2, 4, 5 and 6 require that you download install, image and zip files needed for the flashing.
All this was performed on a Windows PC. Windows 7, Mac and Linux users will probably have to do some steps differently.
1.0 Install the latest Motorola USB drivers
The installation file can be found at: http://developer.motorola.com/docstools/USB_Drivers/
1.1 Install the drivers and ensure that your Xoom is recognized by the computer
2.0 Installation of development software
Android SDK and Java SDK need to be installed. You can find the installation kits here.
http://developer.android.com/sdk/index.html In case you can't find fastboot.exe, look for it here (thanks to jerrycycle): http://forum.xda-developers.com/showpost.php?p=19546334&postcount=5
Update: you could also just install the adb fastboot pack here:http://www.android.net/forum/downloads.php?do=file&id=67
http://www.oracle.com/technetwork/java/javase/downloads/index.html
2.1 Install them as any other software, making an Android SDK folder on C/.
2.2 Make sure that all the files you need are in the Platform Tools folder (fastboot, recovery image file and so on). Copy any files in the Tools folder to the Platform Tools folder if necessary. Note: If the Android SDK complains that the Java Dev Kit can't be found, just press Back and then Next again. Wierd, but that seems to do the trick ... go figure.
(Warning: Never put any zip files in your Platform Tools folder. Flashing zip files through fastboot will cause very serious problems. Zip files must be flashed from the external micro SD card through CWM recovery on the Xoom...we'll get to that later.)
2.3 Test that ADB and FASTBOOT works. You should open a command window by right clicking in your Platform Tools folder where all of your files are, plug in your Xoom to your computer with your Motorola cable (it may not work with a generic cable) and write 'adb devices'. Your Xoom should now be listed. Did your device not show up? Make sure that you have USB debugging enabled in Settings/Applications/Development on your Xoom.
Optional: Those that want to be able to access adb from any where on their computer, here's a tip from scsa20: "For windows, if you go into System Properties and choose Advanced, then Environment Variables..., you'll be able to edit the Path variable under System variables, just add the path to where adb and fastboot is located (separated with a semi-colon ().
Here's what my Path variable looks like:
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%Sy stemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\ System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\android-sdk-windows\tools;C:\android-sdk-windows\platform-tools;C:\Program Files (x86)\Common Files\Acronis\SnapAPI\
It's long but do you see the android stuff there at the end?"
Update: xda poster Mandelbrot Benoit suggests an alternate adb setup, here: http://forum.xda-developers.com/showpost.php?p=18072572&postcount=50
If your windows computer doesn't see your Xoom, consider this (Originally Posted by AngryBulleteyeTruth):
When the xoom does not show up on PC it may be the problem of.... windows media player!
Xoom uses drivers of WMP to communicate with PC. If someone does not have the newest WMP drivers it will not show up and you can see xoom device in the devices tab on PC having an exclamation mark.
So the solution is to download and install Windows Media Player 11. It has worked for me.
--------
OK. Now that you are set up, it's Showtime! Take a deep breath...
3. Unlocking the device for flashing
This step will effectively erase the internal storage, including all your apps and settings. Use whatever backup you want to secure important data before you start. (It will also void your warranty, so you still have time to go back.)
3.1 Power up and start the Xoom.
3.2 Ensure that your device is fully recognized by the computer. A good sign is that the 'Portable device' dialog is activated on Windows when your Xoom has booted. The Xoom should also be seen in 'Computer'. If not, go back to step 2 and double check your USB drivers.
3.3 Use the command 'adb reboot bootloader' to go into Flash mode.
3.4 Use the command 'fastboot oem unlock'. This will trigger a dialog on your Xoom. Follow the instructions on the screen to complete the unlocking. I repeat, this *will* do a factory reset and all data will be lost!
3.5 Once unlocked, the Xoom will restart and work as normal. Don't bother to do any setup at this time, just make sure that USB debbuging is checked in settings, and now go on to step 4
4. Install recovery image (CWM) UPDATED 4/19/12
If you haven't done it already, download the recovery image file and save it to your computer in the Platform Tools folder.
(Download the recovery image from this link: http://forum.xda-developers.com/showthread.php?t=1604014 only the img file flashed through fastboot Remember, never try to flash a zip file through fastboot!)
Important: At this time, make sure you have a good (known to be working) microsd card in your sdcard slot in your Xoom. Reboot the Xoom with the sdcard in the slot to make sure it's mounted.
4.1 Boot into flash mode with 'adb reboot bootloader.'
4.2 Install your downloaded recovery image: 'fastboot flash recovery eos-recovery-r6.img' or whatever is the exact name of the recovery img file you are flashing.
4.3 Enter CWM recovery with the procedure below.
4.4 Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo section 4.
4.5 Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work (if you see Starting Fastboot Protocol), experiment with the timing (see below).
4.6 When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for getting this far!
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. Just repeat steps 4.1 through 4.6 if that happens.
UPDATE(12/28/11) Since putting this guide together, Motorola has issued a number of Over-the-Air (OTA) updates that have complicated the process of flashing the Clockawork Mod recovery, so if you have accepted any OTA updates, please read the following, which describes each step (http://forum.xda-developers.com/showthread.php?p=26009191#post26008083) (Thanks to Landorin.)
(If you have root and want to remove these files, remove or rename /system/etc/install-recovery.sh with something like root explorer. You can then flash your custom recovery through fastboot again.)
For those of you that get stuck with some error like 'device not recognized' poster Madjinj gives the following advice:
1) Be sure that you have your adb folder in the root of C drive directly and be sure that you are in adb folder in command prompt program (CMD in Windows machines) i.e by typing "cd c:\XXX" where XXX is the name of adb folder in your machine.
2) Be sure that you type "adb reboot bootloader" in comand prompt to activate adb program. if the problem persists, try typing "fastboot reboot" then after reboot type "adb reboot bootloader" in command prompt program.
3) Use the USB cable that came with your Xoom (some cables are not good in flashing for unknown reason..!!
4) make sure that you activate USB debugging mode.
5.0. Rooting the Xoom
The Universal Xoom Root zip file from solarnz is located here: http://forum.xda-developers.com/showthread.php?t=1242241
5.1 You need to transfer the Universal Xoom Root zip file to a working external micro SD card. You can do this on a computer or cell phone, but the Universal Xoom Root zip file must be located in the root directory of the micro SD card.
5.2 Insert the now prepared SD card in the Xoom.
5.3 Boot into recovery (as described in 4.3). Navigate using the volume buttons and press the power button to select the active option.
5.4 Select 'Install ZIP from sd card.'
5.5 Select 'Choose ZIP.'
5.6 Navigate to the ROOT zip file with the Volume buttons and select it with the Power button. Confirm that you want to install it.
5.7 Everything should indicate success, so back out to the main CWM menu and reboot the device.
5.8 From Android Market, install any app requiring root and start it. If the rooting was successful, then the app should request superuser permission and you should be able to grant it without any problems.
6. Flashing a new rom or kernel...(e.g. Tiamat Moray Rom and/or Odachi Kernel). Look in the Xoom Heaven thread or in the Development section of this form for all of these files.
6.1 This step is identical to 5, but swap out the ROOT zip for the ROM or KERNEL zip. For simplicity, you may want to prepare the micro SD card with both zip files at the same time in step 5.1..."
------------------------
This is still one of the best explanations of how to use adb and fastboot to unlock and root the Xoom and install a custom recovery, etc, and doesn't deserve to buries on back pages of this forum. Hopefully, the step-by-step nature of this guide will help those of you that have limited experience with this kind of tinkering.
Oh, and please feel free to correct any errors or omissions. As I said, it came from several sources and needed to somewhat updated.
Thank you, just bought my xoom yesterday and was confused on the steps to take!
This has made it as clear as possible for me and will follow your instructions to the letter tonight.
Sent from my MZ604 using xda premium
fastyan said:
Thank you, just bought my xoom yesterday and was confused on the steps to take!
This has made it as clear as possible for me and will follow your instructions to the letter tonight.
Sent from my MZ604 using xda premium
Click to expand...
Click to collapse
Good luck! Let us know how you make out and if anything needs to be clarified.
think im doing something wrong as unlocked fine but when i go to install the recovery file it keeps coming up cannot load? any ideas where im going wrong?
been at it 3 hours now lol and losing the will to live im sure its gona be something simples
fastyan said:
think im doing something wrong as unlocked fine but when i go to install the recovery file it keeps coming up cannot load? any ideas where im going wrong?
been at it 3 hours now lol and losing the will to live im sure its gona be something simples
Click to expand...
Click to collapse
Check to make sure that your file download is good, and that you are typing it's name correctly. Better yet, you could rename the file "recovery.img" and that will make it very easy to get it right.
On the sd card?I thought we had to put it into sdk platform tools? I have put it and renamed it onto my sd card but what is the command to flash recovery from sd card?
Also noticed once I have done "adb reboot bootloader" my computer doesn't see the XOOM properly, is in can't see it in my computer but does make a noise when I connect and disconnect is this correct? Debugging is on.
Sent from my MZ604 using xda premium
fastyan said:
On the sd card?I thought we had to put it into sdk platform tools? I have put it and renamed it onto my sd card but what is the command to flash recovery from sd card?
Also noticed once I have done "adb reboot bootloader" my computer doesn't see the XOOM properly, is in can't see it in my computer but does make a noise when I connect and disconnect is this correct? Debugging is on.
Sent from my MZ604 using xda premium
Click to expand...
Click to collapse
When you're in the bootloader, you won't be able to access the SD Card or anything of that sort and adb won't work, in stead, when you're in the bootloader, you're switching over to fastboot. I'm sure if you type in fastboot devices you'll see your xoom listed.
Thank you for the reply and that's one thing sorted but any idea why its telling me "cannot load recovery"? I have tried renaming it and downloaded the recovery file 4 times incase that was wrong but still no joy :-(
I have done this all before on my phone and never had a problem so I must be missing something but f$*@ed if I know what?
Thanks again for your help though.
Sent from my Desire HD using xda premium
Just had a thought. Could it be that the XOOM hasn't actually unlocked, would that cause it to not load? Is there any way to check if its unlocked successfully? Although I did try it twice before?
Sent from my MZ604 using xda premium
Once you got it in the bootloader, you gotta make sure you do fastboot oem unlock, press volume down then up, press volume down again then up again, and let it format and reboot.
If it's already unlocked, you'd get a message telling you so (generally).
Then when you go to flash the recovery, make sure that the recovery image is in the folder where fastboot is and type in fastboot flash recovery recovery.img (if I remember the syntax that is, I'm at work and don't feel like scrolling up or going into the root guide to confirm xD ).
fastyan said:
On the sd card?I thought we had to put it into sdk platform tools? I have put it and renamed it onto my sd card but what is the command to flash recovery from sd card?
Also noticed once I have done "adb reboot bootloader" my computer doesn't see the XOOM properly, is in can't see it in my computer but does make a noise when I connect and disconnect is this correct? Debugging is on.
Sent from my MZ604 using xda premium[/QUOTE
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote. Of course the cwm recovery img goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
Click to expand...
Click to collapse
okantomi said:
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote.Oof course the cwm recovery img.. goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
Click to expand...
Click to collapse
With the way I have my system setup, I can run adb and fastboot wherever I am
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote. Of course the cwm recovery img goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
No progress yet as im at work but when I get home I will start the process from scratch again and see how I get on and will keep you posted.
scsa20 said:
With the way I have my system setup, I can run adb and fastboot wherever I am
Click to expand...
Click to collapse
Care to share???
That would be helpful to many, I'm sure. We could add it to the guide, along with anything else you can think of.
fastyan said:
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote. Of course the cwm recovery img goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
No progress yet as im at work but when I get home I will start the process from scratch again and see how I get on and will keep you posted.
Click to expand...
Click to collapse
If, as you follow this guide, you find any explanations that are not clear or if you think of a step to take or something else that might improve the guide, please post it and we can add it in. It's been almost 6 months since I've unlocked and at least a couple of months since I've had to use adb, so I'm sure I've forgotten some things. Those of you whose experience is fresh can give really good advice. That's how this guide was originally written, by pingvinen, right after he had gone through a grueling rooting process.
okantomi said:
Care to share???
That would be helpful to many, I'm sure. We could add it to the guide, along with anything else you can think of.
Click to expand...
Click to collapse
For windows, if you go into System Properties and choose Advanced, then Environment Variables..., you'll be able to edit the Path variable under System variables, just add the path to where adb and fastboot is located (separated with a semi-colon (;)).
Here's what my Path variable looks like:
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\android-sdk-windows\tools;C:\android-sdk-windows\platform-tools;C:\Program Files (x86)\Common Files\Acronis\SnapAPI\
Click to expand...
Click to collapse
It's long but hey, see where the android stuff is near the end?
@Okantomi:
We all have learned some things from trial & error (eg.the sk cannot detect java dev kit)
i could only flash recovery after renaming it to recovery(do not forget to add.img in cmd while flashing).also the official motorola name recovery as same.
after downloading sdk and updating to platform tools i have kept a zip in safe location so that i do not need to download again platform tools if i install sdk fresh
initially knowledge was scattered now it is at one place.
right now testing steady hawkin's kernel and new recovery
btw good signature pic.
Ok so another night has gone and still can't get recovery on!! Tried re unlocking the XOOM and every time it comes up with "cannot load recovery.img" I tried installing everything on my laptop and went right from the start and getting exactly the same thing!
Starting to think im never gonna get this sorted now :-( just feels like the XOOM isn't unlocking? Every time I go through the unlocking process it never states that its already unlocked? Is there any way I can check that it is unlocked?
Please help im losing the will to live now lol
Sent from my MZ604 using xda premium
I would say to send it to me and I can take a wack at it but I don't think you want to wait that long to simply root it.
Let me ask you, are you getting any sort of error messages when you do fastboot flash recovery recovery.img? If so, what's that error message?
scsa20 said:
I would say to send it to me and I can take a wack at it but I don't think you want to wait that long to simply root it.
Let me ask you, are you getting any sort of error messages when you do fastboot flash recovery recovery.img? If so, what's that error message?
Click to expand...
Click to collapse
Not getting any error message it just says "cannot load recovery.img"
I have tried with and without the .img and always the same?
Tried going through the whole process again on my laptop incase I had missed something but exactly the same.
When I unlock it I follow the onscreen instructions and at the end it says its complete before it reboots. Then I turn on usb debugging again and reboot bootloader all ok but won't let me load the new recovery?
Normally I would just say it wasn't meant to be and leave as it is but I wont be beaten on this so I'm purposely not installing anything on it till its done. Any ideas apart from bringing it round yours lol ;-)
Sent from my Desire HD using xda premium

How To: Unlock bootloader and Root using a Mac

This process is very similar to how its done on Windows but I thought I would go ahead and post it here for those who have never rooted or used terminal before. I know the first time I rooted an Android device I was very happy to have a Mac specific guide to follow . Many of you may think this is simplified too much but, like I said, I created this with first time rooters in mind. If a Mod would like to sticky it thats fine. Also, I've tried to be very careful and thorough with the instructions, but if anyone notices a problem please let me know.
As always, I am not responsible if something goes wrong and your device gets bricked. I will try to be as specific as possible and this process worked for me. Also, I don't claim to have the knowledge to fix any problems you may encounter along the way. There are a lot of very talented people here who have extensive knowledge of Android, but I am not one of them. I can unlock my bootloader and root my device but that's about it. So if you do encounter a problem I will try to help but there is no guarantee I can fix the issue (in fact the odds are that I can't fix the issue). Proceed with caution!
Important: Unlocking your bootloader will wipe your device! Please backup anything that is important (pics, vids, documents, etc)!
This guide only applies to the 2013 Nexus 7
A. Prep
1. Charge the Nexus 7 to at least 80% so it doesn't turn off during the process
2. Unlock developer options by navigating to -- settings > about tablet -- and then click the build number 7 times
3. Enable USB Debugging by navigating to -- settings > developer options -- and select the USB Debugging box
4. Download the Android SDK for Mac here and unzip it once it has downloaded. DO NOT use the link posted below for the sdk. It does not contain fastboot and you will not be able to complete the rooting process. Please use the full sdk from Google that I have linked here. EDIT: Google has changed the download for the SDK. Please see posts 73-75 on page 8 for instructions regarding how to get everything you will need for the SDK.
5. Download the latest TWRP for your device here and place it in the platform-tools folder of the SDK. Make sure the TWRP file you download is for the 2013 Nexus 7...not the 2012 version. To find the platform-tools folder -- open the adt-bundle-mac folder you downloaded and unzipped > sdk > platform-tools -- place the TWRP file here. Other files in the platform-tools folder should include adb, api, fastboot, notice.txt, and a few others.
B. Unlock the Bootloader - Warning--This will wipe your device! Backup anything important!
1. With your device powered on, plug it into your Mac
2. Open up terminal and navigate to the platform-tools folder which has the adb, fastboot, and TWRP files. An easy way to do this is to type "cd" (without the quotes) into terminal, add a single space, and then drag and drop the platform-tools folder onto terminal and then press enter.
3. Type this command into terminal: ./adb reboot bootloader
4. If you correctly navigated to the platform-tools folder, you should get an error message saying the device is unauthorized. Go to the Nexus 7 and there should be a dialogue box asking you to authorize the computer. Authorize the computer.
5. Re-type the command: ./adb reboot bootloader
6. Your device should now boot into fastboot mode. On your N7, the word "start" will be at the top in green and you can also see a lot of your device information on this screen
7. Type into terminal: ./fastboot oem unlock
8. Your Nexus 7 will now display a message about unlocking your device. Use the volume button to select the option to unlock the device and then press the power button to confirm the choice.
9. Your device will return to the fastboot mode screen and you can now see in the device information section near the bottom that the device is unlocked. While on this screen, press the power button to select the green "start", which will reboot your device. You must restart your device here or you will run into a softbrick issue during the root process!
10. Congrats! Your device is now unlocked. If you want to root proceed to the next section.
C. Rooting
1. Once your device has rebooted from the unlocking process, everything will have been wiped and reset. You will have to go back and unlock developer options again and you will also have to enable USB debugging again, which can be found part A. Prep of this guide.
2. Download the current version of SuperSU to your Nexus 7. It will go to the download folder on your N7. It can be found here. (Note: The version of SuperSU I have linked to is 1.93, but it gets updated from time to time. You might want to look around and see if a more current version is available. The thread for SuperSU can be found here.)
3. Turn your N7 off and then boot into fastboot mode by pressing the Volume Down button while also pressing the Power Button to turn the device on. If done correctly you should see the green "start" again at the top and the device information near the bottom.
4. Plug the N7 into the computer and make sure terminal is still directed to your platform-tools folder. For instructions on how to navigate to the platform-tools folder see part B. Unlock the bootloader.
5. Type the following into terminal: ./fastboot flash recovery nameofTWRPrecovery.img
5a. For the nameofTWRPrecovery.img part above, you must type the exact file name of whatever TWRP (or other) recovery you've decided to use. This is the same file that you downloaded and placed in the platform-tools folder in Part A. Step 5. above. For me the file name I had to type was openrecovery-twrp-2.6.0.0-flo.img and the total command looked like this: ./fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img
6. In terminal you should see the process taking place and it will tell you when its finished and how long it took (less than a second).
7. Now, while still in fastboot mode, use the volume button to navigate to Recovery and press the power button.
8. The N7 will boot into TWRP which we just installed.
9. Using the touch screen, select install and then navigate to the download folder where you saved the SuperSU file
10. Select the SuperSU file using the touchscreen and then swipe to flash it. You will see the rooting process occur on the screen.
11. Congrats! You are now rooted. Select Reboot System and you are done!
Your instructions couldn't be any simpler. I am unlocked and rooted now. This is my first Android device. Thank you very much.
Glad it was helpful for you!
Is there any step involved to install drivers here which I saw mentioned while using Windows system?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Very nice guide! Well done
Sent from my Nexus 7 2013 using xda app-developers App
redhat_123 said:
Is there any step involved to install drivers here which I saw mentioned while using Windows system?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
No, you don't need any drivers for the Mac (which makes it simpler than the Windows process in my opinion). I've included links in the how-to for everything you will need .
geckocavemen said:
No, you don't need any drivers for the Mac (which makes it simpler than the Windows process in my opinion). I've included links in the how-to for everything you will need .
Click to expand...
Click to collapse
Thanks a lot. This is the first time I used MAC to unlock and root a device and it was very quick. Appreciate your effort in putting up the detailed steps.
I just saw this post so I figured I may as well chime in. I've been rooting devices and using adb for years, so the issues wasn't a lack of experience.
I was having an issues with my device being reported as 'Offline'. Despite downloading the SDK several times I was unable to get the latest version.
I posted a thread last week with the updated version of adb needed for OS X in case anyone runs into this same issues that I did: http://forum.xda-developers.com/showthread.php?t=2390999
wad3g said:
I just saw this post so I figured I may as well chime in. I've been rooting devices and using adb for years, so the issues wasn't a lack of experience.
I was having an issues with my device being reported as 'Offline'. Despite downloading the SDK several times I was unable to get the latest version.
I posted a thread last week with the updated version of adb needed for OS X in case anyone runs into this same issues that I did: http://forum.xda-developers.com/showthread.php?t=2390999
Click to expand...
Click to collapse
Hi wad3g, was the problem you ran into related to the link for the Mac sdk I posted in the guide? If it was with my link I'd like to fix it so others don't have the same issue. Thanks!
EDITED TO ADD: Please only use the link in the how-to for the full sdk from Google. wad3g's link only has adb but not fastboot. To complete the rooting process you will need fastboot also.
geckocavemen said:
Hi wad3g, was the problem you ran into related to the link for the Mac sdk I posted in the guide? If it was with my link I'd like to fix it so others don't have the same issue. Thanks!
Click to expand...
Click to collapse
Yes, it is from the same link as above on Google's developer site. They hadn't updated the SDK yet, so each time I downloaded ADB v1.0.29 - ADB for 4.2. I was finally able to find ADB & Fastboot v1.0.31 for Android 4.3. Also, just so you know, the .zip on my thread is not the full SDK. If you're not a developer you don't need the full SDK, so for most the rooter's here my zip will be all that is needed.
You may just want to mention checking what version of ADB you're running prior to start or if you're having any issues. If you're running an older version than 1.0.31 you need to update.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hope this helps! Let me know if you have any other questions.
Thanks wad3g. But just to clarify, Google updated the Mac version of the sdk on the 29th of July so the link in the original how-to will work for any version of Android. It's the same thing I used to download the sdk and I'm running version 1.0.31. Also, as mentioned it does contain more than is strictly necessary for unlocking and rooting. However, the original link in the how-to will provide you with the most up-to-date version of the Mac sdk that Google has released, should they update it in the future.
Please Help!!!
Hi I followed all your instructions and right when i was ready and tried to flash the recovery, I get this list of options after waiting for device:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address. default: 0x10000000
-n <page size> specify the nand page size. default: 2048
-S <size>[K|M|G] automatically sparse files greater than
size. 0 to disable
I don't understand what I should pick or if I should pick any. Please help as soon as possible.
EDIT: The reason I got this list is because I dragged in the fastboot into the terminal because when I tried to enter ./fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img, it said this: -bash: fastboot: command not found
Don't worry you haven't broken anything. What you saw is basically just a message that says you entered an incorrect command and then it presents a list of acceptable commands. Just start the section C. Rooting over again and don't move the recovery file into the command window...just type the full name of the recovery file instead.
EDIT...I think I didn't understand your edit properly the first time. I think you got the bash message because terminal was no longer pointed at the platform-tools folder. To do the rooting process you must make sure terminal is still directed at platform-tools folder. It should still be if you didn't close terminal or do anything else in terminal after the unlocking process. However, if terminal is not directed to the platform-tools folder you can use the "cd" command found in part B. of the how-to to get terminal pointed to the right place again. Once you've done that you can just start Part C. again and all should be fine. When I rooted I just left terminal open after completing the unlocking process and it was still directed at platform-tools. If you closed terminal it wouldn't be pointed at the right location where fastboot is.
One other thing: Are you sure there is a fastboot file in your platform-tools folder? It should look just like the adb file except it will be named fastboot instead.
LAST EDIT PLEASE READ: I'm assuming you used wad3g's download because I just checked and it does not have a fastboot file in it and that is why you got the -bash message. Please use the link in the how-to to download the full sdk from google. Pull out the fastboot file from Google's sdk and put it wherever you put your adb file that you got from wad3g. At that point you will be able to continue with Part C. Rooting.
Hope that last edit of mine helped out. Just follow the how-to step by step (including my links) and you'll be ok.
Thanks So Much But One Last Question
geckocavemen said:
Don't worry you haven't broken anything. What you saw is basically just a message that says you entered an incorrect command and then it presents a list of acceptable commands. Just start the section C. Rooting over again and don't move the recovery file into the command window...just type the full name of the recovery file instead.
EDIT...I think I didn't understand your edit properly the first time. I think you got the bash message because terminal was no longer pointed at the platform-tools folder. To do the rooting process you must make sure terminal is still directed at platform-tools folder. It should still be if you didn't close terminal or do anything else in terminal after the unlocking process. However, if terminal is not directed to the platform-tools folder you can use the "cd" command found in part B. of the how-to to get terminal pointed to the right place again. Once you've done that you can just start Part C. again and all should be fine. When I rooted I just left terminal open after completing the unlocking process and it was still directed at platform-tools. If you closed terminal it wouldn't be pointed at the right location where fastboot is.
One other thing: Are you sure there is a fastboot file in your platform-tools folder? It should look just like the adb file except it will be named fastboot instead.
LAST EDIT PLEASE READ: I'm assuming you used wad3g's download because I just checked and it does not have a fastboot file in it and that is why you got the -bash message. Please use the link in the how-to to download the full sdk from google. Pull out the fastboot file from Google's sdk and put it wherever you put your adb file that you got from wad3g. At that point you will be able to continue with Part C. Rooting.
Click to expand...
Click to collapse
Again in a bit of a sticky pickle. I got it to work because my problem was that I didn't direct the terminal to the folder. Now I am booted into TWRP but I don't understand what you mean by the SuperSu file. I it just the whole folder titled UPDATE-SUPERSU-v1.51?
EDIT: OMG IT WORKED!!! Thanks so much I got it rooted and it works awesome now!!!
Best tutorial for mac ever
I found this so helpful and easy! My nexus 7 is rooted now!:good:
:good::good::good::good:
thanks a lot
Thanks for the guide.
Want to say thanks for your very detailed explanations.
If I may, I would like to suggest one more step after the final step. Make a Nandroid backup. That really helps a lot for people who screwed stuff up.
Yes, creating a nandroid backup is very important and can definitely save you when flashing Roms and stuff if something goes wrong. Creating a nandroid before rooting could get you back to stock with an unlocked botloader too. But I guess that isn't as important now that Google has released the factory images.
Sent from my Nexus 7 using xda app-developers app

Hdx 8.9 3th gen install android

I rooted my tablet by using king root but I don't know what to do for android. Can someone tell me how to do that. I'm in the latest version and using windows computer
Practically said:
I rooted my tablet by using king root but I don't know what to do for android. Can someone tell me how to do that. I'm in the latest version and using windows computer
Click to expand...
Click to collapse
Wait - I responded to a PM and directed you to the appropriate thread. Please check your mail and proceed accordingly. The HDX forums have a wealth of information that should allow you to unlock your device and install a custom ROM with minimal effort.
Thanks for answer @Davey126 I red your mail but I still have some questions. I bought this tablet yesterday and this is my very first Android experience. I got how to root and unlock my device but I don't know the rest I mean is there any thread for very beginners ?
Practically said:
Thanks for answer @Davey126 I red your mail but I still have some questions. I bought this tablet yesterday and this is my very first Android experience. I got how to root and unlock my device but I don't know the rest I mean is there any thread for very beginners ?
Click to expand...
Click to collapse
If your device is currently unlocked you should be able to launch a custom recovery environment called TWRP. That's where most device maintenance is performed such as installing different versions of 'android' otherwise known as custom ROMs. Try this:
- power off device
- press and hold <power>+<vol-up> until Kindle Fire logo appears
- immediatlely release power button followed by volume 1-2 seconds later
- wait a few more seconds for next screen to appear
- what happens?
To exit recovery mode long press power until device shuts off. A short press will start the device normally.
Your response will determine next steps. If TWRP is present you're just a few steps away from installing a custom ROM. If stock Amazon recovery appears (just two options) then there is more work to be done.
Davey126 said:
If your device is currently unlocked you should be able to launch a custom recovery environment called TWRP. That's where most device maintenance is performed such as installing different versions of 'android' otherwise known as custom ROMs. Try this:
- power off device
- press and hold <power>+<vol-up> until Kindle Fire logo appears
- immediatlely release power button followed by volume 1-2 seconds later
- wait a few more seconds for next screen to appear
- what happens?
To exit recovery mode long press power until device shuts off. A short press will start the device normally.
Your response will determine next steps. If TWRP is present you're just a few steps away from installing a custom ROM. If stock Amazon recovery appears (just two options) then there is more work to be done.
Click to expand...
Click to collapse
I dont get this mean
Run:
Code:
adb shell
su
dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot
how can i run this
Practically said:
I dont get this mean
Run:
Code:
adb shell
su
dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot
how can i run this
Click to expand...
Click to collapse
I'm stuck at waiting for any device screen and there is fastboot text on my tablet
Practically said:
I dont get this mean
Run:
Code:
adb shell
su
dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot
how can i run this
Click to expand...
Click to collapse
In Windows Dos prompt
Practically said:
I'm stuck at waiting for any device screen and there is fastboot text on my tablet
Click to expand...
Click to collapse
Your driver not installed properly. Pls just follow my thread tips.
@kkcheong sorry for bother you just to clarify my situation. I rooted my tablet and spent 8 hours yesterday to unlock it but couldn't. First of all code_generator.bat works fine it creates unlock.code file. however When i apply the unlock bat I got an error on my tablet screen which says unlock code is not correct. Can you help me about what to do by explaining to very very very noob person. Another issue is i cant copy the 2 files to root folder i tried es browser and root browser.
1. I think your ADB driver not properly install. Check your Hardware Device in your windows for ADB. If no such ADB in your Hardware means you have install ADB properly
2. You cannot copy to root? You maybe need to enable R/W with root explorer or es explorer root.
Practically said:
@kkcheong sorry for bother you just to clarify my situation. I rooted my tablet and spent 8 hours yesterday to unlock it but couldn't. First of all code_generator.bat works fine it creates unlock.code file. however When i apply the unlock bat I got an error on my tablet screen which says unlock code is not correct. Can you help me about what to do by explaining to very very very noob person. Another issue is i cant copy the 2 files to root folder i tried es browser and root browser.
Click to expand...
Click to collapse
Practically said:
@kkcheong sorry for bother you just to clarify my situation. I rooted my tablet and spent 8 hours yesterday to unlock it but couldn't. First of all code_generator.bat works fine it creates unlock.code file. however When i apply the unlock bat I got an error on my tablet screen which says unlock code is not correct. Can you help me about what to do by explaining to very very very noob person. Another issue is i cant copy the 2 files to root folder i tried es browser and root browser.
Click to expand...
Click to collapse
Suspect vulnerable bootloader (and cubed TWRP) have not been installed as outlined in step #2 of the unlock thread OP.
I can transfer the two file to root folder. Now what should I do. Sorry for long questions but I have limited opportunity for using a computer since I don't have. I use friend of mine's. I want to make sure I got every step correctly. In the post I can do generate code thing. I successfully generate unlock.code file but the whe I write adb shell in cmd I got error something like adb is not recognised. Do you have any idea of any script file that do these things automatically.
So
Step 1 Done
Two files was copied to root folder
But stuck at code thing. Btw I don't have any driver issue since I can enable fastboot and get Unock code is wrong error
Practically said:
I can transfer the two file to root folder. Now what should I do. Sorry for long questions but I have limited opportunity for using a computer since I don't have. I use friend of mine's. I want to make sure I got every step correctly. In the post I can do generate code thing. I successfully generate unlock.code file but the whe I write adb shell in cmd I got error something like adb is not recognised. Do you have any idea of any script file that do these things automatically.
So
Step 1 Done
Two files was copied to root folder
But stuck at code thing. Btw I don't have any driver issue since I can enable fastboot and get Unock code is wrong error
Click to expand...
Click to collapse
You need to access the device via adb to issue the commands listed in step #2 of the unlock post:
- boot into FireOS and unlock device
- enable USB debugging from the FireOS settings menu (Google if you need help finding it)
- tether device; you may get an authorization prompt on device (look for it)
- there may be a notification indicating device is connected in 'charge mode'; switch it to 'file transfer' also known as 'MTP'
- open a Windows command prompt and navigate to folder where adb/fastboot commands live
- issue commands referenced in above post
If the host you are using does have (or you can't find) adb/fastboot installing the following package may be beneficial: https://forum.xda-developers.com/showpost.php?p=42407269&postcount=1

Categories

Resources