[HOW TO][UPDATED GUIDE] Unlocking & Rooting your XOOM! - Xoom General

UPDATED XOOM FLASHING GUIDE 02/02/12​
I recently bought a US Xoom MZ604 and had trouble flashing it initially. I came to a realization that the newer models of Xoom reinstalls the Stock Recovery after you flash a custom Recovery (eg. CWM, Rogue Recovery etc). This is uber frustrating for newer Xoom owners, especially those who are new to the flashing community, simply because you don not know exactly what's going on.
Also, I could not find any proper, full and updated guide to flashing your Xoom. So i decided to take the initiative to do so.
WARNING: I DO NOT TAKE ANY RESPONSIBILITY IF YOUR XOOM TURNS INTO A USELESS BRICK. BY FOLLOWING THIS GUIDE, YOU WILL VOID YOUR XOOM WARRANTY WITH MOTOROLA. YOU HAVE BEEN WARNED TO EXERCISE CAUTION WHILE FOLLOWING THIS GUIDE. STRICTLY FOLLOW THIS GUIDE AND I ASSURE YOU, NOTHING WOULD GO WRONG.
In order to follow this guide, you need fundamental knowledge of ADB and Fastboot for Android. Search around the forum for this knowledge.
STEP 1: Obtaining Required Materials
a.) Download the latest version of Android SDK from HERE and install it into your the root of your C: drive.
b.) Download the latest version of Java SE from HERE and install.
c.) Download and Install the latest version of Motorola USB Drivers from HERE.
STEP 2: Unlocking your Bootloader
What is a Bootloader?
In literal terms, bootloader is code that is executed before any Operating System starts to run. The concept of bootloaders is universal to virtually all Operating systems that inculcates operating systems on your PC, laptop, smartphones, and other such devices. Bootloaders basically package the instructions to boot operating system kernel and most of them also have their own debugging or modification environment. As the bootloader kicks off before any piece of software on your device, it makes it extremely processor specific and every motherboard has it’s own bootloader. Source: http://www.addictivetips.com/mobile/what-is-bootloader-and-how-to-unlock-bootloader-on-android-phones-complete-guide/
Click to expand...
Click to collapse
1.) Make sure your Xoom is turned on. Connect it to your PC via USB.
2.) On your PC, open up File Explorer and Browse to:
C:\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
3.) In that directory, make sure nothing is selected, SHIFT+Right Click into empty space and select "Open command window here".
4.) Command Prompt will open up. Type the following command:
adb reboot bootloader
Click to expand...
Click to collapse
Your XOOM will reboot into the bootloader showing "Starting Fastboot Support Protocol".
6.) Type the following command into the Command Prompt to unlock your bootloader:
fastboot oem unlock
Click to expand...
Click to collapse
7.) Read the warning and follow the instructions on the Xoom Tablet itself from this point onwards. Use the Volume Down key to navigate to 'Accept' the agreement and press Volume Up to select.
8.) Once selected, your Xoom will now unlock and format itself, meaning, all data will be cleared and you will back to a factory rest.
9.) Reboot your Xoom with the following command:
fastboot reboot
Click to expand...
Click to collapse
10.) Exit Command Prompt.
STEP 3: Rooting your Xoom
1.) Download the latest version of "Universal Xoom Root" from this thread. Place the .ZIP file into the root of your SD card.
2. Download this version of "ClockworkMod Recovery - Modified for Motorola Xoom" and place it into this directory:
C:\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
This will your new Recovery. MAKE SURE THAT IT IS IN .IMG FORMAT.
2.) With your Xoom still connected to your PC, type the following commands into Command Prompt (open up using the same method as STEP 1) to install your new Recovery.
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Click to expand...
Click to collapse
3.) Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery. If you miss this window and somehow end up booting your Xoom normally, repeat from STEP 3, section 2 onwards again. DO NOT CLOSE THE COMMAND PROMPT WINDOW.
4.)To root your Xoom, please perform the following:
"install zip from sdcard" -> "Choose zip from sdcard", then select the Xoom-Universal-Root.zip file you downloaded.
Note: use the volume buttons to navigate and the power button to select
Click to expand...
Click to collapse
After the root flashes itself, DO NOT REBOOT YOUR XOOM!
5.) Now you have to rename the 2 notorious files, that reinstall your Stock Recovery over CWM, into a format that is unreadable by the bootloader. In the already opened Command Prompt, type the following commands:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
Click to expand...
Click to collapse
6.) Reboot with CWM. Let your Xoom boot normally.
To test whether the root and flashing of CWM has been successful, type the following into your command prompt:
adb reboot recovery
Click to expand...
Click to collapse
If you are able to access the new Recovery, CONGRATULATIONS, you have successfully UNLOCKED & ROOTED your Xoom.
I would like to thank the Xoom Android community for your valuable commitment to into Xoom Android Development. Without you guys, the Xoom wouldn't feel much powerful in terms of usage. Also, I'd like to extend my gratitude to okantomi for his help when I first started out.
Those those experienced users of Xoom, please kindly help the newbies like me answer their questions in this thread. Could I also request the mods to sticky this thread for reference.
NOTE: For users who would like to revert to the original recovery, type the following into ADB: (tip provided by wontoniii)
adb shell mv /system/recovery-from-boot.p.old /system/recovery-from-boot.p
adb shell mv /system/etc/install-recovery.sh.old /system/etc/install-recovery.sh
adb reboot
Click to expand...
Click to collapse
Reference Threads:
1.) [Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]
2.) [ROM][Nightly][ICS] Team Eos WiFi Nightlies (Wingray/MZ604)
3.) [Root] Universal Xoom Root - ANY XOOM ANY UPDATE

Just my opinion, I would not recommend to everybody the step3/point6 as you do it...
I would just do something like:
adb remount
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
Click to expand...
Click to collapse
This can be easily reverted with:
adb remount
adb shell mv /system/etc/install-recovery.sh.old /system/etc/install-recovery.sh
Click to expand...
Click to collapse
In case someone could want the old recovery back without flashing anything

wontoniii said:
Just my opinion, I would not recommend to everybody the step3/point6 as you do it...
I would just do something like:
This can be easily reverted with:
In case someone could want the old recovery back without flashing anything
Click to expand...
Click to collapse
I believe your method is better, at least there's still a recovery to revert to in case something goes wrong. I'll add it to the guide. Thanks for the suggestion!
Sent from my Xoom using Tapatalk

My tool can do it automatically, check on the signature LordAIOTool, and if you guys can please test and tell me the results
---------- Post added at 08:57 PM ---------- Previous post was at 08:39 PM ----------
wontoniii said:
Just my opinion, I would not recommend to everybody the step3/point6 as you do it...
I would just do something like:
This can be easily reverted with:
In case someone could want the old recovery back without flashing anything
Click to expand...
Click to collapse
I liked your idea too, will put on my tool (can I?)

XxLordxX said:
I liked your idea too, will put on my tool (can I?)
Click to expand...
Click to collapse
Sure, no prob

Thread moved to General.

This seams to be a good guide can anyone tell me if it works it is more detailed than the other guide ???? and why was it moved to general

This guide is great and easy and very updated i dont know why other people dont use it. One thing tho you should be more clear on how to reboot into recovery tell them to press volume up + power then let go then wait three seconds and after logo and press only the volume down

Having a problem with using your guide
Ok, I'm a noob. I am probably missing something simple. When I type "adb reboot bootloader" at the command prompt it says "Device not found." My Xoom is connected via USB (Same cable it came with). Xoom appears in my explorer window I can browse through the files; I even transferred files to the SD card. It is just not detected from the command prompt window when I start the unlocking procedure. Any assistance would be appreciated. Using Xoom 4G, Android 3.2.4; Windows 7

Make sure that adb debugging is checked. You can find this under Applications > Development settings.
Before you type, check if your device is listed
Code:
adb devices
This should list your device.
dstruble said:
Ok, I'm a noob. I am probably missing something simple. When I type "adb reboot bootloader" at the command prompt it says "Device not found." My Xoom is connected via USB (Same cable it came with). Xoom appears in my explorer window I can browse through the files; I even transferred files to the SD card. It is just not detected from the command prompt window when I start the unlocking procedure. Any assistance would be appreciated. Using Xoom 4G, Android 3.2.4; Windows 7
Click to expand...
Click to collapse

kewlguru said:
Make sure that adb debugging is checked. You can find this under Applications > Development settings.
Before you type, check if your device is listed
Code:
adb devices
This should list your device.
Click to expand...
Click to collapse
That did the trick I figured it was something simple like that. Thanks for the help.

Superb Guide!
Many thanks, I spent the best part of a day trying various methods but found this to be the most n00b friendly
1 point it may be worth adding is to use adb you must have java installed on your pc, without you get error "adb.exe is not a valid win32 application"

first time root/flash rom question
Hi all..to start with sorry if im asking in the wrong place. I have a stock Xoom with an unmodded ICS I also own the Bionic. Also I have never rooted or flashed anything so I am a super noob (soon to change though).
I wated to be able to have USB host functionality and be able to have SD card read/write assess so last week I started searching Google which led me to this wonderful sight of great help. There might be too much help because after tons of reading there is more than one way to do what I want. Can someone please point me in the best way to root and which rom I should use that will give me the least about of trouble.
Thanks in advance

Don_Don said:
Hi all..to start with sorry if im asking in the wrong place. I have a stock Xoom with an unmodded ICS I also own the Bionic. Also I have never rooted or flashed anything so I am a super noob (soon to change though).
I wated to be able to have USB host functionality and be able to have SD card read/write assess so last week I started searching Google which led me to this wonderful sight of great help. There might be too much help because after tons of reading there is more than one way to do what I want. Can someone please point me in the best way to root and which rom I should use that will give me the least about of trouble.
Thanks in advance
Click to expand...
Click to collapse
Ihave similar story m8. I spent the majority of yesterday reading and learning how to root. This is by far the easiest guide to follow to ulock and root your xoom.

