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] HTC Desire S Radios [PG88IMG.zip] (Updated: 21 Oct 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 S 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 S.
Make sure the filename is PG88IMG.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 S to the computer via USB.
On the computer, open terminal and run the following commands:
Code:
adb push PG88IMG.zip /sdcard/PG88IMG.zip
adb shell md5sum /sdcard/PG88IMG.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 S 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 S normally.
Downloads:
From Gingerbread-based RUUs:
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

Thanks for putting these in one place, and even though there's a warning about bricking phone's, I would like to warn everyone that flashing a radio is very rarely necessary, and should not be done on a whim!!! Not enough is known about recovering from a bad flash on the NVRam (radio), and if this happens you could end up with a very expensive calculator.

Thanks a LOT !!!!!!! My radio is here, so i can flash others, and if i find errors, i can come back. Thanks again man.

New Radio from leaked official ROM
This is the Radio that came with the recently leaked official Desire S Sense v3.0 ROM.
20.4130.0818U_3817.07.00.19_M RADIO

so is this linux only or can the terminal be replaced with the command prompt?

dan-fish said:
so is this linux only or can the terminal be replaced with the command prompt?
Click to expand...
Click to collapse
This isn't for linux specifically, this is also possible for windows, where by terminal he means windows command prompt (CMD), assuming that you have the relevant ADB installed.
If you don't download it from here

I have a question: there are some compatibility issue between radio and hboot version?

You can use the new radio with the old hboot.
Any problem for use that.
If you want to install the new hboot while you have already install the new radio, there's no problem of incompatibility

ben_pyett said:
This is the Radio that came with the recently leaked official Desire S Sense v3.0 ROM.
20.4130.0818U_3817.07.00.19_M RADIO
Click to expand...
Click to collapse
Can anyone confirm what the md5sum for this file should be?
Any chance a download link for this radio could be added to the top post?

There is already newer radio available - 20.44.30.0821U_3821.08.00.24_M

uoosuow said:
There is already newer radio available - 20.44.30.0821U_3821.08.00.24_M
Click to expand...
Click to collapse
[RADIO](added ril)New leaked radio:20.44.30.0821U_3821.08.00.24_M

Well done @ben_pyett
Thk's

It would be nice if the top post could be updated with these radios & md5sums
hint hint @gu1dry

runagate17 said:
It would be nice if the top post could be updated with these radios & md5sums
hint hint @gu1dry
Click to expand...
Click to collapse
I only add radios pulled from full RUUs (that I pulled personally) or reliable sources.

gu1dry said:
I only add radios pulled from full RUUs (that I pulled personally) or reliable sources.
Click to expand...
Click to collapse
Fair enough! much safer that way.....you don't get people shouting at you then!
If people want the other leaked RADIO's there are links to them elsewhere!

Question:
Is there somewhere a GUIDE for downgrading Radio if the leaked one will not work how i hope?

Sure. The guide are so simple:
you'll have to use fastboot command but not the PG88IMG flash
Use a simple command : fastboot flash radio your_radio_file.img

And as "your_radio_file.img" i'll take the image file included in PG88IMG.zip.
Am i right?

When you unzipped the PG88IMG, you've found a file "radio.img"

my radio on my HTC DS is 20.28I.30.085AU_3805.06.02.03_M on this post no "_M" on the end. is there a difference on that? thanks!

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

[Q] Radio for HTC Sensation 6.11

I flashed new firmware 3.24.401.1 RUU and then flashed 6.11 Rom
But doesn’t show radio 11.68.3504.00U_11.21.3504.13_2.
I still have radio 11.65.3504.00U_11.19.3504.29_2
Not sure what to do from here, please advise.

Usually radio fails to flash correctly if you try to flash the firmware package without having supercid (or having correct firmware for your cid http://forum.xda-developers.com/showthread.php?t=1459767)

3.33 fw?

i think i have 3.32 fw still is there a need to upgrade?

From what I can tell the 3.33 firmware has just the following files:
adsp.img
android-info.txt
radio.img
rcdata.img
tz.img
I am not sure if updating the firmware is any different to updating to the latest radio 11.24a.3504.31_m
If the radio is flashed is there any difference to flashing the 3.33 firmware package? The new package does not contain any bootloader in it.

GhostXSeries said:
From what I can tell the 3.33 firmware has just the following files:
adsp.img
android-info.txt
radio.img
rcdata.img
tz.img
I am not sure if updating the firmware is any different to updating to the latest radio 11.24a.3504.31_m
If the radio is flashed is there any difference to flashing the 3.33 firmware package? The new package does not contain any bootloader in it.
Click to expand...
Click to collapse
Did you download the one from baadnewz's link? the proper firmware.zip has a full firmware including hboot v1.29.0000 for sensation xe and 1.27.0000 for sensation. Also the new firmware contains a new kernel version (though htc havent dropped the source for it yet so I'm spamming @htcdev on twitter )