yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] durrence:
This works, and I see my device. All of the adb commands work. The procedure works up to the point where i enter the second "adb reboot bootloader". At that point my xoom is stuck at the Motorola flash screen which shows the logo, and at top, "Starting fastboot protocol support". The xoom no longer responds to any adb or fastboot commands.

Without doing anything else, I can disconnect the xoom, connect my Samsung android phone and it responds to all of the adb commands.

I have to hold the volume up button on the xoom while I push the power button to get it to turn off so it will re-boot.

I have read comments on this and other forums and many people are having the same problem.
[Xoom Android Development] jase33:
OK. Lets not let this get you down. You can manually reset the xoom using the volume up and power button. Then continue with the process. Just make sure when you do the reset disconnect the xoom from the pc and reconnect it when the Xoom is fully rebooted.

Sent from my Xoom
[Xoom Android Development] durrence:
I have no problem re-setting the xoom and using it. I am trying to get it rooted using the procedure at the beginning of this thread, but it doesn't work.

I would settle for getting it rooted using any other procedure. So far no one has pointed me to a procedure (that works) to root my stock 3.2 xoom.
[Xoom Android Development] jase33:
Well the process does work. It has worked for others who have posted in this thread and for myself multiple times. I suggest you read through the adb guide that is linked in the op. And also try and learn more about your Xoom before saying something does not work. Everyone who has pm'd me for help found an issue with their adb setup or was typing something wrong. If you can't figure it out I don't know what to tell you and I cannot do it for you.

Sent from my HD2
[Xoom Android Development] Kagalaska:
now rooted the above works still received "link failed File exists" msg just moved to next command. thanks
[Xoom Android Development] jase33:
That's awesome. Glad to hear it.

Sent from my HD2
[Xoom Android Development] durrence:
Finally rooted. This may help others who had my problem:

I was still stuck at "fastboot flash boot rootboot.img"

Computer kept showing "error: cannot load 'rootboot.img'" and my xoom showed the Motorola logo, and "Starting fastboot protocol support" at the top.

After beating my head against the wall for a week, I decided to use a different computer. I had been using a fast 64 bit computer running Windows 7. I then fired up my old, slow 32 bit computer running Windows 7, loaded all of the software, files, and drivers on it and the procedure worked like a charm.

Although I had loaded the latest Motorola driver, I noticed while using the old computer (the one that worked) that after I entered the second "adb reboot bootloader" the computer said that it was loading a new driver. That never happened with other computer. Go figure.

Thanks to everyone who tried to help.
[Xoom Android Development] disgustip8ted:
dont hate too much on htc, they voxed to not lock bootloaders any longer, compounded with that htc made the first nexus phone (which i have and still love) and the bootlaoder unlocking process is the same as this.

i just got the wifi xoom yesterday so im catching up on everything, i searched around a bit and found that fastboot oem lock works on some models, does it still work on 3.2? i imagine you would have to flash the stock boot loader back, is there an image of that around somewhere(probably on the moto xoom source code page, will have to check that out)?

edit: ah very nice, found the system images here: http://developer.motorola.com/products/software/ will try the process of relocking in a bit once its done charging if no one has tried this yet.
[Xoom Android Development] ccossin:
Are the steps for pushing Superuser absolutely necessary or can I skip that and install Superuser later?

