Database Info

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

**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

HTC OneX AT&T Manual root process (No Desktop)

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.

[Q] How to unroot phone Atrix 2

I used the eacy one click to root phone. I would like to unroot it now. I am having touch screen freezing problem. I need to start removing applications to see which one is causing the problem or if it is a hardware issue or software.
I downloaded the zip file 1-click_exploit. I expanded the files and ran the application. I have read that there is an option to uninstall with in that file but I don't see one. Where do I find it. If I just do a factory reset will it remove it? If I do a reset do I have to repurchase all of my apps?
Thank you in advance!

A factory data reset will not remove root.
Also, a reset does not delete your purchases. They are all stored in your google account. So, if they do get deleted, just reinstall them.
As far as unrooting, I do not know. Someone else may chime in here...probably going to tell you to post in the Q&A section as well.

Doesn't the one-click have an un-root feature?
Sent from my bootloader-locked MB865.

The one click method also has an un root option in the folder.
Sent from my MB865 using xda app-developers app

Generally the only trace rooting leaves is a setuid binary "su" in /system/bin. And Superuser.apk to manage permission which apps get to invoke the binary. So unrooting involves uninstalling Superuser application and removing the su binary. If you want to do it by hand: (1) adb remount (2) adb shell (3) su (4) rm /system/bin/su

kousik said:
Generally the only trace rooting leaves is a setuid binary "su" in /system/bin. And Superuser.apk to manage permission which apps get to invoke the binary. So unrooting involves uninstalling Superuser application and removing the su binary. If you want to do it by hand: (1) adb remount (2) adb shell (3) su (4) rm /system/bin/su
Click to expand...
Click to collapse
I have no idea what the above manual steps are for. I can uninstall the application but where and how do I remove the su binary. On the phone? Please send directions for a non technical type of user.
Thank you!

MaTrixJ said:
The one click method also has an un root option in the folder.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Not sure where in the the following files in 1-click_exploit is the unroot option.I have attached a list of the files in the download.

bushbaum said:
Not sure where in the the following files in 1-click_exploit is the unroot option.I have attached a list of the files in the download.
Click to expand...
Click to collapse
Out of these files, adb.exe and .dll files are left in your windows PC. Not sure if they are deleted afterwards, if not, you can always unzip the above into a directory. You'll need the adb and the dll files.
The su and superuser.apk are two files that are pushed to your phone that provides the root functionality.
The zerg file is the exploit payload temporarily used to root your phone, and removed later by the script.
So if you have unzipped these into a directory, connect your phone via USB (make sure usb debugging is on), and run the commands
Code:
adb.exe remount
adb.exe shell
su // superuser may pop a permission request on phone screen
rm /system/bin/su
rm /system/app/Superuser.apk
exit

kousik said:
Out of these files, adb.exe and .dll files are left in your windows PC. Not sure if they are deleted afterwards, if not, you can always unzip the above into a directory. You'll need the adb and the dll files.
The su and superuser.apk are two files that are pushed to your phone that provides the root functionality.
The zerg file is the exploit payload temporarily used to root your phone, and removed later by the script.
So if you have unzipped these into a directory, connect your phone via USB (make sure usb debugging is on), and run the commands
Code:
adb.exe remount
adb.exe shell
su // superuser may pop a permission request on phone screen
rm /system/bin/wu
rm /system/app/Superuser.apk
exit
Click to expand...
Click to collapse
What mode is my usb connection? charge only? I have the phone setting usb setting on. I run the commands (using the run command in windows accessories). When I go run "adb.exe remount" the black command screen blinks on screen so then under I go to run again and entered "adb.exe shell" the run command screen opens up with [email protected]:/$ I put in "su" After I entered the command rm system/bin/wu I get a "read only error" how do I change from read only?
Sorry for all these questions but I warned you that I was not a technical user. Thanks

