Database Info

[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] Is there a RUU for HBOOT 1.27.1100

Hello,
my HTC SENSATION has the HBOOT Version 1.27.1100 and I want to download a RUU to restore my HTC device completely. But I can´t find a RUU with this HBOOT version.
I only have to download the right RUU and install it on my HTC device to restore it completely, right?

james0912 said:
Hello,
my HTC SENSATION has the HBOOT Version 1.27.1100 and I want to download a RUU to restore my HTC device completely. But I can´t find a RUU with this HBOOT version.
I only have to download the right RUU and install it on my HTC device to restore it completely, right?
Click to expand...
Click to collapse
Hi,
Download hboot 1.17 HERE
Then you can use an RUU for that firmware.

which ruu can i use now???
i only want to restore my htc sensation completely!

james0912 said:
which ruu can i use now???
i only want to restore my htc sensation completely!
Click to expand...
Click to collapse
Hi,
You need an RUU that matches your area and carrier.
Look HERE

malybru said:
Hi,
Download hboot 1.17 HERE
Then you can use an RUU for that firmware.
Click to expand...
Click to collapse
Hey malybru can you flash this file with the stock recovery? Also this only changes the Hboot version correct?

T-Macgnolia said:
Hey malybru can you flash this file with the stock recovery? Also this only changes the Hboot version correct?
Click to expand...
Click to collapse
Hi,
It's a PG58IMG.zip .
So, it's just placed on the sd card.
Recovery is not involved.
Yes,it will only change the hboot.

malybru said:
Hi,
It's a PG58IMG.zip .
So, it's just placed on the sd card.
Recovery is not involved.
Yes,it will only change the hboot.
Click to expand...
Click to collapse
Man I had a duh money, I realized after I posted that that that file will flash automatically when you boot to Hboot, as that is the file name that Hboot looks for. But still doesn't Hboot use the recovery to flash the file?

T-Macgnolia said:
Man I had a duh money, I realized after I posted that that that file will flash automatically when you boot to Hboot, as that is the file name that Hboot looks for. But still doesn't Hboot use the recovery to flash the file?
Click to expand...
Click to collapse
Hi,
I knew you knew that.
I just posted for general information.
I think it flashes in bootloader,before recovery starts.

malybru said:
Hi,
I knew you knew that.
I just posted for general information.
I think it flashes in bootloader,before recovery starts.
Click to expand...
Click to collapse
Ok this will be my last post here cause I don't want to hyjack this thread.
This has brought a question to mind and I will have to see if I can find the answer some how. The question is what does Hboot use to flash the PG58IMG.zip. I personally have always thought it used recovery to flash the file.

T-Macgnolia said:
Ok this will be my last post here cause I don't want to hyjack this thread.
This has brought a question to mind and I will have to see if I can find the answer some how. The question is what does Hboot use to flash the PG58IMG.zip. I personally have always thought it used recovery to flash the file.
Click to expand...
Click to collapse
It uses the bootloader to flash the file. If you put it on your sd card and reboot into bootloader (volume down button + power button) you will be asked to update. Choose yes using the volume buttons and the file will be flashed, easy as that
Sent from my HTC Sensation using XDA

james0912 said:
Hello,
my HTC SENSATION has the HBOOT Version 1.27.1100 and I want to download a RUU to restore my HTC device completely. But I can´t find a RUU with this HBOOT version.
I only have to download the right RUU and install it on my HTC device to restore it completely, right?
Click to expand...
Click to collapse
When you install a rom by a RUU, it will also flash the stock Hboot version. Take a look at the shipped roms thread.
Sent from my HTC Sensation using XDA

james0912 said:
Hello,
my HTC SENSATION has the HBOOT Version 1.27.1100 and I want to download a RUU to restore my HTC device completely. But I can´t find a RUU with this HBOOT version.
I only have to download the right RUU and install it on my HTC device to restore it completely, right?
Click to expand...
Click to collapse
Hboot 1.27 is clearly ICS.
Download official RUU from here (RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed)
This is the latest official ICS RUU for unbranded Europe Sensation.
If your device is branded or your region is not Europe then search for the appropriare RUU.
Run the exe from pc with phone usb plugged. It will restore your phone as "out of the box".
Hope it helped.

Man I really don't understand any of this lol......... I'm just gonna ask a few questions and you guys can either respond or not....
1) I am on stock ICS, rooted, with HTC Dev Unlocked and using Clockwork. If I wanted to un-root, remove clockwork and re-lock the Hboot... How would that go exactly? 1.27.0000 etc...
2) I don't understand why getting S-Off is so difficult. If one would simply downgrade from ICS to GB, wouldn't that change the Hboot version to a lower one, and then you would be able to use the Revolutionary way? Or is that not possible to do? Or does the downgrade not affect the Hboot?
3) Which Custom ROM am I able to flash at the moment? Any, based on ICS?

