[DEV] HTC Sensation & HTC Sensation XE firmware | Partitions Info | [11.07.2012]

Search This thread

mike1986.

Senior Member
This thread's content might brick your device.
This is not a ROM thread, so I'm not going to answer again and again and again the same questions over and over and over again.
You can't read - quit this thread now. You can read but you can't understand more or less simple things - quit as well.
You can read and you understand things, but you are too lazy to read the whole thread before asking the question - watch this first. And quit.

I compared the content of HTC Sensation and HTC Sensation XE RUU's.


index1.php

Some conclusions based on users feedback after flashing Sensation XE RUU:

1. It definitely doesn't brick the device. If you have Super-CID, it can be flashed even on regular Sensation (PG5813000).
2. It seems that most of those, who flashed it can tell that their device is now noticeable faster.
3. It doesn't bring S-ON to your device.
4. "fastboot flash <partition name> <file name.img>" doesn't work with new 1.20 hboot. But it's not really a problem, because most users doesn't use fastboot.

Other conclusions:

1. adsp.img is the same in all HTC Sensation and HTC Sensation XE RUUs. So it's irrelevant to us.
2. pg2fs_spcustom.img is the same in all HTC Sensation and HTC Sensation XE RUUs. So it's irrelevant to us. This image wasn't in RUUs since the beginning. It came out first in 1.45.401.2 RUU.
3. splash1.nb0 is the same in all HTC Sensation and HTC Sensation XE RUUs. So it's irrelevant to us. It's just a splash screen anyway.
4. dzdata_4g.hdr and dzdata_4g.img came out first in 3.06.401.1/101 RUU. Before it was just one image - dzdata.img.
5. rcdata.img is the same in all HTC Sensation and HTC Sensation XE RUUs. But it's different for HTC Sensation 4G U.S. T-Mobile and it contains some additional settings. It contains radio settings.
6. radio.img and rcdata.img are radio related. Should affect better connectivity quality, but should not affect overall performance in any way.
7. hboot_8x60_1.20.0000_20111215_signedbyaa.nb0, sbl1.img, sbl2.img, sbl3.img and tz.img are all (probably) bootloader related. It should not affect overall performance (probably).
8. The only left is rpm.img which probably is relevant to us (as rmk40 also stated). But it doesn't mean it can be flashed just as a single image. Probably it has to be flashed with other
images like radio or bootloader related to avoid risk of bricking the device.
9. Because new images came out in new RUUs (dzdata_4g.hdr and dzdata_4G.img replaced dzdata.img) it's very possible that we need to flash new bootloader as well.
10. ramdisk.img came out first in 3.06.401.1/101 RUU. It has the same content as ramdisk in boot.img and I have no idea why HTC made is as additional image (maybe even allocated partition for that?).
11. dzdata_4G images are different in Sensation and Sensation XE RUU. Is it because Sensation XE supports less CID locations?
12. Flashing dzdata_4g.hdr and dzdata_4g.img removes the content of userdata partition. In bootloader it's market as "userdata" file so it's probably not radio related.
13. dzdata_4G.img contains QUALCOMM Logging tools (LOCAL_CFLAGS += -DFEATURE_DATA_LOG_SYSLOG #LOCAL_CFLAGS += -DFEATURE_DATA_LOG_ADB LOCAL_CFLAGS += -DFEATURE_DATA_LOG_QXDM) so it's irrelevant to us.

Here is the partitions table from before and after flashing new firmware:


index1.php



sep9.png



Download firmware for HTC Sensation (PG5813000, PG5811000 & PG5810000) & HTC Sensation XE (PG5813001)

Firmware from 3.12.401.2/102 RUU
--- MD5 checksum: FF644ED2BFF6A6058023C6FF36401E5C *PG58IMG.zip ---

Supported devices:
--- CID's added by users requests are marked with green color ---
cidnum: 11111111
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__N34
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__016

cidnum: HTC__044
cidnum: HTC__038

cidnum: VODAP203
cidnum: VODAPE17
cidnum: VODAP102

Firmware from 3.24.401.1 & 3.25.401.101 RUU
--- MD5 checksum: 4774D8928FB9D364F83CDDE16BAC4553 *PG58IMG.zip ---
--- Only for 3.24.401.1 & 3.25.401.101 based ROMs

Supported devices:
--- CID's added by users requests are marked with green color ---
cidnum: 11111111
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__N34
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__016

cidnum: HTC__044
cidnum: HTC__038

cidnum: VODAP203
cidnum: VODAPE17
cidnum: VODAP102
cidnum: VODAP001

Firmware from 3.30.401.1 & 3.30.401.101 RUU
--- MD5 checksum: 824295C6ACDC8D55BED9E0B913192DBE *PG58IMG.zip ---
--- Only for 3.30.401.1 & 3.30.401.101 based ROMs

Supported devices:
--- CID's added by users requests are marked with green color ---
cidnum: 11111111
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__N34
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__016

cidnum: HTC__044
cidnum: HTC__038

cidnum: VODAP203
cidnum: VODAPE17
cidnum: VODAP102
cidnum: VODAP001

Firmware from 3.32.401.x & 3.32.401.10x RUU
--- MD5 checksum: 74A8E07D40A42DA1B4B56C224C42E692 *PG58IMG.zip ---
--- Only for 3.32.401.x & 3.32.401.10x based ROMs

Supported devices:
--- CID's added by users requests are marked with green color ---
cidnum: 11111111
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__N34
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__016

cidnum: HTC__044
cidnum: HTC__038

cidnum: VODAP203
cidnum: VODAPE17
cidnum: VODAP102
cidnum: VODAP001

Firmware from 3.33.401.6 & 3.33.401.106 RUU
--- MD5 checksum: A28BABD1636C406FA953E56008128F31 *PG58IMG.zip ---
--- Only for 3.33.401.6 & 3.33.401.106 based ROMs

Supported devices:
--- CID's added by users requests are marked with green color ---
cidnum: 11111111
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__N34
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__016

cidnum: HTC__044
cidnum: HTC__038

cidnum: VODAP203
cidnum: VODAPE17
cidnum: VODAP102
cidnum: VODAP001

Why it's better then full RUU:

1. It doesn't contain stock recovery
2. It doesn't contain stock, non rooted system
3. It doesn't contain secured boot.img
4. It wont wipe your data partition
5. It's much smaller :D

PG58IMG.zip content: [UPDATE: 22.02.2012]

adsp.img - updated [11.07.2012] - This is needed for 3.12.xxx.x/3.24.xxx.x/3.25.xxx.x/3.30.xxx.x/3.32.xxx.x/3.33.xxx.x based ROM to boot!
android-info.txt - updated [011.07.2012]
dzdata_4g.hdr - removed from the package [28.12.2011]
dzdata_4g.img - removed from the package [28.12.2011]
hboot_8x60_1.29.0000_20120302_signedbyaa.nb0 (with locked fastboot) - updated [11.07.2012]
pg2fs_spcustom.img - removed from the package [01.03.2012]
radio.img - updated [11.07.2012]
rpm.img - updated [11.07.2012]
sbl1.img - updated [20.01.2012]
sbl2.img - updated [22.02.2012]
sbl3.img - updated [20.01.2012]
tz.img - updated [11.07.2012]

How to flash:

1. Check your CID using fastboot getvar cid and MID using fastboot getvar mid
2a. If your CID and MID are supported by default, navigate to point 3.
2b. If your CID or MID is not supported by default, do this: (you do it at your own risk)
2c. Open PG58IMG.zip (don't extract it)
2d. Open android-info.txt in text editor
2e. Add your cidnum: <your CID> or modelid: <your MID> to the list, save file and close archive
3. Place PG58IMG.zip on your SD card
4. Boot your device holding power button + vol down button
5. Follow instructions on the screen

Additional information:

1. Flash above firmware at your own risk!
2. It's recommended to flash it before flashing custom ROM based on proper RUU!
3. HTC Sensation variants:

PG5813000 - HTC Sensation
PG5813001 - HTC Sensation XE
PG5810000 - HTC Sensation 4G
PG5811000 - HTC Sensation in Telstra network

4. RUU variants:
x.xx.61.x - Orange UK (United Kingdom)
x.xx.69.x - Orange PL (Poland)
x.xx.73.x - Orange FR (France)
x.xx.75.x - Orange ES (Spain)
x.xx.110.x - T-Mobile UK (United Kingdom)
x.xx.111.x - T-Mobile DE (Germany)
x.xx.113.x - T-Mobile CZ (Czech Republic)
x.xx.161.x - Vodafone UK (United Kingdom)
x.xx.163.x - Vodafone FR (France)
x.xx.165.x - Vodafone IT (Italy)
x.xx.168.x - Vodafone GR (Greece)
x.xx.206.x - O2 UK (United Kingdom)
x.xx.401.x - World Wide English
x.xx.468.x - Turkey
x.xx.497.x - Morocco
x.xx.498.x - WWE Brightpoint US (United States)
x.xx.531.x - T-Mobile US (United Kingdom)
x.xx.666.x - Bell Canada
x.xx.707.x - Asia WWE (World Wide English)
x.xx.709.x - Asia TW (Taiwan)
x.xx.720.x - Asia India
x.xx.771.x - Hutchison 3G UK (United Kingdom)
x.xx.841.x - Telsra WWE (World Wide English)
x.xx.862.x - Voda-Hutch AU (Australia)
x.xx.901.x - TIM IT (Italy)
x.xx.911.x - SK Telecom (South Korea)
x.xx.1400.x - HTC China
x.xx.1403.x - HTC China CMCC (China Mobile Communications Corporation)

I did some research myself, but I also used info from here and here

Please post here your findings, thoughts or experience with after flashing images listed above.
 
Last edited:

mike1986.

Senior Member
Some conclusions based on users feedback after flashing RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.06.401.101_Radio_11.59.3504.00U_11.16.3504.16_M_test_231336.exe RUU:

1. It definitely doesn't brick the device. If you have Super-CID, it can be flashed even on regular Sensation (PG5813000)
2. It seems that most of those, who flashed it can tell that their device is now noticeable faster
3. It doesn't bring S-ON to your device
 

tinker2000

Senior Member
Apr 25, 2009
862
186
Near Grantham
Some conclusions based on users feedback after flashing RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.06.401.101_Radio_11.59.3504.00U_11.16.3504.16_M_test_231336.exe RUU:

1. It definitely doesn't brick the device. If you have Super-CID, it can be flashed even on regular Sensation (PG5813000)
2. It seems that most of those, who flashed it can tell that their device is now noticeable faster
3. It doesn't bring S-ON to your device
Hi Mike,

My experiences are exactly as you describe. your HD v5 ROM is most definitely faster after flashing the RUU. I had to superCID first, asyou described :)
I also followed Ziggy's method where HBOOT returned back to 1.17 after flashing.
 

mike1986.

Senior Member
Hi Mike,

My experiences are exactly as you describe. your HD v5 ROM is most definitely faster after flashing the RUU. I had to superCID first, asyou described :)
I also followed Ziggy's method where HBOOT returned back to 1.17 after flashing.

You can also flash PG58IMG.zip. I will prepare such package without hboot, sbl and other irrelevant stuff.
 

mike1986.

Senior Member
1. adsp.img is the same in all HTC Sensation and HTC Sensation XE RUUs. So it's irrelevant to us.
2. pg2fs_spcustom.img is the same in all HTC Sensation and HTC Sensation XE RUUs. So it's irrelevant to us. This image wasn't in RUUs since the beginning. It came out first in 1.45.401.2 RUU
3. splash1.nb0 is the same in all HTC Sensation and HTC Sensation XE RUUs. So it's irrelevant to us.
4. dzdata_4g.hdr and dzdata_4g.img came out first in 3.06.401.1/101 RUU. Before it was just one image - dzdata.img
5. rcdata.img is the same in all HTC Sensation and HTC Sensation XE RUUs. So it's irrelevant to us.
6. dzdata_4g.hdr, dzdata_4g.img, radio.img and rcdata.img are all radio related. Should affect better connectivity quality, but should not affect overall performance in any way.
7. hboot_8x60_1.20.0000_20111215_signedbyaa.nb0, sbl1.img, sbl2.img, sbl3.img and tz.img are all (probably) bootloader related. It should not affect overall performance (probably).
8. The only left is rpm.img which probably is relevant to us (as rmk40 also stated). But it doesn't mean it can be flashed just as a single image. Probably it has to be flashed with other
images like radio or bootloader related to avoid risk of bricking the device.
9. Because new images came out in new RUUs (dzdata_4g.hdr and dzdata_4G.img replaced dzdata.img) it's very possible that we need to flash new bootloader as well.
 