I ask because I've previously purchased Superuser Elite and I want to use that.
[Xoom Android Development] F22loader:
Worked flawlessy! It was easier copying and pasting the text and that way was less prone to typos. Thanks a lot for this guide.
[Xoom Android Development] fredexcav:
i have the same issue, but i dont see an option to open the command window in the directory
[Xoom Android Development] fredexcav:
i have the same issue, but cannot see an option to open a command window in the directory:(
[Xoom Android Development] jase33:
You can install later. That is fine, but remember your root apps will not work until it is installed.

Sent from my Xoom
[Xoom Android Development] jase33:
Hold down the shift key and right click the mouse. You will then see an option that says "open command window here"

Sent from my Xoom
[Xoom Android Development] fredexcav:
got it thanks!!
[Xoom Android Development] ccossin:
Thanks muchly.

Next query: I downloaded rootboot, but the file I got was rootboot.txt. Should I just rename it to rootboot.img?
[Xoom Android Development] algirnavi451:
anyway to root my Xoom, which is on 3.2 with a Mac?
[Xoom Android Development] jase33:
I just tested the download link and the file downloaded as rootboot.img. Maybe try re-downloading.
[Xoom Android Development] jase33:
Follow this for the Mac:

You will need fastboot for mac. Download HERE

Open a terminal (located in the utilities folder)

Navigate to your sdk/platform-tools folder

Type; ./adb devices - (look for the xoom serial number to show its connected.)

Type; ./adb reboot bootloader

Type; chmod 755 fastboot

Type; ./fastboot oem unlock

Type; adb reboot bootloader

Type; ./fastboot flash boot rootboot.img

Type; ./fastboot reboot

Type; ./adb remount

Type; ./adb push su /system/bin

Type; ./adb shell

Type; chmod 4755 /system/bin/su

Type; exit

Type; ./adb push Superuser.apk /system/app

Disconnect and reboot xoom. Download a root app and test.
[Xoom Android Development] algirnavi451:
when i get to ./fastboot oem unlock, i get an error that says i cannot execute binary file. I downloaded the fastboot for mac that you have in the OP
[Xoom Android Development] jase33:
do you have it in the folder with your adb tools? you must have the android sdk installed if you do not.
[Xoom Android Development] algirnavi451:
yes I do, I have the SDK installed as well with the necessary extension (platform-tools) which has the adb command. thats where all my files are in, like fastboot, su, recovery and such. I assume i was supposed to unzip the fastboot download
[Xoom Android Development] cenkaetaya:
hi, we have tried the process a few times with all indicated success. all files and operations seem to go through perfectly like instructed.

however once im done, i reboot, there is no root. i downloaded superuser, but it doesnt open, just seems to hang at its background. we have replied the flashing commands and it still doesnt seem to be rooted. i am not sure what is wrong since everything seemed to go smoothly, and ...

its not rooted.

any help

thanks
[Xoom Android Development] jase33:
If your files are in the right place and you are starting terminal with the correct path then I don't know. Sorry, but I don't know Mac that well. Maybe someone Herr can help. Good luck.

Sent from my Xoom
[Xoom Android Development] jase33:
It seems like the permissions are not being set. Try again and pay close attention for any error messages.

Sent from my Xoom
[Xoom Android Development] algirnavi451:
You had the wrong fastboot, a little digging around i found it here:

http://developer.htc.com/adp.html
[Xoom Android Development] jase33:
Wow. Thanks. I could have sworn that's the one from my MacBook pro. But then again I never use it. I updated the link in the op.

Sent from my HD2
[Xoom Android Development] joshw0000:
Hey guys, quick question. I booted to bootloader and did the oem unlock. I read the disclaimer and "thought" I selected volume up. My device now reads "Device unlock operation aborted" and the volume keys no longer respond. Should I do another adb reboot bootloader to start over, or power the device off. Not really sure what I should do to safetly get out of this mode or if I'm even in any danger. Thanks for any help!

Edit: Disregard. I didn't follow the guide properly...on to the next step.
[Xoom Android Development] Joel1030:
Great tutorial!!!!
[Xoom Android Development] gitit20:
Thank u for this I looked and looked could not find it but then some one linked to it thanks guys...
[Xoom Android Development] its114:
Great work on the guide! I flashed 3.0.1 first, then allowed the xoom to update to 3.1 and then 3.2. Experienced a few hiccups with fastboot commands from terminal. I had to install MOTOROLA drivers and Android SDK on another computer, then retry. The process was a breeze after switching computers. Success!! Now I'm rooted and on 3.2!

Not sure if it matters but when I installed the android SDK on the 2nd computer, noticed there is a 3.2 install that my first machine didn't have.
[Xoom Android Development] gitit20:
Just want to be sure but after a hard reset will i still be rooted?
[Xoom Android Development] rmarquez1974:
Yes.
[Xoom Android Development] CARLITOZ18:
help me im new

I unlocked my xoom but I don't know were I have to put the files fasboot, kernal stock, and the new boot anyone can tellme were I have to put that files??
[Xoom Android Development] droidx1978z4:
You will get different answers on this depending on who you ask. A lot of people will tell you to put them in the tools or platform tools folder. I personally just created a new folder on my hardrive named android and put them in there. Once you open a command prompt you will have to type cd C:\Android to designate the path though. From there just follow the directions in the OP.
[Xoom Android Development] Androidalchemist:
How come when I type advanced push such/system /bin. It says cannot state 'su': no such file or directory. Any help would be great thanks
[Xoom Android Development] jase33:
Because the directory path in the command window is not the same location as where that file is.

Sent from my HD2
[Xoom Android Development] Androidalchemist:
Thanks
[Xoom Android Development] Androidalchemist:
Still stuck
[Xoom Android Development] Androidalchemist:
I did what was said in the directions but I'm missing something
[Xoom Android Development] JRd1st:
Did you put su and superuser.apk in the same folder that adb resides in?

Also go to the folder where adb is and do Shift + right-click and select "open command window here " and run the adb commands from there.
[Xoom Android Development] rickyx:
Anyway to unroot...

Hey, it's just an amazing tuto you have written Jase. I've enjoyed my beloved rooted xoom a lot. Thank you so much for that. But now i'm gonna change it for the 3G version and the warranty is void. Is there any way i can unroot and lock it via adb?

I can't find the one click app and the forum is closed on XDA...

Thank you for any help. :)
[Xoom Android Development] Androidalchemist:
Thanks man
[Xoom Android Development] mhz1000a:
Yeah!!! done~Now i can use change my ip. thank u very much. =)
[Xoom Android Development] jase33:
because neither of those programs are meant to be run alone. open a command window and type your adb & fastoot commands from there.
[Xoom Android Development] Androidalchemist:
Link failed file exists, ln-s/system /bin/su/system /xbin /su
[Xoom Android Development] Androidalchemist:
Nevermind got it, about time! Thanks for the help.
[Xoom Android Development] mhz1000a:
thank u, i alrealy flash done,

i copy everything and cmd.exe to platform-tools folder, and open cmd.exe type fastboot, and ......... and every work =) thanks :D
[Xoom Android Development] PirateGorilla:
Thank you very much. Excellent tutorial.
[Xoom Android Development] fopho:
I have searched through this forum and tried what some people have said but im not really having any luck in getting this working. Whenever I do the "fastboot flash boot rootboot.img" i get the error: cannot load 'rootboot.img'. I took another persons advice and tried it on an older computer that is not on 64 bit windows (my main computer is on windows 7 64bit but i also tried it on a win7 32 and a windows xp.) I get the same error on all three computers.

Yes i have all the files in the appropriate folders

Anyone have any idea how to get it working?
[Xoom Android Development] cenkaetaya:
I would like to report that i did finally root it.

the issue seems to be with 64bit, after many retries on my vaio z, we tried it on my friends 32bit t-pad, and it worker.

however a few questions..... it seems that the XOOM generally doesnt work as well.

certain apps will crash and not work. like raging thunder works, but crashes supppper earily. that falling meat boy, game i forget what its called, no longer works and worked before root.

like.. why is this? i thought i unlocked my device why are things working less? i almost feel like unrooting it again.

it was more stable in games.

anyone else have this issue?
[Xoom Android Development] rickyx:
@fopho. I ve had this problem too. Try to put all the files (rootboot.img, su, Superuser.apk...) in the same folder as the adb and fastboot executable (platform-tools something like that) and try again.
[Xoom Android Development] fopho:
I have them in the same folder as adb. Should I put them in a subfolder?
[Xoom Android Development] runandhide05:
to any one on stock 3.2 are you having any wifi issuses, dropping days? Going from a blue wifi icon to the grey?
[Xoom Android Development] steiner:
Wow - excellent write-up. Exactly the detail that I needed to get this done.

Thanks!
[Xoom Android Development] steiner:
Trying to verify root -- Hoping/guessing it is simple - any tips?

As a follow up: I am in terminal on the device and I can see the su link from /system/xbin -> /system/bin/su

From inside the /system/bin directory, I see the su folder with (-rwsr-xr-xr-x root root) privileges.

::

Root Access is not properly configured or was not granted.

Superuser.apk - com.noshufou.android.su - version 2.3.6 is installed!

The adb binary is set to default shell user access as root

Standard su binary location: ls -l /system/bin/su:

-rwsr-xr-x root root 26264 2011-08-05 08:53 su

Standard su binary location: ls -l /system/xbin/su:

lrwxrwxrwx root root 2011-08-08 10:19 su -> /system/bin/su

Alternate su binary location:

/sbin/su: Permission denied

