Database Info

*Unroot 2.2* 3.29.651.5 10/20/10

Ok, this worked for me as of 10/20/10, i had my phone rooted by unrevoked, I am like many of the people here who kept having issues with all the PC36IMG.zip not working. I have extracted a new PC36IMG.zip from the ruu's and have not had any issues. I also had the dreaded "main version is older" issue. This seemed to take care of the issue! Im now back to stock!
Step 1 you will need to go here:
http://downloads.unrevoked.com/forever/current/unrevoked-forever-son.zip
If you used Unrevoked Forever at any time, flash unrevoked-forever-son.zip from recovery until hboot shows S-ON(Credit to djR3Z tut)
Step 2
http://www.megaupload.com/?d=108Z9R8Y
This is the PC36IMG.zip file that you will need
- Put this on the root of your sdcard
- Boot into hboot and let it load up the PC36IMG.zip
- It will run like a normal update
- Reboot when finished
- It will do a few other things (Load radio and update)
- After it fully loads you should be back to complete stock!!!!
Lemme know if this doesn't work for you
LIKE I SAID THIS WORKED AS OF 10/20/2010!!!
I am not responsible for damages to your phone! You chose to go the route you did, so face the consequences, I'm just posting what has worked for me, so use at your own risk! Love the android, love my evo!

Has been tested and works if you have a rooted via unrevoked method.

So can I update my evo ota to 3.29.651.5 and then follow these steps? Right now I have the stock 3.26.651.6 rooted with unrevoked3. TIA

m4f1050 said:
So can I update my evo ota to 3.29.651.5 and then follow these steps? Right now I have the stock 3.26.651.6 rooted with unrevoked3. TIA
Click to expand...
Click to collapse
Im not understanding? If you apply just the PC36IMG you should at least lose root and be updated to latest update. You have to run the first tool to relock the bootloader. You will see in hboot if it is locked or unlocked. Locked is s- on unlocked is s- off

My bad, I was wanting to root or better yet, update to 29 and then root.
Sent from my PC36100 using XDA App

yes you can achieve root on the new update through unrevoked. I'm not a fan of rooting this way, as people have had lots of trouble unrooting (had this problem myself). Thats why I came up with this tut so you can unroot if you have to send back to sprint. my method was the only one that worked for me to get unrooted.

people...just use unrevoked 3...i mean its a one click process...u dont have to do anything after that in about 2 minutes your rooted and nand unlocked =P

m4f1050 said:
So can I update my evo ota to 3.29.651.5 and then follow these steps? Right now I have the stock 3.26.651.6 rooted with unrevoked3. TIA
Click to expand...
Click to collapse
Just flash a ROM that's based on the 3.29 update.

Well hopefully this works. I'm not going to root with unrevoked again I don't think. It was much easier for me to unroot my last phone w/o using unrevoked.
Nope, as of 1/19/11 this does not work.

Will this work if I didn't use unrevoked? I am currently having an issue where my usb/charging port is not working properly and can not connect to the computer. I am rooted but need to unroot so I can send my phone back.

Diplomat2387 said:
Will this work if I didn't use unrevoked? I am currently having an issue where my usb/charging port is not working properly and can not connect to the computer. I am rooted but need to unroot so I can send my phone back.
Click to expand...
Click to collapse
This is incredibly outdated, so no, it will not currently work with your phone.

dkelle4 said:
This is incredibly outdated, so no, it will not currently work with your phone.
Click to expand...
Click to collapse
Even if I downgraded my ROM?..I am currently on a 2.1 ROM..

Only one way to find out. It SHOULD. I ended up downloading one of the early official 2.2 releases and flashed that on my phone. Of course now it won't do another OTA because the "signatures are invalid".

dkelle4 said:
This is incredibly outdated, so no, it will not currently work with your phone.
Click to expand...
Click to collapse
I haven't seen any "unroot" threads that have worked for me. Is there one I'm missing?

jpitt916 said:
Only one way to find out. It SHOULD. I ended up downloading one of the early official 2.2 releases and flashed that on my phone. Of course now it won't do another OTA because the "signatures are invalid".
Click to expand...
Click to collapse
I tried just putting the pcimg on my sd card and power up into bootloader and it gives me an error saying that the image is older or something...Agh.

[Q] Unrooted Phone Still Not Taking Update

My phone was rooted with unrevoked, then I went through the steps to unroot it. I am s-off on the phone and back to stock but I still get the ! message with the droid guy when trying to apply the latest update. What exactly do I need to change or fix in order to apply this update? PLEASE help!

It's possible that maybe your phone doesn't allow FOTA unless you're S-ON. I've seen weirder things.

hypnotoadstool said:
My phone was rooted with unrevoked, then I went through the steps to unroot it. I am s-off on the phone and back to stock but I still get the ! message with the droid guy when trying to apply the latest update. What exactly do I need to change or fix in order to apply this update? PLEASE help!
Click to expand...
Click to collapse
If you are s-off then you're still rooted. S-on is unrooted. This shouldn't matter. Maybe your phone is different but Evos can receive ota updates while rooted. Your ROM however must be COMPLETELY stock. Not a stock ROM intended for a rooted device with busy box and super user but stock as in ALL system is unmodified.
Sent from my PC36100 using Tapatalk

Yup, as long as you still have the attribute S-Off on your phone, than you are rooted.
Connect your phone to PC and connect the HTC Sync software, then run the original RUU from the PC. That should do the trick.

Your problem might be that you have uninstalled or frozen some bloatware that came with the original rom. Apps that come from the service providers like vodafone apps etc.

[HOW-TO] ROOT TMOUS OTA 2.3.4 (if you lost root)

For those that lost root due to the TMOUS OTA 2.3.4 update, here's how I got it back.
When i updated, I had to install the stock recovery for the update to take affect. When I reverted back to stock recovery, the update flashed. I wiped my device, however, and thought that I'd be able to keep root and use Titanium. I was wrong, so here's how I fixed it:
Requirements (mostly just reminders not really telling you what to do here....)
1. S-OFF prior to updating
2. Stock Recovery to process the update
3. Disable Fastboot (Settings > Power > Fastboot)
Regain Root on 2.3.4 OTA Update
1. Download the HBoot CWM Recovery and SU flash able ZIP file from here:
http://forum.xda-developers.com/showthread.php?t=1192300
2. Place the HBoot CWM Recovery file on the root of your sdcard (i.e.. sdcard/)
3. Power off device
4. Go into HBoot (Vol Down + Power)
5. Flash the CWM Recovery image
6. Reboot
7. Delete the CWM Recovery file off of your sd card
8. Power off
9. Reboot into Recovery (can be selected through HBoot if easier)
10. Choose the SU Root ZIP file that you downloaded in step 1 and flash it
11. Reboot, you're rooted with CWM Recovery again
This method work perfectly for me. I imagine anyone who did the OTA Update and has Rooted their phone would know they went to Stock recovery to apply the update or were always on it.

Thank you for the guide

Noobish question, how did you remove CWM and go back to stock recovery? Perhaps you should add this to the OP.

I was just gonna write this up. Oh well. THANX! I'd press your thanx button but I used them all up already. Maybe a beer?
EDIT: Can you please write up a how-to for going from whatever anyone is on to TMOUS Stock 1.45.531.1 + CWM + Root ? I believe it would be really helpful and I am just too lazy to do it myself

WARNING After installing the OTA, the bootloader now says in pink on the very top
******LOCKED*******
Also, Fastboot flash commands don't work (trying to flash splash image)
HBOOT is now: 1.18.0000
Re-running Revolutionary fixes it. and extended Fastboot commands work again.
And brings it back to 1.17.1111

if someone made a nandroid backup of the ota rooted thru cwm couldnt you just load that instead using the restore option?

