Database Info

[Q] HBoot and Radio Advice please

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

How to flash new radio with hboot 1.13?

I know with Hboot 1.13, I can't flash radio in recovery. I've heard I've to do supercid or relock the phone to RUU or somethings like that?
Could ne1 kinda give me any information or links on how to do it step by step?
Thanks

1. Do that SuperCID thing
2. Go to Recovery, install the 1.74 ( I think ) RUU
Your phone will be re-locked now and be pretty much vanilla.
3. Install 2.12 Update
4. Unlock again
5. Have fun

http://forum.xda-developers.com/showthread.php?t=1671643
I just found the relative thread of how to do supercid on One S. After doing supercid... I have to go to recovery mode and run the 1.78 RUU? and OTA to 2.21? After all, Unlock it again and root.
My Question is do I need to flash stock recovery, stock boot and relock bootloader myself before run the 1.78 RUU?

Did you try to root the 2.21 RUU?

After installing 2.21 RUU, I've unlocked my bootloader, reinstalled CWM recovery, rooted my phone (everything was on that thread http://forum.xda-developers.com/showthread.php?t=1583427) and reinstalled my CM10 backup (without forgetting to flash boot.img via fastboot) and everything is OK!

Thanks everyone. I just successfully updated my radio with 2.21 RUU now. After that, I unlocked my bootloader again and install clockwork recovery and SU.
I just flashed trickdroid V7.1, everything works great. Actually, the procedure isn't difficult but extremely troublesome ... damn the HTC doesn't give us S-Off.

I don't remember, but will booting into recovery allow you to flash radio without flashing the ruu first. Don't know if cwr or twrp would be better for that. It worked on kernels, I believe, as the htc restrictions did not then apply.

It depends on your actual hboot, since 1.13 hboot you can't directly flash radio throught recovery and you have to install the latest RUU but if you are still on an older hboot you can flash the radio via CWM or TWRP (follow this thread http://forum.xda-developers.com/showthread.php?t=1684477).

I am familiar with that link and have used it. As I am on .06 hboot I have no issues flashing radios.
Was just trying to determine for others if that method would work on .13 and higher and why not. I personally am not 100% sure if it will or will not--
Since I have not seen any posts on doing that, it probably won't--not sure

[Q] reboot loop / update hboot

My Hox has been running CleanRom 5.1 for sometime now, but I wanted to make the jump to a JB rom. I'd been having trouble in the past where I'll flash a JB rom (doing all the other stuff with it too), and it will start up fine. However during a reboot, it will get stuck in a boot loop despite the correct boot.img being flashed. After some searching of the forums and the web, I figured it must be my hboot - I'm at 1.14.0002.
How does one go about upgrading / updating the hboot to 1.31 / 1.39, which from what I've read seems to be what I need to get a JB rom to work properly? I've seen bits and pieces saying to download a RUU or nandroid back up, but my CID is 1111111 (The generic one) and I can't find a RUU to match it. Is that what I even need to do to update the hboot?

uncledoobie said:
My Hox has been running CleanRom 5.1 for sometime now, but I wanted to make the jump to a JB rom. I'd been having trouble in the past where I'll flash a JB rom (doing all the other stuff with it too), and it will start up fine. However during a reboot, it will get stuck in a boot loop despite the correct boot.img being flashed. After some searching of the forums and the web, I figured it must be my hboot - I'm at 1.14.0002.
How does one go about upgrading / updating the hboot to 1.31 / 1.39, which from what I've read seems to be what I need to get a JB rom to work properly? I've seen bits and pieces saying to download a RUU or nandroid back up, but my CID is 1111111 (The generic one) and I can't find a RUU to match it. Is that what I even need to do to update the hboot?
Click to expand...
Click to collapse
if you have hboot 1.14, you can downgrade via JET. This will require a computer running linux and involves intentionally bricking and then debricking your device. This method is not everyone's cup of tea.
If you are flashing the boot.img and getting bootloops, I wouldn't think downgrading your hboot would help. Did you remember to wipe data from TWRP (and the cache/dalvik of course)?

