Database Info

Downgrade Help!!?

Is there any easiest way to downgrade my Tmobile HTC One s to Hboot 1.06 without going through bricking and unbricking procedure i want to have JB with Wifi working .. Please Help

more
i am on hboot1.14 right now ulocked recovery installed TWRP 2.XXX with trickdroid 9.0

shshsh007 said:
Is there any easiest way to downgrade my Tmobile HTC One s to Hboot 1.06 without going through bricking and unbricking procedure i want to have JB with Wifi working .. Please Help
Click to expand...
Click to collapse
Unfortunately, there's none, so quit whining, either just do it or wait for T-Mobile Jellybean upgrade.
The person that made the method is a genius, so just go his way. I'm still very junior.

Thanks for the Help
Any Senior members clarification or any link where i can get the needed information on this matter would be appreciated!!

shshsh007 said:
Is there any easiest way to downgrade my Tmobile HTC One s to Hboot 1.06 without going through bricking and unbricking procedure i want to have JB with Wifi working .. Please Help
Click to expand...
Click to collapse
I would suggest you S-Off your device. After that you can flash any hboot you want. Altho you probably won't need to anymore, since on S-Off you can flash radio firmware regardless of hboot version.
-Jobo

thank you JoBo
touch of jobo said:
I would suggest you S-Off your device. After that you can flash any hboot you want. Altho you probably won't need to anymore, since on S-Off you can flash radio firmware regardless of hboot version.
-Jobo
Click to expand...
Click to collapse
if you could direct me the link on how to downgrade to any Hboot after Soff, i will be greatfull
whether flashing EU Radio will make my Wifi work on Trickdroid 9.0 on my HTC Tmobile?

