Database Users

How to COMPLETELY unroot EVO to send back to Sprint

How do I COMPLETELY unroot EVO to send back to Sprint
Like s-off s-on plz help

If you rooted using Unrevoked 3.21 there is a thread listed in Android Development explaining the process as well as the needed links to download the needed zip files to turn S-On and the zip file to restore back to Stock Froyo 2.2

SouthernEvo said:
If you rooted using Unrevoked 3.21 there is a thread listed in Android Development explaining the process as well as the needed links to download the needed zip files to turn S-On and the zip file to restore back to Stock Froyo 2.2
Click to expand...
Click to collapse
Tbd but I used toast.method to root that used a lot of adb

mccurt29 said:
Tbd but I used toast.method to root that used a lot of adb
Click to expand...
Click to collapse
Ok but there are still methods in the forum for unrooting just like how you rooted. I would just do a search for them and choose which one you feel is the easiest for you to understand. Also if you are getting another EVO unrevoked 3.21 is as many in here have said easy peasy for rooting.
Good luck

playya said:
Ok but there are still methods in the forum for unrooting just like how you rooted. I would just do a search for them and choose which one you feel is the easiest for you to understand. Also if you are getting another EVO unrevoked 3.21 is as many in here have said easy peasy for rooting.
Good luck
Click to expand...
Click to collapse
Thanks!......

You need to run the RUU.exe found in the Dev section. It will do the trick.
Sent from my PC36100 using XDA App

novanosis85 said:
You need to run the RUU.exe found in the Dev section. It will do the trick.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Precisely. It can be found here:
*OFFICIAL* RUU_SuperSonic_S_Sprint_WWE_3.29.651.5_Radio_2.15. 00.09.01_NV_1.77_CNV_rel.
One thing to check first: do you have S-OFF? This would be the case if you ever ran Unrevoked Forever or Unrevoked 3.21. If so, you'll need to flash the Unrevoked Forever S-ON tool from recovery before running the RUU.

Noxious Ninja said:
Precisely. It can be found here:
*OFFICIAL* RUU_SuperSonic_S_Sprint_WWE_3.29.651.5_Radio_2.15. 00.09.01_NV_1.77_CNV_rel.
One thing to check first: do you have S-OFF? This would be the case if you ever ran Unrevoked Forever or Unrevoked 3.21. If so, you'll need to flash the Unrevoked Forever S-ON tool from recovery before running the RUU.
Click to expand...
Click to collapse
Thx guys I never used unrevok just toast methods but how do u check the A-on thing & should it be on or off
Also this 1 guy on this forum said he used the ruu & had s-on/off but Sprint still found out he rooted so should I wipe that ex--- >#366# stuff too?

