[DroidXcon]

Post #1 = Index
Post #2 = FAQ
Post #3 = GingerSnap One click root (Retired Semi Auto root)
Post #4 = ADB rooting (Beginner-Intermediate)
Post #5 = How to root using a Mac (Beginner-Intermediate)
Post #6 = Removing apps once rooted (Coming soon)
Post #7 = How to Unroot
Post #8 = Credits

The methodS of rooting your Android device as described in the article herein is solely for enthusiasts and not for the faint of heart.

Android Central, Android Police, Team AndIRC and myself disclaim all liability for any harm that may befall your device, including, but not limited to: bricked phones, voided manufacturer warranties, exploding batteries, etc.

THESE METHODS ONLY WORK FOR ED1 BUILD, ANYTHING BEYOND THAT REQUIRE A CUSTOM KERNEL THAT INCLUDES ROOT

[DroidXcon]

Q: What is Root?

A: Root, is super user access of your phones operating system. Think of your phone as a desktop computer. Right now you are logged on as a guest account. you can browse things and use applications but if you really want to change anything in your system you can't. What gaining root does is it gives you superuser permission to alter files that you could not before; again thinking of it as a computer you now have an Administrator account.

Q:Does rooting void my warranty?

A:Yes and no. If you walk into your carriers store with a phone that has Root access and they actually check it they have the right to say this phone was tampered with. But for those of you in the know, there are methods to unroot your phone first.

Q: Does rooting slow down my phone or drain battery.

A: NO, root is not an application or a running process, gaining root does not do anything but give you permissions that you normally would not have. Basically all you did during the rooting process was move files around. Its what you do with this new found permission that changes things. But as far as just rooting it does not make a difference.

Q: Will i lose any apps or data during the rooting process?

A: No, for the same reason as above. Rooting is basically just moving some files around. Of course there is always a risk of something happening in any process. I would say chances are of causing serious problems is slim to non. Its what you do with this new found permission that changes things. But as far as just rooting it does not make a difference.

Q: I lost root during an update, am i doomed?

A: No, what happend was the file containing your super user access was over written. Just re-attempt gaining root and you will be fine.

********************************************************************************************

Preparations:

1. Download and Install Samsung Drivers



2. Go to Settings > Applications > Developement > Enable Debugging, then connect your phone to your PC, allow 2-3 minutes to configure drivers

[DroidXcon]

Gingersnap (along with all other Android modifications) is experimental software and while I have made this as safe as possible, differences in operating environments and natural disasters can cause your device to become unusable. Please make sure you understand this important fact before downloading.

Disclaimer: Neither myself, Android Central or any other member of Android Central are responsible for any disasters that occur as a result of any hack or modification you perform on your device. Your use of this application is at your own risk!

With that out of the way, I'd like to introduce you to the Gingersnap Root Utility. Gingersnap is a one-click root utility, much like SuperOneClick or Universal Androot.

The nitty gritty: Gingersnap uses a modified version of the famous to automatically root your Android-powered device and installs the necessary files to maintain a permanent root status.

Pre-use Requirements:
1) You need the . Not the Client Profile, the full .NET 4 Framework.
2) For some reason you need the redistributable installed. Don't ask me why.
3) You need proper drivers for the your phone. Your video card doesn't work without drivers and neither will your phone.
4) Before running this Utility please make sure your phone is in debugging mode

Instructions:

• Download and unzip Gingersnap-V1.2.zip to anyplace on your computer
• Connect your phone to computer in debugging mode
• Open Gingersnap-V1.2 folder
• Double click Gingersnap applications icon
  
• press GO , sit back and relax

Credits:
Gingersnap Utility: drewwalton19216801
GingerBreak exploit:
Autoroot shell script (com.sh): Droidxcon, YAY ME!
MAJOR thanks to jondevere for being drewwalton19216801's personal guinea pig!

Think you're ready? The file is attached to this post.

Source Code:
The modified GingerBreak source code is attached to this post. The filename is gingerbreak-mod-gs-src.zip

[DroidXcon]

