Database Info

Noob Question about the correct RUU I need...

So I've tried about 5 different RUU's to get my phone back to 2.2 with no luck.
Either a signature error or bootload mismatch or something or another.
I have a Sprint HTC Evo with 2.3.3.
Can someone help me get this thing back and running on 2.2?
I recently tried to use Unrevoked on it...which caused some issues with the bootloader .
Thanks, guys/gals

If you aren't s-off then you can't run an RUU for an older version. If you are s-off, just flash a rooted stock 2.2 rom. You can try a different RUU if you're already s-off, just make sure that you follow the directions closely.
If you're trying to root by downgrading, it won't work unless the phone is already s-off. If the phone is s-off and you're trying to gain root access, just flash a PC36IMG of a recovery then flash a rooted rom from there.
If you're taking it in for repair, keep s-off so you can re-root if you get the phone back (if you're already rooted and want to stay that way).
Sent from my PC36100 using Tapatalk

plainjane said:
If you aren't s-off then you can't run an RUU for an older version. If you are s-off, just flash a rooted stock 2.2 rom. You can try a different RUU if you're already s-off, just make sure that you follow the directions closely.
If you're trying to root by downgrading, it won't work unless the phone is already s-off. If the phone is s-off and you're trying to gain root access, just flash a PC36IMG of a recovery then flash a rooted rom from there.
If you're taking it in for repair, keep s-off so you can re-root if you get the phone back (if you're already rooted and want to stay that way).
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Hey, thanks for the reply .
I'm not sure what you mean by S-OFF/S-ON however .
Also, I've tried probably five or six different RUU's, none of them want to run.

[GUIDE][07/01] Flashing ICS FIRMWARE 3.12 base img files.

DISCLAIMER. Do it at your own risk.. I am not responsible for bricks....bla bla bla, usual stuff.
If in doubt-STAY AWAY!
Q/A First.
Do I HAVE to flash this FW? - YES, if you want to flash ICS 4.0.3 based rom. If not, it just won't boot. Latest firmware works with previous (2.3.4,2.3.5,4.0.1) roms.
Do I NEED SuperCID? - YES, it will help in case you need to revert and if your CID is not on the update.zip list
Will I lose S-OFF? - NO
Can I use this FW with earlier builds? - YES
Will I lose fastboot commands like flash splash1? - Yes
Is it safe? Never 100% but no fails so far. Flash at your own risk
Can I revert to previous hboot, like 1.17? Yes, make sure you are superCID.
Any disadvantages? None so far
Any advantages? More optimised fw/drivers for ICS. Users report faster ROM operation.
Why does it say ***LOCKED*** in bootloader? Because hboot is locked (don't panic)
Can I go back to **REVOLUTIONARY**? Yes, flash 1.17 HBOOT at the bottom of OP.
HOW TO
0. Make sure you are S-OFF and superCID. Check HERE
1. Download zip from HERE Credits to rmk40, this is FW I used).
2. Do nandroid backup.
3. Copy/paste PG58xxxxx to the root of your microSD
4. Make sure MD5 match!!! MD5 checker I use HERE
4. Make sure MD5 match again!!!
4. And once again, make sure MD5 match.
5. Reboot into bootloader (if you don't know how to do it, don't do any of that at all)
6. microSD will be scanned and will ask you if you want to update, press +vol for YES
7. Follow onscreen instructions.
8. Now just pull sd card out if you don't have microSD reader or delete PG58xxxx if you do. PG58 will prevent you from going into recovery if phone sees it.
9. Reboot into bootloader-go to recovery
10. Put your SD card back in
11. Reboot or flash new rom
12. You are done. Just delete that PG58 file so it doesn't stop you getting into recovery again.
REVERT TO 1.17 HBOOT
ziggy1001 said:
Direct link with MD5
http://forum.xda-developers.com/showpost.php?p=20681060&postcount=22
Click to expand...
Click to collapse
Paste on root of SD card, make sure MD5 matches. Repeat update from bootloader (steps 1-12 from above) and you should be done.
If anyone has anything to add, feel free.
Remember, if you flash RUU, then process is slightly different and will most likely involve unlocking via HTCDEV (haven't really looked into it)

This is for all Sensation's, right?

aNYthing24 said:
This is for all Sensation's, right?
Click to expand...
Click to collapse
Indeed. Mike provided img files from both RUUs. I'm pretty sure it's safe to mix and match, since we ran 1.73 RUUs on normal Senny, but wouldn't recommend risking it just in case. But there is always a brave one ... LOL Who is it gonna be this time?

I've already followed the steps as in mike1986's thread and all went well, but what is the benefit of reverting to 1.17 HBOOT?

piplewis said:
I've already followed the steps as in mike1986's thread and all went well, but what is the benefit of reverting to 1.17 HBOOT?
Click to expand...
Click to collapse
Advanced fastboot commands

nice work on the thread mate, do you want to include a note that mikes files will update the radio too, just make sure everyone is clear on what is updates

Does it improve performance noticeably? I'm just a bit overwhelmed, sorry.

Hawke84 said:
nice work on the thread mate, do you want to include a note that mikes files will update the radio too, just make sure everyone is clear on what is updates
Click to expand...
Click to collapse
So there will be no possibility of downgrading the radio?...our i have to revert to 1.17 to flash older radios?
I have 10.56 and i m satisfied with it...

jjdoctor said:
So there will be no possibility of downgrading the radio?...our i have to revert to 1.17 to flash older radios?
I have 10.56 and i m satisfied with it...
Click to expand...
Click to collapse
You can still do it via PG58 update, but not via fatboot flash radio radio_image_name.img

I want to try this so bad, but I am scared as heck! What do we need to know before doing this? Such as, what do we risk other than an all out brick? Will we be able to go back to what we have now?
Matt

tinky1 said:
Find 1.17 HBOOT in PG58xxxx in THIS THREAD (provided by ziggy1001)
)
Click to expand...
Click to collapse
Direct link with MD5
http://forum.xda-developers.com/showpost.php?p=20681060&postcount=22