As always gents.... Just a tiny tiny bit of patience will go a long way.
If your already rooted through Revolutionary, there is zero need to flash any official FOTA. Not sure why some people seem to want to try it out when they're already rooted? It's NO different than the Euro 2.3.4 OTA. Peeps all over these forums and the web are saying the same thing....no change.
Actually worse if you count the fact that heavy graphically intense games crash now as they do with all stock kernel 2.3.4 Euro ROMs.
Rooted versions of the Tmous 2.3.4 FOTA are already rolling out (birgertime I believe has one out). Give it a day and there will be more that are heavily customized like the ones from Baadz, Lee, Mike etc
It's easy to understand why people want to install the latest official firmware...but if you're rooted and or want to be....there is no need to ever go through official channels (HTC/Tmo) to get your updates.
Just for the people who might be unclear. To everyone else... carry on

Hoggles said:
As always gents.... Just a tiny tiny bit of patience will go a long way.
If your already rooted through Revolutionary, there is zero need to flash any official FOTA. Not sure why some people seem to want to try it out when they're already rooted? It's NO different than the Euro 2.3.4 OTA. Peeps all over these forums and the web are saying the same thing....no change.
Actually worse if you count the fact that heavy graphically intense games crash now as they do with all stock kernel 2.3.4 Euro ROMs.
Rooted versions of the Tmous 2.3.4 FOTA are already rolling out (birgertime I believe has one out). Give it a day and there will be more that are heavily customized like the ones from Baadz, Lee, Mike etc
It's easy to understand why people want to install the latest official firmware...but if you're rooted and or want to be....there is no need to ever go through official channels (HTC/Tmo) to get your updates.
Just for the people who might be unclear. To everyone else... carry on
Click to expand...
Click to collapse
exactly what i said and what i was thinking. my brother in law & friend aren't rooted yet so they could go for the OTA but my fiancé and I are rooted. I have to make sure she doesn't install the update. i have no desire to root her sensation again. lol - for me, i'll be downloading the euro ota

EmceeGeek said:
exactly what i said and what i was thinking. my brother in law & friend aren't rooted yet so they could go for the OTA but my fiancé and I are rooted. I have to make sure she doesn't install the update. i have no desire to root her sensation again. lol - for me, i'll be downloading the euro ota
Click to expand...
Click to collapse
Keep one thing in mind though... Your brother in-law & friend should realize that if they do ever one day want to root, they should stay far away from any official HTC updates. HTC will make them agree to an online waiver that will void many parts of their warranty if they choose to use HTC's online unlocker.
If they ever plan on rooting, they should go through Revolutionary....simply because it's the best of both worlds. You can have root, HTC/Tmo will never know.... and you can now get S-ON back after Revolutionary for warranty repairs and such

Quick question. I just got my sensation replaced with a new one(previous one had problems) and it came with 2.3.4 can I still get s-off and root?
Sent from my HTC Sensation 4G using XDA App

nxt said:
WARNING After installing the OTA, the bootloader now says in pink on the very top
******LOCKED*******
Also, Fastboot flash commands don't work (trying to flash splash image)
HBOOT is now: 1.18.0000
Re-running Revolutionary fixes it. and extended Fastboot commands work again.
And brings it back to 1.17.1111
Click to expand...
Click to collapse
Thanks, I was wondering why this happened.

Nightfall983 said:
Quick question. I just got my sensation replaced with a new one(previous one had problems) and it came with 2.3.4 can I still get s-off and root?
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
Yes Revolutionary works just fine, make sure you download the latest version from http://revolutionary.io/

nxt said:
Yes Revolutionary works just fine, make sure you download the latest version from http://revolutionary.io/
Click to expand...
Click to collapse
Thanks, I'll root it now
Sent from my HTC Sensation 4G using XDA App

[Q] Got OTA update available after custom ROM???

