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

Root Rooting Froyo on DX

OMJ

Bazinga
Nov 27, 2009
3,289
825
Pennsylvania
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 Droid X.

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:\droidxroot
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:\droidxroot\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 rw,remount -t ext3 /dev/block/mmcblk1p21 /system
15.) exit
16.) adb push c:\droidxroot\Superuser.apk /system/app
17.) adb push c:\droidxroot\su /system/bin
18.) adb push c:\droidxroot\busybox /system/bin
19.) adb shell
20.) chmod 4755 /system/bin/su
21.) chmod 4755 /system/bin/busybox
22.) mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
23.) rm /data/local/tmp/rageagainstthecage-arm5.bin
24.) exit

I would suggest rebooting your phone but its not required.
 
I'd just like to add, don't get impatient at step 11.

It took me almost 5 minutes before my adb connection was reset. It was all smooth sailing from then on though.

yeah when I did it on my friends droid 2 I waited around 15 minutes and it never pushed back to the tools folder. the directions I'd found said this may happen and to exit out and I think it was to try to push the rage file again, I did that and it still didnt push me back to the tools folder but when I exited out and went to adb shell I had the # sign so it had worked for me. everything else went smooth as butter.
 
Upvote 0
I realize this thread is a little old, but has anybody done this on a mac...i started editing all the steps into the correct format for Terminal on a mac, but I get to a few points where I'm not sure and don't want to mess things up.

What i mean is instead of cd \c:\ on a PC...it's cd /users/username and so on...some things are back wards.


Also: the reason I'm doing this is because I'm already on 2.2 from the leak, I'd really like to gain root back as 1 click and Universal Androot are no longer the easy option.
 
Upvote 0
I realize this thread is a little old, but has anybody done this on a mac...i started editing all the steps into the correct format for Terminal on a mac, but I get to a few points where I'm not sure and don't want to mess things up.

What i mean is instead of cd \c:\ on a PC...it's cd /users/username and so on...some things are back wards.


Also: the reason I'm doing this is because I'm already on 2.2 from the leak, I'd really like to gain root back as 1 click and Universal Androot are no longer the easy option.



I would just put all of the files in Droid2Root.rar in the adb tools directory, then use the relative path when you're rooting.


eg:

adb push ./ageagainstthecage-arm5.bin /data/local/tmp



I'm using a mac too, so let me know if you have any other questions.
 
Upvote 0
yeah when I did it on my friends droid 2 I waited around 15 minutes and it never pushed back to the tools folder. the directions I'd found said this may happen and to exit out and I think it was to try to push the rage file again, I did that and it still didnt push me back to the tools folder but when I exited out and went to adb shell I had the # sign so it had worked for me. everything else went smooth as butter.


can someone tell me what he means by exiting out? and to try and push the rage file again. And exiting out again, "went to adb shell" where at?
 
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