I just want to correct a small error here.
In Step 6 of Step 3, you say you want to check and make sure that the new bootloader is on there correctly.
I think you mean to say check and make sure the new "Recovery" is on there and the adb command would be "adb reboot recovery".
Am I wrong? If so, please disregard.

At which point do I back up data already on Xoom? Will there be any data loss?

Don_Don said:
At which point do I back up data already on Xoom? Will there be any data loss?
Click to expand...
Click to collapse
You have to backup your data before unlocking the bootloader, which is the VERY FIRST step.

gbenj said:
I just want to correct a small error here.
In Step 6 of Step 3, you say you want to check and make sure that the new bootloader is on there correctly.
I think you mean to say check and make sure the new "Recovery" is on there and the adb command would be "adb reboot recovery".
Am I wrong? If so, please disregard.
Click to expand...
Click to collapse
Yes you are right. Thanks for pointing that it, it could have confused some. I'll rectify that right away.

Ok so I have a question about this rooting process and I haven't seen the answer yet. My question is will this process work weather your xoom is running ICS or HC?

TADitto said:
Ok so I have a question about this rooting process and I haven't seen the answer yet. My question is will this process work weather your xoom is running ICS or HC?
Click to expand...
Click to collapse
Yes, this process will work regardless of your OS.

Related

[GUIDE] MAC Rooting Nexus S

