Database Info

How To UN ROOT. TUTORIAL. Your Problems are solved!

UPDATE: With all of the newer rooting and S-Off methods, and new hardware and firmware revisions, this thread may or may not help with your specific case if trying to unroot and go back to unrooted stock. I originally wrote this based of of the very first root methods known for the Launch EVO. There is a good chance that this method will still work, but there could definitely be something unaccounted for in your own specific case, so tread with caution. It is very doubtful that anything in this tutorial will result in your EVO becoming a fancy-schmancy paperweight, but if something goes afoul, you could have a nice headache to deal with...
Ok guys. There is a lot of partial and mis-information floating around out there about how to UN ROOT if you have to send your phone back for replacement, or you want the official unrooted OTA 2.2.
OLD NEWS!!!---> NEWER METHODS AVAILABLE TO ACTUALLY FIX PRI DOWNGRADE> SEARCH!!!! EDIT your PRI to show 1.40, thanks to sturmen for the pointer, and Calkulin for the method: http://forum.xda-developers.com/showpost.php?p=7267559&postcount=66
This assumes you are full root, S-Off. Note, this is not tested with simple root but should work (EDIT, Simple Root is basically Toastcfh's method, so you simple root users should be set), only with Toastchf's root method and nand unlock.
After reading every thread on the forum here, I think I finally found a fool proof way to do it. All the info was out there, but in several places and each one was missing something.
1) Before you start clicking and flashing and running RUUs, Check your HBoot build. You need to have the 0.76.2000 from Toastcfh's method #2. If you have 0.79.0000 (whatever) go to step 2 below. If you're getting Bootloader errors when running an RUU, I can almost guarantee that you don't have the correct HBOOT. If you somehow still have 0.76.2000 from previous modding, proceed to step 3.
2) Toast's Nand Unlock method. Found here: http://forum.xda-developers.com/showthread.php?t=701835
EDIT: The more I think about it, I think you can just run Simple Root to re-attain the .76 HBOOT and engineering build. It would eliminate the need for any adb, and SHOULD produce the same results. Just run the RUU after you run and complete simple root. See notes in BLUE below too!
THIS STEP IS 100% NECESSARY IF YOU HAVE THE .79 HBOOT version!!!...Do step #2 in Toast's thread, just like you did when you originally unlocked NAND (OR YOU SHOULD BE ABLE TO JUST RUN SIMPLE ROOT AGAIN...UNconfirmed, but should work methinks...). Not 100% sure which steps are necessary, but I do know you need to do steps #1 (Well, #1 is Nandroid Backup, so proceed at own risk if you skip) and #2 again. Make sure after you flash the Flash_Image, and the mtd-eng through adb, that you then load the PC36IMG.zip (Engineering Build), onto the root of your SD card, and boot into HBOOT, and let it install (just like you did when rooting). I didn't bother to flash the Recovery image at the end of step 3, but I don't think it would hurt if you're nervous about losing a custom recovery image in case this method for some reason does not work. It has come to my attention that flashing the engineering build (the PC36IMG from Toast's thread)through fastboot, might be as crucial as simply having the .76 HBOOT version. It at least is a surefire way to make sure you can run an RUU on top of it. There are probably other builds/roms that will work and allow you to run the RUU, but this one is confirmed, so don't skip that step!
3) If you have the 0.76.2000 HBOOT (can be checked by powering down, and booting by holding VOL down and Power), then you can go ahead and boot into the rom, and proceed with downloading the RUUs found here: http://shipped-roms.com/shipped/Supersonic/
Go ahead and download the first one (at least). I think the others are optional to "upgrade" but why should we care. We just want to go back to unrooted stock.
4) Make sure you have the latest version of HTC Sync installed, found here: http://www.htc.com/uk/SupportViewNews.aspx?dl_id=933&news_id=627
Install, and let it do it's thing. Will probably have to restart your PC when complete. Not even 100% sure this is necessary, but it won't hurt. It's basically for the HTC drivers from what I understand.
5) Run the RUU from your pc while your evo is in the phone loaded state of the Rom, (not the bootloader) with the phone connected through USB and have HTC sync selected. Even if it doesn't connect to HTC sync on your PC, you should be ok.
If you get a USB error after the screen goes black with the HTC LOGO, don't touch the phone. Exit the RUU via the EXIT button when given the option.
6) Run the RUU again and see what happens. The Error could happen 1 more time, but just exit again, and run RUU one last time.
7) Thank everyone here at XDA that our EVOs are so badass...I'm certinly not a dev, but these devs work hard for us to have the baddest ass phone there is right now.
Any problems, let me know. I assume your errors are the same ones I was getting, and it's all because of the wrong HBOOT.
I really take no credit for this, as I'm just compiling information in a tut....

