Develop Bugs

[REQ][HOW TO] Relock or Unroot EVO

I have been searching the web for how to relock my EVO. This is because i am taking it back to sprint for a screen fix and I have learned from the PPCGEEKS thread all the problems and warranty stuff related to rooting as well as the odds of them discovering that I have rooted it. I just don't want to risk it and I would like to know how to relock, just for the knowledge.
Does anyone have specific instructions how??
PPCGEEKS Thread: http://forum.ppcgeeks.com/showthread.php?t=126849

http://shipped-roms.com/shipped/Supersonic/
Download first and last, and flash in the same sequence.

So thats all?? its done? It's unrooted? That seems simple.

Yep, that's how easy it is.
On some phones (one out 5 I "control") I had to get all 3 and flash in the same sequence, otherwise last one wouldn't flash over the first - not sure why.

redsolar said:
last one wouldn't flash over the first - not sure why.
Click to expand...
Click to collapse
that surprises me. the latest RUU should flash over anything *theoretically*.
what error did it give you when you attempted?
yes, it should be easy to restore the phone to stock. think of all their service departments fixing/refurb'n phones. one simple flash and its all completely stock no matter what was loaded before.
for those more technically included, since this is the dev board, if the eng build RUU is loaded the PRI is downgraded and as of now, no currently released RUU is able to upgrade the PRI ... but thats such a small issue, can almost guarantee nobody will notice.

Damn screen... I have to do the same thing, and just one other question, besides those files I will just have to use Htc Sync to flash them right?

Yellowcard8992 said:
Damn screen... I have to do the same thing, and just one other question, besides those files I will just have to use Htc Sync to flash them right?
Click to expand...
Click to collapse
Those RUUs are just exe files. So sync will provide you with drivers yes, but after downloading you just run from that download with your phone plugged in.

wow after reading that thread on ppcgeeks i dont think i ever want to leave xda! must be a young crowd over there. i ran the latest 1.47 RUU that i downloaded from HTC before I returned my phone. much to my surprise they didn't even take the phone out of the box! still, since it only takes 10 minutes might as well do it.

barnacles10 said:
Those RUUs are just exe files. So sync will provide you with drivers yes, but after downloading you just run from that download with your phone plugged in.
Click to expand...
Click to collapse
are you talking about just using the volume down and power button method?

redsolar said:
Yep, that's how easy it is.
On some phones (one out 5 I "control") I had to get all 3 and flash in the same sequence, otherwise last one wouldn't flash over the first - not sure why.
Click to expand...
Click to collapse
whats the point in running all 3 on a phone you are returning? just running the first one is good enough to unroot and restore to stock. i only ran the most recent one, because i had already upgraded the baseband and was unable to run the earlier ones because of it.

joeykrim said:
that surprises me. the latest RUU should flash over anything *theoretically*.
what error did it give you when you attempted?
yes, it should be easy to restore the phone to stock. think of all their service departments fixing/refurb'n phones. one simple flash and its all completely stock no matter what was loaded before.
for those more technically included, since this is the dev board, if the eng build RUU is loaded the PRI is downgraded and as of now, no currently released RUU is able to upgrade the PRI ... but thats such a small issue, can almost guarantee nobody will notice.
Click to expand...
Click to collapse
I was surprised too when I tried first.
The 1.47 RUU just sat on the "waiting for bootloader" screen and timed out after ~90 seconds, "unable to find phone" (tried multiple times) and the screen would get stuck in white bootloader/RUU message (battery pull required) - so i am guessing 0.76.2 bootloader was too low for it. That was flashing from 3.2.2+ DamageControl ROM, didn't try from any other one, since the DC -> 1.36 -> 1.47 stock worked well.
And yes, the PRI caveat is there, but as joeykrim said, that's minor, plus you can always say "PRI what - huh?", right?

OneStepAhead said:
whats the point in running all 3 on a phone you are returning? just running the first one is good enough to unroot and restore to stock. i only ran the most recent one, because i had already upgraded the baseband and was unable to run the earlier ones because of it.
Click to expand...
Click to collapse
Running latest OTA makes you seem more of a "dumb user" who wouldn't even know what root is?

Yellowcard8992 said:
are you talking about just using the volume down and power button method?
Click to expand...
Click to collapse
No. RUUs are handled differently. You download the file. And run it on your computer with the phone plugged in. It does everything for you. You DO NOT flash these via recovery.

