Database Info

[ANCIENT-TUTORIAL] IDIOT-PROOF Root Guide! NAND Unlock and ADB Update!!

This guide is ancient, guys. The only purpose it should serve now is showing you how to set up ADB or flash something through recovery. You can use unrEVOked Forever to root now, which is much faster and easier. Quit sending me PMs with questions about this.
After the positive response I got from my Swype guide, I decided to do one for root too. I have found that Toast's guide goes way over the head of a lot of new users (Using adb to copy and rename files? C'm on, Toast!), and I want to simplify things down for them.
In this guide, I will provide a way for you to backup your phone in case you have any vital programs, and I will take you all the way through getting back to the rooted stock image and restoring your apps (from there, you will be on your own!). This DOES work with Sprint's latest OTA (ends in .6).
Please let me know if there are any errors or any omissions (something like Titanium Backup not working with unrEVOked; I haven't tested this). Also, if someone wants to take some screenshots of the recovery stuff or just has images of the steps, just let me know, and I can add them.
If you get stuck on a step, please post it in the topic first instead of directly PMing me. It's not that I don't want to personally help you (you can ask all the people I've helped), but I'm not always directly available, and other users can freely help you out if you post in the thread! It also provides a little "mini-troubleshooting" scenario for anyone else with the same issue as you. I also recommend reading the entire guide before doing it so you will have some idea of what steps you will be taking! Thanks!
TABLE OF CONTENTS:
SECTION I: BACKING UP YOUR APPS
SECTION II: ROOTING FOR THE FIRST TIME
SECTION III: INSTALLING A CUSTOM RECOVERY
SECTION IV: INSTALLING A CUSTOM ROM
SECTION V: NESSECARY SOFTWARE INSTALLATION
SECTION VI: INTRODUCTION TO ADB
SECTION VII: UNLOCKING NAND
1. First things first, if you don't want to backup your apps, skip to step #14.
SECTION I: BACKING UP YOUR APPS
2. Go to the settings menu, and select Applications.
3. Check the box next to "Unknown Applications" and accept the warning.
{
"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"
}
4. Go to your web browser and navigate to http://unrevoked.com/m/ .
5. Click the logo to download the file, as it says.
6. Once the file is done downloading, click it.
7. Click the install button, and hit "open" when it is done installing.
8. Click Start!
9. When you get the "Done." message, navigate to the Market and find Titanium Backup. I HIGHLY recommend the donate version, but you need to donate to the dev via PayPal to get a license file, and it could take him up to a day to email it to you.
10. Click "open" after it is done installing and click the "Problems?" tab at the bottom.
11. Click "yes" to install BusyBox.
12. When Titanium Backup restarts, press Menu and select "Batch."
13. Backup all of your apps here.
SECTION II: ROOTING FOR THE FIRST TIME
14. Plug in your phone's USB cable and connect it to your computer. You should get a prompt in the notification bar that the phone is connected. Open the notification bar and select where it says "charge only."
15. Change the type to "disk drive" and select "Done."
16. Download this file, and save it to your desktop.
17. Since your phone is connected as a disk drive, navigate to My Computer and you will see it as "Removable Disk." Drag and drop the file you just downloaded to the icon.
18. At this point, we are about to flash the debug image. YOUR DATA WILL ALL BE WIPED AFTER THIS POINT!
19. Hold down "power" to bring up the following menu. Select "Power off."
20. Select "Ok."
21. Thanks to mrono, we now have some images of the recovery image for your ease of use, but I will post toast's exact words that you should follow to the letter. If you want step-by-step versions of this, skip to step 21a.
- Hold volume down while powering the phone on. continue to hold volume down until you see the WHITE bootloader screen.
- After a few seconds it will begin to checking for files, and find PC36IMG.zip. while its doing this it will show a blue progress bar while its checking. (this takes 30 - 60 seconds to finish)
- It will then list all the images in the zip and ask you if want to flash. SAY YES
- When its finished it will ask you if you would like to reboot. AGAIN... SAY YES
- At this point it will boot into a rooted rom.
Click to expand...
Click to collapse
Essentially, you just have to hold the volume down button as you press the power button, and the phone will do the rest. Just accept any prompts you get.
21a. When powering on, hold down the volume down key, and keep holding it down until this screen appears.
21b. It will search for a second then prompt you to install the PC36IMG.zip. Select yes.
21c. After the installation is complete, select yes to reboot your device.
22. You are now rooted! Congratulations! However, this debug ROM will not show protected apps in the Market, so we're going to install a rooted version of the stock ROM now.
23. After everything is booted, reconnect your USB cable and enter disk drive mode as described before.
24. Navigate to the PC36IMG.zip file and rename it however you want. This prevents it from running when ever you reboot. After this file is renamed, disable "disk mode" the same way you enabled it.
SECTION III: INSTALLING A CUSTOM RECOVERY
NOTE: Steps 25 - 28 were removed due to ROM Manager being updated. Follow the steps in step 29 below.
29. If ROM Manager just won't work for you, download this file, rename it to "update.zip," and copy it to the root of your SD card just like we did with the PC36IMG zip before. A common problem that people have here is actually typing the last ".zip" in when naming the file. ONLY type "update" as the file name because the file you are downloading is already in .zip format, and Windows hides known file extensions. If you get any kind of "file cannot be found" or "verification error" on this step, then you probably made this mistake, and you just need to rename the file.
Please note: This is the ONLY file on your SD card to be named "update.zip." Do NOT rename any other files to "update.zip" or remove this file.
SECTION IV: INSTALLING A CUSTOM ROM
30. At this time, we will download the rooted stock ROM. Get it here and save it to your desktop. Do NOT rename this downloaded ROM to "update.zip!"
31. Copy it to your SD card exactly like we did before with the first ROM. Make sure you re-enable disk mode so you can copy files again.
32. Once again, thanks to mrono we have photos of this step, but I will give you the exact words from Koush on how to boot into recovery. Skip to step 32a for exact step-by-step instructions in this step.
When you want to launch the recovery image
* Turn on your device with 'volume down' pressed and select 'Recovery'
* When the exclamation mark appears, press and hold 'volume up' then press 'power'
* Select the second option, 'Apply sdcard:update.zip
* That's it, ClockworkMod recovery should launch!
Click to expand...
Click to collapse
Just like before, we turn off the phone and hold the volume down key as we power on the device. However, this time we will select "Recovery" from the menu (move down with the volume button and select it with the power button). Now you will see a screen with an exclamation mark. Press and hold the volume up button and press the power button. Select the "apply update.zip" option, and you will be in recovery mode.
32a. Just as before, hold down the volume down key as you power on the phone until this screen appears. Select "Recovery" from the menu.
32b. When you enter recovery, you will see the following screen. Don't panic.
32c. Hold the volume up button and press the power button. You will now be presented with the following screen.
32d. From here, select "apply sdcard:update.zip." Remember, this is the recovery image from before. Your phone will boot into the ClockworkMod custom recovery.
33. First, wipe the cache partition and the user data by selecting their respective menu options. From here, select "install zip from sdcard." Now select "choose zip from sdcard" and navigate to the stock ROM .zip file that we downloaded. Skip to step 33a for step-by-step images, but the text below may help you navigate the recovery menu:
The full recovery menu will read as follows:
-reboot system now
-apply sdcard: update.zip
-wipe data/factory reset
-wipe cache partition
-install zip from sdcard
-nandroid
-partitions menu
-advanced
- *****Go Back*****
Click to expand...
Click to collapse
Select the bolded in the items in the order in which they appear. After all is wiped, select -install zip from sdcard then pick -choose zip from sdcard and finally navigate to the zipped ROM that you want to install.
33a. From the recovery menu, select the following options and confirm them: "wipe data/factory reset" followed by "wipe cache partition."
33b. After everything is wiped, navigate to "install zip from sdcard," then select "choose zip from sdcard."
33c. Now, navigate to the custom ROM that you downloaded and select it. You will get a progress bar.
34. After the ROM is done installing, press "**Go Back**" and then pick "reboot system now" from the menu.
35. Congratulations again! You are now running a rooted version of the stock ROM (or the custom ROM of your choice). You can restore your apps with Titanium Backup or you can get another custom ROM and flash it exactly the same way that you flashed the stock ROM. I highly recommend Fresh ROM, which can be found in this topic. In fact, ANY custom ROM can be flashed in the same manner that is described in steps 30-34.
35a. Make sure you flash the latest radio update before installing any custom ROMs! It flashes just like a ROM, and you can download it and find any warning information here. Don't dp this yet if you plan on continuing the guide and unlocking NAND because you will have to do it again at the end of the guide.
SECTION V: NESSECARY SOFTWARE INSTALLATION
36. We are going to download and install three pieces of software here: 7-Zip, HTC Sync, and the Android SDK. First, we will install 7-Zip. Navigate to the 7-Zip website (http://www.7-zip.org/download.html) and download the appropriate version for your copy of Windows (either 32 or 64 bit). Install it. In my opinion, this is the best archive utility, and it just makes life easier if we're on the same page.
37. Next, head to the HTC website (http://www.htc.com/us/support/evo-sprint/downloads/) and download the HTC Sync update for Windows. Install it. This should take care of your drivers for 32 or 64 bit.
38. Finally, head to the Android Developers (http://developer.android.com/sdk/index.html) website and select the Windows version of the Android SDK. Agree to the software agreement and save the file.
39. Take the zip file that you just downloaded and copy it to your C: drive as shown.
40. Once the file is copied, right click on it and select 7-Zip then "Extract Files Here." You should now see a folder called "android-sdk-windows" in the root of your C: drive. You've installed the Android SDK successfully.
SECTION VI: INTRODUCTION TO ADB
41. Accessing ADB is very easy. Click on the new android-sdk-windows folder, and you will see a bunch of different folders inside. We're going to be concerned with the "tools" folder, but don't open it!
42. Hold down the shift key and right click the tools folder. Select "Open Command Window Here" from the pop-up list. You have now opened an adb window, and any interaction with your phone will be done through this simple command line. You can copy lines directly from this tutorial and paste them into the command window by right clicking and selecting "Paste" (CTRL+V will not work in the command line).
43. If you want to manually navigate to the adb line (you don't need to do this unless you couldn't get step 42 to work), open a Command Prompt window (Run -> "cmd.exe" on XP/Vista, or just search "Command Prompt" in Windows 7). Now enter the following line of code: cd C:\android-sdk-windows\tools\ . This will take you to the tools folder where you must execute all adb commands.
44. Remember how to get to the adb command prompt. Any time I tell you to enter something via adb take the following steps: Connect your phone via USB, ensure USB Debugging is enabled (Menu -> Settings -> Applications -> Development, but this should be already enabled from the previous steps), and open the command window via either method described in steps 42 or 43. You can find a list of basic adb commands here or by typing "adb help" from the adb command line. You should always be able to directly copy and paste any code that I give you, however.
SECTION VII: UNLOCKING NAND
45. Download Toast's EVO Recovery files here. Save the .zip file anywhere you please. When it is done downloadi ng, right click it, and "Extract Files Here" using 7-Zip again. We are going to use a batch file in this folder to enter a custom recovery mode in a minute.
46. Download the new PC36IMG.zip debug ROM located here. When the menu pops up asking you to save the file, remove the "eng-" off the name so it only reads "PC36IMG". It is very important that you do this before you copy the file to your phone, either now or manually after you save it. NOTE: This is NOT the same image that we used in the first portion of the guide. You MUST download this version.
47. Next, download Toast's custom recovery image located here. Again, right click it and select "save target as." This time delete everything else off the front of the file name so it only reads "recovery".
48. The last two files that you will be downloading are mtd-eng.zip (located here) and flash_image.zip (located here). Once both of these files are downloaded them, right click and "Extract files here" with 7-Zip. You will now have the following files downloaded and extracted:
49. Copy the flash_image, mtd-eng.img, recovery.img, and PC36IMG.zip files to the root of your SD card just as shown below.
50. Now the fun part!! Open an adb window and enter the following code:
Code:
adb reboot recovery
Your phone will now reboot and show the yield sign with the red exclamation point. Don't touch it!
51. Navigate to that "evo-recovery" folder that you extracted earlier and right click on the "recovery-windows" batch file. Select "Run as Administrator" from the menu to execute the file. Another command window will pop up and spew out a bunch of lines. Don't touch it! Just look at your phone which is now in the Amon RA recovery image! If right-clicking doesn't work, try double-clicking to run it normally.
52. Special thanks to Riztnack for the wonderful screens in the follownig sections! Select "Backup and Restore" from the recovery menu. After that select the option to backup your current ROM. You have just performed a nandroid backup. Keep this in mind, becase we are going to restore this after the whole process is over.
53. Select "reboot" from the recovery menu and let your phone boot back up. Make sure you are connected to your computer via USB (you should not be in disk drive mode here or you will get an error), and go back to that same adb window we had open before and used to reboot our device (you can close the window that opened when you ran the batch file). Enter the following lines exactly as they are written, ONE LINE AT A TIME (I recommend copy and pasting):
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img
You will get an error message if anything goes wrong in the shell. When you enter the last three commands the window will just repeat them again to confirm that they were executed properly.
54. Now power off your phone just as before. Hold the volume down button as you press power to turn the device on. It will enter the bootloader just as before.
55. Select YES to flash the image, and after it is done flashing select YES to reboot. Don't worry if one of the "TP" options is bypassed. This is normal.
56. Once rebooted, go back to your adb command window and enter the following commands:
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img
reboot recovery
You will get the same confirmations when you enter the 2nd through 4th commands. After you enter the last one the phone SHOULD boot into the same recovery that we were in before. If your phone does NOT boot into recovery, take the following steps: Disconnect from USB, pull the battery, reboot the device, and enter the same adb commands as in step 53. After that, enter lines 2 throuh 5 from step 56. You should now be in recovery. Disclaimer: These were just the steps that I took after my phone did not boot into recovery the first time. They worked for me, so let me know if they work for you or not.
57. Your NAND is now unlocked!! Once your phone boots directly into recovery in step #56, take that as confirmation of success! While in recovery, wipe your user data (factory reset) and wipe the Dalvic cache.
58. Head to the Backup/Restore menu and restore that last nandroid backup that you just did. You can now reboot your phone, and it will be exactly the same as before.
58a. Make sure you flash the latest radio update before installing any custom ROMs! It flashes just like a ROM, and you can download it and find any warning information here. Even if you installed it before, you will have to flash it again because the debug ROM writes an older version.
59. Be sure to rename that PC36IMG.zip to something else like "NAND-PC36IMG.zip" just like you did before so that it doesn't try to boot it every time you enter the bootloader.
60. You can now enter recovery mode by entering the bootloader (holding volume down while powering on the device) and selecting recovery or by using the QuickBoot app (I highly recommend it). You can also use apps like AdFree or Root Explorer to freely edit your /system partition.
I really hoped this guide helped you guys, and I look forward to your feedback.
I'm not going to be asking for any donations because I'm not the one doing all of the work--the devs are the real contributers. I've just taken thier methods and spelled them out in an easy-to-follow way. Those guys work long hours contributing to the community so you should be donating to them.
That's all, folks! I hope you enjoy your root! Big thanks to all of the devs who have made this possible!
Here are some important links with relevant discussions:
Original root guide.
Fake-flash recovery guide.
Stock RUU topic with discussion.
Stock OTA topic with discussion.
How to fix QuickBoot and ROM Manager's rebooting functions on some ROMs.
ADB guide for when you're ready to take the next step.
Making ClockworkMod your permanent recovery.
Original NAND unlock guide.

that's beautiful for noobs

madunix said:
that's beautiful for noobs
Click to expand...
Click to collapse
Thank you!

So this is basically like mixed with Toast's root and unrevoked.

Very well done!
May I make a suggestion?
Maybe change step 24 to
24. Navigate to the PC36IMG.zip file and rename it however you want. This prevents it from running when ever you reboot.
Someone might actually look for debig .zip

will this guide work if i installed the OTA update (version ends in .6 instead of .1)
thanks

MrDSL said:
Very well done!
May I make a suggestion?
Maybe change step 24 to
24. Navigate to the PC36IMG.zip file and rename it however you want. This prevents it from running when ever you reboot.
Someone might actually look for debig .zip
Click to expand...
Click to collapse
Done. Thanks for the input.
jblazea50 said:
will this guide work if i installed the OTA update (version ends in .6 instead of .1)
thanks
Click to expand...
Click to collapse
Yes, I believe it will.

thanks, about to try it out

You might add in on step 26 that you need to switch back to 'charge only' mode for Rom Manager to work, otherwise you get a 'SD card not mounted' error. (at least I did )
Otherwise, great post!

How does one go from Clockwork recovery back to stock recovery?

I love how you have your Drives named.....especially the one for Pirated Stuff. I laughed.

strung said:
How do you go from Clockwork recovery back to stock?
Click to expand...
Click to collapse
You can't permanently flash clockwork yet, it's just temporary until you reboot then the stock recovery goes back. Unless there have been some major developments today.

logosmonkey said:
You might add in on step 26 that you need to switch back to 'charge only' mode for Rom Manager to work, otherwise you get a 'SD card not mounted' error. (at least I did )
Otherwise, great post!
Click to expand...
Click to collapse
Oh yes! Good post!
strung said:
How do you go from Clockwork recovery back to stock?
Click to expand...
Click to collapse
ClockworkMod recovery is actually just that file named update.zip in the root of your memory stick. We can't actually flash a real recovery image yet, so it is tricked into thinking we are flashing an update when we are really going into a recovery image.

worked like a charm; installed damagecontrol .v3 rom

jblazea50 said:
worked like a charm; installed damagecontrol .v3 rom
Click to expand...
Click to collapse
Happy to hear it! Did you do the unrEVOked bit, by chance? I actually never tested that out personally because I was already rooted when I wrote this.

Thanks so much for this. I'm new to android and didn't understand any of the terminology people were using. This is good.
I think my only suggestion would be to skip the initial rom manager install to download the recovery. I couldn't get rom manager to actually download the update.zip and it probably would have saved some time to just download the update.zip in the first place and do it manually. It kept saying it was successfully downloaded when it wasn't.

roybotnik said:
Thanks so much for this. I'm new to android and didn't understand any of the terminology people were using. This is good.
I think my only suggestion would be to skip the initial rom manager install to download the recovery. I couldn't get rom manager to actually download the update.zip and it probably would have saved some time to just download the update.zip in the first place and do it manually. It kept saying it was successfully downloaded when it wasn't.
Click to expand...
Click to collapse
Thanks for the input. Please let me know if anyone else is having problems with ROM manager on the debug ROM, and I will switch it around.

TheBiles said:
Happy to hear it! Did you do the unrEVOked bit, by chance? I actually never tested that out personally because I was already rooted when I wrote this.
Click to expand...
Click to collapse
i went from step 1 to 34, followed all of it; the only thing is i installed a different custom rom; had to install the recovery image as an update.zip
also, i don't think you mentioned in your guide to wipe data/factory reset prior to installing custom rom because when i did it the 1st time, got stuck in a boot loop; then i realized i had to wipe and it worked fine;
oh, also, after the boot loop, i had to do flash the recovery image as update.zip again because it wasn't there when i went back to recovery

I know this a noob question but will this work after the htc update?
I keep hearing mixed things!!!!
Thanks and OMG that was beautiful

jblazea50 said:
i went from step 1 to 34, followed all of it; the only thing is i installed a different custom rom; had to install the recovery image as an update.zip
also, i don't think you mentioned in your guide to wipe data/factory reset prior to installing custom rom because when i did it the 1st time, got stuck in a boot loop; then i realized i had to wipe and it worked fine;
oh, also, after the boot loop, i had to do flash the recovery image as update.zip again because it wasn't there when i went back to recovery
Click to expand...
Click to collapse
Yeah, I added in that data wipe bit not long ago because I forgot to. I wonder why the ROM Manager doesn't work in the debug ROM... I'll definitely just remove that later tonight.

[GUIDE] XOOM WIFI CUSTOM RECOVERY, ROOT AND CUSTOM KERNEL for NooB’s (Depreciated)

5/12/2011 : Thread marked depreciated due to the recent movement to get the 3.1 Honeycomb update installed. While parts of this tutorial may remain valid, the overall synopsis is not. For those of you that have used this guide I can vouch for the procedure in the thread linked below as a viable option to install the 3.1 update.
Thread to 3.1 Android Update
This tutorial was written for the NooB’s among us (like me) that are new to this stuff and are having a hard time “piecing together” all of the steps. While I am actually a not quite a beginner, NONE of these steps/methods/files have been developed by me. I have simply compiled the procedure in a document that I hope will be useful. With this in mind all the credit belongs to the many individuals that contribute in the XDA Developers forum. I have reviewed many posts by many people and have used all of the information along the way. I have intentionally chosen NOT to mention any specific names for fear that I will leave someone out. If you see anything herein that reminds you of something you posted then it probably is true and you are respectfully THANKED!!!
THIS TUTORIAL WAS CREATED AND TESTED ON THE US WIFI ZOOM. THE PC WAS RUNNING VISTA 32BIT
As a courtesy I will attempt to keep this post up to date with links to revised files. Bear in mind that I performed my upgrade using the original information/links and it was successful. I suggest that since this tutorial is for beginners that you follow the ORIGINAL links to complete the guide. Once you get that far you should have a better understanding of the procedures and be ready to "experiment" by flashing new kernals, recoveries, rom's, etc., using directions found in the corresponding section(s) of the development forum. After-all that is the real reason for most of this stuff anyway. As an example.... there is a 5/3 update below which adds links to newer versions of the Tiamat Kernel and Clockwork Mod. While you could probably just download and use the updated versions of these files in conjunction with this tutorial, I have NOT personally verified this to work. If anyone does try, or if the Dev's want to chime in, please post so that I can update accordingly. Thanks.
5/3/2011 --- UPDATE: Added Links to updated Tiamat Kernel (1.4.1) & Clockwork Mod (3.0.2.8) and added links to discussion threads.
5/11/2011 --- NOTICE: If you are wanting to upgrade to the recently released 3.1 Honeycomb Update than I suggest you re-consider following this guide. The upgrade procedure requires that the device be stock or the update will fail. Furthermore there has not been a Kernel Developed yet that works with 3.1 and some users were complaining about issues with ClockWork Recovery after applying 3.1. See the development section for more information
A) Installing ADB
ADB stands for Android Debug Bridge and simplistically stated will be used to send commands to your XOOM using the keyboard on your PC. In essence your PC will be acting like a terminal. ADB is included in a package known as the Android SDK. The following steps should be taken to insure a successful install of the SDK, therefore giving you access to ADB.1. Install Java JDK : http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u25-download-346242.htmla. Download appropriate Java SE Development Kit (JDK) from link above
b. Double click to Install JDK
c. Accept Setup Defaults​2. Install SDK Starter Package: http://developer.android.com/sdk/index.htmla. Download SDK Starter Package from link above. There are versions available for Microsoft Windows, Linux and Mac OS X. In case of Windows, both an installer and a zip file are available but there isn’t any need to use the installer as a formal installation is not required. Download the ZIP file.
b. Once you have downloaded the SDK, simply extract the compressed file to a location on your computer. In our case, we have extracted it to the root of our C drive and that makes [FONT=&quot]C:\android-sdk-windows[/FONT] the installation location of the SDK. From here onwards, we shall be referring to this location as the ‘SDK folder’.​3. Download the SDK Platform Tools using the SDK Mamager.a. Browse to the SDK folder and launch SDK Manager.
b. When launching it for the first time, it will present you with a window to choose packages to install. The first option begins with ‘Android SDK Platform-tools’. Make sure it is checked, and uncheck all the other packages for now. You can check/uncheck a package by simply double clicking on the package. Again, the only package you want to install is the Android SDK Platform-Tools.
c. Once the process is done, you will have a ‘platform-tools’ folder inside your SDK folder. That folder will include ADB and all its dependencies.
d. Make a copy of the File “fastboot.exe” which is in the “tools” directory and place it in the “platform-tools” directory.​B) Install XOOM USB Driver
Just to be sure your XOOM is recognized by your PC it is recommended that you install the latest USB drivers for your system.1. Install MotoHelper : http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Driversa. Download the Driver with MotoHelper from the Link above
b. Double Click downloaded file and follow on-screen instructions to install.​C) Unlock Bootloader
Unlocking the bootloader gives you full control over the device so you can flash new Recovery’s, kernels, ROM’s, ETC. THIS STEP WILL DELETE ALL DATA AND SETTINGS ON YOUR XOOM.1. Put XOOM in Debug modea. On the device, go to home screen, press [FONT=&quot]Apps[/FONT] > >Settings>>Applications>>[FONT=&quot]Development[/FONT], and enable [FONT=&quot]USB Debugging[/FONT].
b. Now connect your XOOM to the PC via USB. New hardware installation should begin and it will start looking for and installing the drivers.
c. A prompt should appear that states the drivers were installed successfully. On my PC the AutoPlay Device Options also appeared. I clicked “Open Device to View Files” and saw the device Storage with 27.8 GB free of 28.7 GB.​2. Execute ADB Commandsa. Open a command prompt by navigating to the ‘SDK Folder’, Holding the shift key, right clicking on the “platform-tools” folder and selecting “Open Command Window Here” from the popup menu.
b. In the new command window type: adb reboot bootloader and press enter.
c. Wait for the Dual Core screen with “Starting Fastboot protocol support” in the upper left corner to appear and then type: fastboot oem unlock in the command window and press enter. You should see: “To continue, follow instructions on the device’s display…”.
d. Read the WARNING on you XOOM and either Continue Below or Cancel following the on-screen instructions.
e. If you decided to continue then on the XOOM Push Volume Down Button to change the selection from “Cancel” to “I accept” and then press the Volume Up to select that choice.
f. You will be questioned again so Push Volume Down then Volume Up to confirm you want to UNLOCK your device. You will see “Device Unlock operation in progress…” “Formatting UDA”
g. When the operation completes the device will read”Device unlock operation done – rebooting…” and the device will reboot. The windows new hardware “gong” will sound a couple of times during this procedure. After this step when my XOOM rebooted I also saw an “MTP Device” driver Install dialog box on my PC. Unplug the device, and quickly perform the initial set-up. You can “Skip” any steps that will allow you to (like WiFi setup). Just get back to the home screen and continue below:
h. Verify that USB debugging is still enabled and if not re-enable it as outlined above.
i. Re-connect your XOOM to the PC and close any AutoPlay dialog.​D) Install Custom Recovery
A custom recovery allows you to flash files created by community developers such as ROM’s, Radios, Kernels, Themes, ETC. It also allows you to perform special tasks such as system backup’s, partitioning, cache wiping, ETC. As of 4/28/2011 the generally accepted custom recovery for the XOOM is ClockworkMod Recovery v3.0.2.5. Clockwork Discussion Threada. Download Clockwork Mod from here: ClockworkMod 3.0.2.5
3.0.2.8 ClockworkMod
b. Place the File “recovery.img” that you just downloaded in the “platform-tools” directory
c. In the previously open command window (if you closed it then re-open as described above) type: adb reboot bootloader and press enter.
d. The device will reboot into bootloader mode (as described above) and when this completes type: fastboot flash recovery recovery.img
e. Check the screen of your XOOM and see: “Flashing StorMgr partition recovery STATUS: - done!
f. Type: fastboot reboot in the command window and press enter.
g. Your XOOM should now boot with no noticeable changes.
h. In your command window type: adb reboot recovery
i. Your XOOM will reboot and an unfamiliar screen will appear. This is the “recovery” program and at this time you should simply verify that you see a reference to ClockworkMod Recovery in the upper left corner of the XOOM. This indicates that our efforts have been successful.
j. When my device rebooted into recovery I also saw additional Device Drivers install. This took a little while and I waited to do anything until I received the “Device Driver Installed Successfully” dialog.
k. Navigate in ClockworkMod Recovery by using the volume up/down to “move” and the power button to “select”. Look for reboot system, highlight it and hit the power button. Your zoom will reboot normally.
OPTIONAL STEPS
l. At some time later (AFTER YOU ARE ROOTED) to avoid the need to execute ADB commands to enter recovery, I suggest you look for a free application called “Quick Boot”, by Sirius Applications from the market.
m. Once Quick Boot is installed run it and simply select “Recovery” to boot into ClockworkMod. ​E) Install Custom (Tiamat)Kernel to your XOOM
The Tiamat Kernel we have chosen includes many advantages over the “stock” kernel most notably being support for the SD Card slot which as of this writing has still not been released by Moto. Tiamat Discussion Threada. Download the file “Tiamat_Xoom-v1.4.0.zip” from here: Tiamat Kernel 1.4.0
Tiamat Kernel 1.4.1 A big Thanks to Cam3era who acted as a gunia pig for this....Apparently you are better off flashing the 1.4.0 Kernal first and then flashing the 1.4.1. Details are in the Tiamat Thread
b. Make sure you have an SD Card in your XOOM. Some people are having issues with the system reporting the wrong size of the SD card and it has been suggested that you format your card in another android device prior to using it with your XOOM. Another “trick” was to use a small capacity card. Apparently this may still be a current issue so I recommend you format you card prior to use. I personally had a 1GB Micro SD that I formatted in my Android Phone.
c. Enter Recovery via adb by typing: adb reboot recovery in your terminal window and press enter.
d. Now, using the Volume Up and Volume Down buttons on the XOOM to move the prompt and the power button to execute a selection: i. Go to "mounts and storage"
ii. Select "mount USB storage"
iii. Your SD Card will now be mounted on your computer. Copy the Tiamat kernel zip you downloaded above onto the SD Card.
iv. "Go Back" TWICE then go into "install zip from sdcard" then "choose zip from sdcard"
v. Navigate to the zip file and select it.
vi. Navigate to “Yes – Install Tiamat_Xoom-v1.4.0.zip” and select it. It will now flash and you will see some scrolling text and a progress indicator.
vii. Wait until it says “Install from sdcard complete.
viii. Back out to main menu and reboot.​e. After the XOOM reboots (this could take a while) check to insure that USB debug mode is still enabled. If not, re-enable it as described above.​F) Root the XOOM and Install Superuser APK
Root access is similar to “administrator” privileges and gives you the power to run specially developed programs that take advantage of these additional rights. An example would be a program called titanium backup which coupled with the “super user” privileges can perform backup duties not available in “non-root” environments. The following file was obtained and discussed here: Link
a. Download the file Root_Xoom.zip from here: http://forum.xda-developers.com/attachment.php?attachmentid=579548&d=1303896724
b. Connect your XOOM to the PC (again be sure Debug mode is enabled) and close any AutoPlay dialog boxes that pop up.
c. In the same command window used previously type: adb reboot recovery
d. Now, using the Volume Up and Volume Down buttons on the XOOM to move the prompt and the power button to execute a selection: i. Go to "mounts and storage"
ii. Select "mount USB storage"
iii. Your SD Card will now be mounted on your computer. Copy the “Root_Xoom.zip” file you downloaded above onto the SD Card.
iv. Go Back" TWICE then go into "install zip from sdcard" then "choose zip from sdcard"
v. Navigate to the “Root_Xoom.zip” file and select it.
vi. Navigate to “Yes – Root_Xoom.zip” and select it. It will now flash and you will see some scrolling text and a progress indicator.
vii. Wait until it says “Install from sdcard complete.
viii. Back out to main menu and reboot.​e. After the XOOM re-boots check to see that you have a new App in the Drawer called “Superuser”.​G) CLEANUP
As you become more at ease with using Clockwork Recovery you will use it more and more. There are many more features than can be described here and after all, that is beyond the scope of this tutorial. I highly recommend that you seek out more information about this tool so you can put it to good use. One term you will see used a lot is “wiping”. Wiping does exactly that to a specific partition(s) and/or file(s) thereby insuring that a new installation is “clean” and no “remnants” of prior information exist. The upside to this “cleaning” is that there is less chance of corruption from using older (or incompatible) versions of files or data and the downside is that this “data” may contain useful information such as high scores, completed game levels or even previously remembered passwords. You should learn how to back-up this data using Titanium Backup or another backup application and manually reload it after your upgrade is considered “stable”. This allows you to wipe and thereby insure that any “issues” you experience are not related to “remnants”. So, with this all said, I recommend that you now Wipe your User Data and Cache. Again, if you have not backed up, this will erase and reset things that you may not want erased or reset. Proceed with caution!!!!
a. Enter Recovery via quickboot or adb as described above.
b. Using the Volume and Power Buttons as described above navigate to “wipe data/factory reset” and select it.
c. Navigate to “Yes – delete all user data” and select it. Wait until it says “Data wipe complete”.
d. Navigate to “wipe cache partition” and select it.
e. Navigate to “Yes – Wipe Cache” and select it. Wait until it says “Cache wipe complete”.
f. Navigate to “reboot system now” and select it.
g. Set up your rooted, custom recovery, custom Kernel XOOM!! ​ENJOY