mccurt29 said:
Thx guys I never used unrevok just toast methods but how do u check the A-on thing & should it be on or off
Also this 1 guy on this forum said he used the ruu & had s-on/off but Sprint still found out he rooted so should I wipe that ex--- >#366# stuff too?
Click to expand...
Click to collapse
Reboot into the bootloader (turn phone off, then hold power+volume down until it comes on). Then look at the end of the first line.
If it says SHIP S-ON, you're good.
If it says SHIP S-OFF, you need to run the Unrevoked tool.
If it says ENG S-OFF (which should be the case if you used Toast's method), it is indeterminate.
However, if you never used Unrevoked at all, you shouldn't have to worry about it. You can check after you run the RUU, which will reset it to the SHIP bootloader.
I believe the 3.29 RUU resets everything, including the PRI. Toast's method downgraded the PRI, and it was difficult to get it back before the current update, so this used to be a sure-fire way of telling whether you had rooted. Unless you had a bad Wimax flash and broke your 4G, I *think* you should be OK. But I don't know for sure.

Noxious Ninja said:
Reboot into the bootloader (turn phone off, then hold power+volume down until it comes on). Then look at the end of the first line.
If it says SHIP S-ON, you're good.
If it says SHIP S-OFF, you need to run the Unrevoked tool.
If it says ENG S-OFF (which should be the case if you used Toast's method), it is indeterminate.
However, if you never used Unrevoked at all, you shouldn't have to worry about it. You can check after you run the RUU, which will reset it to the SHIP bootloader.
I believe the 3.29 RUU resets everything, including the PRI. Toast's method downgraded the PRI, and it was difficult to get it back before the current update, so this used to be a sure-fire way of telling whether you had rooted. Unless you had a bad Wimax flash and broke your 4G, I *think* you should be OK. But I don't know for sure.
Click to expand...
Click to collapse
thanx that did the trick now to the sprint store tomorrow wish me luck

If your still having trouble then try this:
http://forum.xda-developers.com/showthread.php?t=780141&highlight=unroot
I just unrooted mine last night and it only took me 5 mins, just flash the unrevoked and then do the update on the PC36IMG and thats it.

S-ON and S-OFF

Today I accidently turned it on (the thing in the bootloader) and now I can't turn it off no matter what so I can do a revert to stock .img, I used the PDI15.img or w.e that would revert back to stock forgetting that I had the newest radio and now I can't revert to stock or turn S-OFF. Please help
Current Configurations:
GLACIER PVT SHIP S-ON
HBOOT - 0.86.0000
MICORP - 0429
RADIO - 26.09.04.26_M
eMMC - BOOT
More Info:
When I use a PDIMG or w/e file it errors out as being old

Can you still boot? Like into your rom? If so just try rooting using visionary and using a root explorer to push the gfree files to data/local/ then just follow the normal rooting procedure
Sent from my HTC Glacier using XDA Premium App

Nicgraner said:
Can you still boot? Like into your rom? If so just try rooting using visionary and using a root explorer to push the gfree files to data/local/ then just follow the normal rooting procedure
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Yeah I can still boot into my rom, bootloader, and recovery and okay will try that
EDIT: Okay I did, I tried turning S-OFF but it says something about eMMC power cycle failed

XxKOLOHExX said:
Yeah I can still boot into my rom, bootloader, and recovery and okay will try that
EDIT: Okay I did, I tried turning S-OFF but it says something about eMMC power cycle failed
Click to expand...
Click to collapse
dude! I noticed this also this morning. I am rooted(using setcpu and root explorer just fine) but in hboot it says s=on. I was also wanting to flash the stock .img and start fresh. thought I was the only one having this problem. tried everything you did and got the same results.

What ROM are you on? AFAIK, gfree, requires the stock kernel to do what it does. How on earth did you turn S-ON? That sort of thing shouldn't just happen out of nowhere.

How is the progress on fixing your phone?

jdkoren said:
What ROM are you on? AFAIK, gfree, requires the stock kernel to do what it does. How on earth did you turn S-ON? That sort of thing shouldn't just happen out of nowhere.
Click to expand...
Click to collapse
currently on Evil D mTGB v1.0, Faux 0.0.7 CFS lv leak kernel. everything works fine, no FC's or anything. just having the same issues as XxKOLOHExX. I really have no idea how it turned on by itself, I dont remember doing anything out of the ordinary

I was trying to get back to stock from the rom i was on. (MIUI) and when I used the stock .img though the bootloader it went all good till it rebooted, then it said failed because the file was old and now I am stuck with s-on and I don't know how to turn it off

How did you get to the stock bootloader? Did you have eng bootloader at one point? What meth of root did you use? Alot of info missing.
Now download the stock radio.img and push it via adb or just download the PD15IMG.zip (radio only not rom included). Once this is done you can revert back to stock rom/radio using standard PD15IMG.zip (radio+rom). Now depending on the type of root you used it would depend if you still have radio flag on/off even if your reverted back to stock bootloader.
PS: You can get PD15IMG.zip (stock radio) from master radio thread and PD15IMG.zip (stock radio/rom) by doing search.

PermROOT said:
How did you get to the stock bootloader? Did you have eng bootloader at one point? What meth of root did you use? Alot of info missing.
Now download the stock radio.img and push it via adb or just download the PD15IMG.zip (radio only not rom included). Once this is done you can revert back to stock rom/radio using standard PD15IMG.zip (radio+rom). Now depending on the type of root you used it would depend if you still have radio flag on/off even if your reverted back to stock bootloader.
PS: You can get PD15IMG.zip (stock radio) from master radio thread and PD15IMG.zip (stock radio/rom) by doing search.
Click to expand...
Click to collapse
It flashed the bootloader when I flashed the PD15IMG.zip, it just stop when I did the whole procedure. Nope never flashed an Engineer Bootloader. I used theunlockr.com sites method
I tried that, it uziped then tried to flash the radio then just went back to the original menu for the bootloader

If you used the VISIONary+ (TempROOT) and root.sh (PermROOT) meth then you already had engineering hboot (0.85.2007) pushed though terminal on "/dev/block/mmcblk0p18". Now you did something in between is what I would like to know.
As you flashed new radio (26.09.04.26_M) which I am clear. But what I like to know is how did you end up with default hboot (0.86.0000)? If you had S=OFF you didn't lose it via flashing new radio. Which PD15IMG.zip did you install? Now when you say PD15IMG.zip what do you mean? It can be anything as its default mt4g system based image. Stock PD15IMG.zip = (Sense 2.2.1 Rom/Radio 26.03.02.26_M). Did you install leaked PD15IMG.zip from Panache? or GB2.3.3S?
Are you not 1 of the Royal dev's? who try to take over Silence's IG if I recall. I am just assuming here but this is why you do "NOT" dump system image via hboot. What you should have done was do complete total system wipe (format /data; /system) and then flash new edify based CWMR flashable rom.

PermROOT said:
If you used the VISIONary+ (TempROOT) and root.sh (PermROOT) meth then you already had engineering hboot (0.85.2007) pushed though terminal on "/dev/block/mmcblk0p18". Now you did something in between is what I would like to know.
As you flashed new radio (26.09.04.26_M) which I am clear. But what I like to know is how did you end up with default hboot (0.86.0000)? If you had S=OFF you didn't lose it via flashing new radio. Which PD15IMG.zip did you install? Now when you say PD15IMG.zip what do you mean? It can be anything as its default mt4g system based image. Stock PD15IMG.zip = (Sense 2.2.1 Rom/Radio 26.03.02.26_M). Did you install leaked PD15IMG.zip from Panache? or GB2.3.3S?
Are you not 1 of the Royal dev's? who try to take over Silence's IG if I recall. I am just assuming here but this is why you do "NOT" dump system image via hboot. What you should have done was do complete total system wipe (format /data; /system) and then flash new edify based CWMR flashable rom.
Click to expand...
Click to collapse
Yeah I know that, I Was trying to go back to stock everything using the unrooting method(PD15IMG.zip). Using this file I was able to get through the first step and it rebooted, then it went back to bootloader and now it won't take the PD15IMG.zip saying that it is an older file. Yes I am one of the devs, That's why before posting I tried everything I could think of, gfree, old unrooting methods, etc. I didn't use a dump lol I'm not that noobish haha

Thats where you got owned as the PD15IMG.zip (stock rom/radio) just reverted back to hboot (0.86.0000) from eng hboot (0.85.2007). While you attempted to go further you couldn't do to security turning on (S=ON). Now this normally wouldn't be problem but since you had newer radio (26.09.04.26_M) it wouldn't replace it with old.
All you had to do was follow few simple meths which you should have learned it over the years. Go back same way you came by first reverting back to original radio image and then after doing complete system wipe you should have reverted back to original factory based via stock pd15img.
Ill post back with solution soon let me think this out. I don't want to brick your phone trying to manually push the radio.img nor the eng_hboot.img. As if you try to push radio now would fail on write and give you hard brick. Since S=ON and if you try to push eng_hboot.img who knows what will happen as no R/W access on mmcblk could could also fail thus giving bad flash which can also brick the device. Ill see what happens and post back at... you folks just made more extra work for me.

PermROOT said:
Thats where you got owned as the PD15IMG.zip (stock rom/radio) just reverted back to hboot (0.86.0000) from eng hboot (0.85.2007). While you attempted to go further you couldn't do to security turning on (S=ON). Now this normally wouldn't be problem but since you had newer radio (26.09.04.26_M) it wouldn't replace it with old.
All you had to do was follow few simple meths which you should have learned it over the years. Go back same way you came by first reverting back to original radio image and then after doing complete system wipe you should have reverted back to original factory based via stock pd15img.
Ill post back with solution soon let me think this out. I don't want to brick your phone trying to manually push the radio.img nor the eng_hboot.img. As if you try to push radio now would fail on write and give you hard brick. Since S=ON and if you try to push eng_hboot.img who knows what will happen as no R/W access on mmcblk could could also fail thus giving bad flash which can also brick the device. Ill see what happens and post back at... you folks just made more extra work for me.
Click to expand...
Click to collapse
Thank you so much for the help

PermROOT said:
Thats where you got owned as the PD15IMG.zip (stock rom/radio) just reverted back to hboot (0.86.0000) from eng hboot (0.85.2007). While you attempted to go further you couldn't do to security turning on (S=ON). Now this normally wouldn't be problem but since you had newer radio (26.09.04.26_M) it wouldn't replace it with old.
All you had to do was follow few simple meths which you should have learned it over the years. Go back same way you came by first reverting back to original radio image and then after doing complete system wipe you should have reverted back to original factory based via stock pd15img.
Ill post back with solution soon let me think this out. I don't want to brick your phone trying to manually push the radio.img nor the eng_hboot.img. As if you try to push radio now would fail on write and give you hard brick. Since S=ON and if you try to push eng_hboot.img who knows what will happen as no R/W access on mmcblk could could also fail thus giving bad flash which can also brick the device. Ill see what happens and post back at... you folks just made more extra work for me.
Click to expand...
Click to collapse
lol sorry for the extra work, just dont wanna have the chance of bricking my phone but like XxKOLOHExX I wanted to revert back to stock from mTGB using the stock PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60.140e_26.03.02.26_M_release_155771_signed. everything he described is happening to me also, step by step. I rooted with the visionary+ and permroot method(unlockr). I did download and flash the 26.08.04.30 radio. heres what I see in hboot
GLACIER PVT SHIP S-ON
HBOOT-0.86.0000
MICROP-0429
RADIO-26.08.04.30_M3
eMMC-boot
Sep 27 2010, 11:12:59
so what youre saying is that we should try flashing the stock radio first, wipe the whole phone(including sdcard?), then flash the stock PD15IMG? Ill give it a shot real quick, thanks
*edit* hboot wont even let me flash the stock radio, itll say checking but wont actually let me update it

Well clarknick27 the problem here is that root.sh to gain PermROOT via VISIONary+ just push the 0.85.2007 eng hboot and giving temporary S=OFF, the true security flag as we know it is controlled in the radio. So when you try to revert back using stock PD15IMG (rom/radio) it reverted back to the stock 0.86.0000 hboot thus turning on the security flag on.
What you all should have done is reverted back same way you installed it. Which would have been first use PD15IMG.zip (stock radio) and then use stock PD15IMG.zip (radio/rom). I still need some sleep lol I just wokeup after sleeping 2hours.
The MT4G I tested on I rooted it via VISIONary+ and then flashed GB Leak rom not the PD15IMG.zip (leak radio/rom) which contained the 0.89.0005 hboot. So after flashing stock radio PD15IMG.zip (radio 26.03.02.26_M) I was able to flash stock PD15IMG.zip (rom/radio) without problem. Which is same as I suspected even after S=ON due to same version radio no problem. If I had newer radio after that point it would be locked out. Let me go to sleep and wakeup and ill see what happens from there. As I have clean MT4G ill have to reroot it first.

BTW XxKOLOHExX and clarknick27 just in case my account gets disabled. Do the following and report it here and ill see from there.
1) Which working rom you currently have installed on the device?
I know trying to reroot using gfree may give you similar result as my test: http://forum.xda-developers.com/showthread.php?t=1066966 < not important but unable to root on newer rom.
2) What happens when you try to reroot it using VISIONary+ (TempROOT) and root.sh (PermROOT)?
Did you try it? If so what is the end result? so post back. Ill check and go from there.