Directions: (Assuming you followed preparations from Post #2)

Download DSChargeRoot.zip:


With your phone in debugging mode set to stay awake
1. Extract downloaded DSChargeRoot.zip file directly to your C:\ Drive

After placing DSChargeRoot folder to your C: drive it should look like this in your windows explorer. This will allow the path C:\DSChargeRoot to be found from command prompt later in this tutorial

2. Now go to your start button on your menu bar,in the run field or search field depending on your version of windows, type CMD and hit enter. The command box will present itself. From here on out just copy and paste the commands i will provide below. To paste in the command box you must right click on the mouse and select paste. Do not paste BOLD text below those are just for info.

Commands are as follows:

cd C:\DSChargeRoot 

adb devices

It will state
"List of devices attached
I500******* device"
If you dont see this you are not connected

adb push su /data/local/su
adb push Superuser.apk /data/local/Superuser.apk
adb push GingerBreak /data/local/GingerBreak
adb push com.sh /data/local/com.sh
adb shell chmod 777 /data/local/su
adb shell chmod 777 /data/local/GingerBreak
adb shell chmod 777 /data/local/com.sh
adb shell

The adb shell command will not put you in the phones internal command terminal. This is represented with "$" prompt. You will now execute the GingerBreak exploit. This make take serveral minutes.

/data/local/GingerBreak

After entering the above command Gingerbreak will do its thing. A successful exploit will end with this,"[!] dance forever my only one"
If it ends in anything else or if it hangs for more than 5 minutes pull your battery and attempt to root again.
After exploit is complete you will have a command prompt that looks like this "#". That represents root access. You will now excute shell script then reboot your phone.

/data/local/com.sh
exit
exit
adb reboot

Your phone will now reboot. Congrats Enjoy your rooted device

check app drawer to see if superuser app is installed,if it is you are rooted

[DroidXcon]

I do not own a Mac so i am not the best person to ask questions about set up but post questions and i will have people that know much more than me about Mac devices to help answer them.

It's extremely important that you download the necessary files to the proper place.
Download the following file to your Macintosh HD root folder:

Using Safari: click link to open Multiupload page --> right click the direct download button > download linked file as > click macintosh HD > click save

Open Finder - on your Mac - and double click the "android-sdk-mac_x86.zip" in your Macintosh HD root folder to extract.

Using Safari downloads window: right click android-sdk-mac_x86.zip > click show in finder > double-click android-sdk-mac_x86.zip

FYI -- Regarding Mac Disk Errors:

At various points -- throughout this procedure -- your Mac may display a disk error message like the one below. You can safely click Ignore when you see "The disk you have ejected was not readable by this computer" and click OK when you see "This disk was not ejected properly."

Do the following on your phone:

1. If your phone is plugged into your Mac – unplug it now.
2. Then hit the menu capacitive button > settings > applications > development > check USB debugging > then click Ok.
3. Plug the phone into your computer (you will leave it plugged in for the duration of this procedure).

Opening Terminal on the Mac:

1. Open applications > go to utilities > then open terminal.
2. Enlarge the terminal window for easier viewing.
3. Syntax notes:
   
   • You do not type the $ before any of the commands below. The $ represents the command prompt and is shown for illustration purposes only.
   • To avoid errors, for more complex commands, I recommended copying from this post to the terminal. All you need to do is 1) select the line in this window 2) hit command-c and then 3) hit command-v in terminal to paste it.
   • You DO need to type the period in front of each command. For example: the period here: ./adb devices is part of the command. It will not work without it. If you copy and paste lines, as I recommend, it is important to get the period during the selection.
   • Unless otherwise specified, you should never see an error after entering a command. If you did, double-check that you just entered the correct thing.
   • For the more curious, I will give you a complete rundown of what each command does in post #2.
   • Please do not PM me If something doesn't work right, please select, copy, and paste the last several lines of your terminal session into a new post in this thread.
   
   

Enter or copy/paste the following ./adb (without the $) lines into terminal:

$ cd ..
$ cd ..
$ cd and*
$ cd tools
$ ./adb devices

Terminal should return a result that displays your device (the name will vary from the one shown). If it doesn't show as attached, you will not be able to continue.

$ ./adb push su /data/local/su
$ ./adb push Superuser.apk /data/local/Superuser.apk
$ ./adb push GingerBreak /data/local/GingerBreak
$ ./adb push com.sh /data/local/com.sh
$ ./adb shell chmod 777 /data/local/su
$ ./adb shell chmod 777 /data/local/GingerBreak
$ ./adb shell chmod 777 /data/local/com.sh
$ ./adb shell

The adb shell command will not put you in the phones internal command terminal. This is represented with "$" prompt. You will now execute the GingerBreak exploit. This make take serveral minutes.

/data/local/GingerBreak

After entering the above command Gingerbreak will do its thing. A successful exploit will end with this,"[!] dance forever my only one"
If it ends in anything else or if it hangs for more than 5 minutes pull your battery and attempt to root again.
After exploit is complete you will have a command prompt that looks like this "#". That represents root access. You will now excute shell script then reboot your phone.

/data/local/com.sh
exit
exit
$ ./adb reboot

Your phone will now reboot. Congrats Enjoy your rooted device

check app drawer to see if superuser app is installed,if it is you are rooted

[DroidXcon]

Removing apps once rooted (Coming soon)

[DroidXcon]

Unroot batch file download:



How to Unroot

• Download Start_Unroot.zip
• UnzipStart_Unroot.zip folder Place anywhere on your computer
• Place your phone in debugging mode
• Connect phone to PC
• Open Start_Unroot folder Double Click Start_Unroot.bat

When the command window prompts you to enter adb shell , press any key to continue

To copy and paste into the command window, simply copy the command, then right click in the command window and a drop down menu will appear. Then select the option Paste

Then at the "$" prompt enter the following commands

su

After entering this command look at your phone screen right away Superuser app may ask you to allow or deny root permission , select allow . Once you receive "#" prompt you may proceed. if you get permission denied , pull your battery and try again