I really appreciate your post. This should be sticky
P/s: you can make this instruction even better if you include some pics that can illustrate the process, some frequently errors and solutions to fix those errors.

Thanks for the kind words!
One step at a time my friend. This was my first attempt at creating a tutorial and I tried to handle the "pictures" with very detailed wording. Embedding screenies into future efforts is on my to do list.
The bottom line regarding this is..... I created the tutorial before I even took my XOOM out of the box and then followed it to see if it worked. While I had some minor issues with the original draft, I believe they have all been taken care of in this final.
I expect that if any issues are encountered, it will involve the SD Card size which seemed to be a common issue for some. I had NO problems with mine.
And, while I'm at it....... I was a little hesitant to include the information on "quick boot". Some members (and I'm taking this off the top of my head right now) had issues using clockwork when it wasn't initiated using the adb reboot recovery command. I seem to recall that there was a difference in this regard between the WiFi and 3G versions. In any case if Clockwork does not seem to be working for you then stick with starting up recovery using adb and NOT Quick Boot. Having Quick Boot available in your app drawer is recommended however in case you ever experience issues mounting the device to your PC.
tritran18518 said:
I really appreciate your post. This should be sticky
P/s: you can make this instruction even better if you include some pics that can illustrate the process, some frequently errors and solutions to fix those errors.
Click to expand...
Click to collapse

