• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Rooting the Droid without rsd lite up to and including FRG83D

OMJ

Bazinga
Nov 27, 2009
3,289
825
Pennsylvania
This works for rooting all the stock builds released for droid so far....up to FRG83D

I started a new thread about this because its a very different method than the one use in this thread and I didnt want the methods to be confused. This method is safer imo as it does not require flashing sbf files.

This method was originally used to root the Droid2

First off All credit goes to Sebastian Krahmer at C skills. Please see fit to donate via Paypal to 7-4-3-C@web.de

Credit for the tutorial goes to karnovaran at xda. You can find his original thread here. I have changed the directions a little to make them slightly easier and suited for the Droid1.

Whats needed
ADB for instructions on setting up adb see this video by unlockr
Current Motorola Drivers
Rageagainstthecage

1.) Enable usb debugging if you dont already have it enabled
Go to settings on your phone
then applications
then development
check the box for usb debugging[/Hide]
2.) Extract rageagainstthecage.zip to c:\droidroot
3.) Connect your phone to the computer via usb cable
4.) on the computer open the command prompt. (In the start menu under accessories)
5.) cd to your adb tools directory. For most the command would look like this cd C:\android-sdk-windows\tools
6.) adb devices (This should list a device as a long number under list of devices. If it doesnt something is wrong.)
7.) adb push c:\droidroot\rageagainstthecage-arm5.bin /data/local/tmp
8.) adb shell
9.) cd /data/local/tmp
10.) chmod 0755 rageagainstthecage-arm5.bin
11.) ./rageagainstthecage-arm5.bin (This can take a minutes just let it go until you are returned to your adb tools folder)
12.) adb devices
13.) adb shell (you should now see a # instead of a $)
14.) mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
15.) exit
16.) adb push c:\droidroot\Superuser.apk /system/app
17.) adb push c:\droidroot\su /system/bin
18.) adb push c:\droidroot\busybox /system/bin
19.) adb shell
20.) chmod 4755 /system/bin/su
21.) chmod 4755 /system/bin/busybox
22.) mv /system/recovery-from-boot.p /system/recovery-from-boot.p.disabled Note if you are on a build earlier than froyo this step will fail. That is fine and expected.
23.) mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system
24.) rm /data/local/tmp/rageagainstthecage-arm5.bin
25.) exit

I would suggest rebooting your phone but its not required.
 
thanks worked like a charm! can I go installing custom roms for them now? or is this simply root access.

you can flash custom roms although there is 1 annoyance right now, if you put a custom recovery on reboot before flashing a rom the stock recovery will come back. I meant to add the fix for it into the guide but forgot. Give me like 5 minutes to make sure this works and then I will tell you how to do it. Its real simple
 
Upvote 0
Great work OMJ :)

I can't find you're original thread, but maybe you should also put the steps to disable the "flash stock recovery" scripts? Not sure if possible in the adb shell, but I think the easiest would be something like mv /system/recovery-from-boot.p /system/recovery-from-boot.disabled

edit: never mind just saw your post :)
 
  • Like
Reactions: OMJ
Upvote 0
Great work OMJ :)

I can't find you're original thread, but maybe you should also put the steps to disable the "flash stock recovery" scripts? Not sure if possible in the adb shell, but I think the easiest would be something like mv /system/recovery-from-boot.p /system/recovery-from-boot.disabled

edit: never mind just saw your post :)

thats the exact command I am using. Just had to try it on my own phone first
 
Upvote 0
ok for anyone who used this guide before 225pm eastern time on sept 8 2010 do the following


Hook you phone back up to usb.
open command prompt and cd to you adb tools folder
Then type the following commands
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mv /system/recovery-from-boot.p /system/recovery-from-boot.p.disabled
mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system
exit


that just makes it so you can flash custom recoveries anyone doing this guide after the specified time its already part of the guide.
 
Upvote 0
ok for anyone who used this guide before 225pm eastern time on sept 8 2010 do the following


Hook you phone back up to usb.
open command prompt and cd to you adb tools folder
Then type the following commands
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mv /system/recovery-from-boot.p /system/recovery-from-boot.p.disabled
mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system
exit


that just makes it so you can flash custom recoveries anyone doing this guide after the specified time its already part of the guide.


Is there a way in SDB terminal to verify that the following took effect? When I ran the original commands, I got an error on the recovery-from-boot.p.disabled line that said file or directory not found??

Thanks
 
Upvote 0
Is there a way in SDB terminal to verify that the following took effect? When I ran the original commands, I got an error on the recovery-from-boot.p.disabled line that said file or directory not found??

Thanks

flash a custom recovery then boot into recovery. Then reboot into the os and then reboot into recovery a second time. If its still the custom recovery the second time then it worked. If its back to stock recovery the second time then something is wrong.
 
  • Like
Reactions: stephejo
Upvote 0
Procedures seem to work fine. For those of us using windows XP, the file in step 5 is located at c:\AndroidSDK\tools I had previously rooted using Easyroot and ROM Manager, but kept the stock FRG01D. When I upgraded to FRG22D thru a thread on this forum, I unfortunately did not know enough to investigate the possibility of losing root........ which I did after this upgrade. Having re-rooted using the thread above, will my rom and rooting applications be usable?
 
Upvote 0
Watch the spaces before the forward slashes in the commands........ they are hard to spot. I had the same problem initially.

I don't have an issue with spaces, I am somewhat of an advanced DOS user from the days before Windows. I know about entering commands via the cmd window.

When I PUSH rageagainstthecage, it doesn't copy. When I do superuser and su I get an error message stating failed to copy: read-only file system
 
Upvote 0
I don't have an issue with spaces, I am somewhat of an advanced DOS user from the days before Windows. I know about entering commands via the cmd window.

When I PUSH rageagainstthecage, it doesn't copy. When I do superuser and su I get an error message stating failed to copy: read-only file system

without rageagainstthecage you wont be able to push the other files. Are you sure rageagainstthecage isnt pushing? what happens when you try steps 10 and 11?
 
Upvote 0
without rageagainstthecage you wont be able to push the other files. Are you sure rageagainstthecage isnt pushing? what happens when you try steps 10 and 11?

I am not sure what is going on, but after through the steps multiple times, it finally started to work. Originally when I got to steps 10 and 11, I got an error, when I went through it again (to relate the error message here), everything worked.

Looks like I now have a rooted phone. Thanks.
 
Upvote 0
I am not sure what is going on, but after through the steps multiple times, it finally started to work. Originally when I got to steps 10 and 11, I got an error, when I went through it again (to relate the error message here), everything worked.

Looks like I now have a rooted phone. Thanks.

no problem glad you got it figured out
 
Upvote 0
Wow! Unhappily, I lost root when Verizon pushed FRG22D to my phone. Your rooting method is straightforward and easy as pie. Mega thanks! It's a relief to be rooted again. No, I'm not constantly swapping ROMs and themes and stuff, but I really appreciate the extra security of running Backup Pro with superuser permissions and having full access to Titanium Backup. Bravo!

I'm curious, though: why do you think this method is safer than using SPrecovery, spf lite, and flashing sbf files? I've never followed that route, and perhaps the straightforwardness of the method you detail in this thread answers my question. But I was wondering what you meant by that?
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones