Database Info

[Q] RUU and Recovery

Isn't the problem of installing OTA updates is the Recovery used by Clockworld mod? Why not just flash in the stock recovery instead of clockword mod?
I don't know if that is possible, but I'll just say what I see and tell me if I'm wrong
The PG58IMG.zip used for flashing Clockworld mod, contained an image called "recovery.img" which is basically available for those CIDs
Code:
HTC__001
HTC__E11
HTC__032
HTC__102
HTC__Y13
HTC__203
HTC__405
HTC__N34
HTC__304
HTC__A07
HTC__016
HTC__J15
So, my CID is HTC__J15, can't I use the "recovery_signed.img" in the "rom.zip" of the RUU to flash my old recovery? I can't see why it may not be possilble of creating a "PG58IMG.zip" and write in an andoid-info.txt with this:
Code:
modelid: PG5813000
cidnum: HTC__J15
mainver: 1.34.415.1
hbootpreupdate:0
DelCache:1
or just flashing using ADB the recovery_signed.img and we're done?
What you think?
Please gently tell me if I'm wrong, I'm just willing to learn and know more about this
Thank you

Nobody? Should this be posted in development?
Sent from my HTC Sensation Z710e using XDA App

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

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.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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:
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
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.

k will do asap

homais said:
k will do asap
Click to expand...
Click to collapse
You will do what?

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

mike1986. said:
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
Click to expand...
Click to collapse
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.

tinker2000 said:
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.
Click to expand...
Click to collapse
You can also flash PG58IMG.zip. I will prepare such package without hboot, sbl and other irrelevant stuff.

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.

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?

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

tinky1 said:
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
Click to expand...
Click to collapse
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?

mike1986. said:
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?
Click to expand...
Click to collapse
[Edit] Ignore me, missed something. Scotsman said he couldn't flash a splash image once updated, but that was 1.20.

First post updated with new info.

Catnap said:
[Edit] Ignore me, missed something. Scotsman said he couldn't flash a splash image once updated, but that was 1.20.
Click to expand...
Click to collapse
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

He was testing fastboot commands. Reboot-bootloader worked but not FLASH commands. 1.20 hboot.
mike1986. said:
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
Click to expand...
Click to collapse
Sent from my HTC Sensation Z710e using XDA App

mike1986. said:
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
Click to expand...
Click to collapse
I meant the new HBoot was stopping him flashing a custom splash image using fastboot as a test to see what was borked

tinky1 said:
He was testing fastboot commands. Reboot-bootloader worked but not FLASH commands. 1.20 hboot.
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
Catnap said:
I meant the new HBoot was stopping him flashing a custom splash image using fastboot as a test to see what was borked
Click to expand...
Click to collapse
ah, so it's confirmed that fastboot "flash" commands doesn't work with new hboot. Thanks!

mike1986. said:
ah, so it's confirmed that fastboot "flash" commands doesn't work with new hboot. Thanks!
Click to expand...
Click to collapse
Yep:
http://forum.xda-developers.com/showpost.php?p=20727312&postcount=94

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?

mike1986. said:
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
Click to expand...
Click to collapse
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!

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.

[Q] Opening Only Bootloader

Hey all, i have a very big problem.
i don't know how can i fix. My Desire S is opening only boot loader mode and i want to install latest rom version for turkey or europe (are those versions same?)
1 month ago an update available in turkey and i want to install bu i didn't cause i rooted my phone and s-off before. After i tried to make all settings original: now my phone is s-on and i can load any ROM with RUU. When i try to install an error is becoming: Error [131]: Customer ID Error. i have no gold card and no other phone to prepare.
*** Security Warning ***
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-3822.10.08.04_M
eMMC-boot
Mar 10 2011, 14:58.38
I haven't been using my phone for 1 month. Please help me.

