• 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

icecold said:
With my phone being on FRG83D, I opted to root with SuperOneClick on Friday, and I played around with the options root gave me (overclock, wifi tethering, etc), but I smashed my phone's display on saturday morning. So, after waiting so long to take the plunge, I have to revert back to stock before I send it in.

Now, I know that SuperOneClick has an unroot option, but in case that doesn't work, I'm curious as to the best way to revert back to stock.

I saw the link above on how to do this, but this is using RSDLite. Being this is how to root without RSD Lite, I thought I would see something a little more specific.

I have also seen the option of flashing an Unrooted stock option via Rom Manager, but this (from what I have read) has had mixed results. Could I just use the same method of manually updating to FG83D, flashing the update.zip file?

Any help would be appreciated. Thanks in advance.
Click to expand...

As far as I know, the only proven way to unroot is to flash an sbf with rsd...

Kratos
 
kratos said:
It's good that you had success with this. I have talked to a couple people who try to unroot using that rom and had some problems.

Kratos
Click to expand...


The biggest problem I have heard is that the unrooted stock ROM does not removed the superuser icon from the app drawer though it unroots it. I guess you would just need to remove the superuser.apk before installing the ROM (though I don't know if that would interfere with ROM Manager working.).
 
skilaufen said:
The biggest problem I have heard is that the unrooted stock ROM does not removed the superuser icon from the app drawer though it unroots it. I guess you would just need to remove the superuser.apk before installing the ROM (though I don't know if that would interfere with ROM Manager working.).
Click to expand...

Funny thing is it removed super user icon off my Droid.
 
Dark Jedi said:
Funny thing is it removed super user icon off my Droid.
Click to expand...

Cool.:cool: I wonder if it depends on where it is located in the ROM or what version it is. Chainsdd has updated it several times since the origninal ninja icon. The superuser icon not being removed is the biggest issue I have read about. Thankfully I have not had to return my phone to stock (and I am hoping to never have to).
 
I have no clue. I am as dumb as the day is long when it comes to these phones and what you can do with them. I am shocked I can root them lol.
 
kratos said:
As far as I know, the only proven way to unroot is to flash an sbf with rsd...

Kratos
Click to expand...

Thanks for the info. I only have a work laptop with power user access (damn IT Nazis), so lining up a computer to do this work is kind of a pain.

I will attempt to use the unroot option using SuperOneClick, version 1.6.5. If that doesn't work, I'll try the ROM Manager option. Again, if that fails to return everything to stock, I will go the RSD route.

I'll post my results for others to use as they may...
 
One of the issues I've heard about with using rom manager is that it doesn't remove all traces of root. Other than that and rsd, I don't know of any other way to unroot. Hopefully the super one click method work properly.

Kratos
 
I actually haven't heard a lot of positive for either one of the options (SuperOneClick or ROM Manager), but I figure I will give them both an chance. Worst case scenario (I think) will be that I have to re-root.

It will give me the opportunity to go through the long method of rooting anyways, since I plan on setting up both ADB and RSD Lite before I start.

Again, thanks for the help.
 
kratos said:
One of the issues I've heard about with using rom manager is that it doesn't remove all traces of root. Other than that and rsd, I don't know of any other way to unroot. Hopefully the super one click method work properly.

Kratos
Click to expand...

Unrooting with stuff like Super One Click will in fact unroot you for sure, but it only removes superuser.apk su binary and maybe busybox. It wont revert any changes youve made to /system.

Basically I am saying yes it will unroot you, but no it will not revert you to stock.
 
OMJ said:
Unrooting with stuff like Super One Click will in fact unroot you for sure, but it only removes superuser.apk su binary and maybe busybox. It wont revert any changes youve made to /system.

Basically I am saying yes it will unroot you, but no it will not revert you to stock.
Click to expand...

So, I guess thats what people mean when they say out doesn't remove all traces of root. Since the edits to /system would still be present. It sounds like the most thorough method is to flash an sbf with rsd lite.

Thanks for the info.

Kratos
 
OMJ said:
Unrooting with stuff like Super One Click will in fact unroot you for sure, but it only removes superuser.apk su binary and maybe busybox. It wont revert any changes youve made to /system.

Basically I am saying yes it will unroot you, but no it will not revert you to stock.
Click to expand...

I ended up "biting the bullet" and just using the RSD Lite method to revert back to stock. Thanks for the explanation. It wasn't nearly as bad as I thought it would be. I had the old one back to stock and the replacement phone rooted in about 30 minutes.

Then the owner of the computer I was using had me root and install voodoo on his Samsung Mesmerize...now that was a pain in the ass!
 
TBH, if you're worried about anyone finding out if you have been rooted or not, you're probably better off just using RSDLite and flashing a stock SBF.

Any other way may leave you chasing down ghosts and whatnot, as OMJ mentioned.
 
I'm Rooting this phone for a friend.

When I got to step 14 "14.) mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system"

I got a message "mount: Operation not permitted"

I rebooted the phone, thnking this may solve the issue...

Now I can't get the OS to load, all I get is a screen showing the following

Bootloader
2C.7C

Battery OK
OK to Program
Transfer Mode:
USB


When I "adb devices", I get nothing under the "List of Devices Attached".

Did I just brick his phone?
Hope not...

Thanks.


Edit:
Solved.
Holy CRAP that was freaking me out.
Found that the dpad was stuck upwards. Rouged up the keyboard a little and rebooted while open, booted right back up.

Sigh of releif.

Anybody know why the mount wasn't working?

btw I started out with a $ prompt in the ADB shell, not #.... was this phone already rooted??

Thanks.


***EDIT #2***
Restarted from #1 and I'm now rooted.
Now on to flashing CM6.1.2!!!

So Geeked right now!
 
Well, glad you got it all figured out, but I just had to add this little personal motto of mine:

Friends don't let friends hack/root their friend's phones.

good luck
 
Thank you for this set of instructions. Very easy to understand and simple to do. Every single problem I encountered was user error from mistyping a command. Absolutely flawless execution. I am tickled with my now rooted Droid. Already installed Clockwork to back up the ROM. Added overclocking and boy does going to 1Ghz make a difference. Now backing up all apps with Titanium. Couldn't have done it as easily with other instruction. Outstanding job. You are now my first choice for instructions on modding my Droid as well as my top recommendation.
 
My $ won't turn into a #
What am I doing wrong?
I ran through the process once and it worked but my phone did not root and when I tried again the $ won't change to a #
 
I have tried this method about 10 times over the past 2 days on my Droid X. I get past step 11 and then when I do step 12 my device does not show up. I have usb debugging enabled and I have it in charge only mode as PC mode will not bring up usb debugging. Can anyone help me with this?
 
Wrink30 said:
I have tried this method about 10 times over the past 2 days on my Droid X. I get past step 11 and then when I do step 12 my device does not show up. I have usb debugging enabled and I have it in charge only mode as PC mode will not bring up usb debugging. Can anyone help me with this?
Click to expand...

Welcome to the forums,

One of the reasons you may be having a problem is this is the Droid 1 forum. I don't know if this method works on the X. You might want to check out the below link for the Droid X.

Droid X - All Things Root - Android Forums
 
skilaufen said:
Welcome to the forums,

One of the reasons you may be having a problem is this is the Droid 1 forum. I don't know if this method works on the X. You might want to check out the below link for the Droid X.

Droid X - All Things Root - Android Forums
Click to expand...
+1 ^^^ this. There is a variation of this method that works on the X, but I've also heard that z4root works on the Droid 2 and the Droid X. If you can't find it in the market, I have it.

good luck
 
First off let me say thank you to OMJ for posting this thread. I have rooted twice using this method.
UnROOTING is the tricky part. I am the weirdo that wants OTA updates, then wants root back. Im about to reroot after updating to 2.2.2 verizon OTA. I unrooted with no trace of root and all the stock apps returned using a full stock zip of the ota. I used clockwork to open it and it seemed to brick my phone. Fortunately i somehow got it to load the update.zip i have of 2.2.2 . So now that i have the update i have a ? or request.. is it possible to add something to the typed commands to make a folder that keeps the unaltered files before the "push" (i presume linux' way of saying overwrite?") Or can i just skip that step and deny ota updates? I really just want a failsafe to get back to stock without rsdlite or anything else aside from typing dos commands. I obviously
am not super programming literate, but it seems so simple to root this way.
Unrooting should be this straightforward.
EDIT:: I just reread the steps and step22 disables stock recovery right? I had tried several smaller (30mb or so) stock update.zips and had them not work. The full 70mb or so were the only ones that worked. If step 22 is reversable (i.e. same line but typing "enable" versus "disable" would it make using tbe smaller stock recovery images easier.

.EDIT: Having just re read the steps i still dont know how the hell i got that to work. I did use a 77mb update.zip, so maybe the recovery is reinstalled with that. Idk. Im learning...before i root again i had to ask if there can be an easier way.

*** To the people that got the weird bootload screen i.e. usb ok power ok...
I got that hitting the arrow the wrong way. Nearly shat myself pulled the batt and tried again.

****To those wanting to unroot:this may work, it may not, it may seriously fu$# up your phone (i dont have warranty to worry about thankfully theres ebay) i unrooted by loading a full (70 mb ot so) new verizon update.zip files both times. It failed to unroot with smaller 30mb or so ons (ota)Both times i dwnlded them on droid sites In the recovery stock or clockwork (had clockwork the 2nd time but not the first) i ran that update.zip till it worked. Maybe thats a no no, but it worked for me. No superuser, no remnant except on sd card where i made a folder called droidshit to save the files from here. Busybox & SU.
 
You must log in or register to reply here.
Back
Top Bottom