Thanks
This is exceptionally well done. A tremendous resource. I hope you will keep it up to date. I will refer to it often. Thank you!

I hope this works.....With this it is time to root. Thank you for a great step by step instructions.

This is an excellent tutorial! Thank you. I may take the plunge now. One request : would you be so kind as to add the steps to return to stock and relock the wifi version?
Sent from my Xoom using Tapatalk

See this tread: Stock Image
I have NOT done this procedure but will follow that thread to see how it turns out.
Someone DID apparently re-lock the device but I don't know if that procedure removes all indications that the device was un-locked in the first place.
cam30era said:
This is an excellent tutorial! Thank you. I may take the plunge now. One request : would you be so kind as to add the steps to return to stock and relock the wifi version?
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse

Didn't really want to bump my own thread but I was hoping someone would have tried this by now. Anybody?
I didn't put this "guide" in the development section because I didn't actually develop anything. Perhaps I should have?

This is an awesome step by step instruction! Good Work! Thanks a lot!

Land Master said:
Didn't really want to bump my own thread but I was hoping someone would have tried this by now. Anybody?
Click to expand...
Click to collapse
Ran through it yesterday on my father in law's new Xoom, worked great!!!
I was holding out for HTC flyer with pen, or Transformer with keyboard...
But, was impressed and may be going with Xoom now myself.
Thanks so much for the guide, it worked very well and he's happily tethered to adhoc wifi on his droid now, so very thankful as well.
Sent from my SCH-I500 using XDA App

Awesome tutorial! Now I have a place to point new users to when they hijack my thread

bigrushdog said:
Awesome tutorial! Now I have a place to point new users to when they hijack my thread
Click to expand...
Click to collapse
Thanks BRD for everything you do. I added links to the 5/1 files but also a disclaimer. Your thoughts on this would be appreciated.

Feedback
Land Master, I just used your tutorial to root my wifi Xoom. It is very well written and easy to understand and follow. I installed the Tiamat 1.4.1 kernel. Worked fine. Have confirmed that I have Superuser permissions. And "about" shows the Tiamat 1.4.1 kernel.
First a suggestion: Under "Install Custom Kernel" your instruction states "c. Enter Recovery via “Quick Boot” application or thru adb". I tried to use Quick Boot but could not (obviously) because I was not rooted yet. Had to use ADB, which worked fine. You may want to modify the instructions here to remove the Quick Boot option at this point?
Second, I have a request for help. I purchased a Sandisk 16gb micro SD card. Formatted it in my rooted Droid Incredible. Placed it in my Xoom and rebooted. I can not find my external SD Card with Root Explorer. Any suggestions?

cam30era said:
Land Master, I just used your tutorial to root my wifi Xoom. It is very well written and easy to understand and follow. I installed the Tiamat 1.4.1 kernel. Worked fine. Have confirmed that I have Superuser permissions. And "about" shows the Tiamat 1.4.1 kernel.
First a suggestion: Under "Install Custom Kernel" your instruction states "c. Enter Recovery via “Quick Boot” application or thru adb". I tried to use Quick Boot but could not (obviously) because I was not rooted yet. Had to use ADB, which worked fine. You may want to modify the instructions here to remove the Quick Boot option at this point? Corrected This THANKS!
Second, I have a request for help. I purchased a Sandisk 16gb micro SD card. Formatted it in my rooted Droid Incredible. Placed it in my Xoom and rebooted. I can not find my external SD Card with Root Explorer. Any suggestions?
Click to expand...
Click to collapse
Cam30era.....Thanks for your help. Honestly I haven't played with the SD Card in mine but do know that I have an "external" directory that is viewable in Root Explorer under "sdcard". With this said you should check the Tiamat thread because I believe the SD card "stuff" was removed in 1.4.1 because it was sketchy. I personally am still on 1.4.0.
I don't really want to take people away from the "official" (Tiamat) thread because they will all need to "learn" the same way most of us have.... by trial and error. It is my belief that this is what makes all of this fun and worthwhile. With that said however, it is my belief that a "Stable" SD Card fix will not become available until after the official Moto update drops.
My goal here was to get people to a "starting point" thus allowing them to get their feet wet and subsequently give them the tools (Root, Recovery, ETC) to continue the journey into flashing different stuff. This is why I wrote the disclaimer above.... Hoping that people would just stick to what is "known good" and march onward by researching other threads and learning as they go.

Land Master said:
Cam30era.....Thanks for your help. Honestly I haven't played with the SD Card in mine but do know that I have an "external" directory that is viewable in Root Explorer under "sdcard". With this said you should check the Tiamat thread because I believe the SD card "stuff" was removed in 1.4.1 because it was sketchy. I personally am still on 1.4.0.
I don't really want to take people away from the "official" (Tiamat) thread because they will all need to "learn" the same way most of us have.... by trial and error. It is my belief that this is what makes all of this fun and worthwhile. With that said however, it is my belief that a "Stable" SD Card fix will not become available until after the official Moto update drops.
My goal here was to get people to a "starting point" thus allowing them to get their feet wet and subsequently give them the tools (Root, Recovery, ETC) to continue the journey into flashing different stuff. This is why I wrote the disclaimer above.... Hoping that people would just stick to what is "known good" and march onward by researching other threads and learning as they go.
Click to expand...
Click to collapse
I'll try flashing 1.4.0 and then back to 1.4.1 and let you know. Thanks for the suggestions.

OK. I just tried to flash 1.4.0 from CWM. Got following error message:
E:Error in /sdcard/tiamat_xoom-v1.4.0.zip
(status 0)
Installation aborted.
I'm getting help now on the Tiamat thread. I'll keep you posted on how this gets resolved.

Land Master, FYI: I successfully flashed 1.4.0. This did create a fully functional external folder inside sdcard. I then flashed 1.4.1 and it's a go. So you may want to modify your tutorial to indicate that you must flash 1.4.0 first.
A big "thank you" for this excellent tutorial, and for your help. I probably would not have rooted my Xoom without this outstanding aid.

cam30era said:
Land Master, FYI: I successfully flashed 1.4.0. This did create a fully functional external folder inside sdcard. I then flashed 1.4.1 and it's a go. So you may want to modify your tutorial to indicate that you must flash 1.4.0 first.
A big "thank you" for this excellent tutorial, and for your help. I probably would not have rooted my Xoom without this outstanding aid.
Click to expand...
Click to collapse
Very glad you got it sorted. I added your suggestion to the OP.

mbowe said:
It worked very well and he's happily tethered to adhoc wifi on his droid now.
Click to expand...
Click to collapse
Ad-hoc? A stock xoom doesn't support this but a rooted one can now? Didn't realize that had been enabled.

hi,
can i install the kernel and the custom recovery without root ?
i thought i need to have root first....

N00b tutorial: Flashing EOS3 to MZ604 Xoom (Wifi)