you need to change the cid of your phone.
therefor youneed an unlocked bootloader and fastboot.
check this thread
http://forum.xda-developers.com/showthread.php?t=1192300
and start reading at
STEP 4. WRITE SUPER CID [YOU ONLY NEED TO DO THIS ONCE]
the thread is in the sensation forums but changin the cid is the same.
get the supercid (11111111) (able to install every rom) or the cid the rom youre trying to flash is asking for.
a list of all cids
Code:
SuperCID 11111111
Asia-HK-CHT HTC__622
ATT CWS__001
BM BM_001
Bouygues-Telecom BOUYG201
Brightstar-PTB BSTAR502
Brightstar-SPA BSTAR301
Chunghwa-Taiwan CHT__601
CT HTCCN702
CU HTCCN703
DCM DOCOM801
DOPOD DOPOD701
Era T-MOB009
Fastweb-IT FASTW401
GOOGLE GOOGL001
H3G-DAN H3G__F05
H3G-Italy H3G__402
H3G-ROI H3G__003
H3G-SWE H3G__G04
H3G-UK H3G__001
HTC-Asia-SEA HTC__037
HTC-Asia-SEA-WWE HTC__044
HTC-Australia HTC__023
HTC-BE HTC__E41
HTC-Czech HTC__C24
HTC-Denmark HTC__F08
HTC-Dutch HTC__E11
HTC-EastEurope HTC__032
HTC-ELL HTC__N34
HTC-FRA HTC__203
HTC-FRA-Bouygues HTC__247
HTC-GCC HTC__J15
HTC-GER HTC__102
HTC-India HTC__038
HTC-ITA HTC__405
HTC-Nor HTC__Y13
HTC-Norway HTC__H10
HTC-Poland HTC__B25
HTC-PTG HTC__506
HTC-Russia HTC__A07
HTC-SPA HTC__304
HTC-Sweden HTC__G09
HTC-Turkey HTC__M27
HTC-WWE HTC__001
Hutch-Australia HUTCH001
O2-DE O2___102
O2-UK O2___001
Open-Channel HTCCN701
Optus-Australia OPTUS001
ORANGE-AT ORANG113
ORANGE-BE ORANG012
ORANGE-CH-FRA ORANG203
ORANGE-CH-GER ORANG104
ORANGE-ES ORANG309
ORANGE-French ORANG202
ORANGE-PL ORANGB10
ORANGE-PO ORANG008
ORANGE-SK ORANG006
ORANGE-UK ORANG001
Rogers ROGER001
SMC-Voda-HK SMCVD001
TELEF-Spain TELEF301
Telstra TELST001
TELUS TELUS001
TIM-Italy TIM__401
TMA T-MOB102
TMCZ T-MOB004
TMD T-MOB101
TMH T-MOB007
TMHR T-MOB006
TMMK T-MOBL11
TMNL T-MOB003
TMSK T-MOB008
TMUK T-MOB005
TMUS T-MOB010
TWM-TW HTC__621
VIRGIN-UK VIRGI001
VODA-Africa-South HTC__016
VODA-Australia VODAP021
VODA-Germany VODAP102
VODA-Greece VODAP006
VODA-Ireland VODAP019
VODA-Italy VODAP405
VODA-Mobilkom VODAP120
VODA-Netherland VODAPE17
VODA-New-Zealand VODAP022
VODA-Portugal VODAPD18
VODA-Proximus VODAP024
VODA-SA VODAP026
VODA-SFR VODAP203
VODA-Spain VODAP304
VODA-Swisscom-DE VODAP110
VODA-Swisscom-FR VODAP212
VODA-Swisscom-IT VODAP416
VODA-Swisscom-WWE VODAP015
VODA-TR VODAPM27
VODA-UK VODAP001
[email protected]://www.handy-faq.de/forum/htc_sensation_forum/215188-so_bekommt_supercid.html

I Can't Write CID
Thanks but i cant write cid because of an error:
"... INFO[ERR] Commad Error !!!"
I think my phone isnt able to writing cid cause is S-ON and i cant make it S-OFF, its opening ony bootloader.

@sky_tr
Can you post command "fastboot getvar all" results.

Hey, here is the results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.401.1
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__M27
(bootloader) battery-status: good
(bootloader) battery-voltage: 4060mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0

