• 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

Well, you have found the way to unroot without RSD Lite, it is pretty much what I have here:

Unroot your Droid WITHOUT RSD Lite

As far as step 22, what that does is rename (via a move "mv" command) the script file that will check and make sure you have stock recovery on every boot, thus disabling it. Enabling it would be to rename it back to the original, not changing the new extension to enable.

Now as far as unrooting with a few commands, well that could get tricky. As you know, the file that gives us root is the 'su' binary with the corresponding setting of it's permissions to 6755 (or 4755 in this guide). We now have unfettered root access. When we put the Superuser.apk file in /system/app it's function is to check each time an app calls for 'su' and then prompts us if we want to allow it or not. Without Superuser.apk any app could request 'su' and we'd never know. The busybox binary adds more shortcuts/commands to our system which many if not most root apps rely upon being in place to function.

So with all that in mind, in _theory_ you _might_ be able to unroot via these commands (DO NOT TRY THIS!!):

Code:
su
mount -o remount,rw /dev/nul /system
rm /system/bin/busybox
rm /system/app/Superuser.apk
rm /system/bin/su
reboot

However I am sure the second to last command would fail since you are using the 'su' binary and I doubt it would be allowed to be deleted while in use. AND THIS WOULD LEAVE YOUR PHONE OPEN TO ANY APP TO CALL SU WITHOUT YOUR KNOWLEDGE.
 
So - I think I've seen a couple of posts here that you have been able to use this method even after you have gotten the 83G OTA update. Have I read that right?

Cause I think I'm ready to take the plunge if it will work.
 
Well, you have found the way to unroot without RSD Lite, it is pretty much what I have here:

Unroot your Droid WITHOUT RSD Lite


thank you. I just wanted a confirmation that it, in fact should work again.
I'm about to root the new update so
VVVVV
Ill post back here when im done. But yes, a couple of people have said they rooted frg83g
So - I think I've seen a couple of posts here that you have been able to use this method even after you have gotten the 83G OTA update. Have I read that right?

Cause I think I'm ready to take the plunge if it will work.
 
Thanks I just used this to root my frg22. So I'm ready to start doing some ROMs which I'll read up on but I just have 1 question to make sure I understand. Since I did not backup anything before rooting, a backup that I make now (I'll be sure to make before doing any ROMs) will be a backup of my rooted phone, correct? Doesn't seem to be a big deal, but just want to make sure I understand.

Also, if I did ever want to get back to frg22 not rooted, would that be possible?

OMJ's response
absolutely....you can either use an sbf file or flashingthis http://android.clie a5e329b00288.signed-voles-ota-50454.zip like you would a rom there is no way to make a backup of your system before its rooted...
I still use the file that I downloaded from this link to return to stock. Once reactivate my phone I am prompted to do the OTA updates until my phone is current.

OMJ, do you still have this file or a new file (update.zip)) to revert you to stock? It would seem that this is a lot simpler than how people are trying to go back to stock. I don't know how to post the update.zip file myself.

Update: Okay, Teddy I see your link on your page with the frg83g ota update.zip. guess I'll use that the next time I need to un-root. And I appologize Teddy, I saw all the talk about using commands to un-root and didn't follow your link with detailed directions on how to flash an update.zip

www.peteralfonso.com/p/downloads.html
 
I was just pushed the FRG83G update and have confirmed that this method works for rooting it also on my Droid 1. Awesome! :D

Same here. It works great!! I am one of those people who un-rooted in order to get FRG83G. I got sick of problems with custom ROMs so I guess I have to go through this every time there is an update.

I am going to try the latest release from Pete Alfonso for Gingerbread though. It's intriguing!
 
Same here. It works great!! I am one of those people who un-rooted in order to get FRG83G. I got sick of problems with custom ROMs so I guess I have to go through this every time there is an update.

I am going to try the latest release from Pete Alfonso for Gingerbread though. It's intriguing!

If you really like the 'stock' layout but want to have a faster phone, then Pete's is clearly the way to go. His Gingerbread runs like a champ on the Droid, and it's kept me from buying a Thunderbolt- I can wait for the Bionic and it's tegra2 processor now. I might just have to abandon the Droid in favor of some dual-core love when it finally drops, though.
 
Same here. It works great!! I am one of those people who un-rooted in order to get FRG83G. I got sick of problems with custom ROMs so I guess I have to go through this every time there is an update.

I am going to try the latest release from Pete Alfonso for Gingerbread though. It's intriguing!