codeprimate said:
if you have hboot 1.14, you can downgrade via JET. This will require a computer running linux and involves intentionally bricking and then debricking your device. This method is not everyone's cup of tea.
If you are flashing the boot.img and getting bootloops, I wouldn't think downgrading your hboot would help. Did you remember to wipe data from TWRP (and the cache/dalvik of course)?
Click to expand...
Click to collapse
Yep, do the wipes of everything, plus factory reset. I flash the boot.img properly from each rom every time. Is going to 1.31/1.39 a downgrade from 1.14? or an upgrade?

uncledoobie said:
Yep, do the wipes of everything, plus factory reset. I flash the boot.img properly from each rom every time. Is going to 1.31/1.39 a downgrade from 1.14? or an upgrade?
Click to expand...
Click to collapse
From 1.14 to 1.39 would technically be an upgrade, but most people want to downgrade their hboot to 1.09 (as 1.09 allows flashing of kernels/radios).
Just quickly, when you are flashing the boot.img, are you writing
"fastboot flash boot boot.img" this will flash the kernel, so it persists it through boot.
or
"fastboot boot boot.img" this will load the kernel at startup, but will not persist it through a reboot.

codeprimate said:
From 1.14 to 1.39 would technically be an upgrade, but most people want to downgrade their hboot to 1.09 (as 1.09 allows flashing of kernels/radios).
Just quickly, when you are flashing the boot.img, are you writing
"fastboot flash boot boot.img" this will flash the kernel, so it persists it through boot.
or
"fastboot boot boot.img" this will load the kernel at startup, but will not persist it through a reboot.
Click to expand...
Click to collapse
holy ****e, i think that's it. i've been doing just the latter. i forgot the "flash".
i will try this and report back.
Update: Success!

uncledoobie said:
holy ****e, i think that's it. i've been doing just the latter. i forgot the "flash".
i will try this and report back.
Update: Success!
Click to expand...
Click to collapse
LOL, glad to hear you have it sussed.

uncledoobie said:
my CID is 1111111 (The generic one) and I can't find a RUU to match it. Is that what I even need to do to update the hboot?
Click to expand...
Click to collapse
That CID is not "generic", its called SuperCID, which basically bypasses all CID check.
The problem is version check, in which the RUU will not run if it detects a newer (higher number) hboot version already on the device. So that is why downgrading by "unofficial" means is the only way to move down to a previous (lower number) hboot version.

redpoint73 said:
That CID is not "generic", its called SuperCID, which basically bypasses all CID check.
The problem is version check, in which the RUU will not run if it detects a newer (higher number) hboot version already on the device. So that is why downgrading by "unofficial" means is the only way to move down to a previous (lower number) hboot version.
Click to expand...
Click to collapse
ah ok good to know.

so only downside of 1.14 comparing to 1.09 is that on 1.14 you have to flash kernels/radios manually via fastboot and 1.09 doesn't require that procedure?
codeprimate said:
From 1.14 to 1.39 would technically be an upgrade, but most people want to downgrade their hboot to 1.09 (as 1.09 allows flashing of kernels/radios).
Just quickly, when you are flashing the boot.img, are you writing
"fastboot flash boot boot.img" this will flash the kernel, so it persists it through boot.
or
"fastboot boot boot.img" this will load the kernel at startup, but will not persist it through a reboot.
Click to expand...
Click to collapse

For1n said:
so only downside of 1.14 comparing to 1.09 is that on 1.14 you have to flash kernels/radios manually via fastboot and 1.09 doesn't require that procedure?
Click to expand...
Click to collapse
I don't think the device firmware was changed from 1.09 to 1.14 (as it was from 1.14 to 2.14), so I believe that is correct. I may be wrong, there may have been firmware upgrades, but they don't seem to be as drastic as the 2.14 update (which changed the touchscreen firmware to the point that old kernels had no touchscreen functionality).

