Read and learn, Padowan

https://spreadsheets.google.com/spre...Dg1ODc1ODI&ifq

Hey hip,
Thanks very very much. Looks like that tutorial will help a lot. If I happen to have any questions I will shoot you a pm if that is OK.
Iv started to download the things needed and will be beginning this very soon.

So the steps are, do the ruu, run the s-on tool(at this time I will be unrooted?), and then reroot using the easiest method which is still unrevoked correct?


Sent from my PC36100 using XDA App

Originally Posted by htcevo4g03

Hey hip,
Thanks very very much. Looks like that tutorial will help a lot. If I happen to have any questions I will shoot you a pm if that is OK.
Iv started to download the things needed and will be beginning this very soon.

So the steps are, do the ruu, run the s-on tool(at this time I will be unrooted?), and then reroot using the easiest method which is still unrevoked correct?


Sent from my PC36100 using XDA App

Close, run the S-On tool first in recovery, then RUU, that will get you back to stock. Then Re-Root, flash Amon Ra Recovery, flash your ROM.

Originally Posted by HipKat

Close, run the S-On tool first in recovery, then RUU, that will get you back to stock. Then Re-Root, flash Amon Ra Recovery, flash your ROM.

ok im = finished with s-on and ruu. I followed the direction exactly as it said too.
SO yes im back to stock now but one thing I noticed im still S-off, is this correct or does this mean i may have done something wrong?
I did not notice any thing that went wrong during the first part but the second part,-Reboot bootloader, flash ruu part it started the update and after it went through the progression of updating each one it showed this:
Parsing....(sd zip)
Boot-fail pu
recovery-ok
system-ok
userdata-ok
splash1-ok
wimax-ok
Partition update failed(in black)
Update failed(in red)

and a side note, i did try installing a root only app and it wouldnt let me. so I just dont know.

i am stock but still says s-off. Not sure where to go from here??

I feel like I have seen this before. Does your evo get incredibly hot during the flash? Specifically close to the soft buttons at the bottom of the screen? My first one had an issue where it was built with what I can only guess was a faulty batch of capacitors in the power management section of the phone's hardware internals. When it would use too much power, for example, flashing a rom, or even leaving the screen on for extended amounts of time, it would reset, then due to the temperature generated during boot, it would continuously do exactly what you are describing. Even your list of working ROMs is about the same as mine was. I brought it back to the stock ROM by flashing and putting it into the freezer until it came up successfully, then had the Sprint service center check it out. They had no clue what was wrong, so they blamed me for it. Since I didnt have insurance, I bought a new evo and took my old one apart. I am a 10 year electronics technician for the US Army, so I know what I am doing as far as troubleshooting hardware issues, and I found 3 blown capacitors. Just thought I would share my experiences, hopefully this helps. My suggestion would be to purchace insurance (if you dont already have it), flash it to stock, un-root and remove S-off, wipe everything (read: EVERYTHING to include log files etc.) and make an insurance claim. You will get a refurbished evo as a replacement, but since this is a hardware issue that HTC and Sprint arent acknowledging, refurbished is a lot better and cheaper than the $400 i had to spend on a new one...

Originally Posted by Serial70

I feel like I have seen this before. Does your evo get incredibly hot during the flash? Specifically close to the soft buttons at the bottom of the screen? My first one had an issue where it was built with what I can only guess was a faulty batch of capacitors in the power management section of the phone's hardware internals. When it would use too much power, for example, flashing a rom, or even leaving the screen on for extended amounts of time, it would reset, then due to the temperature generated during boot, it would continuously do exactly what you are describing. Even your list of working ROMs is about the same as mine was. I brought it back to the stock ROM by flashing and putting it into the freezer until it came up successfully, then had the Sprint service center check it out. They had no clue what was wrong, so they blamed me for it. Since I didnt have insurance, I bought a new evo and took my old one apart. I am a 10 year electronics technician for the US Army, so I know what I am doing as far as troubleshooting hardware issues, and I found 3 blown capacitors. Just thought I would share my experiences, hopefully this helps. My suggestion would be to purchace insurance (if you dont already have it), flash it to stock, un-root and remove S-off, wipe everything (read: EVERYTHING to include log files etc.) and make an insurance claim. You will get a refurbished evo as a replacement, but since this is a hardware issue that HTC and Sprint arent acknowledging, refurbished is a lot better and cheaper than the $400 i had to spend on a new one...

SOrry I was in the middle of editing my last post. read it now. I followed the steps hip said to do but still s-off. Lost my man

Originally Posted by htcevo4g03

SOrry I was in the middle of editing my last post. read it now. I followed the steps hip said to do but still s-off. Lost my man

If you used the unrevoked s-on tool, it needs to be run several times to actually take. It will say that it was successful, but the only way to know for sure is the text at the top of the boot loader. If you only ran it once and it said success, then you flashed the latest RUU, you have quite the issue on your hands. HTC has locked the recovery mode with the latest RUU, so until someone finds a way around it, you are stuck with the stock ROM and S-off. If you search through the Android Development section of this forum, there is more info about this than I have offhand. I was reading about it because I am about to trade in my old evo for $150 off of an HTC Evo View 4G, so I pushed the latest RUU to my old phone to trade it in with no issues.

Originally Posted by Serial70

If you used the unrevoked s-on tool, it needs to be run several times to actually take. It will say that it was successful, but the only way to know for sure is the text at the top of the boot loader. If you only ran it once and it said success, then you flashed the latest RUU, you have quite the issue on your hands. HTC has locked the recovery mode with the latest RUU, so until someone finds a way around it, you are stuck with the stock ROM and S-off. If you search through the Android Development section of this forum, there is more info about this than I have offhand. I was reading about it because I am about to trade in my old evo for $150 off of an HTC Evo View 4G, so I pushed the latest RUU to my old phone to trade it in with no issues.

no if you look at the top of page 3 of this thread hip pointed me to a tutorial which included the unrevoked s-on tool, ruu 3.70(i think) which brought me to 2.2 stock not 2.3 so no it wasnt the latest ruu. Im definately on 2.2, not 2.3 thank goodness.

all i know is i followed the direction. Im back to stock 2.2, it still says s-off, yet when i try to install root only apps it will not let me because it says im not rooted. Oh man soo confused, i wish someone would come to the rescue..

Re-run whatever tool you used to root initially. Sometimes they don't take on the first try as well. I would suggest unrevoked, its the easiest I've seen yet.

TBH, it's probably OK that you're still S-Off. I ran S-On and RUU twice and both times, I never even checked to see if it did indeed set me S-ON.

Did you use the PC36IMG version of RUU or the Computer exe program??
Personally, I prefer the PC36IMG. After it ran, did your phone boot up? If it did, are you back to stock?