SU binary not found or not operating properly
[Xoom Android Development] steiner:
Hmmm - for some reason, my su privileges had changed to not include the s. Logged into the machine from adb-remount, re-ran the chmod command and restarted. Working now!
[Xoom Android Development] Neofury212:
Looks Great! you wouldn't happen to have a boot.img for a 3g 3.2 laying around?-AT
[Xoom Android Development] disgustip8ted:
you can grab the system images from the moto dev website. its a zip that includes the boot, recovery, system and userdata .img files that you can flash. make sure to get the proper ones for your model.

here is the site:

http://developer.motorola.com/products/software/
[Xoom Android Development] droidx1978z4:
This isn't really the place to post this question, but yes many people have the same issue. I have this problem on both the xoom and my transformer since updating to 3.2. You can stop this by assigning a static IP instead of using DHCP. There are at least two threads dedicated to this issue.
[Xoom Android Development] aplacetorest:
ok newbie here

i extracted all the files to a folder. then i opened command prompt. typed what you said, but it said not recognized. I cant even get past step one haha. help?
[Xoom Android Development] SnakeManJayd:
Just used this to unlock my Xoom. Worked perfectly.

Only suggestion is maybe to make the spaces in:

ln -s /system/bin/su /system/xbin/su

clearer, it was hard to see whether it was spaces or not.

great review though. Thanks
[Xoom Android Development] c9h9no3:
Worked perfect, for the Mac users that aren't familiar with adb or sdk. Follow the beginning steps for the MS users to extract the files, and then scroll down to the Mac directions and download the fastboot for mac. Put that file in the tools folder and rename it fastboot instead of fastboot-mac.

Pretty straight forward tutorial.

Thanks!
[Xoom Android Development] allenlo83:
Is this rooting method suitable for MZ600 Verizon Xoom?
[Xoom Android Development] jase33:
Updated OP to include Verizon 3G

Sent from my HD2
[Xoom Android Development] let22:
Your 3G Verizon boot (kernel) partition link is not working
[Xoom Android Development] jase33:
fixed link
[Xoom Android Development] kosenn:
I will admit I was a little nervous about doing this. Once it was done, I breathed a sigh of relief and accomplisment. The instructions are straight forward and clear. Thank you.
[Xoom Android Development] shuura:
I finally worked up the nerve to root my Xoom after having it for only 4 days. I followed the instructions and all went through without a hitch! Amazing work! Thank you!!
[Xoom Android Development] oshizzle1991:
I was able to unlock my bootloader, but when i try and flash the rootboot.img, i get this error "error: cannot load "rootboot.img"" any ideas? i'm very experienced with adb and rooting lol, its not like i dont have adb or fastboot set up. any help would be appreciated!
[Xoom Android Development] cwizardtx:
Is the .img file you are flashing in the same folder as fastboot.exe ?

I like to put all my stuff in the platform-tools folder of the Android SDK including all of the .img files.

I used this guide as a reference for going back to completely stock FYI, and it was just what I needed for assurance.

Going back and forth between stock/non-stock/rooted/un-rooted is a simple matter at this point :)
[Xoom Android Development] disgustip8ted:
C heck the md5 for the download and mak sure the battery is over 2% or plugged in
[Xoom Android Development] o0 DIDDY 0o:
Im having the same problem. I am keeping all my files androidsdk/tools. Anyone have a solution?
[Xoom Android Development] oshizzle1991:
so i was able to flash the img....but it was freaking weird. I left my computer alone for like 4 hours, then tried to flash the image (i put everything in the right folders btw) the first time it failed...so i was getting aggitated, so i immediatley tried it again, and it flashed it succsessfully. Totally weird, but my xoom is now rooted and is running Hammerhead rom!
[Xoom Android Development] Arun01:
I've done everything down to the T...but after i reboot & download a app requiring root access it gives me a error..requires root access message...and i never got an error during my entire rooting process..what should i do?
[Xoom Android Development] Slimgym20:
If anyone is having issues setting up ADB, I found this post to help a ton!

http://www.xoomforums.com/forum/mot...windows-7-64-bit-other-windows-platforms.html

It cuts out a lot of things and makes it really simple.
[Xoom Android Development] o0 DIDDY 0o:
It finally flashed for me as well. Now that I'm rooted though I am experiencing this graphical glitch on the Motorola dual core splash screen, seconds before the xoom loads into the boot animation. Any one else experiencing this?
[Xoom Android Development] BiFi2000:
Re-locking

go to: http://xdaforums.com/showthread.php?t=1209341

