Database Info

[RADIO] HTC Desire HD Radios [PD98IMG.zip] (Updated: 7 Sept 2011)

Code:
/* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or the end of the world. Please do some research
* if you have any concerns about flashing a radio before flashing it!
* YOU are choosing to make these modifications, and if you point the
* finger at me for messing up your device, I will laugh at you. */
How to Flash:
In order for this to work, the HTC Desire HD needs to be S-OFF. Flashing the radio with a corrupt file or interrupting the flash, can brick the device, please proceed with caution.
Download the your choice of radio for the HTC Desire HD.
Make sure the filename is PD98IMG.zip exactly or it will not work and copy it to the same folder as adb (the /platform-tools folder within the Android SDK folder).
Connect the HTC Desire HD to the computer via USB.
On the computer, open terminal and run the following commands:
Code:
adb push PD98IMG.zip /sdcard/PD98IMG.zip
adb shell md5sum /sdcard/PD98IMG.zip
NOTE: The md5 should match up the provide the original download location. If not, redownload & try again.
Code:
adb reboot bootloader
The HTC Desire HD will reboot & usually boot into fastboot. Pressing the Power button will put the device into the bootloader.
The bootloader will scan for the radio update. Once it finds the update, select Yes.
Allow the bootloader to finish flashing the updated radio, and reboot the HTC Desire HD normally.
Downloads:
From Froyo-based RUUs:
From the 1.15.405.1 RUU:
12.21.60.12_26.02.00.09
md5: 4aba7abfbeb93cd7c0061eb9eb706d97
From the 1.24.405.1 RUU:
has the same radio as the 1.15.405.1 RUU
From the 1.28.405.1 RUU:
12.28.60.140e_26.03.00.04
md5: 3ad11deb26f4b39186dce334d606c130
From the 1.28.405.1_R2 RUU:
12.28a.60.140e_26.03.02.08
md5: 4cf186ce53723a5185fe21e76d82dd38
From the 1.31.207.1 RUU:
12.28b.60.140e_26.03.02.26
md5: f01f7a2b264811636c470c7b530fece9
From the 1.31.1400.1 RUU:
has the same radio as the 1.28.405.1_R2 RUU
From the 1.32.207.1 RUU:
has the same radio as the 1.28.405.1_R2 RUU
From the 1.32.405.3 RUU:
12.28b.60.140e_26.03.02.15
md5: 2e1759eb2308a5ec0910122be9d6b5f0
From the 1.32.405.6 OTA/RUU:
has the same radio as the 1.31.207.1 RUU
From the 1.32.707.1 RUU:
has the same radio as the 1.28.405.1_R2 RUU
From the 1.32.832.6 RUU:
has the same radio as the 1.31.207.1 RUU
From the 1.39.111.1 RUU:
has the same radio as the 1.31.207.1 RUU
From the 1.40.61.2 RUU:
has the same radio as the 1.31.207.1 RUU
From the 1.43.466.2 RUU:
has the same radio as the 1.31.207.1 RUU
From the 1.43.1010.2 RUU:
has the same radio as the 1.31.207.1 RUU
From the 1.60.1400.7 RUU:
12.32.60.140e_26.04.00.05
md5: f6f0f08af1b4afa0ce883041cad736b0
From the 1.72.405.3_R RUU:
12.28e.60.140f_26.04.02.17
md5: 14b8dacee267c9598107339c6001275d
From the 1.72.405.3_R2 OTA/RUU:
has the same radio as the 1.72.405.3_R RUU
From the 1.75.75.2 RUU:
has the same radio as the 1.72.405.3_R RUU
From the 1.75.110.2_R RUU:
has the same radio as the 1.72.405.3_R RUU
From the 1.75.771.2 RUU:
12.28g.60.140f_26.05.02.15
md5: 24ad1d0f9fb48dbd8cdefe4ac4af48ed
From the 1.75.1400.4 RUU:
12.35a.60.140f_26.04.03.30
md5: faf2e82e101907f8587d041b1301a5ed
From the 1.80.502.3 RUU (AT&T Inspire 4G Stock):
12.39.60.19_26.06.04.06
md5: dea534848a9b71fc54878c0111ceed76
From the 1.83.415.4 RUU:
has the same radio as the 1.72.405.3_R RUU
From the 1.84.61.2 RUU:
12.28g.60.140f_26.05.05.27
md5: c7eea236eaaa2edf978934633d58398d
From the 1.84.502.11 RUU:
12.39a.60.19_26.06.06.30
md5: 991dc7acd70fa13d47ca6d0a4b6f857f
From the 1.84.661.1_R RUU:
12.35d.60.140f_26.06.03.24
md5: 64bb83fda93052fcc8c1423b7a433e77
From the 1.84.832.2 RUU:
has the same radio as the 1.84.61.2 RUU
From the 1.89.516.2_R RUU:
has the same radio as the 1.84.61.2 RUU
From Gingerbread-based RUUs:
From the 2.16.0.0 RUU:
12.41.60.19_26.06.04.14
md5: f964b25bda91dd377c78b54ce46fdd7b
From the 2.25.0.0 RUU:
12.35d.60.140f_26.08.03.07
md5: 2cf70fce7c649822bc67a719b0a68d46
From the 2.25.1400.1 RUU:
has the same radio as the 2.25.0.0 RUU
From the 2.31.1400.1 RUU:
has the same radio as the 2.25.0.0 RUU
From the 2.36.405.5 RUU:
12.54.60.25_26.09.04.11
md5: 167130dc3853eae382526fbf5b2a9070
From the 2.36.405.8_R RUU:
has the same radio as the 2.36.405.5 RUU
From the 2.37.707.3 RUU:
has the same radio as the 2.36.405.5 RUU
From the 2.37.762.2 RUU:
has the same radio as the 2.36.405.5 RUU
From the 2.37.832.6 RUU:
has the same radio as the 2.36.405.5 RUU
From the 2.42.415.1 RUU:
has the same radio as the 2.36.405.5 RUU
From the 2.43.661.1 OTA/RUU:
12.56.60.25_26.10.04.03
md5: 73fc5a09b44b4c4367ea75a231ce0818
From the 2.47.502.7 RUU:
has the same radio as the 2.43.661.1 OTA/RUU
From the 2.50.405.2 RUU:
has the same radio as the 2.36.405.5 RUU
From the 2.50.771.2 RUU:
12.56.60.25_26.09.04.28
md5: c760c92ab29ba60249250db0ae71e788
From the 2.52.1010.2 RUU:
12.59.60.26_26.11.04.21
md5: b5062872cf6f2898d74e9f6a0dbb9664
From the 3.06.405.1 RUU:
12.62.60.27_26.13.04.19
md5: 7e3f9b9381209e7643e7e94ea7028ad0

