Database Info

[Radio] 2.05.00.06.10 WiMax update

This is meant for 1.47.651.1 ROMs ONLY!
This is not the full radio but this will update the WiMax, recovery & kernel(same as in the OTA 1.47.651.1 zip).
Flash this through the bootloader like you would Toast's PC36IMG.zip(Power off, then Vol Down & Power button).
This will overwrite what ever recovery console you have, so once it's booted, replace the recovery console to what you were using before.
Also, this will not change the baseband version but it will update WiMax, so that's a start
EDIT: Full radio has been released, so removing this update

On a roll, dude. Donation is imminent.

I'm still not able to connect to 4g after appyling this update.

Looks promising.
I don't have 4G coverage here, but I flashed this radio upgrade against your rooted OTA Update ROM as a test.
I can confirm that nothing breaks =)
I was able to, without any problem, reflash the recovery I was using.
I can't wait for a full release that completely upgrades the radio!

and we will keep current rom settings and root with this?

Yes, your data & ROM are untouched as this only updates WiMax, recovery console & kernel

So, i understand this is not the full radio update..
But it WAS a full update with the OTA's that were sent out today right? I dont quit know what a radio.diff is (i think thats what they called it)

Excuse me for being a noob but does this mean that I will have do redo nand protection after I use this radio update? I did your update to OTA 1.47.651.1 without any problems. Thanks

mayfly82 said:
Excuse me for being a noob but does this mean that I will have do redo nand protection after I use this radio update? I did your update to OTA 1.47.651.1 without any problems. Thanks
Click to expand...
Click to collapse
no, you'll be fine doing this.

A 'diff' would be an update that only contains lines of code that changed from the original. This gives us a smaller payload making it less burdensome on the network for OverTheAir updates.

Touch censors are non responsive when flashing over Avalaunch's Froyo ROM via bootloader. Gonna have to flash Amon Ra's recovery via ADB. Also, the radio still shows up as version 1.39.00.05.31 is this expected? Thanks in advance.

c0mputerp0et said:
A 'diff' would be an update that only contains lines of code that changed from the original. This gives us a smaller payload making it less burdensome on the network for OverTheAir updates.
Click to expand...
Click to collapse
Nice! Thanks!!!
neckface said:
Touch censors are non responsive when flashing over Avalaunch's Froyo ROM via bootloader. Gonna have to flash Amon Ra's recovery via ADB. Also, the radio still shows up as version 1.39.00.05.31 is this expected? Thanks in advance.
Click to expand...
Click to collapse
"This is meant for 1.47.651.1 ROMs ONLY!" from the OP. Could be the issue. not sure if Avalaunch's has been updated yet.??

What exactly is meant by this line in the op?
"This will overwrite what ever recovery console you have, so once it's booted, replace the recovery console to what you were using before."
Details for a noob?
Really hope this update helps my 4G connection, otherwise I gotta return this phone ina few days

frettfreak said:
Nice! Thanks!!!
"This is meant for 1.47.651.1 ROMs ONLY!" from the OP. Could be the issue. not sure if Avalaunch's has been updated yet.??
Click to expand...
Click to collapse
Lawl Guess I neglected to notice that in my haste. I'll switch ROM's in a bit and give her a whirl again. Thanks.
EDIT: Got everything working again, flashed your OTA ROM and followed through with the radio. Sweet deal, man. Kudos again!

neckface said:
Lawl Guess I neglected to notice that in my haste. I'll switch ROM's in a bit and give her a whirl again. Thanks.
Click to expand...
Click to collapse
Coulda been an edit after the OP.. who knows.. and no prob man!! good luck!

frettfreak said:
Coulda been an edit after the OP.. who knows.. and no prob man!! good luck!
Click to expand...
Click to collapse
Nah, I saw what I wanted to see, or didn't, rather. Lol Everything's workin' now.

I know that this does not work... I tested it but maybe someone smarter can build off of it... In theory it should work but it doesn't on my phone... The file that it complains about is there maybe I just have the syntax wrong. Calkulin Please get this working.

Is there a reason we can't stick the radio diff into a PC36IMG.ZIP and upgrade via the bootloader as well?

I flashed this update over your release of today's update and 4G will start but will not connect. Any ideas of what I may have done wrong?

holob said:
Is there a reason we can't stick the radio diff into a PC36IMG.ZIP and upgrade via the bootloader as well?
Click to expand...
Click to collapse
we could try it... (you first) not saying that it will do anything bad but I have no idea.

Help! Wrong radio

Alright, so I've had an htc sensation running on leedroid 3.10 for quite some time now. Recently it started to restart randomly, so I decided to upgrade my rom. So then I attempted to install insertcoin ICS, but I needed a new radio. So I chose one figuring it would work and now my device doesn't connect to internet or even my data. Whenever I try to install a different radio now to attampt fixing it, it says I have the wrong CID! I NEED my phone to work soon because i have a lot of important things to do that involve it!! Thanks for all help and please respond soon! FYI it says my radio is 10.11.9007.06_M2. Should I maybe reflash the hboot?
EDIT: And in case you're wondering, I've been searching for the solution for hours. I've never been more afraid of anything not working than this phone, and I can't afford a new phone, so please help!

BUMP! Please help I can't sleep because of this

Flash back to stock, do a little research and find the radio version that came with your phone. Flash it.
A lot of times, I've found, the problem with these new unofficial ports of ICS is that the radio doesn't work on them. So go back to stock radio and find a stable ROM to work with.

Jesushaxyou said:
Flash back to stock, do a little research and find the radio version that came with your phone. Flash it.
A lot of times, I've found, the problem with these new unofficial ports of ICS is that the radio doesn't work on them. So go back to stock radio and find a stable ROM to work with.
Click to expand...
Click to collapse
Thanks! My only problem is, how do I know which radio came stock? Do all sensations come stock with the same radio?

Which version of the sensation do you have? XL? XE?

Jesushaxyou said:
Which version of the sensation do you have? XL? XE?
Click to expand...
Click to collapse
Just the Sensation 4g, not the XE or XL

Here you go.
http://forum.xda-developers.com/showthread.php?t=1178143
I believe you should download the 10.58.9035.00U_10.15.9035.02_2 version.

Jesushaxyou said:
Here you go.
http://forum.xda-developers.com/showthread.php?t=1178143
I believe you should download the 10.58.9035.00U_10.15.9035.02_2 version.
Click to expand...
Click to collapse
Thank you, but the same problem persists. I'm not sure what could even be the cause of this problem though. My exact step are to boot by holding vol down and power (im not sure what its called), and then it automatically attempts to install it, but then I get that error message. Afterward I attempted to install it by going to recovery and opening it as a zip file, and that failed just the same.

Jesushaxyou said:
Here you go.
http://forum.xda-developers.com/showthread.php?t=1178143
I believe you should download the 10.58.9035.00U_10.15.9035.02_2 version.
Click to expand...
Click to collapse
also is there anyway to install the radio while installing the stock firmware? Why can't you back up the radio anyway? And hwile I'm at it, what does CID even have to do with radio that it would cause these problems? Will location matter? I'm in NJ US.

As far I know you can't dual flash the radio and OS. Also, I think you'll be ok in NJ with a stock radio. Just as fine as you were before all this.

[Q] Differences between hboots 1.06, 1.09, 1.13, and 1.14?

So I successfully downgraded from hboot 1.14 to 1.06, and used the TMOUS 1.53 RUU to restore it, but now I am curious as to what the major differences and incompatibilities each hboot has. Since I was on 1.14 I understand that that one had more restrictions and broke wi-fi on some roms. Which hboot would be "best" for 3rd arty roms and overall usage? I'm asking this partly because even with hboot 1.06 wi-fi was still too buggy for use on CM10.

byliu88 said:
So I successfully downgraded from hboot 1.14 to 1.06, and used the TMOUS 1.53 RUU to restore it, but now I am curious as to what the major differences and incompatibilities each hboot has. Since I was on 1.14 I understand that that one had more restrictions and broke wi-fi on some roms. Which hboot would be "best" for 3rd arty roms and overall usage? I'm asking this partly because even with hboot 1.06 wi-fi was still too buggy for use on CM10.
Click to expand...
Click to collapse
1.06, flash the new radio seperately once your on 1.06.

usaff22 said:
1.06, flash the new radio seperately once your on 1.06.
Click to expand...
Click to collapse
Thanks for the info, which radio is that though?

<here you go mate, http://d-h.st/XBu it was posted on this forum by torx, i think , it's a flashebel zip. with aroma installer so just folow the instructions

alexskin said:
<here you go mate, http://d-h.st/XBu it was posted on this forum by torx, i think , it's a flashebel zip. with aroma installer so just folow the instructions
Click to expand...
Click to collapse
Alright I'll try it out. thanks!

byliu88 said:
So I successfully downgraded from hboot 1.14 to 1.06, and used the TMOUS 1.53 RUU to restore it, but now I am curious as to what the major differences and incompatibilities each hboot has. Since I was on 1.14 I understand that that one had more restrictions and broke wi-fi on some roms. Which hboot would be "best" for 3rd arty roms and overall usage? I'm asking this partly because even with hboot 1.06 wi-fi was still too buggy for use on CM10.
Click to expand...
Click to collapse
I wonder if you could please explain how you were able to downgrade. I heat tons of conflicting info on this.
Thanks in advance.

HD Case said:
I wonder if you could please explain how you were able to downgrade. I heat tons of conflicting info on this.
Thanks in advance.
Click to expand...
Click to collapse
He probably used the instructions in the development section:
http://forum.xda-developers.com/showthread.php?t=1990043

Kamilr97 said:
He probably used the instructions in the development section:
http://forum.xda-developers.com/showthread.php?t=1990043
Click to expand...
Click to collapse
Thanks,
Yikes! Now I see why a lot of people don't even attempt this

I have also downgrade my hboot back to 1.06 and my wifi is also buggy i hope there is a solution for
Maybe i must go back to stock but i dont know if my wifi then is fix

fjjfrank said:
I have also downgrade my hboot back to 1.06 and my wifi is also buggy i hope there is a solution for
Maybe i must go back to stock but i dont know if my wifi then is fix
Click to expand...
Click to collapse
I downgraded from 1.14 to 1.06 too, installed 1.53 RUU and then experienced wifi issues on Trickdroid 8.
I had to flash "extra partitions" to make it work. Seems to be some partitions required for wifi to work on versions based on latest sense kernels.
I flashed extra partitions 2.35 and wifi did not work. Then I flashed 1.84 and wifi on Trickdroid 8 would connect, but from time to time (very frequently every 15 seconds on average) disconnect and reconnect, randomly (was annoying and killing my battery). I moved to trickdroid 7 TMOUS version and wifi works perfectly, never disconnects.
(My phone was from T-Mobile)
Here are the links, taken from this post: http://forum.xda-developers.com/showthread.php?t=1657831&page=271
2.35 Extra Partitions
https://www.dropbox.com/s/7gtuvbynr3...rtitions.zip?m
1.84 Extra Partitions
https://www.dropbox.com/s/mmjcqisgoo...rtitions.zip?m
NOTE: On CM rom I never had issues even without flashing extra partitions, and even when I was on hboot 1.14.
Hope this helps,
Regards,
Diego
---------- Post added at 07:57 PM ---------- Previous post was at 07:51 PM ----------
And regarding the topic from this post, hboot is like the BIOS of the phone. You gain nothing from upgrading it, only gain restrictions from 1.13 and above. So as far as I read it is better to stick to 1.06
Regarding the procedure to downgrade, for the one that asked, it can make you panic on the step when you upload hboot 1.06. For me, it failed 3 times, and I had to go to work after third time with a "bricked" phone -.-
But I came back, tried from my laptop instead of my PC, and worked on the first attemp!. Seemed to be my PC USB not working properly or not being fast enough/not having enough power, who knows.
It seems scary but is fairly straight through, the procedure is perfectly detailed. Did it from an Ubuntu 12.04 live image.
Regards,
Diego

HD Case said:
I wonder if you could please explain how you were able to downgrade. I heat tons of conflicting info on this.
Thanks in advance.
Click to expand...
Click to collapse
Yes, I used the guide Kamilr mentioned. It was fairly nerve wracking but if you carefully read all of the instructions and get an idea of what your doing it goes pretty smoothly. Same with sperad, flashing the hboot itself failed for me 3 times, but all you had to do was reboot and retry. But anyways regarding the wifi issue. flashing the new radio did not seem to alleviate anything, but I flashed viperOneS and wifi now works fine, so I plan to stay with it.
@fjjfrank Try relocking your bootloader, then running your RUU http://d-h.st/users/agentc13/?fld_id=2293#files (if you're on tmobile its 1.53, im not sure about the other networks), which'll bring you back to stock. Wi-Fi worked perfectly on stock when I tried that after downgrading to 1.06. If its good from there you can try what i did and unlock your bootloader again and flash viperOneS which worked for me.

byliu88 said:
Yes, I used the guide Kamilr mentioned. It was fairly nerve wracking but if you carefully read all of the instructions and get an idea of what your doing it goes pretty smoothly. Same with sperad, flashing the hboot itself failed for me 3 times, but all you had to do was reboot and retry. But anyways regarding the wifi issue. flashing the new radio did not seem to alleviate anything, but I flashed viperOneS and wifi now works fine, so I plan to stay with it.
@fjjfrank Try relocking your bootloader, then running your RUU http://d-h.st/users/agentc13/?fld_id=2293#files (if you're on tmobile its 1.53, im not sure about the other networks), which'll bring you back to stock. Wi-Fi worked perfectly on stock when I tried that after downgrading to 1.06. If its good from there you can try what i did and unlock your bootloader again and flash viperOneS which worked for me.
Click to expand...
Click to collapse
oke thanks
i am from the netherlands and i have got a unbranded one s
witch hboot can i install without updating my bootloader

[Q] Stupid upgrading existing root question [ANSWERED]

Hi,
I want to flash an AT&T One X to some of the latest jelly bean ROMs (MIUI in particular). The phone is currently rooted with the old firmware. I've read all the guides and I'm unclear as to how to upgrade the firmware on existing root.
Since its currently rooted, do I just flash one of the new ROMs and I'm updated to new firmware?
Or do I do RUU first to new firmware and re-root? (Do I use the original bin file from first root?) If so, is there a guide for this around?
Thanks for the help

Is your bootloader unlocked, and do you have TWRP installed?
If so, flashing JB is like flashing any other ROM (no need to RUU, and no benefit at all to do so). Just move the ROM to the phone's SD card, then flash from recovery. If on hboot 1.14, you will need to extract boot.img from the ROM zip, and flash with fastboot.
This will likely answer many of your questions: http://forum.xda-developers.com/showthread.php?t=1952076
Also, its customary (and useful) to have some information about the question you are asking in your thread title, not just [Q].

Sputnikk23 said:
Hi,
I want to flash an AT&T One X to some of the latest jelly bean ROMs (MIUI in particular). The phone is currently rooted with the old firmware. I've read all the guides and I'm unclear as to how to upgrade the firmware on existing root.
Since its currently rooted, do I just flash one of the new ROMs and I'm updated to new firmware?
Or do I do RUU first to new firmware and re-root? (Do I use the original bin file from first root?) If so, is there a guide for this around?
Thanks for the help
Click to expand...
Click to collapse
Just flash the new rom. You wouldn't want to update your firmware because then you would have to flash the boot.img seperately in fastboot, and you would n't be able to flash radios, or boot animations at all. In fact many people have downgraded their firmware to the old version because of these annoyances.

redpoint73 said:
Is your bootloader unlocked, and do you have TWRP installed?
Click to expand...
Click to collapse
yes bootloader is unlocked and TWRP installed
If so, just move the ROM to the phone's SD card, then flash from recovery. If on hboot 1.14, you will need to extract boot.img from the ROM zip, and flash with fastboot.
Click to expand...
Click to collapse
and that would update the phones firmware to 2.20 but still have hboot 1.14 - which I understand is the preferred version? The RADIO thread says you can't flash radios unless on CM10 with the newer hboot. I'd like to update the phone to the latest and greatest radio too, I'd be safe doing that then?
Also, its customary (and useful) to have some information about the question you are asking in your thread title, not just [Q].
Click to expand...
Click to collapse
Total duh moment...
Edit: crap. can't find a way to edit title. sorry. thanks for answering.

Sputnikk23 said:
and that would update the phones firmware to 2.20 but still have hboot 1.14 - which I understand is the preferred version? The RADIO thread says you can't flash radios unless on CM10 with the newer hboot. I'd like to update the phone to the latest and greatest radio too, I'd be safe doing that then?
Click to expand...
Click to collapse
Firmware and ROM are the same thing. Once you flash a ROM, it formats the system partition and installs the new ROM/firmware. The old firmware is wiped, and new one installed.
Firmware number reported in Settings is somewhat irrelevant when you flash a custom ROM. It will say whatever the dev makes it say, such as MIUI 2.12 etc. The custom ROM might be based on an official firmware number (such as JB 3.17) but its been modded by the dev, so its not really the same firmware anymore. The ROM thread will tell you what firmware version its based on. If you want JB, its going to be based on fimrware 3.xx.
Installing custom ROMs does not touch hboot. The only way to downgrade hboot is with the JET kit in the Development forum, which requires a Linux computer.

redpoint73 said:
Firmware and ROM are the same thing. Once you flash a ROM, it formats the system partition and installs the new ROM/firmware. Firmware number is irrelevant when you flash a custom ROM. It will say whatever the dev makes it say, such as MIUI 2.12 etc. It might be based on an official firmware number (such as JB 3.17) but its been modded by the dev, so its not really the same firmware.
Installing custom ROMs does not touch hboot. The only way to downgrade hboot is with the JET kit in the Development forum, which requires a Linux computer.
Click to expand...
Click to collapse
OK got the first part.
Bootloader says unlocked and hboot 1.09. So I'm good to go download the latest radio I think.
I'm having trouble identifying which latest radio to update to for an AT&T phone in the US.

Sputnikk23 said:
OK got the first part.
Bootloader says unlocked and hboot 1.09. So I'm good to go download the latest radio I think.
I'm having trouble identifying which latest radio to update to for an AT&T phone in the US.
Click to expand...
Click to collapse
Yes, you are good to flash radios with hboot 1.09.
The latest radio from AT&T is the one that was released with firmware 2.20. See the radio thread, if you haven't already: http://forum.xda-developers.com/showthread.php?t=1694012
Keeping in mind the latest radio will not always yield the best results. Radio reception is most often linked to your exact geographic location, and is often a matter of trial and error. But I think many people had some decent battery life improvement with the 2.20 radio. You are also free to try radios 2.29, 2.40 etc. The fact that they were released for other carriers in other countries is irrelevant. They may still yield reception improvements, or not. As mentioned, radio flashing is pretty much trial and error. The latest is not necessarily the greatest.