PermROOT said:
BTW XxKOLOHExX and clarknick27 just in case my account gets disabled. Do the following and report it here and ill see from there.
1) Which working rom you currently have installed on the device?
I know trying to reroot using gfree may give you similar result as my test: http://forum.xda-developers.com/showthread.php?t=1066966 < not important but unable to root on newer rom.
2) What happens when you try to reroot it using VISIONary+ (TempROOT) and root.sh (PermROOT)?
Did you try it? If so what is the end result? so post back. Ill check and go from there.
Click to expand...
Click to collapse
1) currently running Evil D's mTGB v1.0 rom with Faux's 0.0.7 CFS LV leak kernel. tried rooting with visionary and terminal first, no success. I then tried out the gfree method, and got "Attempting to power cycle eMMC...failed. Module failed to load: No such file or directory."
2) I installed Visionary using Astro file manager, then run Visionary. I click on "temproot now" and it starts, but then the screen goes black and doesnt do anything. I have let it sit on the black screen for well over 15mins before with no luck. I can click on "attempt to permroot" and it will ask for permissions and reboot and everything. my s=on but I still have root access and 0.86.000 bootloader. this is what I see using terminal before rebooting to see if s=off

Did you do the Radio S=OFF using gfree? If so that would explain why you still have root as security is disabled on the device totally. If thats the case then just push the eng bootloader manually via adb or though terminal and reboot. For now XxKOLOHExX is locked lets see what I find ill post back for him.