shshsh007 said:
if you could direct me the link on how to downgrade to any Hboot after Soff, i will be greatfull
whether flashing EU Radio will make my Wifi work on Trickdroid 9.0 on my HTC Tmobile?
Click to expand...
Click to collapse
I posted up a bunch of flashable hboots here: http://forum.xda-developers.com/showthread.php?p=39216236#post39216236
But once you're S-Off, you may not need to downgrade hboot anymore, because the restrictions from higher hboots are gone. If it's just for flashing different wifi and radio firmware, you don't need to change your hboot when you're S-Off.
You can find a radio (+ other related firmware) flasher here: http://forum.xda-developers.com/showthread.php?t=1998270
The only scary thing about getting S-Off is the part where you have to get superCID. But this is still less scary than going through the downgrade process. (Both involve poking in p4, but superCID doesn't involve bricking and recovering.)
I don't know which radio/wifi will work for your device and ROM. You have to experiment or search for posts by someone with a similar situation.
-Jobo

shshsh007 said:
if you could direct me the link on how to downgrade to any Hboot after Soff, i will be greatfull
whether flashing EU Radio will make my Wifi work on Trickdroid 9.0 on my HTC Tmobile?
Click to expand...
Click to collapse
Please read what he said. There is no need to downgrade with S-Off.

thank you so much for thr Help!!
touch of jobo said:
I posted up a bunch of flashable hboots here: http://forum.xda-developers.com/showthread.php?p=39216236#post39216236
But once you're S-Off, you may not need to downgrade hboot anymore, because the restrictions from higher hboots are gone. If it's just for flashing different wifi and radio firmware, you don't need to change your hboot when you're S-Off.
You can find a radio (+ other related firmware) flasher here: http://forum.xda-developers.com/showthread.php?t=1998270
The only scary thing about getting S-Off is the part where you have to get superCID. But this is still less scary than going through the downgrade process. (Both involve poking in p4, but superCID doesn't involve bricking and recovering.)
I don't know which radio/wifi will work for your device and ROM. You have to experiment or search for posts by someone with a similar situation.
-Jobo
Click to expand...
Click to collapse
thank you so much for thr Help!!
i'll try and get back to you if troubled..

ok
Darknites said:
Please read what he said. There is no need to downgrade with S-Off.
Click to expand...
Click to collapse
Sure! :highfive:

[Q] Need help with RUU 3.18

Hello,
I am new to oneXL forum and by the looks of all the thread it seems that having S-off and upgrading to latest Ruu 3.14 is needed for most of the custom ROM to flash, i have an unlocked boot-loader and rooted. I am currently with below configuration on my XL,
Evita pvt ship s-on rl
Hboot-1.09.0000
Radio-0.17a.32.09.24_2
openDSP-v25.1.0.32.0405
emmc-boot
I just wanted to know what are my limitations and what better it will do with S-Off and upgrade to RUU.
Thank you

may2118 said:
Hello,
I am new to oneXL forum and by the looks of all the thread it seems that having S-off and upgrading to latest Ruu 3.14 is needed for most of the custom ROM to flash, i have an unlocked boot-loader and rooted. I am currently with below configuration on my XL,
Evita pvt ship s-on rl
Hboot-1.09.0000
Radio-0.17a.32.09.24_2
openDSP-v25.1.0.32.0405
emmc-boot
I just wanted to know what are my limitations and what better it will do with S-Off and upgrade to RUU.
Thank you
Click to expand...
Click to collapse
I also need assistance. I don't have a windows pc, so I find it a bit difficult to run a .exe file lol. Is there any way to flash the ruu in recovery, or do the update with a linux pc? Basically, any way to bypass the while so does requirement...

darthvince said:
I also need assistance. I don't have a windows pc, so I find it a bit difficult to run a .exe file lol. Is there any way to flash the ruu in recovery, or do the update with a linux pc? Basically, any way to bypass the while so does requirement...
Click to expand...
Click to collapse
Search for how to run a vm through Linux via Virtual Box, there are several how-to that have been written on these very forums....

Crappyvate said:
Search for how to run a vm through Linux via Virtual Box, there are several how-to that have been written on these very forums....
Click to expand...
Click to collapse
Hi,
Can you tell me if i need to upgrade Hboot for supercid?, and can i s-off without supercid?

How about you do some searching, and some reading. The answers to your questions lie within these forums. Who knows, you might actually learn something. Basic XDA rules: search before posting.
Sent from my Evita

may2118 said:
Hi,
Can you tell me if i need to upgrade Hboot for supercid?, and can i s-off without supercid?
Click to expand...
Click to collapse
hboot has very little to do with most things. It does not need updating and downgrading for pretty much anything. Newer hboot does protect some partitions like radio and boot, but that really does not get in the way and is entirely overcome once you s-off.
People need to forget about hboot and what version it is, it is unlikely to ever really get in your way these days.
For you second question, why not refer to the s-off thread where the first post tells you what to do?
http://forum.xda-developers.com/showthread.php?p=38174259
---------- Post added at 03:39 AM ---------- Previous post was at 03:32 AM ----------
darthvince said:
Is there any way to flash the ruu in recovery, or do the update with a linux pc?
Click to expand...
Click to collapse
There is a few ways for the phone to accept OTA updates, eg with a vanilla stock ROM or via recovery mode.
You can also just install the full firmware.zip taken from 3.17/3.18 from rebootruu.
They are all far more risky then just supercid, soff and installing a RUU.
Surely you can get access to a Windows machine.

twistedddx said:
hboot has very little to do with most things. It does not need updating and downgrading for pretty much anything. Newer hboot does protect some partitions like radio and boot, but that really does not get in the way and is entirely overcome once you s-off.
People need to forget about hboot and what version it is, it is unlikely to ever really get in your way these days.
For you second question, why not refer to the s-off thread where the first post tells you what to do?
http://forum.xda-developers.com/showthread.php?p=38174259
---------- Post added at 03:39 AM ---------- Previous post was at 03:32 AM ----------
There is a few ways for the phone to accept OTA updates, eg with a vanilla stock ROM or via recovery mode.
You can also just install the full firmware.zip taken from 3.17/3.18 from rebootruu.
They are all far more risky then just supercid, soff and installing a RUU.
Surely you can get access to a Windows machine.
Click to expand...
Click to collapse
Thank you very much...i will start with Supercid and S-off....thanks again

timmaaa said:
How about you do some searching, and some reading. The answers to your questions lie within these forums. Who knows, you might actually learn something. Basic XDA rules: search before posting.
Sent from my Evita
Click to expand...
Click to collapse
I know, what you said is right and i have been reading...but it seems more i read..the more i get confused. I wanted to try one of the methods to do Supercid and S-off but before i proceed i wanted to reassure my self before. Thanks anyways!!!

[SOLVED] Upgrading Firmware + hboot with S-OFF

Right now I'm using the latest ViperROM 2.2.0 with S-OFF, Hboot 1.06 (flashed via S-OFF) and SuperCID 111111. The phone is an unbranded, european, unlocked, non-tmobile phone. Now I was looking into using the newest CM10.1, but for this I'd need to upgrade my radio (and Hboot?).
I haven't had the time to follow all the events. When trying to read what way I should follow, I stumbleupon bricked devices and people who don't have problems. So I actually don't know what to believe and what to do.
Could anyone point me out what I should do with my device do minimize the risk of bricking it while upgrading? Would have followed the instructions in this post http://forum.xda-developers.com/showthread.php?t=2322755, but the 2nd post makes me anxious.
Edit 2013-07-10: I've solved my issues and am now on Hboot 2.15 with S-OFF (didn't lose it with the upgrade) and CM10.1! See the last post for details.

m1schi said:
Right now I'm using the latest ViperROM 2.2.0 with S-OFF, Hboot 1.06 (flashed via S-OFF) and SuperCID 111111. The phone is an unbranded, european, unlocked, non-tmobile phone. Now I was looking into using the newest CM10.1, but for this I'd need to upgrade my radio (and Hboot?).
I haven't had the time to follow all the events. When trying to read what way I should follow, I stumbleupon bricked devices and people who don't have problems. So I actually don't know what to believe and what to do.
Could anyone point me out what I should do with my device do minimize the risk of bricking it while upgrading? Would have followed the instructions in this post http://forum.xda-developers.com/showthread.php?t=2322755, but the 2nd post makes me anxious.
Click to expand...
Click to collapse
Since you are already S-OFF there is no need to upgrade your H-Boot. That does not effect the rom at all. With the Radio, when you flash the Rom it will automatically change the radio to the one preset by CM10.1 for the Rom. If you live in an area not covered by the radio, with S-OFF, you can flash any radio that you would like that is covered where you live and gives you the best service for your Provider.

m1schi said:
Right now I'm using the latest ViperROM 2.2.0 with S-OFF, Hboot 1.06 (flashed via S-OFF) and SuperCID 111111. The phone is an unbranded, european, unlocked, non-tmobile phone. Now I was looking into using the newest CM10.1, but for this I'd need to upgrade my radio (and Hboot?).
I haven't had the time to follow all the events. When trying to read what way I should follow, I stumbleupon bricked devices and people who don't have problems. So I actually don't know what to believe and what to do.
Could anyone point me out what I should do with my device do minimize the risk of bricking it while upgrading? Would have followed the instructions in this post http://forum.xda-developers.com/showthread.php?t=2322755, but the 2nd post makes me anxious.
Click to expand...
Click to collapse
Change your cid back to your og HTC one.
Supercid has lost most it value since your soff. You can change it whenever you want.
Ehh the low hboot you have has almost no added use since your s-off.
Forget about needing a new radio, who told you that? You can flash whatever radio you want.
You need a update hboot and firmware.
New kernels require that. Not radio.
Easiest way. Run latest ruu with your original unbranded HTC cid. No need to relock or s-on. Afterward custom recovery and start flashing.
Verstuurd van mijn One S met Tapatalk

Thanks for the answers!
Still I'm puzzled a bit: I need HBOOT 2.15 for the newer ROMS using the newest Kernel? Meaning I can just update the HBOOT version via the command line, because of my S-OFF and flash the ROM I want? No need to use all the procedures you find around here? I'll preserve my S-OFF?

m1schi said:
Thanks for the answers!
Still I'm puzzled a bit: I need HBOOT 2.15 for the newer ROMS using the newest Kernel? Meaning I can just update the HBOOT version via the command line, because of my S-OFF and flash the ROM I want? No need to use all the procedures you find around here? I'll preserve my S-OFF?
Click to expand...
Click to collapse
if flashing a ruu s-off will be preserved.
so
change to your original cid with fastboot command.
flash a ruu wich is/came originaly with your cid/device (lower version is no problem, if you cant find the jb one of your device),
then do otas till your on JB.
the flash stock recovery, then custom rom. finished.

m1schi said:
Right now I'm using the latest ViperROM 2.2.0 with S-OFF, Hboot 1.06 (flashed via S-OFF) and SuperCID 111111. The phone is an unbranded, european, unlocked, non-tmobile phone. Now I was looking into using the newest CM10.1, but for this I'd need to upgrade my radio (and Hboot?).
I haven't had the time to follow all the events. When trying to read what way I should follow, I stumbleupon bricked devices and people who don't have problems. So I actually don't know what to believe and what to do.
Could anyone point me out what I should do with my device do minimize the risk of bricking it while upgrading? Would have followed the instructions in this post http://forum.xda-developers.com/showthread.php?t=2322755, but the 2nd post makes me anxious.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=43400980&postcount=22

vatsaman said:
http://forum.xda-developers.com/showpost.php?p=43400980&postcount=22
Click to expand...
Click to collapse
That's what I'm wondering about: Everyone seems to tell me some other way to upgrade my phone.
You tried to upgrade your phone via RUU?
There seems to be a method without the RUU, just fastboot: http://forum.xda-developers.com/showthread.php?p=42985992#post42985992
This should get me onto the newest HBOOT and let me use AOSP ROMS with 3.4 Kernel, without loosing S-OFF or bricking my device?
Edit 2013-07-10: I've used this method to go from my hboot 1.06 to hboot 2.15, while still having S-OFF.
http://forum.xda-developers.com/showthread.php?p=42985992#post42985992

[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.

Bootloader s-off problem please help

I was s-off already before and somehow it shows s-on now. I've tried rumrumner, revone, and firewater. They all success but it doesn't show s-off on the bootloader. On firewater it shows there really isn't a helluva lot to do here. bye bye. Which I use google and found that it means I have s-off already. Could it be a bootloader problem? I tried fastboot getvar all and it shows s-on.

It's cos you followed the install guide of insertcoin and flashed the hboot that was suggested.. That boot is a modded one by cmviennau am guessing which hides s-on and removes tampered flag etc

Braddison said:
It's cos you followed the install guide of insertcoin and flashed the hboot that was suggested.. That boot is a modded one by cmviennau am guessing which hides s-on and removes tampered flag etc
Click to expand...
Click to collapse
Sorry for late reply. I tried to flash a fuu to upgrade firmware and it failed. So I took the att ruu and then I took the ota to upgrade to kit kat firmware (hboot 2.22). Are there anything I could do?

It also shows tempered so I don't think it's a hboot that I flashed. Could it be bootloader issue?

Hmm? Well if it's shown as s-on but you are In fact s-off surely that's a bonus?
Try an app that requires s-off to check if you are, or maybe try supercid as you need s-off for that. That's all can suggest.

Braddison said:
Hmm? Well if it's shown as s-on but you are In fact s-off surely that's a bonus?
Try an app that requires s-off to check if you are, or maybe try supercid as you need s-off for that. That's all can suggest.
Click to expand...
Click to collapse
Yup, I have s-off and are there any hboot that will show s-off that I could flash? I know that I got s-off because I was able to change cid.
Edit: It also doesn't show the deveoper purpose thing. I didn't flash any hboot. This is like amazing. I don't know what to say. I didn't flash any different hboot after taking the at&t 4.4.2 ota.