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

[HTC ONE M7] Collection of Firmware up to 6.06.401.1 modified HBOOT, (No Red warning)

Hi Everyone,
OP UPDATE: DON'T reboot your device until you get a success message, also double check you understand EVERY STEPS before trying it out. I AM NOT RESPONSIBLE FOR ANYTHING IF YOU MESS UP THE STEPS...!!
This firmware is WITH OUT the development disclaimer overlay:
This build is for
development purposes only
Do not distribute outside of HTC
without HTC's written permission.
Failure to comply may
lead to legal action.​
** With Latest Radio **
Upgrade your HTC Sync to 3.1.13.0 if you flash this firmware..
DOWNLOAD Firmware 6.06.401.1, NO Red Warning, --md5: -- dd9f5fb8416de0fb6f533ce3e40bbafe
These Firmwares DO NOT delete the contents in SD Card. But please make a back up before flashing for safety.
**N.B. Thanks and Donations are most welcome **
Requirements for flashing: S-OFF
Please Follow the instructions carefully!! Otherwise you may BRICK your device.
Please note that it is for the HTC One M7 UL Only. Not Tested with Sprint Version!!
You may change the MID (at your own risk) in the android-info.txt attached and replace the one inside the firmware.zip if you have another MID.
If you have Super CID "11111111", you don't need to worry about the CID lists inside the android-info.txt file
​
DON'T FORGET TO CLICK THANKS IF YOU FIND THIS THREAD USEFUL.
Dear All,
I have noted a lot downloads of the firmware and most of them just don't even bother clicking thanks :silly:
I appreciate your encouragements and appreciation for my work so that it will give motivation to keep all you updated.
Thanks a lot for everyone contributed..
Thanks @thoughtlesskyle for this video tutorial http://youtu.be/ybu7fZa41so
​
To Check ModelIDs:
Code:
adb reboot bootloader
----- Mobile reboots---
Code:
fastboot getvar all
----Check the following line in the command window: INFOmodelid: PN0714000----
Steps for flashing:
-----
Windows users, need to do these steps first:
- move the file you downloaded and renamed (firmware.zip) to the C:\adb\ folder.
- next, in the C:\adb\ folder hold down SHIFT key and RIGHT-CLICK and select "Open command window here".
-----
Next, plug in phone to PC and type this in terminal/command prompt:
Code:
adb reboot bootloader
----- Mobile reboots---
Now type:
Code:
fastboot reboot-bootloader
After that, type:
Code:
fastboot oem rebootRUU
Note: You should see a silver HTC logo come up on your phone after executing this command.
Note: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
fastboot flash zip C:\adb\firmware.zip
Got this:
Code:
sending 'zip' (30367 KB)... OKAY [ 6.184s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] flushing...
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,99
INFO[RUU]WP,hboot,100
INFO...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 8.090s
Repeat the same command: !! IMPORTANT !! -- PLEASE WAIT A FEW SECONDS BEFORE ISSUING THE COMMAND AGAIN; Otherwise the cmd prompt will be non-responsive saying "Sending data...", If this happens, try disconnecting the USB cable and reconnect.
Code:
fastboot flash zip C:\adb\firmware.zip
You will see this:
Code:
sending 'zip' (30367 KB)... OKAY [ 3.277s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOstart image[adsp] unzipping & flushing...
INFO[RUU]UZ,adsp,0
INFO[RUU]UZ,adsp,18
INFO[RUU]UZ,adsp,30
INFO[RUU]UZ,adsp,41
INFO[RUU]UZ,adsp,52
INFO[RUU]UZ,adsp,64
INFO[RUU]UZ,adsp,75
INFO[RUU]UZ,adsp,86
INFO[RUU]UZ,adsp,97
INFO[RUU]UZ,adsp,100
INFO[RUU]WP,adsp,0
INFO[RUU]WP,adsp,100
INFO...... Successful
INFOstart image[cir] unzipping & flushing...
INFO[RUU]UZ,cir,0
INFO[RUU]UZ,cir,100
INFO...... Successful
INFOstart image[pg2fs_spcustom] unzipping & flushing...
INFO[RUU]UZ,pg2fs_spcustom,0
INFO[RUU]UZ,pg2fs_spcustom,31
INFO[RUU]UZ,pg2fs_spcustom,57
INFO[RUU]UZ,pg2fs_spcustom,82
INFO[RUU]UZ,pg2fs_spcustom,100
INFO...... Successful
INFOstart image[rpm] unzipping & flushing...
INFO[RUU]UZ,rpm,0
INFO[RUU]UZ,rpm,100
INFO[RUU]WP,rpm,0
INFO[RUU]WP,rpm,100
INFO...... Successful
INFOstart image[sbl1-1] unzipping & flushing...
INFO[RUU]UZ,sbl1-1,0
INFO[RUU]UZ,sbl1-1,100
INFOsignature checking...
INFOverified fail
INFO..... Bypassed
INFOstart image[sbl1-2] unzipping & flushing...
INFO[RUU]UZ,sbl1-2,0
INFO[RUU]UZ,sbl1-2,100
INFOsignature checking...
INFOverified fail
INFO..... Bypassed
INFOstart image[sbl1-3] unzipping & flushing...
INFO[RUU]UZ,sbl1-3,0
INFO[RUU]UZ,sbl1-3,100
INFOsignature checking...
INFO[RUU]WP,sbl1-3,0
INFO[RUU]WP,sbl1-3,100
INFO...... Successful
INFOstart image[sbl2] unzipping & flushing...
INFO[RUU]UZ,sbl2,0
INFO[RUU]UZ,sbl2,100
INFO[RUU]WP,sbl2,0
INFO[RUU]WP,sbl2,100
INFO...... Successful
INFOstart image[sbl3] unzipping & flushing...
INFO[RUU]UZ,sbl3,0
INFO[RUU]UZ,sbl3,100
INFO[RUU]WP,sbl3,0
INFO[RUU]WP,sbl3,100
INFO...... Successful
INFOstart image[tp] unzipping & flushing...
INFO[RUU]UZ,tp,0
INFO[RUU]UZ,tp,100
INFO..... Bypassed
INFOstart image[tp] unzipping & flushing...
INFO[RUU]UZ,tp,0
INFO[RUU]UZ,tp,100
INFO...... Successful
INFOstart image[tz] unzipping & flushing...
INFO[RUU]UZ,tz,0
INFO[RUU]UZ,tz,100
INFO[RUU]WP,tz,0
INFO[RUU]WP,tz,100
INFO...... Successful
INFOstart image[radio] unzipping & flushing...
INFO[RUU]UZ,radio,0
INFO[RUU]UZ,radio,6
INFO[RUU]UZ,radio,11
INFO[RUU]UZ,radio,17
INFO[RUU]UZ,radio,23
INFO[RUU]UZ,radio,28
INFO[RUU]UZ,radio,34
INFO[RUU]UZ,radio,40
INFO[RUU]UZ,radio,46
INFO[RUU]UZ,radio,52
INFO[RUU]UZ,radio,59
INFO[RUU]UZ,radio,69
INFO[RUU]UZ,radio,75
INFO[RUU]UZ,radio,81
INFO[RUU]UZ,radio,87
INFO[RUU]UZ,radio,92
INFO[RUU]UZ,radio,99
INFO[RUU]UZ,radio,100
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,23
INFO[RUU]WP,radio,46
INFO[RUU]WP,radio,69
INFO[RUU]WP,radio,92
INFO[RUU]WP,radio,100
INFO...... Successful
INFOstart image[rcdata] unzipping & flushing...
INFO[RUU]UZ,rcdata,0
INFO[RUU]WP,rcdata,0
INFO...... Successful
OKAY [ 54.864s]
finished. total time: 58.143s
Note:The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
fastboot reboot
Then I went back to the bootloader mode (after the phone reboots successfully):
If Boot-Loop Occurs*:
Code:
fastboot erase cache
Restart in boot-loader to check whether everything is fine*:
Code:
adb reboot bootloader
--Phone reboots into bootloader--
Code:
fastboot getvar all
The resulting variable may look like this:
Code:
INFOversion: 0.5
INFOversion-bootloader: 1.57.0000
INFOversion-baseband: 4T.28.3218.04
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.06.401.1
INFOversion-misc: PVT SHIP S-OFF
INFOserialno: HT34LXXXXXXX
INFOimei:
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0714000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 4259mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-01dc707e
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
Firmware 5.11.1540.9, NO Red Warning, --md5: -- 6734d095499a72519335bb894503708f
Firmware 4.19.401.11, NO Red Warning, --md5: -- 8f3a59cdbcc84b9ff2319495eee6ae98
Firmware 4.19.401.9, NO Red Warning, --md5: -- DE93220BEB19CA1FCB3FDF407F2B3D3F
Firmware 4.19.401.8, NO Red Warning, --md5: 30772981922e19437085c92adbea9658 --
Firmware 4.19.1540.4, NO Red Warning, --md5: 49dbb024b28a17383da35593d6cbc860 --
Firmware 4.06.1540.3, NO Red Warning ** --md5: 227c88abad17dba0561a91ad6d353373 --
Firmware 4.06.1540.2, NO Red Warning ** --md5: c9b68c6a17ae323112c99ce0550dba38 --
Previous firmware with modified HBOOT,
Firmware 3.62.401.1 with NO Red Warning are below.
Firmware 3.62.401.1 for MODEL ID: PN0710000 NO Red Warning --md5: 728e3dc18abde0fd10835376332f81ec --
Firmware 3.62.401.1 for MODEL ID: PN0711000 NO Red Warning -- md5: 7fb62e47f347ae05baf4dd821b497752 --
Firmware 3.62.401.1 for MODEL ID: PN0712000 NO Red Warning --md5: 7ab96062ff848550a45dd035967adc83 --
Firmware 3.62.401.1 for MODEL ID: PN0713000 NO Red Warning -- md5: 6bcb6dd99da4d4c73a24725b814e161b --
Firmware 3.62.401.1 for MODEL ID: PN0714000 NO Red Warning -- md5: 6b2d5bf151ddf6ebbb7c6303f6db1889 --
Firmware 3.57.401.500 for MODEL ID: PN0714000
Firmware 3.57.401.500 for MODEL ID: PN0713000
Firmware 3.57.401.500 for MODEL ID: PN0712000
Firmware 3.57.401.500 for MODEL ID: PN0710000
Firmware 3.22.1540.1 : MODEL ID: PN0710000
Firmware 2.24.401.1 : MODEL ID: PN0710000 for Android 4.2.2
FIRMWARE FAQ:
Q: Do I need S-OFF for firmware flashing?
A: YES, It is a must.
Q: Do I need to update my firmware?
A: NO, but updating firmware ensures optimal phone performance.
Q: Does it matter when I flash the firmware (before or after new ROM install)
A: No.
Q: Will updating the firmware erase my SD card or Apps?
A: No, The firmware files provided here does not erase none of those.
Q: If I only flash the ROM, will I get updated to the latest firmware?
A: No. You must flash the firmware separate in most cases.
Q: Can I install a UL edition firmware on a U edition phone?
A: Yes (may be), but you won't have LTE or may experience some other incompatibilities.
Possible Errors while flashing:
If it says "FAILED" do not immediately reboot the device. If you reboot with a FAIL it could brick your device! Listed below error are safe to reboot:
If you encounter one of them, you can just reboot. Nothing changes.
- 12 signature fail (means a signed firmware package is required. This would only happen with S-ON phones though. but safe to reboot)
- 23 parsing image fail (means something wrong with the image in the zip)
- 32 header error (means the zip couldn’t be read and unzipped properly)
- 41 Wrong Model ID (means the MODEL ID in the android-info.txt does not match with your device. you can reboot the device. You may change the MID manually in the android-info.txt at your own risk.)
- 42 Wrong Customer ID (means you need to include the CID of your device in the android-info.txt or change the CID to superCID.)
- 99 UNKOWN (is not yet clear but safe to reboot)
DON'T reboot until you get a success message if you get an error bellow:
- 90 hboot pre-update (means it only flashed hboot and you have to run the process again immediately to flash all other partitions. Don’t reboot before repeating the command. If the command window stuck in the middle for a long time, wait for a few minutes and please unplug the USB and replug it again. Repeat the command again. DON'T reboot until you get a success message.)​
Editing android-info.txt​​
- Use an Editor that doesn't doesn't alter the linebreaks. Don't use Windows Notepad. Use Notepad++
- Only one MID can be in the file.
- CID's can easily be added or removed- one per line
To Get SUPERCID​​
Code:
fastboot oem writecid 11111111
RUUmode:​​
RUU Mode is the mode used for RUU flashes by HTC. It is different from the normal fastboot. You must flash the firmware only in RUU Mode. The RUU mode can be identified by the black background with only a silver HTC logo and if a command is being active a green progress bar will show the progress of any command being excecuted.
For Further Reading​Some more useful threads that might be helpful to you:
- Mike1986’s Firmware thread
- Vomer’s ultimate guide thread
- hes_theone64’s radio flash guide for recovery
- chrisch1974's HOW-TO Flash a custom splash screen
- Sneakyghost's Firmware Flashing & Hboots red warning gone thread
- HTC ONE Partition List:
- Mike1986 Partition explanation:
​
You must be aware that writing to the bootloader -partition increases your risk to lose the device exponentially. You understand and agree that i cannot be held responsible for such or any other damages. The flash process is theoretically safe and tested. I will not accept any responsibility. The method itself is developed by Google and HTC, i have only adapted it and you execute it. You understand that you should not do it if you are not willing to accept this risk.​
For More info, about Super CID, S-OFF and Firmware update process, check this thread:
[Guide] Vomer's Ultimate AIO - S-OFF, SuperCID, Firmware Upgrade & Custom Recovery
Thanks @vomer and @Sneakyghost

Thanks for this. But does this firmware package wipe SD contents?

Is it safe to use 1.44 hboot with 3.57 firmware and a 4.3 Rom?
Sent from my HTC One using XDA Premium HD app

Thanks for this, works. Not much more I can say.

Huey85 said:
Thanks for this. But does this firmware package wipe SD contents?
Click to expand...
Click to collapse
No, firmware never wiped my SD card yet. I have flashed several firmware zips since I have my one and it never wiped anything!
Only thing is to make sure you are s-off before you flash the zip as it might contain a exploit fixed hboot.
Renovated.

jonas2295 said:
No, firmware never wiped my SD card yet. I have flashed several firmware zips since I have my one and it never wiped anything!
Only thing is to make sure you are s-off before you flash the zip as it might contain a exploit fixed hboot.
Renovated.
Click to expand...
Click to collapse
Thanks. I'm well aware that you need to be S-Off to flash firmware via fastboot. But my concern was more around having the device's SD partition wiped, as you can see, with the original 3.57 firmware released by LlabTooFeR here, he stated that it did wipe his SD partition.

There is one mistake for model MODEL ID: PN0710000,
line mainver: 1.28.401.7 change it with mainver: 3.57.401.500
Code:
modelid: PN0710000
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: 3.57.401.500
btype:1
aareport:1
DelCache:1
hbootpreupdate:3

jonas2295 said:
No, firmware never wiped my SD card yet. I have flashed several firmware zips since I have my one and it never wiped anything!
Only thing is to make sure you are s-off before you flash the zip as it might contain a exploit fixed hboot.
Renovated.
Click to expand...
Click to collapse
The latest firmware provided by Llabtoofer wipes the sd card (even confirmed by him). The other customized firmware zips floating around have removed the offending files though.

ClydeB1 said:
The latest firmware provided by Llabtoofer wipes the sd card (even confirmed by him). The other customized firmware zips floating around have removed the offending files though.
Click to expand...
Click to collapse
Yeah I use the modified firmwares usually.
Renovated.

SD Card won't get wiped by default
ClydeB1 said:
The latest firmware provided by Llabtoofer wipes the sd card (even confirmed by him). The other customized firmware zips floating around have removed the offending files though.
Click to expand...
Click to collapse
This firmware doesn't wipe SD card data... You can flash it before or after flashing the 4.3 version ROMs. But recommend before flashing the custom ROM s.
This firmware is the newest released so far for WWE. It is modified to remove the red warning message.:laugh:
You flash it in RUU mode only and only if you have S-OFF.

jonas2295 said:
Yeah I use the modified firmwares usually.
Renovated.
Click to expand...
Click to collapse
Always the safest option
jolishj said:
This firmware doesn't wipe SD card data... You can flash it before or after flashing the 4.3 version ROMs. But recommend before flashing the custom ROM s.
This firmware is the newest released so far for WWE. It is modified to remove the red warning message.:laugh:
You flash it in RUU mode only and only if you have S-OFF.
Click to expand...
Click to collapse
Sorry I wasn't implying that your firmware did wipe the sd card, I was only responding to a post saying that firmware doesn't wipe data. Those that have used LLabtoofer's firmware for example (including him) have however had their sd cards wiped and I am only trying to prevent some person using the firmware and loosing all of their precious photos and videos etc without being aware of the possible risks.

This is my getvar all result after the flash:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.30
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.57.401.500
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4308mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6cad6811
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
is this all right?

atomantmk said:
There is one mistake for model MODEL ID: PN0710000,
line mainver: 1.28.401.7 change it with mainver: 3.57.401.500
Code:
modelid: PN0710000
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: 3.57.401.500
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
Click to expand...
Click to collapse
Yes indeed.
Can someone upload the correct modified firmware for PN0710000 ?

wrong thread! sorry!

spdrosin said:
Yes indeed.
Can someone upload the correct modified firmware for PN0710000 ?
Click to expand...
Click to collapse
https://www.dropbox.com/s/qf0yczoxcccguz3/firmware.zip
Sent from my HTC One using Tapatalk

atomantmk said:
https://db.tt/HLkdgAGn
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
still fail

atomantmk said:
https://db.tt/HLkdgAGn
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanx man, but
focuskr said:
still fail
Click to expand...
Click to collapse
he is wright.
"FAILED (remote: 24 parsing android-info fail)"

how to find model no?

chdpiyush said:
how to find model no?
Click to expand...
Click to collapse
fastboot getvar modelid or fastboot getvar all

spdrosin said:
Thanx man, but
he is wright.
"FAILED (remote: 24 parsing android-info fail)"
Click to expand...
Click to collapse
Wait just a little please
Edit: new link added

[COLLECTION] RUU Nougat & Marshmallow - HTC One A9

FAQ AND INSTRUCTIONS AT POST #2. READ BEFORE ASKING QUESTIONS.​
{
"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"
}
Android Nougat:​UPDATING FROM MARSHMALLOW TO NOUGAT USING A RUU? READ FAQ #4, POST #2
HIA_AERO_UL:​
2.18.617.30 RUU
HTC USA Unlocked
2PQ912000
BS_US001
official .exe version: http://dl3.htc.com/application/RUU_...4.1836039897.1499599428-1468744157.1486469825
2.18.617.30 Firmware
HTC USA Unlocked
Decrypted firmware (for s-off only)
2PQ912000
BS_US001
Link: https://www.androidfilehost.com/?fid=673368273298970193
md5: d1cd9226c046d629ef67812cc74d09f8
2.18.617.10 RUU
HTC USA Unlocked
2PQ912000
BS_US001
.exe version: http://dl3.htc.com/application/RUU_...17.10.exe?_ga=1.5031603.1468744157.1486469825
2.18.617.10 Firmware
HTC USA Unlocked
2PQ912000
BS_US001
Link: https://www.androidfilehost.com/?fid=529152257862708503
md5: bf799f363d4e33eec75948bdb7637502
2.18.617.1 RUU
HTC USA Unlocked
2PQ912000
BS_US001
.exe version:Official link
.zip version: https://www.androidfilehost.com/?fid=745425885120701547
md5: 0956949b54fe63faf895374176618598
2.18.617.1 Firmware
HTC USA Unlocked
2PQ912000
BS_US001
Link: https://www.androidfilehost.com/?fid=457095661767130940
md5: 8f634fcd55fbecab65b1e540364bc41e
HIA_AERO_UHL:​
2.16.206.5 RUU + Firmware
O2 UK
modelid: 2PQ910000
cidnum: O2___001
cidnum: O2___102
RUU Download: https://mega.nz/#!1hsAhACT!Ey4k3szKpdVQqYRaxTCmpXQt_pGO9CR2kKi5fzi8C5g
Firmware Download: https://mega.nz/#!Rss0gIgK!mqgT1vGuCrwGokHRhatSZFRUY_jPXR4HB6LfiMTcyTA
Thanks to @scotty2000
2.16.161.5
Vodafone UK
modelid: 2PQ910000
cidnum: VODAP001
cidnum: VODAP102
cidnum: VODAP304
Link: https://www.androidfilehost.com/?fid=817906626617940451
md5: daac3bfba74c942c8208481e86d8efe7
thanks to @lubo_uni
2.16.841.4 RUU
Telstra
modelid: 2PQ910000
cidnum: TELST001
https://www.androidfilehost.com/?fid=889764386195901714
md5: 47e2997b566d6d139d42b10ae57929c3
Thanks to @scotty2000
2.16.841.4 Firmware
Telstra
modelid: 2PQ910000
cidnum: TELST001
https://www.androidfilehost.com/?fid=889764386195902165
md5: ec31fb73a553e72dd363e67c4d374799
Thanks to @scotty2000
2.17.91.1
EE UK
modelid: 2PQ910000
cidnum: ORANG001
Link: https://www.androidfilehost.com/?fid=529152257862717671
md5: d523202e4f5d8c558e5d1e5e770ae67b
thanks to @scotty2000
2.17.401.2 RUU
HTC Europe
modelid: 2PQ910000
cidnum: HTC__001
cidnum: HTC__034
cidnum: HTC__J15
cidnum: HTC__M27
cidnum: HTC__A07
cidnum: HTC__016
cidnum: HTC__002
Thanks to @scotty2000
Link: https://www.androidfilehost.com/?fid=817550096634759503
md5: 2fab1ba54f9066b557ee4c257620affd
2.17.401.2 Firmware
HTC Europe
modelid: 2PQ910000
cidnum: HTC__001
cidnum: HTC__034
cidnum: HTC__J15
cidnum: HTC__M27
cidnum: HTC__A07
cidnum: HTC__016
cidnum: HTC__002
Link: https://www.androidfilehost.com/?fid=817550096634759689
md5: f232f77195e7c9c2b3d36a4eae6b9dd9
2.16.401.3 RUU
This version, despite being an official & signed ruu, never was released by HTC for consumer use, it was a pre-release version (thanks to @Didusieq for sharing the info here. 2.17.401.2 is the released version. Ppl on 2.16.401.3 will not be able to OTA update to 2.17.401.2. You'll have to revert back to 1.56.401.70 to get OTA to 2.17.401.2 or wait for a 2.17.401.2 RUU.
HTC Europe
modelid: 2PQ910000
cidnum: HTC__001
cidnum: HTC__034
cidnum: HTC__J15
cidnum: HTC__M27
cidnum: HTC__A07
cidnum: HTC__016
cidnum: HTC__002
Thanks to @scotty2000
Link: https://www.androidfilehost.com/?fid=673368273298930244
md5: b3d724a60471e23c93fde161342b6860
2.16.401.3 Firmware
https://www.androidfilehost.com/?fid=745425885120707133
md5: 0434af3ebe54fa14dad312708aac6ed7
HIA_AERO_WHL:​
2.18.651.2 RUU
Sprint
MID: 2PQ930000
CID: SPCS_001
Download: http://dl3.htc.com/application/RUU_...1.2.exe?_ga=1.222208536.1468744157.1486469825
2.18.651.2 Firmware
Sprint
MID: 2PQ930000
CID: SPCS_001
Link: https://www.androidfilehost.com/?fid=673368273298932288
md5: e46d8bfa70e899a45e7b74743becb66a
Android Marshmallow:​HIA_AERO_TUHL:​
1.64.1405.6
HTC CN CHS
modelid: 2PQ911000
cidnum: HTCCN701
Download link: https://www.androidfilehost.com/?fid=601275311581037240
md5: eddf971386e91e2a8b18d4625cc04fda
Thanks to @scotty2000
1.27.1405.12
HTC CN CHS
modelid: 2PQ911000
cidnum: HTCCN701
Download link: https://www.androidfilehost.com/?fid=24438995911972715
md5: ceb261929ab095121b407b6c5e3dc486
1.27.1405.25
HTC CN CHS
modelid: 2PQ911000
cidnum: HTCCN701
Download link: https://www.androidfilehost.com/?fid=24438995911972714
md5: 0593f0399d7c73d81a81d14ac009533f
HIA_AERO_UHL:​
1.56.111.70
TMO DE
modelid: 2PQ910000
cidnum: T-MOB101
Link: https://www.androidfilehost.com/?fid=24459283995296727
md5: ba0dbefc8d3f3b59b01eaafb339e95d3
1.56.206.70
O2 UK
modelid: 2PQ910000
cidnum: O2___001
cidnum: O2___102
Download: https://www.androidfilehost.com/?fid=24459283995296725
md5: 55b406418575a3007eabc6607cc037a1
Thanks to Krocko
1.56.401.70
HTC Europe
odelid: 2PQ910000
cidnum: HTC__001
cidnum: HTC__034
cidnum: HTC__J15
cidnum: HTC__M27
cidnum: HTC__A07
cidnum: HTC__016
cidnum: HTC__002
Link: https://www.androidfilehost.com/?fid=24457741883933257
md5: 0ac63ac2e08b83eb55a44d5893ec3502
1.56.401.170
HTC Europe
odelid: 2PQ910000
cidnum: HTC__001
cidnum: HTC__016
Link: https://www.androidfilehost.com/?fid=24457741883933258
md5: 003a9c4617b11ee653631ab69b448aa0
1.56.91.71
EE UK
modelid: 2PQ910000
cidnum: ORANG001
Link: https://www.androidfilehost.com/?fid=24457741883932916
md5: d9fb062162157e6d40adfaa057947f9e
1.56.1020.70
Bouygues FR
modelid: 2PQ910000
cidnum: HTC__247
Link: https://www.androidfilehost.com/?fid=24457741883932913
md5: efb8f35144d8e8aab31d07a32dabb747
1.27.161.6
Vodafone UK
modelid: 2PQ910000
cidnum: VODAP001
cidnum: VODAP102
cidnum: VODAP304
Link: https://www.androidfilehost.com/?fid=24438995911972389
md5: c55ef03d2cf0bda5425112364b6a95d1
1.27.163.15
Vodafone CH-DE
2PQ910000
cidnum: VODAP203
Link: https://www.androidfilehost.com/?fid=24438995911969982
md5: 818c86c4d26fd55b2aa0effa7681d841
1.27.166.5
Vodafone CH-DE
2PQ910000
cidnum: VODAP110
cidnum: VODAP120
Link: https://www.androidfilehost.com/?fid=24438995911969984
md5: 1080d9b71e20ac94aa26f9a95673fd7e
1.27.114.5
TMO NL
modelid: 2PQ910000
cidnum: T-MOB003
Link: https://www.androidfilehost.com/?fid=24438995911969981
md5: c6f7f4038fb392bdaf61ddc2fc4111ac
1.27.112.5
TMO AT
modelid: 2PQ910000
cidnum: T-MOB102
Link: https://www.androidfilehost.com/?fid=24438995911969983
md5: 271d2554c8b0984e6134a556cc936aaa
1.27.111.5
TMO DE
modelid: 2PQ910000
cidnum: T-MOB101
Link: https://www.androidfilehost.com/?fid=24438995911969179
md5: 3dc3f057ef64102f1770237d676a0404
1.27.425.25
HTC WWE VNM
modelid: 2PQ910000
cidnum: HTC__058
cidnum: HTC__059
Link: https://www.androidfilehost.com/?fid=24438995911969180
md5: 209b5e113ee7f12af62f3fac737fc3fa
1.27.709.15
HTC Asia TW
modelid: 2PQ910000
cidnum: HTC__621
Link: https://www.androidfilehost.com/?fid=24438995911969306
md5: ebd71ebd655cfe91782d14650f1b9012
1.27.708.5
HTC Asia HK
modelid: 2PQ910000
cidnum: HTC__622
Link: https://www.androidfilehost.com/?fid=24438995911969183
md5: c34627bb333ff405331375d8352a5f26
1.27.709.5
HTC Asia Taiwan
modelid: 2PQ910000
cidnum: HTC__621
https://www.androidfilehost.com/?fid=24421527759882465
md5: eea610729b5c8fae4a009ea56fec8004
1.27.707.5
https://www.androidfilehost.com/?fid=24421527759882466
md5: c2faf0888b29f597c8ca8fb95e24f0c4
1.27.771.5
H3G UK
modelid: 2PQ910000
CID: H3G__001
CID: H3G__G04
CID: H3G__106
CID: H3G__003
Download: https://www.androidfilehost.com/?fid=24369303960686710
md5: d9e3e682226439af3519f464f7aa6e18
1.10.709.7
HTC Asia Taiwan
modelid: 2PQ910000
cidnum: HTC__621
Download: https://www.androidfilehost.com/?fid=24369303960686623
md5: 4aef1066a9ceef2880739ff5ef221b4b
1.10.709.5
HTC Asia Taiwan
modelid: 2PQ910000
cidnum: HTC__621
Download: https://www.androidfilehost.com/?fid=24369303960686622
md5: 9f6472b69d05449c82e2d8d8ece3c6d5
1.27.73.5
Orange FR
modelid: 2PQ910000
cidnum: ORANG202
Download: https://www.androidfilehost.com/?fid=24369303960686620
md5: 97fa3f0865e737fd912ed3691760b5f0
1.27.73.7
Orange FR
modelid: 2PQ910000
cidnum: ORANG202
Download: https://www.androidfilehost.com/?fid=24369303960686621
md5: 37417bfbe2289ae4677e83761d2fce6a
1.27.206.5
O2 UK
modelid: 2PQ910000
cidnum: O2___001
cidnum: O2___102
Download: https://www.androidfilehost.com/?fid=24369303960685891
md5: e6c07de4d6ecf78e6ae61a0a7f666e58
1.10.206.7
O2 UK
modelid: 2PQ910000
cidnum: O2___001
cidnum: O2___102
Download: https://www.androidfilehost.com/?fid=24052804347853234
md5: 24fd48bfa65a8da1981f66bd56ac7ab1
1.27.401.5
HTC Europe
modelid: 2PQ910000
cidnum: HTC__001
cidnum: HTC__034
cidnum: HTC__J15
cidnum: HTC__M27
cidnum: HTC__A07
cidnum: HTC__002
cidnum: HTC__016
https://www.androidfilehost.com/?fid=24399994186369413
md5: 3ae114c467af982982c3fbf3c6585280
1.10.401.7
HTC Europe
modelid: 2PQ910000
cidnum: HTC__001
cidnum: HTC__034
cidnum: HTC__J15
cidnum: HTC__M27
cidnum: HTC__A07
cidnum: HTC__002
cidnum: HTC__016
Download: https://www.androidfilehost.com/?fid=24052804347853259
md5: f0940e93251a8739691a9135cdc5ebac
1.27.1020.15
Bouygues FR
modelid: 2PQ910000
cidnum: HTC__247
https://www.androidfilehost.com/?fid=24399994186369368
md5: c70137242a83aca040940ffcccadc908
1.10.1020.7
Bouygues FR
modelid: 2PQ910000
cidnum: HTC__247
Download: https://www.androidfilehost.com/?fid=24052804347853439
md5: e042caa2e55480fa73b86716df3a51a4
1.10.91.7
EE UK
modelid: 2PQ910000
cidnum: ORANG001
Download: https://www.androidfilehost.com/?fid=24052804347853441
md5: 25efb2c59613838a54447cf027c821c9
1.10.771.8
H3G UK
modelid: 2PQ910000
cidnum: H3G__001
cidnum: H3G__G04
cidnum: H3G__106
cidnum: H3G__003
Download: https://www.androidfilehost.com/?fid=24052804347853482
md5: 5c46ce65e96aa3b0bf54b090f55f4a53
1.10.111.7
TMO DE
modelid: 2PQ910000
cidnum: T-MOB101
Download: https://www.androidfilehost.com/?fid=24052804347853523
md5: 981ee338201a7025052a536947db78d2
1.10.112.7
TMO AT
modelid: 2PQ910000
cidnum: T-MOB102
Download: https://www.androidfilehost.com/?fid=24052804347853510
md5: 5c4502b3923b757dd11b58f3f56688cf
1.10.114.7
TMO NL
Download: https://www.androidfilehost.com/?fid=24269982086996612
md5: 0359ce6b1e8afdda0cc371b1ccf30259
1.10.166.7
Vodafone CH-DE
Download: https://www.androidfilehost.com/?fid=24269982086996611
md5: 000aba9d77355beb657017426dcbf126
1.10.163.7
Vodafone FR
CID: VODAP203
Download: https://www.androidfilehost.com/?fid=24269982086996609
md5: 3852f6094c274683d8277ba939f2f4b4
1.10.161.7
Vodafone UK
Download: https://www.androidfilehost.com/?fid=24269982086996608
md5: c15db1fecda2dee3e7b85899e4b638ee
HIA_AERO_UL:​
1.57.617.60 RUU.exe
HTC USA Unlocked
modelid: 2PQ912000
cidnum: BS_US001
Download: http://dl3.htc.com/application/RUU_...17.60.exe?_ga=1.5744307.1024585985.1479423713
thanks to @CarinaPDX
1.57.617.52 RUU.exe
HTC USA Unlocked
modelid: 2PQ912000
cidnum: BS_US001
Download: http://dl3.htc.com/application/RUU_HIA_AERO_UL_M60_SENSE7GP_ATT_MR_NA_Gen_Unlock_1.57.617.52.exe
1.57.617.32 RUU.exe
HTC USA Unlocked
modelid: 2PQ912000
cidnum: BS_US001
Download: http://dl3.htc.com.s3.amazonaws.com...AERO_UL_M60_SENSE7GP_ATT_MR_NA_Gen_Unlock.exe
1.57.617.20 RUU.exe
HTC USA Unlocked
modelid: 2PQ912000
cidnum: BS_US001
Download: http://dl3.htc.com/application/RUU_HIA_AERO_UL_M60_SENSE7GP_ATT_MR_NA_Gen_Unlock_1.57.617.20.exe
1.57.617.20 RUU.zip
HTC USA Unlocked
modelid: 2PQ912000
cidnum: BS_US001
Download: https://www.androidfilehost.com/?fid=24459283995314374
md5: b3bea514444c420d612b1a2d40175017
thanks to @65vdub for extracting the zip from the exe version and uploading.
1.27.600.5
HTC LA TELCEL SPA
modelid: 2PQ912000
cidnum: HTC__332
Link: https://www.androidfilehost.com/?fid=24438995911972390
md5: 191a02e23f80a861d8845bf9b277adb4
1.27.428.5
HTC CAN
modelid: 2PQ912000
cidnum: HTC__051
Link: https://www.androidfilehost.com/?fid=24438995911972388
md5: 59573f22412a52f697ddbcaefcc61748
1.56.617.1 RUU.zip
HTC USA Unlocked
modelid: 2PQ912000
cidnum: BS_US001
Link https://www.androidfilehost.com/?fid=24399994186368579
md5: 14481f7b1afc9bf67b6a27391b841eb1
1.56.617.1 RUU.exe
HTC USA Unlocked
modelid: 2PQ912000
cidnum: BS_US001
Download
1.55.617.4 RUU.exe
HTC USA Unlocked
modelid: 2PQ912000
cidnum: BS_US001
Download
1.12.617.6 RUU.exe
rahaar
HTC USA Unlocked
modelid: 2PQ912000
cidnum: BS_US001
Download: http://dl3.htc.com/application/RUU_HIA_AERO_UL_M60_SENSE7GP_ATT_NA_Gen_Unlock_1.12.617.6.exe
1.12.617.6 RUU.zip
HTC USA Unlocked
modelid: 2PQ912000
cidnum: BS_US001
Download: https://www.androidfilehost.com/?fid=24269982087008238
md5: 2a8c51ced68c6751abb35021df9d1f73
1.27.502.5
AT&T (Cingular)
modelid: 2PQ912000
cidnum: CWS__001
Download: http://dl3.htc.com/application/RUU_HIA_AERO_UL_M60_SENSE7GP_ATT_Cingular_US_1.27.502.5.exe
1.10.502.3
AT&T (Cingular)
modelid: 2PQ912000
cidnum: CWS__001
Download: https://www.androidfilehost.com/?fid=24269982087001291
md5: 2aa9e842d86dd9d1785c9d41cd002d83
1.12.428.1
HTC CAN
MID: 2PQ912000
cid: HTC__051
Download: https://www.androidfilehost.com/?fid=24369303960685997
md5: b3b96edd52debaed2bae1b21e30aac8b
1.07.598.5
HTC LA AMX SPA
MID: 2PQ912000
CID: HTC__332
CID: HTC__339
Download: https://www.androidfilehost.com/?fid=24369303960685998
md5: afed4cb85490f90ce0b9128761e1210e
HIA_AERO_WHL:​
1.60.651.4
Sprint
MID: 2PQ930000
CID: SPCS_001
Download: https://www.androidfilehost.com/?fid=673791459329049795
thanks to @Kiki.G
1.57.651.1
Sprint
MID: 2PQ930000
CID: SPCS_001
Download: http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe
1.09.651.1
Sprint
MID: 2PQ930000
CID: SPCS_001
Download: https://www.androidfilehost.com/?fid=24369303960685995
md5: 7023763098d675c04ff085f3ccbf6d83
1.10.651.1_R4
Sprint
MID: 2PQ930000
CID: SPCS_001
Download: https://www.androidfilehost.com/?fid=24369303960685996
md5: 3ac9d0954b27066ad30f3b78c31ad5fb
Contributed to this collection:
alray
scotty2000
wakers
Reinhard H.
rahaar
tomkins0752
65vdub
AntikerTa
Asselalf
CarinaPDX
aries2747
Kiki.G
lubo_uni
I will try to keep this thread updated when new RUU are available. If you want to contribute to this collection, please upload your RUU (preferably on androidfilehost.com) share the link and I'll add it in the OP with credits to you.

FAQ - Instructions
FREQUENTLY ASKED QUESTIONS:​
What RUU should I use, can I flash this RUU:
Use "fastboot getvar all" to get and note your MID, CID and version-main.
Both your MID and CID must be listed under the RUU you want to flash
Knowing your version-main, read FAQ 2 and 3.
RUU version numbers explained
a.bb.ccc.dd
a: Usually 1 digit only. Major android update since device release. This device shipped with Marshmallow so a RUU starting with 1 is Marshmallow, with 2 is Nougat and so on.
bb: Usually 2 digits. Major changes in HTC firmware/software
ccc: Usually 3 digits, sometimes 4. This numbers represent your region/carrier version. This number doesn't change (unless you convert your phone). E.G: 1.10.617.1 isn't newer than 1.10.401.1. Both are same versions designed for different operators/regions.
dd: Usually 2 digits, sometimes 3. Minor update / security fix
Do I need S-OFF ?
If your phone is S-ON you can't downgrade simply by flashing an old ruu **(See how to downgrade with S-ON below). The combination of a, bb and dd (see above explanations) of the ruu you want to flash must be same or newer than your version-main (fastboot getvar version-main)
If your phone is S-ON you can't convert to another region/carrier. The ccc digits in a.bb.ccc.dd must be the same (see above explanations)
If your phone is S-ON you can only flash signed RUU or Signed Firmware. If the RUU file name you want to flash ends with "decrypted.zip" it is not signed and will requires S-OFF. If its ending with "signed.zip" it is signed and can be flashed with S-ON
UPDATING from Marshmallow to Nougat RUU (2.xx.xxx.x)? READ THIS !!!
EXPECT THIS:
bootloader reporting these errors:
(bootloader) ERR check AES encrypted magic string failed.
FAILED (remote: 12 RU_ZIP_ERROR )
Signature verify fail
and ruu will not flash
WHY:
HTC is now signing Nougat RUUs with a different signature than Marshmallow RUUs. The Key to read that signature is embedded in your phone firmware, more precisely in the HOSD (hosd.img).
That mean, if your phone is still running a Marshmallow firmware (version starting with 1.) your phone firmware (and so your hosd.img) had not been updated yet with the new signature key which will result in your phone not being able to verify the Nougat ruu signature.
HOW TO SOLVE:
You can't flash a Nougat RUU if your phone isn't already running the Nougat firmware ---> You must update your firmware to 2.xx.xxx.x before flashing a 2.xx.xxx.x RUU / You can't update from 1.xx.xxx.x to 2.xx.xxx.x without updating your firmware to 2.xx.xxx.x first.
DOWNGRADING from Nougat to Marshmallow READ THIS !!!
Read FAQ #4, same thing apply when downgrading, you need the old marshmallow decryption key on your phone for the marshmallow RUU to pass signature verification. Downgrade your firmware to 1.xx.xxx.x before flashing a 1.xx.xxx.x RUU.
DOWNGRADING with S-ON:
Below explanations are for the One A9 Only. This procedure can work on other HTC devices but will require a different command since the partitions are different for each device.
If you're stuck S-ON and you must downgrade because there is no recent RUU available for your phone, there is method you can try. Usually it will only work if you are downgrading to a version that's is using the same bootloader version (well it was working that way for older HTC device using hboot i.e M7/M8, don't know if the same apply for A9). Usually if you're going to flash an older RUU with a version-main starting with the same digit at positon "a" (see above "RUU version explained") it should work. In many cases, the only things preventing you from downgrading when S-ON is your version-main: When flashing a RUU, your actual version-main is compared with the RUU version. If the RUU version is newer or equal to your version-main (and all other parameters explained above are ok), it will flash. Otherwise the ruu will fail. Your version-main number is stored on the /misc partition (mmcblk0p28) starting at decimal block #2208. See image below:
The good news for you is that mmcblk0p28 is not write protected, even when your phone is S-ON. So we can change the version-main value manually in that partition to a lower version so when flashing an old RUU it will pass that check.
How to manually change your version-main:
Warning:Always double check your partition table before doing any modification to confirm the location of your /misc partition. Another user reported to have his /misc partition located to p29 instead of p28. You don't want to mess your partition or write data to the wrong partition. Double check using "cat /proc/emmc" and "cat /proc/partition" from an adb shell.
​
Warning: "dd" commands can be dangerous. Make sure there is no typo in your command, you don't want to mess your partition or write data to the wrong partition.
​
Method 1: When booted in the OS (a ROOTED rom is required)
With your phone connected to your computer, open an ADB command window
start an adb shell
ask and grant super user privileges
edit the version-main (see below explaination "What command should I use to edit my version-main")
exit the shell
reboot in bootloader/download and confirm your version-main correctly changed
strike over numbers = numbers used for example, read below to determine which numbers you must use.
Code:
adb shell
su
echo -ne "[STRIKE]1.10.651.1\x00\x00[/STRIKE]" | dd of=/dev/block/mmcblk0p28 bs=1 seek=2208
exit
exit
adb reboot download
fastboot getvar version-main
Method 2: From a custom recovery (a ROOTED rom isn't required)
With your phone connected to your computer, open an ADB command window
start an adb shell
edit the version-main (see below explaination "What command should I use to edit my version-main")
exit the shell
reboot in bootloader/download and confirm your version-main correctly changed
Code:
adb shell
echo -ne "[STRIKE]1.10.651.1\x00\x00[/STRIKE]" | dd of=/dev/block/mmcblk0p28 bs=1 seek=2208
exit
adb reboot download
fastboot getvar version-main
Method 3: From a terminal emulator (no computer required, ROOTED rom requried)
Start your terminal emulator app
Ask and grant SU to your terminal app
edit the version-main (see below explaination "What command should I use to edit my version-main")
exit the shell
reboot in bootloader/download and confirm your version-main correctly changed
Code:
su
echo -ne "[STRIKE]1.10.651.1\x00\x00[/STRIKE]" | dd of=/dev/block/mmcblk0p28 bs=1 seek=2208
exit
adb reboot download
fastboot getvar version-main
Method 4: From TWRP's embedded terminal (No computer required, ROOTED rom not required)
Reboot your phone in recovery/twrp
from twrp main menu, select "Advanced" then "Terminal"
edit the version-main (see below explaination "What command should I use to edit my version-main")
reboot in bootloader/download and confirm your version-main correctly changed
Code:
echo -ne "[STRIKE]1.10.651.1\x00\x00[/STRIKE]" | dd of=/dev/block/mmcblk0p28 bs=1 seek=2208
What command should I use to edit my version-main (one more time, this is for the One A9 Only):
Use this command:
echo -ne "version-main" | dd of=/dev/block/mmcblk0p28 bs=1 seek=2208
Click to expand...
Click to collapse
version-main must be replaced by the appropriate number for your situation. For example if you're going from 1.27.401.10 to 1.10.401.1, version-main will be 1.10.401.1\x00\x00. Do not remove the quotes in the command, they must be there:
i.e:
Code:
echo -ne "1.10.401.1\x00\x00" | dd of=/dev/block/mmcblk0p28 bs=1 seek=2208
Why adding \x00\x00 at the end of 1.10.401.1?
- In theory, a version-main can have up to 12 characters (this includes dots). Since 1.10.401.1 is only 10 characters we want to null out the last 2 characters that aren't used. x00 is the hexadecimal expression for the "null" value. If you're not doing this it could result in wrong version-main, for example if your previous version-main was 1.27.401.222 and you only input "1.10.401.1" instead of "1.10.401.1\x00\x00" in the command, the final result will be 1.10.401.122 since the last 2 digits weren't erased with the "null" value. If you're going to use a version-main that is 11 characters, only add \x00 once so the 12th characters in null.
Some RUU.exe links are dead, give a 404 error:
read this:
https://forum.xda-developers.com/showpost.php?p=73313457&postcount=1021
How to flash (RUU.ZIP):​
SD Card Method:
Rename the RUU zip file "2PQ9IMG.zip", save it at the root of your external sd card (FAT32) (exfat should also work, to be confirmed). Reboot the phone in download mode and wait for the magic...
Using fastboot commands Method (MS Windows, Linux, MacOS):
Save the ruu zip file in your adb/fastboot folder along with htc_fastboot.exe(see post 43). Open a command window from that folder then type:
Code:
fastboot oem rebootRUU
htc_fastboot flash zip <file_name>.zip
Wait for the "finished. Total time: xx sec" before doing anything. Then:
Code:
fastboot reboot
Make sure you have the latest HTC drivers installed on your computer and that you are using htc_fastboot.exe for the flash zip command.
How to flash RUU.EXE (For MS Windows Only)​
Make sure you have the latest HTC drivers installed and MS Visual C++ 2008 Redistributable Package (If you launch the RUU and nothing happens, then you don't have the MS Visual C++ installed). Connect your phone to your computer and launch the ruu.exe file. Follow instruction from the RUU program.
How to flash firmware.zip​
It can be done the same way as flashing a RUU.zip, see above SDcard & fastboot methods.

Can I flash these on my sprint version?
Sent from my unknown using Tapatalk

Cj719 said:
Can I flash these on my sprint version?
Sent from my unknown using Tapatalk
Click to expand...
Click to collapse
The RUU must match your phone MID, CID and Version-main to be flashed. Is the Sprint version the same UHL variant with the same MID? ---> no, WHL. If yes then it might be possible to convert it to another version (would requires s-off first) but its a little early to talk about which version can be converted to another version. No one posted technical info about the A9 yet (partition table, getvar, etc). So for now the answer is no.
We will probably see a Sprint RUU, the sprint RUU are normally posted on HTC's website but none for the A9 yet.
http://www.htc.com/us/support/rom-downloads.html

I can post the partitions because I have the sprint version already
Sent from my unknown using Tapatalk

Not one of your RUUs, but I obtained 2PQ9IMG_HIA_AERO_[email protected]51002.2_29.05_F_release_signed.zip for ATT.
Which appears to be the same firmware running on mine.
I am attempting to flash it from external sdcard but download mode is printing the error "22 RU_HEADER_ERROR"
Any idea what this error means? Zip header appears to be properly intact

jcase said:
Not one of your RUUs, but I obtained 2PQ9IMG_HIA_AERO_[email protected]51002.2_29.05_F_release_signed.zip for ATT.
Which appears to be the same firmware running on mine.
I am attempting to flash it from external sdcard but download mode is printing the error "22 RU_HEADER_ERROR"
Any idea what this error means? Zip header appears to be properly intact
Click to expand...
Click to collapse
Not sure why as I don't own the A9 and never tried to flash anything on this phone yet. I guess you already checked the md5 (if available) and that your ext sd is fat32? Otherwise I would try to flash it using fastboot or htc's version of fastboot since it looks like newer RUU can only be flashed with htc's fastboot (at least this is true for the M7 (7.xx.xxx.x ruu) don't know for other models...)

alray said:
Not sure why as I don't own the A9 and never tried to flash anything on this phone yet. I guess you already checked the md5 (if available) and that your ext sd is fat32? Otherwise I would try to flash it using fastboot or htc's version of fastboot since it looks like newer RUU can only be flashed with htc's fastboot (at least this is true for the M7 (7.xx.xxx.x ruu) don't know for other models...)
Click to expand...
Click to collapse
You can flash newer ones using sdcard still, or you can break apart the jumpozip (forgot the proper name) into small ones and flash with normal fastboot, I had a corrupted download but now have a sane one

jcase said:
I had a corrupted download but now have a sane one
Click to expand...
Click to collapse
So you were able to flash it? Would it be possible for you to share the link of that at&t RUU so i can add it to the OP?

alray said:
So you were able to flash it? Would it be possible for you to share the link of that at&t RUU so i can add it to the OP?
Click to expand...
Click to collapse
I can't sorry, I can ask someone else with it to, but because of what I do im not comfortable sharing proprietary things

jcase said:
I can't sorry, I can ask someone else with it to, but because of what I do im not comfortable sharing proprietary things
Click to expand...
Click to collapse
No problem, I understand that

I feel stupid .. my i have ONE A9u .. what does that mean ? and which is the correct ruu ?

hamanoosh said:
which is the correct ruu ?
Click to expand...
Click to collapse
We can't tell you what RUU you need if you don't provide any information about your phone. Post the output of "fastboot getvar all" (remove your IMEI/SN before posting).

Info only, i used the 1.10.502.3 Sense 7GP Android 6.0 - Signed RUU.zip for my at&t usa A9 and returned to stock via sd card method and re-rooted with no problems at all.

alray said:
We can't tell you what RUU you need if you don't provide any information about your phone. Post the output of "fastboot getvar all" (remove your IMEI/SN before posting).
Click to expand...
Click to collapse
Hmmm im new to this but my phone is running 1.10.709.9
But security patch it 1-10-2015

hamanoosh said:
Hmmm im new to this but my phone is running 1.10.709.9
But security patch it 1-10-2015
Click to expand...
Click to collapse
There is no ruu for x.xx.709.x version yet.

See thats what in talking about and now today i got an 1.27.709.5 update!!
Why is phone different?! i65.tinypic.com/121wqgw.png
i63.tinypic.com/2vipaxc.png

hamanoosh said:
See thats what in talking about
Click to expand...
Click to collapse
No I don't see what you are talking about... You asked for a x.xx.709.x RUU I'm saying there are none for this version yet...
Why is phone different?!
Click to expand...
Click to collapse
What do you mean different?

Does anyone know when the unlocked US version will be available. I've had mine for about two weeks now and a week of that its been in a drawer. I need to restore and start over.

FatKris said:
Does anyone know when the unlocked US version will be available. I've had mine for about two weeks now and a week of that its been in a drawer. I need to restore and start over.
Click to expand...
Click to collapse
There is no ETA available for RUU, its not like they are releasing these files for the public like Nexus's factory images. HTC does not release their RUU for the public except a few versions on their website. They will be uploaded when (and if) available (when leaked).