Update on my phone
I took it to the sprint store yesterday and against everything I have heard the guy at the store turned my phone and checked it. Thank god I used redsolar's posted method. I must have the appearance of someone who would root there phone. It passed his inspection, luckily.
Thanks for the help

I rooted with the new Simpleroot OTA Edition, with Fresh Rom 053, and RA-Rec.
I'm trying to start over from stock so I can re-root my phone, but I can't get the RUU's to work. The oldest one will actually try and put the phone in bootloader, but while its waiting for bootloader it eventually just stops and gives me the 170 error, usb connector problem.
So is there any other way to go about this? Any help would be greatly appreciated.

murdercitydan said:
I rooted with the new Simpleroot OTA Edition, with Fresh Rom 053, and RA-Rec.
I'm trying to start over from stock so I can re-root my phone, but I can't get the RUU's to work. The oldest one will actually try and put the phone in bootloader, but while its waiting for bootloader it eventually just stops and gives me the 170 error, usb connector problem.
So is there any other way to go about this? Any help would be greatly appreciated.
Click to expand...
Click to collapse
ya what I do is replug the usb coord then try ruu again while the phone is stuck on the HTC sign,then if that doesn't work I just manually go into bootloader myself (power+volume down) then use the ruu.exe, works everytime but then it tells me my current version is not valid, so if you ota'd you probably won't ever be able to go back to 1.32.651.1/.6 stock but you can just use the new 1.47.651.1 ruu to regain stock after ota.

Tundricles said:
ya what I do is replug the usb coord then try ruu again while the phone is stuck on the HTC sign,then if that doesn't work I just manually go into bootloader myself (power+volume down) then use the ruu.exe, works everytime but then it tells me my current version is not valid, so if you ota'd you probably won't ever be able to go back to 1.32.651.1/.6 stock but you can just use the new 1.47.651.1 ruu to regain stock after ota.
Click to expand...
Click to collapse
Thanks a **** load Tundricles, you saved my ass.
I was getting so pissed, I'd run the RUU and once it got to opening the bootloader on my phone it was get frozen on the HTC screen, and the RUU would get the use connection error. So I unplugged my phone, and noticed it was in the bootloader, but if the usb was plugged in, it wouldn't show the bootloader screen for some reason. So I just plugged it back in and started the RUU back up, it instantly went past the "Waiting for bootloader..." message and started updating.
Thank you, and for anyone else having similar problems, READ THIS!

Flashing the RUU doesn't restore the stock recovery does it?
I ran Unrevoked 2 a while back and I have RUU'd but I'm pretty sure Clockwork Mod is still there.
Sent from my EVO 4G using the XDA App.

ViViDboarder said:
Flashing the RUU doesn't restore the stock recovery does it?
I ran Unrevoked 2 a while back and I have RUU'd but I'm pretty sure Clockwork Mod is still there.
Sent from my EVO 4G using the XDA App.
Click to expand...
Click to collapse
It should. RUU replaces everything but PRI
Sent from my PC36100 using XDA App

murdercitydan said:
Thanks a **** load Tundricles, you saved my ass.
I was getting so pissed, I'd run the RUU and once it got to opening the bootloader on my phone it was get frozen on the HTC screen, and the RUU would get the use connection error. So I unplugged my phone, and noticed it was in the bootloader, but if the usb was plugged in, it wouldn't show the bootloader screen for some reason. So I just plugged it back in and started the RUU back up, it instantly went past the "Waiting for bootloader..." message and started updating.
Thank you, and for anyone else having similar problems, READ THIS!
Click to expand...
Click to collapse
np glad I could help

[Q] Can anybody help me out, please?

I've searched the forums and have not found a situation that really matches mine.
I've been running on a Cyanogen nightly build for probably two months with no problems. Out of nowhere this morning my phone reboots itself (while it was idle; I wasn't even touching it) and then gets stuck in a boot loop. I get the White HTC Evo 4G screen, then it powers off and comes back up to the white screen again. Over and over.
All I can get do is hboot. Even telling hboot to go into the recovery mode puts my back into the boot loop. Fastboot, clear storage, and hboot usb all seem to work though. I've tried downloading the PC36IMG.zip file (http://forum.xda-developers.com/showthread.php?t=780141) in that thread, but hboot loads it and tells me that it is older than my current version, and only gives me the option to reboot, or not to reboot. Doesn't load the image.
Here is the information on my hboot screen:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-0.97.0000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.09.01
Aug 19 2010, 14:29:08
Anybody have any ideas? Thanks!