PermROOT said:
Did you do the Radio S=OFF using gfree? If so that would explain why you still have root as security is disabled on the device totally. If thats the case then just push the eng bootloader manually via adb or though terminal and reboot. For now XxKOLOHExX is locked lets see what I find ill post back for him.
Click to expand...
Click to collapse
thanks for taking the time to help out, Ill give it a shot
*edit* just tried pushing the eng bootloader through adb and it didnt stick or flash, rebooted into hboot and it still says 0.86.0000, s=on, 26.08.04.30_M3 radio

S-off stuck?

followed some of the guildlines on here about unrooting phone , however it seems no matter what i do S-off will not become S-on, tried the guide to unrooting the automated way, also the Flashing the stock rom way, and the 2.3.4 GB update still stuck with S-off any help would be appreciated

Read saranhai's instructions in this recent thread. Pretty straight-forward and bulletproof.

TeeJay3800 said:
Read saranhai's instructions in this recent thread. Pretty straight-forward and bulletproof.
Click to expand...
Click to collapse
haha thanks TeeJay3800
yea, like i said in the other thread, just follow those instructions and you should be able to get s-on again.

If you have Radio S-OFF, then flashing a stock ROM from RUU or PD15IMG.zip will *not* give you S-ON again. There is already a whole thread about how to get back to S-ON.

