Hi,
I've been using custom roms for a couple months now but am still a bit bewildered by the link between HBoot and the Radio.
My current setup is HBoot 1.17.1111, radio 10.14.9035.01_M and virtuous ICS rom. Pretty sure that when it was stock I started with HBoot 1.18.
My question is, do roms include an HBoot flash, i can see a 'boot.img' file in the root directory of the rom zips?
What HBoot/radio combination is recommended?
Ta.
corumuk said:
Hi,
I've been using custom roms for a couple months now but am still a bit bewildered by the link between HBoot and the Radio.
My current setup is HBoot 1.17.1111, radio 10.14.9035.01_M and virtuous ICS rom. Pretty sure that when it was stock I started with HBoot 1.18.
My question is, do roms include an HBoot flash, i can see a 'boot.img' file in the root directory of the rom zips?
What HBoot/radio combination is recommended?
Ta.
Click to expand...
Click to collapse
ROM's do not inclide HBOOT or Radio. only RUU's do.
the best way to get latest hboot and radio is to flash the leaked ICS RUU from capychimp and robocik
Hi mrangry.
From what i understand if i flash the ICS RUU i will retain S-Off but the bootloader will be locked which cannot currently be undone by revolutionary.
When i first attempted unlocking it was following the official HTCDev guide (to the letter) which didn't work (even though it said it was successful), whereas revolutionary worked fine, so i'm a bit apprehensive about flashing the RUU.
ok i've tried applying the ruu, after ensuring supercid is set, but am getting a connection error.
the ruu states 'waiting for bootloader' for a couple of minutes then throws up 'Error 171, usb connection error' even though during the early part of the setup it detected the phone and rom version number. HTC Sync also doesn't seem to detect the phone when connected by USB.
any further tips would be appreciated.
edit: the ruu was run with the phone on as normal, the ruu then tries to reboot into the bootloader. i'm assuming i could try to run the ruu with the bootloader already loaded, but given the problems already wasn't sure whether this would be a good idea.
gave up on the ruu and installed the firmware zip posted in a separate thread. flashed ok, am now restoring a 4ext nandroid.
nothing is ever straightforward is seems!
just thought i'd update and say much improved battery life with the new firmware, just over 48 hours (fairly light use of apps).
I was thinking...how about we all devise a list of compatible ROMs for each hboot version?? That way it would lessen the confusion on compatible hboots.. Maybe even a recovery list as well. Any thoughts?
Sent from my One X using Tapatalk
It isn't even the hboot that matters, it's the firmware that the hboot is a part of that matters. You can flash just the hboot all you like and it won't achieve anything without the rest of the firmware.
It'd be a short list anyway; any current aosp ROM requires at least the 3.18 firmware which includes the 2.14 hboot. Any Sense 5 ROM requires at least the 5.08 firmware that includes the 2.15 hboot. Any Sense 4 ROM it doesn't matter.
I'm pretty sure this information is mentioned in my Evita FAQ thread already but I'll double check and revise it if necessary.
Sent from my Evita
OK. Cuz I keep trying to flash ROMs and getting prop boot errors. Lol
Sent from my One X using Tapatalk
The ONLY difference I have ever noticed was the 1.09 hboot and all the others. 1.09 is the only hboot that would allow me to shell restart/hot reboot in stock 4.1.1. If I had any other hboot with stock 4.1.1, it would just get stuck on the boot animation.
But this was the ONLY difference I found.
chrisb906 said:
OK. Cuz I keep trying to flash ROMs and getting prop boot errors. Lol
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
It's pretty simple. If you want to run an aosp ROM you need to at least run the 3.18 RUU. If you want to run a Sense 5 ROM you need to flash the 2.15 firmware. The 2.15 firmware is compatible with both so you may as well just flash that and you're safe either way.
If you've been flashing just hboots you've been doing it wrong and probably have a major mismatch between your firmware and your hboot. Also, if you have a modified hboot (red text removed) it can cause problems.
Sent from my Evita
If you want to run the latest Hboot and firmware with many of the AOSP Roms you basically have two choices:
1. Modify the install script to accept the HBoot version #:
http://forum.xda-developers.com/showthread.php?t=2627309&page=5
2. Downgrade to 2.15 and move back to 2.18 after Rom install:
http://forum.xda-developers.com/showthread.php?t=2517148
then
http://forum.xda-developers.com/showthread.php?t=2651052
You must be SOFF to do any of this!
So far CM 11 supports the new Firmware and Hboot. Any Rom using CM as the base (after they introduced support) will work with no problems.
Absolutely. It remains to be seen whether there's actually any benefit to changing from 2.15 to 2.17 or 2.18 though.
Sent from my Evita
timmaaa said:
Absolutely. It remains to be seen whether there's actually any benefit to changing from 2.15 to 2.17 or 2.18 though.
Sent from my Evita
Click to expand...
Click to collapse
I flashed it after the "reduced" version was released by 24ky. So far I can't tell the difference between them. The only difference I have noticed is a slight bit better signal but it's nothing to write home about and it may only apply to me in my cell coverage area. So I'll stick with it for now.
timmaaa said:
It isn't even the hboot that matters, it's the firmware that the hboot is a part of that matters. You can flash just the hboot all you like and it won't achieve anything without the rest of the firmware.
It'd be a short list anyway; any current aosp ROM requires at least the 3.18 firmware which includes the 2.14 hboot. Any Sense 5 ROM requires at least the 5.08 firmware that includes the 2.15 hboot. Any Sense 4 ROM it doesn't matter.
I'm pretty sure this information is mentioned in my Evita FAQ thread already but I'll double check and revise it if necessary.
Sent from my Evita
Click to expand...
Click to collapse
so a long story short...what is the best firmware to flash almost any rom?
chrisb906 said:
so a long story short...what is the best firmware to flash almost any rom?
Click to expand...
Click to collapse
is this 2.15 on this list somewhere? lol
Edit: I mean the ruu with the 2.15
http://androidruu.com/?developer=Evita
timmaaa said:
It's pretty simple. If you want to run an aosp ROM you need to at least run the 3.18 RUU. If you want to run a Sense 5 ROM you need to flash the 2.15 firmware. The 2.15 firmware is compatible with both so you may as well just flash that and you're safe either way.
If you've been flashing just hboots you've been doing it wrong and probably have a major mismatch between your firmware and your hboot. Also, if you have a modified hboot (red text removed) it can cause problems.
Sent from my Evita
Click to expand...
Click to collapse
What about aokp? I can't flash that with 2.15
Sent from my One X using Tapatalk
chrisb906 said:
is this 2.15 on this list somewhere? lol
http://androidruu.com/?developer=Evita
Click to expand...
Click to collapse
Lol, this dead horse refuses to go away. There's literally nothing left to beat....
It's this simple really:
Sense based Roms 4.2.2 and higher = 2.15 (for now) You can try 2.17 or 2.18...who knows. I haven't seen any reports yet.
AOSP based Roms 4.2.2 and higher = 2.14 (unless the Rom's updater script is modified to allow higher, in which case it really doesn't make much of a difference.)
Should you want to go with an AOSP Rom with a higher firmware and Hboot and the Rom's updater script hasn't been updated see my post above.^^
Make sense?
Yea..fully. Lol
Sent from my One X using Tapatalk
Just asking cuz I couldn't flash any aokp Roms. That's all
Sent from my One X using Tapatalk
And I did do the hboot 2.15 on the resurrected pandasa op. Haha
Sent from my One X using Tapatalk
I've flashed both AOKP and AICP with the 2.15 firmware installed. Anyway, like madcat said, kinda beating a dead horse here now, it should be simple.
Sent from my Evita
Yea. It is simple. I know this..but I still can't flash the aokp ROMs..even with appropriate versions. Just saying
Sent from my Desire HD using Tapatalk
I think that's because you've messed something up in flashing all these things without really knowing what you're doing.
Run the 3.18 RUU, flash the modified version of TWRP 2.6.3.0 or the new official TWRP 2.7, and flash the ROM. Do nothing but those. Report back.
Sent from my Evita
OK. But to let u know I ran 3.18 ruu then flashed 2.15 hboot.. Was that a bad idea?
Sent from my Desire HD using Tapatalk
If you flashed just the hboot, yes it was a bad idea. Like I said earlier in the thread, flashing just the hboot achieves nothing.
Sent from my Evita
Hello,
i'm having a lot of trouble with the viper made rom ( http://forum.xda-developers.com/showthread.php?t=2667758). I'm new here, so i cannot post it there.
My problems began when i try to install the updates. I have installed the original rom version 3.0.0. i get the OTA message, but when i try to install it in recovery, the phone can't mount the sd card, and the installation doesn't continu. I tried to do it manually (using the download link i found in one of the posts) and that seemed to work.
Then i got another OTA notification, to upgrade to version 3.1.0, but when i tried to boot after the installation, i couldn't enter my sim pincode, and when i reboot, the phone keeps looping. I have to install the original rom twice (once with and one time without wiping) before the ROM boots normally.
What am i doing wrong?
i'm on Hboot 1.25 and radio:1.15.50.05.29
I'm S-on (RL)
It seems that viper made a fll rom, with the updates included.
Wrong Hboot?
Martin_Weterholt said:
Hello,
What am i doing wrong?
i'm on Hboot 1.25 and radio:1.15.50.05.29
I'm S-on (RL)
Click to expand...
Click to collapse
I'm not sure but i think it starts with your Hboot, maybe one of the older members can verify, but according to the rom it requires Hboot version 2.15 or 2.16.
I am in the process of updating my Hboot by downloading and flashing the RUU as well as achieving S-OFF status
fidodaj said:
I'm not sure but i think it starts with your Hboot, maybe one of the older members can verify, but according to the rom it requires Hboot version 2.15 or 2.16.
I am in the process of updating my Hboot by downloading and flashing the RUU as well as achieving S-OFF status
Click to expand...
Click to collapse
You need to update hboot first
2.15 is most compatible i suppose
LS.xD said:
You need to update hboot first
2.15 is most compatible i suppose
Click to expand...
Click to collapse
Question. Is there a way for me to upgrade the hboot without the ruu wiping everything? Or will I just have to make a backup. I plan to go s-off before upgrading the hboot.
fidodaj said:
Question. Is there a way for me to upgrade the hboot without the ruu wiping everything? Or will I just have to make a backup. I plan to go s-off before upgrading the hboot.
Click to expand...
Click to collapse
If you're S-OFF ist possible I think
No, you don't need to update the hboot. I am on 1.06 and Viper works fine...in fact any ROM works fine for me but that's another story. The updated firmware (2.13 or 2.15) is required only for Android 4.4.x KitKat due to a check present in the updater-script. There's no such check nor requirement for previous Android versions and Viper 3.x is based on Android 4.2.2
The problems first could come from not being S-Off...this makes impossible to flash the kernel from recovery so any OTA that has a kernel is not flashed properly. I remember that 3.1.0 has also a full ROM ZIP, maybe is good if you flash that one from recovery and flash the kernel after that in fastboot. Also it could matter the recovery you're using, I would recommend latest TWRP
Sent from nowhere over the air..
Rapier said:
No, you don't need to update the hboot. I am on 1.06 and Viper works fine...in fact any ROM works fine for me but that's another story. The updated firmware (2.13 or 2.15) is required only for Android 4.4.x KitKat due to a check present in the updater-script. There's no such check nor requirement for previous Android versions and Viper 3.x is based on Android 4.2.2
..
Click to expand...
Click to collapse
In the viper rom forum post it says ROM firmware required hboot 2.15/2.16.. Am I to j just ignore tha? Or is it that it is only required that hboot (2.15/2.16) if you are s-on and s-off can do whatever you like? Lol
You need hboot 2.16 for Radio 1.20
And to Flash hboot 2.16 you will need S-OFF
Sent from my loved HTC One S using (most time buggy) Tapatalk
LS.xD said:
You need hboot 2.16 for Radio 1.20
And to Flash hboot 2.16 you will need S-OFF
Sent from my loved HTC One S using (most time buggy) Tapatalk
Click to expand...
Click to collapse
Actually I'm on hboot 2.15 with Radio 1.20.XX
I know this doesn't help... just saying..
To contribute smth. To get the most out of the Viper 3 Rom, everyone should upgrade their Radio to 1.20.XX. And this is actually why you need to S-OFF.
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.