Hi all.
A few days ago I entered the Xoom forum asking about how to modify an "unaltered" Spanish/European Xoom (Wifi Only, MZ604) running stock Android Honeycomb (3.2) and flash a custom ROM with Android 4.1.1 (JellyBean), so that I don't have to wait Motorola to release the updates (still in Honeycomb in Europe, while in US they're enjoying JB), and to enjoy the extras that custom ROMs offer (root, overclocking, etc).
Xda users "wesamothman" and "Cubanluke88" answered quickly to my question and this allowed me to unlock my Xoom bootloader, install TWRP Recovery and flash EOS3 ROM (JellyBean for Xoom from TEAM EOS). The results are awesome; the change from Honeycomb to Jellybean, plus the totally stable overclocking at 1.2 and even 1.4 Ghz is worth the fact that you void the Xoom warranty by doing this procedure. It's like having a brand new tablet.
As I found some problems/mistakes in the procedure I was given, I've created a new "Guide for Noobs" (based on wesamothman's) so that anybody can reproduce the same steps and convert an European Xoom (Wifi Model, MZ604) into a modern EOS3-powered Xoom.
NOTE: I initially wrote this tutorial using the EOS-RECOVERY-6.IMG as the CWM Recovery software to install in the Recovery Partition. The recommended recovery software now is TWRP so I've updated the tutorial replacing the download links and filename.img to flash. The procedure remains the same, although I really tested and executed it with eos-recovery-6, not with TWRP. Anyway, it is supposed to be flashed and work the same way than I initially described it.
NOTE THAT THIS PROCEDURE IS FOR EOS3 - (EOS NIGHTLY <= v155).
EOS4 (nightly >= v156) requires a slightly different procedure!!!
Please, remember that by unlocking the bootloader (and flashing non official software) you're voiding the device warranty and that I'm not responsible of any damage that your device can suffer. I'm just explaining how I did the unlocking+flashing to convert my SLOW XOOM in a fully working JellyBean system. Remember also that this procedure is for WIFI ONLY Xooms. 3g xooms need a different rom/procedure.
So, sumarizing, that's what we are going to do:
a.- Unlock the "bootloader" of the Motorola Xoom so that we can "install" custom software in both the "recovery" and the "data" partitions. Please notice that by unlocking the bootloader you void the device warranty.
b.- Flash TWRP software into the recovery partition, (I was flashing EOS-Recovery-v6 software initially but now is deprecated and TWRP must be used) so that we can launch this software pressing a combination of keys during power-on. This software will allow us to make full backup/restore of the device memory, and to install any ROM (EOS2, EOS3, cyanogenmod, EDGE, etc) in the system. Thanks to this recovery we are safe against problems in the O.S. (even if we break it), because we can always recover from backup or flash a new ROM (including the "stock" ROM, I mean, the ROM shipped oficially with the device) and solve the situation.
c.- Once recovery is installed, do a NANDROID backup of the NAND of our device, to have a copy of the "stock" system.
d.- From Recovery, flash the desired ROM (EOS3 in my case) and the Google Apps applications (they can't be included inside the ROM for legal reasons, so they are flashed separately) to the "data" particion.
e.- Restart and enjoy our new system (you can also made another NANDROID backup to save this "working point" for the future).
Steps a). and b). need a working computer with Linux, Windows or Mac. After doing b).- you can do everything from the Xoom itself and you don't need the computer anymore. After doing b)., you'll be able to download ROM images directly under your Xoom in the uSD card and reflash any new ROM directly rebooting the tablet into recovery-mode.
Steps a) and b) can be done from Linux, Windows and Mac. Although I have Linux in my laptop, I found that almost all the tutorials in Internet explain the procedure under Windows so I installed temporary a Windows system to do the "PC dependant" steps, because I didn't want to experiment with the "risky" actions in both steps.
So, let's start with the "PC dependant" actions, which includes steps a). and b).
I'll try to update the thread with screenshots in the future, as I didn't take photos/screenshots of the procedure, I'll check images.google.com to find something that fits the text, and add the later to the tutorial if they are really needed.
PART 1 .- HOW TO INSTALL TWRP RECOVERY:
Here we are going to unlock our Xoom and install a custom recovery software into the recovery partition. The recovery software is launched when you start your Xoom in recovery mode, and this is achieved by pushing Power, VolUP and VolDown key combinations when you power-on the tablet (we'll see how later).
So we'll replace the original "recovery" software by a custom one that allows us to flash NON OFFICIAL software to the data partition.
To do that, first we have to download all the required software in the Xoom enternal uSD card and prepare our PC system to recognize and work with the Xoom. We have to download:
Get the Motorola USB drivers for your system: http://developer.motorola.com/docstools/USB_Drivers/ . This step is only needed under Windows, so that the Windows System recognizes the Xoom and the Android SDK binaries (adb and fastboot) can send data to the tablet. Check that you're downloading the right drivers (32 or 64 bits) for your 32 or 64 bits System, and install them. If the Android SDK in your Linux system can recognize the Xoom, you're ready to use Linux also to do the following steps.
Download and Install in your PC the lastest JavaSE JDK from Oracle's website: http://www.oracle.com/technetwork/java/javase/downloads/index.html.
Download and install the Android SDK for your system: http://developer.android.com/sdk/index.html .
Download the EOS v155 ROM and GoogleAPPS for that version. My final choose was EOS3 ROM Wingray (Jellybean for Xoom), and installed v155 from the nightly compilations (which is the latest nightly in Android 4.1, being v156+ Android 4.2). "Nightly" means that as the software is still not "final version" (it's still in development) a new version is released almost everyday, correcting bugs or adding new features. I personally didn't found any bug in v155 but you can check the EOS3 thread in XDA to check that the latest version has no bugs reported by people in that thread.
ROM: http://goo.im/devs/teameos/roms/eos3/nightlies/wingray/ (as of date September-2012 - I recommend v141 )
GAPPS: Latest: http://teameos.org/gapps/wingray (I used http://goo.im/devs/teameos/roms/eos3/gapps/gapps-jb-20120802-eos-signed.zip for v155).
EOS3 THREAD: http://forum.xda-developers.com/showthread.php?t=1764751
And the most important, download TWRP the "recovery software" that will allow you to work without the need of the PC (I was using Team Eos Recovery 6 initially, but now is deprecated and TWRP must be used):
Team Win Recovery Project 2.x, (TWRP): http://forum.xda-developers.com/showthread.php?t=1782235
You should download the IMG file (example: R.A.H.v3_TWRPv2.5.0.img). Check that the size of the downloaded file matches the size that is shown in the above link. This is the most important file because it will allow to install the recovery system and it's CRITICAL that the file is not corrupted..
Steps:
a.- Install in your PC the Android SDK, open Windows' cmd, enter the android-sdk folder and run:
Code:
tools\android.bat update sdk
Now select "Android SDK Tools", "Android SDK platform-tools", and Extras/"Google USB Driver". Click on "Install packages".
This will download and install the packages needed so that we can access the Xoom from the PC for "flashing" data purposes; mainly "adb" and "fastboot". Adb allows us to work with the xoom started in the Android System, and fastboot allows us to work with the xoom started in fastboot mode, which is the mode we'll use to "flash" the recovery software.
b.- Enable USB debugging in the XOOM (in settings, development), so that we can use adb with the tablet.
c.- Install the Motorola USB drivers for your laptop (32 or 64 bits, check it in the Windows system properties).
d.- Plug the Xoom to your PC.
e.- Execute cmd and enter the android-sdk/platform-tools folder.
Run "adb devices". You should see that the system identifies your Xoom with a long numbers+letters string. If you get an empty "List of devices attached", then you must enter the control-panel -> devices and "Fix problem with device" over the MZ60x device, so that the system can bind the right USB drivers we installed to that concrete device.
After a While, Windows will fix it and re-executing "adb devices" will show a message like:
Code:
List of devices attached
037887sda897xz device
(the digits string will vary according to your device)
Now, with your xoom working under the Android OS, do:
Code:
adb reboot bootloader
With the above, you'll enter fastboot mode without needing to press any key in the startup. Fastboot mode is a special bootmode in the xoom that allows the PC to send data to the Xoom and "write" to Recovery and Data partitions. You can also enter that mode starting the Xoom with "Power+Volume Up" pressed simultaneously.
Now your Xoom will show the Motorola logo and the words "Fastboot protocol...". If you need to stop now for any reason, you can abandon this mode safely and reboot the tablet with "Power+VolUP+VolDown" for a few seconds.
{
"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"
}
(Photo: fastboot mode, taken from google images)
But let's continue.... If you now do:
Code:
fastboot devices
You should get a string like
Code:
List of devices attached
037887sda897xz fastboot
If you don't see that string (and you see and error about device not found), you have to "fix/repair" the usb drivers again in the Windows ControlPanel / Devices. Now you'll see a "FASTBOOT" device instead of the MZ60x you repaired before (that's why we have to repair/fix again the device, because Windows see it as a different device while in fastboot mode).
After repairing it, unplug and plug the USB cable (still in fastboot mode) and repeat the command:
Code:
fastboot devices
Now it will work and you'll see the device recognized by "fastboot".
Issue the following command to unlock the Xoom (you'll void the warranty). If you don't unlock the xoom, data and recovery partitions will be "read only" and you can't send the "new software" to them.
Code:
fastboot oem unlock
Follow the Xoom's onscreen instructions to unlock the bootloader. You have to use VolDown to move through options and VolUP to accept an option. The device will ask you twice if you are sure that you want to unlock the device and void the warranty, and then it will make a "factory reset" of the O.S. .
The xoom will reboot and your old android OS will show, but now with a factory reset. Select language, time, etc. Enable again "USB debugging" and execute in the PC:
Code:
adb reboot bootloader
(to start again the tablet in fastboot mode)
Now copy the recovery file (the name may vary, with something like R.A.H.v3_TWRPv2.5.0.img) to the android-sdk/platform-tools/ folder with name "recovery.img" and execute:
Code:
fastboot flash recovery recovery.img
You will see something like:
Code:
C:\Users\sromero\Desktop\android-sdk-windows\platform-tools>
fastboot flash recovery recovery.img
sending 'recovery' (XXXXX KB)...
OKAY [ 0.499s]
writing 'recovery'...
OKAY [ 1.014s]
finished. total time: 1.529s
Check in the xoom's screen that the file was correctly written and execute:
Code:
fastboot reboot
Now disconnect the USB cable and enter recovery mode with:
- When the Motorola logo appears, tap Volume Down (not press, tap) repeteadly until "Android Recovery" is displayed in the screen.
- In this moment, pressing Volume Up will send you to Recovery Mode.
- If you press by mistake again Volume Down, you'll enter DRS mode. You can leave it with VolUP+VolDown+Power and try again (Xoom is powered off).
And you'll start the TWRP Recovery recovery system. If you see the standard Android recovery system instead of TWRP recovery, you can repeat the above "fastboot flash recovery recovery.img". You don't have to unlock the bootloader again, just flash the recovery software and reboot again in recovery mode with "fastboot reboot" and "adb reboot recovery".
(Photo: my Xoom in EOS6 recovery mode, TWRP is different, with better controls and more features )
You can start recovery mode also manually by powering on the Xoom and when the motorola logo appears, wait 3 seconds and press VolUp.
Now, you have your device unlocked and recovery installed. Now, you are SAFE because you can do nandroid backups and restores and can put any ROM in your system and go back with a backup or flash another different rom.
PART 2 .- HOW TO USE TWRP RECOVERY
How to enter in recovery mode:
A.- Manually:
- Turn Xoom off.
- Press Power to turn Xoom on.
- When the Motorola logo appears, tap Volume Down (not press, tap) repeteadly until "Android Recovery" is displayed in the screen.
- In this moment, pressing Volume Up will send you to Recovery Mode.
- If you press by mistake again Volume Down, you'll enter DRS mode. You can leave it with VolUP+VolDown+Power and try again (Xoom is powered off).
b.- From "adb" in a PC system with Android running on the tablet connected to that PC:
Executing "adb reboot recovery"
c.- With a custom ROM, selecting "reboot" will ask you if you want a normal reboot or a recovery-reboot.
How to use recovery mode:
Use the Volume Up and Volume Down keys to move between options and Power button to select an Option:
Code:
Up -> VolumeUp button
Down -> VolumeDown button
Select -> POWER button
Available options for a basic CWM / recovery are:
Reboot system now -> exit Recovery mode.
install zip from sdcard -> allows to install ZIPs to data partitions such as ROMs.
wipe data/factory reset -> delete all the contents in the data partition (needed before flashing a ROM)
wipe cache partition -> delete cache partition.
backup and restore -> allows doing "nandroid" backups and restore of our system (FULL MEMORY BACKUPS).
mounts and storage -> allows to mount aditional media to save/read data.
advanced -> extra options.
(Photo: Nandroid backup)
NOTE: TWRP is newer than the OLD EOS-recovery-6, the above capture and options may differ.
PART 3 .- HOW TO INSTALL EOS3 ROM:
Now we've installed recovery, so we don't need the PC anymore. We can enter in recovery mode at any moment and do backup/restores, flash new roms, flash updates, etc.
To install EOS3 ROM (or any other "full install" -not update- ROM, do):
Start the Xoom in recovery mode.
Backup/restore -> backup the current system to our external SD.
Wipe data/factory reset -> remove partition contents
Wipe cache -> delete the cache
Advanced -> Wipe Dalvik Cache
Advanced -> Wipe Battery Stats
Install ZIP from SDCARD -> /sources/ -> the eos3 rom .zip file.
Install ZIP from SDCARD -> /sources/ -> the gapps .zip file.
Reboot
Install gmail, youtube, etc from Market (not included anymore in gapps).
Enjoy your new rom!
PART 4 .- HOW TO UPDATE EOS3 ROM or install a new different ROM:
Start the Xoom in recovery mode.
Backup/restore -> backup the current system to our external SD.
Wipe data/factory reset -> remove partition contents
Wipe cache -> delete the cache
Advanced -> Wipe Dalvik Cache
Advanced -> Wipe Battery Stats
Install ZIP from SDCARD -> /sources/ -> the new rom .zip file.
Install ZIP from SDCARD -> /sources/ -> the gapps .zip file.
Reboot
Enjoy your new rom!
I hope this can help people to unlock their xooms.
Thanks to "wesamothman" and "Cubanluke88" for the initial support given and specially to EOS Team and the people that created ClockWorkMod for sharing their time, work and knowledge with us. They've converted my "slow xoom" in a very powerfull and fully functional tablet.

Couldn't expect less from you. Super great guide...
Sent from my MZ601 using Tapatalk 2

Post reserved for updates in case the initial post gets too large...

I wish all new Android users would do the level of research the OP did prior to making his initial question thread. We guided you a bit but if I remember right, your first post showed quite well that you had done your homework. If more people committed themselves to understanding what they're doing prior to doing it, I'd imagine there'd be a lot less "bricks" in the android world. Great work dude and nice job entering the forums with a bang.
Sent from my Xoom using Tapatalk 2

Thanks for your words...
In this thread I've tried not only to give a procedure (the forums and lots of websites are full of procedures) but also explain the concepts themselves (oem unlock, adb, fastboot, recovery mode, gapps, etc).
"Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime".
Thanks.
--
Sent from my Xoom with EOS3 ROM using Tapatalk 2

Updated with some pictures

Updated with links to v141...

eos 6 recovery.img not available
the recovery image file is not available in the link..could you update the link. Thank You !
Great tutorial

kakrikakri said:
the recovery image file is not available in the link..could you update the link. Thank You !
Great tutorial
Click to expand...
Click to collapse
Hi.
According to this URL, EOS6 RECOVERY.IMG has been deprecated:
http://forum.xda-developers.com/showthread.php?t=1604014
Now you can use Team Win Recovery Project 2.2, (TWRP):
http://forum.xda-developers.com/showthread.php?t=1782235
Flashing is almost similar to EOS6 recovery method described above, just check the last link.

NoP_Compiler said:
Hi.
According to this URL, EOS6 RECOVERY.IMG has been deprecated:
http://forum.xda-developers.com/showthread.php?t=1604014
Now you can use Team Win Recovery Project 2.2, (TWRP):
http://forum.xda-developers.com/showthread.php?t=1782235
Flashing is almost similar to EOS6 recovery method described above, just check the last link.
Click to expand...
Click to collapse
wow that was a quick reply.. THANKS (Y)

kakrikakri said:
wow that was a quick reply.. THANKS (Y)
Click to expand...
Click to collapse
Anyway, I have the eos-recovery-r6.img.zip file in my desktop, I can send you via email if you want to use it instead of TWRP (but you should not, as Team Eos recommends their new recovery system).
I'm going myself to update to TWRP this evening (they have a .zip file that you can flash from an existing recovery like my current "EOS6 recovery").

Same method for stock ics?
Sorry I am a bit paranoid..but will this same unlocking bootloader and flashing recovery method work for stock ics on my xoom?
Thanks !

Help !!! In a lot of trouble
I flashed the twrp recovery and then it rebooted..everything was perfect till that point
then i rebooted into recovery..and when i selected to install zip from usb drive..it said mount to sdcard failed (at this point the roms were downloaded in my internal storage) and it does not detect any zip files.
I tried putting the zip files on a proper micro sdcard and then rebooted into recovery..but still no luck.. it just says it failed to mount sdcard.
Special note:- and btw.. when i reboot into recovery and after pressing the vol up button there is a droid icon on my screen, but no 'recovery' menu shows up.. then i pressed volup+power button, this action popped up the list of menus of the recovery screen... (do u think this might be a problem?)
please help me i am panicking here..is there anyway i can flash a different recovery..like the eos recovery or the cmw?
HELP !!!!

kakrikakri said:
I flashed the twrp recovery and then it rebooted..everything was perfect till that point
then i rebooted into recovery..and when i selected to install zip from usb drive..it said mount to sdcard failed (at this point the roms were downloaded in my internal storage) and it does not detect any zip files.
I tried putting the zip files on a proper micro sdcard and then rebooted into recovery..but still no luck.. it just says it failed to mount sdcard.
Special note:- and btw.. when i reboot into recovery and after pressing the vol up button there is a droid icon on my screen, but no 'recovery' menu shows up.. then i pressed volup+power button, this action popped up the list of menus of the recovery screen... (do u think this might be a problem?)
please help me i am panicking here..is there anyway i can flash a different recovery..like the eos recovery or the cmw?
HELP !!!!
Click to expand...
Click to collapse
Twrp recovery doesnt mount external sdcard by default, you need to mount it first thru recovery. Just go to mounts and check the box to mount external sdcard

wesamothman said:
Twrp recovery doesnt mount external sdcard by default, you need to mount it first thru recovery. Just go to mounts and check the box to mount external sdcard
Click to expand...
Click to collapse
I am sorry i panicked.. I think its working fine now..i flashed a wrong recovery it seems.
May i ask ! if we are installing the eos 3 rom for the first time, does it take very long to boot the very first time?
because i my xoom is booting up after installing, and the eos logo is on display for more than 10-15 mins.. is it supposed to take this long?

kakrikakri said:
I am sorry i panicked.. I think its working fine now..i flashed a wrong recovery it seems.
May i ask ! if we are installing the eos 3 rom for the first time, does it take very long to boot the very first time?
because i my xoom is booting up after installing, and the eos logo is on display for more than 10-15 mins.. is it supposed to take this long?
Click to expand...
Click to collapse
First time ROM flashing is longer than normal booting, like 5 min ,
If you got stuck in boot loop, reboot into recovery using the power and sound keys combination and clear cache and dalvik and reboot again

kakrikakri said:
I am sorry i panicked.. I think its working fine now..i flashed a wrong recovery it seems.
May i ask ! if we are installing the eos 3 rom for the first time, does it take very long to boot the very first time?
because i my xoom is booting up after installing, and the eos logo is on display for more than 10-15 mins.. is it supposed to take this long?
Click to expand...
Click to collapse
Did you finally succeded "booting" EOS3?

NoP_Compiler said:
Did you finally succeded "booting" EOS3?
Click to expand...
Click to collapse
Yes it did and it works perfectly
Thank you NoP_Compiler and wesamothman
Sent from my Xoom using xda app-developers app

Just to say thanks for 1 of the best tutorials I have ever found,from stock ICS to eos 3 wingray nightly 151 in less than 20 mins. Only prob I had was android SDK wouldn't find x64 java on win had to install 32bit version on top but only hiccup

dead android in step 2
Hi,
Thanks for the great tutorial.
I got thru Step 1, using the image "openrecovery-twrp-2.3.1.0-wingray.img"
In Step 2, when I enter in recovery mode, I get a screen with a "dead droid" image.
Any idea about what I might be missing?
thanks!

[Q] Re: THE ULTIMATE NEWB GUIDE. I'm too noob for to noob guide, help.

. I don't even want a custom ROM. I just want to be rooted and run stock with rooted google play store apps. Am I there?
I just want to run rooted apps with no ROM flashing...oh god why...where is the guide to root and only root?
You'd think this http://forum.xda-developers.com/show....php?t=1652398 would be where to go to do that, but evidently it's sending me down the road to custom ROM flashing. AGHGHGhjkdashbdas. Do not want.
Ok, so here's where I am, I have finished step 8:
1. Download Odin 1.85 .
2. Download(USE FIREFOX!) ClockworkMod TOUCH 5.5.0.4 OR TWRP 2.2.2.0, they are both named "recovery.tar.md5" and will be downloaded as "recovery.tar.md5", DO NOT CHANGE the filename or else it wont install.
3. Extract the contents of odin-185.zip to a folder.
4. Run Odin 1.85.exe from the folder you extracted it to.
5. Prepare Odin: Check "auto-reboot" and UNCHECK ALL OTHER OPTIONS. SEE COMPUTER SREEN PICS BELOW.
6. Only Click "PDA" and select the recovery.tar.md5 file you downloaded. SEE COMPUTER SREEN PICS BELOW.
7. How To Put your device into Download Mode: DO NOT TOUCH THE POWER BUTTON FOR THIS PROCEDURE. - download mode is NOT the same as recovery mode
a. Connect the USB cable to your PC, but NOT to your phone.
b. Remove the battery.
c. Reinsert the battery.
d. ATT PHONES - Press and keep down both Volume Up and Volume Down keys simultaneously.
ROGERS PHONES - Press and keep down only the Volume Down key.
DO NOT RELEASE THE VOLUME KEY(S) UNTIL INSTRUCTED TO DO SO IN STEP (f)
e. Insert the USB cable into your device. The phone will turn itself on when usb cable is inserted - DO NOT TOUCH THE POWER BUTTON.
f. You will now see a screen w/a yellow triangle warning you about installing a rom . Now release the volume key(s) - SEE PHONE PICS BELOW
g. Press and release the "Volume Up" key to enter into download mode - SEE PHONE PICS BELOW
h. You should now be at the Download Mode screen w/odin recognizing your phone. SEE COMPUTER SREEN PICS BELOW.
8. Click Start in Odin. It will flash the new recovery and will reboot the phone when completed. Your device will autoreboot into android. You are done using ODIN.
9. UPDATING CWM OR TWRP:
Now you need to udate CWM, download and copy cwm6027touch_v14.4.6_skyrocket.zip file to your sdcard, boot into recovery and choose "INSTALL FROM SDCARD" from recovery, install the file and reboot back into recovery to see if it installed correctly.
sk8erwitskil's CWM thread is here HERE , check to see if above file is the latest or dl the "Flashable zip" CWM file from there.
If upgrading TWRP go here HERE and follow the dev's instructions on using goo app, or you can use the flashable TWRP 2.4.1.0 file HERE and copy that file to your sdcard, boot into recovery and pick "INSTALL" from recovery, install the file and reboot back into recovery to see if it installed correctly.
How to enter recovery read section #2 below.
How to use cwm read THIS, also read Q&A on recoveries
You can upgrade to either CWM OR TWRP from which ever recovery TAR file you used in ODIN in step #2 from above.
10. You're done newbie and soon to be a power user, read and educate yourself as much as you can before flashing, happy flashing.
Click to expand...
Click to collapse
I don't know how to do step 9. Do I even need it? I have no desire to run a custom ROM.

yargdpirate said:
OK so here's the list of instructions I'm using to root my Skyrocket:
I have completed everything through step 4. I completely do not understand what to do after that. So, like I'm a 40 year old soccer mom, can you explain what I'm supposed to do to fulfill step 5? Is it through the odin app on my pc? Is this completed on my phone? The link provided that ostensibly explains to noobs how to do this (http://forum.xda-developers.com/showthread.php?t=1777970) doesn't adequately explain to me what I'm doing and where.
Help, please!
Click to expand...
Click to collapse
Assuming that you have successfully installed your custom recovery you then need to know which recovery you installed before you update it. If you used CWM you can get the updated version from the Skyrocket development thread. Put the updated CWM file on your SD card and flash that zip while in recovery. If you used TWRP you can update it through the app that it installed if it did install one. GooManager (someone correct me if I am wrong on the name) I think GooManager needs suoeruser privileges. So which recovery did you flash?

CodeNameRedNeck said:
Assuming that you have successfully installed your custom recovery you then need to know which recovery you installed before you update it. If you used CWM you can get the updated version from the Skyrocket development thread. Put the updated CWM file on your SD card and flash that zip while in recovery. If you used TWRP you can update it through the app that it installed if it did install one. GooManager (someone correct me if I am wrong on the name) I think GooManager needs suoeruser privileges. So which recovery did you flash?
Click to expand...
Click to collapse
Put the updated CWM file on your SD card and flash that zip while in recovery?
Click to expand...
Click to collapse
It's CWM. How do I
A. Put the updated CWM file on my SD card and
B. Flash that zip while in recovery? Is that through Odin, or what?
Thanks

yargdpirate said:
It's CWM. How do I
A. Put the updated CWM file on my SD card and
B. Flash that zip while in recovery? Is that through Odin, or what?
Thanks
Click to expand...
Click to collapse
i think you should stay on stock, read more b4 you brick your phone, no sense in rooting/installing custom roms when you dont know how to install a file on your scard, im not putting you down but trying to give you friendly advice

Vincom has a point. I taught myself through these forums and Google how to do it back in October of 2011. I flashed many a ROM and many files since then until I bricked mine Thursday. Now I have to pay 60 dollars to get it fixed. But on the upside I now have a Note II to play with.
Edit: She is asking for help though and she did ask in the right thread. Some people need more help than others.

vincom said:
i think you should stay on stock, read more b4 you brick your phone, no sense in rooting/installing custom roms when you dont know how to install a file on your scard, im not putting you down but trying to give you friendly advice
Click to expand...
Click to collapse
Oh. ****. I don't even want a custom ROM. I just want to be rooted and run stock with rooted google play store apps. Am I there?
I just want to run rooted apps with no ROM flashing...oh god why...where is the guide to root and only root?
You'd think this http://forum.xda-developers.com/showthread.php?t=1652398 would be where to go to do that, but evidently it's sending me down the road to custom ROM flashing. AGHGHGhjkdashbdas. Do not want.
Ok, so here's where I am, I have finished step 8:
1. Download Odin 1.85 .
2. Download(USE FIREFOX!) ClockworkMod TOUCH 5.5.0.4 OR TWRP 2.2.2.0, they are both named "recovery.tar.md5" and will be downloaded as "recovery.tar.md5", DO NOT CHANGE the filename or else it wont install.
3. Extract the contents of odin-185.zip to a folder.
4. Run Odin 1.85.exe from the folder you extracted it to.
5. Prepare Odin: Check "auto-reboot" and UNCHECK ALL OTHER OPTIONS. SEE COMPUTER SREEN PICS BELOW.
6. Only Click "PDA" and select the recovery.tar.md5 file you downloaded. SEE COMPUTER SREEN PICS BELOW.
7. How To Put your device into Download Mode: DO NOT TOUCH THE POWER BUTTON FOR THIS PROCEDURE. - download mode is NOT the same as recovery mode
a. Connect the USB cable to your PC, but NOT to your phone.
b. Remove the battery.
c. Reinsert the battery.
d. ATT PHONES - Press and keep down both Volume Up and Volume Down keys simultaneously.
ROGERS PHONES - Press and keep down only the Volume Down key.
DO NOT RELEASE THE VOLUME KEY(S) UNTIL INSTRUCTED TO DO SO IN STEP (f)
e. Insert the USB cable into your device. The phone will turn itself on when usb cable is inserted - DO NOT TOUCH THE POWER BUTTON.
f. You will now see a screen w/a yellow triangle warning you about installing a rom . Now release the volume key(s) - SEE PHONE PICS BELOW
g. Press and release the "Volume Up" key to enter into download mode - SEE PHONE PICS BELOW
h. You should now be at the Download Mode screen w/odin recognizing your phone. SEE COMPUTER SREEN PICS BELOW.
8. Click Start in Odin. It will flash the new recovery and will reboot the phone when completed. Your device will autoreboot into android. You are done using ODIN.
9. UPDATING CWM OR TWRP:
Now you need to udate CWM, download and copy cwm6027touch_v14.4.6_skyrocket.zip file to your sdcard, boot into recovery and choose "INSTALL FROM SDCARD" from recovery, install the file and reboot back into recovery to see if it installed correctly.
sk8erwitskil's CWM thread is here HERE , check to see if above file is the latest or dl the "Flashable zip" CWM file from there.
If upgrading TWRP go here HERE and follow the dev's instructions on using goo app, or you can use the flashable TWRP 2.4.1.0 file HERE and copy that file to your sdcard, boot into recovery and pick "INSTALL" from recovery, install the file and reboot back into recovery to see if it installed correctly.
How to enter recovery read section #2 below.
How to use cwm read THIS, also read Q&A on recoveries
You can upgrade to either CWM OR TWRP from which ever recovery TAR file you used in ODIN in step #2 from above.
10. You're done newbie and soon to be a power user, read and educate yourself as much as you can before flashing, happy flashing.
Click to expand...
Click to collapse
I don't know how to do step 9. Do I even need it? I have no desire to run a custom ROM.

For just rooting u have to run the superuser zip through your recovery
Oh and if you are not understanding what the stickies are saying to do then look it up on youtube because there are a lot of step by step instructions there.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

a. put updated file in your micro sd card.... plug ur micro sd card to pc... drag file and drop it in your micro sd card. put the micro sd card back in phone.
b. to go to recovery press power button + vol+ + vol- all at once and hold.
why do u need to unlock play store app? playstore is accessible completely even without root. you can also sideload Amazon appstore and other apps without root. no need to get all bricked up just to run playstore. i'm confused what are you trying to do again?

droidbabyxda said:
a. put updated file in your micro sd card.... plug ur micro sd card to pc... drag file and drop it in your micro sd card. put the micro sd card back in phone.
b. to go to recovery press power button + vol+ + vol- all at once and hold.
why do u need to unlock play store app? playstore is accessible completely even without root. you can also sideload Amazon appstore and other apps without root. no need to get all bricked up just to run playstore. i'm confused what are you trying to do again?
Click to expand...
Click to collapse
im guessing he wants to run apps from play that require root, eg titanuim backup, but he doesnt know how to put a file on his sdcard, but then he has to learn how to install zips from recovery which someones got to teach him since he doesnt want to read/learn/search for the answers. he seems to be impatient and wants it done "now", its a brick waiting to happen, my advice to him was to slowdown and learn

vincom said:
im guessing he wants to run apps from play that require root, eg titanuim backup, but he doesnt know how to put a file on his sdcard, but then he has to learn how to install zips from recovery which someones got to teach him since he doesnt want to read/learn/search for the answers. he seems to be impatient and wants it done "now", its a brick waiting to happen, my advice to him was to slowdown and learn
Click to expand...
Click to collapse
agree and such bad attituted too. i wouldn't want to help anybody who cusses in every conversation geez little respect goes a long way

It you just want to root and not want to flash any custom ROMs or anything related to it,I will tell you how to from total beginning
ALL DATA WILL BE LOST , BACKUP EVERYTHING
In order to root Android 4.2 the following three requirements must be satisfied beforehand:
The Android SDK, which you can download from Google Developers
A custom recovery like ClockworkMod (CWM) or Team Win Recovery Project (TWRP)
SuperSU, which you can download from CF-Root
There are no major differences between the two, but TWRP is more touch-oriented thanks to larger buttons. CWM is also available in a touch-compatible variant, but it has much smaller buttons. It's a matter of personal preference between the two though, but you have to choose one.
Before starting the process I urge you to perform a backup, as all data might be lost afterwards. You can copy the contents of the SD card to a safe external location such as cloud storage service or computer hard drive.
The first step that needs to be performed after all the files are downloaded is to install the Android SDK. Afterwards open the Android SDK Manager and select the following two items:
Android SDK Platform-tools -- it contains the required programs to install Android 4.2 Jelly Bean
Google USB Driver -- it contains the necessary drivers for the Nexus device
Then you should create a folder in an easily accessible location within the command line. In this example I will use a folder named "Root" in my C:\ drive in Windows. The path name will therefore be: "C:\Root".
From the folder where Android SDK Platform-tools is installed (in my case it is "C:\Program Files x86)\Android\android-sdk\platform-tools" copy the following files to the previously created "Root" folder:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
The following files must also be copied to the "Root" folder:
CWM-SuperSU-v0.97.zip -- SuperSU file
The custom recovery that you previously downloaded for your specific device (please see below)
For my 8 GB nexus 7 wifi(codename "grouper" I will use TWRP with the name "openrecovery-twrp-2.3.1.0-grouper.img".
You can easily find the codename for your devoice by looking into Google
The custom recovery file differs for each device, please make sure you download the correct file
In order to make the process smoother for instance the SuperSU file can be renamed to "root.zip" and the custom recovery to "customrecovery.zip". It's a matter of convenience, but for accuracy I will stick to the original naming for this guide.
If the previous steps are completed you must have the following six files in your "Root" folder:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
CWM-SuperSU-v0.97.zip -- SuperSU file
The custom recovery. In my case it is "openrecovery-twrp-2.3.1.0-grouper.img"
From there, you can proceed to install the drivers for "fastboot mode". To install them, follow these steps:
Power off your Nexus device.
Press and hold Volume Up and Volume Down then press and hold the Power button; the device will now enter "fastboot mode".
Go to Device Manager (Computer -> Properties -> Device Manager in Windows 7/8) and identify the device; for me it shows up as Android 1.0.
Right click Android 1.0 and select "Update Driver Software," then select "Browse my computer for driver software".
Select "Let me pick from a list of device drivers on my computer," then click "Next".
From "Have Disk..." option go to the folder where you have Google USB Driver installed (for me it's "C:\Program Files .(x86)\Android\android-sdk\extras\google\usb_driver" and select "android_winusb.inf".
Out of the three options select "Android ADB Interface" and validate any future warning window to install the driver.
Final preparations
Everything is prepared in order to start the installation process, but in order to do so a command window must be opened. Windows Key + R opens "Run"; type in "cmd" and the command window appears. Typing "cd C:\Root" and pressing Enter sets the "Root" folder as the working directory. Pressing the Shift key and right clicking inside the "Root" folder will also deliver the same result.
The device must be turned on in "fastboot mode" which I have explained at step no.2 during the driver installation process, and obviously plugged-in to the computer. You then have to type in the following commands while in "fastboot mode":
fastboot devices -- this is just for verification purposes; if there is no listed device then the drivers have been improperly installed and steps 1 through 7 must be redone.
fastboot oem unlock -> you have to accept the prompt in order to continue -- this command will unlock the bootloader, but it will also erase the data on the device which is why a backup is necessary.
fastboot reboot-bootloader -- this will reboot the bootloader.
fastboot flash recovery openrecovery-twrp-2.3.1.0-grouper.img -- this will flash the custom recovery --please use the specific file and name for your particular Nexus device!
fastboot erase cache -- this will erase the cache -- might not be necessary but it's just as a precaution.
fastboot reboot -- this will reboot the device.
After Android 4.2 is loaded and running the SuperSU file must be copied from the "Root" folder to the internal storage (shows up in Windows Explorer as a Nexus device). A simple copy and paste will do the trick here.
Then you have to power off the Nexus device and enter "fastboot mode" again. Use the Volume Up and Volume Down keys to navigate until you can select "Recovery Mode". After the power button is pressed the device will reboot in the new custom recovery.
Rooting your Nexus device
If you have ClockworkMod installed, you have to perform the following steps:
Select "install zip from sdcard"
Select "choose zip from sdcard"
Select "0" (zero) folder
Select "CWM-SuperSU-v0.97.zip"
Select "Yes - Install CWM-SuperSU-v0.97.zip"
Select "Go Back"
Select "reboot system now"
If you have Team Win Recovery Project installed, you have to perform the following steps:
Press "Install".\
Select "CWM-SuperSU-v0.97.zip" -- for me it's in the "0" (zero) folder
Swipe to confirm flash
Press "Wipe cache/dalvik" (just as a precaution)
Swipe to wipe
Press "Reboot System"
After Android 4.2 loads your device can run apps with elevated privileges (meaning it's rooted). A SuperSU app is installed in order to allow root requests, so please use your judgement on which apps you grant access.
If you experiences any problem, please reply and I will look into it.
Sent from my Nexus 7 using xda app-developers app
Sent from my Nexus 7 using xda app-developers app

^^you want him todo that, lmao, he doesnt even know how to put a file on his sdcard to flash it in recovery, theres no way a computer newb is going to be able to follow what you posted

That's why I have not used the word flash anywhere, I know that he does not know how to flash , I have posted the right thing for a total noob,( at least if he knows how to use command in windows or install drivers)
I helped him in the way I could and what he requested
Sent from my Nexus 7 using xda app-developers app

You think that helped. LOL. Your telling him to do things that aren't even required to gain root with this device. Not everything is a nexus bro. Next time you wanna help study up on the phone your giving advice about. lol

Well , thanks for telling me that every android isn't rooted in same manner, I was thinking that all devices are rooted in same ways like for my nexus
Sent from my Nexus 7 using xda app-developers app

naman14, im not putting you down, your step by step howto is admirable, good work, but the problem is that the op is clueless on tech stuff, its not the word "flash" he has a problem with, i could of said "install" and it would lead to same conclusion, he doesnt know how to copy a file to his sdcard, if he cant do that he has no business in modding his phone until he learns more. anyhow the op is long gone by now

I upgraded my samsung skyrocket s2 version 2.3.6 to 4.0.4 through the Kies. Then I tried to install TWRP 2.2.0 and Odin 1.85. I saw COM 14 ; COM 17 when I hit start button .It said
FAILED. Now it showed a yellow triangle in the middle of phone & monitor pictures. ( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again). Please help . Thank you very much.
I just tried other laptop . I saw COM 3 but it said it couldn't open the serial (COM )port . All thread completed (success 0/ failed 1)

[GUIDE] Unlock/Root/Flash for Moto X Style/Pure

[SIZE=+3]Heisenberg's How-To Guide For Beginners[/SIZE]
{
"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"
}
[SIZE=+2]Moto X Pure[/SIZE]​
[SIZE=+1]Intro[/SIZE]
This thread will serve as a location for basic how-to guides for the Moto X Pure. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
[size=+1]Prerequisites[/size]:
You'll need a working adb/fastboot environment on your PC to get through some of these guides. Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C:\ called SDK (C:\SDK). Once you've downloaded the zip you can extract it into your C:\SDK folder. Navigate to C:\SDK\android-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Library
Once you have installed those, inside C:\SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You'll find Motorla drivers here, download it and install, then reboot your PC.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
[SIZE=+1]Index[/SIZE]
How To Unlock Your Bootloader
How To Install A Custom Recovery On Your Device
How To Make A Nandroid Backup With TWRP Recovery
How To Root Your Stock Rom
How To Install A ROM with TWRP Recovery
How To Install A Custom Kernel With TWRP Recovery
How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System
[SIZE=+1]1. How To Unlock Your Bootloader[/SIZE]
Go into About Phone in Settings, click on Build Number 7 or 8 times until it says you have enabled Developer Options. Go back to Settings and enter the newly opened Developer Options section, scroll and click on the Enable OEM Unlock option.
Power off your phone then boot into fastboot mode (power + volume down).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.​
Once you've confirmed your fastboot connection issue this command:
Code:
fastboot oem get_unlock_data
It should return something like this:
Code:
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
Copy that code (with no spaces between the characters) and paste it somewhere for safekeeping, you'll use it in a minute.
Go to the Motorola bootloader unlocking page. You'll need to create an account with Motorola if you don't already have one. Once you're signed in you can scroll down to step 6 and paste the above code into the text field and hit the “can my device be unlocked” button.
Read the terms and conditions and accept them if you agree (you can't continue unless you accept).
Click the “request unlock key” button and an email with your unlock token will be sent to the email account that you signed up with.
Once you have retrieved the token from the email you can use it within the following command to unlock your bootloader:
Code:
fastboot oem unlock xxxxxxxxxx
(Replace the xxxxxxxx with your unique unlock token)​
Your bootloader is now unlocked!
Reboot with this command:
Code:
fastboot reboot
It's now safe to disconnect your usb cable.
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
[SIZE=+1]2. How To Install A Custom Recovery On Your Device[/SIZE]
Prerequisites: unlocked bootloader.
Download the recovery of your choice, here's TWRP.
Make sure you check the md5 to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Put the phone in fastboot mode and connect it to your PC via usb cable.
Open a command prompt from within your fastboot folder (shift + right click, select open command prompt here), and enter the following commands:
Code:
fastboot flash recovery <filename>.img
(Replace <filename> with the actual filename of the recovery, the recovery filename in the command will change depending on which recovery you're flashing)
Wait for the recovery to flash, it'll only take a few seconds, you'll get a finished message in your command prompt window once it's done.
It's now safe to disconnect your usb cable.
Don't reboot the phone normally, use the volume buttons to highlight recovery and press the power button to select it. This will stop the stock OS from patching it with the stock recovery in boot. Once you've booted into TWRP like this once, you can reboot normally.
[SIZE=+1]3. How To Make A Nandroid Backup With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
A nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
All you need to do is enter TWRP recovery, select the backup option from the TWRP home screen, check the system/data/boot boxes, and swipe to backup. The process will take a few minutes.
[SIZE=+1]4. How To Root Your Stock Rom[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
Please note: this method is only valid for Lollipop, do not use this method on Marshmallow. You can find a systemless root method for Marshmallow here, big thanks to @ivcarlos!
Download SuperSU to your phone.
Boot into TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to where you have SuperSU stored on your sd card and select it.
Swipe to install.
Once you've installed SuperSU you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button. That's it.
[SIZE=+1]5. How To Install A ROM with TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
Installing a ROM is a pretty straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above).
Download a ROM and appropriate Gapps package and place on your device.
Boot into your custom recovery.
Perform a full wipe.
Select the wipe option from the TWRP home screen.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your sd card and select it.
Swipe to install.
Most ROMs will run an installer script at this point but some ROMs have what is called an Aroma Installer which allow you to choose some install options before the script runs.​
You will also need to install the appropriate gapps package directly after installing the ROM.
Once you've installed all necessary zips you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
[SIZE=+1]6. How To Install A Custom Kernel With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
A custom kernel can open up a new level of control over your device, such as overclocking/underclocking, undervolting, changing governors, changing I/O schedulers, adjusting colour calibrations, adjusting sound calibrations, and many other options.
Download a kernel that is compatible with your current ROM.
Check the md5 to verify its integrity.
Enter TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to the kernel and select it.
Swipe to install.
You'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
Once your phone has booted up you can use a kernel tuning app to change governors, I/O scheduler, clock speed, and other options. Some of the popular kernel apps are Kernel Auditor, Trickster Mod, No Frills, Kernel Tuner, and many more.
[SIZE=+1]7. How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
There may come a time when you accidentally wipe your OS while trying to perform a basic cache wipe in recovery. Don't laugh, it can happen to the best of us. The best way to insure yourself against being stuck in recovery is to keep a ROM zip or a TWRP/CWM backup (a nandroid backup) on your sd card at all times.
This solution seems like common sense but apparently there are quite a few people out there who don't store a ROM or backup on their phone. You might think it's easy to just mount the OTG storage and copy a ROM across to your phone from your PC (which is definitely an option), but there's always a chance that you won't be near your HDD or sd card at the time, or it won't recognise your phone properly. Basically you need to insure yourself against Murphy's law.
Donate To Me

This will be very helpful to many thanks for taking the time to put this together!
Sent from my XT1575 using Tapatalk

Thank you so much for taking the time on the guide. There will be many who will use it in the years to come! I'm just about at the verge of needing to root so I can get some insight into my battery life woes

This is much appreciated. All I did on my LG G2 was root as I did not see any roms that interested me since the bootloader is locked. I haven't used TWRP in a couple of years, so all this will help me clear the old cobwebs in my head.

Thank you so much for this! Exactly the kind of information I need. Can I trouble you to maybe add one more section to your guide: What to do when there's an OTA update from the manufacturer (Motorola)? I have concerns like:
- Would being rooted prevent OTA updates? (Assuming stock ROM).
- Would I need to "unroot" the phone to get the update? If so, how to unroot the the phone?
- Is the process to root the phone again after the the update the same, or could it possibly change?
- Would I need to wait until root is confirmed for the new version before attempting to re-root?

You said to "Make sure you check the md5 to verify its integrity".
What does this mean and how would I do this?

Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery

elitemeat said:
You said to "Make sure you check the md5 to verify its integrity".
What does this mean and how would I do this?
Click to expand...
Click to collapse
You can download an MD5 checker. They give you the MD5 checksum and you can compare when you run the utility. Just do a google search for md5 checker.

Oops

emailrob said:
Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery
Click to expand...
Click to collapse
Thanks for your suggestions.
1. This info has been added.
2. This section is in the same place in all of my guides, I see no problem (and have had no problems) with its location. Anyone following a guide should read it first before attempting it anyway.
3. I've added inductions to download the zip directly to the phone, less mess.

emailrob said:
Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery
Click to expand...
Click to collapse
This is already covered here:
http://forum.xda-developers.com/moto-x-style/help/root-to-updates-t3200588

Oaklands said:
You can download an MD5 checker. They give you the MD5 checksum and you can compare when you run the utility. Just do a google search for md5 checker.
Click to expand...
Click to collapse
If you're on Windows, I highly recommend this one, I've been using it for ages: http://code.kliu.org/hashcheck/

I flashed SU and it didn't give me root, any suggestions?

mxpxboi said:
I flashed SU and it didn't give me root, any suggestions?
Click to expand...
Click to collapse
Have you enabled root for apps (and adb if you wish) in Developer Options?

Heisenberg said:
Have you enabled root for apps (and adb if you wish) in Developer Options?
Click to expand...
Click to collapse
I don't see root for apps in Developer Options.

mxpxboi said:
I don't see root for apps in Developer Options.
Click to expand...
Click to collapse
Ok. I don't have this device yet (I have to jump through a few hoops to get it in my country), hopefully one of our other helpful members can lend a hand with your problem.

Heisenberg said:
Ok. I don't have this device yet (I have to jump through a few hoops to get it in my country), hopefully one of our other helpful members can lend a hand with your problem.
Click to expand...
Click to collapse
Well thanks for your help anyway. I followed the steps to a tee, and no root. So I was a little confused.

mxpxboi said:
Well thanks for your help anyway. I followed the steps to a tee, and no root. So I was a little confused.
Click to expand...
Click to collapse
It's a bit odd because this is definitely how to root this phone. Was the SuperSU flash successful in TWRP? Have you tried a second time?

Heisenberg said:
It's a bit odd because this is definitely how to root this phone. Was the SuperSU flash successful in TWRP? Have you tried a second time?
Click to expand...
Click to collapse
It did flash successfully, I flashed the one it linked to UPDATE-SuperSU-v1.94.zip, I'm going to try the newest one BETA-SuperSU-v2.49.zip. I'll report back.
---------- Post added at 10:57 PM ---------- Previous post was at 10:44 PM ----------
That worked, I would update your post with this link BETA-SuperSU-v2.49
Now if I can figure out how to remove the bootloader unlocked boot screen.
All root apps except Titanium Backup seem to be working for me.

mxpxboi said:
It did flash successfully, I flashed the one it linked to UPDATE-SuperSU-v1.94.zip, I'm going to try the newest one BETA-SuperSU-v2.49.zip. I'll report back.
---------- Post added at 10:57 PM ---------- Previous post was at 10:44 PM ----------
That worked, I would update your post with this link BETA-SuperSU-v2.49
Now if I can figure out how to remove the bootloader unlocked boot screen.
All root apps except Titanium Backup seem to be working for me.
Click to expand...
Click to collapse
Cool, I've updated the link. There's a thread discussing how to remove that boot screen in the q&a or general section. Not sure about your Titanium problem, if you have root access it should work.