**THIS IS FOR US 3G XOOM ONLY**
**DO NOT USE THIS ON WIFI MODEL**
This guide in no way implies or expresses any warranties.
What you choose to do with your equipment is your sole responsibilty.
__________________________________________________ ______________________________________
SUMMARY
You must already be running Honeycomb 3.2 on your Xoom
You will be unlocking your Xoom, if you have not already. This will wipe data so make sure to back everything up that you would like to keep.
You will be unlocking your Xoom, if you have not already. This will wipe data so make sure to back everything up that you would like to keep.
You will be performing steps in ADB. If you are not familiar with this, read HERE first.
You will need Xoom USB drivers and Fastboot
You will need the boot (kernel) partition with rooted stock 3.2 kernel (thanks & credit to, solarnz and p3droid) [see Attachment]
You will need Superuser.apk and su binary to enable functioning root [see Attachment]
**Before you get started, make sure the USB Debugging option is enabled in the Settings. Go to Settings --> Applications --> Development -->USB Debugging**
PROCEDURE
Download and unzip files. Place kernel.img, superuser.apk & su binary in the same place you will open your command window.
Open command window:
Type; adb devices - you should see a long serial number on the screen. If no serial number appears, recheck your adb, sdk & moto usb driver files.
Type; adb reboot bootloader
Type; fastboot oem unlock - and follow the steps on your xoom's screen (You have to accept the terms by pressing the volume down key, and then select 'accept' by pressing the volume up key.)
Allow the xoom to boot up completely and go back into settings and enable USB debugging again.
In the command window on your PC type; adb reboot bootloader - (if xoom does not respond, disconnect from pc and reboot manually by holding vol up + power. then reconnect after fully rebooted)
Type; fastboot flash boot kernel.img
Type; fastboot reboot
Allow the xoom to boot completely - your xoom should be in normal operating mode for the remainder of the process.
In the command window on your PC type; adb remount
Type; adb push su /system/bin
Type; adb shell ln –s /system/bin/su /system/xbin/su
Type; adb shell chmod 4755 /system/bin/su
Type; adb push Superuser.apk /system/app
Thats it...your done!! Unplug the xoom and reboot. Your xoom is now stock rooted.
You can now flash ClockworkMod, other kernels and roms. To verify root, download a root user app from the market and run it.
You should be prompted to allow superuser permissions.
Mac Only Procedure
You will need fastboot for mac
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 kernel.img
Type; ./fastboot reboot
Type; ./adb remount
Type; ./adb push su /system/bin
Type; ./adb shell ln –s /system/bin/su /system/xbin/su
Type; adb shell chmod 4755 /system/bin/su
Type; ./adb push Superuser.apk /system/app
Disconnect and reboot xoom. Download a root app and test.
If you found this helpfull press the THANKS button.
thanks & credit to, solarnz and p3droid for the kernel & jase33 for the form and style of this TUT!
PS: to the mods --> please move this thread to the Dev part, currently it's not possible for me to post in there...
can't get this to work
I've followed the instructions to the letter a half dozen times now and when I get to
adb shell ln –s /system/bin/su /system/xbin/su
The reply is that the folder can't be found. Any advice? thanks much!
I know a lot of people have been looking for a guide like this.
dslcpm said:
I've followed the instructions to the letter a half dozen times now and when I get to
adb shell ln –s /system/bin/su /system/xbin/su
The reply is that the folder can't be found. Any advice? thanks much!
Click to expand...
Click to collapse
I just went on past that step and it appears to have still taken the root.
Hi!
Have you had the su binary in the same direstory
From which youve executed the following cmd:
Type; adb push su /system/bin
Because then everything should be fine!
Bye
Thanks a lot
Move ---> xoom android development
Hi mods,
please move this article to Xoom Android Development.
Thanks
Worked perfect
Sent from my HTC Sensation Z710e using XDA Premium App
Related
For anyone having issues with running this in linux.
I used zikronix guide and modified it for use in a linux support thread. The original thread can be found here:
http://forum.xda-developers.com/showthread.php?t=829045
This is my setup:
-I made sure to show my .bashrc profile and path to my tools folder if you needed help getting that setup as well... If not please ignore.
Code:
[email protected]:~$ cat .bashrc | grep adb
alias start-adb='sudo /usr/local/android-sdk/tools/./adb start-server'
alias kill-adb='sudo /usr/local/android-sdk/tools/./adb kill-server'
[email protected]:~$ cat .bashrc | grep android-sdk
export PATH="/usr/local/android-sdk/tools/:${PATH}"
[email protected]:~$ $PATH
bash: /usr/local/android-sdk/tools/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:
Download: http://www.wackynoodle.com/hboot202-s_off-V6.2.zip
Download (Mirror): http://sdx-downloads.com/EVO/devs/jerdog/fixes/hboot202-s_off-V6.2.zip
Now This might make things easier.
-I have this so that you are in the same enviroment that i was in so that the paths will be the same.
Code:
wget http://www.wackynoodle.com/hboot202-s_off-V6.2.zip
mkdir Evo-root
mv hboot202-s_off-V6.2.zip
cd Evo-root
unzip hboot202-s_off-V6.2.zip
- This step I just made sure that adb devices showed my device. If not get it working.
- Once adb devices showed my device properly, I simply ran the following commands.
Code:
adb push root/unrevoked-forever.zip /sdcard/
adb push root/mtd-eng.img /sdcard/
adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip
adb push root/flash_image /data/local/
adb push root/rageagainstthecage /data/local/tmp
adb push root/amon_ra.img /sdcard/
- Then this is just changing permissions. Pretty straight forward.
Code:
adb shell
chmod 0755 /data/local/tmp/rageagainstthecage
chmod 0755 /data/local/flash_image
- Running the script. Should kick you out of adb... If not after 5 min kill the adb server and restart.
Code:
adb shell
./data/local/tmp/rageagainstthecage
- Now you should see a "#", if you do proceed. If not then run the script above again till it works.
Code:
adb shell
- If you saw that "#" run this. This can only be ran as root "#" means root.
Code:
./data/local/flash_image misc /sdcard/mtd-eng.img
Now you are going to want to reboot into the bootloader. Make sure once you do that you selet bootloader and let the PC36IMG.zip load.
Code:
reboot bootloader
After that is done reboot into the new rooted rom. Then make sure adb works again. Then run the following commands. Make sure you terminal is in the same directory this entire time there is no reason to leave the direcory we went into earlier "cd Evo-root" You directory should always be Evo-root. Thanks. The part that I found out was the second command where the entire recovery/ needed the permissions changed to be executable. As you saw in my post on that forum board.
- This will remove the PC36IMG.zip to a different name so that the bootloader won't get confused again. Then the second commands makes the directory executable recursivly. Then the third will reboot you into recovery.
Code:
adb shell mv /sdcard/PC36IMG.zip /sdcard/PC36IMG-ENG.zip
chmod -R +x recovery/
adb reboot recovery
- Now this is going to be done at the recovery screen. As long as you followed the steps above it will work fine. Should only take you about 20 mins to root this phone. Though it took me about 2 hours since no one else has been rooting using linux. I am thinking about writing a script that will root everything and alls you have to do is follow a terminal guide.... But ill see.
- Just run these commands that will allow you to flash the unrevoked-forever.zip. Once you follow the onscreen instructions of the unrevoked-forever.zip you will be able to reboot into the recovery and see the S-Off. Once that is done reboot into the rom, now we need to flash a custom recovery!
Code:
adb push recovery /
adb shell busybox --install /sbin
adb shell nohup /sbin/recovery &
- Again make sure your terminal was never closed and in the same folder. Then simply run these commands to flash the Amon_ra recovery. Since it has wimax capabilities I prefer it.
Code:
adb push root/flash_image /data/local/
adb shell
chmod 0755 /data/local/flash_image
./data/local/flash_image recovery /sdcard/amon_ra.img
reboot recovery
Now you should see the custom recovery and you should be able to flash any rom you desire!
reserved for later use
i see that they are same commands as the pc.., so would this also work with PC?
nickespi said:
i see that they are same commands as the pc.., so would this also work with PC?
Click to expand...
Click to collapse
I am guessing your talking about windows? Sure make sure adb is in your path. Though there are steps in here that are only for linux.
95% success
Well I want to thank you for this thread
It has worked for me I have root I have NAND unlocked
I can flash ROMs
The only issue I have is my radio/baseband and PRI version have been lowered
I have not been able to get thise back where they whould with either update or by using teh wimax.ADDRESS.tree.xml fix (there is no file with that)
If you have any ideas how to fix this would be much appreciated
I am unable to get higher tahn baseband 1.36.00.04.02 in ant rom
when I got teh phone it was 2.15.00.xx.xx
any help would be appreciated
100% Success
THANK YOU
My Evo
Hardware 004
Build 3.30
Hboot 2.02
Baseband 2.15.xx.xx
is now sucessfully rooted.
I did have some problems after being able to flash ROMs of not haveing PRI and Baseband updated.
On thread #787756 there are downloads that can be flashed to fix this problem if anyone else is in that boat.
zikronix sent me there for the fix...I believe he is adding it to the main thread but if it isn't there yet I wanted to add it now for anyone in my boat.
Again this method works and there is success.
Happy rooting
Hey thanx for this Linux guide. Does this steps work with the update 12.25.10 on the windows thread?
Will you update this guide?
Okay, this was my first time trying to root my phone and it would figure that non of the automated methods worked for me. Still, I was able to get root on my US Cellular Samsung Galaxy S Mesmerize (SCH-i500 for the kids keeping track at home) and these are the steps that I took. I hope this helps others who may be scratching their head wondering what to do when the developers haven't gotten around to (read: forsaken) us.
The nice thing about this method is that it doesn't require Windows (though you still do download SuperOneClick).
NOTE: This is only for an officially updated Mesmerize. Rooting is unnecessary for the leaked version.
APOLOGY: I can't post any links to anything outside the forum as I am a newer member, so, sorry for not being able to post URLs.
1. Download the Android SDK from the Android developer website and install/unzip it. You may need to add the path to the adb tool (found under platform-tools for me) to your PATH variable.
2. Download the SuperOneClick tool and unzip it
3a. If you are using Windows, then make sure to install the drivers for your phone. I don't have Windows, so don't ask me which file to download. Sorry.
3b. Enable USB Debugging on your phone (Settings->Applications->Development->Check "USB Debugging").
4. Connect your phone to your computer using the USB cable
5. Open a shell (or command prompt on Windows) and change directories to where you unzipped SuperOneClick
6. Run the following commands to copy files to your device
A. adb push psneuter /data/local/tmp/psneuter
B. adb push busybox /sdcard/busybox
C. adb push su-v2 /sdcard/su
NOTE: A quick note of each of these files.
A. psneuter - an exploit to gain root access temporarily on your phone
B. busybox - a compilation of common unix commands to help you along the CLI world
C. su - the super-user command used to gain elevated privileges
7. Run the following command to get a command line interface to your device
adb shell
At this point, you should see a $ prompt indicating that you are on your phone.
From here, you will change directories to where you put the exploit, change the permissions so you can run it, copy over the files that we need to sustain root access, and finally, install the Superuser.apk app so that you can manage root access from the UI.
Execute the following commands:
$ cd /data/local/tmp
$ chmod 777 psneuter
$ ./psneuter
Here, you will be disconnected from your device. This is normal. Just run "adb shell" again to get back in, though now, you will notice that the prompt has changed to a #. The following commands will reflect that.
# mount -t rfs -o remount,rw /dev/block/st19 /system
# cd /system/xbin
# cat /sdcard/busybox > busybox
# cat /sdcard/su > su
# chmod 4755 busybox
# chmod 4755 su
# exit
Now, you will be back on your computer. Type the following to install the Superuser.apk app.
adb install Superuser.apk
That should do it! You now have root access. Go ahead and try to install Titanium Backup (requires root). You can also install a terminal app or anything else.
I hope this helps. Report your successes/failures in the comments.
Hi there! I followed the instructions here:
Code:
Download and unzip files. Place rootboot.img, superuser.apk & su binary in the same place you will open your command window.
Open command window:
Type; adb devices - you should see a long serial number on the screen. If no serial number appears, recheck your adb, sdk & moto usb driver files.
Type; adb reboot bootloader
Type; fastboot oem unlock - and follow the steps on your xoom’s screen (You have to accept the terms by pressing the volume down key, and then select ‘accept’ by pressing the volume up key.)
Allow the xoom to boot up completely and go back into settings and enable USB debugging again.
In the command window on your PC type; adb reboot bootloader - (if xoom does not respond, disconnect from pc and reboot manually by holding vol up + power. then reconnect after fully rebooted)
Type; fastboot flash boot rootboot.img (for WiFi)
OR Type; fastboot flash boot 3Grootboot.img (for 3G Verizon)
Type; fastboot reboot
Allow the xoom to boot completely – your xoom should be in normal operating mode for the remainder of the process.
In the command window on your PC type; adb remount
Type; adb push su /system/bin
Type; adb shell
Type; ln -s /system/bin/su /system/xbin/su (this line starts with lower case “L”, like llama)
Type; chmod 4755 /system/bin/su
Type; exit
Type; adb push Superuser.apk /system/app
to root my xoom. I have an UK xoom 3.2. And everything was going great.
After the first reboot (fastboot flash boot rootboot.img )
When the xoom booted, it was fine, I've logged into my gmail account using my wifi hotspot.
But then ...
after executing this steps and rebooting:
In the command window on your PC type; adb remount
adb push su /system/bin
adb shell
ln -s /system/bin/su /system/xbin/su (this line starts with lower case “L”, like llama)
chmod 4755 /system/bin/su
exit
adb push Superuser.apk /system/app
Now I don't have wifi anymore. The wifi only shows an error.
How can I fix this? I've did a basic search but most related to ppl using version 3.2.1, since I'm using 3.2 I did not believe it would apply to myself.
Any ideas?
Thanks
No idea how to fix that one.
However I can suggest using a one click rooting method in the future - i think i used a tool called xoot the 1st time to root before jumping to ICS.
The above process you mentioned was one of the things that put me off rooting at the start of ownership.
Hopefully someone will be a long soon to help with your problem
What are the specifics of the error you're getting with wifi?
Is the error when you try to turn wifi on?
Did you allow restoring apps/settings when you booted after the rooting process?
Hi lads,
thanks for the support, I've solved by restoring the stock image (3.0) and then using the universal root procedure.
Regards
vinicius.carvalho said:
Hi lads,
thanks for the support, I've solved by restoring the stock image (3.0) and then using the universal root procedure.
Regards
Click to expand...
Click to collapse
where did you get it?
I wanted to share my experience with following this thread
http://forum.xda-developers.com/showthread.php?t=1709296
i unfortunatly do not meet the 10 post limit
Following the process i got stuck here
Code:
Now it's time to reboot
adb reboot
After phones reboots
adb remount <-----------------HERE---------------------------
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell rm /data/local.prop
adb reboot
ADB told me that i dod not have the correct permissions to push the SU file to the phone. The phone would boot, but would not load the widgets or bottom menu. Attempting to open settings would prompt Android.Core to crash.
Scary stuff
The problem was with the ADB Reboot command. It normally reboots the phone properly, but when i ran ADB Reboot, the phone cut power (off) instead of rebooting. Something did not go as intended and i needed to power on my phone, and reboot it manually without the USB cable connected (lagged too much).
After that, the ADB Remount was successful and the rest of the process ran smoothly. I am happily rooted
Thank you to all
~Can someone copy this into the actual thread? I want to help spread rootsauce.
I wanna post this guide cuz i searched around and couldnt find any method for kitkat and lollipop, get full sd card write WITHOUT permanent ROOTING.
Some may say: just root, make changes with root file manager, and unroot from superSU. BUT, for this device, from what i experienced, the option for full uninstall/complete unroot, in superSU app, will just hang and do nothing .
I use IntelAndroid-FBRL 05-16-2015 Public Trail Release, made by @social-design-concepts - a really big thanks :good:.
http://forum.xda-developers.com/showpost.php?p=60770086&postcount=352
The tweaks may work on other intel based devices, when temporary CWM recovery is triggered.
Reboot tablet in fastboot/droidboot mode - vol+ and power until asus logo apears.
Install intel android drivers - there are over 8mb limit of .7z files, so i cant add them here, just search intelandroiddrvsetup1.1.5.zip.
Connect tablet to pc with usb cable.
Unzip IntelAndroid-FBRL-05-16-2015-PTR.7z from @social-design-concepts and enter launcher.bat
type ACCEPT after reading the warning
Now:
- chose T2 if u are using Kitkat
- chose T4 if u are using Lollipop
Tablet reboots and after some screen artefacts (is normal) you are in temporary CWM recovery, which has a temporary root adb shell.
Keep tablet connected to pc.
Now download ADBfolder.7z, decompress it, and open inside a command prompt/window.
In this window insert commands, each followed by enter:
adb devices
adb shell id
adb shell mount /system
adb shell mv /system/etc/hosts /system/etc/hosts.bak
adb push hosts /system/etc/hosts
adb shell chmod 0644 /system/etc/hosts
adb shell mv /system/etc/permissions/platform.xml /system/etc/permissions/platform.xml.bak
adb push platform.xml /system/etc/permissions/platform.xml
adb shell chmod 0644 /system/etc/permissions/platform.xml
adb shell reboot
The tweaks remain even after factory reset.
For removing the tweaks, in case of installing oficial updates through OTA or manual, trigger again temporary CWM recovery, enter ADB folder, open command window and use these commands, each followed by enter:
adb devices
adb shell id
adb shell mount /system
adb shell rm /system/etc/hosts
adb shell mv /system/etc/hosts.bak /system/etc/hosts
adb shell rm /system/etc/permissions/platform.xml
adb shell mv /system/etc/permissions/platform.xml.bak /system/etc/permissions/platform.xml
adb shell reboot
It can be done, for lazy ones , with pasting these commands in two .bat files (one for install, other for remove), but I wanted ppl to see what is actually happening.
You can use another hosts file, but keep in mind the /system has limited space, so large ones may not fit.
b0by said:
I wanna post this guide cuz i searched around and couldnt find any method for kitkat and lollipop, get full sd card write WITHOUT permanent ROOTING.
Some may say: just root, make changes with root file manager, and unroot from superSU. BUT, for this device, from what i experienced, the option for full uninstall/complete unroot, in superSU app, will just hang and do nothing .
I use IntelAndroid-FBRL 05-16-2015 Public Trail Release, made by @social-design-concepts - a really big thanks :good:.
http://forum.xda-developers.com/showpost.php?p=60770086&postcount=352
The tweaks may work on other intel based devices, when temporary CWM recovery is triggered.
Reboot tablet in fastboot/droidboot mode - vol+ and power until asus logo apears.
Install intel android drivers - there are over 8mb limit of .7z files, so i cant add them here, just search intelandroiddrvsetup1.1.5.zip.
Connect tablet to pc with usb cable.
Unzip IntelAndroid-FBRL-05-16-2015-PTR.7z from @social-design-concepts and enter launcher.bat
type ACCEPT after reading the warning
Now:
- chose T2 if u are using Kitkat
- chose T4 if u are using Lollipop
Tablet reboots and after some screen artefacts (is normal) you are in temporary CWM recovery, which has a temporary root adb shell.
Keep tablet connected to pc.
Now download ADBfolder.7z, decompress it, and open inside a command prompt/window.
In this window insert commands, each followed by enter:
adb devices
adb shell id
adb shell mount /system
adb shell mv /system/etc/hosts /system/etc/hosts.bak
adb push hosts /system/etc/hosts
adb shell chmod 0644 /system/etc/hosts
adb shell mv /system/etc/permissions/platform.xml /system/etc/permissions/platform.xml.bak
adb push platform.xml /system/etc/permissions/platform.xml
adb shell chmod 0644 /system/etc/permissions/platform.xml
adb shell reboot
The tweaks remain even after factory reset.
For removing the tweaks, in case of installing oficial updates through OTA or manual, trigger again temporary CWM recovery, enter ADB folder, open command window and use these commands, each followed by enter:
adb devices
adb shell id
adb shell mount /system
adb shell rm /system/etc/hosts
adb shell mv /system/etc/hosts.bak /system/etc/hosts
adb shell rm /system/etc/permissions/platform.xml
adb shell mv /system/etc/permissions/platform.xml.bak /system/etc/permissions/platform.xml
adb shell reboot
It can be done, for lazy ones , with pasting these commands in two .bat files (one for install, other for remove), but I wanted ppl to see what is actually happening.
You can use another hosts file, but keep in mind the /system has limited space, so large ones may not fit.
Click to expand...
Click to collapse
where can i get this ADBfolder.7z?