cmstlist said:
If you have Radio S-OFF, then flashing a stock ROM from RUU or PD15IMG.zip will *not* give you S-ON again. There is already a whole thread about how to get back to S-ON.
Click to expand...
Click to collapse
Actually it depends on how you turned s-off. IF you use the root.sh version flashing the PD15IMG will turn "s" back on. If you use ./gfree, flashing the PD15IMG will not turn the "s" back on.
I know, I've done it both ways.

neidlinger said:
Actually it depends on how you turned s-off. IF you use the root.sh version flashing the PD15IMG will turn "s" back on. If you use ./gfree, flashing the PD15IMG will not turn the "s" back on.
I know, I've done it both ways.
Click to expand...
Click to collapse
Thank you for the clarification. My understanding is that root.sh does not confer Radio S-OFF but rather fakes it via the ENG HBOOT. Is this a correct assessment?
Ergo if you have true Radio S-OFF (via gfree), then PD15IMG will maintain that S-OFF.
My understanding was that most devs are recommending gfree over root.sh to make things easier to users down the line and reduce the chances of perm-brick. It just means a bit more manual labour.

cmstlist said:
Thank you for the clarification. My understanding is that root.sh does not confer Radio S-OFF but rather fakes it via the ENG HBOOT. Is this a correct assessment?
Ergo if you have true Radio S-OFF (via gfree), then PD15IMG will maintain that S-OFF.
My understanding was that most devs are recommending gfree over root.sh to make things easier to users down the line and reduce the chances of perm-brick. It just means a bit more manual labour.
Click to expand...
Click to collapse
Basically yes. The root.sh is a faux s-off. It works like s-off but not really turning it off. The ./gfree IIRC removes the flags completely. So said person down the road will not have problems.
However with us having two different eMMC chips. The root.sh will turn off the flags for the good eMMC chips, and will not do anything if you have a bad eMMC chip set. While the ./gfree completely removes them. So if you have a good chip or a problematic chip ./gfree will root both.
Now with that being said it's extremely easy for a bad eMMC chipped phone to become bricked. That is why we are seeing so many "Failed-PU" threads popping up. The Partition Update isn't being handled correctly via the eMMC chip, and bricking the device.
all in all use root.sh to root your phone, if that doesn't work use ./gfree with EXTREME caution.

