Related
Here's my question. My friend's brother attempted to root his stock Evo using simpleroot instructions I sent my friend 4-5 months ago (pre-2.2) without knowing that simpleroot isn't supported. His phone is now borked. When he tries to load into bootloader, he gets an error (not sure which one), but his phone will boot into android.
What I'm wondering is this: As of yesterday, his phone was updated and current as per sprint and the update commands in the system menus... Can he flash back to an older stock rom via RUU (such as this one) without causing other problems? If my understanding is correct, the latest sprint updates aren't yet rootable, right?
Any help on this issue?
Thanks
Is the phone s-off?
Sent from my PC36100 using XDA App
badutahboy said:
Here's my question. My friend's brother attempted to root his stock Evo using simpleroot instructions I sent my friend 4-5 months ago (pre-2.2) without knowing that simpleroot isn't supported. His phone is now borked. When he tries to load into bootloader, he gets an error (not sure which one), but his phone will boot into android.
What I'm wondering is this: As of yesterday, his phone was updated and current as per sprint and the update commands in the system menus... Can he flash back to an older stock rom via RUU (such as this one) without causing other problems? If my understanding is correct, the latest sprint updates aren't yet rootable, right?
Any help on this issue?
Thanks
Click to expand...
Click to collapse
No, you can not run an older ruu. If he updated to today or yesterdays update hes stuck. If he is on HBOOT 2.02 he can flash the 3.30.651.3 ruu or ths 3.70.651.1 but you can not ruu further back.
animal7296 said:
No, you can not run an older ruu. If he updated to today or yesterdays update hes stuck. If he is on HBOOT 2.02 he can flash the 3.30.651.3 ruu or ths 3.70.651.1 but you can not ruu further back.
Click to expand...
Click to collapse
Are either of these rootable yet?
and can someone explain what S-on and off means?
badutahboy said:
Are either of these rootable yet?
and can someone explain what S-on and off means?
Click to expand...
Click to collapse
Yes, they're both rootable.
S-ON vs S-OFF; is just basically a security parameter that's being locked/unlocked. This allows for PC36IMG's files to be flashed via the bootloader without having to use or have authenticated signature keys from Google.
Basically, if you ever accept an OTA and it flashes and removes your recovery (CWM or Amon_RA); then you have no way of flashing custom roms/mods, etc... however with S-OFF, you have the ability to get your recovery back and set yourself back to root if need be.
Essentially, S-OFF allows for another method of flashing stuff to the phone besides just using the CWM or Amon_RA recoveries.
Hboot versions however can affect S-OFF; so it's important that if there is a new OTA that you always hold off, until a developer can validate that the hboot can be exploited and that the OTA can be rooted.
badutahboy said:
Are either of these rootable yet?
and can someone explain what S-on and off means?
Click to expand...
Click to collapse
1. 2.02 is rootable 2.10 is not and is the newest one.
2.0 S-ON means you can not flash roms s-off means you can. It is the security of the phone kind of.
If you can not get into bootloader then you can try running the oldest ruu and then the next. It wont hurt the phone at all (I just did it today) it will just give you an error and reboot the phone.
pseudoremora said:
Yes, they're both rootable.
S-ON vs S-OFF; is just basically a security parameter that's being locked/unlocked. This allows for PC36IMG's files to be flashed via the bootloader without having to use or have authenticated signature keys from Google.
Basically, if you ever accept an OTA and it flashes and removes your recovery (CWM or Amon_RA); then you have no way of flashing custom roms/mods, etc... however with S-OFF, you have the ability to get your recovery back and set yourself back to root if need be.
Essentially, S-OFF allows for another method of flashing stuff to the phone besides just using the CWM or Amon_RA recoveries.
Hboot versions however can affect S-OFF; so it's important that if there is a new OTA that you always hold off, until a developer can validate that the hboot can be exploited and that the OTA can be rooted.
Click to expand...
Click to collapse
Thanks for the explanations and the help.
How do I find out if it's S-on or off, and is it possible to change?
pseudoremora said:
Yes, they're both rootable.
S-ON vs S-OFF; is just basically a security parameter that's being locked/unlocked. This allows for PC36IMG's files to be flashed via the bootloader without having to use or have authenticated signature keys from Google.
Basically, if you ever accept an OTA and it flashes and removes your recovery (CWM or Amon_RA); then you have no way of flashing custom roms/mods, etc... however with S-OFF, you have the ability to get your recovery back and set yourself back to root if need be.
Essentially, S-OFF allows for another method of flashing stuff to the phone besides just using the CWM or Amon_RA recoveries.
Hboot versions however can affect S-OFF; so it's important that if there is a new OTA that you always hold off, until a developer can validate that the hboot can be exploited and that the OTA can be rooted.
Click to expand...
Click to collapse
I have been trying to root 2.10 since yesterday and it has proven to not be possible as of yet. If you have a rooting method that works for me then would you share please?
animal7296 said:
I have been trying to root 2.10 since yesterday and it has proven to not be possible as of yet. If you have a rooting method that works for me then would you share please?
Click to expand...
Click to collapse
Im with u brotha im stuck on 2.10 from a mistake i made. Was originally on 0.76.2
Sux man
Sent from my PC36100 using Tapatalk
badutahboy said:
Thanks for the explanations and the help.
How do I find out if it's S-on or off, and is it possible to change?
Click to expand...
Click to collapse
To see if you're S-OFF or S-ON; you can boot your phone into bootloader mode.
To do this:
1. Power down the phone
2. Hold the Volume Down + Power button
3. You'll see a white screen with three little Androids
4. Read the very top of the screen; should tell you if you are S-ON or S-OFF.
You can reboot afterwards.
And yes, you can switch from the S-ON to S-OFF and vise versa, though I don't see why you would want to do the latter.
animal7296 said:
I have been trying to root 2.10 since yesterday and it has proven to not be possible as of yet. If you have a rooting method that works for me then would you share please?
Click to expand...
Click to collapse
luckylui said:
Im with u brotha im stuck on 2.10 from a mistake i made. Was originally on 0.76.2
Sux man
Click to expand...
Click to collapse
I apologize to the both of you guys; I was under the impression that 2.10 was S-OFF, apparently testing is still being done. For now, looks like you'll have to sit tight. Sorry guys.
pseudoremora said:
To see if you're S-OFF or S-ON; you can boot your phone into bootloader mode.
To do this:
1. Power down the phone
2. Hold the Volume Down + Power button
3. You'll see a white screen with three little Androids
4. Read the very top of the screen; should tell you if you are S-ON or S-OFF.
You can reboot afterwards.
And yes, you can switch from the S-ON to S-OFF and vise versa, though I don't see why you would want to do the latter.
I apologize to the both of you guys; I was under the impression that 2.10 was S-OFF, apparently testing is still being done. For now, looks like you'll have to sit tight. Sorry guys.
Click to expand...
Click to collapse
However it has been verified that if you were S-OFF on 2.02 you can install the OTA and you will end up with HBOOT 2.10 with S-OFF.
pseudoremora said:
To see if you're S-OFF or S-ON; you can boot your phone into bootloader mode.
To do this:
1. Power down the phone
2. Hold the Volume Down + Power button
3. You'll see a white screen with three little Androids
4. Read the very top of the screen; should tell you if you are S-ON or S-OFF.
You can reboot afterwards.
And yes, you can switch from the S-ON to S-OFF and vise versa, though I don't see why you would want to do the latter.
I apologize to the both of you guys; I was under the impression that 2.10 was S-OFF, apparently testing is still being done. For now, looks like you'll have to sit tight. Sorry guys.
Click to expand...
Click to collapse
No prob pimp
Ima call sprint n see if i can some how get me a phone w the 2.02 hboot and just pretty much get an upgrade from 0003 hardware to 0004 Lol
Im like jumpy rite now ahaha
Sent from my PC36100 using Tapatalk
tpbklake said:
However it has been verified that if you were S-OFF on 2.02 you can install the OTA and you will end up with HBOOT 2.10 with S-OFF.
Click to expand...
Click to collapse
True this, but when i did it i was at 0.76.2 and now screw at 2.10 cause it updated all the way n i didnt want to do that.. Got lost in the tangle haha
Sent from my PC36100 using Tapatalk
tpbklake said:
However it has been verified that if you were S-OFF on 2.02 you can install the OTA and you will end up with HBOOT 2.10 with S-OFF.
Click to expand...
Click to collapse
Yea, I heard about this in the IRC; too bad these guys can do that... unfortunate; but I'm sure the Unrevoked team will have a fix soon enough.
luckylui said:
No prob pimp
Ima call sprint n see if i can some how get me a phone w the 2.02 hboot and just pretty much get an upgrade from 0003 hardware to 0004 Lol
Im like jumpy rite now ahaha
Click to expand...
Click to collapse
Good luck with Sprint; I don't know how helpful they're going to be, but you never know...
@luckylui and animal7296, check out the 2.02/2.10 rooting thread again, it seems they got something working. Good luck.
badutahboy said:
Here's my question. My friend's brother attempted to root his stock Evo using simpleroot instructions I sent my friend 4-5 months ago (pre-2.2) without knowing that simpleroot isn't supported. His phone is now borked. When he tries to load into bootloader, he gets an error (not sure which one), but his phone will boot into android.
What I'm wondering is this: As of yesterday, his phone was updated and current as per sprint and the update commands in the system menus... Can he flash back to an older stock rom via RUU (such as this one) without causing other problems? If my understanding is correct, the latest sprint updates aren't yet rootable, right?
Any help on this issue?
Thanks
Click to expand...
Click to collapse
There actually is a way to downgrade without rooting, all you need to do is flash the mtd-eng.img file to your misc partition as explained in toast's rooting part 2 thread. After you do that it will let you flash any ruu that is compatible with your phone
Sent from my PC36100 using XDA App
So I'm ending Verizon and need to give my phone to best buy for the buyback program but I don't think they will take it running rooted I know the new ota is out but what do I do to do this ota do I flash a froyo stock rom? Or ...
Help me out guys thanks alot ill miss my incredible and y'all aswell
Ill be getting att infuse 4g over the HTC inspire 4g I think..
Sent from my NookColor using Tapatalk
I'd put it back to stock 2.2. There are a couple "get back to stock" threads in the development section, basically you'll just have to flash the S-ON zip in recovery, then flash the stock 2.2 RUU.
Just wondering, does Verizon refuse to work on your phone if it is rooted? Different scenarios:
1) Hardware issue. Do they care if it is S-Off and has a custom ROM?
2) Will they not even touch a phone that is obviously rooted?
3) Do they care about S-Off when you take it in?
Evo 4G over here, Sprint works on rooted phones. If it is a software issue they will RUU you, but won't mess with S-Off
Thanks! this is helpful
tropicalbrit said:
Just wondering, does Verizon refuse to work on your phone if it is rooted?
Click to expand...
Click to collapse
I personally would return the phone to stock before returning it for a hardware issue, but I think most Verizon employees (a) don't care about rooting because their phones are probably rooted as well, or (b) wouldn't even know what S-OFF means or what to look for to determine if a phone's rooted. This is assuming you're just going in to your neighborhood Verizon store for a few questions or something, not for warranty issues, those people that receive the phones might look for root, who knows?
I think there's a lot more paranoia about rooting and Verizon's stance on it than is warranted though. I've seen all sorts of rumors about Verizon "tracking" rooted users, or building a database of rooted phones. Those kind of rumors have been going on for a while with no sort of confirmation or anything whatsoever coming from them.
FWIW, I've returned a rooted, s-off Incredible, with an Unrevoked splash screen to Verizon for a warranty repair. The employee did not care. (or maybe they just didn't have a clue.)
k_nivesout said:
I'd put it back to stock 2.2. There are a couple "get back to stock" threads in the development section, basically you'll just have to flash the S-ON zip in recovery, then flash the stock 2.2 RUU.
Click to expand...
Click to collapse
Question
I flash both at the same time like
S-on tool then right away stock ruu?
Sent From My Optimized HTC Incredibly Dinc
The timing doesn't really matter, but the S-ON zip has to be flashed in recovery whereas the RUU is flashed in hboot. The RUU replaces CWM recovery with the stock recovery, and you couldn't flash the S-ON zip with the stock recovery. But it shouldn't matter as far as flashing the RUU *right* after the S-ON zip, since the RUU is official HTC firmware, you can flash it with S-ON, anytime. Bear in mind that you can't downgrade with S-ON though, for example, if you flash the 2.3 RUU (with S-ON) there's no way to get back to 2.2.
Thinking about it, even if you flashed the RUU first, you still have S-OFF, so would be free to install a custom recovery & superuser then flash back to whatever.
Ok so I got impatient and installed the Gingerbread update that VZW pushed out a week or so ago, found the file here since I wasnt one of the lucky few to get the OTA push. I flashed it through HBOOT since it was a signed file, please note that I'm not rooted and the phone is completely stock. I want to go back to 2.2 stock and wait for the official, and apparently I'm not doing something right. running the RUU for the 2.2 gives me a bootloader version error, and dropping the zip named PB31IMG.zip and flashing through hboot gives me the "main version is older" error. I have tried installing Unrevoked 3 and it gets past the last reboot, after "waiting for system to settle" message, it says "running root" for a few minutes then says "unable to get root, is your firmware too new?"
...so yea, I'm guessing I'm S.O.L.? Sorry kinda noob here, came from the Eris forum, I guess theres a few things that are different.
What problems are you having with the RUU that you flashed? You can't downgrade, as you found out, so being stock S-ON you don't have many options other than flashing a different 2.3 stock image, and/or waiting for the actual OTA.
resyek83 said:
Ok so I got impatient and installed the Gingerbread update that VZW pushed out a week or so ago, found the file here since I wasnt one of the lucky few to get the OTA push. I flashed it through HBOOT since it was a signed file, please note that I'm not rooted and the phone is completely stock. I want to go back to 2.2 stock and wait for the official, and apparently I'm not doing something right. running the RUU for the 2.2 gives me a bootloader version error, and dropping the zip named PB31IMG.zip and flashing through hboot gives me the "main version is older" error. I have tried installing Unrevoked 3 and it gets past the last reboot, after "waiting for system to settle" message, it says "running root" for a few minutes then says "unable to get root, is your firmware too new?"
...so yea, I'm guessing I'm S.O.L.? Sorry kinda noob here, came from the Eris forum, I guess theres a few things that are different.
Click to expand...
Click to collapse
The only way i know to get back to 2.2 is to s-off your phone then ruu the 2.2. which will get you back to s-on 2.2, but you will be get the update nag every day once they start pushing the OTA out again.
resyek83 said:
Ok so I got impatient and installed the Gingerbread update that VZW pushed out a week or so ago, found the file here since I wasnt one of the lucky few to get the OTA push. I flashed it through HBOOT since it was a signed file, please note that I'm not rooted and the phone is completely stock. I want to go back to 2.2 stock and wait for the official, and apparently I'm not doing something right. running the RUU for the 2.2 gives me a bootloader version error, and dropping the zip named PB31IMG.zip and flashing through hboot gives me the "main version is older" error. I have tried installing Unrevoked 3 and it gets past the last reboot, after "waiting for system to settle" message, it says "running root" for a few minutes then says "unable to get root, is your firmware too new?"
...so yea, I'm guessing I'm S.O.L.? Sorry kinda noob here, came from the Eris forum, I guess theres a few things that are different.
Click to expand...
Click to collapse
For the moment, I think you are SOL, only because the same thing happened to me.
If you have 2.3.4 and S-ON, there's not really a way to downgrade back to 2.2, as HBOOT won't allow a downgrade. In fact, only PB31IMG.zip files that are signed by HTC will allow to be flashed. All others will not be recognized by HBOOT.
Unrevoked will no longer root after you have flashed RUU and have S-ON. You will get the error you are describing.
I have also tried newer root tools, such as Revolutionary, which is in the Beta phase.
Unfortunately, this method is not supported for the Incredible, and per Unrevoked's support channel on IRC, this is not likely, as apparently a phone that is only over a year old is considered a 'Legacy' device.
At this point we can only hope for the following:
HTC unlocks the Bootloader for the Droid Incredible on HTCdev.com. Only a handful of devices are listed at the moment.
Team Unrevoked releases a new version of Unrevoked that can find an exploit for 2.3.4 and enable root.
Revolutionary adds support for 'legacy' devices such as the incredible.
We are in a small minority, but hopefully enough devices will get the OTA, or refurbs get sent out with 2.3.4 that users will eventually require a new way to root.
Hang in there.
Yeah, if you're s on then from everything I've read, your screwed for now.
ahh ok....yea i kinda figured. I should have done a tad more research before I did it....everything works ok at the moment, except my battery life isnt as good as it was, but its not terrible. I guess I'll wait for the official OTA or wait and see if Unrevoked can come up with a solution.
your best option woulda been to root first. While you still had S-off flash the file you found here. Then if you wanted you could have reinstalled Clockwork recovery and superuser and either flash a stock rom or unroot. whats killing you is S-on.
TheBr0ken said:
your best option woulda been to root first. While you still had S-on flash the file you found here. Then if you wanted you could have reinstalled Clockwork recovery and superuser and either flash a stock rom or unroot. whats killing you is S-off.
Click to expand...
Click to collapse
Doing that with S-On is what has OP in this position in the first place. You have the right idea but mixed up S-On and S-Off.
TheBr0ken said:
your best option woulda been to root first. While you still had S-on flash the file you found here. Then if you wanted you could have reinstalled Clockwork recovery and superuser and either flash a stock rom or unroot. whats killing you is S-off.
Click to expand...
Click to collapse
Thank you, Captain Hindsight. In my situation, I was coming from a Rooted, 2.3 Sense 3.0 ROM, with S-Off.
I believe S-off is swicthed back to S-ON when you flash the RUU.
In the mean time, my phone is borked. Too new of a firmware on too "old" of a device.
SlimSnoopOS said:
Doing that with S-On is what has OP in this position in the first place. You have the right idea but mixed up S-On and S-Off.
Click to expand...
Click to collapse
yup, fixed.
deadsoulboy said:
Thank you, Captain Hindsight. In my situation, I was coming from a Rooted, 2.3 Sense 3.0 ROM, with S-Off.
I believe S-off is swicthed back to S-ON when you flash the RUU.
In the mean time, my phone is borked. Too new of a firmware on too "old" of a device.
Click to expand...
Click to collapse
what killed you was you musta flashed the s-on patch for some reason. I ran the same file you did. I still have s-off
The RUU does NOT turn the security flag to -ON. You do lose root until you flash a custom recovery and superuser, which is done easily.
Any hope for us S-ONs with 2.3.4? Is there something by way of unrevoked or something we can flash to try and get back to root?
There has to be something...
So I have a droid inc that I'm sending back in, and I want to revert it to stock. Right now, I'm running s-off, with a rooted stock OTA 2.3.4 (Incubusj's, I think) with the latest CWM. What do I need to do to make this thing bone stock to return it? I've done a search, and maybe I just suck at searching, but I can't find good, concise directions, and I don't want to screw it up.
sk8erord said:
So I have a droid inc that I'm sending back in, and I want to revert it to stock. Right now, I'm running s-off, with a rooted stock OTA 2.3.4 (Incubusj's, I think) with the latest CWM. What do I need to do to make this thing bone stock to return it? I've done a search, and maybe I just suck at searching, but I can't find good, concise directions, and I don't want to screw it up.
Click to expand...
Click to collapse
Search for the Ultimate get back to stock thread. It'll tell you what you need to to to get back to Stock 2.2 with S-ON.
That thread seems rather old. I'm running the 2.15.10.07.07 radio on hboot .92. Do I still just run the s-on and then run the RUU?
Well, was probably unnecessary, but I reverted to the old radio, flashed a rooted stock rom, then ran s-on through recovery, then a stock pb31img rom through bootloader. So it is bone stock again.
sk8erord said:
That thread seems rather old. I'm running the 2.15.10.07.07 radio on hboot .92. Do I still just run the s-on and then run the RUU?
Click to expand...
Click to collapse
True, that thread is old, but the info is still good. Good call on reverting back the radio, as you don't want that to cause any troubles. Pretty easy to get back to stock and S-ON huh?
This was probably asked before but I couldn't find anything on my searches...
I need to return my phone since I got a refurb'd but I'm having issues turning it back to S-ON... has anyone returned their phone with S-OFF? Did they attempt to charge your account or something to that effect? I can definitely do the RUU and return it to stock unrooted but the bootloader shows S-OFF as well as the 6.17 Hboot instead of S-ON and 2.16 Hboot...
TIA!
gqukyo said:
This was probably asked before but I couldn't find anything on my searches...
I need to return my phone since I got a refurb'd but I'm having issues turning it back to S-ON... has anyone returned their phone with S-OFF? Did they attempt to charge your account or something to that effect? I can definitely do the RUU and return it to stock unrooted but the bootloader shows S-OFF as well as the 6.17 Hboot instead of S-ON and 2.16 Hboot...
TIA!
Click to expand...
Click to collapse
Well they can't really do anything about us rooting phones since the supreme court says we can do whatever the hell we want to devices we paid for, thanks to the Apple lawsuit. However rooting voids your warranty so I suppose the question is why are you returning. If you are returning it because it's in some way physically defective, you *might* be ok. But if it has malfunctioned, it could bite you in the ass. More information would be helpful.
You should also realize that Sprint has been very inconsistent on this issue. There are those who have had warranty work/returns done and had no issues with it having S-Off and even custom roms still installed. Then there are those who have gotten caught. It should also be pointed out that this is in your contract, so please don't be one of those guys that get denied then RAGE about it on these forums. When you rooted, you clicked a box that said "Your warranty is now void" or at least read that somewhere I am certain! Anyway more info pls, or try it anyway and good luck! Worst thing they will do is give you the phone back and void your warranty totally. You could always toss it in the sink for a few hours then file insurance claim on it.
gqukyo said:
This was probably asked before but I couldn't find anything on my searches...
I need to return my phone since I got a refurb'd but I'm having issues turning it back to S-ON... has anyone returned their phone with S-OFF? Did they attempt to charge your account or something to that effect? I can definitely do the RUU and return it to stock unrooted but the bootloader shows S-OFF as well as the 6.17 Hboot instead of S-ON and 2.16 Hboot...
TIA!
Click to expand...
Click to collapse
I tried returning my Evo with S-Off, and the person who was looking at it recognized it in the bootloader. He said "I personally used Revolutionary too. Sadly, we can't return this."
I was able to find a solution, however. Download the zip file attached to this forum post, rename it to PC36IMG.zip, and place on the root of your SD card. Boot into your bootloader. You will be prompted to update. Choose yes. It should flash quick. When it asks you to reboot, choose yes and reboot back into the bootloader. It should show S-ON with 6.17 HBOOT. From there flash your RUU and you should be back to 2.16 HBOOT with S-ON!
I got a refurb a couple months ago and it arrived S-OFF, so I dunno
Thank you all for your responses. I did try to run the RUU and Captain Throwback's S-ON zip but no luck, I'll probably just unroot and RUU it back to the newest firmware and just return it like that. Since borrowedchief said he received his with S-OFF, its probably a hit or miss as most other things at Sprint...
I just sent my old phone back with S-OFF. My issue though was power cycling. Sprint even credited me the $100 premium for my insurance because they failed to replace my phone before it had water damage. I took the phone in multiple times with no luck. Finally the Tech told me I had good news and bad news. Good news, you are getting a new phone. Bad news you have to pay $100 because you have water damage. The first Rep I talked to said we should have replaced the phone the first time. Credited me the money once they received my old phone.
I just returned my phone a few days ago with the s-off but i did have the original rom on the phone. They didnt say anything to me and when i received the new phone, the s was also off.......
Obviously the official rule is that they dont take them back S-off... Some people get lucky and either get a lazy rep or a rep that wants to be nice... It's a gamble
richp1970 said:
I just returned my phone a few days ago with the s-off but i did have the original rom on the phone. They didnt say anything to me and when i received the new phone, the s was also off.......
Click to expand...
Click to collapse
I returned mine too but the terms state that they have up to 2 billing cycles to charge us for any damages or whatnot... guess we'll see...
Their policies at sprint are now that they service rooted phones meaning with S-off they just RUU back up to the latest and it usually reflashes over ENG hboot and other things meaning that it's just gonna be s-on when you get it.
I rooted my phone and is s-off too and cant get it back to s-on
gqukyo said:
This was probably asked before but I couldn't find anything on my searches...
I need to return my phone since I got a refurb'd but I'm having issues turning it back to S-ON... has anyone returned their phone with S-OFF? Did they attempt to charge your account or something to that effect? I can definitely do the RUU and return it to stock unrooted but the bootloader shows S-OFF as well as the 6.17 Hboot instead of S-ON and 2.16 Hboot...
TIA!
Click to expand...
Click to collapse
Originally Posted by Captain_Throwback
Here I will post my 2.16 hex-edited HBOOT to appear as 6.17. I'm not really a good person to put together a guide, but I can give you this file, which should at least help.
I TAKE NO RESPONSIBILITY IF YOU (SOMEHOW) BRICK YOUR DEVICE. FOLLOW THESE INSTRUCTIONS AT YOUR OWN RISK!!!
Also note that I have 0003 hardware, so there are no guarantees that this will work for you! That being out of the way, let me continue . . .
I used AndroidFlasher to flash this HBoot, as it was extremely easy (just renamed to HBOOT.img). Flashing through Fastboot (directly on the device) might also work, I guess, if you rename the file to PC36IMG, but I didn't try it that way.
I was able to do this successfully on Windows XP 32-bit (I always have issues getting anything to work on my Windows 7 machine), so I'm not sure how (or if) it'll work on Vista or 7 (or on 64-bit versions).
Note that if you're doing this with your device connected to your computer, USB Debugging MUST BE TURNED ON!!
If you want to return to stock, I first recommend flashing a stock ROM. I recommend the most recent Gingerbread update, which can be found in this post (RUU can be found here).
After successfully un-rooting your device by flashing the unrooted ROM from above, now we must re-lock NAND (set S-ON). Basically, you just flash the hboot.img from the attached zip file, and it will set your device HBOOT version to 6.17, and re-lock your NAND (S-ON). Then, you can re-flash the ROM from the above step, and it *should* overwrite the hex-edited HBOOT with the "official" version, and restore your device to stock.
Again, this worked for me, but if it doesn't work for you, don't go blaming me, and calling my method a sham.
Thanks to {ParanoiA} for posting the link to the thread where the hex-editing was mentioned, and thanks to thefredelement (from that thread) for posting a working method!
Maybe someone else can test my method and confirm it works for them & others, and then put a real guide together, for everyone else (like me) that needs to return their device for service after rooting with Revolutionary.
Thanks man! I rooted gingerbread 2.3.3 with revolutionary and try to unroot with unrevoked foreverson.zip but no luck because I didn't use there method to root. Hours and hours of research came accross your thread and all I can say thank you.
*****Very important to complete last step because if you don't you will have S-on but your HBOOT will be 6.1... For my last step I didn't flash using HBOOT I just downloaded RUU most current file because my phone came with 4.24.651.1 I just ran RUU booted back to white screen and HBOOT now shows HBOOT 2.1
Here you should use this method. It was origanally posted by captainthrowback and thanks to him now im back to s-on I was rooted and went back to stock but had s-off and I used this method to go back to s-on and it worked. My evo is on hardware v0004 and it worked fine too. Hope this method works for you to. Good Luck. Have any other questions just ask
To get charging port and home button fixed. I have insurance and my phone is rooted. They have to repair it right? I remember reading on here that rooted phones can be worked on by sprint employees now. True, correct?
Wrong. My friend is a tech at the local Sprint Store and I asked her about that. Her answer was hysterical laughing.
You may want to try and flash a Stock Rom first.
I thought they had to repair them now?
Sorry, you thought wrong.
So should I just unroot and take it in? I don't mind. I think when I took it in last time the rep said he couldnt fix it cuz it was rooted and it was the charging port that tiem too.
You can. I just keep my stock/rooted setup in a Nandroid, in case that ever happens ,so I can roll back to Stock without unrooting. I don't think they'd check for S-off, but you never know
Ill just unroot. I can use djrez's method to unroot if my bootloader doesnt say revolutionary at the top right? I am pretty sure i used unrevoked forever to unroot.
DRatJr said:
Ill just unroot. I can use djrez's method to unroot if my bootloader doesnt say revolutionary at the top right? I am pretty sure i used unrevoked forever to unroot.
Click to expand...
Click to collapse
If you used unrevoked then you can just flash s-on & RUU. You may have to downgrade your radio to get the s-on zip to work.
If you're taking it in for a bad usb port, they'll most likely replace it instead of trying to fix it.
Sent from my PC36100 using Tapatalk
I plan to flash the S-ON then let hboot upgrade to the PC36IMG that is in DJREZ's unroot thread. Woudl that be sufficient enough?
DRatJr said:
I plan to flash the S-ON then let hboot upgrade to the PC36IMG that is in DJREZ's unroot thread. Woudl that be sufficient enough?
Click to expand...
Click to collapse
how do i get S-ON on my evo when i used unrevoked3 not unrevoked forever...is there like a zip file for that
weztcoazt said:
how do i get S-ON on my evo when i used unrevoked3 not unrevoked forever...is there like a zip file for that
Click to expand...
Click to collapse
Unroot method is the same. Unrevoked 3 had Forever built in.
Sent from my PC36100 using Tapatalk
DONT ever flash s-on haha i've taken my evo to get fixed a couple of times and they're never checked for s-off. I guess you could though if you were getting a replacement.
Well I'm trading the phone in for a different....my evo looks stock but still with the s-off. My evo says a mandatory update is available n I'm wondering what that will do lol
Sent from my PC36100 using XDA App
HipKat said:
Wrong. My friend is a tech at the local Sprint Store and I asked her about that. Her answer was hysterical laughing.
You may want to try and flash a Stock Rom first.
Click to expand...
Click to collapse
This document was leaked a little while ago, have they since rescinded the policy?
It was 3 weeks ago when I talked to her
Khilbron said:
This document was leaked a little while ago, have they since rescinded the policy?
Click to expand...
Click to collapse
Nope. But not all service locations/employees have fallen in line behind the policy either.
KJ
HipKat said:
Sorry, you thought wrong.
Click to expand...
Click to collapse
Actually, you're wrong.
If the issue has nothing to do with being rooted, why would it matter? If a phone comes into my service center with software issues that's rooted, then yes it pertains to the issue. Digitizer out? Root has nothing to do with it. I leave it the way it is and repair.
weztcoazt said:
how do i get S-ON on my evo when i used unrevoked3 not unrevoked forever...is there like a zip file for that
Click to expand...
Click to collapse
Yea. If u are s-off and used unrevoked to root, then you need 2 downgrade ur radio to 2.05.xx.xx and then flash the s-on zip. After that if ur back to s-on just flash the 3.70 pc36img
Sent From My Pocket