mount -o remount,rw -t rfs /dev/block/stl10 /system
rm /system/xbin/su
rm /system/bin/su
rm /system/bin/busybox
exit
exit

Your phone will now reboot
Once the phone restarts you must uninstall superuser app
settings>applications>manage applications>superuser

Once uninstalled Unroot is complete.

[DroidXcon]

• Android Central member imnuts for driver info
• for Gingerbreak exploit
• for posting original adb method

[DroidXcon]

Reserved for future methods1

[DroidXcon]

Reserved for future methods2

[sicario666]

Believe this or not... I DLd gingerbreak1.10 and used it to root a charge last night. After trying numerous times to root via ADB. Being denied access when attempting to gain permanent root. I figured why not try gingerbreak since the file was already located in the package zip. To my surprise it worked! For any1 looking for gingerbreak, Google it... I don't want to supply a link to upset anybody. Especially droidXcon. This is his thread,not mine. Follow whatever method tickles the pickle

TboltMeatclaws-talkatap

[poloboogie]

I'm not against it innfact I'm happy that it's starting but isn't it to early to be rooting without devs. Well rom manager still work and let us backup our rooted stock? What are the benefits this early?

[moondrius]

There is no recovery yet so rom manager is useless. I rooted so I could restore all my apps with titanium and use wireless tether if I ever need to. Its also nice for removing bloatware and blocking adds.

[DroidXcon]

Believe this or not... I DLd gingerbreak1.10 and used it to root a charge last night. After trying numerous times to root via ADB. Being denied access when attempting to gain permanent root. I figured why not try gingerbreak since the file was already located in the package zip. To my surprise it worked! For any1 looking for gingerbreak, Google it... I don't want to supply a link to upset anybody. Especially droidXcon. This is his thread,not mine. Follow whatever method tickles the pickle

TboltMeatclaws-talkatap

if you compare my adb method vs jcase's i added in adb chmod commands which changeds mode, chmod'ing a file changes what permissions it has. This is the reason you were getting permission denied, permissions were never set.

I didnt add the gingerbreak app yet because im working with someone to improve upon it.

thats why i left extra posts to add upon these methods.

I'm not against it innfact I'm happy that it's starting but isn't it to early to be rooting without devs. Well rom manager still work and let us backup our rooted stock? What are the benefits this early?

There is no recovery yet so rom manager is useless. I rooted so I could restore all my apps with titanium and use wireless tether if I ever need to. Its also nice for removing bloatware and blocking adds.

++1 on what moon says................also i don't like to sit around and wait for the devs to do all the work for me, if i did that i would never learn anything. Also its good for the devs to see that there is a demand for their talents. For instance when i see newer phones with people struggling to root i am compelled to jump in and do what i can to help. I imagine alot of devs feel the same way.

[davey11]

Don't forget even w/o recovery, you can now use root explorer, to move, delete, copy files. Can create custom sound events, change shutdown and boot animations, can extract apks from flash zips and install, among other things. Also have access to rooted only apps in the market.
I know that imnuts has a recovery ready to go.
Most important tho is we need VZW to RELEASE THE PHONE!!

[DroidXcon]

Semi Auto Root works but superuser app needs to be downloaded after root is run. I will improve on this soon

[imnuts]

If people have issues with this root method on ED2, can someone try rage.bin to see if that works?

[whitepearl86]

How long does it sit after the 1st command line using Semi auto root?

Thanks!

[DroidXcon]

How long does it sit after the 1st command line using Semi auto root?

Thanks!

usually like 3 mins to exploit on some phones it takes longer. if its around 10 mins and nothing, i would battery pull and try again

[whitepearl86]

usually like 3 mins to exploit on some phones it takes longer. if its around 10 mins and nothing, i would battery pull and try again

I am at 10 minutes now, sitting on the vold: 2383 GOT Start: 0x000162e8 GOT end: 0x00016328

already pulled better ones, this was 2nd attempt

[DroidXcon]

I am at 10 minutes now, sitting on the vold: 2383 GOT Start: 0x000162e8 GOT end: 0x00016328

already pulled better ones, this was 2nd attempt

Did you do the update today because that could be the problem.

[whitepearl86]

so trying thru the ADB. In both methods under list of devices attached , mine says *******408acc device

is that right?

[whitepearl86]

Did you do the update today because that could be the problem.

i bought the phone today and i am pretty sure they updated me in the store

[DroidXcon]

so trying thru the ADB. In both methods under list of devices attached , mine says *******408acc device

is that right?

lol i edited that for you , dont want people having your serial number if you can help it ..... yeah as long as you see a serial number it should be good, to make sure its not seenig another device try the adb devices with the phone not plugged in and you should see no number

[whitepearl86]

lol i edited that for you , dont want people having your serial number if you can help it ..... yeah as long as you see a serial number it should be good, to make sure its not seenig another device try the adb devices with the phone not plugged in and you should see no number

Thanks for the edit!

OK well i tried both methods and nothing, pulled battery 3 times now.

I restarted phone and laptop..trying one last time

I got detected Froyo then command lines and it hangs in the last command line being the vold