Where is my radio and what is the latest one that u have???
Have anyone test it???

eliashadow said:
Where is my radio and what is the latest one that u have???
Have anyone test it???
Click to expand...
Click to collapse
The 26.08.04.07 radio is not available from a reliable source. And the radio are listed in release order, from oldest to newest. The RUU the 26.09.04.11 radio came from just leaked 4 hours ago.

Beware the Typo:
Code:
adb shell md5sum /sdcard/PD98MG.zip
Nice work

schauol1 said:
Beware the Typo:
Code:
adb shell md5sum /sdcard/PD98MG.zip
Nice work
Click to expand...
Click to collapse
Fix'd, thanks for pointing that out.

rils for Radio 12.54.60.25_26.09.04.11_M2 is include

doudou1206 said:
rils for Radio 12.54.60.25_26.09.04.11_M2 is include
Click to expand...
Click to collapse
No, these are just radios.

you can also just reboot into bootloader and flash. It worked perfect.

klquicksall said:
you can also just reboot into bootloader and flash. It worked perfect.
Click to expand...
Click to collapse
But transferring without verifying the md5sums can cause people to flash corrupted files, which will most likely brick the device.

gu1dry said:
But transferring without verifying the md5sums can cause people to flash corrupted files, which will most likely brick the device.
Click to expand...
Click to collapse
Yes that is possible. Flashing any. Radio is dangerous. People just need to use caution. Still better than fastboot.
Sent from my Desire HD using XDA Premium App

I can't see the point in doing this when you can easily download the radio from the radio thread and check the md5 then drop the radio.img in the folder from my thread then follow the guide on my thread
With how you described to do it this way seems a lot of messing about having to rename radio and typing loads of commands when the guide I created is a lot more simple
Could you please explain the benefits of your method???
Sent from Pluto

klquicksall said:
Yes that is possible. Flashing any. Radio is dangerous. People just need to use caution. Still better than fastboot.
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
Not totally true I flashed a radio from htc desire s Rom by accident on to dhd and all it did was sit on splash screen pulled battery and reflashed correct radio no brick. Also its been mentioned that the dhd has a back up radio that kicks in if you flash the wrong one or a corrupted radio( not tested myself).
Sent from Pluto

leith51 said:
I can't see the point in doing this when you can easily download the radio from the radio thread and check the md5 then drop the radio.img in the folder from my thread then follow the guide on my thread
With how you described to do it this way seems a lot of messing about having to rename radio and typing loads of commands when the guide I created is a lot more simple
Could you please explain the benefits of your method???
Sent from Pluto
Click to expand...
Click to collapse
Well, as a Linux user, I haven't managed to make fastboot work... And this method is completely platform independent. For me it's great

swiftscythe said:
Well, as a Linux user, I haven't managed to make fastboot work... And this method is completely platform independent. For me it's great
Click to expand...
Click to collapse
So its good for Linux users and works fine that's good to know will add link with credits to my thread for Linux users my guide will cover all Windows Linux and mac with links to appropriate threads
Sent from Pluto

This is the best, because it is the simplest.
Just download the zip file, put the downloaded zip file in the root of the sdcard, restart to bootloader, choose bootloader, press volume up button when asked.
Finish!
I've been waiting for something like this since the first time I wanted to update my DHD radio image.
Never use my laptop anymore.
Thx bro.

What is the point of this thread?!?!?
There's already one thread that covers the radios roms for the DHD....
shutdown this please...

Thanks for your nice work..

swiftscythe said:
Well, as a Linux user, I haven't managed to make fastboot work... And this method is completely platform independent. For me it's great
Click to expand...
Click to collapse
leith51 said:
So its good for Linux users and works fine that's good to know will add link with credits to my thread for Linux users my guide will cover all Windows Linux and mac with links to appropriate threads
Click to expand...
Click to collapse
Erm, can we re-phrase that to "it's good for those linux users that can't get fastboot to work". As an Ubuntu user I got fastboot to work without problems and prefer the fastboot method. My personal preference maybe but I just don't like the implication of the above wording. Thank you.

Thanks for this gu1dry. Did you also put these on the cyanogenmod wiki?
To the ones wondering what's the point of these PD98IMG radios:
You don't need fastboot. You don't need an ENG s-off HBOOT, only radio S-off.
It's easier and safer.

sonym4n said:
This is the best, because it is the simplest.
Just download the zip file, put the downloaded zip file in the root of the sdcard, restart to bootloader, choose bootloader, press volume up button when asked.
Finish!
I've been waiting for something like this since the first time I wanted to update my DHD radio image.
Never use my laptop anymore.
Thx bro.
Click to expand...
Click to collapse
+1
There is no need for adb anymore, just drop in the sd root and reboot

[RADIO][24 Nov 2011] HTC Sensation Radios [PG58IMG.zip]

