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.
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:
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
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:
Some conclusions based on users feedback after flashing RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.06.401.101_Ra dio_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
Archived devices and my other threads:
These threads are still open, but support is limited to rare updates.
Some conclusions based on users feedback after flashing RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.06.401.101_Ra dio_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.
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.
Archived devices and my other threads:
These threads are still open, but support is limited to rare updates.
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.
Archived devices and my other threads:
These threads are still open, but support is limited to rare updates.
Interesting. Do you have any conclusions thus far?
[Edit] What I mean is; are you saying that only the rpm image has the potential to offer any real benefits?
<- wat
If you're reading this, congrats. You are better at reading than most of these forums.
Ubuntu has become the most successful *nix distribution for a number of reasons, … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?