FnH84 said:
Man I really don't understand any of this lol......... I'm just gonna ask a few questions and you guys can either respond or not....
1) I am on stock ICS, rooted, with HTC Dev Unlocked and using Clockwork. If I wanted to un-root, remove clockwork and re-lock the Hboot... How would that go exactly? 1.27.0000 etc...
2) I don't understand why getting S-Off is so difficult. If one would simply downgrade from ICS to GB, wouldn't that change the Hboot version to a lower one, and then you would be able to use the Revolutionary way? Or is that not possible to do? Or does the downgrade not affect the Hboot?
3) Which Custom ROM am I able to flash at the moment? Any, based on ICS?
Click to expand...
Click to collapse
Hi,
1. I think that you can just run the RUU in the post above yours.(If your phone is European)
2.Downgrading is not possible on hboot 1.27.000
HTC have locked you out of this possibility.
3.As you say.Any 3.32. based ICS ROM.

malybru said:
Hi,
1. I think that you can just run the RUU in the post above yours.(If your phone is European)
2.Downgrading is not possible on hboot 1.27.000
HTC have locked you out of this possibility.
3.As you say.Any 3.32. based ICS ROM.
Click to expand...
Click to collapse
Thank you very much Not planning un-root but was just wondering, in case I have to do that at some point, it's good to know how

FnH84 said:
Man I really don't understand any of this lol......... I'm just gonna ask a few questions and you guys can either respond or not....
1) I am on stock ICS, rooted, with HTC Dev Unlocked and using Clockwork. If I wanted to un-root, remove clockwork and re-lock the Hboot... How would that go exactly? 1.27.0000 etc...
Click to expand...
Click to collapse
It can be done only by running corresponding RUU which can be found based on your firmware(in your case it is 3.32) and cid (to get cid "fastboot getvar cid")...if you are unbranded i.e. cid is HTC__001..then you can run the above mentioned ruu...or else you should get the appropriate one...if you can't find it then post your cid along with radio..we can find the appropriate one for you
2) I don't understand why getting S-Off is so difficult. If one would simply downgrade from ICS to GB, wouldn't that change the Hboot version to a lower one, and then you would be able to use the Revolutionary way? Or is that not possible to do? Or does the downgrade not affect the Hboot?
Click to expand...
Click to collapse
If you are S-ON you can't downgrade...not by running a RUU or by flashing firmware directly...that's why people use revolutionary first to get soff and then they'll flash unlocked firmware to update the hboot and all...
It you are SOFF you can literally do anything ..upgrade, downgrade..its your choice..
3 ) Which Custom ROM am I able to flash at the moment? Any, based on ICS?
Click to expand...
Click to collapse
As you are unlocked via HTC dev..if you update your recovery with 4EXT latest one which has smartflash mode ON(exclusive SON flash)..you could have any ROM
Edit: I'm bit late huh anyways for more detailed answer look ay my post
sent from my blazing fast pyramid through sonic waves

Error [155] - Trying to update HBOOT

Hi, I want to flash a development RUU, but everytime I try, I get Error [155]. This RUU is supposed to have 1.13.0000 bootloader version, but I don't know how to update from 1.06.0000 and if it may cause the error.
Any suggestion about it? Thanks in advance.

You're talking about ONE S, right?

Right, HTC One S

Well first of all is the chosen RUU compatible with your CID ?? If it isnt it will fail so you need to download one that is compatible, Or change your CID to match the one inside the RUU..
Secondly, If you haver done this and still get the error, Try to run the RUU from fastboot.
Oh and also, RUU requires a LOCKED / RELOCKED bootloader and sometimes stock recovery too !

azzledazzle said:
Well first of all is the chosen RUU compatible with your CID ?? If it isnt it will fail so you need to download one that is compatible, Or change your CID to match the one inside the RUU..
Secondly, If you haver done this and still get the error, Try to run the RUU from fastboot.
Oh and also, RUU requires a LOCKED / RELOCKED bootloader and sometimes stock recovery too !
Click to expand...
Click to collapse
Yes, I have the same CID that is inside the RUU.
Could you tell me how to run it from fastboot?
I'm trying almost everything I can (locked, relocked, unlocked, stock recovery...), even I'm trying now to update to the latest OTA_Ville_U_HTC_Europe_1.78.401.2-1.53.401.2 (now I have 1.53.401.2 from Orange Spain) as it has a firmware update (maybe hboot 1.13.0000?) what I think that can be one of the reasons why I can't flash the rom I need.
Thanks in advance!

