Database Info

USCC Mesmerize Rooting on Official 2.2 (Froyo)

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.

[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.

[Build.Prop] Xperia L

Hi there
I was messing with my build.prop to tweak and test it on my ROM and I got bootloop. I had to flash system again via ftf as I didnot make a backup on my PC. However, there are many ways to edit/flash build.prop again and thus if anyone of you have a problem while editing build.prop you can write it back to your device using ADB Shell commands.
Run Command Prompt where you have adb. You must have drivers installed properly. For drivers check into my forum :
http://forum.xda-developers.com/showthread.php?t=2493042
adb pull /system/build.prop C:\Users\user\Desktop
User is your user name on PC. You may copy it anywhere else by changing the location of the file.
"build.prop" on your desktop should appear. Open it with using a wordpad. Change what ever you want to.
adb push C:\Users\user\Desktop\build.prop /sdcard/build.prop
This will copy the build.prop on your sd card
ADB remount
ADB push c:\build.prop /system/ depending where your file is. In this case, I am trying to mount directly from C:/ to phone. If this doesnot work, you should use the above command to copy it in sdcard and then try to push it from sd card.
If suppose that doesnot work either, use adb shell
adb shell
A shell is used to run commands.
su mount -o remount,rw none /system
busybox cp /sdcard/build.prop /system/build.prop
mount -o remount,ro none /system
You are done ! Good Luck
UPDATE
I am unable to reach device using adb commands. Anyone who knows how can i push build.prop when my adb is not working and my phone is bootlooped

Problem using adb with Moto C

Hi, I'm having trouble choosing the right section, anyway..
After more than a year i managed to correctly install ADB drivers, because before i installed Google driver, when i noticed i must install Motorola driver , the removing of previous one did not successful done, so the Motorola one did not installed well, by manually removing files it succeed.
But now another annoying not previewed issue, i need to exchange a file in /system/etc both in my tablet and my Motorola moto C tel. , it needs to remount system part. in r/w but to do this need to restart adb as root but with 'adb root' this is the answer:
adbd cannot run as root in production builds
my system is 7.0, what can i do?

You can install a temporary root to run shell-commmands what require root-rights like mount in ADB:
Code:
adb devices
adb push <FULL-PATH-TO-SU-BINARY-ON-PC> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
adb shell "/data/local/tmp/su -c 'mount -o rw,remount,rw /system'"

I have two questions, i don't find any su command available in the net.
I don't understand how it is possible to have to do all these hard maneuvers with a debug tool, i think it might be simpler.. why there's a command remount or root if it doesn't work?