Database Info

(advice needed) Hboot 2.00.0002, should I downgrade or not ?

I currently have a desires s (S-ON, not-rooted and bootloader unlocked), I am not sure if I should downgrade to hboot 0.98 as S-OFF for this is not available right now and as the title says I want you all to tell me what to do !
I could either keep this hboot and simply unlock the boot loader, root my phone and install a custom recovery to flash roms. But that way I won't be able to S-OFF my device and hence I wouldn't be able to install all custom roms such as virtuous saga which requires S-OFF .
And If I downgrade my device, I am not sure if the kernels,radio, and other things would be that efficient plus I doubt if I would be able to install all roms, like ICS Sense 4 roms
(kinda new to all this so I don't know if I am being a noob, but I seriously need your reply on this)
Sent from my HTC Desire S using xda premium

I can tell you what i did:
I unlocked my bootloader at htcdev right away when i got my desire s, then got superuser access to my phone. It was pretty fun, but I couldn't do EVERYTHING Plus, I lost parts of my warranty.
I really wanted s-off to be able to flash all roms available.
After a month or so, i did a downgrade of the hboot, with this instructions.
It worked flawlessly, although it's an hour of work or so if you're new to android. Terminal/ADB looks weird and complicating at first, but hey, you just need to copy the lines off the tutorial, it works perfect if you do as told
My advice: DON'T unlock at HTCdev (gives yo FULL warranty, even if you flash a custom rom), and just simply follow the downgrade instructions. Then you'll have full access, full warranty and no limitations at all, it's absolutely worth the downrade/s-off!
I'm running ICS now and couldn't be happier with my phone!

First of all thank you for your help on this, even I have had the same thought that its better to downgrade my phone and S-OFF it rather than keeping it S-ON.
Btw I came across anouther doubt which I guess its better to ask here instead of creating a new thread every time, : if I have to use an ruu to downgrade ny device, should my current radio (as seen in bootloader) match the ruu's radio ??
Sent from my HTC Desire S using xda premium

No

Have changed my Rom twice not touched the radio firmware at all.
If it ain't broke don't fix it, also read on xda somewhere radio firmware is a local thing it may work in your area but not mine
Sent from my HTC Desire S using Tapatalk

13th Dev said:
I could either keep this hboot and simply unlock the boot loader, root my phone and install a custom recovery to flash roms. But that way I won't be able to S-OFF my device and hence I wouldn't be able to install all custom roms such as virtuous saga which requires S-OFF .
And If I downgrade my device, I am not sure if the kernels,radio, and other things would be that efficient plus I doubt if I would be able to install all roms, like ICS Sense 4 roms
Click to expand...
Click to collapse
IMO, there is not much need for you to flash radio.. most of the time you won't need to do so..
and HBoot version can be changed if you are S-Off..
but i have to disagree with your statement that if you don't S-Off you are not able to flash all custom roms.. yes, some may fail to boot up, but mostly they will boot up without problem..
I am currently at the same Hboot as you, HTCDev unlocked and i have tried many roms without problem..
the only thing about having S-On for me is that i will always be dependant on my computer to flash ROM.. other than that, there's no problem generally.. Oh, maybe there is one thing, HTC may know that your phone has already been unlocked since you are using their unlocker.. but there are some ways to relock it and restore the "RELOCKED" in bootloader to "LOCKED"..
I am a newbie, and that's why i unlocked it with HTCDev, but if i were to do it all over again, i would have spend few more days to learn how to downgrade the Hboot and S-Off instead.. you can always flash newer Hboot later anyway..
So my advice, don't worry so much about the radio, or the Hboot version (you can tweak that later) at the moment, then downgrade the Hboot and S-Off it..
IMO it's much better than using HTC unlocker..

thank you guys for all your help and advice, finally after spending a couple of days,I successfully downgraded hboot 2.00.0002 to .98 one.
once again, thankyou all
Sent from my HTC Desire S using xda premium

I assume that you're revolutionary S-OFF by now, you can now easily upgrade on the latest re-engineered hboot

@doghous exactly !, I'm thinking of changing my hboot to the new re_engineered 2.00.0002 by vampire36, or if someone could suggest a better one.......
Sent from my HTC Desire S using xda premium

13th Dev said:
@doghous exactly !, I'm thinking of changing my hboot to the new re_engineered 2.00.0002 by vampire36, or if someone could suggest a better one.......
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
I have successfully S-Off my DS from HTC Unlock using the method by Skanob, it's pretty straight forward and noob-proof.. (not that you need that now ) and can be used to revert back to stock, S-On, Locked (not Re-locked) if you ever need to repair..
As for Hboot, i have upgraded the Hboot to Eng Hboot 7.00.1002 (the one you mentioned above) so that would be my recommendation, too!

doghous said:
I assume that you're revolutionary S-OFF by now, you can now easily upgrade on the latest re-engineered hboot
Click to expand...
Click to collapse
Does anyone know what the differences between the different versions of ENG Hboot?
ENG v0.98.2000 vs. ENG v2.00.xxxx vs. ENG v7.xx.xxxx
Any benefits of using v2.00 or v7.xx over the v0.98?
Thx.

anchemis said:
ENG v7.xx.xxxx
Click to expand...
Click to collapse
This one isn't an eng hboot. Better use 2.00.2002

anchemis said:
Does anyone know what the differences between the different versions of ENG Hboot?
ENG v0.98.2000 vs. ENG v2.00.xxxx vs. ENG v7.xx.xxxx
Any benefits of using v2.00 or v7.xx over the v0.98?
Thx.
Click to expand...
Click to collapse
A good question actually, even I have the same doubt and would really appreciate if someone could post the answer !
Sent from my HTC Desire S using xda premium

This is what I've gathered from forum trawling...
v0.98.xxxx: the original hboot for 1.x roms
Has the partitions: /system, /cache, /data (all ext3 or ext4)
Fastboot support, supports Revolutionary S-OFF
ENG v0.98.xxxx: engineering version of above
v2.00.2002: the new hboot for 2.x roms (Sense 3.0 etc.)
Has the partitions: /system, /system/lib, /cache, /data (all ext4)
NOT supported by Revolutionary
-> apparently, some Sense 3.0+ roms need this new /system/lib partition to work (stability issues), but I'm not sure which ones though...
->Note Revolutionary is NOT supported, so to S-OFF you need to downgrade using TacoRoot, ZergRush/Misc_versions, XTC clip or some other method.
ENG v2.00.xxxx: engineering version of above
RVL v6.98.1000: hboot that comes after you S-OFF with revolutionary
It is of a higher version number so breaks overflashing functionality, so you CANNOT revert to RUU (for warranty returns etc.)
-> Note: This can be overflashed with v6.98.2000 (OverARX), which then allows you to overflash a stock or engineered hboot.
v7.00.1002[\B]: modified 2.00.2000
NOT ENG BOOTLOADER
But are there any real life benefits of one over the other?

for example I have the Rev v6.98.1000 hboot, so what you mean is that I could have problems while flashing roms (occasionally), and hence I should change my hboot to the engineered one ?
Sent from my HTC Desire S using xda premium

I got really frustrated with being S-ON and found the HBOOT downgrade instructions dubious so I found someone in my area with an XTC CLIP device and S-Offed the bastard , don't care much about warranty at this point however.

@ste_vald well done there !, having an s-offed device is surely much better
Sent from my HTC Desire S using xda premium

13th Dev said:
for example I have the Rev v6.98.1000 hboot, so what you mean is that I could have problems while flashing roms (occasionally), and hence I should change my hboot to the engineered one ?
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
No, you should be fine installing most of the ROM's (unless specified otherwise in the OP of the ROM).
However, ENG Hboot is recommended so that if required later you can easily flash new radio's / Hboot.

Thank you, but can't I flash radios on this rev hboot
Sent from my HTC Desire S using xda premium

No, i believe you can't! You will require an ENG Hboot...

HBOOT 2.02 can S-OFF ??

Can I S-OFF the hboot 2.02 ??
I mean this guide: http://forum.xda-developers.com/showthread.php?t=1399331 will work for my HBOOT 2.02 ?

No, because zergRush won't work. You'll have to unlock your bootloader to gain any sort of root.
Edit: this guide would work
http://forum.xda-developers.com/showthread.php?t=1318919

To S-OFF you first have to downgrade to an older HBOOT, which is done by gaining some form of root, running misc_version and then an older RUU. After you're S-OFF you can put on a newer (S-OFFed) HBOOT if you don't want Revolutionary's default one.
As long as you're running gingerbread (i.e. Android 2.3.x, and not ICS which is 4.0.4), you can get temproot. See my signature for more information.

paulie-uk said:
To S-OFF you first have to downgrade to an older HBOOT, which is done by gaining some form of root, running misc_version and then an older RUU. After you're S-OFF you can put on a newer (S-OFFed) HBOOT if you don't want Revolutionary's default one.
As long as you're running gingerbread (i.e. Android 2.3.x, and not ICS which is 4.0.4), you can get temproot. See my signature for more information.
Click to expand...
Click to collapse
S-OFF is something I too want to do to my HTC Desire S, looking in your signature you are running 2.00.2002.
I am on a newer HBOOT the 2.02.0002.
I understand you have to downgrade first, and then S-OFF, but after S-OFF can I then flash the ICS RUU and get it back to 2.02.0002?
Will it still say Revolutionary? or go back to saying Unlocked (As I am HTC DEV Unlocked).
My main concern is that I don't like the idea of having 0.98, on there after, or having a fake number 6.98 or 7.00.2000 etc.
There seems to be a lot of people still on 2.00.X and not on the 2.02.X.
Are you S-OFF paulie-uk?

readmanr said:
S-OFF is something I too want to do to my HTC Desire S, looking in your signature you are running 2.00.2002.
I am on a newer HBOOT the 2.02.0002.
[...]
Are you S-OFF paulie-uk?
Click to expand...
Click to collapse
I'm hboot S-OFF (what revolutionary can provide), not radio S-OFF (sadly the only way to do this on SAGA is with some extra equipment). I believe the 2.02.0002 hboot came in the ICS RUU, it's just got a bit tighter security, I don't think the partitions have changed since the last version (someone correct me if I'm wrong here).
readmanr said:
There seems to be a lot of people still on 2.00.X and not on the 2.02.X.
Click to expand...
Click to collapse
I'm using an S-OFFed ENGineering hboot, where you see people on the other version (2.00.0002) it is (usually) the stock SHIP hboot.
readmanr said:
I understand you have to downgrade first, and then S-OFF
Click to expand...
Click to collapse
You will have to downgrade. Sadly this will wipe your phone.
readmanr said:
but after S-OFF can I then flash the ICS RUU and get it back to 2.02.0002?
Will it still say Revolutionary? or go back to saying Unlocked (As I am HTC DEV Unlocked).
My main concern is that I don't like the idea of having 0.98, on there after, or having a fake number 6.98 or 7.00.2000 etc.
Click to expand...
Click to collapse
After you're S-OFF, I'd suggest you try a custom ROM and not flashing the 4.0.4 RUU (it's a buggy experimental version). Flashing an official RUU is pretty much how you return to stock, so it would most likely overwrite your S-OFFed hboot with a S-ON stock one. Remember, the S-OFF on our device is done in the hboot and not the radio.
When you're S-OFFed the first hboot you will have will be Revolutionary's 6.98 one. You can change this after.
I've found that 2.00.2002 works with all of the ROMs I've tried (which have been based on gingerbread, ICS and JellyBean). The "fake number" ones are there to make flashing a S-ON hboot more difficult, meaning that an OTA update wouldn't undo it. However, it is quite obvious if you were to send your phone in for repairs (still in warranty!?!?!) which is why a few of the tech-savvy who want S-OFF put on the ENG hboots instead.
If you want to overwrite Revolutionary's hboot with a different one with a lower version number, you will need to use dd and if it goes wrong it will brick your phone. You can find the ENG hboots on cyannogenmod's wiki if you don't trust the files I provide in other posts, but I strongly suggest you read about what you're going to do until you're comfortable with it before taking action.
Remember that after changing a hboot or radio, you should always re-wipe and re-flash your phone as partitions can move and always check the md5 first.

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

[S4] HBOOT Comparison | 2.15 vs 2.16

This is a comparison between the older Jellybean HBOOT 2.15 and the leaked HBOOT 2.16​
HBOOT 2.15 Pros​
Supported by about 95% of the HTC One S ROMs around
Ability to mount storage as Mass Storage. TWRP 2.7.x.x and lower
Going S-ON with this HBOOT won't corrupt your SD Card
HBOOT 2.15 Cons​
Smaller SD Card partition - 10 GB of Storage
Smaller System partition - 1 GB-ish (Not sure what exact size is)
Older Radio, ADSP, WCNSS and other firmware elements
HBOOT 2.16 Pros​
Bigger SD Card Partition - 12.9 GB of Storage
Bigger System Partition - About 1.5 GB - Useful for ported Sense ROMs
Updated Radio and other firmware elements - Better Radio performance, battery life, etc.
Growing support for HBOOT 2.16 ROMs
HBOOT 2.16 Cons​
Requires S-OFF to instal
Supported by about 30% of the HTC One S ROMs around
Going S-ON will corrupt your SD Card (Trust me!)
Installation NOT recommended for first time users
As you can see here there is no real advantage of upgrading to HBOOT 2.16 other than the increased partition sizes, but there is not really any disadvantage other than the S-ON SD Card corruption, it does give you slightly better Radio performance though. Anyway, hopefully this will help users decide whether or not to upgrade to HBOOT 2.16
Please tell me more of your pros and cons of each HBOOT that are NOT already listed here and I will include them​

Very useful, great idea

Well I'm on HBOOT 2.15.4444 (moonshine hboot) and I have the full set of fastboot oem flash commands. I also manually upgraded to the newer Radio 1.20, with matching WCNSS and ASDP so I'm fine that way. I use CM 11 M10 atm, got to update my signature, and it doesn't support HBOOT 2.16 yet. I dont need the bigger partition sizes, i'm doing just fine for now so I'm sticking with HBOOT 2.15.4444 for the foreseeable future.

This is a good thread idea. But to help users interested I would add a definition of what is an HBOOT...
As I read your post, I see 2 possibilities :
you're talking about the firmware: boot loader + partition layout + recovery + radio + other partitions
or just the boot loader and partition layout
I would say number 2 but this is arguable...

kdd998 said:
This is a good thread idea. But to help users interested I would add a definition of what is an HBOOT...
As I read your post, I see 2 possibilities :
you're talking about the firmware: boot loader + partition layout + recovery + radio + other partitions
or just the boot loader and partition layout
I would say number 2 but this is arguable...
Click to expand...
Click to collapse
Mainy people on this thread refer to hboot 2.16 as the whole firmware (radio, bootloader, adsp, wcnss and parition scemes)

dd98 said:
Mainy people on this thread refer to hboot 2.16 as the whole firmware (radio, bootloader, adsp, wcnss and parition scemes)
Click to expand...
Click to collapse
Well the more technically inclined don't. When they think HBOOT 2.16, they think HBOOT 2.16 firmware that @LlabTooFeR leaked

javelinanddart said:
Well the more technically inclined don't. When they think HBOOT 2.16, they think HBOOT 2.16 firmware that @LlabTooFeR leaked
Click to expand...
Click to collapse
yes thats what im talking about

dd98 said:
HBOOT 2.16 Cons​Need to downgrade to HBOOT 2.15 to run an RUU
Click to expand...
Click to collapse
I have previously run an RUU to downgrade from 2.16 to 2.15. Why would you not be able to run it? I thought it would be the safest method.

rosswhite said:
I have previously run an RUU to downgrade from 2.16 to 2.15. Why would you not be able to run it? I thought it would be the safest method.
Click to expand...
Click to collapse
strangely enough whenever i ran an ruu, i had to re-install hboot 2.15

dd98 said:
strangely enough whenever i ran an ruu, i had to re-install hboot 2.15
Click to expand...
Click to collapse
That's really odd. That shouldn't happen. I can always RUU over HBOOT 2.16 (well not ALWAYS, my computer is broken so....)
Also, as far as I know, only flash Radio, WCNSS, and ASDP from HBOOT 2.16 firmware on 2.15. I've run into issues before.

ability to mount mass storage in TWRP 2.7.1.2 , it works fine on my phone

kingofsurf said:
ability to mount mass storage in TWRP 2.7.1.2 , it works fine on my phone
Click to expand...
Click to collapse
thats only for hboot 2.15 though

dd98 said:
thats only for hboot 2.15 though
Click to expand...
Click to collapse
No it works on 2.16 also

Flashalot said:
No it works on 2.16 also
Click to expand...
Click to collapse
im thinking of modified twrp 2.6.1.0 then

I don't see older radios as a con since the one that come with jb was the best for me plus with s-off you can have any radio.
Sent from my One M8 using Tapatalk

I would like to try to go back to 2.15 because the call quality issue with sense6 drives me crazy. How to do? What ruu should I flash?

kingofsurf said:
I would like to try to go back to 2.15 because the call quality issue with sense6 drives me crazy. How to do? What ruu should I flash?
Click to expand...
Click to collapse
im assuming its a european one s, like mine. just flash this ruu
you need one of the following cids
11111111
HTC__001

How to install hboot 2.16
Can you help me how to install HBOOT 2:16 ???
Plzz...

ShkodranY said:
Can you help me how to install HBOOT 2:16 ???
Plzz...
Click to expand...
Click to collapse
There is a whole Q&A bit just for that or the one thread that has everything you need to flash it.
Sent from my One M8 using Tapatalk

ShkodranY said:
Can you help me how to install HBOOT 2:16 ???
Plzz...
Click to expand...
Click to collapse
You can try my guide here

[Q] Any SAFE & easy way to upgrade to HBOOT 2.16? Currently S-OFF with HBOOT 2.15

Hi everyone,
I got S-OFF quite a while back (when the first method came out, can't remember the name) and at that time I also upgraded to HBOOT 2.15 using some RUU (can't remember the details). Also, my factory CID is HTC__001 (I got it SIM-free).
Could anyone recommed a tried and tested way to upgrade to HBOOT 2.16? Wouldn't really want to brick my phone...
Thanks

It's really depressing that no one has an answer for this...

Is there any advantage to 2.16?

Well, as for me, I see the situation like this:
- You have S-OFF. You can flash whatever you like to system partitions, and even to HBoot
- You don't have S-off. You can only flash HTC-signed images to system partitions, sich as hboot, tz, radio, etc
Hboot 2.16 is a stuff from HTC One m7 world and won't won't boot on HTC One S straight away as a dump from that phone. If you modify it, you break signature, so you will get working but not flashable via RUU hboot.
Am I missing something?

@Jem256: Advantages and disadvantages can be found here.
@ovimunt: Upgrading to 2.16 isn't that complicated or risky (AS LONG AS YOU FOLLOW THE INSTRUCTIONS [look at the first post]). If you want to use the mounting option in recovery mode you need to flash the recovery I linked in my signature afterwards.
@ojomio: Actually hboot 2.16 is a leaked firmware which HTC abandoned before it was finished completely but it got finished and released by llabtoofer.

Follow MaximusHD
All U have to do just flash MaximusHD Rom or Follow their instructions coz MaximusHD requires Hboot 2.16