I unrooted using the over the air update, installed Pete Alfonsos gpa 14,
and installed his custom kernels. i started with the 1G kernel and have been trying all the others. it all works flawlessly. Pete Alfonso is a perfectionist genius. WORKS PERFECTLY ON FRG83G
 
I'm on step 13. Instructions say "you should now see a # instead of a $", but I am still seeing the $. Should I continue anyway? Any suggestions would be appreciated.
 
UPDATE: I'm on step 11 now and it doesn't seem to be doing anything. As soon as I hit enter it returns me to a "$" prompt. When I type in adb devices it tells me permission denied. Where do I go from here?
 
antivirus reports the mediafire link to rage is infected, is there a different link to download or is this a false message?
 
antivirus reports the mediafire link to rage is infected, is there a different link to download or is this a false message?

Welcome to the forums,

rageagainstthecage will set off some virus scanners as it uses an exploit to get root. The difference is the exploit is intentional as is your use of it. As long as you trust the source you download from you should be fine.

My desktop computer's virus scanner also considers it a virus when I run a scan.
 
i just have to say that this was the easiest root walk through i found for droids on 2.2. one of the best things about it is that i dont have to install a rooted ROM for it to work. i did have some issues with the command to disable the recovery, but im not worried in the least not wanting to install custom ROMs or kernels anyway. i just wanted a simple stock OS root. Thank you thank you thank you for being great.

P.S. i registered just so i could post to this thread.
you sir will have my gratitude for a very long time.

Teabling
 
i just have to say that this was the easiest root walk through i found for droids on 2.2. one of the best things about it is that i dont have to install a rooted ROM for it to work. i did have some issues with the command to disable the recovery, but im not worried in the least not wanting to install custom ROMs or kernels anyway. i just wanted a simple stock OS root. Thank you thank you thank you for being great.

P.S. i registered just so i could post to this thread.
you sir will have my gratitude for a very long time.

Teabling

Welcome to the forums and glad everything worked well for ya.
 
Hey, will this work on the original droid? I got up to about step 12 or so, and now my device doesn't come up when I enter "adb devices". I've double checked, and I do have the android folder, then the tools folder selected. I'm not sure what happened.
 
Hey, will this work on the original droid? I got up to about step 12 or so, and now my device doesn't come up when I enter "adb devices". I've double checked, and I do have the android folder, then the tools folder selected. I'm not sure what happened.

This is for the Original Droid.
 
UPDATE: I'm on step 11 now and it doesn't seem to be doing anything. As soon as I hit enter it returns me to a "$" prompt. When I type in adb devices it tells me permission denied. Where do I go from here?

Any help on this? I'm hitting the same road block.
 
Will this process work for 2.2.2 build FRG83G ? Hoping to root my phone with in the next 30mins. Thanks

Edit: Got everything worked out and it appears to have worked
 
Will this process work for 2.2.2 build FRG83G ? Hoping to root my phone with in the next 30mins. Thanks

Edit: Got everything worked out and it appears to have worked

For anyone else wondering about the same thing, this method does work the the most current 2.2.2 FRG83G version of Android.

Ajak- Glad to hear you got everything worked out and are not rooted! If you need any help or suggestions, let us know. We are here to help!

Kratos
 
UPDATE: I'm on step 11 now and it doesn't seem to be doing anything. As soon as I hit enter it returns me to a "$" prompt. When I type in adb devices it tells me permission denied. Where do I go from here?

Same here. I took the liberty of running ls -l and got this:

Code:
ls -l
-rwxr-xr-x shell    shell        5392 2011-08-16 23:30 rageagainstth
in
-rw-rw-rw- shell    shell      115962 1970-01-16 17:36 PdaNet.apk

Which seems to be right, I think? I think that corresponds to 0755. But anyway, I exited and ran adb shell again, and I still get $ instead of #


EDIT: Actually I think I figured it out. If you are having this problem, make EXTRA SURE you ran step 11, that is the part that runs the script that actually gives you root access! Don't know how I missed it, but check again.
 
EDIT: Actually I think I figured it out. If you are having this problem, make EXTRA SURE you ran step 11, that is the part that runs the script that actually gives you root access! Don't know how I missed it, but check again.
Brilliant deduction Watson! Yes, if step 11 is not allowed to finish properly, everything else is moot; you must run it again.
 
I'm having trouble downloading rageagainstthecage. I've tried with Firefox, Chrome and IE and I get error messages each time.

EDIT: Never mind, had to disable my antivirus software.
 
Back
Top Bottom