Last edited:

mike1986.

Senior Member
Looks like we only really need hboot and all of the IMG in 6. for camera (hdr), radio freq (4g) and radio.IMG itself.

Sent from my HTC Sensation Z710e using XDA App

I would say rpm.img is also relevant to us.

So anyway - anyone can confirm/deny:

1. After flashing RUU you still have S-OFF but you can't use fastboot commands as long as you flash back 1.17 hboot?
 

Catnap

Senior Member
Sep 24, 2010
957
453
I would say rpm.img is also relevant to us.

So anyway - anyone can confirm/deny:

1. After flashing RUU you still have S-OFF but you can't use fastboot commands as long as you flash back 1.17 hboot?

[Edit] Ignore me, missed something. Scotsman said he couldn't flash a splash image once updated, but that was 1.20.
 

undercover

Senior Member
Oct 10, 2010
14,726
4,435
London, UK
He was testing fastboot commands. Reboot-bootloader worked but not FLASH commands. 1.20 hboot.
No need to flash it, because he already have exactly the same one. splash1.nb0 is the same since RUU_Pyramid_HTC_Europe_1.28.401.1_Radio_10.42.9007.00P_10.11.9007.15_M_release_192608_signed.exe



Sent from my HTC Sensation Z710e using XDA App
 

Catnap