1/27/11 Update: Some members have commented that the MoDaCo Superboot method is easier, and although I haven't used it myself, it does look easier. If you want to go that route instead, you'll still need to unlock your bootloader, which means completing Steps 1-5 below. After that, you can go with the method given here: http://forum.xda-developers.com/showthread.php?t=927838
________________________________________________________
The following directions should let you root your Nexus S using an Intel Mac running OS 10.5 or 10.6. Thanks to Koush for providing the method and the recovery img, to ChainsDD for providing Superuser, and to Luxferro for providing a workaround for 2.3.1.
You should apply the 2.3.1 OTA update before obtaining root. Otherwise you'll have to do it over again after the update. If you installed a rooted/insecure boot image with the original instructions and now find yourself unable to upgrade to 2.3.1 (Status 7 error), one option is to use ROM Manager to restore the 2.3.1 Nandroid backup kindly provided by momohammed20 in this thread. From there, you will have stock 2.3.1 and can follow the steps below to obtain root again.
Warning: If you break your phone trying this, I am not responsible. I do not guarantee that the following is safe or that the steps are correct. Rooting your phone voids the warranty. I have no responsibility for anything that occurs as a result of your following these directions! I cannot provide any support nor guide you in undoing this process and restoring the phone to factory condition.
This process will wipe your phone. Ie, you will lose all your apps/data on your phone and have to reinstall them. It will also wipe your external storage, so back that up prior to proceeding if you want to keep anything.
1) Download the "androidsdk.zip" file from here: http://www.box.net/shared/ljhg8t5sjh
Unzip that file (if not already unzipped automatically upon download), and place the "androidsdk" folder on your Desktop. It has to be in this location for the rest of the steps to work.
2) On your phone, go to Menu>Settings>Applications. Select "Development" and check the box next to "USB debugging"
3) Connect the phone to your Mac via the USB cable
4) Open a Terminal window on your Mac (Applications>Utilities>Terminal), and copy/paste the following into the Terminal:
Code:
~/Desktop/androidsdk/platform-tools/adb reboot bootloader
Hit "Return" and wait for your phone to to reboot into Bootloader/Fastboot mode
5) If your Bootloader screen says "LOCK STATE - UNLOCKED" then skip to Step 6. If it says "LOCK STATE - LOCKED" then copy/paste the following into the Terminal:
Code:
~/Desktop/androidsdk/tools/fastboot oem unlock
Hit "Return" and on your phone will prompt you to confirm and warn you that you are going to lose everything. Confirm. At this point you will have an unlocked bootloader.
6) Copy/paste the following into the Terminal window:
Code:
~/Desktop/androidsdk/tools/fastboot flash recovery ~/Desktop/androidsdk/tools/recovery-clockwork-3.0.0.0-crespo.img
Hit "Return" again and wait for recovery to flash.
7) At this point you should still be in Bootloader/Fastboot mode. DO NOT REBOOT YOUR PHONE*. Press the "Volume Down" key until "RECOVERY" is highlighted, and press the "Power" key to select this option.
*Note: You must go to Recovery directly from Bootloader/Fastboot mode after Step 6 without rebooting your phone in between, or else your phone will replace ClockworkMod Recovery, hang at the "Google" splash screen requiring a battery pull, and you'll need to start again from Step 6.
For the following steps while in Recovery, use "Volume Down" to highlight a selection and "Power" to choose that selection:
8) Choose "mounts and storage"
9) Choose "mount USB storage". Your phone should now be mounted on the Mac as a Device called "NO NAME"
10) Look inside the "androidsdk" folder on your Desktop for a file called "su2361ef.zip", and using the Finder on your Mac, copy that file (without unzipping it) to the main directory of your mounted phone ("NO NAME").
11) Eject/unmount your phone in the Finder on your Mac.
12) On your phone, choose "Unmount"
13) Choose "mount /system"
14) Choose "+++++Go Back+++++"
15) Choose "install zip from sdcard"
16) Choose "choose zip from sdcard"
17) Choose "su2361ef.zip"
At this point you have root, but your phone will continue to replace ClockworkMod Recovery on reboot. To prevent this, do the following:
1) Reboot your phone, and download the app "Root Explorer" from the Market
2) Open Root Explorer and navigate to the "etc" directory.
3) Tap on the gray box that says "Mount R/W"
4) Tap and hold on the file "install-recovery.sh" and rename this file to "install-recovery.sh.old"
5) Download the app "ROM Manager"
6) Open ROM Manager and choose "Flash ClockworkMod Recovery". At this point you are all set .
---------------------------------------------
To re-lock your bootloader (Optional step):
1) With your phone connected and "USB Debugging" still enabled (which it will be unless you disabled it after the above), copy/paste the following to the Terminal:
Code:
~/Desktop/androidsdk/platform-tools/adb reboot bootloader
Hit "Return" and wait for your phone to to reboot into Bootloader/Fastboot mode
2) Copy/paste the following to the Terminal:
Code:
~/Desktop/androidsdk/tools/fastboot oem lock
Hit "Return".
Reboot your phone.
---------------------------------------------
Major thanks to Koush, ChainsDD, momohammed20, and Luxferro!
Your gonna need the recompiled fastboot. Then it makes it super easy.
So whats the advantage of having a rooted/insecure boot image as opposed to not? Sorry for the noob question
thanks x1,000,000
I would be lost without this, thanks a lot!!!
took me about 10-15 minutes
Didn't know I was going to lose all my data though, luckily I've only had it a few days and it all can be replaced
You freaking rock man! Thanks for this. Ill be rooting mine very soon.
I'm a little confused here...
About 1/5 of the way down on that page, find the link for "su-2.3.6.1-ef-signed.zip", which is the link for the Froyo version of Superuser. Control-click (right click) on that link and choose "Download Linked File As..." Save that file (called "su2361ef") to your desktop and then copy it to the main directory of your mounted phone ("NO NAME").
Am I to change the name of this file to "su2361ef" or leave it as is... "su-2.3.6.1-ef-signed.zip" than place it into my main directory?
Thanks
Help please.
I'm down to the final steps, but when I try to get into recovery mode I keep getting a little Android with an "!" over it.
What am I doing wrong? I've pulled the battery, and tried it over a few times, but I keep getting the same thing.
rashad1 said:
thanks x1,000,000
I would be lost without this, thanks a lot!!!
took me about 10-15 minutes
Didn't know I was going to lose all my data though, luckily I've only had it a few days and it all can be replaced
Click to expand...
Click to collapse
Glad it was helpful. You should have gotten a warning on your phone screen about losing the data in Step 10, and you could have turned back at that point. I've now edited the post above to make it clear there as well.
WilliamStern said:
I'm a little confused here...
About 1/5 of the way down on that page, find the link for "su-2.3.6.1-ef-signed.zip", which is the link for the Froyo version of Superuser. Control-click (right click) on that link and choose "Download Linked File As..." Save that file (called "su2361ef") to your desktop and then copy it to the main directory of your mounted phone ("NO NAME").
Am I to change the name of this file to "su2361ef" or leave it as is... "su-2.3.6.1-ef-signed.zip" than place it into my main directory?
Thanks
Click to expand...
Click to collapse
When I did it, the zip was already called "su2361ef". If yours is called "su-2.3.6.1-ef-signed.zip", I would leave it like that without renaming. Just remember the name so you can choose it in Step 21.
WilliamStern said:
Help please.
I'm down to the final steps, but when I try to get into recovery mode I keep getting a little Android with an "!" over it.
What am I doing wrong? I've pulled the battery, and tried it over a few times, but I keep getting the same thing.
Click to expand...
Click to collapse
Which step were you at? I hope someone can help you. I don't have any expertise . I only shared the steps above because they worked for me.
Amin Sabet said:
When I did it, the zip was already called "su2361ef". If yours is called "su-2.3.6.1-ef-signed.zip", I would leave it like that without renaming. Just remember the name so you can choose it in Step 20.
Which step were you at? I hope someone can help you. I don't have any expertise . I only shared the steps above because they worked for me.
Click to expand...
Click to collapse
I keep getting the "!" above the little Android, but when press power button plus volume up I only get 4 options.
-reboot system now
-apply update from /sdcard
-wipe data/factory reset
-wipe cache partition
I'm not seeing any of the other options you mention above.
I WANT ROOT! lol
WilliamStern said:
I keep getting the "!" above the little Android, but when press power button plus volume up I only get 4 options.
-reboot system now
-apply update from /sdcard
-wipe data/factory reset
-wipe cache partition
I'm not seeing any of the other options you mention above.
I WANT ROOT! lol
Click to expand...
Click to collapse
You did not flash the clockworkmod recovery correctly. The Triangle with exclamation point is the stock recovery image.
Redo the step that says fastboot flash recovery etc..etc..
Sent from my Nexus S
How about a noob guide for windows also Not that I wont be able to figure out from other sources when I want to root for the first time. But a noob guide here will come handy as well ;-)
Err... I give up. I just can't seem to get anything to work. I've followed everything step by step and nothing. I think it's my bootloader that won't unlock?
WilliamStern said:
Err... I give up. I just can't seem to get anything to work. I've followed everything step by step and nothing. I think it's my bootloader that won't unlock?
Click to expand...
Click to collapse
we can't help you much if you don't provide any detailed info other than you're not in the right recovery. Boot the phone on again and type this in terminal:
Code:
./adb reboot bootloader
check status of bootloader: LOCKED / UNLOCKED
and we go from there.
jroid said:
we can't help you much if you don't provide any detailed info other than you're not in the right recovery. Boot the phone on again and type this in terminal:
Code:
./adb reboot bootloader
check status of bootloader: LOCKED / UNLOCKED
and we go from there.
Click to expand...
Click to collapse
I think this is where I'm having an issue? Nothing seems to happen whenever I input a command into my terminal on my computer.
WilliamStern said:
I think this is where I'm having an issue? Nothing seems to happen whenever I input a command into my terminal on my computer.
Click to expand...
Click to collapse
What happens if you plug your phone into the USB and type adb devices?
Michael.B. said:
What happens if you plug your phone into the USB and type adb devices?
Click to expand...
Click to collapse
I'm new at all this, so I'm sorry.
this is what I get
-bash: adb: command not found
WilliamStern said:
I'm new at all this, so I'm sorry.
this is what I get
-bash: adb: command not found
Click to expand...
Click to collapse
Seems like you have not installed adb yet. What OS are you on?
EDIT: Duh, looked at the thread title. I may not be of much help, but did you update your path directory to look at the correct folders?
Michael.B. said:
Seems like you have not installed adb yet. What OS are you on?
EDIT: Duh, looked at the thread title. I may not be of much help, but did you update your path directory to look at the correct folders?
Click to expand...
Click to collapse
Yeah, I did the updates.
I'm gonna try again from scratch. Thanks for the help.
William, what happens when you plug your phone into the Mac, open Terminal, and copy/paste the following command (don't forget to change "Amin" to the name of YOUR home directory):
Code:
/Users/Amin/Desktop/androidsdk/platform-tools/adb devices
Typing just "adb devices" won't work because we never set the path to adb, but the above code should work (and give you a list of connected devices, which would be just your Nexus represented as a number) if you correctly did Steps 1-4 above.

[GUIDE] Root 2.3.3 On a Mac WITH OEM Unlock!

***
If you're looking for a guide on how to root on Windows, there is a fantastic guide here written by W0lv3r1n3!!
***
I know there is a stickied guide for this but it hasn't been updated since 2.3.1 so I decided to update it a little bit just to make things easier for people. Credit for this goes to Amin Sabet and DistortedLoop with a few changes/additions by me.
Warning: If you break your phone trying this, I am not responsible. I do not guarantee that the following is safe or that the steps are correct. Rooting your phone voids the warranty. I have no responsibility for anything that occurs as a result of your following these directions! I cannot provide any support nor guide you in undoing this process and restoring the phone to factory condition.
This process will wipe your phone. Ie, you will lose all your apps/data on your phone and have to reinstall them. It will also wipe your external storage, so back that up prior to proceeding if you want to keep anything.
1) Download this file (http://dl.dropbox.com/u/22368847/adb-fastboot.zip) and unzip it to your desktop (Inside you'll find all the files you need to proceed including "adb", "fastboot", "recovery-clockwork-3.0.0.5-crespo.img", and "su-2.3.6.1-ef-signed.zip").
2) On your phone, go to Menu>Settings>Applications. Select "Development" and check the box next to "USB debugging"
3) Connect the phone to your Mac via the USB cable
4) Open a Terminal window on your Mac (Applications>Utilities>Terminal), and copy/paste the following into the Terminal:
Code:
~/Desktop/adb-fastboot/adb reboot bootloader
Hit "Return" and wait for your phone to to reboot into Bootloader/Fastboot mode
5) If your Bootloader screen says "LOCK STATE - UNLOCKED" then skip to Step 6. If it says "LOCK STATE - LOCKED" then copy/paste the following into the Terminal:
Code:
~/Desktop/adb-fastboot/fastboot oem unlock
Hit "Return" and on your phone will prompt you to confirm and warn you that you are going to lose everything. Confirm. At this point you will have an unlocked bootloader.
6) Copy/paste the following into the Terminal window:
Code:
~/Desktop/adb-fastboot/fastboot flash recovery ~/Desktop/adb-fastboot/recovery-clockwork-3.0.0.5-crespo.img
Hit "Return" again and wait for recovery to boot.
For the following steps while in Recovery, use "Volume Down" to highlight a selection and "Power" to choose that selection:
8) Choose "mounts and storage"
9) Choose "mount USB storage". Your phone should now be mounted on the Mac as a Device called "NO NAME"
10) Move the zip file "su-2.3.6.1-ef-signed.zip" from the "adb-fastboot" folder to the "NO NAME" Device on you computer.
11) Eject/unmount your phone in the Finder on your Mac.
12) On your phone, choose "Unmount"
13) Choose "mount /system"
14) Choose "+++++Go Back+++++"
15) Choose "install zip from sdcard"
16) Choose "choose zip from sdcard"
17) Choose "su-2.3.6.1-ef-signed.zip"
Some people with new Nexus S' are finding that the file discussed in the following steps does not exist. If you cannot find it but can still reboot into Clock Work Recovery Mod then don't worry, you're still rooted and fine!
At this point you have root, but your phone will continue to replace ClockworkMod Recovery on reboot. To prevent this, do the following:
1) Reboot your phone, and download the app "Root Explorer" from the Market
2) Open Root Explorer and navigate to the "etc" directory.
3) Tap on the gray box that says "Mount R/W"
4) Tap and hold on the file "install-recovery.sh" and rename this file to "install-recovery.sh.old"
~~~~~~~~~~~~~~~~~~~~~​
Updated for ICS and included instructions in the zip!
5) Download the app "ROM Manager"
6) Open ROM Manager and choose "Flash ClockworkMod Recovery". At this point you are all set .
Mods any chance we can get this stickied to replace the old one? There seems to be some confusion about using the old version to root.
Nicely done.
any guides to root 2.3.3 for windows?
J__ said:
any guides to root 2.3.3 for windows?
Click to expand...
Click to collapse
Honestly, its a very similar process. Just download a different version of the SDK and make sure you put the recovery image in the folder of the installed SDK called tools. Then when you get to executing the commands do this:
Code:
cd *remove the asterisks and type the file path to the directory for the tools folder of your SDK folder in program files*
Then remove the
Code:
desktop/adb-fastboot/
and just type the other parts.
jlevy73 said:
Nicely done.
Click to expand...
Click to collapse
You think its enough of a difference to switch this with the other stickied thread on rooting for a mac jlevy?
im getting this error message "cannot load 'recovery-clockwork-3.0.0.5-crespo.img'"
so stuck on step 6. any advice?
thanks
Also, curious because now I have an unlocked bootloader but nothing else has been done. This shouldn't be an issue I assume.....
I've never heard of someone having that issue. Try the command fastboot flash recovery recovery-clockwork-3.0.0.5-crespo.img
Sent from my MattedBlues CM7 Google Nexus S!
kenvan19 said:
You think its enough of a difference to switch this with the other stickied thread on rooting for a mac jlevy?
Click to expand...
Click to collapse
I don't think it's enough but it would make a great add-on to the original rooting for mac thread.
-bash: fastboot: command not found
Is what it staid after trying that. Not sure what I am doing wrong. Have rooted several phones before.
owlmatt said:
-bash: fastboot: command not found
Is what it staid after trying that. Not sure what I am doing wrong. Have rooted several phones before.
Click to expand...
Click to collapse
Did you install the android SDK? I'm a little lost, I'm not sure what could be going wrong...I used this method to root both my and my wife's phones with no issues.
This could be the place I screwed up. I've never used the SDK on a mac and don't have a pc. I downloaded the files, used eclipse and loaded up everything it asked me to do.
I will look around for others guides on this maybe.
Maybe I need to learn more about android SDK, but I tried to follow all the instructions. One thing that was a problem was using the newest version of eclipse. It wouldn't install any add ons so I went to the older 3.4 version.
I would go to help, install new software, click on development tools, sign the terms then always get an error loading the software. This step does work on version 3.4. I guess I'm a real new noob at SDK.
owlmatt said:
This could be the place I screwed up. I've never used the SDK on a mac and don't have a pc. I downloaded the files, used eclipse and loaded up everything it asked me to do.
I will look around for others guides on this maybe.
Maybe I need to learn more about android SDK, but I tried to follow all the instructions. One thing that was a problem was using the newest version of eclipse. It wouldn't install any add ons so I went to the older 3.4 version.
I would go to help, install new software, click on development tools, sign the terms then always get an error loading the software. This step does work on version 3.4. I guess I'm a real new noob at SDK.
Click to expand...
Click to collapse
Oh no! I see where I screwed up in my guide...I'm sorry I see it clearly now...don't know how I missed it before.
instead of
Code:
~/Desktop/androidsdk/tools/fastboot boot recovery-clockwork-3.0.0.5-crespo.img
type
Code:
~/Desktop/adb-fastboot/fastboot boot recovery-clockwork-3.0.0.5-crespo.img
Still the same result for me. Sucks. I had moved the recovery image into the SDK to match you code, previously as I i've been trying everything I know.
owlmatt said:
Still the same result for me. Sucks. I had moved the recovery image into the SDK to match you code, previously as I i've been trying everything I know.
Click to expand...
Click to collapse
Okay I have one last idea...I'll grab the link then edit this with the stuff...brb
Download this SDK http://www.box.net/shared/ljhg8t5sjh it should have everything including an older version of CWM which should still work (again unzip it to your desktop) and try using this command:
Code:
~/Desktop/androidsdk/tools/fastboot flash recovery ~/Desktop/androidsdk/tools/recovery-clockwork-3.0.0.0-crespo.img
If it works you can flash the newest version of CWM through rom manager later.
I AM ROOTED!!! How do I buy you a beer?
owlmatt said:
I AM ROOTED!!! How do I buy you a beer?
Click to expand...
Click to collapse
Haha don't worry about it man! Just glad you're rooted now
Happy to if you change your mind. Just post your paypal. Otherwise Thanks again. I hit thanks on the site as well a bunch of times.
Time to start flashing and overclocking.
owlmatt said:
Happy to if you change your mind. Just post your paypal. Otherwise Thanks again. I hit thanks on the site as well a bunch of times.
Time to start flashing and overclocking.
Click to expand...
Click to collapse
If you really want to do something, I'd suggest buying the XDA Premium app from the market and help support XDA as a whole.
Consider it done.

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