boot into bootloader and connect USB cable, Select fastboot and then run the RUU on your PC.
Make sure bootloader is locked BEFORE running the ruu

azzledazzle said:
boot into bootloader and connect USB cable, Select fastboot and then run the RUU on your PC.
Make sure bootloader is locked BEFORE running the ruu
Click to expand...
Click to collapse
Yes, it's something I've already tried. Another problem I'm trying to solve is when installing from stock recovery, cause it says sdcart can't be mounted...

What are you trying to install from Stock Recovery ?? you cant flash an RUU and all flashable zip files MUST be signed otherwise it will fail..
I also had the cant mount sd card error in stock recovery, But when i tried CWM i didnt.. Dont know much about how stock recovery works, I just know i dont like it lol

lol, me neither!!!
I'm trying to install a stock rom, so I am supposed to do it from stock recovery, that's the matter. But I can't do it because it can't mount sdcard. I'm getting crazy, but now it is something personal, between the phone and me!!! I'll try to be patient and find the solution.

Stock ROM ?? How have you obtained this ? has someone posted it in a flashable .zip file ? If so, You need to flash it via CWM Recovery THEN flash stock recovery through fastboot.
If the Stock ROM is a Nandroid you will also need to restore this using CWM Recovery. THEN flash stock recovery after.
If the Stock ROM is dissected from an RUU you will need to flash this via bootloader, BUT unless you have a S-OFF phone (which i doubt you do cause there is no S-OFF yet) It wont work.

azzledazzle said:
Stock ROM ?? How have you obtained this ? has someone posted it in a flashable .zip file ? If so, You need to flash it via CWM Recovery THEN flash stock recovery through fastboot.
If the Stock ROM is a Nandroid you will also need to restore this using CWM Recovery. THEN flash stock recovery after.
If the Stock ROM is dissected from an RUU you will need to flash this via bootloader, BUT unless you have a S-OFF phone (which i doubt you do cause there is no S-OFF yet) It wont work.
Click to expand...
Click to collapse
Ok, it is the third option, and evidently, I'm not S-OFF. I had read a thread where they dissected this zip and I thought it was useful. Now I have found the RUU, I will try to install it. I've changed the zip and relocked it but I'm still finding Error [155]

Its useful if you are S-OFF, You just extract the ROM.zip from the RUU, Rename it to the phones model number, So in our case it would be PG40100.img ( i think) and then flash it in bootloader. However ignore this option as it wont work with a S-ON device...
If you still get the Error 155 message and you're positive you've done everything correctly, Maybe download the same / another RUU, Chances are it could have been a bad / corrupted download It happens to us all !

Ok, finally I solved it. I found original RUUs for HTC_Europe 1.53 and 1.78
Firstly, I changed my CID to HTC__001, extracted recovery.img from 1.53 RUU, flashed it, relocked the bootloader and installed the 1.53 RUU... and it worked!!! After that, nothing special to say installing 1.78 (hboot and radio updated!)

rpachecoh said:
Ok, finally I solved it. I found original RUUs for HTC_Europe 1.53 and 1.78
Firstly, I changed my CID to HTC__001, extracted recovery.img from 1.53 RUU, flashed it, relocked the bootloader and installed the 1.53 RUU... and it worked!!! After that, nothing special to say installing 1.78 (hboot and radio updated!)
Click to expand...
Click to collapse
I have done exactly (!!) the same, but you know, I have Hboot in version 2.15. And I can run none of RUUs, because I think they are not compatible with this version of Hboot (And this is that Error 155 for me). Well, so what can I do for installing the Stock RUU to my One S ?

[Q] Downgrade HBOOT?

Hello,
I installed the 2.16 HBOOT, but for CM i need 2.15 HBOOT...
Is there a way to downgrade your HBOOT?
Im superCID + sOFF

yooouuri said:
Hello,
I installed the 2.16 HBOOT, but for CM i need 2.15 HBOOT...
Is there a way to downgrade your HBOOT?
Im superCID + sOFF
Click to expand...
Click to collapse
Yes, should be no problem, just follow instructions here http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274&nocache=1&z=674317537341266

portah said:
Yes, should be no problem, just follow instructions here http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274&nocache=1&z=674317537341266
Click to expand...
Click to collapse
Tnx it worked!
Cant mount in recovery.. Can somebody else help me?
Do i need to ADB sideload the rom?

yooouuri said:
Tnx it worked!
Cant mount in recovery.. Can somebody else help me?
Do i need to ADB sideload the rom?
Click to expand...
Click to collapse
If you are after MaximusHD firmware, you should also reflash TWRP or other recovery for villie, and ...
Actually if it would me who want go back, I would use original RUU (that one that can be easily S-Off, SuperCID and so on) so
1) Do HBOOT down grade
2) oem lock
3) flash original RUU
You do not need remove S-Off or SuperCID so only if original RUU will removed them you will need to do it again.

