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

gu1dry · Jul 20, 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 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

mikeDCMDVA · Jul 20, 2011

gu1dry said:
In order for this to work, the HTC Sensation needs to be S-OFF.

10characters

Max128 · Jul 20, 2011

Due to the impending release of AplhaRev X for the HTC Sensation,

It is not his impending has not yet release date!

gu1dry · Jul 20, 2011

Max128 said:
It is not his impending has not yet release date!

Impending doesn't meaning it has a release date, just that it's coming soon.

Max128 · Jul 20, 2011

ok i Understand What You meant to say.

Thank you for your work

eyegor · Jul 20, 2011

It kinda means that it's coming REALLY soon.

jerrylzy · Jul 21, 2011

Thanks very much...

Sent from my HTC Sensation 4G using XDA App

Jamison904 · Jul 21, 2011

gu1dry said:
Impending doesn't meaning it has a release date, just that it's coming soon.

Amazing! Thank you so much for this. Next thing I will do right after True root.

setzer715 · Jul 21, 2011

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

Solidus_n313 · Jul 21, 2011

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

setzer715 · Jul 21, 2011

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

Doesn't this link have Eng S-Off Bootloader?

Maybe I'm reading into things too much and not understanding.

crackeyes · Jul 21, 2011

setzer715 said:
Doesn't this link have Eng S-Off Bootloader?

Maybe I'm reading into things too much and not understanding.

It does contain an Eng s-off but you have to have S-off to flash it

gu1dry · Jul 21, 2011

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>

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.

Solidus_n313 · Jul 21, 2011

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.

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

Jimmy Flip · Jul 21, 2011

crackeyes said:
It does contain an Eng s-off but you have to have S-off to flash it

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.

Solidus_n313 · Jul 21, 2011

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.

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 :/

Jimmy Flip · Jul 21, 2011

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)

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.

setzer715 · Jul 21, 2011

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.

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.

Mystik · Jul 21, 2011

crackeyes said:
It does contain an Eng s-off but you have to have S-off to flash it

it's funny to me, since doesn't that mean we'd need a signed s-off bootloader?

... hilarious.

joemm · Jul 21, 2011

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://xdaforums.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.

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

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts