As far as i understand if I
1. Run AOSP Roms the radio that shows in H.Boot Doesn't matter at all
2. Run Sense Roms the radio that shows in h.boot does matter and the only way to truly change it is by flashing ruu's
Im just wondering btw.
AOSP roms use the radio that comes with the rom. Sense roms use the radio thats flashed on your device.
If you have an old hboot, 1.06 or 1.09, you can flash radios in recovery. On newer hboots you can not. You can however downgrade your hboot. There is a sticky on that.
Related
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).
Hi guys the title says it all. This is what i have:
HTC Sensation
Hboot 1.17.1111 S-OFF by Revolutionary.
CWM Recovery.
Super CID'ed.
Rooted
Well, as far as i know i have to Flash 4ext Recovery, download http://d-h.st/5Z6, put on the root of SDCARD, Go to Bootloader, Update the Firmware, and pull out the battery. Remove zip from SD Card, go to recovery, superwipe and Flash ARHD 6.7?
Now, the Questions about this:
1.- The Firmware makes the bootloader change to 1.27.xxxx Does that matter if i am S-OFF or will the phone remain being S-OFF?
2.- Does the FW include the Radio? If it does...
3.- Does the included radio works for Mexico Carriers or not?
Thanks Guys...
luis4ever said:
Hi guys the title says it all. This is what i have:
HTC Sensation
Hboot 1.17.1111 S-OFF by Revolutionary.
CWM Recovery.
Super CID'ed.
Rooted
Well, as far as i know i have to Flash 4ext Recovery, download http://d-h.st/5Z6, put on the root of SDCARD, Go to Bootloader, Update the Firmware, and pull out the battery. Remove zip from SD Card, go to recovery, superwipe and Flash ARHD 6.7?
Now, the Questions about this:
1.- The Firmware makes the bootloader change to 1.27.xxxx Does that matter if i am S-OFF or will the phone remain being S-OFF?
2.- Does the FW include the Radio? If it does...
3.- Does the included radio works for Mexico Carriers or not?
Thanks Guys...
Click to expand...
Click to collapse
1. You will remain S-OFF but your hboot will say LOCKED but dont worry, it just means you havent used htcdev unlock and you dont need to because S-OFF is better so just ignore the LOCKED text.
2. Yes
3. Should be but if you have signal problems you can always flash a different radio.
Oh and one more thing - you say you HAVE to flash ARHD ROM, well you dont HAVE to, you can flash any ICS ROM you want, the choice is not limited to only 1 ROM
Jonny said:
1. You will remain S-OFF but your hboot will say LOCKED but dont worry, it just means you havent used htcdev unlock and you dont need to because S-OFF is better so just ignore the LOCKED text.
2. Yes
3. Should be but if you have signal problems you can always flash a different radio.
Oh and one more thing - you say you HAVE to flash ARHD ROM, well you dont HAVE to, you can flash any ICS ROM you want, the choice is not limited to only 1 ROM
Click to expand...
Click to collapse
So you say it will change from Revolutionary to LOCKED but it will remain with S-OFF right? And i used ARHD because all use that rom for example. Now, the FW says 3.32.xxx and there are roms based on 3.33, what if i want thar rom? Do i need to change the FW again? And if i want to go back should i flash 3.32 and that everytime?
luis4ever said:
So you say it will change from Revolutionary to LOCKED but it will remain with S-OFF right? And i used ARHD because all use that rom for example. Now, the FW says 3.32.xxx and there are roms based on 3.33, what if i want thar rom? Do i need to change the FW again? And if i want to go back should i flash 3.32 and that everytime?
Click to expand...
Click to collapse
I knew about the example, i was kidding (sorry, I have a rather weird sense of humor at times )
ROM's based on 3.33 firmware will also work on 3.32 firmware, only difference is a newer radio which some users have reported as having a better signal than the 3.32 radio.
Once the firmware has been flashed once, it doesnt need to be flashed again and if you want to go back to 3.32 firmware after flashing 3.33 firmware, all you need to do is flash 3.32 firmware.
And yeah, the text will change from Revolutionary to LOCKED but you will stay S-OFF
i had hboot 1.14 and couldnt flash an older radio for a MIUI.US aosp ROM (2.8.10)
i used the hboot downgrade tutorial and flashed the older TMOUS radios but none of them let me connect to wifi
how do i get wifi to work on this rom?
get EU RUU version u can try with latest than install custom rom
Recently went back to stock 1.78 (from cm9) to try and get the latest OTA update, but it only gives me the 4.0.4 update.
Im currently on radio 0.16 but want to get the latest radio (1.11?) before putting a JB rom on.
Its been ages since ive done much with my phone since i was happy with cm9 but ive managed to get supercid and s-off so far. Now I understand the process to flash the radio, but I dont know where to find the latest radio. Can you simply take the radio.zip out of the latest OTA thats linked around here somewhere or is there more to it?
Hope that makes sense,
Thankyou.
On 1.06 or s-off this way. You should use TWRP recovery so.
The thing you'll see is called aroma installer. Just tag the radio you want and it'll be flashed. There is a sense and an AOSP/AOKP version of that installer.
There isn't a collection of radio's somewhere that you can permanently flash? Thought it'd be quite easy now with s-off.
The sense stuff will be written permanently to a partition on the phone.
The AOKP/AOSP radio will be flashed to a folder, as e.g. CM 10/10.1 and derivates load it from a folder. The radio needs to be reflashed only when flashing a new AOKP/AOSP rom (as that folder gets deleted). So it's 'temporarily'.
The aroma installer imho is the easiest way to flash a new/different radio. No need to carry around a machine with you to fastboot flash.
What's the most compatible radio version for Jelly Bean Sense ROMs?
I'm running TrickDroid 9.1.0 right now, since it was the only one that worked well with my HBOOT (1.14.0004) / Radio (1.08ts.50.02.16), but the wifi and GPS don't work.
meleniumshane90 said:
What's the most compatible radio version for Jelly Bean Sense ROMs?
I'm running TrickDroid 9.1.0 right now, since it was the only one that worked well with my HBOOT (1.14.0004) / Radio (1.08ts.50.02.16), but the wifi and GPS don't work.
Click to expand...
Click to collapse
Should be the 1.11 EU. But latest TMUS 1.13 is fine so.
rootrider said:
Should be the 1.11 EU. But latest TMUS 1.13 is fine so.
Click to expand...
Click to collapse
I'm going to have to look up how to update the radio. Hopefully that will fix the Wifi glitch on my current ROM. I'd like to do a bit of tethering next week.
I currently don't have any major issues with the phone, but I noticed a lot of people with either Hboot 2.14 and 2.15 while I'm on Hboot 1.09. I bought this phone at release, always stuck with CleanROM, and now currently on CleanROM 7.0 P1. Is there a good reason why I should run the AT&T 3.18 RUU to update my Hboot to 2.14, or can I just stick with 1.09? If performance and stability can be improved by upgrading, I can be persuaded.
Thanks. Details are below:
EVITA S-OFF
CID - 11111111
HBOOT - 1.09.0000
RADIO - 1.31a.32.45.16_2
Basically it goes like this:
The 2.14 firmware is required to flash any current aosp ROM. If you don't have that firmware installed the ROM simply won't install.
The 2.15 firmware is required on any Sense 5 ROM to stop signal loss and reboot issues. These issues can also be avoided by flashing the Beastmode kernel.
Note how I referred to it as firmware and not hboot. There is a common misconception that it is just the hboot that is required, this is false. It is the firmware package as a whole that's required, of which the hboot is just one component of. I think the reason people make this mistake is because the firmware is referred to by the hboot number (1.09, 1.14, 2.14, 2.15).
Sent from my Evita
The radio number listed in the OP is for the Sense 5 radio. So the OP must have flashed that radio separately from the 2.15 firmware package at some point, if they are on hboot 1.09 and have always been so.
If no signal drops of random reboots are experienced, there isn't a reason to update to the 2.15 hboot and associated firmware. Either you are in the population that simply does not experience that problem, or having the 1.31 radio has already resolved it. It has been suspected that the radio is the main culprit, but I don't think it was ever confirmed that flashing the Sense 5 radio (1.31) alone without the other 2.15 firmware solves the issue.
redpoint73 said:
The radio number listed in the OP is for the Sense 5 radio. So the OP must have flashed that radio separately from the 2.15 firmware package at some point, if they are on hboot 1.09 and have always been so.
If no signal drops of random reboots are experienced, there isn't a reason to update to the 2.15 hboot and associated firmware. Either you are in the population that simply does not experience that problem, or having the 1.31 radio has already resolved it. It has been suspected that the radio is the main culprit, but I don't think it was ever confirmed that flashing the Sense 5 radio (1.31) alone without the other 2.15 firmware solves the issue.
Click to expand...
Click to collapse
You are correct, I did have to flash the radio separately using carl1961's firmware in his Sense 5 ROM (along with the wifi and DSP img). Sure enough, this fixed all issues I had with the radio. I guess in my situation, I didn't have to update the hboot.
timmaaa said:
Basically it goes like this:
The 2.14 firmware is required to flash any current aosp ROM. If you don't have that firmware installed the ROM simply won't install.
The 2.15 firmware is required on any Sense 5 ROM to stop signal loss and reboot issues. These issues can also be avoided by flashing the Beastmode kernel.
Note how I referred to it as firmware and not hboot. There is a common misconception that it is just the hboot that is required, this is false. It is the firmware package as a whole that's required, of which the hboot is just one component of. I think the reason people make this mistake is because the firmware is referred to by the hboot number (1.09, 1.14, 2.14, 2.15).
Sent from my Evita
Click to expand...
Click to collapse
I think I understand your explanation when I make it analogous to PC terms: hboot is more like the BIOS, firmwares are packages that include the BIOS and drivers (radio, wifi, etc.), and the HTC RUU is a stock image that includes the BIOS, operating system, and drivers. That would explain why I was able to update the radio and wifi without touching my hboot. Please correct me if I'm wrong.
Thanks for both your explanations, looks like I'll stick with 1.09 for the indefinite future.
Yes your analogy is spot on.
Sent from my Evita