Rooting Gingerbread 2.3.6 (4.5.141) - The Complete Guide

Having just purchased another Atrix that was running stock Gingerbread 2.3.6 (4.5.141), I was frustrated by the lack of a complete rooting guide and appropriate files. There is a guide in this forum (Link) which is based on an article from Android Advice (Link), but I noticed that both lack a lot of basic information for the inexperienced user. Also, the zip file available from Android Advice was missing a key file (Superuser!). So, I made a guide.
This may look complicated, but is super easy. If you don't feel comfortable using this method, you can use this automated tool (yes, it works on 4.5.141). It won't be as satisfying, or even feel good. You won't learn anything, but you will be rooted. Download tool here (link in OP is broken).
Pre-work:
1) Read the xda Atrix Beginners Guide (then read it again)! (Link)
2) Download and install 7zip. (Link)
3) If they are not already installed on your PC, download and install the Atrix drivers for Windows. (Link)
4) Download the attached files (sorry, had to break them in to two files due to forum size constraints). Create a new folder on your hard drive named "Android" (c:\Android). Extract both attached zip files to this folder (all the files need to be in "Android", not in a sub folder).
5) On your phone go to Settings, Applications, Development, then tick USB Debugging.
Notes:
Do not type quotes.
After each command hit enter.
Be mindful of spaces.
You can simply copy each command and paste in to the command prompt.
If you encounter any errors after entering a command, just ignore and keep going (assuming you entered the command properly).
Work:
1) Attach your phone to the PC via USB. In the USB settings make sure USB Mass Storage is selected.
2) Reboot phone while holding volume down until you see "fastboot".
3) Press volume up to initiate fastboot.
4) On your PC click the Start menu, then in the search box type "cmd"
5) In the command prompt type "cd c:/android"
6) "fastboot.exe flash preinstall preinstall.img"
7) "fastboot.exe reboot"
8) Wait for phone to reboot.
9) "adb shell"
10) "/preinstall/dosu". If you get an error (I did), type "/preinstall/su"
11) "/bin/mount -o remount,rw /system"
12) cp /preinstall/su /system/bin/"
13) "chmod 6755 /system/bin/su"
14) "PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk"
15) Reboot phone.
16) On your phone go to your apps and make sure the Superuser icon is there. Open the app, go to settings, then update the SU binary.
17) Open a terminal emulator, then type "su" and hit enter. You should see "#" if you are rooted. Or, download Root Checker from the Play Store.
My phone rebooted itself after step 11, so I had to re-open the adb shell.
I copied and pasted the text from the command prompt for reference (attached).
If I missed anything or have any errors, let me know and I will update the post.
Good luck!
Note: If you experience problems with updating superuser after rooting, try going in to Manage Applications and clear Superuser data. If that doesn't work go to the Play Store and Install Superuser Update Fixer.
Downloads:
My Atrix AFH Folder
*****
Thanksssss
Just want to show my appreciation. Your guide followed step by step worked flawlessly on my atrix. Ive been trying to root this darn thing for about a week and a half with no luck. found your guide and worked perfect first time around. Thanks..
David
Thanks for the information. Just wanted to do this, and while reading the procedure, I found that there is no Superuser.apk in the attachments. Do I have to get it from some other place.
Thanks
upndwn4par said:
Having just purchased another Atrix that was running stock Gingerbread 2.3.6 (4.5.141), I was frustrated by the lack of a complete rooting guide and appropriate files. There is a guide in this forum (Link) which is based on an article from Android Advice (Link), but I noticed that both lack a lot of basic information for the inexperienced user. Also, the zip file available from Android Advice was missing a key file (Superuser!). So, I made a guide.
Remember to click THANKS if this guide helped you!
Pre-work:
1) Read the xda Atrix Noob Guide (then read it again)! Link
2) Download and install 7zip. Link
3) If they are not already installed on your PC, download and install the Atrix drivers for Windows. Link.
4) Download the attached files (sorry, had to break them in to two files due to forum size constraints). Create a new folder on your hard drive named "Android" (c:\Android). Extract both attached zip files to this folder (all the files need to be in "Android", not in a sub folder).
5) On your phone go to Settings, Applications, Development, then tick USB Debugging.
Notes:
Do not type quotes.
After each command hit enter.
Be mindful of spaces.
Work:
1) Attach your phone to the PC via USB. In the USB settings make sure USB Mass Storage is selected.
2) Reboot phone while holding volume down.
3) Press volume up to initiate fastboot.
4) On your PC click the Start menu, then in the search box type "cmd"
5) In the command prompt type "cd c:/android"
6) "fastboot.exe flash preinstall preinstall.img"
7) "fastboot.exe reboot"
8) Wait for phone to reboot.
9) "adb shell"
10) "/preinstall/dosu". If you get an error (I did), type "/preinstall/su"
11) "/bin/mount -o remount,rw /system"
12) cp /preinstall/su /system/bin/"
13) "chmod 6755 /system/bin/su"
14) "PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk"
15) Reboot phone.
16) On your phone go to your apps and make sure the Superuser icon is there. Open the app, go to settings, then update the SU binary.
My phone rebooted itself after step 11, so I had to re-open the adb shell.
I copied and pasted the text from the command prompt for reference (attached).
If I missed anything or have any errors, let me know and I will update the post.
Good luck!
Click to expand...
Click to collapse
RE super user pkg.
aksma said:
Thanks for the information. Just wanted to do this, and while reading the procedure, I found that there is no Superuser.apk in the attachments. Do I have to get it from some other place.
Thanks
Click to expand...
Click to collapse
Well for me what happen is down at the bottom he has two links for two of the files you need to zip. in one of those, there is a superuser file. When doing the cmd commands at the end you will end up installing the superuser. The best thing to do which really helped me was to download the command prompt text file, that way you can mimic exactly what you see. Hope this helps.
-David
Thanks David, I just started doing the same. Lets see how it goes.
good luck
aksma said:
Thanks David, I just started doing the same. Lets see how it goes.
Click to expand...
Click to collapse
no problem. Believe me i was in the same position. I must of tried rooting mine like 15 times to no avail ,then i found this thread and it worked.
Worked like a Champ!! Thanks David... Was quick and easy.. ..
excellent
aksma said:
Worked like a Champ!! Thanks David... Was quick and easy.. ..
Click to expand...
Click to collapse
Good deal. So glad i found this thread haha.
Glad I could help!
good one.
Thanks a lot
was so expected that this guide
Going to give it a try
I read through everything and think I have somewhat of a clue on what I need to do..LOL. Whatever the results I will post back and let you know. I have had my atrix since it was first released and have never had the time to root it as I cannot be without a phone couldn't take a chance.
I retire soon so hopefully will have more time to get invovled in things as this is a great forum.
Mac
Thanks!
Rooted phone
dmacdog said:
I read through everything and think I have somewhat of a clue on what I need to do..LOL. Whatever the results I will post back and let you know. I have had my atrix since it was first released and have never had the time to root it as I cannot be without a phone couldn't take a chance.
I retire soon so hopefully will have more time to get invovled in things as this is a great forum.
Mac
Click to expand...
Click to collapse
Welcome to the wonderful world of messing with your phone!
You really can't harm your phone trying to root it. If you type a command wrong, just re-type it. No worries. There are lots of good guides out there for whatever you want to do. The noob guide (linked on the first page) is a great place to start. And there are plenty of members willing to help.
Let us know how things go!
thanks
that was cool!
very usefull!! thank you!
very useful
Sent from my MB860 using xda premium
condor7272 said:
that was cool!
Click to expand...
Click to collapse
Yes it is. Awesome feeling to look in your app drawer and see this:
THANKS!!
upndwn4par said:
Welcome to the wonderful world of messing with your phone!
You really can't harm your phone trying to root it. If you type a command wrong, just re-type it. No worries. There are lots of good guides out there for whatever you want to do. The noob guide (linked on the first page) is a great place to start. And there are plenty of members willing to help.
Let us know how things go!
Click to expand...
Click to collapse
followed the directions and am now rooted!!
next to look for boot load unlock - not sure why but 'im gonna figure it out - and then an ics rom or wait for the q3 'official' motorola release . . . decisions
1iJakk said:
followed the directions and am now rooted!!
next to look for boot load unlock - not sure why but 'im gonna figure it out - and then an ics rom or wait for the q3 'official' motorola release . . . decisions
Click to expand...
Click to collapse
Don't unlock your bootloader if you think you will want official Moto ICS update (major hard brick risk).

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