@sky_tr
Yeah it doesn't look to good.
You need to look into making a Goldcard on the PC with a SDcard reader.
How did you s-off your phone and how did you get stock again?
You can have a look at this thread, similar problem, however your problem is that your cid (not your mainversion as the linked thread).
So if you can get a goldcard made (not sure if someone else can make it for you) then you should be golden.
Edit;
Ypu can try this (needs a sd card reader I think); the thread is here
Also, you can MAYBE get the cid on the memory card using a old windows mobile phone and using the app from http://psas.revskills.de/

hey thank you, but i haven't fixed yet..

Try have a look at this thread here

On first, I'm not the writer of this help, I just wante to send it for all xda 's users who's got the same problem.
1.First I put my mem card into my laptops or computer card reader
2.I downloaded readcid.exe from here: jo0ls' .Net stuff: Read secure digital (SD) card serial number from the CID
3.I formatted my 2gb micro sd (not quick format)
4.I ran readcid.exe as an administrator
5.I copied the cid no as it is and pasted it in sd card serial (CID) (link: psas.revskills.de/?q=goldcard)
6.I downloaded the goldcard.img file
7.I downloaded HxD Hex Editor from here: HxD - Freeware Hex Editor and Disk Editor | mh-nexus
8.I clicked on extras open disk and selected my microsd card
9.I clicked on extras open disk image and selected goldcard.img
10.Then I got 2 tabs.
11.I opened the second tab (goldcard.img) edit- select all
12.I opened the first tab (microsd) *selected lines 1-170* then paste write
13.I clicked on save and my goldcard was ready
14.I downloaded RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30. 0822U_3822.10 from here: FileFactory Folder view - Saga
15.I removed my goldcard from my laptop's card reader and put it in my htc desire s and restarted the phone in fastboot
16.I downloaded htc fastboot drivers from here: public:revolutionary [RootWiki]
17.I connected the usb cable on my laptop and then on my phone where i got installing drivers android 1.0 (I am using windows 7 by the way)
18.My phone was in fastboot usb mode and i then ran RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30. 0822U_3822.10 which finished successfully and then my phone restarted and I saw the new htc logo instead of the t-mobile one!
19.I removed my goldcard and put it somewhere safe just in case
20. What I've read during the whole process is that in case of ota updates i will have to reinsert the goldcard before the installation but i am not sure whether this is valid or not.
Click to expand...
Click to collapse
Thanks again @FoX777 and thank's for @kashoulis too

I did everything step by step but same error: Error [131]: Customer ID Error.

sky_tr said:
I did everything step by step but same error: Error [131]: Customer ID Error.
Click to expand...
Click to collapse
It's coming from your goldcard.
I think that you have had several times this error during the rom's flash. It's important that you select in the editing of the card with HxD, 'physical disk' and not the logical disk'

Thanks, i corrected my mistake but already same error Error Code 131.. :S

Then you didn't make the make the card correctly.

foX2delta said:
Then you didn't make the make the card correctly.
Click to expand...
Click to collapse
My sd card Samsung 8 GB, should i use 2 GB ??
If i have a gold card can i fix all these problems and load any RUU?
And here is another problem:
HBOOT
SD Checking ...
Loading ... [PG88DIAG.zip]
No Image!
Loading ... [PG88DIAG.nbh]
No image or wrong image!
Loading ... [PG88IMG.zip]
-----------------------------------------------
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.401.1
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__M27
(bootloader) battery-status: good
(bootloader) battery-voltage: 4060mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0

Use your 2GB, and maybe that is your Samsung Sdcard don't appreciate by your DS.
Sometimes, some SDcard aren't good for some phone.
I have read on several forums, that there were problems with the Samsung's SD cards.

I've personally used a 2GB SanDisk HC card as my GoldCard. Rescued a friend's phone with it, and have kept it safely stashed away, boldly labeled as "GOLDCARD- When all else fails"
Dunno about Samsung cards....started hating Samsung ever since i found out their eMMC was the reason our DS was falling dead all over the world, so i keep away from their products now.