you lost root, s-on
you can still start the bootloader so it's not a brick
need to get s-off before you can load recovery again and reflash your rom
have you tried the RUU? if it installs and defaults you then you can unrevoked to root

NewZJ said:
you lost root, s-on
you can still start the bootloader so it's not a brick
need to get s-off before you can load recovery again and reflash your rom
have you tried the RUU? if it installs and defaults you then you can unrevoked to root
Click to expand...
Click to collapse
Trying the RUU here now: http://forum.xda-developers.com/showthread.php?t=874091
Wish me luck!

luck has been wished

Kuhmo said:
Trying the RUU here now: http://forum.xda-developers.com/showthread.php?t=874091
Wish me luck!
Click to expand...
Click to collapse
This didn't work. Everything is still the same, except that my hboot version is now 2.10.0001. Any other thoughts?

still won't not into any rom? did you get errors?

NewZJ said:
still won't not into any rom? did you get errors?
Click to expand...
Click to collapse
No, the app on the PC said everything was successful. The progress bar on the phone progressed without errors too.

what happens when you reboot the phone not going into bootloader?

Just the HTC EVO 4G splash screen. Over and over and over...

does it show the boot animation or just stuck on splash?

Just the splash. No animation.

pull the battery, remove your sdcard, put the battery back in, see if it gets to the animation

Doh, you upgraded your hboot. It's alright though, just run the ruu one more time and your should be ok
Sent from my PC36100 using XDA App

Wrong button..

xHausx said:
Doh, you upgraded your hboot. It's alright though, just run the ruu one more time and your should be ok
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I asked my wife to check this thread from the car on the way to dinner. Saw the response. So I took my laptop inside with us and used the RUU one more time. No luck. I decided that it must be a hardware issue. I took the SD out and removed the evidence that the phone had been rooted, then took it to the sprint service center up the road. They just replaced it for me. Thanks for your time! I DO want to root my phone again, the ROMs are just so much better than the stock installation. Should I not install the OTA updates if I'm going to root it? Which guide should I follow for rooting?

never do OTA when rooted, use unrevoked to root, unrevoked.com

NewZJ said:
never do OTA when rooted, use unrevoked to root, unrevoked.com
Click to expand...
Click to collapse
Not when rooted. I meant should I update to the latest OTA UNTIL I decide to do the root again? Is the latest OTA unrootable?

Same deal.
Here is the post that I put in the wrong forum that I was about to post here until I saw this thread...
Wellp. I win.
I win a no expenses paid trip to my nearest Sprint dealer.
Ever since I used unrevoked to root my phone in November, I've been voraciously digging through these forums for tasty roms. I've been snorting lines of Cyanogen, MIUI, and a myriad of other, well-designed roms.
Using a on older version of hboot (pre 1 methinks) I was able to avoid the latest hassles with ClockworkMod (plus, I down(up?)graded to 2.6 via RomManager).
Tonight, as I was enjoying some tasty foodstuffs at my local foodstuff vendor, my phone rebooted. Then, it rebooted again. Then again. I once made the folly of flashing a new rom without running the appropriate wipes, and was no stranger to the bootloop. I patiently fired up hboot (my poor volume rocker is all but wore out) and ordered up the trusty recovery mode.
...then it rebooted again... and again... and again.
PusSidiasus: ONOES! I HAVE THE WTFBBRICKED MY PRECIOUS!
SmartAsSidiasus: Hang on for a second, let's check the internet. Try this link: tinyurl.com/4vgeyeg
PusSidiasus: ...
Unfortunately, my internal dialogues are not nearly as witty. Also, my best attempts to de-brick-ify were for naught. Fastboot gave some wacky error message when I tried to flash a new recovery, and installing via PC36IMG.zip did nothing to improve the situation. I even went so far as to install a stock image someone pulled from an RUU (with a 2.02hboot, so as to avoid wimax woes)...
Still, a whole lotta nothing. I can't do anything beyond hboot, and whatever recovery image I install (Clockworkmod, AmanRa) the machine still bootloops.
At this juncture, I've resigned to taking the phone into the sprint store and playing dumb. It is a stock rom, though I hope the attendant misses the S-OFF bit at boot. Which brings me to my proper question:
1) Has anyone run aground a similar issue and found a way out?
OR...​
2) Anyone know how to turn S-(back)ON in my current situation?​
Any insight would be greatly appreciated. Also, you can rest assured that I'll be rooting again whatever phone I walk away with, and the work that is exhibited in these forums is amazing. Keep churning out wonderful roms and guides.
Sidiasus
(Currently, Sadiasus... )