Code:
/* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or the end of the world. Please do some research
* if you have any concerns about flashing a radio before flashing it!
* YOU are choosing to make these modifications, and if you point the
* finger at me for messing up your device, I will laugh at you. */
How to Flash:
In order for this to work, the HTC Sensation needs to be S-OFF. Flashing the radio with a corrupt file or interrupting the flash, can brick the device, please proceed with caution.
Download the your choice of radio for the HTC Sensation.
Make sure the filename is PG58IMG.zip exactly or it will not work and copy it to the same folder as adb (the /platform-tools folder within the Android SDK folder).
Connect the HTC Sensation to the computer via USB.
On the computer, open terminal and run the following commands:
Code:
adb push PG58IMG.zip /sdcard/PG58IMG.zip
adb shell md5sum /sdcard/PG58IMG.zip
NOTE: The md5 should match up the provide the original download location. If not, redownload & try again.
Code:
adb reboot bootloader
The HTC Sensation will reboot & usually boot into fastboot. Pressing the Power button will put the device into the bootloader.
The bootloader will scan for the radio update. Once it finds the update, select Yes.
Allow the bootloader to finish flashing the updated radio, and reboot the HTC Sensation normally.
Downloads:
From Gingerbread-based RUUs:
From the 1.23.163.1 RUU:
10.38.9007.00P_10.11.9007.06
md5: 9f4146692616cfd34d4c14412eec304a
From the 1.24.161.1 RUU:
10.39.9007.00P_10.11.9007.09
md5: 071ea37012ddce8df250c68f13a38cbb
From the 1.24.162.1 RUU:
has the same radio as the 1.24.161.1 RUU
From the 1.24.163.1 RUU:
has the same radio as the 1.24.161.1 RUU
From the 1.24.166.1 RUU:
has the same radio as the 1.24.161.1 RUU
From the 1.24.401.1 RUU:
has the same radio as the 1.24.161.1 RUU
From the 1.24.468.1 RUU:
has the same radio as the 1.24.161.1 RUU
From the 1.24.911.1 RUU:
has the same radio as the 1.24.161.1 RUU
From the 1.27.161.1 RUU:
10.42.9007.00P_10.11.9007.15
md5: 6e37fb179d2e7b765c1c9b4d5149f983
From the 1.27.168.5 RUU:
has the same radio as the 1.27.161.1 RUU
From the 1.27.187.5 RUU:
has the same radio as the 1.27.161.1 RUU
From the 1.27.401.3 RUU:
has the same radio as the 1.27.161.1 RUU
From the 1.27.531.2 RUU:
has the same radio as the 1.27.161.1 RUU
From the 1.28.707.2 RUU:
10.43.9007.00P_10.11.9007.19
md5: 13a111f7e9b7f5d59d119c75c7fb9627
From the 1.28.708.2 RUU:
has the same radio as the 1.28.707.2 RUU
From the 1.28.709.3 RUU:
has the same radio as the 1.28.707.2 RUU
From the 1.28.720.2 RUU:
has the same radio as the 1.28.707.2 RUU
From the 1.29.531.2 RUU:
has the same radio as the 1.27.161.1 RUU
From the 1.34.206.1 RUU:
10.43a.9007.00U_10.51.9007.27
md5: 81b96fd9db9d37965a698dc02e8a945b
From the 1.34.771.1_R RUU:
has the same radio as the 1.34.206.1 RUU
From the 1.34.841.6 RUU:
has the same radio as the 1.34.206.1 RUU
From the 1.35.61.1 RUU:
has the same radio as the 1.34.206.1 RUU
From the 1.35.75.1 RUU:
has the same radio as the 1.34.206.1 RUU
From the 1.35.401.1 RUU:
has the same radio as the 1.34.206.1 RUU
From the 1.35.666.1 RUU:
10.50.9007.00U_10.12.9007.21_2
md5: 3c2e34200c3a1d78dddc261bd32be850
From the 1.35.707.1 RUU:
has the same radio as the 1.34.206.1 RUU
From the 1.35.708.1 RUU:
has the same radio as the 1.34.206.1 RUU
From the 1.35.709.1 RUU:
has the same radio as the 1.34.206.1 RUU
From the 1.45.401.2 OTA/RUU:
10.56.9035.00U_10.14.9035.01
md5: 64a0383b87b4b780cf516f7d7e43b784
From the 1.45.531.1 OTA:
has the same radio as the 1.45.401.2 OTA/RUU
From the 1.50.401.1 RUU:
has the same radio as the 1.45.401.2 OTA/RUU
From the 1.72.401.1 RUU:
10.58.9035.00U_10.15.9035.02_2
md5: 722549b642a1374964798cc82100855e
From the 1.73.401.2 RUU:
has the same radio as the 1.72.401.1 RUU
From the 1.73.401.4 RUU:
has the same radio as the 1.72.401.1 RUU
From the 2.08.401.1 RUU:
11.59.3504.00U_11.16.3504.16
md5: 5341559678f9f2066315b5214a26cb84

gu1dry said:
In order for this to work, the HTC Sensation needs to be S-OFF.
Click to expand...
Click to collapse
10characters

Due to the impending release of AplhaRev X for the HTC Sensation,
It is not his impending has not yet release date!

Max128 said:
It is not his impending has not yet release date!
Click to expand...
Click to collapse
Impending doesn't meaning it has a release date, just that it's coming soon.

ok i Understand What You meant to say.
Thank you for your work

It kinda means that it's coming REALLY soon.

Thanks very much...
Sent from my HTC Sensation 4G using XDA App

gu1dry said:
Impending doesn't meaning it has a release date, just that it's coming soon.
Click to expand...
Click to collapse
Amazing! Thank you so much for this. Next thing I will do right after True root.