[q] 2.16 s-off tmous

This is more of a clarification request than a help question
As I understand it, mind you I am not that well versed in Android dev, you cannot obtain SuperCID/S-OFF either through Moonshine or Facepalm methods when you are on 2.16 HBOOT. Is that correct?
Given this is fact, the only way to have 2.16 + S-OFF is to be S-OFF before upgrading HBOOT to 2.16?
So let's say for my phone I have 2.15 HBOOT Moonshine'd S-OFF, if I upgrade to HBOOT 2.16 will i still maintain my S-OFF status?
And as a side question, what methods are available to upgrade my HBOOT from 2.15 to 2.16? Current phone is TMOUS CM10.1.3 with the latest *.17 firmware.

pyrocide said:
This is more of a clarification request than a help question
As I understand it, mind you I am not that well versed in Android dev, you cannot obtain SuperCID/S-OFF either through Moonshine or Facepalm methods when you are on 2.16 HBOOT. Is that correct?
Given this is fact, the only way to have 2.16 + S-OFF is to be S-OFF before upgrading HBOOT to 2.16?
So let's say for my phone I have 2.15 HBOOT Moonshine'd S-OFF, if I upgrade to HBOOT 2.16 will i still maintain my S-OFF status?
And as a side question, what methods are available to upgrade my HBOOT from 2.15 to 2.16? Current phone is TMOUS CM10.1.3 with the latest *.17 firmware.
Click to expand...
Click to collapse
Yes you stay s-off unless you give a certain command in fastboot. I'm not going to say the command because someone will type it and mess up their phone.
(FYI do not Go back to S-on unless your phone is completely back to stock)
Follow the original post in the Maximus HD thread, that flashes the new firmware that will update the HBoot, Radio, Repartition for new Android. Also the modified TWRP in that post is the only recovery that will work with the new firmware.
Oh, and yes, Moonshine and Facepalm do not work with 2.16. But there is a new way to S-off using rumrunner, that will even work with 2.16.
http://forum.xda-developers.com/showthread.php?t=2558334

tivofool said:
Yes you stay s-off unless you give a certain command in fastboot. I'm not going to say the command because someone will type it and mess up their phone.
(FYI do not Go back to S-on unless your phone is completely back to stock)
Follow the original post in the Maximus HD thread, that flashes the new firmware that will update the HBoot, Radio, Repartition for new Android. Also the modified TWRP in that post is the only recovery that will work with the new firmware.
Oh, and yes, Moonshine and Facepalm do not work with 2.16. But there is a new way to S-off using rumrunner, that will even work with 2.16.
http://forum.xda-developers.com/showthread.php?t=2558334
Click to expand...
Click to collapse
Do i have to be on stock to follow the Maximus install or can I be on a different rom with a different recovery than what is provided in the install package until I flash the provided recovery at the end of the install?