How is this possible?
I've S-OFFed and rooted with Revolutionary my Desire S. Than I 've flashed it with pree-rooted SAGA S stock ROM (stock, hmmm...) and I've flashed a new radio.
I went on to check the update and there it was! Official update available! I didn't go on, because I',m not sure what it means.
Does anyone know whether it is safe to go on with the update? I don't know which update it is, but anyway, what could happen?

s-off phones with prerooted stock roms can receive updates but as i can see many ppl had problems (stuck on HTC logo etc...) after update

Just plain weird. There are a lot of people (mainly devs) said that you/we shouldnt be able to receie OTA updates if hboot/recovery among other things are not official releases.
Based on what you've done the last tine is update the recovery to newest one? Is it the official release?
If so, this gave me the impression that ota updates are dependent on the phone's recovery version/image?
Sent from my HTC Desire S using XDA App

Skanob said:
Based on what you've done the last tine is update the recovery to newest one? Is it the official release?
If so, this gave me the impression that ota updates are dependent on the phone's recovery version/image?
Click to expand...
Click to collapse
I've got the updated CVM Recovery via ROM Manager. It is the latest version. Otherwise I still have the old HBOOT ENG 0.98.2000.
I figure, if it's a "stock ROM" only being pree-rooted that could confuse the "official update", as nothing is acctualy changed, only root is made. But that's still weird, because I wasn't given the offer to the official 2.3.5/ 3.0 sense update.
Yet after the "manual" update, the updates continue.
Mind you, there is one strange thing though...
After each reboot phone wants to send the info to the HTC, saying "the phone has recovered/ rebooted strange way. Inform HTC?"
I decline every time...
And I wonder which update could it be? Kernell, sense 3.5? HBOOT 2.00...?

what prerooted rom u use?
update cant be 3.5 only 3.0.3.5 is leaked rom

Adidas108 said:
what prerooted rom u use?
update cant be 3.5 only 3.0.3.5 is leaked rom
Click to expand...
Click to collapse
Like I mentioned at the begginning; I used pree-rooted SAGA S HTC Europe 2.10.401.4.

LogicXLz' said:
Like I mentioned at the begginning; I used pree-rooted SAGA S HTC Europe 2.10.401.4.
Click to expand...
Click to collapse
Beginning of what?? Thats not latest version. There is update to 401.5
~Swaypovano sa Desire S BRE!~

AHA! I know what you mean "Adidas108"...
Yeah, I know there is an update to 401.5. But I was given the option to the official update after 401.4 pree-rooted stock ROM...
And am wondering whether it is possible that now the officialy offered OTA could be 401.5? That's what I wrote before... I mean, this maks no sense. There shouldn't be a possibility of an update.
Since I've flashed the pree-rooted ROM, after each reboot phone wants to send the info to the HTC, saying "the phone has recovered/ rebooted strange way. Inform HTC?" Has anyone experienced this?

It sends that maybe because it wasnt fully successful to applyin the updates properly?
Again, still plain wierd. Hhmmm. Yhere mut be something at play here that we still didnt know how updates are pushed.
Im startibg to think that it may be dependent on the network/sim card you're ysing. Maybe by IP address that the phone is connected to?
Sent from my HTC Desire S using XDA App

I have s-off and rooted my Desire S with Revolutionary and I recieved the Sense 3.0 and Android 2.3.5 update yesterday evening. I installed it and now my phone just won't go past the HTC welcome screen. Just white bacground with HTC logo. I can go to bootloader and I already tried some things as mentioned in the threads about how to s-on Desire S from s-off but it still hangs on the HTC logo. I also tried the factory reset but no luck. I think I need to s-on somehow without booting the system and then the new update would maybe work which is already installed. Or maybe I can just reset all the software and make it s-on and start from zero. Any ideas? I just want my phone to work again
Many thanks!

