Unroot Motorola Droid?

[dudeitsmattx]

kinda of a dumb question, but once the new 2.0.1 is on the phone and u delete the update right from ur sdcard so its not taking up space since on the phone? thanks

[romeov]

i just dont see the whole need to have the phone rooted. besides being able to change file names so they dont run in the background of ur phone to save battery life. i mean what else can you do? i dont know how to hack into the system like these guys to change/fix things so idk lol..

You clearly don't understand what rooting is or why it's so amazing then. Wait till the completely custom roms for the phone come out that give you things like the full HTC sense UI (Eris clone) full and running on your Droid with tons of little fixes and all the best hacks built right in to make your phone the best of all android devices combined.

[coolkidd]

This is actually what I'm waiting for... custom ROMs!

[Dirge]

Hi everyone, I'm new to the forums! I just read the whole thread and have been wanting to root my Droid to customize it to my liking. I have but one question though: If I decide to unroot my Droid for whatever reason, is there any way to save all my apps on my sd card so they won't be lost when I return to my unrooted phone? Or will they remain untouched?

[mkloharry]

Alright, I have successfully unrooted my droid, and removed the Superuser App. Now starting off, I was still rooted when I did this. I began be fixing all of the changes I had done from the beginning such as changing the names of all of the apps I did not want to start (CorpCal, Email, etc). So after everything went from *.bak to *.apk, I simply just removed Superuser.apk While I'm not sure if there are any other files associated with this, I'm not sure, but that got rid of it for me. Now if you have already unrooted your droid, you will have to root it again to get rid of it.

Once you get it rooted, to remove Superuser.apk i entered the following into the terminal emulator

su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
rm Superuser.apk
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
sync
reboot

Now this worked for me, but i cannot assure it will do the same for you. Ill assume that I used the right commands because everything worked for me. After i removed Superuser.apk i then proceeded to unroot it by apply the 2.0.1 patch. After that I received Permission denied. A good sign for ones who want to unroot.

Let me know if there are any corrections/problems with my method

good write up.. i did everything you said to do on my phone and the Superuser app is gone. and after the 2.0.1 update i typed su in the terminal and it says Permission denied also.. nice

worked great for me thanks

[hondabomdc5]

ok so my droid is rooted, i did the manual update bc i was to impatient to wait for the OTA update. Well, i was wondering since my phone is rooted, will i recieve any future OTA updates? i know that there is supossed to be another update coming out in jan, so i was curious as to if i would recieve the OTA update, if not, then i was planning on unrootingmy phone if i can figure it out, after reading what everybody is saying, it gets kinda confusing. thanks and sorry for the noobness, im sure somebody will bash

[jeff.essy]

Did you find out how to get rid of the superuser permision icon?

Okay, so I re "updated" to 2.0.1, and it DID successfully un-root my droid, but the "Superuser Permissions" app is still in my applications menu. How can I get rid of that?

[Bear in NM]

ok so my droid is rooted, i did the manual update bc i was to impatient to wait for the OTA update. Well, i was wondering since my phone is rooted, will i recieve any future OTA updates? i know that there is supossed to be another update coming out in jan, so i was curious as to if i would recieve the OTA update, if not, then i was planning on unrootingmy phone if i can figure it out, after reading what everybody is saying, it gets kinda confusing. thanks and sorry for the noobness, im sure somebody will bash

Honda,

No bash, as the answer is not totally obvious. From what I have gathered, think of the root as a line in the sand with VZW and OTA's. The more "stuff" that you do to your rooted droid, the farther away from line you get, until the line is too far to see, or cross back over without risk.

There is a risk with rooting and still allowing OTA's, as no one knows definitvely what the real 2.1 is gonna do to phones in various states of "unfactoryness". The upside as was explained to me, and is sort of being confirmed by the 2.1 rom users/hackers/beta testers is that indeed there are folks who will get the updates earlier than VZW intends for them to be released, and get them working with everyone's help. perhaps a better anology would be a fork in the road, where you have to decide which road to take.

Craig

[jeff.essy]

i did that but when i type su in terminal eluminator and hit enter a screen pops up and asks to allow or deny root access.

[IEatCake]

This:

su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
rm Superuser.apk
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
sync
reboot

Should really be this:

su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
cd /system/app
rm Superuser.apk
mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system
sync
reboot

While the first one works, there is a whole write up on why you should be careful with the mtdblock3 vs 4... I didn't know this at first until I read a better explanation of it.