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

Root help! I cant unroot

magic1,

In post #1 where you said you tried the PB00IMG.zip file, which PB00IMG.zip was it (base root ROM, leak v1 or v2 or v3)?

I don't know if we ever clarified this (or if it really matters?). I know that some folks couldn't use the base root ROM PB00IMG.zip due to the "main version is older" error, but I don't know that I saw it happening with one of the 2.1 leaks (not sure anyone has tried this).

So, midnight assassin might be on the right track...easy to try (depending on your answer, that is...).
 
can't you unroot just by flashing one of the leaks?

The "Official"RUU produces exactly the same result as the Leak-V3 PB00IMG.zip. (In fact, the "rom.zip" file contained within the "Official" RUU is identical to the Leak-V3 PB00IMG.zip)

Whether or not someone experiences the "Main Version is older" message depends on the history of the phone in question, but the result will be the same whether the HBOOT or RUU installation method is used.


Having said that, magic1 should be using either the leak-V3 ROM or the "Official" RUU - and performing the jcase "Flash any RUU" method first if the experience "Main Version is Older" messages.

eu1
 
The "Official"RUU produces exactly the same result as the Leak-V3 PB00IMG.zip. (In fact, the "rom.zip" file contained within the "Official" RUU is identical to the Leak-V3 PB00IMG.zip)

Whether or not someone experiences the "Main Version is older" message depends on the history of the phone in question, but the result will be the same whether the HBOOT or RUU installation method is used.

Having said that, magic1 should be using either the leak-V3 ROM or the "Official" RUU - and performing the case "Flash any RUU" method first if the experience "Main Version is Older" messages.

eu1

Thank you (again), eu1.

magic1,

You can get the the leak-v3 ROM here:

http://androidforums.com/htc-droid-eris/69688-htc-droid-eris-os-2-1v3-download.html

(which I gleaned from this post of erisuser1's: http://androidforums.com/eris-all-t...re-stock-bootloader-recovery.html#post1363157).
 
Thank you (again), eu1.

magic1,

You can get the the leak-v3 ROM here:

http://androidforums.com/htc-droid-eris/69688-htc-droid-eris-os-2-1v3-download.html

(which I gleaned from this post of erisuser1's: http://androidforums.com/eris-all-t...re-stock-bootloader-recovery.html#post1363157).

As a matter of fact i saw that thread and was planning on following it once i get back in town. I've just been searching thru all of these posts trying to collect an arsenal of plans to put in place when the time comes;)
 
Did you make the Nandroid backup before you flashed rootme.zip? The rootme.zip update-type file is what put the su program and SuperUser app on your phone.

If you saved the Nandroid backup before the rootme.zip flash, then you should be able to simply restore that backup. Then, the only trace of rooting left on your phone would be the custom recovery partition.

If you did the Nandroid backup after you flashed rootme.zip, then you'll have to nuke the parts individually (easiest via Root Explorer, or EStrongs (I think this will let you), or you could do it manually via a Terminal Emulator or from the SDK's adb utility. I can find and point you to some threads that discuss (I'm a little slammed today so I can't do any detailed digging at the moment, but I can look for them tonight--unless another very helpful member replies to you first :D).

Don't forget to remove any other root-only apps you might have (drocap2, wi-fi tethering, etc.).

Cheers!

You know, I got to thinking. I'm not trying to unroot my phone because I don't like root, I'm just trying to "fool" someone onto thinking the phone is stock. So I downloaded and flashed ivans official 2.1 with root access and voila it looks almost identical to stock minus superuser permissions, wireless and wired tethering for root users. It even shoes the option to check for system updates although it fc when you try to open it. What all should I uninstall and delete to make it look "totally stock" ? I was able to delete both tether apps using titanium backup but I guess ill have to buy root explorer to get rid of superuser permissions ( unless somebody can tell me another way ).:D
 
You know, I got to thinking. I'm not trying to unroot my phone because I don't like root, I'm just trying to "fool" someone onto thinking the phone is stock. So I downloaded and flashed ivans official 2.1 with root access and voila it looks almost identical to stock minus superuser permissions, wireless and wired tethering for root users. It even shoes the option to check for system updates although it fc when you try to open it. What all should I uninstall and delete to make it look "totally stock" ? I was able to delete both tether apps using titanium backup but I guess ill have to buy root explorer to get rid of superuser permissions ( unless somebody can tell me another way ).:D

magic1,

Well, someone would actually have to type the "su" command in to see that you have root (I think that since you've removed the SuperUser whitelist app, that you wouldn't get prompted to allow any root-access from any of your apps). Anyone disagree?

You can easily test this by trying to launch something like drocap2 (free screen capture app on the Market). If it just won't allow you to run it, that's probably as much as you need / want. Someone would have to go looking for the su program (and or try to boot into custom recovery) to really tell that you've rooted (there's other tell-tale signs too like the Settings -> About phone -> Software Information screen where it lists your Kernel version which would not match a stock 2.1 phone). I think this is why most folks try to eradicate all of the footprints left-over from rooting...just in case. ;)

If you do simply want to remove the su program, there's a couple of ways to do it.

------------------------------

via the Android SDK: the only downside of doing this is that you might have to mess with your USB drivers to get your phone to actually "talk" to adb. The commands that I show below using the Android Terminal emulator are the same if you use the SDK's adb tool (i.e., via "adb shell").

------------------------------

via a terminal emulator (such as Android Terminal Emulator (free in the Market)):

