This was a guide made by Darkonion on xda for the droid 2.
Very Important: Make sure you copy the commands exactly, the exact amount of spaces and ensure you have the everything exact or it will not go through.
***NOTE: Proceed at your own risk. I and the providers of this code are not responsible for anything you do to your phone!***
Setup:
- Install adb (
here) and Samsung drivers for windows
[Installed and did an update for ADB. ADB comes in a .rar file. I extracted it to C:\, ran the set-up file, and had it update. Folder for adb by default was “android-sdk-windows.” I had drivers installed earlier for Motorola when I was setting up EasyTether. They are newer drivers than the link listed above. Didn't need to install them.]
- Download attached archive: see rootzwiki
- Extract to a directory, I used c:\fascinateRoot
[There should be four files. It is easier if you extract these 4 files to the “tools” folder in your adb/sdk folder that you just extracted to C:\. In other words, extract the 4 files to
c:\android-sdk-windows\tools]
- Make sure you have USB degugging enabled
[This is under Settings->Applications->Development, check USB debugging]
- Change connection to PC Mode
[When you plug your phone into your computer with USB, there should be a notice in the “window blind.” Select the USB connection detected and choose PC Mode. Phone should disconnect from the computer and reconnect again.]
Process:
- Open command prompt
[Start Menu->Run->cmd.exe]
-
cd c:/wherever-your-sdk-tools-folder-is
[ex.
cd c:/android-sdk-windows/tools
Your command line prompt should now say something like:
C:\android-sdk-windows\tools>]
-
adb devices (to verify the connection)
[You should see a device listed.]
[Skip this line]- cd c:/fascinateRoot
[These next 4 steps, after entering each one, you'll see an amount of data transferred.]
- -
cd c:/fascinateRoot
- adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
- adb shell
[The command line should now start with a “$” instead of c:\]
<('.'<) [Ignore Kirby]
- cd data/local/tmp
<('.'<) [Ignore Kirby]
[after typing in this next command, it won't really say anything, it'll just spit back out your command. This is normal.
ex.
$ cd data/local/tmp
cd data/local/tm
- chmod 0755 rageagainstthecage-arm5.bin
<('.'<) [Ignore Kirby]
- ./rageagainstthecage-arm5.bin
[Type this exactly like it is.]
<('.'<) [Ignore Kirby]
- let the process run until it 'kicks' you out (may take a minute or two)
[This actually took me awhile before the program kicked me out. Go do something productive for 5 minutes then come back. I actually washed dishes and cleaned up my room while I waited. You'll know when it is done when you it'll kick you back to the DOS command. It'll look something like this:
c:\android-sdk-windows\tools>
- adb devices (to verify the connection)
-
adb shell
[The command line should now start with a "#" instead of c:\]
<('.'<) [Ignore Kirby]
(you should now have a # prompt, if not return to ./rage step above)
-
exit
cd c:/fascinateRoot
- adb push Superuser.apk /system/app/Superuser.apk
- adb push su /system/bin/su
- adb push busybox /system/bin/busybox
- adb shell
[All these next steps, make sure you type them as is here. The command line prompt is now # like stated in the step above. The commands will act like the “$” commands above where you enter it, and it'll spit you the command back out.]
- chmod 4755 /system/bin/su
- chmod 4755 /system/bin/busybox
- exit