[HACKS] Root Droid 1 - regardless of OS version

[MotoCache1]

I spend so much time answering questions that I don't often post to say "thanks" for all the positive feedback and comments. I'm glad this has been helpful to so many. I might be wrong, but if you are already on FRG22D, I think that my files/method are the only known way to get rooted without downgrading some part of your phone first. That's kinda cool.

[Edited to add: As of this morning (9/9) my method is no longer the only method. It was for awhile, but no longer. The guys at Droid Life published a tutorial on using the "rage against the cage" binary method to root FRG22D. I believe it is OS version specific, so it could possibly break in future versions, but then again, there may never be another release for the D1, so that may not be an issue. In any event, if you're having trouble with my method, head on over there and check out the alternative.]

 

[guidot]

I spend so much time answering questions that I don't often post to say "thanks" for all the positive feedback and comments. I'm glad this has been helpful to so many. I might be wrong, but if you are already on FRG22D, I think that my files/method are the only known way to get rooted without downgrading some part of your phone first. That's kinda cool.

Right now I think it is the only way.

Excellent work and great support.

I would sign up for DB but I already have it... :wink:

 

[jeffe65]

Moto - I already use DB as well; the only place I can't access it is at work, because of WebNanny - er, excuse me, "Web Marshal".

Thanks for you help; I'm assuming that since my su files are in the right directories, I'm ok for now. If we ever get another update I need that breaks root, I'll give your method a try. Now it's off to find out about backups, ROMs, etc...dancedroid

 

[MotoCache1]

Great post Jeffe65. I wouldn't bother "unrooting" - probably no need. Tell me the answers to the following (you can just use a numbered list that matches my numbered questions to your numbered answers) and I'll let you know if I see any issues and what I'd do.

1. Where is your Superuser.apk (likely /system/app or /data/app).
2. Where is your "su" (likely /system/bin or /system/xbin).
3. Where is your "busybox" (likely /system/bin or /system/xbin).
4. Where is your "mkdir" (likely /system/bin or /system/xbin).

They are in, respectively:

1. /system/app
2. /system/bin
3. /system/bin
4. /system/bin

Sorry - just now getting to this.

1. Your Superuser.apk is in the same place that my package puts it.
2. Your su is in the same place that my package puts it.
3. My package puts busybox in /system/xbin
4. My package puts the busybox symbolic links (of which "mkdir" is one) in /system/xbin as well.

So, if you re-rooted with my package today, the only "ill effect" is that you'd end up with your current copy of busybox and its symlinks in /system/bin and another in /system/xbin. Generally this wouldn't cause any issues, but if it were me I'd go back in and clean one of them out afterward just because that's how I am.

 

[jeffe65]

Sorry - just now getting to this.

1. Your Superuser.apk is in the same place that my package puts it.
2. Your su is in the same place that my package puts it.
3. My package puts busybox in /system/xbin
4. My package puts the busybox symbolic links (of which "mkdir" is one) in /system/xbin as well.

So, if you re-rooted with my package today, the only "ill effect" is that you'd end up with your current copy of busybox and its symlinks in /system/bin and another in /system/xbin. Generally this wouldn't cause any issues, but if it were me I'd go back in and clean one of them out afterward just because that's how I am.

Thanks for explaining that; I'm beginning to understand how this is set-up. My question is, does the location of busybox, symbolic links, etc. have any effect when I get into SPRecovery, ROMs, and other fun things? For now I'm just OC'd, and running a few other root-dependent apps, but I'd like to eventually get deeper into this.

I get the impression the "1-click" methods may or may not lend themselves to what you want to do with the phone down the road; it helps to understand more of what you're actually doing.

 

[MotoCache1]

Thanks for explaining that; I'm beginning to understand how this is set-up. My question is, does the location of busybox, symbolic links, etc. have any effect when I get into SPRecovery, ROMs, and other fun things?

Nope. No well behaved app should be trying to call busybox directly in a special location unless it is keeping its own copy (like Titanium Backup does). Anything that needs busybox should be "finding" it through the PATH. Incidentally, /system/bin appears before /system/xbin in the PATH ("echo $PATH" in a terminal window), so the version in /system/bin would be the one that would end up "prevailing".

I get the impression the "1-click" methods may or may not lend themselves to what you want to do with the phone down the road; it helps to understand more of what you're actually doing.

There is a certain bliss to ignorance, but I don't find it appealing.

 

[scmtech]

First of all wanted to say thanks works great and was super easy to follow. Now I have a question to unroot incase it would be needed what would be the easiest way to do this?
Again thanks for all the great work.

 

[MotoCache1]

First of all wanted to say thanks works great and was super easy to follow. Now I have a question to unroot incase it would be needed what would be the easiest way to do this?
Again thanks for all the great work.

That depends on why. What would come up that would require you to unroot? The term "unroot" by itself means too many things to different people.

 

[adambomb777]

Worked great on both phones upgraded to frg22. It is good to have root back. Only problem I had was copying the file to root on phone. I was looking for a certain file to put it in. I didn't think it would be as easy as copying to sd card and renaming. Great write up!

 

[lurker_hlb3]

I have two questions

1. The PC system I will be using has XP pro on it , but the USB interface is 1.1 vice 2.0, will this have an effect when using RSD Lite?

2. What is the approximate amount of time between selecting "start" on RSD Lite and the reboot of the driod. Also what is the approximate of this after the droid reboots to "PASS" on RSD Lite?

 

[scmtech]

First of all wanted to say thanks works great and was super easy to follow. Now I have a question to unroot incase it would be needed what would be the easiest way to do this?
Again thanks for all the great work.

That depends on why. What would come up that would require you to unroot? The term "unroot" by itself means too many things to different people.

Well to remove the su. if for some reason i would need to take it back to verizon. But I now think I can answer my own question. I could always use the FRG01B.sbf then install the frg22.zip file. And again I think I am one of those people that just want to know that they can do something if they want to do it.

 

[jr4000watts]

i cant seem to figure this out ive been trying since last night and nothing maybe you guys could help, i read and re read the detailed steps but can seem to get it to root. i am running frg22d.

1. downloaded everything needed, 32 bit moto drivers, RSD lite, the complete root file,SPRecovery SBF for the Droid 1.
2. i have renamed the Complete root file to "update.zip" and even tried just "update"

i can get into the SPRecovery but when i apply the update i get this.

(complete text whats on the error)
--Install from SD card...
Finding update package
E:Can't mount /dev/block/mmcblk0p1(or /dev/block/mmcblk0
(no such file or directory)
E:Can't mount SDCARD:Update.zip
Installation Aborted

 

[Abe21599]

i cant seem to figure this out ive been trying since last night and nothing maybe you guys could help, i read and re read the detailed steps but can seem to get it to root. i am running frg22d.

1. downloaded everything needed, 32 bit moto drivers, RSD lite, the complete root file,SPRecovery SBF for the Droid 1.
2. i have renamed the Complete root file to "update.zip" and even tried just "update"

i can get into the SPRecovery but when i apply the update i get this.

(complete text whats on the error)
--Install from SD card...
Finding update package
E:Can't mount /dev/block/mmcblk0p1(or /dev/block/mmcblk0
(no such file or directory)
E:Can't mount SDCARD:Update.zip
Installation Aborted

battery pull doesnt fix it?

 

[jr4000watts]

So when i get the error message do i pull the Battery then redo the process? sorry im learning and new to this.

 

[Abe21599]

So when i get the error message do i pull the Battery then redo the process? sorry im learning and new to this.

well just when it happens pull the battery, turn it back on, and try the update again. worked for me when i had that error