redpoint73 said:
Yes, you are good to flash radios with hboot 1.09.
The latest radio from AT&T is the one that was released with firmware 2.20. See the radio thread, if you haven't already: http://forum.xda-developers.com/showthread.php?t=1694012
Keeping in mind the latest radio will not always yield the best results. Radio reception is most often linked to your exact geographic location, and is often a matter of trial and error. But I think many people had some decent battery life improvement with the 2.20 radio. You are also free to try radios 2.29, 2.40 etc. The fact that they were released for other carriers in other countries is irrelevant. They may still yield reception improvements, or not. As mentioned, radio flashing is pretty much trial and error. The latest is not necessarily the greatest.
Click to expand...
Click to collapse
Cool. THank you. Very helpful. About to flash. TWRP is ver 2.2. Any significant reason to upgrade to 2.3?

Sputnikk23 said:
Cool. THank you. Very helpful. About to flash. TWRP is ver 2.2. Any significant reason to upgrade to 2.3?
Click to expand...
Click to collapse
Keeping recovery up-to-date is usually a good idea.
Please be sure to click the "Thanks" button for posts that helped you.
Also, you can edit the thread title at any time. Click "Edit" then click "Go Advanced" to edit the title.
---------- Post added at 12:56 PM ---------- Previous post was at 12:52 PM ----------
Ha, love the new thread title!

redpoint73 said:
Keeping recovery up-to-date is usually a good idea.
Please be sure to click the "Thanks" button for posts that helped you.
Also, you can edit the thread title at any time. Click "Edit" then click "Go Advanced" to edit the title.
---------- Post added at 12:56 PM ---------- Previous post was at 12:52 PM ----------
Ha, love the new thread title!
Click to expand...
Click to collapse
Hmm.. all is well except the phone died while playing with it and now won't charge via a PC USB cable? No charge light at all.

After you flashed a rom or before? If it completely died it'll take 5 or so minutes before the light comes on and able to boot up once its on the charger.
By all means I mean no disrespect and I'm not questioning your intelligence, but make sure your computer is on while you are charging via USB. I forget about that sometimes
Sent from my One X using Tapatalk 2

Also, use the wall charger, not USB, when something like this happens. The wall charger charges much faster (more amps?) than USB, by far. Leave it on the wall charger for several hours, then see if the charge light comes on, or if you can boot.
This has randomly happened to some people, and leaving the phone on the wall charger for a few hours usually does the trick.

yup it came back after a couple minutes. thanks again.

Radio Trouble

I'm on 2.16 S-Off and SuperCID...
I tried to go back to 2.15 and it seems to have killed my radio. It doesn't hold either a cell signal or a wifi signal, tried multilple radio flashes (1.15, 1.2) with no luck. It connects for a few seconds, then drops even mid call.
I think it's software related because all was well until I decided to go back to hboot 2.15
If anyone can help I'd greatly appreciate it...

What method of flashing did you use exactly?

Dooxed said:
What method of flashing did you use exactly?
Click to expand...
Click to collapse
For the radios I used the sense radio installer v6.
To go back to 2.15, I used a Rogers RUU, then updated to JB

myqj said:
For the radios I used the sense radio installer v6.
To go back to 2.15, I used a Rogers RUU, then updated to JB
Click to expand...
Click to collapse
Have you removed the sim card reboot and reinsert sim card?

tivofool said:
Have you removed the sim card reboot and reinsert sim card?
Click to expand...
Click to collapse
Yup, tried all that, tried going back to stock, tried different radios in stock, tried CM all without luck.
I'm starting to think it may be hardware...

Edit: Hmm, maybe I should read your reply first.. Already tried going back to stock.. then I don't know!
Is the top cap of your One S properly connected? Maybe clean the contacts a bit? All antennas except the WiFis are located at the top.
-----------------
When I was stuck on hboot 2.16 after playing around with some ROMs (I am not sure, but I blame Maximus HD 10) I installed the ICS RUU for Europe, file RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe to be exact.
This took me back to hboot 1.14 (or so), including the old radio / recovery / etc. :good:
If you want to try this, make sure adb or fastboot is working on your PC and connect the phone by USB.
I got the file here (AndroidRUU). If you are in the US or somewhere else another RUU might be better for you.