Senior Member
Sep 24, 2010
957
453
No need to flash it, because he already have exactly the same one. splash1.nb0 is the same since RUU_Pyramid_HTC_Europe_1.28.401.1_Radio_10.42.9007.00P_10.11.9007.15_M_release_192608_signed.exe

I meant the new HBoot was stopping him flashing a custom splash image using fastboot as a test to see what was borked :)
 

mike1986.

Senior Member
He was testing fastboot commands. Reboot-bootloader worked but not FLASH commands. 1.20 hboot.



Sent from my HTC Sensation Z710e using XDA App

I meant the new HBoot was stopping him flashing a custom splash image using fastboot as a test to see what was borked :)

ah, so it's confirmed that fastboot "flash" commands doesn't work with new hboot. Thanks!
 

avihai1989

Member
Jul 21, 2011
15
0
make zip from ruu

Hi,
I tried to make my own rom from the new ICS RUU with kitchen.
All i did add is root, busybox. I zipalligned the apk's and change the update-script to updater-script.

When I flashed the rom, I didn't have all the built-in languages as the roms published here by others, and the home screen was text less...

Anybody knows why?
 

sjappie

Senior Member
Jan 15, 2006
261
31
Arnhem
Some conclusions based on users feedback after flashing RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.06.401.101_Radio_11.59.3504.00U_11.16.3504.16_M_test_231336.exe RUU:

1. It definitely doesn't brick the device. If you have Super-CID, it can be flashed even on regular Sensation (PG5813000)
2. It seems that most of those, who flashed it can tell that their device is now noticeable faster
3. It doesn't bring S-ON to your device
1. Yes, just flashed the RUU, all OK.
2. Yes, but not so mutch as everybody describes(!)
3. Device stays S-Off and unlocked at my device. I have hboot 1.20.

Now i'm back to your 3.8.9 with hboot 1.20, radio 10.58.9035.00U_10.15.9035.02_2 . No problems here!

Still i think its a bit to laggy for a daily driver. Especially when you get used to the speed of 3.8.9. I'll think a tweaked kernel and ROM will also solve the lag!
 

Catnap