First, thank you for the write up and radio links and contribution to all of this.
Now for my question: Wouldn't fastboot be easier and safer?
1 - Copy the .img to your /sdk/tools folder (or whatever folder depending on computer OS). Verify MD5.
2 - Boot into bootloader (Vol Down + Pwr).
3 - Navigate to Fastboot (Vol down to Fastboot and press Pwr). Make sure your phone says Fastboot USB.
4 - Open command promt (or terminal depending on OS)in folder you put file.
5 - Type:
Code:
fastboot flash radio xxxx.img
xxxx is radio name.
I find this faster and safer. I find SDCards can corrupt the file easier than anything else therefore leaving the file on your computer to flash from is one less transfer and possible issue. As we all know, the 2 things that have the greatest chance of bricking a device are your Radio and Bootloader images.
Just my .02

Fastboot probably won't be available at first, htc locked that down pretty tight for signed packages, this method is certain to work when s-off is released...
When eng s-off arrives, that should be a different story
Sent from my HTC Sensation 4G using XDA App

Solidus_n313 said:
Fastboot probably won't be available at first, htc locked that down pretty tight for signed packages, this method is certain to work when s-off is released...
When eng s-off arrives, that should be a different story
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
Doesn't this link have Eng S-Off Bootloader?
Maybe I'm reading into things too much and not understanding.

setzer715 said:
Doesn't this link have Eng S-Off Bootloader?
Maybe I'm reading into things too much and not understanding.
Click to expand...
Click to collapse
It does contain an Eng s-off but you have to have S-off to flash it

setzer715 said:
First, thank you for the write up and radio links and contribution to all of this.
Now for my question: Wouldn't fastboot be easier and safer?
</snip>
Click to expand...
Click to collapse
Flashing radios via fastboot is actually more dangerous. Due to first, flashing the Engineering Hboot, which that process in itself is pretty dangerous, and second, fastboot will accept anything & during the flash, the radio image can become corrupt & brick the device.

gu1dry said:
Flashing radios via fastboot is actually more dangerous. Due to first, flashing the Engineering Hboot, which that process in itself is pretty dangerous, and second, fastboot will accept anything & during the flash, the radio image can become corrupt & brick the device.
Click to expand...
Click to collapse
i agree 100%, but most ppl who dont understand this will prefer conveinence/speed but risk bricking, over doing it the tried and tested method with minimal risk and maximum effort that reduces the chances of a fancy paperweight...

crackeyes said:
It does contain an Eng s-off but you have to have S-off to flash it
Click to expand...
Click to collapse
I think he was responding to Solidus_n313's comment that 'Fastboot probably won't be available at first'. Once you have radio S-OFF, it's trivial to get ENG S-OFF. It looks to me like AlphaRevX is hboot S-OFF but it's still S-OFF so we should be able to toggle @secuflag to get radio S-OFF without too much trouble. Basically, what I'm saying is that we'll all have ENG S-OFF very soon after AlphaRevX is released.

dazweeja said:
It looks to me like AlphaRevX is hboot S-OFF but it's still S-OFF so we should be able to toggle @secuflag to get radio S-OFF without too much trouble. Basically, what I'm saying is that we'll all have ENG S-OFF very soon after AlphaRevX is released.
Click to expand...
Click to collapse
yeah, alpharev's is hboot, as the radio is locked uber tight for the time being. i also agree that ENG S-OFF will arrive shortly after the release.
the major concern is the extra security protocols implemented in @secuflag on the S4G (dont appear this way for the E3D), and while they will be bypassed/overwritten in time, there appear to be redundant calls to @secuflag than can precede hboot and radio modifications...(from what ive seen and recognize at least)
all i know is that if/when alpharev and teamwin collaborate, all these issues will no longer be a problem, but that seems to be a long shot, as the 2 are having some issues with each other atm :/

Solidus_n313 said:
the major concern is the extra security protocols implemented in @secuflag on the S4G (dont appear this way for the E3D), and while they will be bypassed/overwritten in time, there appear to be redundant calls to @secuflag than can precede hboot and radio modifications...(from what ive seen and recognize at least)
Click to expand...
Click to collapse
If it's S-OFF, eMMC write-protection is not enabled at boot so we can write to radio_config and toggle @secuflag directly. If the eMMC write-protection is still enabled, then I don't see how the phone could be considered S-OFF (or how we could flash custom ROMs for that matter). I guess it will all become clear in time.

gu1dry said:
Flashing radios via fastboot is actually more dangerous. Due to first, flashing the Engineering Hboot, which that process in itself is pretty dangerous, and second, fastboot will accept anything & during the flash, the radio image can become corrupt & brick the device.
Click to expand...
Click to collapse
I can see that, I guess I somehow got it in my head that fastboot was always the safest way to flash images. I bricked a G1 once, LONG time ago, by trying to flash an HBoot in recovery, but that is still different than what you are doing.

crackeyes said:
It does contain an Eng s-off but you have to have S-off to flash it
Click to expand...
Click to collapse
it's funny to me, since doesn't that mean we'd need a signed s-off bootloader?
... hilarious.

Which method of Flashing Radios is Safer....my opinion.
I disagree with the statement that updating the radio through bootloader is safer than fastboot for the following reasons:
First it generally thought that flashing radio.img through bootloader update (PG58IMG.zip for the sensation) method unpacks the radio.img to /cache first then flashes from /cache which makes it susceptible to corruption and there are no checks before the radio.img is flashed
and second there are file checks performed before fastboot flashes the radio.img.
I run the G2/DesireZ radio thread HERE :http://forum.xda-developers.com/showthread.php?t=970809
In which I have seen several bricks from the bootlaoder update (PG58IMG.zip for the sensation) method flashing a corrupt .img file and never any from flashing the radio.img through fastboot. My radio.img's have been downloaded well over 10000 times and this has been my experince with flashing radio's.

[Firmware][Jan 17]User-Friendly Firmware 1.17/3.12/3.24/3.30/3.32/3.33 Universal

