[GUIDE][US WIFI & 3G] How To Root Your Xoom From 3.2 Stock [PC & Mac]

[TreyDaPrince]

Unless I'm mistaken JCase and Jase are two different people.

Sent From My Xoom or Thunderbolt, pick one

 

[1el]

I am stuck at •Type; ln -s /system/bin/su /system/xbin/su (this line starts with lower case "L", like llama)

i get the following error: "ln" is not recognized as an actual .....

 

[jase33]

I am stuck at •Type; ln -s /system/bin/su /system/xbin/su (this line starts with lower case "L", like llama)

i get the following error: "ln" is not recognized as an actual .....

Keep trying, you will get it. Try copy and paste the command. Its easy to mess up the spaces if you're not carefull

Sent from my Xoom

 

[1el]

thank you Jase,

finally got it, but i am stuck at: chmod 4755 /system/bin/su . Once in the adb shell i get the msg: no such file or directory.

help please!!!!!!!!!!

 

[TreyDaPrince]

thank you Jase,

finally got it, but i am stuck at: chmod 4755 /system/bin/su . Once in the adb shell i get the msg: no such file or directory.

help please!!!!!!!!!!

Be sure to place the su and su binary in the same place you run fastboot.

Sent from my Xoom or Thunderbolt, pick one

 

[Legato Bluesummers]

it sounds like he never pushed the SU and Super user APK files across if it can't find them in the device.

 

[durrence]

stuck

I am stuck at "fastboot flash boot rootboot.img"

Computer shows "error: cannot load 'rootboot.img'" and xoom is stuck at the
Motorola flash screen which shows logo, and at top, "Starting fastboot

protocol support"

I can power down and reboot the xoom and it starts normally. I can run adb

shell and see all files in the xoom. I have started this procedure 3 times,

made sure I had the latest files and all files in the right places and it

stops in the same place every time.

Any suggestions?

 

[jase33]

The file you are trying to push is not in the same place you opened the command window. That is why it can't find the file. Open command window where you saved the the files by right clicking in that folder and selecting open command window. If they are on your desktop, right click there and open a command window. The files you want to push must be in the same directory you have opened the command window.

Sent from my Xoom

 

[1el]

I had the same problem. I just updated the drivers. Put all files on the desktop (make sure to unRAr the file Zip file as well), and press shift and right-click, open command from there.

 

[1el]

Got it ThanKS

 

[Scourge1024]

Thanks! The other solution using CWM recovery won't work for me because there's not enough space on my SD card for it. Hey, it's from way back. It's tiny.

 

[Kdawg1700_1]

Thanks

Thanks for this procedure. It worked great after reading the whole thread

 

[jayhammy]

None of the fastboot commands works. When I type adb reboot bootloader, the Xoom show "starting Fastboot Protocol support" in upper left corner. But typing the "fastboot" commands in the command prompt give me the error "not recognized as an internal or external command." What am I doing wrong?

 

[JRd1st]

Try going to the folder where fastboot resides, usually C:\Program Files (x86)\Android\android-sdk\tools with your file manager. Then, in that window, click Shift+right click and select "Open command window here" and run your fastboot commands from there.

 

[jayhammy]

Try going to the folder where fastboot resides, usually C:\Program Files (x86)\Android\android-sdk\tools with your file manager. Then, in that window, click Shift+right click and select "Open command window here" and run your fastboot commands from there.

Thanks. But am I typing the words "fastboot....." into the command prompt window or someplace else? What do I do with the fastboot app?

EDIT: nevermind! I hadn't changed the directory to where the tools are. All set for now. Thanks!

EDIT #2: SUCCESS!

 

[Kagalaska]

ok so all seems good up to and including adb shell command. the next line that shows in the command prompt window is a # symbol, i paste the next code line in and get the following- the pasted command is repeated and "link failed File exists". any ideas?

 

[1el]

ok so all seems good up to and including adb shell command. the next line that shows in the command prompt window is a # symbol, i paste the next code line in and get the following- the pasted command is repeated and "link failed File exists". any ideas?

I had the same thing. I just restarted my xoom and started at the remount command!

 

[Kagalaska]

thanks, will give it a try

edit restarted xoom, started at adb remount still same result. 3 attempts

 

[JRd1st]

thanks, will give it a try

edit restarted xoom, started at adb remount still same result. 3 attempts

Sounds like the link is already created and it's not letting you do it again?

I'd try going to the next step. Worse that could happen is you wouldn't have su linked...

Sent from my Xoom using XDA Premium App

 

[durrence]

I am having the exact same problem. The xoom stops responding to the computer because it does not completely re-boot after the second "adb reboot bootloader" and it hangs on the Motorola splash screen and shows "Starting fastboot protocol support". If it is re-booted it starts responding again.

There seems to be a problem with the bootloader in version 3.2.

I have followed these instructions precisely, for 5 tries and the results are always the same. Anybody else have any suggestions?