Looks like it worked for me. I am restoring a ROM right now. After that, ill revert back to the previous bootloader. So far, so good!
So now, where do you guys see the improvements?
Matt

I just tried to flash it but it have me CID error... I used supercid by this method
http://forum.xda-developers.com/showthread.php?t=1192630
What could be wrong?

jjdoctor said:
I just tried to flash it but it have me CID error... I used supercid by this method
http://forum.xda-developers.com/showthread.php?t=1192630
What could be wrong?
Click to expand...
Click to collapse
I am getting ready to flash it, but I did supercid by the method in the sticky-noted post near the top of the Sensation forums.
[Guide] to Installing S-off, Unlocking, ClockWork, Root, SuperCID & S-on

jjdoctor said:
I just tried to flash it but it have me CID error... I used supercid by this method
http://forum.xda-developers.com/showthread.php?t=1192630
What could be wrong?
Click to expand...
Click to collapse
Does your bootloader screen show **locked** in pink color ?

hsnmz said:
Does your bootloader screen show **locked** in pink color ?
Click to expand...
Click to collapse
Yes it shows Locked in pink... My hboot is now 1.20
My radio didn't upgrade... I still have 10.56....
I flashed it over Ultimite ROM... i thought it will erase my ROM but nothing changed....:-/
It flashed everything but showed cid error in last one... I don't know what was it....
So now i have to go back to 1.17, supercid using adb and fish 1.20 again?
I supercid using terminal emulator... I guess that didn't work...

jjdoctor said:
I supercid using terminal emulator... I guess that didn't work...
Click to expand...
Click to collapse
Wait, what?!
You tried to SuperCID via Terminal Emulator, while the phone was running? oO
What's wrong with following the instructions in the stickied guide and using adb?

Never in my life i used adb stuff... :-/
never tried to learn it either... But i guess i have to learn it now..
Now tell me what to do?
should i download hboot 1.17, flash it and then reflash 1.20 after supercid?

jjdoctor said:
Never in my life i used adb stuff... :-/
never tried to learn it either... But i guess i have to learn it now..
Now tell me what to do?
should i download hboot 1.17, flash it and then reflash 1.20 after supercid?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1192300 this is the thread I have followed time and time again with success step 4 is to do cid

is this firmware just relevent to ics roms or can it be used on 3.0/3.5 roms??????

[Q] Going back to stock from ICS?

Hi guys!
Sorry another n00b question but just wanted to make sure...
So I am one of those that got tired to waiting for the OTA and finally decided, at least for now, to try one of the ICS ROMs. I've done some on GB so I'm vaguely familiar with flashing and all that but since it's my first time with ICS I'd like to ask you experts out there.
Basically I just want to make sure that if/when TMo finally pushes out the "official OTA", I can give that a try also. I guess my fear is that I've been reading how it's difficult...or impossible?...to go back to stock since I have to flash my firmware.
Can you go back to 100% Stock TMo GB from ICS?
I currently have already S-Off, root (superuser), and S Cid to 11111111 in preparation. I figure while I wait for TMo, at the very least, I can run my phone rooted to let apps like AutoKiller Memory help my phone run better. I also did a backup using 4EXT.
My next step is to take the plunge but before I do, I'd like to know that I can go 100% back. I've done it with GB ROMs but wasn't sure about ICS because of the whole firmware thing.
Can someone LMK if it should be no problem? Much appreciated for guiding a n00b like me! You guys are awesome!!!

It's not hard...
http://forum.xda-developers.com/showpost.php?p=21989089&postcount=2
This is how I do it:
1. Place firmware on root of sdcard.
2. Use 4ext recovery control to reboot to recovery (power menu).
3. Restore my stock nand from 4ext recovery.
4. Use 4ext recovery to reboot into bootloader (power menu).
5. Select "bootloader" from fastboot menu and let hboot detect the firmware. (volume up for "yes")
6. Let it complete and press power to reboot when prompted...
All my roms, nands, firmwares, radios, etc... are backed up on my sdcard. As long as I've got a good charge on the battery I can go back and forth between BG and ICS multiple times without ever connecting to a PC or pulling my battery...
If you don't have a nand of your stock rom then just flash the 1.50.531.1RUU... And restore your CID.

Thanks for the info GROGG88! So this will restore my firmware too? So basically using the RUU should get me back to full stock including the firmware? Or do I need to downgrade the firmware manually first?
Also noticed that in the link you gave, it has Hboot 1.17. Does it matter that my original is 1.18?
Again apologies for new n00b questions! Thanks for all your help!!!

If you go by the guide in the link I posted then you'll be able to restore a stock nand if you have one. After that you can flash 1.18 hboot and stock recovery.
The easiest way would be to flash the RUU which will put EVERYTHING back to stock including firmware, but you'll keep s-off (which is good).
It really depends on whether or not you backed up an unmodified version of your stock GB...
I'm going to post download links for the 1.50.531.1 RUU and a PG58IMG.zip version of it in the General section. You can use the PG58IMG.zip to restore individual components by extracting the files, removing whatever you don't want, and archiving the files you do want back into a zip...

GROGG88 said:
If you go by the guide in the link I posted then you'll be able to restore a stock nand if you have one. After that you can flash 1.18 hboot and stock recovery.
The easiest way would be to flash the RUU which will put EVERYTHING back to stock including firmware, but you'll keep s-off (which is good).
It really depends on whether or not you backed up an unmodified version of your stock GB...
I'm going to post download links for the 1.50.531.1 RUU and a PG58IMG.zip version of it in the General section. You can use the PG58IMG.zip to restore individual components by extracting the files, removing whatever you don't want, and archiving the files you do want back into a zip...
Click to expand...
Click to collapse
Thanks again GROGG!!!

GROGG88 said:
If you go by the guide in the link I posted then you'll be able to restore a stock nand if you have one. After that you can flash 1.18 hboot and stock recovery.
The easiest way would be to flash the RUU which will put EVERYTHING back to stock including firmware, but you'll keep s-off (which is good).
It really depends on whether or not you backed up an unmodified version of your stock GB...
I'm going to post download links for the 1.50.531.1 RUU and a PG58IMG.zip version of it in the General section. You can use the PG58IMG.zip to restore individual components by extracting the files, removing whatever you don't want, and archiving the files you do want back into a zip...
Click to expand...
Click to collapse
Can you LMK when you post those files as well as the link! Much appreciated!!!

Files can be found here: http://forum.xda-developers.com/showpost.php?p=25561199&postcount=1

GROGG88 said:
Files can be found here: http://forum.xda-developers.com/showpost.php?p=25561199&postcount=1
Click to expand...
Click to collapse
Thanks GROGG88!
Also wanted to ask...I know you mentioned that after the procedures I will have everything stock but still with S-Off. Do you know if I can receive OTA with S-Off or will I have to adb and make it S-On again making the phone COMPLETELY stock.
Thanks again for all your help! I might have to follow these procedures sooner than I thought with the latest announcement about the OTA ICS!

GROGG88 said:
If you go by the guide in the link I posted then you'll be able to restore a stock nand if you have one. After that you can flash 1.18 hboot and stock recovery.
The easiest way would be to flash the RUU which will put EVERYTHING back to stock including firmware, but you'll keep s-off (which is good).
Sorry another related question...why is it good to keep s-off? Advantage?
Sorry again for all the questions! Hoping to expand my knowledge!
Click to expand...
Click to collapse

You can use the OTA with s-off. You want to keep s-off so that you can flash a custom recovery and re-root after the update. You can s-off the new bootloader, but it involves a new procedure that involves jumping a wire from a terminal to ground that many are not comfortable with.
It is much better to keep s-off...

GROGG88 said:
You can use the OTA with s-off. You want to keep s-off so that you can flash a custom recovery and re-root after the update. You can s-off the new bootloader, but it involves a new procedure that involves jumping a wire from a terminal to ground that many are not comfortable with.
It is much better to keep s-off...
Click to expand...
Click to collapse
Good to know! Thanks! So the new procedure requires you to do something physical to your phone? That sounds just wrong...I guess they really don't want s-off, huh?
I'll definitely keep s-off so I won't have to jump through these hoops!!!

[Q] OTA Updates on rooted, 111111, s-off, custom rom devices?

I have a couple questions.
I am on the 1.16 hboot with cid111111 and s-off unlocked tampered. twrp and maximus rom.
I finally did super cid and s-off on my one-s. Shortly after I recieved a notification that ota update 3.16.401.8 (612.27 mb) was available.
I was wondering if it would even work if i attempted to update. or would i have to update manually. Or would it brick it.
The main reason i would want to update is because the JB Sense roms just dont seem to run smoothly on my phone.
I was thinking this would update everything so the custom roms run smoother.
And Should i even update my hboot. does it make a difference.
I would usually be against it(ive had to downgrade other phones before).

Never take an OTA if you are on a custom rom with a custom recovery. Especially if you have SuperCID, unless you want a paperweight. If you want that OTA, you need to get you original CID, flash stock recovery, relock bootloader, then flash an RUU for your carrier.

impostle said:
Never take an OTA if you are on a custom rom with a custom recovery. Especially if you have SuperCID, unless you want a paperweight. If you want that OTA, you need to get you original CID, flash stock recovery, relock bootloader, then flash an RUU for your carrier.
Click to expand...
Click to collapse
Ok. ill look into that. sounds easy enough. last time i tried to update, i couldnt because of my cid. now i guess since there is an official t-mob i can do it?
You cant flash an ruu with super cid?
Oh and also, Once i update my hboot am i able to install the older ICS roms like maximus. thats just the most stable one i have found for my particular phone.
One more. Will i be able to restore my cid with s-off

ruu update
i relocked, then changed my cid to HTC__001
I triedto update via ruu exe file. but i got an error 155.
Im not sure how to update via the zip of the ruu. if its possible.
Also cant find any instruction or files for the original recovery.
I will try to install ota. hopefully i dont end up with a new frisbee.
If i were to extract the framwork.zip frim the ruu zip then install it via fastboot. would that give me the latest hboot. then maybe i could install the updates.

myphonesbetter said:
i relocked, then changed my cid to HTC__001
I triedto update via ruu exe file. but i got an error 155.
Im not sure how to update via the zip of the ruu. if its possible.
Also cant find any instruction or files for the original recovery.
I will try to install ota. hopefully i dont end up with a new frisbee.
If i were to extract the framwork.zip frim the ruu zip then install it via fastboot. would that give me the latest hboot. then maybe i could install the updates.
Click to expand...
Click to collapse
If you update your Hboot that kind makes it more difficult to flash custom roms. You should just find a nice custom jellybean rom, there are some good ones out there.

impostle said:
If you update your Hboot that kind makes it more difficult to flash custom roms. You should just find a nice custom jellybean rom, there are some good ones out there.
Click to expand...
Click to collapse
updating your hboot makes no significant difference (its a myth that its more difficult to flash custom roms on a later hboot).
im on latest hboot and can flash all things i want.
and if your device is S-off dont bother to relock your device/reinstall stock recovery. It will get overwritten anyways.
only thing important is to change the cid. you can always install a older hboot if s-off
have you tried the ruu.exe while in fastboot-usb?

real187 said:
updating your hboot makes no significant difference (its a myth that its more difficult to flash custom roms on a later hboot).
im on latest hboot and can flash all things i want.
and if your device is S-off dont bother to relock your device/reinstall stock recovery. It will get overwritten anyways.
only thing important is to change the cid. you can always install a older hboot if s-off
have you tried the ruu.exe while in fastboot-usb?
Click to expand...
Click to collapse
When I said it was more difficult I meant it was more work, having to flash the boot.img separately. If you are on a lower Hboot you don't have to do that. Also if you are going to suggest he do S-Off you should at least give him a warning about some of the issues people have ran into after doing it.
EDIT: Thats what I get for watching too many threads, I miss stuff.

impostle said:
When I said it was more difficult I meant it was more work, having to flash the boot.img separately. If you are on a lower Hboot you don't have to do that. Also if you are going to suggest he do S-Off you should at least give him a warning about some of the issues people have ran into after doing it.
Click to expand...
Click to collapse
he is already S-off. (see first post)
but anyways, if you dont do research before you do something, and it fuks up your device, its still gonna be your own fault.
what issues your talking about?

real187 said:
he is already S-off. (see first post)
but anyways, if you dont do research before you do something, and it fuks up your device, its still gonna be your own fault.
what issues your talking about?
Click to expand...
Click to collapse
I saw a thread about people losing 3g/4g data after an S-Off.
With S-Off you are made in the shade, you can downgrade your Hboot just by running the appropriate RUU. But you have to change your CID back to what is was before you try to flash the RUU.

impostle said:
I saw a thread about people losing 3g/4g data after an S-Off.
With S-Off you are made in the shade, you can downgrade your Hboot just by running the appropriate RUU. But you have to change your CID back to what is was before you try to flash the RUU.
Click to expand...
Click to collapse
I have seen the tread. But im scepitical, because if it really was only because of the s-off more people should have it. Might be hardware related.
Eh you do not have tot change back your Cid to original (if its a branded Cid the ruu still wont run), just a valid HTC Cid.
Verstuurd van mijn One S met Tapatalk

He could flash from recovery or fastboot flash any hboot he wants with s-off. No RUU needed for downgrade or upgrade. That's only needed to go back to stock for warranty purposes.
@myphonesbetter
If you want the red warning text overlay to be gone as well choose any of the files here and flash it within recovery. S-Off needed to do so!
To remove ***Tampered*** as well download hboot 1.140004. You will need to come from a lower hboot version so if you're already on >1.140004 flash one <1.140004 first.
--- edit ---
You can lock/unlock your phone as well by flashing. Read more in [how to] reset your lock status flag. Also it's in the Droid DNA forums it's valid for One S. Remember: You need s-off for this to work.
--- and one more ---
You can change your CID pretty simple on rootet devices. Just enter fastboot mode and type:
'fastboot oem writecid HTC__001'
Reboot bootloader then. You can find a collection of HTC ONE S CID's here

^^^^^Very helpful post. thank you. I wouldve never found that.
When you run the ruu .exe, do you have to be in fastboot or in android? The install app told me just to turn the phone on so i figured it would automatically go into bootloader. but it did nothing at all to my phone and gave me an error 115.
When i tried the ota it tells me that I am runnning an altrered OS and i will have to install it a different way.
Sorry for the easy questions. but i just cant seem to find any threads that say how to. I found the ruu and a zip of the ruu. but not how to install it.
The best sense rom has instructions on flashing a newer hboot. .but i want to install a completely stock rom.

myphonesbetter said:
^^^^^Very helpful post. thank you. I wouldve never found that.
.
Click to expand...
Click to collapse
guess you run out of thanks, no?

Never even noticed the thanks meter. I have more of a direct thank you approach.
I tried to flash the ruu .exe in fastboot. and it actually rebooted into the black htc screen, so i figure thats the way to do it.
Unfortunately I got another error. image error (159) use the correct rom and flash again.
I am attempting to flash 3.16.401.8 onto hboot 1.16 (relocked) i am s-off and i changed my cid to HTC__001 via fastboot.
Is there another way. or can i flash the zip in twrp or cwm? Again i just want an oem jelly bean with the proper hboot and radio and everything that the OTA would change. so i can be up to date before i move on to the JB roms.
Ive tried all of the custom ones, and the wifi cuts in and out. i used the wifi partition fix. and i flashed the latest radio. nothing helped for more than a few hours.

don't know what to say; normally you can flash whatever rom you want without problems;
guess 99% of users here did it.
however I can not understand what do you want to be full stock? warranty problems?

ultimul said:
don't know what to say; normally you can flash whatever rom you want without problems;
guess 99% of users here did it.
however I can not understand what do you want to be full stock? warranty problems?
Click to expand...
Click to collapse
Yah thats usually how it works for me. if it works for 99% of people with one step. ill have to do it manually with 20 steps. I guess its made me learn alot about adb and fastboot. I could never get adb to work untill i upgraded to windows 7 recently. until then i had to exract everything to my sdcard via terminal emulator and then drag it to my computer form the card and modify things. but ive been forced to learn quite a bit.
Its weird. I bought my phone off of craigslist from someone who had no idea how to root. But when i opened it into hboot it said Tampered and locked. with no signs of ever being unlocked. completely stock rom and no red warning text on the splash screen.
The reason i want to be stock it so i know all the correct partitions and everything are set up right. (that part i dont understand yet).
I know that a normal system wipe in twrp or cwm doesnt wipe everything. If i wipe and install the same rom i am using(just to clear it up and start over) it doesnt even wipe the app data. (at least on my phone)
Im thinking that its because i am installing a euro rom with a HTC__001 cid and mine was originally TMUS T-MOB010 .
one thing i noticed also is that windows could not verify either of the ruus i downloaded from shppied roms
How do i flash the ruu.zip that i downloaded? Do i need to rename it update.zip like the older phones? Its been a while.

Ok so i know im pretty much helping myself here but i hate when i come across threads with no conclusion.
I was able to succesfully update with the t-mob 2.35 ruu .exe thats on shipped roms .com so i know its not a problem with my computer.
still on hboot1.14 (thought i was on 1.16).
I changed my cid back to t-mob010.
Im just not sure why i cant update with the htc__001 with the 3.16 update.
Any help would be appreciated.