##NOTICE - Please Make sure you are downloading correct one for your ROM and Read this post!##
Thanks goes to Mike for his firmware files, Revolutionary for patching the file, and all devs who keep giving us a reason to flash.
Also Thanks goes to hoosbude who hosted my firmware files when I needed a place to keep them up for everyone
PLEASE realize that this has the same warnings as all firmware. It can brick your device so please know how to flash it before you do so. I am not responsible if you misflash and brick your device.
This thread is beginner friendly so by all means ask and I will respond when I can or I am sure others are willing to help as well.
Firmwares that I have posted:
3.33 Universal is the latest/stable release ICS 4.0.3 FW for Sensation (sense 3.6 Version and works for Sense 4 also)
3.32 Universal is ICS 4.0.3 FW for Sensation (sense 3.6 Version) that has the Unlocked bootloader (posted by Mike1986)
3.30 Universal is ICS 4.0.3 FW for Sensation (sense 3.6 Version) that has the Unlocked bootloader (posted by Mike1986)
3.24 Universal is ICS 4.0.3 FW for Sensation (sense 3.6 Version) that has the Unlocked bootloader (posted by Mike1986)
3.12 Universal is ICS 4.0.3 FW before that (Sense 3.5 Version)
1.17 Universal This is the original Revolutionary 1.17.1111 Firmware with a completed Gingerbread Firmware v 1.45 package (Radio 10.14.9035.01_M)
######################################################
What is all this?
What I have here is a series of flashable updates of a complete GingerBread package and the latest ICS Firmware [Firmware from 1.17 - 3.33]
This is for those who don't know or have bad luck editing the android-info.txt file. Some people don't want to superCID or don't know how to use fastboot or adb. This makes you able to update without having to superCID or have to go to a PC.
So what is universal about it?
I have added a method found by mf2112 that allows the android-info file to have a wildcard tag. So instead of having a T-Mobile file where the android-info file has every cidnum the identifier is one entry into the android-info file and it covers every possible CID that T-Mobile has.
######################################################
"I really want to use the latest ICS! How do I go about doing this?
I get this PM'd to me a lot. The best way I have seen to do it is as shown
0. Make sure you are S-OFF (These won't work if you aren't)
1. Download PG58IMG.zip for the version you want
2. Copy/paste PG58IMG.zip to the root of your microSD
3. Make sure MD5 match!!!
4. Reboot into bootloader (While phone it completely off hold down Vol - and Power. Keep pressing until in bootloader. In Ext4, if in android, choose Power Menu - Bootloader)
5. Once in the Bootloader choose Bootloader and then microSD will be scanned and will ask you if you want to update, press +vol for YES
6. Follow onscreen instructions.
7. Now just pull sd card out (when process is finished) if you don't have microSD reader or delete PG58xxxx if you do. PG58 will prevent you from going into recovery if phone sees it.
7.5 If you don't have a SDCard Reader - Pop the SDCard out. Boot into the bootloader, go down to recovery, pop the SD-Card in then choose recovery.
8. If you do have a SDCard Reader -> Reboot into bootloader and go to recovery after deleting PG58IMG.zip file and putting the SDCard back in the phone
9. Reboot or flash new rom
10. You are done. Enjoy the ROM
My ROM doesn't boot. HELP!
Boot into recovery and clear dalvik and cache. 99% of the time this will fix that issue.
######################################################
How can I tell if the firmware flashed successfully???
In the bootloader up at the very top it will say the firmware version you just installed.
Ex: -Firmware-3.33- or -Firmware-1.17-
How to check your current Firmware Version for those who flashed before the most recent update:
fastboot getvar version-main
How to check your CID & MID:
You can do this one of the following ways.
1. fastboot load into the bootloader and do:
fastboot getvar cid
fastboot getvar mid
If you don't have fastboot I have provided a download of it at the bottom of this post. Read the Read-Me file inside of it.
2. For those without fastboot you can use an app called CID Getter. CID is displayed at the top. MID is at the line ro.mid
This will not tell if you are SuperCID or not it just tells your original CID.
3. If you want to do it by terminal, open a terminal on the phone and do:
su
getprop ro.cid
getprop ro.mid
If it gives you the result of CID: 11111111 and MID PG58******
You are superCID. Use any file you like it doesn't matter they all work for you.
######################################################
What is in the Universal Firmware File android-info.txt?
modelid: PG5813000
modelid: PG5813001
modelid: PG5810000
modelid: PG5811000
cidnum: H3G__***
cidnum: HTCCN***
cidnum: HTC__***
cidnum: HTC*****
cidnum: VODAP***
cidnum: T-MOB***
cidnum: ORANG***
cidnum: O2___***
cidnum: ********
######################################################
Can I edit the firmware files and change them to my liking?
Ofcourse! And let me teach you how below ^_^
How to edit the android-info.txt File via Windows (Will add Linux later. Sorry I don't own a MAC so I can't tell how to use that)
1. Go download Notepad++ and install it [It is free and is a great editer and makes it easier]
2. Download your PG58IMG.zip file you want to edit or one from a post by a DEV.
3. Double click file and open using Windows Archive Manager (Windows built in ZIP program)
4. Right click android-info.txt and copy it. Paste outside of the zip file
5. Right click android-info.txt you just pasted and open in notepad++
6. Add your cidnum that you want to the file or modelid. Use the ones already in there as an example.
7. Make sure there are no spaces after your cidnum or modelid (So it shouldn't be "cidnum: T-MOB010_" _ = space)
8. Save it
9. Double click the PG58IMG.zip again. Click android-info.txt and delete it in the archive (Don't extract the archive)
10. Drag and drop the new android-info.txt over PG58IMG.zip
11. Flash your newly packaged edited Firmware
12. Grab a drink and celebrate. You just created a custom firmware package.
[Here is a video tutorial how! http://youtu.be/fW5jSiqDRLg (Thanks to Iocn)]

Beginner Friendly Firmware Downloads:
Firmware 3.33 Universal:
DOWNLOAD:http://d-h.st/SuC
MD5: 07cc2a2ea4473e8fe8d6fe844c4020a1
Firmware 3.32 Universal (Non-TMOUS):
DOWNLOAD: http://d-h.st/OCH
MD5: 861dd138f68523a6cc56db7a0320ee0f
Firmware 3.30 Universal:
DOWNLOAD: http://d-h.st/jqh
MD5: f818413b0a4284c41308dd52b82efe33
Firmware 3.24 Universal:
DOWNLOAD: http://d-h.st/F2k
MD5: be7c5075f966d386c87f7ea8103f7445
Firmware 3.12 Universal:
DOWNLOAD: http://d-h.st/iMn
MD5: 4bf63f041560702828dede9fa1d6c328
Firmware 1.17 Universal
DOWNLOAD: http://d-h.st/Kbp
MD5: 84c684219911858e4480856be5a2be0f
====================================================================================
HBoot 1.29.0000 Patch (Go from Hboot 1.27.1100 to 1.29.0000)
Download: http://d-h.st/ETo
MD5: f47d270e24cdca66a14278ed6d3e0a38
HBoot 1.27.1100 Patch (Go from Hboot 1.29.0000 to 1.27.1100)
Download: http://d-h.st/gz1
MD5: 83606014bde64fd5b3076bd1aa1cf3fc
====================================================================================
Backup Links (Thanks to Emanon!!!!)
Firmware 3.12 unlocked hboot http://www.mediafire.com/?2ztahkck2lr74h0
Firmware 3.24 unlocked hboot http://www.mediafire.com/download.php?889vi1ej4op00vw
Firmware 3.30 unlocked hboot http://www.mediafire.com/download.php?np485s36z2s7akn
Firmware 3.32 unlocked hboot http://www.mediafire.com/download.php?mrynwif8cznhhvx
Firmware 3.32 TMOUS unlocked hboot http://www.mediafire.com/download.php?wbq2cg6ce2v2r8y
Firmware 3.33 Universal unlocked hboot http://www.mediafire.com/download.php?jxmi7jpiqbshgj1
Link for DropBox folder
https://www.dropbox.com/sh/rgtw3gumdbmvlol/7wugYfXmjF

Update Log:
[1/17/13] Changed HBoot via Hex Editor to report what Firmware Version you installed in the bootloader (ex -Firmware-3.33-)
[7/23/12] Added Full upgrade 3.33 Package.
[7/10/12] Fixed 3.33 to no longer have a HBOOT File and also combined "Others 1 & 2" into firmware package to make a full Universal package
[7/6/12] Added 3.33 Universal
[6/15/12] Updated 90% of packages to Universal Firmware. Switched hosting to Dev-Host.
[5/31/12] Added Universal FW link for v3.32 here for testing http://forum.xda-developers.com/showpost.php?p=26815412&postcount=1194
[5/17/12] Added TMO 3.32.531.14 710RD to post 2, Updated post 1 instructions (more specific)
[3/30/12] Built a complete GingerBread package after pulling revolutionary HBOOT. Uploaded files for users
**Removed older update info**

Kohr-Ah, it's about time you post this...good work.
Thank you

Ok I used cid finder says cid 111111 that's what I set it too when I rooted what file do I need
Sent from my HTC Sensation 4G using xda premium

Does this have new Ril in it and radio
Sent from my HTC Sensation 4G using xda premium

craven667 said:
Ok I used cid finder says cid 111111 that's what I set it too when I rooted what file do I need
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
That means you are superCID. Any file will work for you

craven667 said:
Oh this has new Ril in it and radio
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
Correct.
This is this firmware
http://forum.xda-developers.com/showthread.php?t=1412618
made friendlier to beginners who don't know how to or don't want to superCID.

Thank you for creating this thread! While I already have the latest firmware loaded, the amount of time I spent reading through page after page of comments just to make sure I was doing it correctly was a bit much.
Again, thanks for contributing.
Sent from my HTC Sensation Z710e using Tapatalk

no image...
I have cidnum: VODAP110 but with the file for VODAPHONE I get the message: no image or wrong image...

Thanks dude. Is 3.24 firmwares are unlocked or locked?
Sorry for bad english

gokberks said:
Thanks dude. Is 3.24 firmwares are unlocked or locked?
Sorry for bad english
Click to expand...
Click to collapse
They are all locked
Same as Mike's firmware. As the only commands you lose are fastboot flash.
Sent from my Sensation in Ur-Quan subspace

hungi said:
I have cidnum: VODAP110 but with the file for VODAPHONE I get the message: no image or wrong image...
Click to expand...
Click to collapse
For all images when it scans them in the vodaphobe file or just one? (Also 3.12 or 3.24?)
Sent from my Sensation in Ur-Quan subspace

1 question
if i update the firmware...i'll be able to turn back to the original rom???? if yest what the steps? sorry for my english

I have a newzeland telecom sensation and it is not listed and I have been very un lucky editing the info, I can't save the changes to the file...
My Cid: TELNZ001
MODID: PG5811000
can you please add this to the file for me !
Thanks for this file they are making life easear for everyone!
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium

Panchulo77 said:
I have a newzeland telecom sensation and it is not listed and I have been very un lucky editing the info, I can't save the changes to the file...
My Cid: TELNZ001
MODID: PG5811000
can you please add this to the file for me !
Thanks for this file they are making life easear for everyone!
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
Will add and upload when i get to a PC figure about two hours from this post.
I will add it to the OTHERS firmware
Sent from my Sensation in Ur-Quan subspace

After reading the PG58IMG.zip, there's no yes / no question for installing, only the normal hboot menu...
Current version: 1.23 S-ON // CID: HTC__102
What's wrong?
ToM

Nightwing0815 said:
After reading the PG58IMG.zip, there's no yes / no question for installing, only the normal hboot menu...
Current version: 1.23 S-ON // CID: HTC__102
What's wrong?
ToM
Click to expand...
Click to collapse
When you flashed firmware it asked you to push vol up for yes and volume down for no didn't it before it began?
Sent from my Sensation in Ur-Quan subspace

Kohr-Ah said:
When you flashed firmware it asked you to push vol up for yes and volume down for no didn't it before it began?
Click to expand...
Click to collapse
It don't ask... It reads the content of the package and then it will switch without asking to a normal hboot menu. After that, i'm hboot 1.23, like before...
ToM

Can the firmware be edited to leave out certain elements?
It seems that the 3.24 firmware includes a screen update that makes AOU screens have a much colder/blue tint look.
Could that element of the firmware be hacked out?
I wouldn't even personally think to try such a thing. But if someone who knows how to code could yank that part of the update out it would be awesome.

Baseband(radio update) ?

Hi, my current version of Baseband is 20.28I.30.085AU_3805.06.02.03_M and i want to install and run ROM ICE DS v 4.4 where i saw that recommended radio is: 20.72.30.0833U_3831.17.00.310..so i am not sure what should i do(how to upgrade it)??, i taught it's better to ask here than to search for some guides etc. coz i read that if something is done wrong , the phone is dead

bobahajduk said:
...i taught it's better to ask here than to search for some guides etc. coz i read that if something is done wrong , the phone is dead
Click to expand...
Click to collapse
Very bad thought and wrong assumption that you'll get better help here by hell knows whom, instead of reading the guides that were written to be understood and executed by thousands of people till today.

See this Guide:
nodeffect said:
HTC Desire S Tutorials/Guides
Click to expand...
Click to collapse
Sent from my Desire S

so i found the list:'' From the Saga Test RUU:
20.23.30.0802U_38.02.01.11
md5: 68b46430f42c07ecdc4f1e68bdaf9123
From the 1.28.401.1 RUU:
20.28b.30.0805U_38.03.02.11
md5: 27d85ee9604584becfa59c213708370a
From the 1.30.110.2_R RUU:
has the same radio as the 1.28.401.1 RUU
From the 1.30.111.1 RUU:
has the same radio as the 1.28.401.1 RUU
From the 1.30.112.1 RUU:
has the same radio as the 1.28.401.1 RUU
From the 1.31.61.1 RUU:
has the same radio as the 1.28.401.1 RUU
From the 1.31.65.1 RUU:
has the same radio as the 1.28.401.1 RUU
From the 1.31.206.1 RUU:
20.28b.30.0805U_38.03.02.14
md5: a898a290eb58ec618ceb3865a90dc878
From the 1.31.351.1 RUU:
20.28b.30.0805U_38.03.02.15
md5: 757cde85b4e8736db93088134f9afc8e
From the 1.31.707.2_R RUU:
has the same radio as the 1.31.351.1 RUU
From the 1.31.720.2_R RUU:
has the same radio as the 1.31.206.1 RUU
From the 1.31.771.1 RUU:
has the same radio as the 1.31.206.1 RUU
From the 1.31.832.3 RUU:
20.28d.30.0805U_3805.04.02.01
md5: 631afebe525a455f34b2238108ac1b43
From the 1.31.950.2_R RUU:
has the same radio as the 1.31.206.1 RUU
From the 1.31.1020.1 RUU:
20.28c.30.0805U_38.03.02.16
md5: 5d82b1d2a70a46eaa93ad10964809f1a
From the 1.32.161.1 RUU:
has the same radio as the 1.31.351.1 RUU
From the 1.35.1113.2 RUU:
has the same radio as the 1.31.832.3 RUU
From the 1.36.415.6 RUU:
has the same radio as the 1.31.832.3 RUU
From the 1.36.841.3 RUU:
has the same radio as the 1.31.832.3 RUU
From the 1.46.1400.8 RUU:
20.28f.30.085AU_3805.04.02.28
md5: f4951ae92f6abd85823d916f46e5312e
From the 1.47.401.4 RUU:
20.28I.30.085AU_3805.06.02.03
md5: 57a3fcc5f72ec928050dbcb32018215f
From the 1.47.832.1 RUU:
has the same radio as the 1.47.401.4 RUU
From the 1.47.950.3 RUU:
has the same radio as the 1.47.401.4 RUU
From the 1.48.707.1 RUU:
has the same radio as the 1.47.401.4 RUU
From the 2.10.401.4 OTA:
20.48.30.0822U_3822.09.08.20
md5: 053544276893dfcc3a7a722c834b6020
From the 2.10.401.5 RUU:
20.4801.30.0822U_3822.10.08.04
md5: 2fddef29eb1f8001d9cad14f48061f54''
But i dont understand which is a right one for me ??

My personal view: until you have learnt more, don't worry about changing radios. Then, if you are having issues that are radio related, then upgrade.
Or, once you are more familiar with changing your phone, then try different radios.
Fyi, I'm on Radio-20.4801.30.0822U_3822.10.08.04
Sent from my Desire S

BillGoss said:
My personal view: until you have learnt more, don't worry about changing radios. Then, if you are having issues that are radio related, then upgrade.
Or, once you are more familiar with changing your phone, then try different radios.
Fyi, I'm on Radio-20.4801.30.0822U_3822.10.08.04
Sent from my Desire S
Click to expand...
Click to collapse
i already had some strange issues with fallout(slow,buggy,youtube not working) than with icecold sandwich (phone restarting)...so i don't know whats the problem ...so i suppose i should upgrade that Radio or whatever..i just want to start using my phone without having always to think about force closing, freezing, restarting etc...

If you want a phone with no issues - then you shouldn't use ICS ROMs yet, until it's officially released.

I Think you Should try and flash the rom and see how it goes...
because there is a good chance it'll work just fine with your current radio.
If not... there is nothing too difficult in flushing a radio, it's a very simple
process if you already unlocked your phone.

maxlieb said:
I Think you Should try and flash the rom and see how it goes...
because there is a good chance it'll work just fine with your current radio.
If not... there is nothing too difficult in flushing a radio, it's a very simple
process if you already unlocked your phone.
Click to expand...
Click to collapse
so if you can answer to my first post it would be very nice

Read the RADIO sticky thread on the development section
Sywepd form my DsereiS

Which is the latest firmware for the One XL?

hi - I'm referring to the firmware, not an RUU or OTA.
For example, from this thread - I see that firmware ver 2.15.0000 comes from 5.08.111.2 ROM.
Is there any later firmware than the 2.15 above ? I'm using CM11 and the only way I can flash firmware is through the adb tool (I dont have windows), so want to figure this out.

sandys1 said:
Is there any later firmware than the 2.15 above ? I'm using CM11 and the only way I can flash firmware is through the adb tool (I dont have windows), so want to figure this out.
Click to expand...
Click to collapse
The newest firmware is inside Brightstar 5.13.1540.2.
Orange 5.14.61.2 and HTC Hong Kong 5.08.708.3 both also have newer firmware than T-Mobile 5.08.111.2 but are not the newest.
Brightstar 5.13.1540.2:
Kernel: 3.4.10-gefd4656
hboot: 2.18.0000
radio: 1.34a.32.45.21_10.142.32.34a
adsp: 33.1.0.45.1128
wcnss: 1031145
tp_syn3202: 3.2_PR1293981
tz: 001.138.020
sbl1: 001.138.004
sbl2: 001.138.009
sbl3: 001.138.007
T-Mobile 5.08.111.2:
Kernel: 3.4.10-g08ef01e
hboot: 2.15.0000
radio: 1.31a.32.45.16_2_10.141.32.34a
adsp: 33.1.0.45.1128
wcnss: 1031145
tp_syn3202: 3.2_PR1293981
tz: 001.138.019
sbl1: 001.138.003
sbl2: 001.138.007
sbl3: 001.138.005

twistedddx said:
The newest firmware is inside Brightstar 5.13.1540.2.
Orange 5.14.61.2 and HTC Hong Kong 5.08.708.3 both also have newer firmware than T-Mobile 5.08.111.2 but are not the newest.
Click to expand...
Click to collapse
Thanks for that !
Would you know how to extract just the firmware from that file so that it can be flashed by doing fastboot oem rebootRUU and
fastboot flash zip <PathToFirmware.zip>, similar to how turge extracted it for 5.08.111.2 ?
Thanks again...

sandys1 said:
Would you know how to extract just the firmware from that file so that it can be flashed by doing fastboot oem rebootRUU and
fastboot flash zip <PathToFirmware.zip>, similar to how turge extracted it for 5.08.111.2 ?
.
Click to expand...
Click to collapse
Ensure s-off and supercid first.
You could create your own unofficial firmware.zip like Turge did that includes some img's that the OTA you are installing may be missing. I think the following will be easiest though.
Ensure 3.17/3.18 complete firmware or better as base is installed on phone, eg 3.18 RUU or previously updating to 3.xx/5.xx officially with HTC OTA. This can be skipped if you are certain you have already installed this or Turges 5.08.111.2 firmware.
Download T-Mobile 3.17.111.1 OTA (or similar complete 3.17/3.18):
http://fotadl.htc.com/OTA_EVITA_UL_...129.32.34a_release_300591m6ejdlmoq874n7fw.zip
Open zip, extract firmware.zip
fastboot oem rebootRUU
fastboot flash zip firmware.zip <<repeat if you get error please flush again immediately. Typically this needs to be done 2-3 times. When it completes without please flush again message you can reboot the phone.
fastboot reboot
If this step is not done you run a higher risk of the device being bricked in the update.
I would suggest reboot to ensure firmware is completely written to device before moving to next firmware.zip package.
Download Brightstar 5.13.1540.2 OTA:
http://fotadl.htc.com/OTA_EVITA_UL_....17.1540.4_release_342737ulobjpm2t4w05mnr.zip
Open zip, extract firmware.zip
fastboot oem rebootRUU
fastboot flash zip firmware.zip <<repeat if you get error please flush again immediately. Typically this needs to be done 2-3 times. When it completes without please flush again message you can reboot the phone.
fastboot reboot
NOTE: HTC official firmware.zip includes boot.img and recovery.img. You will need to reinstall custom recovery and your installed ROMs matching boot.img.
NOTE #2: CM install scripts do not include hboot 2.18 (it includes 2.14, 2.15, 2.16 and 2.17). You would need to hand edit the updater-script for such ROM's to get them to install.
NOTE #3: The above instructions account only for the software versions listed above. Do not assume these instructions can be used for past or future firmware.zip files obtained from past/future OTA. You must always account for the fact OTA expects your phone to already be functional with a particular previous software version. OTA firmware.zip typically does not include files that are expected to already be installed on the device. Updating from unexpected software versions will likely end in a bricked phone. Whereas RUU files contain complete firmware.zip.

What is the reason for wanting the "latest" firmware? I haven't been following CM11 closely (so maybe I'm missing something here), but in general the AOSP ROMs don't require the "latest" firmware, its just the Sense 5 ROMs that act wonky if your firmware (probably radio in particular) is outdated.
So unless I'm missing something, it seems like you are going through a lot of extra work and risk of bricking the phone for no real reason. If you don't do the steps exactly right as twistedddx listed them, you run a high risk of instantly bricking the device (and the only way back is JTAG). In particular, if you don't update the hboot modules correctly (sbl1, 2, and 3 all need to be compatible), its a brick.

I agree with Redpoint, there's absolutely no benefit to flashing this firmware, only risk, unnecessary risk.
Sent from my Evita

sandys1 said:
For example, from this thread - I see that firmware ver 2.15.0000 comes from 5.08.111.2 ROM.
Click to expand...
Click to collapse
2.15 is not technically a firmware number. Its just been often posted here "2.15 firmware" as a sort of shorthand for "the firmware modules that came with hboot 2.15". Each module has different numbers (tz, sbl1, etc.), as twistedddx posted in Post #2 above. Checking the number for each module is the only way to check for what is "latest".