- launch your selected terminal emulator (long-press the menu button to bring-up the keyboard)

- type su to give yourself root access

- type mount -o rw,remount /dev/block/mtdblock3 /system to enable read-write access to the /system filesystem (observe the spaces)

- type cd /system/bin to navigate to the sub

- type rm su to delete the su program

------------------------------

via EStrongs File Explorer: this is a free alternative to Root Explorer and is probably the easiest option (after typing the instructions for this, you might have to re-install the SuperUser app after all in order to do this...)

- download, install, and launch ES File Explorer (note: its sometimes a little wonky for me--I think it wants to also have EStrongs Task Manager and/or Security Manager installed to since it sometimes takes me back to the Market after launching it)

- press the menu button

- select Settings

- scroll down to Root options

- check the box next to Root Explorer (you'll be prompted by the app to tell you that this is an experimental feature and to acknowledge the SU Request--which you probably won't get because you've removed the SuperUser app--so, I hope this won't prove to be a stumbling block for you); select Yes

- when the Select ROM dialog pops-up, select HiAPK and then OK

- check the box next to Mount File System to have ES File Explorer remount /data and /system as writable

- press the back key twice to return to the file exploration screen

- click the "/" icon in the upper left-hand corner of the screen to change to the root filesystem

- scroll down to the system folder

- select the bin folder

- the path displayed in at the top of the screen should say /system/bin/

- scroll down to the su icon, long-press it, and select Delete

That should do it. Good luck.
 
I know this will sound ludicrous to ya but what exactly is the android sdk? If I use one of your methods listed above will that remove the Su program especially the superuser permissions app? I am still gonna try eu1's mention of the ruu method. I just want to have a backup just in case
 
I know this will sound ludicrous to ya but what exactly is the android sdk? If I use one of your methods listed above will that remove the Su program especially the superuser permissions app? I am still gonna try eu1's mention of the ruu method. I just want to have a backup just in case

edit: I just re-read your post...my earlier reply was all about just removing the su program from your phone (I thought you indicated that you've already removed the SuperUser permissions app?).

The Android SDK is the software development kit (Android SDK | Android Developers). Its the starting-point for doing extra stuff on your phone like developing apps. It also has some other tools like the adb (Android Debug Bridge) and the ddms (Davlik Debug Monitor) utility.

The above link shows some easy-to-find download links and a quick start quide. If you wanted to use it, you'd just need to do steps 1 and 2.

Folk's biggest issue, it seems, is actually getting your phone to be able to communicate the your computer via the USB connection to the adb utility (and oftentimes, just navigating to the "tools" directory of the SDK itself).

Here's some threads about installing and using the SDK:

http://androidforums.com/eris-all-things-root/100702-sdk-installed.html

http://androidforums.com/eris-all-things-root/104809-android-2-1-ota-trying-install-adb-driver.html

http://androidforums.com/eris-all-things-root/158136-cant-install-adb-hours-searching.html

http://androidforums.com/eris-all-things-root/147390-help-driver-wont-install-windows-7-eris.html

Cheers!
 
Do you think it may be easier to try estrongs first since I can't get to a computer yet and I've already got it on my phone?
 
Do you think it may be easier to try estrongs first since I can't get to a computer yet and I've already got it on my phone?

Well, if all you want to do is remove the su program, then ES File Manager is the easiest way to go (although you still might have to re-install the SuperUser app to do this, which you can re-uninstall like you did before).

You'll still have a semi-rooted phone with the recovery partition in place...(and a kernel which VZW might notice) so, if you really want to un-root it, you'll have to try flashing the v3 leak or use the RUU as eu1 discussed above.
 
Well, if all you want to do is remove the su program, then ES File Manager is the easiest way to go (although you still might have to re-install the SuperUser app to do this, which you can re-uninstall like you did before).

You'll still have a semi-rooted phone with the recovery partition in place...(and a kernel which VZW might notice) so, if you really want to un-root it, you'll have to try flashing the v3 leak or use the RUU as eu1 discussed above.

That's one of my problems. I've never been able to get rid of the superuser app or widget. I was able to delete wireless and wired tether using titnium backup. I just tried your idea of using estrongs but it showed an error at the very end about not having the SD card mounted?! Gonna try it again. How can I delete that superuser widget?
 
That's one of my problems. I've never been able to get rid of the superuser app or widget. I was able to delete wireless and wired tether using titnium backup. I just tried your idea of using estrongs but it showed an error at the very end about not having the SD card mounted?! Gonna try it again. How can I delete that superuser widget?

magic1,

Not sure what's going on with the SD card mount thing...:confused:

You should be able to delete the Superuser.apk file in the same way as I described for the su program, except that the Superuser.apk lives in the /system/app directory. You might have to reboot to see the app completely disappear from the app drawer.

You've also got to be careful to not remove your own root capability before you've deleted everything you need. I would think that removing the su program should be the last thing you would do.

I was going to suggest that you make sure you've taken a Nandroid backup to protect yourself, but your kind of charting new territory here with the way you are going about this...:D

Good luck! ;)
 
I uprooted with the ruu. It worked flawlessly. The only thing I didn't change was the bootloader its still s-off. I'm not too worried about that though.
 
I uprooted with the ruu. It worked flawlessly. The only thing I didn't change was the bootloader its still s-off. I'm not too worried about that though.

Was it pretty self explanatory as far as walking you through the process? Once you downloaded the ruu how long did it take to complete?
 
Back
Top Bottom