run the ruu to s-on then trade for another

NewZJ said:
run the ruu to s-on then trade for another
Click to expand...
Click to collapse
Ack, sorry... didn't mention in previous post. I fired up windows to run the RUU (I don't trust wine to that stuff) but it couldn't detect the device.

How to enable S-on in bootloader

I ran unrevoked 3 and tried a few things and decided it was not for me, I ran the Sprint RUU and it all worked fine. But under the bootloader screen it still shows S-off. Can I renable it?

venom_762 said:
I ran unrevoked 3 and tried a few things and decided it was not for me, I ran the Sprint RUU and it all worked fine. But under the bootloader screen it still shows S-off. Can I renable it?
Click to expand...
Click to collapse
Sry to hear that. See if THIS helps.

oooh that sucks. you have to re-root (you can just use unrevoked 3 again), then put the unrevoked s-on tool (found in the FAQ section of this thread http://unrevoked.com/rootwiki/doku.php/public/forever ) on the root of your sdcard. boot into recovery, and flash it as you would a rom. then check bootloader to make sure it is s-on. if it is, run the ruu again.
just curious, why dont u like root?

I just tried to re-run Unrevoked 3 and it will not reconnect, the tool just says waiting for device.
And I don't like root because of too much power.

venom_762 said:
I just tried to re-run Unrevoked 3 and it will not reconnect, the tool just says waiting for device.
And I don't like root because of too much power.
Click to expand...
Click to collapse
usb debugging is probably not on. try that.
too much power? like too much battery consumption (wtf?) or too much power over the phone?

too much stuff for me to f-with.

venom_762 said:
too much stuff for me to f-with.
Click to expand...
Click to collapse
hahah ok then. so ya turn debugging on (settings, applications, development, usb debugging) and put the phone on charge only and run unrevoked.

ok I found it, I was trying to root from the hboot screen.

Can't I just wait for the OTA from sprint and that would just turn S-back on?

venom_762 said:
Can't I just wait for the OTA from sprint and that would just turn S-back on?
Click to expand...
Click to collapse
no, it wouldnt turn s-on, and you might not even be able to accept it. if you are having a hard time using unrevoked, seeing as your rom no longer has root permissions, i can lead you through manually flashing amon-ra recovery to your phone and you can flash ur s-on from there.

I just got it to root again using Unrevoked 3 and restored to right after my first root. I should be able to now install the S-on tool and install it from the recovery menu?

venom_762 said:
I just got it to root again using Unrevoked 3 and restored to right after my first root. I should be able to now install the S-on tool and install it from the recovery menu?
Click to expand...
Click to collapse
That is correct. Also, I'm pretty sure that since you were still S off, you could've just flashed a pc36img of a recovery from the bootloader, flashed the s on tool, and then ran RUU.
Edit : just saw that dk already suggested that. Sorry.
Sent from my PC36100 using XDA App

Update I figured it out and ran the S-on tool, booted into the bootloaded and verified it was back on. I then ran the RUU and it should be fully stock and ready to install the OTA?

I just don't want to be that guy does not or has a failed update when the official OTA is out.

Anyone? I dying to know if I can install the next ota.

venom_762 said:
Anyone? I dying to know if I can install the next ota.
Click to expand...
Click to collapse
If you're back to stock, s on, and aren't on the latest OTA, then yes, you can take the OTA if you'd like to. That will bring you up to the latest software update.
Sent from my PC36100 using XDA App

Great I am relieved, I just wondered if when its pushed out if I have problems seeing it. Thank you guys for all of your help.

venom_762 said:
Great I am relieved, I just wondered if when its pushed out if I have problems seeing it. Thank you guys for all of your help.
Click to expand...
Click to collapse
sorry for leaving you in the dark for a while. that was one crazy day. but i'm at my comp now so i can help (not that there's anything left to do).
if i were you, i'd double check you are fully unrooted. boot into bootloader, and make sure you are s-on. then boot into recovery and make sure you have no custom recovery, just the stock htc one. also make sure your rom has no superuser app installed. if not, you are all good.