Thanks op.

Or you can flash the new FroYo update release. =D
But thanks OP. Your hard work is much appreciated.

arozer said:
Or you can flash the new FroYo update release. =D
But thanks OP. Your hard work is much appreciated.
Click to expand...
Click to collapse
You might be correct, but I couldn't get the FROYO OTA to show up in any of the roms I was using.

Question: what's the deal with the PRI? Has anyone been able to properly fix that yet?

sturmen said:
Question: what's the deal with the PRI? Has anyone been able to properly fix that yet?
Click to expand...
Click to collapse
From my research, NO...Unfortunately, but this should get you as good as possible with what's out there now..
EDIT: Yess! See below and in OP!

Bang3r said:
From my research, NO...Unfortunately, but this should get you as good as possible with what's out there now..
Click to expand...
Click to collapse
Hm. I think I remember someone made a hex-edited PRI that people can flash in case they have to return it. I'll find it...

sturmen said:
Hm. I think I remember someone made a hex-edited PRI that people can flash in case they have to return it. I'll find it...
Click to expand...
Click to collapse
That would be cool, but I'm not too worried about that part. Phone is going back tomorrow!

Well, worry even less! Special thanks to Calkulin!

thankssssss

Thanks a lot for this. I have searched for a un root that worked and you were right the bootloader was the problem. Followed directions here and I am back to stock Froyo un rooted.
Thanks
topcop