this gives you an explanation to relock.:rolleyes:
[Xoom Android Development] brentc133:
Please help. When I type in the command prompt window "cd C:\adb remount", I get the following response. "adb is not recognized as an internal or external coomand,operable program, or batch file. I had no problems loading the rootboot.img and fastboot reboot. I never unlocked the bootloader since I had previously when I went from canada regional 3.0.1 to US 3.2. Do I have to unlock again?
[Xoom Android Development] oshizzle1991:
adb remount is a command, you have to type adb remount when you are in androidsdk/tools. so cd to your androidsdk folder, then cd to tools, then type adb remount
[Xoom Android Development] MiamiE:
Is there a video of this up yet? It would be extremely helpful for those non tech savy users. :(
[Xoom Android Development] novalovr66:
Chmod

I keep getting this

chmod 4755 /system/bin/su

Unable to Chmod /: read-only file system

Any ideas?
[Xoom Android Development] PhantomHacker:
Where can I obtain stock 3.2 flashable zip?
[Xoom Android Development] hksuper:
Thank you, I think it worked!

Hi,

I'm a first time rooter, and your guide gave me hope, so I tried it and everything seemed to work but then I downloaded Titanium Backup Root and it said I didn't have root permissions. now it says I do...weird. So I have been trying to make the SD card R/W using Total Commander for Android, but it's not sticking. Did I do something wrong? Do I not really have root?

If I am rooted, what do I get with a ClockworkMod (I mean, what additional functionality?) that I don't get with what I did? Or are there other mods that I may want and why? Is it the pictures? The wallpapers?

Thanks again! and sorry for the noob questions!
[Xoom Android Development] droidx1978z4:
I would guess that you are in fact rooted. Sometimes apps will tell you that you don't have root access the first time you run them because you haven't allowed them superuser access. Then when you go to open the app again it will ask you if you want to grant that app superuser permission.

I'm not familiar with total commander, as I used root explorer myself, so I can't help you there.

Rooting your device and not installing clockwork mod is kind of pointless in my opinion. They pretty much go hand in hand. CWM will allow you to make a backup of your system, and then it allows you to easily flash different roms, kernels, themes, mods, etc. It also allows you to flash back to the recovery that you made, if you experience any issues with whatever you have flashed to your device. Hope that helps.

Look around the xoom development forum to get an idea of what you can flash to the device. The standard way to flash pretty much anything you will find there is through clockworkmod.
[Xoom Android Development] omnia1994:
i m stuck in the 1st step. i checked my sdk & moto usb driver files, but how do i check my adb files? i m noob at android

edit: it said "adb" is not recognizes as an internel or externel command, operable program or batch file"

so what have i missed? i dont really understand the use od android adk n moto driver
[Xoom Android Development] bronisb:
Wow, I made it. It was the first attempt, and according to the procedures in this topic it was very simple, the whole process was very clearly written and understandable, especially for novices such as myself. The only problem I had with adb install, it took me the lot of time. Very good and helpful forum. Thanks again.
[Xoom Android Development] SuicideMyk:
stuck on step 8 fastboot flash boot rootboot.img (for WiFi)

I get error: cannot load 'rootboot.img

all my files are in local disk C drive ?
[Xoom Android Development] jase33:
is that the path you have open on your command window? have you edited your PATH string to include ADB to work from that location? read through the link in my OP to the ADB Guide. It will get you past this.
[Xoom Android Development] SuicideMyk:
I got it now, must have had a bad rootboot.img... after downloading a new one again everything went smooth :cool:
[Xoom Android Development] crazyguy7038:
I've gotten as far as "fastboot flash boot rootboot.img" but the it keeps saying "<waiting for device>". I've tried it over and over many times rebooting and restarting things. As far as I can tell everything is in it's right folder but I have no luck. It won't move past it. Any advice?

Edit: Fixed it...
[Xoom Android Development] dejavu157:
on the ln -s /system/bin/su /system/xbin/su part, i keep getting link failed read-only file system.. can someone please help? I typed it exactly

"ln -s /system/bin/su /system/xbin/su". what am i doing wrong?
[Xoom Android Development] GReddySetGO:
I'm have a little trouble as well... AFAIK, I followed all the steps and did everything right. I have superuser on my apps list, however when I try to use some screenshot apps, it doesn't ask me for superuser permission and I am unable to use it... This should be a clear indication I am not rooted, correct?