pyrocide said:
Do i have to be on stock to follow the Maximus install or can I be on a different rom with a different recovery than what is provided in the install package until I flash the provided recovery at the end of the install?
Click to expand...
Click to collapse
Ya, that is fine to be on a different ROM and Recovery.
Follow the directions exactly. (for example downloading and installing maximus before installing the new firmware and recovery and then reinstalling Maximus.
-------------------------------------------
Here is another post related to MagioRom. It has firmware update instructions and also a link to a tool if you don't want to manually enter commands.
http://forum.xda-developers.com/showpost.php?p=47403627&postcount=3

tivofool said:
Ya, that is fine to be on a different ROM and Recovery.
Follow the directions exactly. (for example downloading and installing maximus before installing the new firmware and recovery and then reinstalling Maximus.
-------------------------------------------
Here is another post related to MagioRom. It has firmware update instructions and also a link to a tool if you don't want to manually enter commands.
http://forum.xda-developers.com/showpost.php?p=47403627&postcount=3
Click to expand...
Click to collapse
Welp i got past the first install but after rebooting into fastboot and oemReboot trying to flash the recovery (after the firmware.zip was successful) I am stuck at the black screen w/ silver HTC logo and an incomplete green bar. Power down and try again? Or wait some more, been about 5 minutes so far.

pyrocide said:
Welp i got past the first install but after rebooting into fastboot and oemReboot trying to flash the recovery (after the firmware.zip was successful) I am stuck at the black screen w/ silver HTC logo and an incomplete green bar. Power down and try again? Or wait some more, been about 5 minutes so far.
Click to expand...
Click to collapse
I believe you are still in RUU mode, so since the firmware successfully flashed, reboot phone into bootloader and fastboot flash recovery recovery.img

tivofool said:
I believe you are still in RUU mode, so since the firmware successfully flashed, reboot phone into bootloader and fastboot flash recovery recovery.img
Click to expand...
Click to collapse
that is correct, following maximus to the letter it did not mention going back to bootloader after flashing the firmware.zip. What about the incomplete green bar should I be worried about that?

pyrocide said:
that is correct, following maximus to the letter it did not mention going back to bootloader after flashing the firmware.zip. What about the incomplete green bar should I be worried about that?
Click to expand...
Click to collapse
Nope, I'm almost positive you have done everything correctly. Just my memory is a little fuzzy, but I'm pretty sure that is exactly what has happened to me. (I've installed Maximus and firmware 3 different occasions)

tivofool said:
Nope, I'm almost positive you have done everything correctly. Just my memory is a little fuzzy, but I'm pretty sure that is exactly what has happened to me. (I've installed Maximus and firmware 3 different occasions)
Click to expand...
Click to collapse
Still not able to flash recovery after rebooting to bootloader fastboot USB mode.
Device now shows instead of Moonshine at the top
***Tampered***
***Locked***
S-OFF
CID T-MOB010
HBoot 2.16
Code:
C:\adb\Install Package>fastboot flash recovery recovery.img
sending 'recovery' (8900 KB)...
OKAY [ 1.077s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.114s
It shouldnt matter still being s-off, but I still have my unlock token to unlock the bootloader.

pyrocide said:
Still not able to flash recovery after rebooting to bootloader fastboot USB mode.
Device now shows instead of Moonshine at the top
***Tampered***
***Locked***
S-OFF
CID T-MOB010
HBoot 2.16
Code:
C:\adb\Install Package>fastboot flash recovery recovery.img
sending 'recovery' (8900 KB)...
OKAY [ 1.077s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.114s
It shouldnt matter still being s-off, but I still have my unlock token to unlock the bootloader.
Click to expand...
Click to collapse
Yep, that is why. Unlock that bootloader.

tivofool said:
Yep, that is why. Unlock that bootloader.
Click to expand...
Click to collapse
Forgive my ignorance but wasnt the entire point of being S-OFF was not having to jack with the bootloader being locked and unlocked/relocked etc?
Got it to boot, working on second maximus install now.

pyrocide said:
Forgive my ignorance but wasnt the entire point of being S-OFF was not having to jack with the bootloader being locked and unlocked/relocked etc?
Got it to boot, working on second maximus install now.
Click to expand...
Click to collapse
I know what you mean, but no, the bootloader needs to be unlocked to root and flash custom roms. But there is still some security that needs to be turned off to be able to change some things, like HBoot and other things.

tivofool said:
I know what you mean, but no, the bootloader needs to be unlocked to root and flash custom roms. But there is still some security that needs to be turned off to be able to change some things, like HBoot and other things.
Click to expand...
Click to collapse
Thanks for the help, got it booting and charging. Gonna test the battery with the extended battery from the One X+ and see how much better this battery is vs CM10.1.3 and bootloops/reboots etc.

[Q] Cannot flash stock/any rom

I decided to update my Dev unlocked Sensation to ICS, but had forgotten it was probably still on a Gingerbread radio. Now I have no working rom, and for some reason I am unable to flash the original rom (RUU) via the SD card method (PG58IMG).
My CID is HTC__E11 and therefor european roms from RUU should work, but I get the following error message when trying the sd card flash: wrong zipped image. In other cases it wont go further than parsing.
When i try to flash the RUU in ruu mode on the phone I get the following error: 99 unknown fail.
Unfortunately I cannot go back to the rom I was on before, since I dont have it anymore.
So the only thing I have now is TWRP recovery 2.6.3 and unlocked HBOOT 1.27.
Furthermore I am unable to see what my current radio firmware is. I want to flash a jellybean rom.
Does anyone know what to do?

MAsterokki said:
I decided to update my Dev unlocked Sensation to ICS, but had forgotten it was probably still on a Gingerbread radio. Now I have no working rom, and for some reason I am unable to flash the original rom (RUU) via the SD card method (PG58IMG).
My CID is HTC__E11 and therefor european roms from RUU should work, but I get the following error message when trying the sd card flash: wrong zipped image. In other cases it wont go further than parsing.
When i try to flash the RUU in ruu mode on the phone I get the following error: 99 unknown fail.
Unfortunately I cannot go back to the rom I was on before, since I dont have it anymore.
So the only thing I have now is TWRP recovery 2.6.3 and unlocked HBOOT 1.27.
Furthermore I am unable to see what my current radio firmware is. I want to flash a jellybean rom.
Does anyone know what to do?
Click to expand...
Click to collapse
ok would i be correct in thinking that you are s-on? how exactly did you upgrade from gingerbread to ics and have you tried formatting all partitions from twrp?

heavy_metal_man said:
ok would i be correct in thinking that you are s-on? how exactly did you upgrade from gingerbread to ics and have you tried formatting all partitions from twrp?
Click to expand...
Click to collapse
Yes I am S-ON. I did try formatting all partitions from twrp, that didnt help. I also tried cwm, but that didnt help either.
My radio was finally displayed by HBOOT, it is: 11.29A.3504.18_M. I believe this is a ICS radio, so there should be no problem here. Unfortunately i cannot find the RUU that corresponds to that radio and trying to flash another ruu wont work.
To go to ICS I just installed the latest CM11 from Sultan, which works on my other sensation (which is S-OFF). I have also tried other roms, but they all wont boot for some weird reason. For every rom I do a full wipe.

MAsterokki said:
Yes I am S-ON. I did try formatting all partitions from twrp, that didnt help. I also tried cwm, but that didnt help either.
My radio was finally displayed by HBOOT, it is: 11.29A.3504.18_M. I believe this is a ICS radio, so there should be no problem here. Unfortunately i cannot find the RUU that corresponds to that radio and trying to flash another ruu wont work.
To go to ICS I just installed the latest CM11 from Sultan, which works on my other sensation (which is S-OFF). I have also tried other roms, but they all wont boot for some weird reason. For every rom I do a full wipe.
Click to expand...
Click to collapse
If your s-on you need to flash the boot.IMG of your rom from fastboot straight after flashing your rom from recovery pal. But I recommend installing 4ext recovery and enabling its "smart flash" feature and this will do it for you try this and check back pal.
Sent from my Nexus 7 using Tapatalk

heavy_metal_man said:
If your s-on you need to flash the boot.IMG of your rom from fastboot straight after flashing your rom from recovery pal. But I recommend installing 4ext recovery and enabling its "smart flash" feature and this will do it for you try this and check back pal.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Lol I have been doing this for so long with a S-OFF device that I totally forgot about that! Thank you so much, sorry for my stupidity haha. Still weird that I cannot flash RUU though...

MAsterokki said:
Lol I have been doing this for so long with a S-OFF device that I totally forgot about that! Thank you so much, sorry for my stupidity haha. Still weird that I cannot flash RUU though...
Click to expand...
Click to collapse
Its cool pal it is, but then again ruus won't flash unless your bootloader is relocked
Sent from my Nexus 7 using Tapatalk