I got a bad eMMC on my Mobilicity Panache, but I decided to take the gamble anyway. So I cautiously went with gfree. Apparently 80% of the "bad" chips will never fail, so... Rolling the dice here.
Anyway to the OP, there's your answer: it depends on how you rooted it.
Sent from my HTC Glacier using Tapatalk

cmstlist said:
I got a bad eMMC on my Mobilicity Panache, but I decided to take the gamble anyway. So I cautiously went with gfree. Apparently 80% of the "bad" chips will never fail, so... Rolling the dice here.
Anyway to the OP, there's your answer: it depends on how you rooted it.
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Hmm guess my old phone was one of the unlucky 20%...
Sent from the HTC Glacier Sense 3.0 using XDA premium app

New DZ seems to be unclocked on gingerbread

UPDATE: Topic title should read 'unlocked'.
Had to start another topic for this. Just recently got my DZ but it came with android 2.3.3 so I thought 'bugger' and thought I would need to downgrade. I bought my phone 'factory unlocked' which I assumed just meant network unlocked.
BUT, I've just booted into the bootloader and it says I'm S-OFF. Does this mean it's a real S-OFF or similar to the engineering HBOOT S-OFF?
Would there be any way to root it without downgrading/custom rom do you think?
Anyone more experienced shed some light?

if it says SHIP S-OFF then you should have true s-off.
In which case getting perm root is simple, follow this guide, but only run the 'Gaining Temp Root' and '
Temp-Rooting to Backup' sections.
This should stick with a reboot, so you will have perm-root.
-Nipqer

Brilliant! This will definitely work even on the stock rom won't it? I only want root for setcpu for underclocking.
Gonna charge it up and give it a shot. Does my hboot version or anything else matter before I try this?
Just for info it says this in bootloader:
VISION PVT SHIP S-OFF
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011,23:36:27
Thanks.

Well I went ahead and tried it and it worked great, I now have root!
I have noticed however that setcpu doesn't appear to allow underclocking with the stock rom. I thought maybe that would be ok. When I move the sliders, nothing changes.
Now that I'm rooted with S-OFF on gingerbread, can I install custom kernels?

If you install rom manager you can install clockworkmod recovery, and install a new rom/kernel through that.
-Nipqer
Sent from my HTC Vision using xda premium

Good stuff, you answered my next question which was how to get clockworkmod on.
Many Thanks.

[Q] Need help turning S ON

so im having a issue with my phone where when i plug the phone in and not always but alot of time just shuts down and boot loops which is why i need to turn s back on so i can send it back into tmobile i tried the one from the true permaroot with the unroot zip and booted to hboot and it continues to say s off does any one know how to fix this?

dfitton said:
so im having a issue with my phone where when i plug the phone in and not always but alot of time just shuts down and boot loops which is why i need to turn s back on so i can send it back into tmobile i tried the one from the true permaroot with the unroot zip and booted to hboot and it continues to say s off does any one know how to fix this?
Click to expand...
Click to collapse
Did you root using the gfree method...?
-Team Inferno
"Quality, not speed"

If you rooted with gfree (and you are), look at the unrooting instructions in gfree thread ("Ultimate S-OFF" in Development section).

yea i used gfree ill look it up and see if it works ty

yea that was the same one i tried before it didnt work

Did you load the original 2.2.1 firmware on the phone, temp-rooted it, and executed gfree with the right flag to make it turn the S-ON back?
I guess you didn't, otherwise it would work.
Please do now.

Jack_R1 said:
Did you load the original 2.2.1 firmware on the phone, temp-rooted it, and executed gfree with the right flag to make it turn the S-ON back?
I guess you didn't, otherwise it would work.
Please do now.
Click to expand...
Click to collapse
How would you execute gfree with the right flag that would make it turn on?

Please read the thread I mentioned in the first of my posts above.