Database Info

[Q] Other possibility to flash my phone to stock ROM?? RUU doesn't work

Hi.
I bought my Sensation few days ago. Updated it to 1.45.401.2, got bored with stock Rom. So I decided to unlock bootloader to use CustomeRoms
I removed SIMCard from Sensation (I needed it in my old phone) and used official bootloader unlocker tool from this site http://www.htcdev.com/bootloader and everything went ok. After unlocking I rebooted my phone to bootloader and saw this:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
Good so far.
Installed Recovery 5.0.2.0 (official tool doesn't include this) - no problem.
Downloaded ROM SlimSense, made full wipe (cache, data system, dalvik etc) installed it per Recovery (succesfully), rebooted and.... the problems started.
After rebooting bootloop started. Full wipe, reinstalation (succesful again), reboot and the same - bootloop.I thought that instalation .zip file maybe was broken - let's try different. Downloaded virtuous_sensation-s-pyramid-v3.0.0-beta ROM, full wiped, installed (succesfully), reboot and... the same - bootloop.
I started suspecting something is wrong so decided to cure my phone by flashing stockROM. Downloaded RUU_Pyramid_HTC_Europe_1.45.401.2_Radio_10.56.9035 .00U_10.14.9035.01_M_release_208857_signed from XDA, full wiped with recovery, and tried to flash it -RUU founds my phone, reboot it to start instalation (black screen with white htc- missing percentage info) and try to send files to phone for 15-20 sec - then RUU show message that it cannot update my phone. When I unplug phone from usb, phone goes back to bootloader and show:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
RUU
Security fail!
Update fail!
After this "try" i still have fully working Recovery. I tried also 1.35 and 1.73 stock ROMs - the same fail
I tried to unlock super cid 11111111 but it didn'twork - some SMART_IO.CRD file is missing.
Then i tried to use revolutionary way of unlocking, but without system on the phone it doesn't recognize it. And i can't have system cause RUU doesn't work.
Then I remembered that my SIM card is out of phone.
So I put it back but it didn't change anything: full wipe, instalation of SlimSense, reboot and... bootloop again, the same with virtuos.
The same fail with RUU! , the same supercid and revolutionary failure.
So here comes my question:
Is there any other posibility to flash stock ROM? PG58img somehow?
Pls - DON'T TELL me that i should use revolutionary first - i know it now.
Tell me how to solve this problem.

Tachion81 said:
Hi.
I bought my Sensation few days ago. Updated it to 1.45.401.2, got bored with stock Rom. So I decided to unlock bootloader to use CustomeRoms
I removed SIMCard from Sensation (I needed it in my old phone) and used official bootloader unlocker tool from this site http://www.htcdev.com/bootloader and everything went ok. After unlocking I rebooted my phone to bootloader and saw this:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
Good so far.
Installed Recovery 5.0.2.0 (official tool doesn't include this) - no problem.
Downloaded ROM SlimSense, made full wipe (cache, data system, dalvik etc) installed it per Recovery (succesfully), rebooted and.... the problems started.
After rebooting bootloop started. Full wipe, reinstalation (succesful again), reboot and the same - bootloop.I thought that instalation .zip file maybe was broken - let's try different. Downloaded virtuous_sensation-s-pyramid-v3.0.0-beta ROM, full wiped, installed (succesfully), reboot and... the same - bootloop.
I started suspecting something is wrong so decided to cure my phone by flashing stockROM. Downloaded RUU_Pyramid_HTC_Europe_1.45.401.2_Radio_10.56.9035 .00U_10.14.9035.01_M_release_208857_signed from XDA, full wiped with recovery, and tried to flash it -RUU founds my phone, reboot it to start instalation (black screen with white htc- missing percentage info) and try to send files to phone for 15-20 sec - then RUU show message that it cannot update my phone. When I unplug phone from usb, phone goes back to bootloader and show:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
RUU
Security fail!
Update fail!
After this "try" i still have fully working Recovery. I tried also 1.35 and 1.73 stock ROMs - the same fail
I tried to unlock super cid 11111111 but it didn'twork - some SMART_IO.CRD file is missing.
Then i tried to use revolutionary way of unlocking, but without system on the phone it doesn't recognize it. And i can't have system cause RUU doesn't work.
Then I remembered that my SIM card is out of phone.
So I put it back but it didn't change anything: full wipe, instalation of SlimSense, reboot and... bootloop again, the same with virtuos.
The same fail with RUU! , the same supercid and revolutionary failure.
So here comes my question:
Is there any other posibility to flash stock ROM? PG58img somehow?
Pls - DON'T TELL me that i should use revolutionary first - i know it now.
Tell me how to solve this problem.
Click to expand...
Click to collapse
PG58img ??? yes, you can try this : http://goo-inside.me/ruu/pyramid/fu...00U_10.14.9035.01_M_release_208857_signed.zip
after download, rename to PG58IMG.zip and move to root of your sd-card, enter to bootloader -> flash this...

i could be wrong (not an expert) but maybe its failing because your phone still says its S-ON

vegi71 said:
i could be wrong (not an expert) but maybe its failing because your phone still says its S-ON
Click to expand...
Click to collapse
As far as I know Official bootloader unlocker gives only "UNLOCKED" and it's enough to flash custom ROMs.
@ ranggazay
I extracted rom.zip from StockROM 1.45 renamed it to PG58IMG.zip and tried to flash but still nothing. Also tried the same earliers StockRoms (1.35, 1.27 etc).
Unfortunately I can't use your file cause i gave my phone to service.

Any solution?
Hello,
did you find a solution to the problem? I experienced this today and thinking about a repair unless I find something here. Did you get any solution? Thank you.

Try flashing the RUU again whist the phone is on FASTBOOT-USB

Same problem here - I'm interested in any solution

Tachion81 said:
As far as I know Official bootloader unlocker gives only "UNLOCKED" and it's enough to flash custom ROMs.
@ ranggazay
I extracted rom.zip from StockROM 1.45 renamed it to PG58IMG.zip and tried to flash but still nothing. Also tried the same earliers StockRoms (1.35, 1.27 etc).
Unfortunately I can't use your file cause i gave my phone to service.
Click to expand...
Click to collapse
S on will not allow you to flash radios. Unlocked bootloader through HTC does not give you s off which is a requirement to flash custom ROMS.
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium

Htc dev method unlock only few parts of the bootloader.
It doesn't unlock the radio area, it doesn't give you advanced fastboot write command access (that's why you can't change your cid) and I think that the boot.img partition (where there is the kernel) is not flashable from recovery.
You unlocked your bootloader on a 2.3.4 rom (with a 2.3.4 kernel, sense 3.0) and you tried to flash two 2.3.5 roms.
Without the possibility to flash a new kernel your phone was trying to boot with a 2.3.4 stock kernel + a rom that was meant for 2.3.5. This could be the cause of your bootloops.
I would try to install a 2.3.4 rom, like android revolution HD 3.x.x, you could have problems with wifi but it should boot at least.

First of all get S-off then supercid ur phone. You need to have s off to install any custom Rom properly. Ones you do that hopefully solve problem. Try not to messing around u might brick ur phone. You already void ur warranty by unlocking bootloader.
Sent from my HTC Sensation Z710e using xda premium

su27 said:
Same problem here - I'm interested in any solution
Click to expand...
Click to collapse
Grandelama said:
Htc dev method unlock only few parts of the bootloader.
It doesn't unlock the radio area, it doesn't give you advanced fastboot write command access (that's why you can't change your cid) and I think that the boot.img partition (where there is the kernel) is not flashable from recovery.
You unlocked your bootloader on a 2.3.4 rom (with a 2.3.4 kernel, sense 3.0) and you tried to flash two 2.3.5 roms.
Without the possibility to flash a new kernel your phone was trying to boot with a 2.3.4 stock kernel + a rom that was meant for 2.3.5. This could be the cause of your bootloops.
I would try to install a 2.3.4 rom, like android revolution HD 3.x.x, you could have problems with wifi but it should boot at least.
Click to expand...
Click to collapse
Same problem but with different unit--- I have a HTC ChaCha.
Any solutions please? I would love to get S-OFF on my ChaCha but I know that is only possible via an XTC Clip.
Why would he have problems with WiFi? I think my stock ROM got broken or one of the stock ROM's kernels got messed up when I installed BusyBox because for some odd reason when I restored to factory settings with stock ROM the WiFi had problems connecting. It couldn't connect to anything at all.

I had same problem and this is how I solved it
Ok here is answer to solve you
Flash any 2.3.5 Rom and open that zip in computer and extract the boot.IMF file and place it to the web folder in c drive and and flash it immediately after installing Rom
Go to bootloader and make sure fastboot USB connected and then flash the boot.IMG file from cmd prompt
Sent from my HTC Sensation Z710e using XDA

With s-on and **unlocked** via htc.dev, you can't flash radio.img or boot.img, nor can you write using fastboot (eg. superCID). RUU will not run with s-on.
You will need to revert and downgrade via this guide, you can then either continue with custom flashing or run the ruu correct for your original software/baseband/carrier/location.
http://forum.xda-developers.com/showthread.php?p=23222794
Sent from my Pyramid-T

solution
ok here is solution
just after u unlocked your bootloader u have to keep stock rom.....means official 2.3.4 and then u need to flash android revolution rom "3.6.x"
then after that rom boots...........just open the revolutionary.exe and try to root it and i am sure u will get s-off
this is what i did to get out of this problem.......after this super cid your phone and u will be able to flash any ruu.....
if u think this helped press thanks button

ptlsajan said:
ok here is solution
just after u unlocked your bootloader u have to keep stock rom.....means official 2.3.4 and then u need to flash android revolution rom "3.6.x"
then after that rom boots...........just open the revolutionary.exe and try to root it and i am sure u will get s-off
this is what i did to get out of this problem.......after this super cid your phone and u will be able to flash any ruu.....
if u think this helped press thanks button
Click to expand...
Click to collapse
Flashing a custom ROM does not give you s off. Which part of you can't flash radios and kernels with s on do you not get?. You cannot flash Android Revolution ROM with s on. Read the OP of the thread, requires s off.
from my HTC Sensation 4G with Beats Audio using xda premium

Rhiannon224 said:
Flashing a custom ROM does not give you s off. Which part of you can't flash radios and kernels with s on do you not get?. You cannot flash Android Revolution ROM with s on. Read the OP of the thread, requires s off.
from my HTC Sensation 4G with Beats Audio using xda premium
Click to expand...
Click to collapse
You're wrong. You can flash ARHD with s-on. The only requisite is to flash the kernel (boot.img) by "fastboot flash boot boot.img" and voila. You need to have the unlocked bootloader with htcdev too.
My Sensation came with HBOOT 1.21, so no revolutionary at all. I unlocked by htcdev, installed 4ext recovery and ARHD 4.1.3 this way.

nangu said:
You're wrong. You can flash ARHD with s-on. The only requisite is to flash the kernel (boot.img) by "fastboot flash boot boot.img" and voila. You need to have the unlocked bootloader with htcdev too.
My Sensation came with HBOOT 1.21, so no revolutionary at all. I unlocked by htcdev, installed 4ext recovery and ARHD 4.1.3 this way.
Click to expand...
Click to collapse
i read that HBOOT 1.21 can be S-OFFed " reported done by a member " in [S-OFF] Juopunutbear S-OFF or [Finally Here!] HTC Unbricking Project threads , i don't remember if the device on GB or ICS
i think it is Juopunutbear S-OFF search inside it [S-OFF] Juopunutbear S-OFF , it is done using the wire trick , link http://unlimited.io/
the only comment i have , is to verify the S-OFF type , is it like hardware S-OFF " i.e can't be S-ON again for warranty reasons ? " or it Software S-OFF

ruu security fail update fail
hi
i am using htc explorer. somedays before i unlocked my phone through htc developer site. After that i made a partition in my sd card to increase internal memory of phone via using link2sd apps.
i found that my old application like ndtv which were already installed in my phone are not working .i reset my mobile by going into its setting menu.
Now phone stucks htc word screen.
To get out of the problem i tried to installed ruu.
But at the last of its installation part
i get an error 155
and get an message
ruu
security fail
update fail
after rebooting my phone it stucks to htc
show me the way to get out of it.

nirajkpatle said:
hi
i am using htc explorer. somedays before i unlocked my phone through htc developer site. After that i made a partition in my sd card to increase internal memory of phone via using link2sd apps.
i found that my old application like ndtv which were already installed in my phone are not working .i reset my mobile by going into its setting menu.
Now phone stucks htc word screen.
To get out of the problem i tried to installed ruu.
But at the last of its installation part
i get an error 155
and get an message
ruu
security fail
update fail
after rebooting my phone it stucks to htc
show me the way to get out of it.
Click to expand...
Click to collapse
if i remember well error 155 means connection issues
but i can't tell you more because you came in a sensation/xe/4g forum
search for your device's forum and ask there

Can't Apply ICS OTA update

I never rooted my phone, it was done halfway there in procedure (never installed a custom ROM)
I had installed bootloader (4ext) and S-off
As of now on the phone I had a rom backup using 4ext for January (back when I was trying to root)
I waited long and hard for the OTA ICS update, which now I realize is out for Bell.
I tried to apply the update, phone reboots and 4ext tries to perform the update and I get a path error SDCARD\download\ (update file name)
Alternatively I tried booting up 4EXT and using "update from zip", with the OTA update file, and that applies and reboots to a stuck HTC white screen.
I just want to get this OTA update installed, thanks for advice!!!
PS: I don't think a factory reset is possible, I don't know where the factory reset data is stored or if its gone

funkbro2 said:
I never rooted my phone, it was done halfway there in procedure (never installed a custom ROM)
I had installed bootloader (4ext) and S-off
As of now on the phone I had a rom backup using 4ext for January (back when I was trying to root)
I waited long and hard for the OTA ICS update, which now I realize is out for Bell.
I tried to apply the update, phone reboots and 4ext tries to perform the update and I get a path error SDCARD\download\ (update file name)
Alternatively I tried booting up 4EXT and using "update from zip", with the OTA update file, and that applies and reboots to a stuck HTC white screen.
I just want to get this OTA update installed, thanks for advice!!!
PS: I don't think a factory reset is possible, I don't know where the factory reset data is stored or if its gone
Click to expand...
Click to collapse
man, mustn't update with official ota updates when you are rooted or s-off!

How can I s-on?

funkbro2 said:
How can I s-on?
Click to expand...
Click to collapse
Dude for ota soff is fine... Just flash the stock recovery And make sure cid is unchanged.. Then apply the OTA again
(just get the stock recovery.img from any gb RUU and flash it via fastboot
fastboot flash recovery recovery.img)
That's all... Dont lose soff... SOFF is fine For ota
Sent from my pyramid.. Through blazing fast sonic waves

funkbro2 said:
How can I s-on?
Click to expand...
Click to collapse
you can be S=OFF but you must have stock recovery installed not 4ext and with the rooted part you will loose when you update, so just flash the stock recovery back on your phone and you are set to update.

What may work for you is to try to install the stock Gingerbread RUU for your phone first. Since you can't boot into GB, you may have to extract the rom.zip file from the RUU, rename it to PG58IMG.zip and place it in the root folder of your sdcard. Then restart your phone into the Bootloader and Gingerbread should reload. You do not need to be S-ON. If that is successful, your bootloader and recovery will be back to stock and you should still be S-OFF. The OTA should work at that point.

Now why would I need to reflash to a previous rom, if I never rooted?
My phone boots when I reverted to the Jan 5 rom backup (which is still phone original rom)
I can definitely try installing original gingerbread rom and then apply the OTA update as suggested

funkbro2 said:
Now why would I need to reflash to a previous rom, if I never rooted?
My phone boots when I reverted to the Jan 5 rom backup (which is still phone original rom)
I can definitely try installing original gingerbread rom and then apply the OTA update as suggested
Click to expand...
Click to collapse
Didn't know you were able to recover from a backup. Thought you were stuck on the white HTC screen. In that case, go ahead and try to fall back to a stock recovery, then try to do the OTA.

OTA still fails for same reason
After downloading OTA update, clicking apply.. Phone restarts and loads up 4EXT which proceeds to apply update. And then results in the cannot load path error

funkbro2 said:
OTA still fails for same reason
After downloading OTA update, clicking apply.. Phone restarts and loads up 4EXT which proceeds to apply update. And then results in the cannot load path error
Click to expand...
Click to collapse
As long as you don't have the stock recovery the OTA fails.. Read my previous post.. For God sake
Sent from my pyramid.. Through blazing fast sonic waves

Used RUU to flash back to "original"
Then did OTA update and it worked no problems
Now using ICS from OTA
Thank you everyone

ganeshp said:
Dude for ota soff is fine... Just flash the stock recovery And make sure cid is unchanged.. Then apply the OTA again
(just get the stock recovery.img from any gb RUU and flash it via fastboot
fastboot flash recovery recovery.img)
That's all... Dont lose soff... SOFF is fine For ota
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
Will this work if I have SuperCID, or do I need to change it back?
Also, once OTA update is done, just reflash 4EXT and then SuperSU?

alza6991 said:
Will this work if I have SuperCID, or do I need to change it back?
Also, once OTA update is done, just reflash 4EXT and then SuperSU?
Click to expand...
Click to collapse
probably you have to change your cid to original
and yes after ota update flash 4ext again

rzr86 said:
probably you have to change your cid to original
and yes after ota update flash 4ext again
Click to expand...
Click to collapse
Posted in help thread, but asking you as well:
My phone is HTC Sensation XE, from Australia on Vodafone network.
I need to change my CID back to original, but I can't remember if it was:
HTC-Australia HTC__023
Hutch-Australia HUTCH001
VODA-Australia VODAP021
In Australia, the network is Vodafone-Hutchinson together, so I don't know which one to take.
Not sure what for, but x.xx.862.x - Voda-Hutch AU (Australia) is my provider/location code.
Any help is much appreciated, thanks in advance.

alza6991 said:
Posted in help thread, but asking you as well:
My phone is HTC Sensation XE, from Australia on Vodafone network.
I need to change my CID back to original, but I can't remember if it was:
HTC-Australia HTC__023
Hutch-Australia HUTCH001
VODA-Australia VODAP021
In Australia, the network is Vodafone-Hutchinson together, so I don't know which one to take.
Not sure what for, but x.xx.862.x - Voda-Hutch AU (Australia) is my provider/location code.
Any help is much appreciated, thanks in advance.
Click to expand...
Click to collapse
install cid getter app from play store
it will show the original cid

Why does my phone isn't updated ?

Hello!
I have a HTC One S. It's unlocked and completely unlinked from any carrier. I bought it like this and I never hacked the bootloader/installed custom ROM (not on this one ^^).
My software version is 2.21.401.10 and here's the OTA update : http://fotadl.htc.com/OTA_Ville_U_I....21.401.10_release_275774cltf0sxl730g7fp1.zip
But when I go in the software update menu and I check the updates, it says 'no update available'.
So my questions are :
1. Why?
2. Is there a way to install this OTA update manually (but keeping it an 'official' way) ?
Thanks!

jafar57 said:
Hello!
I have a HTC One S. It's unlocked and completely unlinked from any carrier. I bought it like this and I never hacked the bootloader/installed custom ROM (not on this one ^^).
My software version is 2.21.401.10 and here's the OTA update : http://fotadl.htc.com/OTA_Ville_U_I....21.401.10_release_275774cltf0sxl730g7fp1.zip
But when I go in the software update menu and I check the updates, it says 'no update available'.
So my questions are :
1. Why?
2. Is there a way to install this OTA update manually (but keeping it an 'official' way) ?
Thanks!
Click to expand...
Click to collapse
This OTA update is for phones with 1.78 version that is why it doesn't detect any updates.

Charkatak said:
This OTA update is for phones with 1.78 version that is why it doesn't detect any updates.
Click to expand...
Click to collapse
If you look at the URL correctly, you'll see that's the version to update from 2.21.401.10 and not from 1.78...
This one only weighs ~39Mo (against >150Mo for the other one)

The url is actually linking to is OTA_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5-2.21.401.10_release_275774cltf0sxl730g7fp1.zip which would be the OTA from 2.21.401.10 to 2.31.401.5 so I'm downloading it now to give it a try.
The problem is most likely that your CID doesn't match the ones that the update has been enabled for. You can use https://play.google.com/store/apps/details?id=org.tritonsoft.cidgetter to find it out. One of the threads listed the CIDs that people had success with. You can try downloading that file, renaming it to update.zip and booting into recovery to install it, but it will probably show an error because of your CID. In which case, you have to wait for the OTA to be pushed to your phone, or wait for an RUU to be available.

will1987 said:
The url is actually linking to is OTA_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5-2.21.401.10_release_275774cltf0sxl730g7fp1.zip which would be the OTA from 2.21.401.10 to 2.31.401.5 so I'm downloading it now to give it a try.
The problem is most likely that your CID doesn't match the ones that the update has been enabled for. You can use https://play.google.com/store/apps/details?id=org.tritonsoft.cidgetter to find it out. One of the threads listed the CIDs that people had success with. You can try downloading that file, renaming it to update.zip and booting into recovery to install it, but it will probably show an error because of your CID. In which case, you have to wait for the OTA to be pushed to your phone, or wait for an RUU to be available.
Click to expand...
Click to collapse
Thanks
My CID is HTC__203 but I didn't find the CIDs list.

jafar57 said:
Thanks
My CID is HTC__203 but I didn't find the CIDs list.
Click to expand...
Click to collapse
My cid is HTC__001 (which is one of the cid's in the zip) and I have placed the zip on the root of my sd card. When I boot into recovery nothing happens except it says something about sd not mounted.
How do I install this ota?
Running completely stock 2.21.401.10 from a RUU install.

I've 2.21 fw installed by RUU and bootloader locked. I try to install this update from recovery
(install update from external storage)
--Invalid Operation--
success rebooting by reasonem-00
CID 405
sorry for my bad english

jafar57 said:
Thanks
My CID is HTC__203 but I didn't find the CIDs list.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=30650526&postcount=6

Shouldn't super cid work I keep trying but won't install every time I choose apply update from external storage but it just errors and reboots
Sent from my HTC One S using xda premium

jafar57 said:
If you look at the URL correctly, you'll see that's the version to update from 2.21.401.10 and not from 1.78...
This one only weighs ~39Mo (against >150Mo for the other one)
Click to expand...
Click to collapse
I see what you mean, but when you open the zip file, there is txt, which indicates this: 1.78.401.2 CL58751 release-keys

Hey guys i have an S4 One S bought from Germany,shipped to Greece.I made the first OTA update from the 1st day and since then,my phone has this software number 1.77.111.5.My serial number is HT24WW405873.I have seen reports from people in my country, that they have got a notification for update to the newest 4.0.4 offered by HTC,but nothing on mine.Is it my serial number,or it is the software number(which is what i am most afraid of) fault?What to do to get updated if software number is the issue?

NickThess said:
Hey guys i have an S4 One S bought from Germany,shipped to Greece.I made the first OTA update from the 1st day and since then,my phone has this software number 1.77.111.5.My serial number is HT24WW405873.I have seen reports from people in my country, that they have got a notification for update to the newest 4.0.4 offered by HTC,but nothing on mine.Is it my serial number,or it is the software number(which is what i am most afraid of) fault?What to do to get updated if software number is the issue?
Click to expand...
Click to collapse
Is your phone locked to specific carriers or is it region free? As noted before the CID is important not the serial number. The CID identifies the device's locale. 1.77 is fairly old yes, my device is European (Netherlands) and it got an 1.78 update on the first day I got it. I only received 2.31 a few days ago so maybe best to just wait.

MattDN93 said:
Is your phone locked to specific carriers or is it region free? As noted before the CID is important not the serial number. The CID identifies the device's locale. 1.77 is fairly old yes, my device is European (Netherlands) and it got an 1.78 update on the first day I got it. I only received 2.31 a few days ago so maybe best to just wait.
Click to expand...
Click to collapse
I suppose it is locked to Deutsche Telekom or T-Mobile(dunno if they both exist in Germany),i get the purple T everytime i boot,before the "HTC one" screen.Its not written above the screen though.I downloaded the CID getter app and it says my CID is T-MOB101,but im confused that i dont get something similar to previous posters,like HTC_405 or HTC_203 ... Oh well,i will wait cos i don't wanna root etc. yet.

Successful flash OTA 2.31 on 2.21 RUU Europe
First make a backup of image/everything! i can not guarantee it will install with every CID on this planet. !!!OWN RISK!!!
I Just flashed the OTA 2.31 on RUU Europe 2.21.401.10. with CID HTC__E11 Netherlands.
You need an Unlocked and Rooted phone for this!
1. Change your CID to HTC__Y13 so that the OTA get triggered! (just do not install it yet! later!)
2. If you got SuperSu installed enable Survival mode!
3. Change your default CID Back and flash stock recovery! No ReLock needed! (you can update the phone now!)
[Important! default cid seems to be needed because of language files after the update i only got 4 languages DE/EN/FR/NL before arround 20?]
4. Reflash ClockWorkMod recovery.
5. After update install CWM-SuperSU-v0.95.zip with help of ClockWorkMod to regain root and turn off Survival mode later when booted!
Chainfire for SuperSU: http://forum.xda-developers.com/showthread.php?t=1538053
Wiki - [Tutorial]CID http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
- [Tutorial]Root, Unlock, Recovery http://forum.xda-developers.com/showthread.php?t=1583427
After this post i'm allowed to post in other categories, so i can make a tutorial if you guys want? with pictures etc...

CarstenDutch said:
First make a backup of image/everything! i can not guarantee it will install with every CID on this planet. !!!OWN RISK!!!
I Just flashed the OTA 2.31 on RUU Europe 2.21.401.10. with CID HTC__E11 Netherlands.
You need an Unlocked and Rooted phone for this!
1. Change your CID to HTC__Y13 so that the OTA get triggered! (just do not install it yet! later!)
2. If you got SuperSu installed enable Survival mode!
3. Change your default CID Back and flash stock recovery! No ReLock needed! (you can update the phone now!)
[Important! default cid seems to be needed because of language files after the update i only got 4 languages DE/EN/FR/NL before arround 20?]
4. Reflash ClockWorkMod recovery.
5. After update install CWM-SuperSU-v0.95.zip with help of ClockWorkMod to regain root and turn off Survival mode later when booted!
Chainfire for SuperSU: http://forum.xda-developers.com/showthread.php?t=1538053
Wiki - [Tutorial]CID http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
- [Tutorial]Root, Unlock, Recovery http://forum.xda-developers.com/showthread.php?t=1583427
After this post i'm allowed to post in other categories, so i can make a tutorial if you guys want? with pictures etc...
Click to expand...
Click to collapse
NickThess, Agrees this would be the only way to get that right...although CarstenDutch why did you flash the RUU as the OTA came out in Holland a few days ago?

MattDN93 said:
NickThess, Agrees this would be the only way to get that right...although CarstenDutch why did you flash the RUU as the OTA came out in Holland a few days ago?
Click to expand...
Click to collapse
If you are on 2.21 the OTA doesn't work. I am on 2.21 via the RUU and do not get any update.

Charkatak said:
I see what you mean, but when you open the zip file, there is txt, which indicates this: 1.78.401.2 CL58751 release-keys
Click to expand...
Click to collapse
No, the version.txt says "2.21.401.10 CL81535 release-keys"

CarstenDutch said:
First make a backup of image/everything! i can not guarantee it will install with every CID on this planet. !!!OWN RISK!!!
I Just flashed the OTA 2.31 on RUU Europe 2.21.401.10. with CID HTC__E11 Netherlands.
You need an Unlocked and Rooted phone for this!
1. Change your CID to HTC__Y13 so that the OTA get triggered! (just do not install it yet! later!)
2. If you got SuperSu installed enable Survival mode!
3. Change your default CID Back and flash stock recovery! No ReLock needed! (you can update the phone now!)
[Important! default cid seems to be needed because of language files after the update i only got 4 languages DE/EN/FR/NL before arround 20?]
4. Reflash ClockWorkMod recovery.
5. After update install CWM-SuperSU-v0.95.zip with help of ClockWorkMod to regain root and turn off Survival mode later when booted!
Chainfire for SuperSU: http://forum.xda-developers.com/showthread.php?t=1538053
Wiki - [Tutorial]CID http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
- [Tutorial]Root, Unlock, Recovery http://forum.xda-developers.com/showthread.php?t=1583427
After this post i'm allowed to post in other categories, so i can make a tutorial if you guys want? with pictures etc...
Click to expand...
Click to collapse
Some questions:
* My One S is rooted, but has the stock recovery. Do I need another recovery first? (edit: probably yes, because now it isnt unlocked?)
* I have SuperSU, but what do you mean with Survival method? Im from Belgium (Flandres), so I dont need more then the 4 languages you've got.
Thx for the advice!

MattDN93 said:
NickThess, Agrees this would be the only way to get that right...although CarstenDutch why did you flash the RUU as the OTA came out in Holland a few days ago?
Click to expand...
Click to collapse
I updated the 2.21 ota at the moment it was available for 1.78 with CID 11111111 because I couldn't wait! not so long ago, I am just a tweaker.
Ps. I installed the 2.21 ota over 1.78
and later on downloaded the 2.21 RUU to get a clean system after messing around with system files etc...
Tapatalk/Swiftkey
---------- Post added at 05:29 PM ---------- Previous post was at 05:00 PM ----------
superiscch said:
Some questions:
* My One S is rooted, but has the stock recovery. Do I need another recovery first? (edit: probably yes, because now it isnt unlocked?)
* I have SuperSU, but what do you mean with Survival method? Im from Belgium (Flandres), so I dont need more then the 4 languages you've got.
Thx for the advice!
Click to expand...
Click to collapse
*You can't be rooted with original recovery. Follow this, Unlock bootloader>Flash custom recovery>Flash SuperSu
*Survival mode means that it trys to stay rooted after ota update, after ota I need to flash the SuperSu.zip again to get permission rights to get it working again. So I guess it's not working really.
What CID are you on? Look for CID Getter on play store.
If you are not familiar with modifying just wait for official ota's or RUU (there is no huge/shocking improvement with 2.31 over 2.21. just a little smoother.
Tapatalk/Swiftkey

CarstenDutch said:
First make a backup of image/everything! i can not guarantee it will install with every CID on this planet. !!!OWN RISK!!!
I Just flashed the OTA 2.31 on RUU Europe 2.21.401.10. with CID HTC__E11 Netherlands.
You need an Unlocked and Rooted phone for this!
1. Change your CID to HTC__Y13 so that the OTA get triggered! (just do not install it yet! later!)
2. If you got SuperSu installed enable Survival mode!
3. Change your default CID Back and flash stock recovery! No ReLock needed! (you can update the phone now!)
[Important! default cid seems to be needed because of language files after the update i only got 4 languages DE/EN/FR/NL before arround 20?]
4. Reflash ClockWorkMod recovery.
5. After update install CWM-SuperSU-v0.95.zip with help of ClockWorkMod to regain root and turn off Survival mode later when booted!
Chainfire for SuperSU: http://forum.xda-developers.com/showthread.php?t=1538053
Wiki - [Tutorial]CID http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
- [Tutorial]Root, Unlock, Recovery http://forum.xda-developers.com/showthread.php?t=1583427
After this post i'm allowed to post in other categories, so i can make a tutorial if you guys want? with pictures etc...
Click to expand...
Click to collapse
The following was my Situation: 2.21.401.10 stock, unlocked stock recovery, rooted, Super CID (1111111). There were no update available. Even Downloading the above linked update, renaming it to update.zip and placing it on root of the sd, booting to recovery was no solution (got red triangle with exclamation in the recovery).
Changed my CID to HTC__001 which should work. (in the File I downloaded there is a list of CIDs which are allowed, HTC__001 is included). Rebooted to recovery tried to apply the update.zip. Again there was the red triangle with exclamation mark.
Now I changed my CID to the one mentioned from you HTC__Y13 and rebooted. And it works indeed. Now I was able to download the Software Update. Since I'm from Switzerland I didn't bother to change the CID again. So I choos to apply the Software-Update. But again ended in the recovery with the red triangle and exclamation mark.
EDIT: The stock recovery boots and there is a green bar below which fills quickly to approximately 1/4 then stopps and shows me a red triangle with exclamation mark.
any help is appreciated. thx in advance

[Q] stuck on splash-screen

Hey guys
I've got a bit of a situation. A friend of mine gave me this sensation (carrier T-mobiel) wich was all but bricked. Since I have some experience rooting and flashing custom ROMs, he asked me to give it a try at reviving it.
The owner had been messing around a bit himself and he managed to install clockwordmod recovery. Don't know if he installed any ROM, the device gets stuck on splashscreen.
I did the following; full format, superwipe and install a ARHD ROM. result was te same; stuck on splash-screen.
Then I did another full format, wipe and installed Cyanogenmod, still the same result.
I wanted to try and install 4EXT touch recovery, but the device doesn't respond to any USB connection method so ADB won't work. there's no working ROM so installing through the app won't go either. basicly, I don't know if there's a way to uninstall and install a recovery through flashing.
I have another phone to use to store required files on a SDcard.
these are the things dat DO work:
Bootloader, fastboot and clockworkmod recovery v5.8.0.9
this is the device's bootloader information
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.01_M
Aug 2 2011, 22:35:52
my guess is that I'm trying to install ROM's that don't work with the current firmware. I don't know if the owner installed the OTA ICS before he got these problems. But I don't know what firmware is currently on this this device, and how to check it.
Lost for clues here and calling out for help
Onemanshow

onemanshow85 said:
Hey guys
I've got a bit of a situation. A friend of mine gave me this sensation (carrier T-mobiel) wich was all but bricked. Since I have some experience rooting and flashing custom ROMs, he asked me to give it a try at reviving it.
The owner had been messing around a bit himself and he managed to install clockwordmod recovery. Don't know if he installed any ROM, the device gets stuck on splashscreen.
I did the following; full format, superwipe and install a ARHD ROM. result was te same; stuck on splash-screen.
Then I did another full format, wipe and installed Cyanogenmod, still the same result.
I wanted to try and install 4EXT touch recovery, but the device doesn't respond to any USB connection method so ADB won't work. there's no working ROM so installing through the app won't go either. basicly, I don't know if there's a way to uninstall and install a recovery through flashing.
I have another phone to use to store required files on a SDcard.
these are the things dat DO work:
Bootloader, fastboot and clockworkmod recovery v5.8.0.9
this is the device's bootloader information
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.01_M
Aug 2 2011, 22:35:52
my guess is that I'm trying to install ROM's that don't work with the current firmware. I don't know if the owner installed the OTA ICS before he got these problems. But I don't know what firmware is currently on this this device, and how to check it.
Lost for clues here and calling out for help
Onemanshow
Click to expand...
Click to collapse
Hi,
2 things you can try.
1.Run a GingerBread RUU.
Look HERE
2.If that works,try s-off.
Look HERE
Then,you could change firmwares and do whatever you like.

Hi Malybru,
I understand what you suggested and I'm currently working on it. Only I can't find the right RUU for this phone.
Current CID is: T-MOB003
getting it superCID'd was no go since I can't get it S-OFF with the revolutionary utility. is there another way to S-OFF the phone besides revolutionary?
edit: I downloaded and executed a RUU that apearantly wasn't compatible with the phone. I'm guessing it removed whatever ROM was installed, but didn't install the ROM from the RUU.
I also followed step 3; RUU to restore stock up to the part of relocking the bootloader. I didn't come any further cause I can't find the right RUU.
the phone now only boots into bootloader with "security warning" displayed below "relocked".
I'm guessing, if I find the correct RUU with gingerbread, things will be okay again.
on a sidenote, does a RUU install also returns the recovery to stock?

onemanshow85 said:
Hi Malybru,
I understand what you suggested and I'm currently working on it. Only I can't find the right RUU for this phone.
Current CID is: T-MOB003
getting it superCID'd was no go since I can't get it S-OFF with the revolutionary utility. is there another way to S-OFF the phone besides revolutionary?
Click to expand...
Click to collapse
Hi,
RUU does not matter too much as long as it is Europe and GB.
If you can find a dutch tmo ,then even better.
No harm will come if it is the wrong one.
It will only throw up an error.
This will at least get a ROM on your phone,so that you can s-off .
Revolutionary is the easiest way to s-off.

so, to summarize:
the RUU has to be TMO for either UK or EU. Does the radio need to match the one that's currently displayed in the bootloader?

onemanshow85 said:
so, to summarize:
the RUU has to be TMO for either UK or EU. Does the radio need to match the one that's currently displayed in the bootloader?
Click to expand...
Click to collapse
Hi,
The closer the match,the more chance of success.
But close will do.
Yes,with the same radio.

finding a dutch RUU with this radio for TMO is pretty challenging. So I tried it with a german version (DE). Other then that it matches the radio, and the carrier.
the first method through the RUU.exe failed, it tells me to get the right RUU for my carrier/phone.
So I tried it through flashing with a SDcard. I changed the CID in the notepad file in the PG58IMG.zip to T-MOB003. In bootloader, it checks the file twice and after that nothing happens, the regular bootloader screen is prompted.
Then I tried to flash it through fastboot CMD command, pretty much my last option according to the guid you linked me. This also fails with the notification that it failed to verify 12 signatures.
now I found some universal firmware packages but they don't seem to contain any ROM and recovery, only firmware. are there any of these universal packages as complete RUU?
or is there a way to bypass the signature check with a fastboot command?

onemanshow85 said:
finding a dutch RUU with this radio for TMO is pretty challenging. So I tried it with a german version (DE). Other then that it matches the radio, and the carrier.
the first method through the RUU.exe failed, it tells me to get the right RUU for my carrier/phone.
So I tried it through flashing with a SDcard. I changed the CID in the notepad file in the PG58IMG.zip to T-MOB003. In bootloader, it checks the file twice and after that nothing happens, the regular bootloader screen is prompted.
Then I tried to flash it through fastboot CMD command, pretty much my last option according to the guid you linked me. This also fails with the notification that it failed to verify 12 signatures.
now I found some universal firmware packages but they don't seem to contain any ROM and recovery, only firmware. are there any of these universal packages as complete RUU?
or is there a way to bypass the signature check with a fastboot command?
Click to expand...
Click to collapse
Hi,
Try the European RUU with the 10.14 radio that matches yours.
Add your CID in the PG58IMG text file.
Make sure you have the phone in fastboot when you attach your USB cable(it should say "fastboot USB"),and start running the RUU from your PC.

http://db.tt/A7lS7PaD
Here is a link to 4ext touch recovery as a IMG. http://db.tt/KFKpcrhB and here is a pg58img.zip. put the zip file onto the sdcard and boot to boot loader. It will hopefully flash the recovery. If not fast boot flash the IMG. Once you have the recovery installed enable smart flash and then flash the roms. Hopefully that will work for you
Sent from my HTC Sensation using xda premium

tnx for the files.
I tried the suggestions you made but flash from sdcard doesn't work; it checks the file once and doesn't do anything after it.
when I try to flash either one of the files through fastboot I get signature verification fail.
my bootloader says RELOCKED, I got that after following step 3.1 in the RUU flash guide to return to stock. I don't know if this is blocking anything from being flashed with the nasty signature notifications?
also, most like because nothing is installed on my device, when I plug in the USB cable when it's turned off, it automatically swithces on displaying SECURITY WARNING below RELOCKED.

Damn, wasn't fast enough. I'm not sure what the best way to approach this is. Either attempt to full s-off the device with revolutionary/ jupuntobear, or re-unlock your boot loader with htcdev, then fastboot flash the recovery. Then install the rom. Then run jupuntobear to full s-off
Sent from my HTC Sensation using xda premium

heavy_metal_man said the right thing. First focus on unlocking it on hTCdev.com and afterwards, flash a 4Ext Recovery to make things easyer. Then put the device in bootmenu (not in the Graphic shell) and attach a USB, start any Official European RUU that is Gingerbread - with 1.50 in the numbers.

an update
I managed to get it unlocked again with htcdev.com. After that I flashed 4EXT recovery, succesfully.
only thing now I need to do is installing a ROM. I tried the following without succes so far:
with RUU
I can't find a dutch RUU for TMO with radio 10.14.9035 anywhere so I tried the closest match possible, a german one. through the .exe method I get incompatibility errors. So I extracted the ROM/.zip, added my CID and tried with SDcard flash and fastboot flash, both unsuccesfull. Hboot checks the file twice and does nothing afterwards, and fasboot prompts the message "FAILED (remote ** unknown fail)"
Universal firmware package to make sure I'm on 3.32, so I can install ARHD 6.7.2 or any other ICS rom
I took one from http://forum.xda-developers.com/showthread.php?p=21711154#post21711154.
I get the same errors as when I was trying to flash the ROM.zip from the RUU, both with sdcard flash and fastboot flash.
a random Gingerbread ROM
I found this GB ROM http://forum.xda-developers.com/showthread.php?t=1226564.
I installed it through EXT4. after a reboot it's stuck in a bootloop. No splash screen is shown however, it get's to the withe-field-green-HTC-screen and reboots after, showing the same.
I don't understand what's wrong. I got a good recovery now and the bootloader is unlocked. For some reason the ROM's I tried are incompatible with the current state of the device and I can't figure out why. are dutch T-mobile branded phones so tough to crack or what?
also, after a certain step wich I can't remember, my bootloader doesn't display a radio anymore.
Current bootloader:
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
EDIT: I would be less restricted in my actions if the damn thing were to be S-OFF. is there any way to get get S-OFF through bootloader/fastboot? All the S-OFF methods and utillities I found so far need the device to have a ROM running.

SOLVED
with help of KGS1992, I managed to restore the device.
- installed a stock GB ROM since I was on hboot 1.18, and to get root acces
- aquired root through adb
- gained S-off with revolutionary
reason why I couldn't manage this before is because I didn't have a genuin stock ROM.
tnx all for the help

onemanshow85 said:
SOLVED
with help of KGS1992, I managed to restore the device.
- installed a stock GB ROM since I was on hboot 1.18, and to get root acces
- aquired root through adb
- gained S-off with revolutionary
reason why I couldn't manage this before is because I didn't have a genuin stock ROM.
tnx all for the help
Click to expand...
Click to collapse
Glad you got sorted pal and thanks for letting us know

[Tutorial] Update to hboot 2.15 via RUU

Running an RUU is only simple for those who haven't been messing with their devices, and that usually isn't us. Since I just did this, I want to write down the steps because I was not able to find easy answers.
This assumes your device is rooted with a different ROM installed. If that is not the case, then you can just download and run the RUU for your device, end of instructions.
Downloading the correct RUU
The most complete list of RUUs for Ville is found on androidruu.com
T-Mobile: http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
HTC Europe: http://www.androidruu.com/getdownlo...28_10.27.50.08L_release_301814_signed_2_4.exe
There are RUU updates listed for other service providers, but I can't tell if they are JellyBean hboot 2.15 or not. If someone knows, I'll update this post.
Preparing your device
Make your device s-off if it isn't already. Why?
You will not have to relock the bootloader to perform the RUU update.
You will not have to flash the boot image separately.
If for some reason you can't or won't go s-off, you can still do this, but will have many more steps to follow.
Instructions to make your device s-off are here for firmwares below 3.14: Facepalm S-Off for HTC Devices One S, One XL, Droid DNA
Or you can use the HTC All-In-One Toolkit which helps you through the process.
Use the HTC All-In-One Toolkit (link above) to change the CID to match the RUU.
You needed Super CID to gain s-off, but it won't help you install RUUs. Even if you are Super CID (11111111), you must change your CID to match the RUU you are installing (mine is TMobile: T-MOB010). I know, kinda defeats the purpose of being Super CID, but the RUU won't succeed otherwise. If you are s-off, it is a one click operation using the All-In-One Toolkit.
Backup your device
Use Titanium backup to backup all your user apps so you can restore them afterwards. (No, don't restore system apps please!)
Also back up your ROM by booting into recovery mode and selecting Backup.
If you are only updating the hboot but keeping the same ROM, you can just restore the backup afterwards. Not sure why anyone would need to update the hboot without installing a new ROM, but then you also have a backup in case things go wrong.
Run the RUU
If you are s-on you will have to relock the bootloader by rebooting into the fastboot mode, connecting your device to the computer and running the command "fastboot oem lock". You will also have to follow the process again to unlock your bootloader after doing the update. Tutorials for that are found elsewhere.
1. Leave bootloader unlocked, and leave s-off as is. No need to go back to s-on or relock bootloader.
2. Run the RUU and wait while it updates the phone (Incidentally, it didn't even wipe my sd partition data!)
3. While you are still in bootloader mode (before booting up), use the All-In-One tool to install the TWRP S4 recovery. Or, if you don't want to use the tool, you'll have to download a recovery and use "fastboot flash recovery" followed by the name of the recovery img file.
4. Reboot bootloader and enter recovery mode
5. Restore from backup or Mount USB from TWRP and copy over the ROM and gapps package, flash, wipe cache, and you are up and running.
If you are s-on you will need to extract the boot.img from the zip you are flashing and flash that image separately with "fastboot flash boot boot.img"
Note that device still has the unlocked bootloader and is still s-off! :victory:
My device before: hboot 1.09, unlocked bootloader, Super CID, s-off (In layman's terms, this is a device with an unlocked bootloader so it can accept other ROMs, set to accept any service provider's RUU update via SuperCID, and has had write permission to the boot sector removed via s-off).
My device after: hboot 2.15, unlocked bootloader, T-MOB010 CID, s-off
If possible, I will answer your comments or questions by updating this post and I'll refer you back to here.

Have you changed your CID?

mag13 said:
Have you changed your CID?
Click to expand...
Click to collapse
Please read again.
I was Super CID (11111111) but easily changed it to match TMobile (T-MOB010) with this tool for the update.
Click to expand...
Click to collapse

yooouuri said:
Please read again.
Click to expand...
Click to collapse
I am on Super CID and it does not work

mag13 said:
I am on Super CID and it does not work
Click to expand...
Click to collapse
You have to change your CID back to the one for your RUU.

Can I use this tutorial to rollback to 2.15 or whatever works for ViperS rom with sense 4 after I flashed MaximusHD and firmware?
Now my phone is like this:
Hboot 2.16
Radio 1.20.50 (worst radio ever)
S-OFF
CID 11111111
The rom's with sense 5 (I tried just maximus because the others are not compatible with the new firmware, the sdcard mount point for multi user) are killing my battery more than twice faster compared with ViperS. 2h Display vs 5h on Viper.
Thank you!

Can we use this as rollback from h-boot 2.16 ?

mag13 said:
I am on Super CID and it does not work
Click to expand...
Click to collapse
I didn't think it would. Glad you didn't brick your phone and I'll update the OP based on your experiment.

flow27 said:
Can we use this as rollback from h-boot 2.16 ?
Click to expand...
Click to collapse
arazvan2002 said:
Can I use this tutorial to rollback to 2.15 or whatever works for ViperS rom with sense 4
Click to expand...
Click to collapse
Upgrading your hboot is a one way street, as far as I know. Can't you change the radio to something else?

I flashed Viper ROM. All the things are ok, gsm, wifi, etc just I can't see the internal memory like I should. I can browse to it file es file explorer but I need a method to default mount the new (4.2.2) location of it. Where is mounted by the internal memory in 4.1 JB? I discovered a file vold.fstab. Maybe I can change something like that somewhere to be able to use 4.1 ROM's again.
Sorry for OFF topic.

Somebody asked it but i want a clear awnser.
Can i use it to roll back to 2.15 from 2.16?

yooouuri said:
Somebody asked it but i want a clear awnser.
Can i use it to roll back to 2.15 from 2.16?
Click to expand...
Click to collapse
Yes you can if youre s-off.
Sent from HTC One S using android 4.2.2 sense 5

Im s-off and changen my RUU back to the origonal.
Using RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
But i get the same error. Cant update because wrong "Update tool".
-------------------------------
Flashed orig_hboot_2.15.0000.zip
But im stuck on 1.20 Radio?

yooouuri said:
Im s-off and changen my RUU back to the origonal.
Using RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
But i get the same error. Cant update because wrong "Update tool".
-------------------------------
Flashed orig_hboot_2.15.0000.zip
But im stuck on 1.20 Radio?
Click to expand...
Click to collapse
Did you run the RUU.exe when your phone was in bootloader (fastboot USB mode)?

tivofool said:
Did you run the RUU.exe when your phone was in bootloader (fastboot USB mode)?
Click to expand...
Click to collapse
That's the right thing to do, yes?

kilo94 said:
That's the right thing to do, yes?
Click to expand...
Click to collapse
Yes

I have the same problem. I can't go back to stock. I haven't changed my CID yet but I see that has not worked for you.
Did you try with HTC__001 ?

dhigby said:
Running an RUU is only simple for those who haven't been messing with their devices, and that usually isn't us. Since I just did this, I want to write down the steps because I was not able to find easy answers.
This assumes your device is rooted with a different ROM installed. If that is not the case, then you can just download and run the RUU for your device, end of instructions.
Downloading the correct RUU
The most complete list of RUUs for Ville is found on androidruu.com
T-Mobile: http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
HTC Europe: http://www.androidruu.com/getdownlo...28_10.27.50.08L_release_301814_signed_2_4.exe
There are RUU updates listed for other service providers, but I can't tell if they are JellyBean hboot 2.15 or not. If someone knows, I'll update this post.
Preparing your device
Make your device s-off if it isn't already. Why?
You will not have to relock the bootloader to perform the RUU update.
You will not have to flash the boot image separately.
If for some reason you can't or won't go s-off, you can still do this, but will have many more steps to follow.
Instructions to make your device s-off are here for firmwares below 3.14: Facepalm S-Off for HTC Devices One S, One XL, Droid DNA
Or you can use the HTC All-In-One Toolkit which helps you through the process.
Use the HTC All-In-One Toolkit (link above) to change the CID to match the RUU.
You needed Super CID to gain s-off, but it won't help you install RUUs. Even if you are Super CID (11111111), you must change your CID to match the RUU you are installing (mine is TMobile: T-MOB010). I know, kinda defeats the purpose of being Super CID, but the RUU won't succeed otherwise. If you are s-off, it is a one click operation using the All-In-One Toolkit.
Backup your device
Use Titanium backup to backup all your user apps so you can restore them afterwards. (No, don't restore system apps please!)
Also back up your ROM by booting into recovery mode and selecting Backup.
If you are only updating the hboot but keeping the same ROM, you can just restore the backup afterwards. Not sure why anyone would need to update the hboot without installing a new ROM, but then you also have a backup in case things go wrong.
Run the RUU
If you are s-on you will have to relock the bootloader by rebooting into the fastboot mode, connecting your device to the computer and running the command "fastboot oem lock". You will also have to follow the process again to unlock your bootloader after doing the update. Tutorials for that are found elsewhere.
1. Leave bootloader unlocked, and leave s-off as is. No need to go back to s-on or relock bootloader.
2. Run the RUU and wait while it updates the phone (Incidentally, it didn't even wipe my sd partition data!)
3. While you are still in bootloader mode (before booting up), use the All-In-One tool to install the TWRP S4 recovery. Or, if you don't want to use the tool, you'll have to download a recovery and use "fastboot flash recovery" followed by the name of the recovery img file.
4. Reboot bootloader and enter recovery mode
5. Restore from backup or Mount USB from TWRP and copy over the ROM and gapps package, flash, wipe cache, and you are up and running.
If you are s-on you will need to extract the boot.img from the zip you are flashing and flash that image separately with "fastboot flash boot boot.img"
Note that device still has the unlocked bootloader and is still s-off! :victory:
My device before: hboot 1.09, unlocked bootloader, Super CID, s-off (In layman's terms, this is a device with an unlocked bootloader so it can accept other ROMs, set to accept any service provider's RUU update via SuperCID, and has had write permission to the boot sector removed via s-off).
My device after: hboot 2.15, unlocked bootloader, T-MOB010 CID, s-off
If possible, I will answer your comments or questions by updating this post and I'll refer you back to here.
Click to expand...
Click to collapse
Hey I used your instructions and everything was perfect thank you. I used to upgarde and downgrade hboot even to restore the HTC one S

I got the RUU "Error: 159" again with both RUU from first post and testet with each common cid, but at the end I only got success with super cid and the TMO_US Ruu.
Now I am back on Hboot 2.15 and can flash again the newest custom-recovery, thank you very much.
I've heard about a flashabe standalone zip for the hboot 2.15 and found this:
Only for S4!
Boot into bootloader and enable fastboot.
Code:
fastboot oem rebootRUU
Wait for the black screen with white HTC symbol. (Like when you flash a RUU)
then enter:
Code:
fastboot flash zip modded_hboot_YOUR_NEEDED_HBOOT.zip
then if you want
Code:
fastboot oem boot
(Boot into your current ROM)
modded_ = The red text is removed and "tampered" is gone in bootloader.
Download:
modded_hboot_1.06.0000.zip - (397.1 KB)
modded_hboot_1.09.0000.zip - (400.6 KB)
modded_hboot_1.13.0000.zip - (399.0 KB)
modded_hboot_1.14.0002.zip - (405.3 KB)
modded_hboot_1.14.0004.zip - (373.2 KB)
modded_hboot_1.14.0005.zip - (373.6 KB)
modded_hboot_2.15.0000.zip - (400.9 KB)
modded_hboot_2.16.0000.zip - (398.6 KB)
Thx goes to: touch of jobo XDA Post Source
DISCLAIMER:this is not my work. i have tested it on my own device,but use it at your own risk. if it melts your phone into a lil pile of goo,its not my fault.
Greetings by Idijt