philos64 said:
Use your 2GB, and maybe that is your Samsung Sdcard don't appreciate by your DS.
Sometimes, some SDcard aren't good for some phone.
I have read on several forums, that there were problems with the Samsung's SD cards.
Click to expand...
Click to collapse
I 've just bought a 2 GB Kingston and i tried making goldcard but same error i don't understand i did everything step by step i can see any mistake..
This is the CID written on the top at cmd screen:
B100970C99A66047323044534D540200
and i wrote it backwards in this web site: http://psas.revskills.de/?q=goldcard like this:
002045D43544032374066A99C079001B
so first two digits already zeros. I tried both (reversed and not reversed)
--------------------
\\.\PhysicalDrive1 F:\
--------------------
Raw CID Bytes: B1-00-97-0C-99-A6-60-47-32-30-44-53-4D-54-02-00
--------------------
Manufacturer ID: 2
OEM ID: TM
Product Name: SD02G
Product Revision: 6.0
Product Serial Number: a6990c97
Manufacture Date: 1/2011
--------------------
Raw CSD Bytes: 00-80-16-80-FF-FF-FF-A9-83-5A-5B-5A-00-2E-00-00
--------------------
CSD Version 2 bit value: CSD Version 1.0
Data Read Access Time 1 (TAAC): 2ms
Data Read Access Time 2 (NSAC): 0
Max Data Transfer Rate: 50Mbit/s
Card Command Classes: 010110110101
Max Read Data Block Length: 10
Partial Blocks For Read Allowed: True
Write Block Misalignment: False
Read Block Misalignment: False
DSR Implemented: False
Device Size: 3751
Max Read Current @ VDD Min: 100mA
Max Read Current @ VDD Max: 200mA
Max Write Current @ VDD Min: 100mA
Max Write Current @ VDD Max: 200mA
Device Size Multiplier: 15
Erase Single Block Enable: True
Erase Sector Size: 128
Write Protect Group Size: 1
Write Protect Group Enable: False
Write Speed Factor: 32
Max Write Data Block Length: 2^10
Partial Blocks For Write Allowed: False
File Format Group: False
Copy Flag (OTP): False
Permanent Write Protection: False
Temporary Write Protection: False
File Format: 0
As a result:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

And you are making the gold card right? Using a hex editor, replacing 0 to 170 and so forth?

foX2delta said:
And you are making the gold card right? Using a hex editor, replacing 0 to 170 and so forth?
Click to expand...
Click to collapse
yepp
And i found a solution here:
I solved the problem... The CID I was getting from gold card tool on PC was wrong! Actualy, I downloaded golden card helper from market, and that app read two CID-s from my card. One was the same like the one I got with PC app, and the other one was different! I tried with that different, and everything worked. Thanks for help!
Click to expand...
Click to collapse
but my phone is not work..

SplashScreen Creator for M8

Hi,
this is not my work, i've only modified for m8!!!!
Original Thread: http://forum.xda-developers.com/showthread.php?t=2475084
Download: https://www.dropbox.com/sh/fjxmey2q266k0jl/cfpe5MS9-o
german and english version available
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
regards
starbase64

The android_info.txt needs to be updated for the M8. Heres the one I use for my developer M8. It should work for all of them though.
Code:
modelid: 0P6B12000
cidnum: 11111111
cidnum: 22222222
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__102
cidnum: HTC__203
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__A07
cidnum: HTC__J15
cidnum: HTC__016
mainver: 1.28.401.7
btype:1
aareport:1
DelCache:1
hbootpreupdate:3

Hi,
both files updated, my mistake sorry.
Code:
modelid: 0P6B10000
cidnum: HTC__001
cidnum: HTC__102
cidnum: HTC__203
cidnum: HTC__E11
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__304
cidnum: HTC__A07
cidnum: HTC__032
cidnum: HTC__J15
cidnum: HTC__016
cidnum: HTC__M27
cidnum: HTC__K18
cidnum: HTC__A48
cidnum: HTC__002
mainver: 1.54.401.5
btype:1
aareport:1
hbootpreupdate:12
regards
starbase64

For some reason this is not working for me? It appears to flash but I still have my same splash image...

Doesn't work.
Sent from my HTC One_M8 using Tapatalk

In your ZIPs, try moving splash1.img to the root of the ZIP, then rename it to splash1.nb0. Also replace android-info.txt if it doesn't match my earlier post. It should work then.

Hi,
both files update, please reload from dropbox.
regards
starbase64
new code with splash.nb0 said:
IF EXIST "image\splash.nb0" (
del image\splash.nb0
)
IF EXIST "flash" (
rd flash /s /q
)
mkdir flash
tools\ffmpeg -i image\splash.png -f rawvideo -y -pix_fmt rgb565 image\splash.nb0
xcopy "tools\android-info.txt" "flash" /i /y
xcopy "image\splash.nb0" "flash" /i /y
tools\7za a -tzip splash.zip .\flash\*
del flash\*.* /q
del image\splash.nb0
move splash.zip flash
Click to expand...
Click to collapse

Just tried this on my International One M8.....had to rename the .nb0 file in the zip from splash.nb0 to splash1.nb0, but after that it worked great. Thanks for posting

thanks for your reply.

fisha21 said:
Just tried this on my International One M8.....had to rename the .nb0 file in the zip from splash.nb0 to splash1.nb0, but after that it worked great. Thanks for posting
Click to expand...
Click to collapse
For you guys ' reference, hint..it's here
mmcblk0p12: 00500000 00000200 "sp1"
so you know how to get it for flash zip
run_program("/sbin/busybox", "dd", "if=/cache/splash.565", "of=/dev/block/mmcblk0p12");
I will suggest using image convert to rgb565 file and put in cache for flash zip
here is one example you guys can try...
see attached, forgot who did that screen, thanks for that..

Do u have to be s-off to flash this?

lulu217783 said:
Do u have to be s-off to flash this?
Click to expand...
Click to collapse
Yes
---------- Post added at 03:10 PM ---------- Previous post was at 02:56 PM ----------
Onepagebook said:
For you guys ' reference, hint..it's here
mmcblk0p12: 00500000 00000200 "sp1"
so you know how to get it for flash zip
run_program("/sbin/busybox", "dd", "if=/cache/splash.565", "of=/dev/block/mmcblk0p12");
I will suggest using image convert to rgb565 file and put in cache for flash zip
here is one example you guys can try...
see attached, forgot who did that screen, thanks for that..
Click to expand...
Click to collapse
Thanks for confirming this for me!
I reused my favorite M7 Splash Screen on my M8, simply by editing the original updater-script and pointing it to mmcblk0p12

My first splashscreen Flash it with this program.
Supported CID :
modelid: 0P6B10000
cidnum: 11111111
cidnum: HTC__001
cidnum: HTC__102
cidnum: HTC__203
cidnum: HTC__E11
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__304
cidnum: HTC__A07
cidnum: HTC__032
cidnum: HTC__J15
cidnum: HTC__016
cidnum: HTC__M27
cidnum: HTC__K18
cidnum: HTC__A48
cidnum: HTC__002
mainver: 1.54.401.5
btype:1
aareport:1
hbootpreupdate:12

Worked like a charm. Thank you.

Doesn't seem to work for me. I place the png in the image and press 1 to convert to flashable zip. It creates a zip but there is nothing inside the zip.

Request!
Hey I know this is a big request but can someone make a universal HTC One M8 "BIOS" Splash?
I had this one back on my mytouch 4g and love it. Below is an uploaded picture for example

VZW_001
Will this work with the script? (see attached image)