bushbaum said:
What mode is my usb connection? charge only? I have the phone setting usb setting on. I run the commands (using the run command in windows accessories). When I go run "adb.exe remount" the black command screen blinks on screen so then under I go to run again and entered "adb.exe shell" the run command screen opens up with [email protected]:/$ I put in "su" After I entered the command rm system/bin/wu I get a "read only error" how do I change from read only?
Sorry for all these questions but I warned you that I was not a technical user. Thanks
Click to expand...
Click to collapse
I was wondering do I have to have the elite version superuser installed to grant permission to system? I just have the free version.

bushbaum said:
What mode is my usb connection? charge only? I have the phone setting usb setting on. I run the commands (using the run command in windows accessories). When I go run "adb.exe remount" the black command screen blinks on screen so then under I go to run again and entered "adb.exe shell" the run command screen opens up with [email protected]:/$ I put in "su" After I entered the command rm system/bin/wu I get a "read only error" how do I change from read only?
Click to expand...
Click to collapse
1. yes -- charge only
2. it is better to open a command prompt -- in run commands type in "cmd" which'll give you a shell, easy to track command outputs
3. in that shell cd to the directory you unzipped and run "adb.exe remount"
4. Unless it says "remount succeeded" further operations won't succeed
5. After you execute "su" your prompt will change from $ to # ... is this happening?
6. Only on # prompt, you can do "rm /system/bin/su" ... that too only if remount succeeded
Let us know at which step it fails.

kousik said:
1. yes -- charge only
2. it is better to open a command prompt -- in run commands type in "cmd" which'll give you a shell, easy to track command outputs
3. in that shell cd to the directory you unzipped and run "adb.exe remount"
4. Unless it says "remount succeeded" further operations won't succeed
5. After you execute "su" your prompt will change from $ to # ... is this happening?
6. Only on # prompt, you can do "rm /system/bin/su" ... that too only if remount succeeded
Let us know at which step it fails.
Click to expand...
Click to collapse
I get the following error after entering the run "adb.exe remount"
*daemon not running starting it now*
*daemon started successfully*
remount failed: operation not permitted

bushbaum said:
I get the following error after entering the run "adb.exe remount"
*daemon not running starting it now*
*daemon started successfully*
remount failed: operation not permitted
Click to expand...
Click to collapse
Then try remounting manually:
Code:
C:\> adb.exe shell
edison$/ su
edison#/ mount -o remount,rw /dev/block/system /system
Afterwards proceed with rest of the script.

[Q] Older Xoom, root problems, read this ! (SOLVED)

As some of you may know I've not been able to unlock ro root my Xoom, much less update the android version. I'm still running 4.1.2, that was last updated by Google. (I have two Xooms)
I have tried everything I've found on this site, and over at the Xoom forums, to no avail. I did, finally get one of them unlocked by switch from a Linux PC to an old XP box.
But, nothing else has come even close to working.
Yesterday I found this,
http://www.droid-life.com/2011/02/25/how-to-root-the-motorola-xoom/
It seems (to this relative newbie) that Droid Life offers a bit more information about rooting and such??? An example below:
---------------------------------------------
5. Type: adb reboot bootloader
6. Type: fastboot flash boot rootboot.img
7. Type: fastboot reboot
8. Wait for your device to reboot all the way.
9. Type: adb remount
10. Type: adb push su /system/bin
11. Type: adb shell ln –s /system/bin/su /system/xbin/su
12. Type: adb shell chmod 4755 /system/bin/su
13. And now this next step you have a couple of options.
Option A: Push Superuser.apk in adb. Type: adb push Superuser.apk /system/app
Option B: Exit adb and download Superuser app from the market.
--------------------------------------------------------
Why couldn't I find this info here, or at the Xoom forums? update: I found it on the Xoom forums
NOTE I still haven't tried it to see if it will work, but the "placement info" seems pretty relevant.

Duh, I get it now.
OK, I get it now. $$ is king.

[GUIDE] Asus fonepad 7 k012 - extSDCard write fix & hosts tweak - NO rooting

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?