Ahh, things go on here! Nice! :laugh:
It's not quite clear if the RUU is the right one on this phone as many people report problems... So let's go OTA.
To flash the 3.16 OTA update your hboot needs to be < 2.15, your recovery needs to be the HTC stock one , your device needs to be relocked (not totally shure as mine wasn't at that time and it worked, but please remember that) and you need to have HTC stock system/ and stock data/ (ICS) files on your phone (you'll have to unroot as well, if rootet), as the OTA seems to check if certain files are present before working.
All that is quite a pain in the ass, isn't it?! So do one the following:
- Just make shure your bootloader version is lower 2.15, else flash a lower one.
- Click here and you'll have access to one of my google drive folders.
- Download the 2.31 zip. Unpack and copy these nandroid backup files into the appropriate TWRP folder on your phone, reboot into recovery and restore. Once done, you'll be able to flash the 3.16 OTA update after reboot. Remember to change CID before if you're on 11111111.
- Or download the 3.16 zip, unpack and restore. You'll have stock htc sense JB without the OTA. You don't even need to downgrade your bootloader in case. CID doesn't matter here.
- To root simply download SU_Bbox file and flash in recovery.
Important: With the JB update HTC invented disk write protection by default. This simply means that files deleted within stock sense JB will be back after rebooting the phone, also root was granted and working (still grats to htc for this one!!!). Check out for elemental x kernel at this point, as flar2 is the one offering additional modules for the stock kernel working around this. So you can be on stock JB as close as possible with write protection disabled.
--- edit ---
I nearly forgot: If you're experiencing WiFi troubles afterwards search for flashing wifi partitions.
--- and one more ---
myphonesbetter said:
I was able to succesfully update with the t-mob 2.35 ruu .exe thats on shipped roms .com so i know its not a problem with my computer.
still on hboot1.14 (thought i was on 1.16).
I changed my cid back to t-mob010.
Im just not sure why i cant update with the htc__001 with the 3.16 update.
Click to expand...
Click to collapse
Cause you're on 2.35 US. You need to be on 2.31 EU before, because 3.16 is EU and there is still no JB update to 2.35 US. 3.16 OTA will work with htc__001 (htc worldwide).

The OTA determined my OS was modified.
I could not restore the folder i took directly out of the zip.
There was a folder inside the folder that contained the same files. I was able to flash this.
My hboot is still at 1.14 my cid is not htc--001 relocked. the update was 650 mb of which i could not use wifi for becauese it just said error.
so 650 mb through tmobile. only took a few minutes but used almoast half of my months dl limit.
IDK. i found instructions on how to update the hboot in best sense roms thread. i will try that.
Edit: the restore for 3.16 worked in twrp. shouldve tried that first.
I may still update my hboot. I cant really find any instructions. Apparently the search just finds every thread and lists it.

If you are on the latest TWRP 2.4.3.0 go back to 2.4.1.0 (the latest one seems to have restore problems).
The folder contained in the zip needs to be copied to /TWRP/BACKUPS/HT23whatever/
You should be able to restore then.
--- edit
hehe, ok then.
You can flash any of these hboots from within TWRP. Up or down, it doesn't matter - you're s-off.
---------- Post added at 10:43 AM ---------- Previous post was at 10:32 AM ----------
CID should be HTC__001 not htc--001. Maybe a typo.

[Q] Desperate - Need Help

Two years ago I had this phone and I wanted to flash. I did. I don't remember all the details of it, but I do know that someone on here helped me flash it and it ended up with a European(?) flash on it and I remember he helped me do something with the radio in order that it would take the flash. I also remember that the reason for the flash was so that TMO wouldn't charge me for tethering. In any case, here's the current situation. I sold the phone and the person came and said they were having issues... so I was trying to restore it to a TMOUS ROM. Eventually, I bricked it, and got the qualcom download mode issue. I found the thread on that on how to fix it, and I did. Now the phone boots to the recovery screen and does nothing else. I am unable to flash ANY of TMO's RUU's, some of the PG58IMG.zip files that I've been able to find all fail... very frustrating.
I followed another thread that talked about how to unlock the bootloader, which involved copying the Identifier Token and sending it in to HTC. I received the response, and ran the command and was successful in unlocking it. When the device rebooted, it even showed the Tmobile animated logo. When I go back into the boot loader, it now reads:
My bootloader screen reads as follows:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT - 1.27.0000
eMMC-boot
JAN 13 2012.17:33:34
Software info shows:
Android Version: 4.0.3
HTC Sense Version: 3.6
Software number: Blitz_2.0.0
Kernel: 3.0.16-gda3fdfc
[email protected]#1
Baseband version: 11.76A3504300U_11.24A.3504.31_M
Build Number 3.33.401.106 CL391535 release-keys
Browser version: WebKit/534.30
At this point, I would try any flash, any rom, any thing to get this phone working for the guy again. I am skittish about flashing anything from this point so I don't mess up and have to start all over somewhere. Can I flash something working from this point? Can I flash a TMO RUU from here?
I have the RUU_Pyramid_TMOUS_1.27.531.2_RADIO_10.42.9007.00P_10.11.9007.15_M_release_192098_signed.exe as well as several others. Id' rather put this phone onto something stock from tmo but will do a custom as long as the phone is restored to working order.
I won't say I'm a newb... but having been away from flashing for a while, I could really use some step by steps to get going again.
The computer I am using to flash with is a Windows XP machine with all the HTC drivers working etc.
**** UPDATE ****
The phone now boots up as it did when this all started. After I did the token thing and got the bin file from HTC, I applied it and the result was the boot loader info above. It got past the tmobile animated logo and actually into the phone starting up as new including applying all the settings I want. Awesome that the phone now functions like a phone again, but I would still like to flash an official TMO Rom to it to restore it back to like out of the box condition. Any help is appreciated.

read this thread
http://forum.xda-developers.com/showthread.php?t=1672425

rzr86 said:
read this thread
http://forum.xda-developers.com/showthread.php?t=1672425
Click to expand...
Click to collapse
I actually have read that... like 6 times to make sure I'm not missing anything. I do remember having to flash the radio back when I did my original flashing, and I think that process is preventing me from using any of the RUU's that I find. Are there any posts/files/resources that will help me flash the radio back to its default, so that I can then flash the RUU?
Also, I am S-ON already, but ANY RUU that I try to flash fails. Do I need to go to S-OFF and then RUU, then back to S-ON?

sc.lord said:
I actually have read that... like 6 times to make sure I'm not missing anything. I do remember having to flash the radio back when I did my original flashing, and I think that process is preventing me from using any of the RUU's that I find. Are there any posts/files/resources that will help me flash the radio back to its default, so that I can then flash the RUU?
Also, I am S-ON already, but ANY RUU that I try to flash fails. Do I need to go to S-OFF and then RUU, then back to S-ON?
Click to expand...
Click to collapse
no you don't need S-OFF
post your cid

rzr86 said:
no you don't need S-OFF
post your cid
Click to expand...
Click to collapse
CID is 11111111
I think I have it licked now.
Used the universal firmware and the viper 5.2.1 flash and it loaded just fine. Never got S-OFF on it, but the viper flash so far is working excellent.

sc.lord said:
CID is 11111111
I think I have it licked now.
Used the universal firmware and the viper 5.2.1 flash and it loaded just fine. Never got S-OFF on it, but the viper flash so far is working excellent.
Click to expand...
Click to collapse
how do you have supercid with S-ON?
also how did you flashed the universal firmware while on S-ON?
those two things can be done only on S-OFF

rzr86 said:
how do you have supercid with S-ON?
also how did you flashed the universal firmware while on S-ON?
those two things can be done only on S-OFF
Click to expand...
Click to collapse
Wish I could tell you.... hence the reason for the original help request.
I can tell you that I hit softbrick on it once and had to unbrick in linux.
Then I got the LOCKED with Security Warning. Then I got the unlock bin file from HTC Dev, used that and got back to UNLOCKED, with no security warning. Then I tried Rumunner without any success at all, stayed S-ON.
in any case, after trying just about everything I could think of, I found the viper post, saw that you said you don't need S-OFF to flash new rom... so i gave it a shot. Updated EXT, flashed the firmware, then the rom and it all went very smoothly. Phone's been working fine since. <shrug>