Skanob said:
It sends that maybe because it wasnt fully successful to applyin the updates properly?
Again, still plain wierd. Hhmmm. Yhere mut be something at play here that we still didnt know how updates are pushed.
Im startibg to think that it may be dependent on the network/sim card you're ysing. Maybe by IP address that the phone is connected to?
Click to expand...
Click to collapse
But according to phone software info it did go thru the "cistom ROM" flash OK. I've got everything as it should be after aplying the flashes...
And since there are many replies in which PPL are stating they got stuck at the "white HTC logo" screen. I'm not to sure if I should try updating via officially offered update.
Can those who updated their phones with the official update, after flashing their phones with custom - pree-rooted or any other kind of ROMs, state their software status, before they continued with an official update offered afterwards. please?

Chalix said:
I have s-off and rooted my Desire S with Revolutionary and I recieved the Sense 3.0 and Android 2.3.5 update yesterday evening. I installed it and now my phone just won't go past the HTC welcome screen. Just white bacground with HTC logo. I can go to bootloader and I already tried some things as mentioned in the threads about how to s-on Desire S from s-off but it still hangs on the HTC logo. I also tried the factory reset but no luck. I think I need to s-on somehow without booting the system and then the new update would maybe work which is already installed. Or maybe I can just reset all the software and make it s-on and start from zero. Any ideas? I just want my phone to work again
Many thanks!
Click to expand...
Click to collapse
Maybe we should S-On our phones before applying the OTA update... But do you have a possibility to flash some other ROM now? Can you even make a recovery afterwards?

Chalix said:
I have s-off and rooted my Desire S with Revolutionary and I recieved the Sense 3.0 and Android 2.3.5 update yesterday evening. I installed it and now my phone just won't go past the HTC welcome screen. Just white bacground with HTC logo. I can go to bootloader and I already tried some things as mentioned in the threads about how to s-on Desire S from s-off but it still hangs on the HTC logo. I also tried the factory reset but no luck. I think I need to s-on somehow without booting the system and then the new update would maybe work which is already installed. Or maybe I can just reset all the software and make it s-on and start from zero. Any ideas? I just want my phone to work again
Many thanks!
Click to expand...
Click to collapse
Here's your answer:
[GUIDE] Possible FIX for the infamous eMMC problem...
---------- Post added at 02:48 PM ---------- Previous post was at 02:46 PM ----------
LogicXLz' said:
But according to phone software info it did go thru the "cistom ROM" flash OK. I've got everything as it should be after aplying the flashes...
And since there are many replies in which PPL are stating they got stuck at the "white HTC logo" screen. I'm not to sure if I should try updating via officially offered update.
Can those who updated their phones with the official update, after flashing their phones with custom - pree-rooted or any other kind of ROMs, state their software status, before they continued with an official update offered afterwards. please?
Click to expand...
Click to collapse
some files/images/partitions might not been updated properly. E.i. Recovery, hboot, kernel, etc..

I'm pretty sure we need to be s-on to apply the new update. At least I'm screwed right now. I cannot do recovery, it shows me a warning sign with a cell phone on the background and just stalls there, I have to take the battery out to kill it.
Okay I messed around and now I got into ClockworkMod recovery and I recieved the eMMC fried chip error. I wiped cache and got rid of the errors. Obviously I still have s-off and still it hangs on the HTC logo when I try to boot. What can I do with it next?
Oh and I forgot to mention one part. After I realized that I can't update sense 3.0 and Android 2.3.5 (phone showed me an exclamation mark with android icon), I used RUU to revert my phone to 1.28. Then used phone to apply a system update 1.47. Then used system update to apply the newest sense 3.0 update and I didn't recieve the warning sign. It showed the progress bar of the install and then while booting stalled at the HTC logo. Since then I can't boot up the system.
And for additional info my HBOOT version is 6.98.1002 and RADIO is 3822.10.08.04_M

If u can use recovery why not flash some other rim?
~Swaypovano sa Desire S BRE!~

Ok, but what rom should i use and can I get s-on by just flashing ROM or what?

Should I root now or after Jellybean is released by AT&T?