No prob man, I booted into the bootloader and S-On is back on and then tried to boot into recovery, a black screen with a red triangle came up so I assume there's no recovery installed. There is also no superuser Icon in the app draw.
The main reason I returned to stock is,is that this is my primary and only phone. I plan on getting the Nexus S when it come to sprint so I will see you guys again. That way if I bork the NS I got my trusty evo to activate.
Again thank you all for the help.

venom_762 said:
No prob man, I booted into the bootloader and S-On is back on and then tried to boot into recovery, a black screen with a red triangle came up so I assume there's no recovery installed. There is also no superuser Icon in the app draw.
The main reason I returned to stock is,is that this is my primary and only phone. I plan on getting the Nexus S when it come to sprint so I will see you guys again. That way if I bork the NS I got my trusty evo to activate.
Again thank you all for the help.
Click to expand...
Click to collapse
ok ya ur totally unrooted. enjoy the cage some prefer it there.
just saying, the evo is freaking hard to brick.

back to stock 2.2....

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?

I need help finding the right ruu so i can get s-off :(

I'm trying to get s-off with my htc evo 4g and im getting so frustrated i cant find anything complete. so far I was able to downgrade my phone to 2.2 from this small tut on themikmik but it never tells how to get actual s-off..i tried unrevoked 3.22 and it stops at waiting for root. im pretty sure i have the hboot drivers installed and it tells my phone what to do up untill it says waiting for root and does nothing. please im a very sad panda. if someone had a link to the ruu that would update my hboot to 2.15.0001 or 2.16.0001 hboot that is rootable with revolution that might work. thank you for your time.

Try here:
http://www.shipped-roms.com/index.php?category=android&model=Supersonic

Thank you! do you happen to know which one of those I should use? Also when I downgraded last I guess it locked my boot loader is that a problem?

Kannz2 said:
Thank you! do you happen to know which one of those I should use? Also when I downgraded last I guess it locked my boot loader is that a problem?
Click to expand...
Click to collapse
Unfortunately it's been way too long since I've messed with the OG EVO. The locked bootloader won't be a problem, though.

Hopefully someone could tell me? I don't really want to update past the hboot I need For the revolution root.

Kannz2 said:
Hopefully someone could tell me? I don't really want to update past the hboot I need For the revolution root.
Click to expand...
Click to collapse
Should be this one:
http://www.shipped-roms.com/downloa....15.00.0808_NV_2.15_release_209995_signed.exe

Thank you I'll try it out I hope I don't mess it up. I just hook the phone up and click on the exe right? Does it need to be in a certain mode?

Kannz2 said:
Thank you I'll try it out I hope I don't mess it up. I just hook the phone up and click on the exe right? Does it need to be in a certain mode?
Click to expand...
Click to collapse
You can run it with the phone booted to the OS or from the bootloader while connected via Fastboot USB mode. Once you've done that just run the exe from your computer by double-clicking on it. You may need to install HTC Sync also.

um it seems that when i try to use that update it says that it is the wrong update and it gives a error "signarure error" with the spelling error.. :crying:

Kannz2 said:
um it seems that when i try to use that update it says that it is the wrong update and it gives a error "signarure error" with the spelling error.. :crying:
Click to expand...
Click to collapse
Is the RUU version newer or older than what's installed on your phone?

I was able to find a flashable image and i got s-off with revolutionary. uh do you happen to know a good kernel to go with cm? or does it flash its own kernel when the rom is flashed? i was able to find a link for cm 7.2 or something like that. know a link for a good kernel? i heard tiamat or mason kernels are good but i cant find a mirror for either of them. you know a place to get them? or a old mirror? thanks for your help ^^

I don't normally make ROM recommendations but if you're looking to go the AOSP route, Deck's Reloaded is one of the best. Everything works. Period. This was one of the last ROM's I ran on my OG EVO before I upgraded. It has the Mason kernel already built in, too.
http://forum.xda-developers.com/showthread.php?t=1661605

thanks for all the help. ^^ You know somewhere that has some custom startup animations? I changed the splashscreen to the green android pooin on a apple but right now its stock boot animation.

Take a look at the themes & apps section. Also, I know that the ROM Toolbox app used to include some custom boot animations.