Thanks
First you need rename the "splash1.img" to "splash1.nb0". Then change the android-info.txt (make sure it includes your device's cid and mid). Flash it. This is mine example.
View attachment splash.zip

Is there any way to get this to work in Linux? I haven't owned a Windows pc in forever
Sent from my HTC One_M8 using XDA Premium 4 mobile app

Onepagebook said:
For you guys ' reference, hint..it's here
mmcblk0p12: 00500000 00000200 "sp1"
so you know how to get it for flash zip
run_program("/sbin/busybox", "dd", "if=/cache/splash.565", "of=/dev/block/mmcblk0p12");
I will suggest using image convert to rgb565 file and put in cache for flash zip
here is one example you guys can try...
see attached, forgot who did that screen, thanks for that..
Click to expand...
Click to collapse
Please don't do this.
Use:
/dev/block/platform/msm_sdcc.1/by-name/sp1
instead
Sure, they should all be the same, but if it were to ever change for some variant or something, this could very likely brick devices.
Also - if someone were to try this on their M9 (yea, stupid but someone will, I promise) it could be bad too.

Unbrand and update 3UK S4 on 1.06 hboot

Hello, I could use a little help, as I cannot flash recovery on branded 3-Mobile UK phone (S4 processor).
I have unlocked the bootloader via htcdev.
More phone info via fastboot getvar all :
Code:
version: 0.5
version-bootloader: 1.06.0000
version-baseband: 0.15.31501S.19_2
version-cpld: None
version-microp: None
version-main: 1.53.771.4
serialno: HT242W411761
imei: ***
product: vle
platform: HBOOT-8960
modelid: PJ4010000
cidnum: H3G__001
battery-status: good
battery-voltage: 4018mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 802fa374
hbootpreupdate: 11
gencheckpt: 0
CID is H3G__001 and HBOOT is 1.06.0000
I have tried flashing both CWM and TWRP from fastboot, but though it seems everything goes well, when I reboot to recovery, it gives me the generic HTC recovery screen (the one with the little bar on the top right of the screen) and reboots after a while to the branded ROM. I think it reflashes the branded recovery automatically, because the bar is proceeding and then reboots the phone.
I cannot root or change CID without custom recovery.
Do I need to flash a boot.img (and which one)?
Thank you in advance!
*UPDATE*
OK, I managed to install an older version of TWRP (2.6.3.0).
What must I do to update hboot and install newer ROMS?

Candlemass said:
Hello, I could use a little help, as I cannot flash recovery on branded 3-Mobile UK phone (S4 processor).
I have unlocked the bootloader via htcdev.
More phone info via fastboot getvar all :
Code:
version: 0.5
version-bootloader: 1.06.0000
version-baseband: 0.15.31501S.19_2
version-cpld: None
version-microp: None
version-main: 1.53.771.4
serialno: HT242W411761
imei: ***
product: vle
platform: HBOOT-8960
modelid: PJ4010000
cidnum: H3G__001
battery-status: good
battery-voltage: 4018mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 802fa374
hbootpreupdate: 11
gencheckpt: 0
CID is H3G__001 and HBOOT is 1.06.0000
I have tried flashing both CWM and TWRP from fastboot, but though it seems everything goes well, when I reboot to recovery, it gives me the generic HTC recovery screen (the one with the little bar on the top right of the screen) and reboots after a while to the branded ROM. I think it reflashes the branded recovery automatically, because the bar is proceeding and then reboots the phone.
I cannot root or change CID without custom recovery.
Do I need to flash a boot.img (and which one)?
Thank you in advance!
*UPDATE*
OK, I managed to install an older version of TWRP (2.6.3.0).
What must I do to update hboot and install newer ROMS?
Click to expand...
Click to collapse
your phone's security is on. I would recommend do the following:
1) S-off ur phone
2) change CID to supercid
3) Run any new RUU
4) Re-flash TWRP
5) Enjoy

bilal_liberty said:
your phone's security is on. I would recommend do the following:
1) S-off ur phone
2) change CID to supercid
3) Run any new RUU
4) Re-flash TWRP
5) Enjoy
Click to expand...
Click to collapse
Thank you for your answer and congrats on your ROM (it is the one I'm running right now ).
I managed to solve the issues yesterday, but the information was so scattered around, it took me half a day (along with the sloooow downloads).
For anyone interested, the procedure was like this :
1) Unlock bootloader via htcdev.com and identifier token
2) Flash TWRP 2.6.3.0
3) Root
4) SuperCID
5) S-OFF
6) Change CID to HTC__001
7) Update HBOOT to 2.15 via firmware flash
8) Run newest RUU
9) Flash newest radio
10) Re-flash TWRP
11) Flash Custom ROM
Step 8 can be skipped, but I wanted to see if it ran the stock ROM ok.
In more detail, with links and files :
Initially the phone was branded on 3UK with CID H3G__001, HBOOT 1.06 and MID PJ4010000.
Code:
version: 0.5
version-bootloader: 1.06.0000
version-baseband: 0.15.31501S.19_2
version-cpld: None
version-microp: None
version-main: 1.53.771.4
serialno: HT242W411761
imei: ***
product: vle
platform: HBOOT-8960
modelid: PJ4010000
cidnum: H3G__001
battery-status: good
battery-voltage: 4018mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 802fa374
hbootpreupdate: 11
gencheckpt: 0
The safest way to update my HBOOT to 2.15 or 2.16 was via a latest official RUU from here http://www.androidruu.com/?developer=Ville . But the latest RUU matching my CID was a bit old (RUU_Ville_U_H3G_UK_1.78.771.5_Radio_0.16.31501S.19_2_10.23.31501S.10L_release_258982_signed) and I didn't know which HBOOT it contained, so I decided to update using the latest European RUU (RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4). In order to do this, I would have to chance CID to something corresponding (i.e. HTC__001 or HTC__N34 for my region - ELL).
(1)
I began with the thread [Tutorial]Root, Unlock, Recovery and flashing a Custom ROM, but got stuck on the recovery flashing, that's when I started this thread. I flashed the latest TWRP (2.7.0.0) and latest CWM (6.0.4.8) but they didn't work.
The recovery boot acted as described in the OP (gave me the generic HTC recovery screen) and tried multiple times. Then I remembered reading something like that the newest recoveries work differently to support newest hboot, so I tried the previous version (TWRP 2.6.3.0 from http://techerrata.com/browse/twrp2/ville ) and it worked.
(2-3)
TWRP also offered to root the ROM by installing supersu automatically, so I didn't have to flash it myself. After the reboot to system, I installed supersu from market, updated su binary and the root access was complete. The rooting was necessary so that we can change the CID to SuperCID.
(4)
SuperCID can be set following this guide [UNLOCK] AT&T Bootloader Unlock Through HTC-Dev. I changed H3G__001 to 11111111 with HxD (needs care not to change more that those 8 bytes and check that the size remains the same - mine was 1024B).
(5)
Next stop is S-OFF via Facepalm with the help of this thread [S-Off] Facepalm S-Off for HTC Devices One S, One XL, Droid DNA. It worked right away, following exactly the procedure as described.
(6)
I changed CID to HTC__001 , not leaving SuperCID on, because there were reports of bricks when flashing OTA updates. Just wanted to be on the safe side.
Easy from fastboot with S-OFF :
Code:
fastboot oem writecid HTC__001
(7-8)
The next step was to flash the latest RUU (RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4), in order to update my HBOOT to 2.15. But this came to a halt, as the RUU didn't proceed, giving me error 159. More info and solution on this matter can be found in the thread RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1. 11.50.05.28_10.27.50.08L_release.
In short, the problem is that the ROM.zip inside the RUU is encrypted and we either had to decrypt it using ruuveal via linux, or to use the already decrypted by hasoon2000 zip ( http://forum.xda-developers.com/showpost.php?p=40925380&postcount=79 ).
As I also mentioned in that said thread ( http://forum.xda-developers.com/showpost.php?p=52852710&postcount=123 ), if you update the HBOOT manually, by flashing corresponding firmware, the RUU flashing proceeds without any issues.
So, I followed the thread [GUIDE][TOOL]FUU/FirmwareHTC One S and flashed the Official Unbranded 2.15 Firmware (Sense) zip via fastboot. The result was an updated HBOOT to 2.15 and the ability to flash the official RUU. With S-OFF there is no need to relock the bootloader.
(9-10-11)
After that, I simply reflashed TWRP and the custom ROM Liberty-S4-V7a. I skipped the manual radio flash, because Liberty ROM had the option to flash it from AROMA installer automatically. For other ROMs, it is a simple flash via fastboot.
Simple, hah