I guess my question is, if I wait to update to jellybean will the method that is available today to root the phone no longer exist? It appears that someone has described a method for me to update to the AT&T version of jellybean once it's available, so that shouldn't be an issue (I hope!).

We won't really know (if they plugged the root exploit hole) until the update goes out, and people try to root. But HTC has killed the previous root method with every AT&T OTA for this device so far. So if I were a betting man, I'd say that the current exploit will not work after updating to JB.
Really, you have nothing to lose if you root now versus after the Jellybean OTA. You can always unroot and accept the OTA later, if you change your mind. Also, if you are rooted and bootloader unlocked, once the AT&T JB OTA rolls out, it will probably be posted in a pre-rooted flashable form within days (maybe even hours) of it being rolled out officially. So you can just flash that on your rooted, BL unlocked device.
But on the other hand, if you accept the OTA and cannot root, you are stuck until a new root exploit is found.

i would root now and wait until a dev gets JB and makes it compatible, because what usually happens when new software or firmware is released is the manufacturers and carriers often patch the vulnerabilities we use to obtain root.

Root it now. There's no telling if a root method for a later version will arrive sooner or later so to be safe I'd do it now. You can flash any jellybean rom you want afterwards.
Sent from my One X using xda app-developers app

One thing that can be said with confidence is that rooting and unlocking is not going to get easier with each update. It may stay the same; it may get a lot harder. So there's no good reason to wait.

I personally haven't had any issues with Viper XL 3.1 (Jellybean), so you could upgrade now if you really wanted to take advantage of some of the features. If you're looking to stay on ICS, Viper XL 2.4 and CleanRom 5.1 are really solid choices.

speaking from experience.
root it now. If you update to jellybean via ota you might run into the problem that I'm currently having. OTA updated my rogers X One then rooted it. Bootloader unlock and root went fine, but when I went to use the penultimate TWRP, the screen wouldn't respond. Had to flash the newest TWRP and that responded to touch. But now when I flash a rom it won't respond to touch. My guess is that something in hboot 2.14 has changed.

veemodz823 said:
root it now. If you update to jellybean via ota you might run into the problem that I'm currently having. OTA updated my rogers X One then rooted it. Bootloader unlock and root went fine, but when I went to use the penultimate TWRP, the screen wouldn't respond. Had to flash the newest TWRP and that responded to touch. But now when I flash a rom it won't respond to touch. My guess is that something in hboot 2.14 has changed.
Click to expand...
Click to collapse
That's true, HTC is almost sure to further mess with hboot, as well as patch the root exploit.
Sent from my HTC One X using xda app-developers app

veemodz823 said:
root it now. If you update to jellybean via ota you might run into the problem that I'm currently having. OTA updated my rogers X One then rooted it. Bootloader unlock and root went fine, but when I went to use the penultimate TWRP, the screen wouldn't respond. Had to flash the newest TWRP and that responded to touch. But now when I flash a rom it won't respond to touch. My guess is that something in hboot 2.14 has changed.
Click to expand...
Click to collapse
redpoint73 said:
That's true, HTC is almost sure to further mess with hboot, as well as patch the root exploit.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Chongodroid flashed the new 2.14 boot and doesn't have an issue.. my guess would be some sort of firmware change/incompatibility

absolutelygrim said:
Chongodroid flashed the new 2.14 boot and doesn't have an issue.. my guess would be some sort of firmware change/incompatibility
Click to expand...
Click to collapse
Which isn't to say that they will even include hboot 2.14 in the AT&T OTA. We seem to get "special" treatment (in a bad way). So I'm betting they will have an even newer hboot for the AT&T update, and f_ck us even more.

I would do it now and never accept any OTA update. My phone came with the 1.14 HBOOT, but after I unlocked the bootloader, I downgraded that using JET and haven't looked back. With an unlocked bootloader and TWRP I am not even sure how they could make the AT&T Jellybean unrootable unless you take the OTA and it screws you with a new HBOOT. My only real advice is to never take an OTA if you plan to root.