Senior Member
Sep 24, 2010
957
453
If it's any use, ADSP (for the first post) seems to be related to audio (?) DSP for MSM devices. At least, that's about as much as I can find. It may well be radio as DSP is not necessarily audio.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 234
    This thread's content might brick your device.
    This is not a ROM thread, so I'm not going to answer again and again and again the same questions over and over and over again.
    You can't read - quit this thread now. You can read but you can't understand more or less simple things - quit as well.
    You can read and you understand things, but you are too lazy to read the whole thread before asking the question - watch this first. And quit.

    I compared the content of HTC Sensation and HTC Sensation XE RUU's.


    index1.php

    Some conclusions based on users feedback after flashing Sensation XE RUU:

    1. It definitely doesn't brick the device. If you have Super-CID, it can be flashed even on regular Sensation (PG5813000).
    2. It seems that most of those, who flashed it can tell that their device is now noticeable faster.
    3. It doesn't bring S-ON to your device.
    4. "fastboot flash <partition name> <file name.img>" doesn't work with new 1.20 hboot. But it's not really a problem, because most users doesn't use fastboot.

    Other conclusions:

    1. adsp.img is the same in all HTC Sensation and HTC Sensation XE RUUs. So it's irrelevant to us.
    2. pg2fs_spcustom.img is the same in all HTC Sensation and HTC Sensation XE RUUs. So it's irrelevant to us. This image wasn't in RUUs since the beginning. It came out first in 1.45.401.2 RUU.
    3. splash1.nb0 is the same in all HTC Sensation and HTC Sensation XE RUUs. So it's irrelevant to us. It's just a splash screen anyway.
    4. dzdata_4g.hdr and dzdata_4g.img came out first in 3.06.401.1/101 RUU. Before it was just one image - dzdata.img.
    5. rcdata.img is the same in all HTC Sensation and HTC Sensation XE RUUs. But it's different for HTC Sensation 4G U.S. T-Mobile and it contains some additional settings. It contains radio settings.
    6. radio.img and rcdata.img are radio related. Should affect better connectivity quality, but should not affect overall performance in any way.
    7. hboot_8x60_1.20.0000_20111215_signedbyaa.nb0, sbl1.img, sbl2.img, sbl3.img and tz.img are all (probably) bootloader related. It should not affect overall performance (probably).
    8. The only left is rpm.img which probably is relevant to us (as rmk40 also stated). But it doesn't mean it can be flashed just as a single image. Probably it has to be flashed with other
    images like radio or bootloader related to avoid risk of bricking the device.
    9. Because new images came out in new RUUs (dzdata_4g.hdr and dzdata_4G.img replaced dzdata.img) it's very possible that we need to flash new bootloader as well.
    10. ramdisk.img came out first in 3.06.401.1/101 RUU. It has the same content as ramdisk in boot.img and I have no idea why HTC made is as additional image (maybe even allocated partition for that?).
    11. dzdata_4G images are different in Sensation and Sensation XE RUU. Is it because Sensation XE supports less CID locations?
    12. Flashing dzdata_4g.hdr and dzdata_4g.img removes the content of userdata partition. In bootloader it's market as "userdata" file so it's probably not radio related.
    13. dzdata_4G.img contains QUALCOMM Logging tools (LOCAL_CFLAGS += -DFEATURE_DATA_LOG_SYSLOG #LOCAL_CFLAGS += -DFEATURE_DATA_LOG_ADB LOCAL_CFLAGS += -DFEATURE_DATA_LOG_QXDM) so it's irrelevant to us.

    Here is the partitions table from before and after flashing new firmware:


    index1.php



    sep9.png



    Download firmware for HTC Sensation (PG5813000, PG5811000 & PG5810000) & HTC Sensation XE (PG5813001)

    Firmware from 3.12.401.2/102 RUU
    --- MD5 checksum: FF644ED2BFF6A6058023C6FF36401E5C *PG58IMG.zip ---

    Supported devices:
    --- CID's added by users requests are marked with green color ---
    cidnum: 11111111
    cidnum: HTC__001
    cidnum: HTC__E11
    cidnum: HTC__N34
    cidnum: HTC__203
    cidnum: HTC__102
    cidnum: HTC__405
    cidnum: HTC__Y13
    cidnum: HTC__A07
    cidnum: HTC__304
    cidnum: HTC__032
    cidnum: HTC__016

    cidnum: HTC__044
    cidnum: HTC__038

    cidnum: VODAP203
    cidnum: VODAPE17
    cidnum: VODAP102

    Firmware from 3.24.401.1 & 3.25.401.101 RUU
    --- MD5 checksum: 4774D8928FB9D364F83CDDE16BAC4553 *PG58IMG.zip ---
    --- Only for 3.24.401.1 & 3.25.401.101 based ROMs

    Supported devices:
    --- CID's added by users requests are marked with green color ---
    cidnum: 11111111
    cidnum: HTC__001
    cidnum: HTC__E11
    cidnum: HTC__N34
    cidnum: HTC__203
    cidnum: HTC__102
    cidnum: HTC__405
    cidnum: HTC__Y13
    cidnum: HTC__A07
    cidnum: HTC__304
    cidnum: HTC__032
    cidnum: HTC__016

    cidnum: HTC__044
    cidnum: HTC__038

    cidnum: VODAP203
    cidnum: VODAPE17
    cidnum: VODAP102
    cidnum: VODAP001

    Firmware from 3.30.401.1 & 3.30.401.101 RUU
    --- MD5 checksum: 824295C6ACDC8D55BED9E0B913192DBE *PG58IMG.zip ---
    --- Only for 3.30.401.1 & 3.30.401.101 based ROMs

    Supported devices:
    --- CID's added by users requests are marked with green color ---
    cidnum: 11111111
    cidnum: HTC__001
    cidnum: HTC__E11
    cidnum: HTC__N34
    cidnum: HTC__203
    cidnum: HTC__102
    cidnum: HTC__405
    cidnum: HTC__Y13
    cidnum: HTC__A07
    cidnum: HTC__304
    cidnum: HTC__032
    cidnum: HTC__016

    cidnum: HTC__044
    cidnum: HTC__038

    cidnum: VODAP203
    cidnum: VODAPE17
    cidnum: VODAP102
    cidnum: VODAP001

    Firmware from 3.32.401.x & 3.32.401.10x RUU
    --- MD5 checksum: 74A8E07D40A42DA1B4B56C224C42E692 *PG58IMG.zip ---
    --- Only for 3.32.401.x & 3.32.401.10x based ROMs

    Supported devices:
    --- CID's added by users requests are marked with green color ---
    cidnum: 11111111
    cidnum: HTC__001
    cidnum: HTC__E11
    cidnum: HTC__N34
    cidnum: HTC__203
    cidnum: HTC__102
    cidnum: HTC__405
    cidnum: HTC__Y13
    cidnum: HTC__A07
    cidnum: HTC__304
    cidnum: HTC__032
    cidnum: HTC__016

    cidnum: HTC__044
    cidnum: HTC__038

    cidnum: VODAP203
    cidnum: VODAPE17
    cidnum: VODAP102
    cidnum: VODAP001

    Firmware from 3.33.401.6 & 3.33.401.106 RUU
    --- MD5 checksum: A28BABD1636C406FA953E56008128F31 *PG58IMG.zip ---
    --- Only for 3.33.401.6 & 3.33.401.106 based ROMs

    Supported devices:
    --- CID's added by users requests are marked with green color ---
    cidnum: 11111111
    cidnum: HTC__001
    cidnum: HTC__E11
    cidnum: HTC__N34
    cidnum: HTC__203
    cidnum: HTC__102
    cidnum: HTC__405
    cidnum: HTC__Y13
    cidnum: HTC__A07
    cidnum: HTC__304
    cidnum: HTC__032
    cidnum: HTC__016

    cidnum: HTC__044
    cidnum: HTC__038

    cidnum: VODAP203
    cidnum: VODAPE17
    cidnum: VODAP102
    cidnum: VODAP001

    Why it's better then full RUU:

    1. It doesn't contain stock recovery
    2. It doesn't contain stock, non rooted system
    3. It doesn't contain secured boot.img
    4. It wont wipe your data partition
    5. It's much smaller :D

    PG58IMG.zip content: [UPDATE: 22.02.2012]

    adsp.img - updated [11.07.2012] - This is needed for 3.12.xxx.x/3.24.xxx.x/3.25.xxx.x/3.30.xxx.x/3.32.xxx.x/3.33.xxx.x based ROM to boot!
    android-info.txt - updated [011.07.2012]
    dzdata_4g.hdr - removed from the package [28.12.2011]
    dzdata_4g.img - removed from the package [28.12.2011]
    hboot_8x60_1.29.0000_20120302_signedbyaa.nb0 (with locked fastboot) - updated [11.07.2012]
    pg2fs_spcustom.img - removed from the package [01.03.2012]
    radio.img - updated [11.07.2012]
    rpm.img - updated [11.07.2012]
    sbl1.img - updated [20.01.2012]
    sbl2.img - updated [22.02.2012]
    sbl3.img - updated [20.01.2012]
    tz.img - updated [11.07.2012]

    How to flash:

    1. Check your CID using fastboot getvar cid and MID using fastboot getvar mid
    2a. If your CID and MID are supported by default, navigate to point 3.
    2b. If your CID or MID is not supported by default, do this: (you do it at your own risk)
    2c. Open PG58IMG.zip (don't extract it)
    2d. Open android-info.txt in text editor
    2e. Add your cidnum: <your CID> or modelid: <your MID> to the list, save file and close archive
    3. Place PG58IMG.zip on your SD card
    4. Boot your device holding power button + vol down button
    5. Follow instructions on the screen

    Additional information:

    1. Flash above firmware at your own risk!
    2. It's recommended to flash it before flashing custom ROM based on proper RUU!
    3. HTC Sensation variants:

    PG5813000 - HTC Sensation
    PG5813001 - HTC Sensation XE
    PG5810000 - HTC Sensation 4G
    PG5811000 - HTC Sensation in Telstra network

    4. RUU variants:
    x.xx.61.x - Orange UK (United Kingdom)
    x.xx.69.x - Orange PL (Poland)
    x.xx.73.x - Orange FR (France)
    x.xx.75.x - Orange ES (Spain)
    x.xx.110.x - T-Mobile UK (United Kingdom)
    x.xx.111.x - T-Mobile DE (Germany)
    x.xx.113.x - T-Mobile CZ (Czech Republic)
    x.xx.161.x - Vodafone UK (United Kingdom)
    x.xx.163.x - Vodafone FR (France)
    x.xx.165.x - Vodafone IT (Italy)
    x.xx.168.x - Vodafone GR (Greece)
    x.xx.206.x - O2 UK (United Kingdom)
    x.xx.401.x - World Wide English
    x.xx.468.x - Turkey
    x.xx.497.x - Morocco
    x.xx.498.x - WWE Brightpoint US (United States)
    x.xx.531.x - T-Mobile US (United Kingdom)
    x.xx.666.x - Bell Canada
    x.xx.707.x - Asia WWE (World Wide English)
    x.xx.709.x - Asia TW (Taiwan)
    x.xx.720.x - Asia India
    x.xx.771.x - Hutchison 3G UK (United Kingdom)
    x.xx.841.x - Telsra WWE (World Wide English)
    x.xx.862.x - Voda-Hutch AU (Australia)
    x.xx.901.x - TIM IT (Italy)
    x.xx.911.x - SK Telecom (South Korea)
    x.xx.1400.x - HTC China
    x.xx.1403.x - HTC China CMCC (China Mobile Communications Corporation)

    I did some research myself, but I also used info from here and here

    Please post here your findings, thoughts or experience with after flashing images listed above.
    30
    Quick update:

    Since losing the unlocked bootloader itself is a Bad Thing [tm] (and I wanted to flash the 3.24 ROM) I patched up HBOOT 1.27.0000.

    Packaged it up nicely with the 3.24 firmware:

    3.24 PG58IMG zip with Revolutionary-patched HBOOT.

    Enjoy.
    11
    Some conclusions based on users feedback after flashing RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.06.401.101_Radio_11.59.3504.00U_11.16.3504.16_M_test_231336.exe RUU:

    1. It definitely doesn't brick the device. If you have Super-CID, it can be flashed even on regular Sensation (PG5813000)
    2. It seems that most of those, who flashed it can tell that their device is now noticeable faster
    3. It doesn't bring S-ON to your device
    10
    k will do asap

    You will do what?
    8
    New firmware from 3.30.401.x ruu's in the first post.