portah said:
If you are after MaximusHD firmware, you should also reflash TWRP or other recovery for villie, and ...
Actually if it would me who want go back, I would use original RUU (that one that can be easily S-Off, SuperCID and so on) so
1) Do HBOOT down grade
2) oem lock
3) flash original RUU
You do not need remove S-Off or SuperCID so only if original RUU will removed them you will need to do it again.
Click to expand...
Click to collapse
Can i use a random RUU?

yooouuri said:
Can i use a random RUU?
Click to expand...
Click to collapse
Okey, what are you trying to reach?
Fix TWRP mount issue? Not possible till update from MaximusHD.
Or just change firmware from MaximusHD which is based on JB 4.2.2 to something that based on JB 4.1.xx?

portah said:
Okey, what are you trying to reach?
Fix TWRP mount issue? Not possible till update from MaximusHD.
Or just change firmware from MaximusHD which is based on JB 4.2.2 to something that based on JB 4.1.xx?
Click to expand...
Click to collapse
Flashed a stock recovery, and then TWRP but not fixed the problem..
Now i connect the phone to my PC and my PC asks to format the sdcard?
I downgraded to 2.15 and i want to install CM but i im getting a error cant mount sdcard -.-
I got 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 can i just run it? And my SOFF + superCID wont go away?

yooouuri said:
Flashed a stock recovery, and then TWRP but not fixed the problem..
Now i connect the phone to my PC and my PC asks to format the sdcard?
I downgraded to 2.15 and i want to install CM but i im getting a error cant mount sdcard -.-
I got 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 can i just run it? And my SOFF + superCID wont go away?
Click to expand...
Click to collapse
They should not, but if they will gone you have to have a known way how to return them. So I suggest to return to those settings from which you have started. If it was HBOOT 2.15 then flash 2.15 if it was more early release flash that one. If you did your S-Off and SuperCID from this RUU then flash it if not then download exactly that that you already S-Offed.

portah said:
They should not, but if they will gone you have to have a known way how to return them. So I suggest to return to those settings from which you have started. If it was HBOOT 2.15 then flash 2.15 if it was more early release flash that one. If you did your S-Off and SuperCID from this RUU then flash it if not then download exactly that that you already S-Offed.
Click to expand...
Click to collapse
When prompt to format it. I just did, the amout of Gigs where the same as it should be, and TWRP mounts the sdcard
I am installing CM now. So the problem is solved. And im still S-OFF and superCID. Thanks for your help!
EDIT; after CM booted, intermediately got a reboot..
Going to wipe everything and try again
EDIT; everything works!

After trying this, i get installations fails with cm11, don't know why. (error executing updater binary in zip)

[Q] Update to 4.4 ROM from 4.2 with old hboot