I followed your guide and ran into a few issues. From my experiences, you can only run the RUU from your software version or higher (Can't use a 1.32 RUU on a Evo with software version 1.47). Therefore, I think everyone should always flash the engineering build so they can use the earliest RUU. Just my 2 cents though...

I'm getting error 155 running Ava Froyo and trying to go back.

blix1337 said:
I followed your guide and ran into a few issues. From my experiences, you can only run the RUU from your software version or higher (Can't use a 1.32 RUU on a Evo with software version 1.47). Therefore, I think everyone should always flash the engineering build so they can use the earliest RUU. Just my 2 cents though...
Click to expand...
Click to collapse
Yes, you are correct, but so am I. This is exactly what step 2 in the OP does (which is a link to Toastcfh's thread about the engineering build).

tonyk__78 said:
I'm getting error 155 running Ava Froyo and trying to go back.
Click to expand...
Click to collapse
Ok. RE-read the OP. Everything is there. Check your HBOOT version by booting to the bootloader. If you have .79, you need to re-flash the engineering build before the RUU will work (Step 2 in the OP to get HBOOT to .76). You cannot run the RUU on top of AVA froyo or any froyo, or any rooted custom 2.1 for that matter if you don't have the proper HBOOT (Which I believe you cannot have if you are running any custom rom). Flash to the engineering build, then the RUU.

How far "unrooted" does this get you? Can you still re-root using toast's method or SimpleRoot?

joypunk said:
How far "unrooted" does this get you? Can you still re-root using toast's method or SimpleRoot?
Click to expand...
Click to collapse
Yes you can still REroot VIA those methods. As long as you don't do a FROYO OTA or manually flash the UNROOTED Froyo...there is no ROOT method for FROYO yet.
It returns completely to UNROOTED stock, except for the PRI, which there is a fix for on the 1st page.
And incidentally (and I just figured this out last night) Simple Root is Toast's method, just automated...
EDIT: I think that you could even UNROOT and RUU to 1.3x (whatever it is), then use the ROOTING methods that were in place before the official 1.47 OTA rooting methods. But, I just did simpleroot last night on top of 1.47, and it is freaking SIMPLE....1 click for root...1 click to flash recovery.

tpdtopcop said:
Thanks a lot for this. I have searched for a un root that worked and you were right the bootloader was the problem. Followed directions here and I am back to stock Froyo un rooted.
Thanks
topcop
Click to expand...
Click to collapse
This is what were trying to show you on Androidcentral as well. Glad you are set!

tonyk__78 said:
I'm getting error 155 running Ava Froyo and trying to go back.
Click to expand...
Click to collapse
As long as you have .76 HBOOT flash back to an earlier rom...one that has a 1.32 base. Then use the 1.32 RUU or 1.47 RUU. You should be set. Make sure you have completed step 2 in OP.

Yes. I have .79, thanks!
Sent from my PC36100 using XDA App

[GUIDE] Rooting existing 1.72 without downgrading

A couple of weeks ago I upgraded to 1.72 using the RUU. I had radio S-OFF but otherwise I lost Clockwork Recovery and ENG HBOOT. My phone is unbranded.
The advice around here seems to be to downgrade, ENG HBOOT again, then re-upgrade. But I didn't really feel like wiping the phone so I tried a few things and managed to root the phone without much hassle in the end. The method is probably dangerous and not failsafe, so I won't be responsible for any damage.
(Sorry if this had been pointed out before)
1. Get the image for Clockwork Recovery 2.5.1.2 from http://forum.xda-developers.com/showthread.php?t=841207
2. In the computer's terminal, type, without quotes, "adb push recovery-clockwork-2.5.1.2-ace-modaco-r2.img /sdcard/recovery.img". This will copy the Clockwork Recovery image on to the SD card.
3. Get psneuter from http://forum.xda-developers.com/showthread.php?t=905003. Follow the instructions on that thread to get adb root shell. (You don't need to push or run misc_version)
4. In the adb shell, make sure that the prompt is #. Type (without quotes) "dd if=/dev/block/mmcblk0p21 of=/sdcard/recovery_orig.bin" This will backup the current recovery partition.
5. In adb shell again, type (without quotes) "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21". This will install Clockwork Recovery.
6. Get the patched Superuser from http://forum.xda-developers.com/showthread.php?t=886999
7. Follow the "Restoring SU" section of this thread http://forum.xda-developers.com/showthread.php?t=885996 for permroot.
8. (optional, dangerous) If you want to ENG S-OFF for future use, get BusyBox from Market, then follow http://forum.xda-developers.com/showthread.php?t=835746.
(This probably needs radio S-OFF to work, but definitely not ENG S-OFF)

@ Devs....is this pertinent to the Dev section? Please reply via PM only.
@ OP... good day .
Regards,
M_T_M

The title is very misleading. It only works on Radio S-OFF devices, and it is VERY VERY bad for the device. The psneuter shoots the device's property service in the head, so your device will definitely not be happy about it. Starting new processes might make the whole system unstable.

jkoljo said:
The title is very misleading. It only works on Radio S-OFF devices, and it is VERY VERY bad for the device. The psneuter shoots the device's property service in the head, so your device will definitely not be happy about it. Starting new processes might make the whole system unstable.
Click to expand...
Click to collapse
I realise that psneuter will leave the system in an unstable state, but the only process that gets started when the phone is in that state is dd in order to copy over the recovery image. Granted, this could nuke the recovery partition, but there was nothing to lose for me since my recovery was somehow already corrupted prior to starting this.
If all goes well, after dd'ing recovery and reboot the effects of psneuter are reversed anyway, so if I understand everything correctly it's no worse for the device than doing a downgrade using psneuter. If I'm wrong, sorry, and I would very much like to be enlightened

Nope, a reboot will unfortunately not fix the property service..
There is no good way to temproot 1.72 yet. And if somebody invents such method, it would still keep people from permrooting their devices because the radio blocks write access. It is the old eMMC problem.

jkoljo said:
Nope, a reboot will unfortunately not fix the property service..
There is no good way to temproot 1.72 yet. And if somebody invents such method, it would still keep people from permrooting their devices because the radio blocks write access. It is the old eMMC problem.
Click to expand...
Click to collapse
In that case, could one reflash the kernel to restore the service? Or does it need a complete ROM reflash?

I do not really know where the service is, so I cannot confirm it.. But it probably needs a rom reflash, which then removes root again.

jkoljo said:
I do not really know where the service is, so I cannot confirm it.. But it probably needs a rom reflash, which then removes root again.
Click to expand...
Click to collapse
Well I could try reflashing boot.img since that doesn't take too much effort. Any way to check whether the service is working properly?

Sorry...thread closed. Non Dev relevant and has become a Q&A thread.
Regards,
M_T_M
Your friendly Mod

Something's wrong...

So I tried rooting the phone and it wouldn't do it. After a restart its just getting stuck at the "MY" logo
Did i brick it?
Edit: its working now but I can't get it rooted. I got the root.rar file unzipped into the sdcard/root but it says its not permited, what am I doing wrong?

That gives us nothing to go on. There are several rooting methods out there. Which are you using?

http://forum.xda-developers.com/showthread.php?t=858021&highlight=operation
That one
When i get to c. Type "sh root.sh" + enter.
it gives me an error and it tells me to restart and check if s=off but when i reboot and hold down the volume button nothing happens. It just reboots normally

That's the best guide out there and the one that I used.
Before attempting to run the script, did you successfully gain temp root using Visionary and set system to R/W?

Try the method here: http://forum.xda-developers.com/showthread.php?t=858996
It is newer and better in my opinion. Try it from the beginning step-by-step and see if it works.

TeeJay3800 said:
That's the best guide out there and the one that I used.
Before attempting to run the script, did you successfully gain temp root using Visionary and set system to R/W?
Click to expand...
Click to collapse
It asked me for super user permission so i'm pretty sure I got temp root.
I finally got something it rebooted and I checked but it still says s-on.
I'll try the script again and post what I get but this is very weird, I had no problems with my G2.
Edit:
my terminal output is
Inserting kernel module
ismod: init_module '/sdcard/root/wpx.ok' failed (Function not implemeneted)
Duplicatiing hboot
2048+0 records in
2048+0 records out
1048576 bites transferred in 0.721 secs (1454335 bytes/sec)
Synchronizing
Powerdown and reboot into hboot to check if s+off
when I reboot i get
GLACIER PVT SHIP S-ON
HBOOT-0.86.0000
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
OK Last edit:
It seems my Hboot being 0.86.0000 had something to do with it, I tried the other method with adb and it worked I finally got S-off. This was harder to do than on my G2 that's for sure.
Thanks to those who tried helping and thanks to kmdub for suggesting the alternate method.

For some reason, you are not writing the proper hboot image. Try to re-download or find another source, because the one you are writing, according to your output, is not the right one.
OR...you could try the method I posted above, which does not require a new hboot and actually turns the radio S=OFF. Seriously though, why not use a different (read newer and better) method if the one you are using is not working?

Evofusion said:
It seems my Hboot being 0.86.0000 had something to do with it, I tried the other method with adb and it worked I finally got S-off. This was harder to do than on my G2 that's for sure.
Thanks to those who tried helping and thanks to kmdub for suggesting the alternate method.
Click to expand...
Click to collapse
While there are other rooting methods out there, there is nothing wrong with the guide you are following. Like I said, it worked great for me. The only thing I can think of is the version of Visionary you are using. r11 is supposed to work better than r14 on the MT4G. The script you run in the beginning flashes the engineering bootloader (0.85.2007), so that's way to tell if the script was successfully run. Just make sure you actually get root access after typing 'su' (so make sure Visionary gets temp root and system is set to R/W first).

Glad you finally got it working.
It seems my Hboot being 0.86.0000 had something to do with it, I tried the other method with adb and it worked I finally got S-off.
Click to expand...
Click to collapse
That's because the method you were trying first requires the ENG hboot as an essential part of the rooting process. It would have worked, but for some reason it seemed like the one you were writing was the same as what you already had. I don't know if you used the other method I posted or another "other" method, but the one I linked to actually turns the radio's security off (S=OFF) among other things, if you so choose. The older method replaces the stock bootloader with one that does not enforce/ignores the radio's set security. Whereas the newer method actually turns that security flag off, so you can use either bootloader. Both can use Visionary and effectively allow you to "root" the device, but the newer method is more permanent, so to speak.

kmdub said:
I don't know if you used the other method I posted or another "other" method, but the one I linked to actually turns the radio's security off (S=OFF) among other things, if you so choose. The older method replaces the stock bootloader with one that does not enforce/ignores the radio's set security. Whereas the newer method actually turns that security flag off, so you can use either bootloader. Both can use Visionary and effectively allow you to "root" the device, but the newer method is more permanent, so to speak.
Click to expand...
Click to collapse
So even though I have the engineering bootloader and my S status is "OFF", the radio security is still on? Does that only matter if for some reason I switch back to the stock bootloader, and as long as I keep the eng SPL the difference in methods is inconsequential?

Evofusion said:
http://forum.xda-developers.com/showthread.php?t=858021&highlight=operation
That one
When i get to c. Type "sh root.sh" + enter.
it gives me an error and it tells me to restart and check if s=off but when i reboot and hold down the volume button nothing happens. It just reboots normally
Click to expand...
Click to collapse
Just a quick FYI on this, did you uncheck Fast Boot in the settings?

So even though I have the engineering bootloader and my S status is "OFF", the radio security is still on? Does that only matter if for some reason I switch back to the stock bootloader, and as long as I keep the eng SPL the difference in methods is inconsequential?
Click to expand...
Click to collapse
That is the impression I got from reading grankin01's method at the link I posted earlier; that yes, the security flag controlling the security is still set to on. Flashing the ENG bootloader is what actually gives you a label that says S=OFF on the older methods, since that bootloader either ignores the security flag or overrides it somehow. I am not certain about exactly how this takes place. What we do know however, is that security is not enforced regardless since it does allow you to effectively root the device, and you obviously have it working with the older method. The benefit of the newer method is outlined in his post. It allows you to retain the original bootloader and truly be S=OFF. I guess one could say that the older method provides an easier return to complete stock (warranty, return, etc.), since all one would have to do is use the PD15IMG to return to a completely stock state, bootloader and all. However, with the newer method, one would have to reverse the steps done with gfree in order to return to S=ON. So I would think that as long as you have the ENG bootloader you are ok, and it may make no difference. I do not know that from experience however, since I have only ever used the newer method with stellar results.

kmdub said:
The benefit of the newer method is outlined in his post. It allows you to retain the original bootloader and truly be S=OFF. I guess one could say that the older method provides an easier return to complete stock (warranty, return, etc.), since all one would have to do is use the PD15IMG to return to a completely stock state, bootloader and all. However, with the newer method, one would have to reverse the steps done with gfree in order to return to S=ON. So I would think that as long as you have the ENG bootloader you are ok, and it may make no difference. I do not know that from experience however, since I have only ever used the newer method with stellar results.
Click to expand...
Click to collapse
Thanks for the info. My understanding of one method versus the other was pretty much what you explained, but it's good to have it clarified.
I used fastboot way back in my G1 days.....first with the original EngSPL, then HardSPL, and finally when haykuro released DangerSPL. Since I would want the engineering bootloader anyway, I suppose there's no disadvantage to using the method I used. For those that want the stock bootloader, I can see why the newer method is advantageous to them.

unroot

Hello all i am new to all this android stuff. Need to remove clockwork mod.
Where do i find the stuff needed to get my sensation back to stock.
this is my software version 1.35.161.2
if you can help that will be great

That's Vodafone UK correct? If so, you'll need to do the following:
1. Set your phone to Super CID using this guide - http://forum.xda-developers.com/showthread.php?t=1192300 (Step 4)
2. Download this RUU - http://www.multiupload.com/SAFC8695JA
3. Reboot the phone into fastboot, connect to your PC and run that RUU
4. Once the RUU has finished you'll be back to stock but still S-OFF. Reset your CID using the guide above but set it to VODAP001
5. Then, using the guide above again, set your phone to S-ON
That should do the job, any questions just say

got a tad lost using the guide. is there not an easyer way to return to stock ?
butt ran the ruu program and that as removed the clockwork mod i think but phone still says s off.

It will say S-OFF, you now need to change back to S-ON using step 5
Did you have to set your phone to Super CID to get the RUU to flash? If so, you'll need to change it back to the Vodafone one befire setting S-ON
So long as you read it all first, then read it again, you should be OK

is there a video tutorial anywhere ?

What have you done so far? You say you ran the RUU, correct? Did this go through without having to set Super CID?
That guide is a n00b proof one so I'm finding it hard to know where you're going wrong

tryed super sid but dont think it worked as did not see the phone reeboot or anything. then used ruu in the link you gave me. worked without super sid i think. as phone was able to bolwload and update over the air update. the clockwork mod is nolonger there when i boot up using volume and power method.
but pnone says s 0ff still.

S-off and im 1.45, but cant root

Ok heres the deal. I got the MT4G slide in jan. I rooted it & gained s-off with the revoloutionary tool. When t mobile rolled out the ota, I installed & I lost my root capabilities. Now i have been looking through the threads trying to figure out how to root my phone. Wen i put my phone into boot loader, it says s-off with 1.45. the other threads that I have seen are 1.55 with s-on. Is there something that I am missing, I want to install cmn 9 or a ics rom. Could somebody point me in the right direction as far as what I am doing wrong. I tried the all in one tool, but I got lost when I has to ue the sdk installer on htcdev. thanks in advance for the help

Try pushing CWM via adb then use that to flash su. There are instructions in one of the stickies. You could do it all in adb of you wanted to.
Hastily spouted for your befuddlement

jbright407 said:
Ok heres the deal. I got the MT4G slide in jan. I rooted it & gained s-off with the revoloutionary tool. When t mobile rolled out the ota, I installed & I lost my root capabilities. Now i have been looking through the threads trying to figure out how to root my phone. Wen i put my phone into boot loader, it says s-off with 1.45. the other threads that I have seen are 1.55 with s-on. Is there something that I am missing, I want to install cmn 9 or a ics rom. Could somebody point me in the right direction as far as what I am doing wrong. I tried the all in one tool, but I got lost when I has to ue the sdk installer on htcdev. thanks in advance for the help
Click to expand...
Click to collapse
When you go into your bootloader, does it say "locked" or "unlocked?" If it's locked, go to HTCdev and unlock it THEN flash CWM recovery via Fastboot.

If you are S-Off, go into bootloader. What does the top say? Revolutionary? Locked? Unlocked? Relocked? If it says Locked/Unlocked/Relocked, you need to flash the Rev HBOOT.

Ok thanks for the pointers. At the top of the screen it says locked. So ill try the dtc dev route. I got hung up on the part when i have to install the sdk & find the files that I have renamed. Is there a video tutorial of the process or is there something I am missing. I have experience with rooting, I have rooter hd2s, my transformer & several evos. I just cant understand that 1 portion of it. Thanks for the fast responses and the help, I didnt think it would be that immediate. I am just tired of not having ics on my phone, but I have it on all of my other devices, .