Hi guys,
I am on an old JellyBAM ROM (7.7.0), based on CyanogenMod 10.1.0 (Android 4.2.2). I want to try KitKat roms (4.4.2) such as latest CM 11 nightlies etc. So I want to know what all I need to do to get my phone ready to install 4.4 roms.
Some background:
I unlocked my bootloader using HTC Dev Token ID method, installed CWM recovery, and flashed my current and past roms that way - it has been around a year since I made any updates to my phone. So I think some of my firmware is not current enough to support 4.4 roms.
I am S-ON.
My main concern is that I have hboot 1.08. All the guides I see talk about either hboot 2.15 or 2.16.
Recovery: CWM v5.8.3.1
Phone is carrier-free Ville S4 processor. Currently service provider is Koodo - a division of Telus (in Canada).
CID: ROGER001
Radio: 0.16.31501S.02
From the reading that I did, what I understood is:
First I should S-OFF (to make things easier for any future playing around). I was thinking of using the Firewater S-OFF Tool (from http://www.androidpolice.com/2014/0...f-tool-will-unlock-any-htc-device-in-moments/)
I need to update my hboot. This is the step I am most worried about, as I have never flashed a RUU before, and that's what most guides say to do. This thread says to just run the JellyBean RUU [http://forum.xda-developers.com/showthread.php?t=2524306]. Would you say that's a pretty safe bet, or is that outdated advice/information?
Once I go S-OFF and update hboot to 2.15, can I just flash CWM (or TWRP) recovery, and flash CM 11 nightlies?
Thanks a lot!

arjundas86 said:
Hi guys,
I am on an old JellyBAM ROM (7.7.0), based on CyanogenMod 10.1.0 (Android 4.2.2). I want to try KitKat roms (4.4.2) such as latest CM 11 nightlies etc. So I want to know what all I need to do to get my phone ready to install 4.4 roms.
Some background:
I unlocked my bootloader using HTC Dev Token ID method, installed CWM recovery, and flashed my current and past roms that way - it has been around a year since I made any updates to my phone. So I think some of my firmware is not current enough to support 4.4 roms.
I am S-ON.
My main concern is that I have hboot 1.08. All the guides I see talk about either hboot 2.15 or 2.16.
Recovery: CWM v5.8.3.1
Phone is carrier-free Ville S4 processor.
Radio: 0.16.31501S.02
From the reading that I did, what I understood is:
First I should S-OFF (to make things easier for any future playing around). I was thinking of using the Firewater S-OFF Tool (from http://www.androidpolice.com/2014/0...f-tool-will-unlock-any-htc-device-in-moments/)
I need to update my hboot. This is the step I am most worried about, as I have never flashed a RUU before, and that's what most guides say to do. This thread says to just run the JellyBean RUU [http://forum.xda-developers.com/showthread.php?t=2524306]. Would you say that's a pretty safe bet, or is that outdated advice/information?
Once I go S-OFF and update hboot to 2.15, can I just flash CWM (or TWRP) recovery, and flash CM 11 nightlies?
Thanks a lot!
Click to expand...
Click to collapse
Whats your CID?
You don't need to be S-OFF if theres a matching RUU for you BUT you cant install lower HBoot versions while you're S-ON. Flashing a custom recovery is also possible while you're S-ON

LS.xD said:
Whats your CID?
You don't need to be S-OFF if theres a matching RUU for you BUT you cant install lower HBoot versions while you're S-ON. Flashing a custom recovery is also possible while you're S-ON
Click to expand...
Click to collapse
I am not sure - I have never checked it before.
I ran CID Getter app, and it's supposed to show me CID in red at the top, but it shows nothing. Some of the app comments say that if the CID is not shown, it means I am SuperCID. I'm not sure about that.
I'm at work, but when I get home, I'll run the fastboot command to find out the CID. I didn't do anything intentionally to get SuperCID, so is it likely that I might be SuperCID? How would I know?

arjundas86 said:
I am not sure - I have never checked it before.
I ran CID Getter app, and it's supposed to show me CID in red at the top, but it shows nothing. Some of the app comments say that if the CID is not shown, it means I am SuperCID. I'm not sure about that.
I'm at work, but when I get home, I'll run the fastboot command to find out the CID. I didn't do anything intentionally to get SuperCID, so is it likely that I might be SuperCID? How would I know?
Click to expand...
Click to collapse
SuperCID = 11111111
Other CIDs are listed here: HTC CID LIST
You can easiliy read the CID with WinDroid Toolkit 2.0

LS.xD said:
SuperCID = 11111111
Other CIDs are listed here: HTC CID LIST
You can easiliy read the CID with WinDroid Toolkit 2.0
Click to expand...
Click to collapse
Thanks for the toolkit.
cid: ROGER001
Btw, what's the purpose of going SuperCID?
Also, I don't want to install lower hboot. I am on hboot 1.08 and I think I need to install hboot 2.15. Right?
I guess S-OFF isn't absolutely necessary, but would be nice to have. Would you recommend using the S-OFF command from the toolkit you linked?

I Don't know which s-off Method is Best for your cid. Have you found matching RUU with hboot 2.15?
With superCID you can switch to other CIDs e.g. for unbranding your device Also it's needed for "Facepalm S-OFF" (Was the only working method for me)
Sent from my loved HTC One S using (most time buggy) Tapatalk

LS.xD said:
I Don't know which s-off Method is Best for your cid. Have you found matching RUU with hboot 2.15?
Sent from my loved HTC One S using (most time buggy) Tapatalk
Click to expand...
Click to collapse
I have seen a few options for RUU, but not sure which one I should use. I don't quite understand the relationships between phone parameters and which RUU to get.
The guide that I linked to in my first post, that I was thinking of using says the following one: (but they don't know what my CID is)
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.5 0.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe​
Androidruu.com has several other RUUs. I guess since my CID says Rogers, I should use one of the Rogers ones?
RUU_Ville_U_Rogers_WWE_1.70.631.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254139_signed.exe - 2013-01-29
or
RUU_Ville_U_Rogers_WWE_1.84.631.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265373_signed.exe - 2013-04-29​
But my current provider is Koodo, which is a subdivision of Telus. So should I use one of the Telus RUUs?
RUU_Ville_U_TELUS_WWE_1.70.661.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254554_signed.exe - 2013-01-29
or
RUU_Ville_U_TELUS_WWE_1.84.661.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265367_signed.exe - 2013-04-29​
I would appreciate any insights into what would be the applicable RUU?
Thanks.

arjundas86 said:
I have seen a few options for RUU, but not sure which one I should use. I don't quite understand the relationships between phone parameters and which RUU to get.
The guide that I linked to in my first post, that I was thinking of using says the following one: (but they don't know what my CID is)
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.5 0.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe​
Androidruu.com has several other RUUs. I guess since my CID says Rogers, I should use one of the Rogers ones?
RUU_Ville_U_Rogers_WWE_1.70.631.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254139_signed.exe - 2013-01-29
or
RUU_Ville_U_Rogers_WWE_1.84.631.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265373_signed.exe - 2013-04-29​
But my current provider is Koodo, which is a subdivision of Telus. So should I use one of the Telus RUUs?
RUU_Ville_U_TELUS_WWE_1.70.661.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254554_signed.exe - 2013-01-29
or
RUU_Ville_U_TELUS_WWE_1.84.661.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265367_signed.exe - 2013-04-29​
I would appreciate any insights into what would be the applicable RUU?
Thanks.
Click to expand...
Click to collapse
As long as you are S-ON you can only flash matching RUUs (Rogers). You will need to gain S-OFF to reach HBoot 2.15 as it seems.

LS.xD said:
As long as you are S-ON you can only flash matching RUUs (Rogers). You will need to gain S-OFF to reach HBoot 2.15 as it seems.
Click to expand...
Click to collapse
Okay. It seems that the best path forward for me is to S-OFF using the Firewater tool (since my device is HTCDEV unlocked/rooted, and having S-OFF means I won't need to unlock bootloader again after running RUU).
Then I'll run the newest Rogers RUU from AndroidRUU.
At this point, I should be on hboot 2.15 and still bootloader unlocked, right?
If I'm right about all that, then I should just have to install a custom recovery and be able to flash the 4.4 ROM I want. Correct?

arjundas86 said:
Okay. It seems that the best path forward for me is to S-OFF using the Firewater tool (since my device is HTCDEV unlocked/rooted, and having S-OFF means I won't need to unlock bootloader again after running RUU).
Then I'll run the newest Rogers RUU from AndroidRUU.
At this point, I should be on hboot 2.15 and still bootloader unlocked, right?
If I'm right about all that, then I should just have to install a custom recovery and be able to flash the 4.4 ROM I want. Correct?
Click to expand...
Click to collapse
Newest Rogers RUU ist HBoot 1.84 as it seems. Once you're S-OFF and have superCID you need to change your CID to unbranded (HTC__001) and flash e.g. unbranded RUU with HBoot 2.15.

LS.xD said:
Newest Rogers RUU ist HBoot 1.84 as it seems. Once you're S-OFF and have superCID you need to change your CID to unbranded (HTC__001) and flash e.g. unbranded RUU with HBoot 2.15.
Click to expand...
Click to collapse
Hmm... I see. Things are getting clearer, but still a little confused about SuperCID stuff.
Will running Tmobile US RUU work? That's the one from the guide I read in my first post. He suggests that RUU to get hboot 2.15.
Once I get S-OFF, then I should get SuperCID. I thought with SuperCID (i.e. 11111111), I can run any RUU. Or should I still manually set CID to HTC__001 before running Tmobile US RUU?

arjundas86 said:
Hmm... I see. Things are getting clearer, but still a little confused about SuperCID stuff.
Will running Tmobile US RUU work? That's the one from the guide I read in my first post. He suggests that RUU to get hboot 2.15.
Once I get S-OFF, then I should get SuperCID. I thought with SuperCID (i.e. 11111111), I can run any RUU. Or should I still manually set CID to HTC__001 before running Tmobile US RUU?
Click to expand...
Click to collapse
To run a RUU NOT MATCHING your stock CID you need S-OFF // SuperCID. You cant install TMobile RUU at first :/
I would act like this:
Run latest Rogers RUU --> READ FACEPALM GUIDE CAREFULLY. There is how to gain SuperCID and then S-OFF. Once done you can change CID to whatever you want and run a (unbranded) RUU with HBoot 2.15.
But that is just what i thought about it. I suggest to let someone else CONFIRM the way suggested by me first.

Have you tried anything yet? If NO. then STOP. Don't do anything and don't upgrade your firmware/hboot yet. It could happen you won't need this. I am on hboot 1.06 and I'm running fine any ROM including KitKat ones. That requirement for a higher firmware is coming from an old issue that was before with earlier Android versions (from the versions that used 3.4.x kernel and up), making SOME phones to misbehave (reboots or other issues). It could be that your phone handles it right and in that case you won't need to upgrade if you don't want to.
WHY? You should not only upgrade your firmware but also to S-Off. It is not required but it makes your life easier. And these procedures bear some risks even if they were successful for others. And why should you risk anything unless it's mandatory? The point is you have a hboot lower than 1.09. There are not to many left and people are tempted to forget, but hboot lower than 1.09 means you're like an S-Off. You can flash radios and kernels from recovery as on any other S-Off device. Only thing you can't do is to remove those red letters from the boot splash screen...that is you can't flash another firmware. But hopefully you might not need it.
OK. All these being said, I would suggest you to first try to see if the ROM works OK on your phone like it is and only if it doesn't you should think about S-Off, upgrading firmware and things like this.
Now, what you have to do is download the ROM you would like...any ROM, and before flashing it follow my guide HERE to change the updater script in the ROM's ZIP to allow flashing the ROM on lower hboots. It is very easy, I do this usually in 1 min, I would suggest to use method 2 that's much easier than to follow all detailed steps in method 1. If you have any questions or unclear things ask but I think it's easy enough.
If after this you cannot boot the ROM or have it working, then you can think of upgrading firmware

@Rapier
thank you for the provided help as usual
Are there any advantages by unsing HBoot 1.06?? I'm on 2.15 // S-OFF // SuperCID // No red letters // "tampered" removed

LS.xD said:
...Are there any advantages by unsing HBoot 1.06?? I'm on 2.15 // S-OFF // SuperCID // No red letters // "tampered" removed
Click to expand...
Click to collapse
For you? NO. You're better than me
The story is like this. I bought the phone in 2012. At that time, the highest hboot was 1.14 I believe (don't remember exactly) and there was no S-Off method available (they appeared later). There was something else tho. The lower hboots (1.09 and lower) permitted to write in the kernel partition or radio partition like an S-Off device. HTC then covered this in the higher hboots. So even if there was no S-Off method, there was a downgrade method that was used to downgrade the hboot from whatever you had to 1.09 or below. I downgraded mine to 1.06...don't ask why I didn't choose 1.09, I thought that was the RUU I considered to be fine for me at that time.
Now being on hboot 1.06 I can do anything except I cannot flash firmwares directly. So I cannot flash a new hboot with red letters removed for example. But I don't care about this...I can flash radios or kernels or splash screens like any S-Off user. The procedure for getting latest firmware and S-Off seems a little bit risky and I've read about alot of issues or problems from people who failed or tried countless times to reach that. So I've asked myself why should I do that if I don't need it?
Then it came the rumor and there were some brick cases of devices that were having some Android 4.3 ROMs and were not on latest firmware (in the meantime 2.13 and 2.15 hboots arise and also the S-Off method). It proved to be not the firmware fault after all. But CM team has included a check in the updater script of the ROM ZIP, to validate if the hboot was 2.13 or 2.15...if not, the flash won't happen. It's a simple assert command present there at the beginning of the script that do the check. As CM team was the pioneer in having the newest Android version ROMs available, everybody based initially their ROMs/builds on CM...so the check in the script was automatically carried over to all the ROMs out there. And it's still here.
As I've tested and I could run fine those ROM's (by removing the check before flash), I noticed that this requirement does not apply to everyone. Some could run fine the ROMs even if they're not on the "latest" firmware.
So that's why I am on 1.06...cause I don't know why should I go through some risky procedures when I don't need to.

Rapier said:
Have you tried anything yet? If NO. then STOP. Don't do anything and don't upgrade your firmware/hboot yet. It could happen you won't need this. I am on hboot 1.06 and I'm running fine any ROM including KitKat ones. That requirement for a higher firmware is coming from an old issue that was before with earlier Android versions (from the versions that used 3.4.x kernel and up), making SOME phones to misbehave (reboots or other issues). It could be that your phone handles it right and in that case you won't need to upgrade if you don't want to.
OK. All these being said, I would suggest you to first try to see if the ROM works OK on your phone like it is and only if it doesn't you should think about S-Off, upgrading firmware and things like this.
Now, what you have to do is download the ROM you would like...any ROM, and before flashing it follow my guide HERE to change the updater script in the ROM's ZIP to allow flashing the ROM on lower hboots. It is very easy, I do this usually in 1 min, I would suggest to use method 2 that's much easier than to follow all detailed steps in method 1. If you have any questions or unclear things ask but I think it's easy enough.
If after this you cannot boot the ROM or have it working, then you can think of upgrading firmware
Click to expand...
Click to collapse
I did read in more than one thread that you MUST have hboot 2.15 to install KitKat roms. Also, on CyanogenMod website, it says:
Firmware compatibility:
CM 10.1-11.0: HBOOT 2.13.0000, 2.15.0000, 2.15.4444.​But no, I haven't done anything yet. So first of all, I'll make a nandroid backup and then just try factory reset, wipe cache/dalvik, and flash a CM 11 ROM, and see if it works. I'll post here whether it worked or not, I won't have time to do this until the weekend though.
Thanks, btw.
Rapier said:
WHY? You should not only upgrade your firmware but also to S-Off. It is not required but it makes your life easier. And these procedures bear some risks even if they were successful for others. And why should you risk anything unless it's mandatory? The point is you have a hboot lower than 1.09. There are not to many left and people are tempted to forget, but hboot lower than 1.09 means you're like an S-Off. You can flash radios and kernels from recovery as on any other S-Off device. Only thing you can't do is to remove those red letters from the boot splash screen...that is you can't flash another firmware. But hopefully you might not need it.
Click to expand...
Click to collapse
I don't get what you're saying. It is still worth getting S-OFF, or it is not?

arjundas86 said:
I did read in more than one thread that you MUST have hboot 2.15 to install KitKat roms. Also, on CyanogenMod website, it says:
Firmware compatibility:
CM 10.1-11.0: HBOOT 2.13.0000, 2.15.0000, 2.15.4444.​But no, I haven't done anything yet. So first of all, I'll make a nandroid backup and then just try factory reset, wipe cache/dalvik, and flash a CM 11 ROM, and see if it works. I'll post here whether it worked or not, I won't have time to do this until the weekend though.
Thanks, btw.
I don't get what you're saying. It is still worth getting S-OFF, or it is not?
Click to expand...
Click to collapse
I beg to differ answering first:
Just try if you can install your preferred rom, AFTER you edited the "updatescript" as suggested by @Rapier.
IN CASE you have problems with the new rom you should get S-OFF + upgrading HBoot to 2.15+

LS.xD said:
I beg to differ answering first:
Just try if you can install your preferred rom, AFTER you edited the "updatescript" as suggested by @Rapier.
Just IN CASE you have problems with the new rom you should get S-OFF + upgrading HBoot to 2.15+
Click to expand...
Click to collapse
Yes, you're right. That's what I meant. I will delete the updater-script lines that Rapier mentioned before trying to install CM11.
If it doesn't work, at least I can restore to my backup, without risk of bricking.
Then I can try the hboot update and s-off if required.
Thanks.

arjundas86 said:
I did read in more than one thread that you MUST have hboot 2.15 to install KitKat roms. Also, on CyanogenMod website, it says:
Firmware compatibility:
CM 10.1-11.0: HBOOT 2.13.0000, 2.15.0000, 2.15.4444.​...
Click to expand...
Click to collapse
Yes, they say so. Then I'm the living proof that this requirement is not true...sorry for that. I've explained above to LS.xD where this requirement came from. The point is that you might have the ROM working even if you're on 1.08 and in this case you won't need to upgrade if you don't want
arjundas86 said:
...I don't get what you're saying. It is still worth getting S-OFF, or it is not?
Click to expand...
Click to collapse
It's depending on what you want. If you want to get rid of that red warning, to have the latest hboot and to have less trouble when flashing ROMs then yes, it worth it. If you just want to upgrade your firmware to 2.15 (to match the ROM requirements) but do not want to make the S-Off, you will have to flash the kernel separately in fastboot mode, after each ROM flash. Also you won't be able to flash a radio. That's why I said that if you are going to upgrade the firmware you should get S-Off as well
BUT, if you're NOT going to upgrade your firmware and you'll be lucky to have the ROM working, you won't need to S-Off since your current hboot is lower than 1.09 and allows you to flash radios and kernels directly from recovery.
And at this point, as you said, it worth a try like you are now and only if it's not working like this you should upgrade and do S-Off. I guess is much easier and less risky to remove 4 lines from that script and flash the ROM to see if it's working, than to go through the firmware upgrade & S-Off procedures

Rapier said:
Yes, they say so. Then I'm the living proof that this requirement is not true...sorry for that. I've explained above to LS.xD where this requirement came from. The point is that you might have the ROM working even if you're on 1.08 and in this case you won't need to upgrade if you don't wantIt's depending on what you want. If you want to get rid of that red warning, to have the latest hboot and to have less trouble when flashing ROMs then yes, it worth it. If you just want to upgrade your firmware to 2.15 (to match the ROM requirements) but do not want to make the S-Off, you will have to flash the kernel separately in fastboot mode, after each ROM flash. Also you won't be able to flash a radio. That's why I said that if you are going to upgrade the firmware you should get S-Off as well
Click to expand...
Click to collapse
Hey Rapier,
I'm having trouble doing getting the zip signed.
I tried the zip signer you had in your guide, as well as a bunch of other zip signing programs, but none of them seem to do the job. I keep getting Error: Status 7.
Not getting bootloops or anything like that, so I was able to restore to my backup. No harm done.