• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[2017.10.08] Fastboot flashing and Firmware [Latest: Unlocked 2.51.617.21]

Search This thread

Sneakyghost

Senior Member
Jul 24, 2008
8,305
13,584
InMyHead
I'm gonna put those two 2.28. versions on the first post, assuming the "Wipe" issue I experienced seems to have been random.

If you encounter a wipe on a NoWipe, please do report and let me know the following info:

1.) S-OFF with Bootloader Locked/Unlocked?
2.) FW version running before flash?
3.) ROM version running before flash?
4.) Last but not least: which of my packs did you flash that wiped your phone?

Stuff to consider when swapping to Android N (7.0.0):
  • TWRP is not compatible with Android 7 on the HTC10 yet. People are working on it. This means you need to downgrade to old firmware with TWRP before flashing a ROM or an OTA, because that won't currently work.
  • Downgrading firmware from 2.xx to 1.xx has so far worked (testing with Team Venom people) - although there was a brick while downgrading on a phone running an earlier test base. So be careful. We at team venom do not yet feel quite safe with this, neither should you!
  • In some scenarios, you WILL lose all your data (a.k.a have a wipe) even if you use the NoWipe - the exact scenario isn't clear yet, I am still looking for info to figure this out. Most likely using 2.28 NoWipe on a 1.95 based FW and ROM setup is causing a wipe - the guess goes towards changed encryption causing it).
  • Should you ever encounter a "Semi-Brick" where you can still get into bootloader-mode but NOT into download, recovery or system, you can use the Bootloader mode to flash all images of a firmware pack manually by running "htc_fastboot flash recovery recovery.img" (there is a full list of flash commands and corresponding images somewhere, but basically its the image name that is the flash command, e.g. for recovery its "flash recovery recovery.img." and for adsp its "flash adsp adsp.img").
  • This type of Semi-Brick happens when people try to swap out keymaster-image, e.g. flash keymaster from 2.28 into 1.95 environment or vice versa (people trying to get TWRP to work did that and broke their phones with that), but it is likely that mixing other firmware images from different generations can also cause this or worse. Little reminder: the HTC10 is quite the finnicky device - it really doesn't like non-standard procedures. It easily breaks.
 
Last edited:

Alan-B

Senior Member
May 6, 2006
1,201
1,279
71
WAVRE
Hi,
My HTC 10 is S-OFF and ulocked.
I tested the version not wip who it is ended with a bootloop !!
As more access to TWRP even in memory very difficult to restore a backup! Just access by fastboot, and re flash a TWRP does not work.
The solution in summer to spend by one complete version 1.7Giga (with fastboot), install has new TWRP and to restore a backup.
 
  • Like
Reactions: Sneakyghost

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,743
7,572
50
Beirut
@Sneakyghost

This is my personal experience so far (bear with me it's a bit long, and sorry for the bad formatting :eek:):

  1. ROM: Viper10 2.5.0
  2. Firmware directly from version-main: 1.80.401.3 to 2.28.401.6
  3. reboot -> stuck in bootloop, at bootsplash (for about 5~10secs) it won't reach bootanimation.
  • Force reboot (POWER+VOLDOWN+VOLUP) to download mode
  1. Reflash PMEUHL_1.95.401.4_NoWipe_TWRP3026
  2. TWRP works and decrypts properly no data loss
  1. Flash Viper10 3.5.0, bootup
  2. Reflash 2.28.401.6
  3. reboot -> stuck in bootloop again same as above
So I guess firmware is no longer "backwards" compatible with older ROMs :( (At least it didn't work for me. I'm assuming that's why TWRP wont currently boot on new firmware).

  1. Back to PMEUHL_1.95.401.4_NoWipe_TWRP3026, use it to dirty flash Viper10 4.0.0
  2. Boot up, and everything is fine no data loss
  3. Back to TWRP3026, and yep, it can no longer decrypt.
  1. Back to download mode, reflash PMEUHL_2.28.401.6_NoWipe_TWRP3026.zip
  2. Try entering TWRP3026, and yep it hangs for a few seconds on bootsplash, then reboots back to Viper10 4.0.0, no data loss
And finally back to 1.95.401.4 firmware, back to TWRP, etc.
  • No data loss
  • TWRP decryption no longer works


Notes:
  • As mentioned, I only used your PMEUHL_x.xx.401.x_NoWipe_TWRP3026.zip packages.

Phone details:
  • S-OFF
  • Bootloader UNLOCKED
  • (bootloader) product: htc_pmeuhl
  • (bootloader) mid: 2PS620000

 
T

tony_5309

Guest
Ok guys, i just did a test totally risking my phone. I had bone stock US Unlocked Nougat on my phone official ota and successfully downgraded by just running a MM ruu.exe (1.96.617.2). i installed TWRP after and everything worked as if Nougat was never on my phone.
I even went ahead and converted back to International HTC__001 for the heck of it. Just thought you all might like to hear that who wants to downgrade. Now just be aware, i was totally stock.
 
Last edited:

afuller42

Senior Member
Apr 1, 2014
1,114
381
37
Owatonna, MN
Ok guys, i just did a test totally risking my phone. I had bone stock US Unlocked Nougat on my phone official ota and successfully downgraded by just running a MM ruu.exe (1.96.617.2). i installed TWRP after and everything worked as if Nougat was never on my phone.
I even went ahead and converted back to International HTC__001 for the heck of it. Just thought you all might like to hear that who wants to downgrade. Now just be aware, i was totally stock.

Thanks for the info.

But many many people have already downgraded successfully due to the fact lots of things are still not working on n. For example viper audio and xposed are 2 big ones
 

emrug

Senior Member
Jul 28, 2013
175
65
Your help here will be appreciated

I need your help Guys. I've flashed Firmware(s) before and its been successful but this time my Phone decided to brick or retire.
(S-OFF and Rooted)
This is what i did:
-Download Mode
-fastboot oem rebootRUU
-fastboot flash zip firmware.zip

After this it normally shows fail, restart itself into RUU mod and then we immediately run fastboot flash zip firmware.zip command again. But my Phone decided not to restart, it just went black and does not respond to anything. Even if i press the buttons forever, charging led does not show, the PC does not recognize it. I mean it is in total sleep, not sure if it'll wake up anytime soon.


C:\Users\manue\Desktop\HTC10\ADB FASTBOOT FILES WINDOWS>fastboot oem rebootRUU
...
OKAY [ 0.203s]
finished. total time: 0.203s

C:\Users\manue\Desktop\HTC10\ADB FASTBOOT FILES WINDOWS>fastboot flash zip "C:\Users\manue\Desktop\HTC10\ADB FASTBOOT FILES WINDOWS\firmware.zip"
sending 'zip' (94569 KB)...
OKAY [ 4.122s]
writing 'zip'...
(bootloader) HOSD CL#831921
(bootloader) Perform pre-update
(bootloader) get 11 images from zip(zip_type=3)
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
FAILED (remote: 90 hboot pre-update! please flush image again immediately )
finished. total time: 6.036s

It didn't restart into RUU Mod, turned off indefinitely.
 
Last edited:

i$tickitinyour$u$hi

Senior Member
Jan 11, 2011
58
13
Stuttgart
I need your help Guys. I've flashed Firmware(s) before and its been successful but this time my Phone decided to brick or retire.
(S-OFF and Rooted)
This is what i did:
-Download Mode
-fastboot oem rebootRUU
-fastboot flash zip firmware.zip

After this it normally shows fail, restart itself into RUU mod and then we immediately run fastboot flash zip firmware.zip command again. But my Phone decided not to restart, it just went black and does not respond to anything. Even if i press the buttons forever, charging led does not show, the PC does not recognize it. I mean it is in total sleep, not sure if it'll wake up anytime soon.


C:\Users\manue\Desktop\HTC10\ADB FASTBOOT FILES WINDOWS>fastboot oem rebootRUU
...
OKAY [ 0.203s]
finished. total time: 0.203s

C:\Users\manue\Desktop\HTC10\ADB FASTBOOT FILES WINDOWS>fastboot flash zip "C:\Users\manue\Desktop\HTC10\ADB FASTBOOT FILES WINDOWS\firmware.zip"
sending 'zip' (94569 KB)...
OKAY [ 4.122s]
writing 'zip'...
(bootloader) HOSD CL#831921
(bootloader) Perform pre-update
(bootloader) get 11 images from zip(zip_type=3)
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
FAILED (remote: 90 hboot pre-update! please flush image again immediately )
finished. total time: 6.036s

It didn't restart into RUU Mod, turned off indefinitely.

had the same problem, flashed the international ota 2.28.401.6
at the second flash it worked but ends up in a bootloop :p
(s-off and unlocked)
 

emrug

Senior Member
Jul 28, 2013
175
65
had the same problem, flashed the international ota 2.28.401.6
at the second flash it worked but ends up in a bootloop :p
(s-off and unlocked)
What makes mine worse is the PC can't recognize it, meaning i can't play with it anymore. The computer stays on waiting waiting for device. :crying:
 

xunholyx

Recognized Contributor
Dec 3, 2012
7,692
5,235
Vancouver
Google Pixel 2 XL
Google Pixel 5
I need your help Guys. I've flashed Firmware(s) before and its been successful but this time my Phone decided to brick or retire.
(S-OFF and Rooted)
This is what i did:
-Download Mode
-fastboot oem rebootRUU
-fastboot flash zip firmware.zip

After this it normally shows fail, restart itself into RUU mod and then we immediately run fastboot flash zip firmware.zip command again. But my Phone decided not to restart, it just went black and does not respond to anything. Even if i press the buttons forever, charging led does not show, the PC does not recognize it. I mean it is in total sleep, not sure if it'll wake up anytime soon.


C:\Users\manue\Desktop\HTC10\ADB FASTBOOT FILES WINDOWS>fastboot oem rebootRUU
...
OKAY [ 0.203s]
finished. total time: 0.203s

C:\Users\manue\Desktop\HTC10\ADB FASTBOOT FILES WINDOWS>fastboot flash zip "C:\Users\manue\Desktop\HTC10\ADB FASTBOOT FILES WINDOWS\firmware.zip"
sending 'zip' (94569 KB)...
OKAY [ 4.122s]
writing 'zip'...
(bootloader) HOSD CL#831921
(bootloader) Perform pre-update
(bootloader) get 11 images from zip(zip_type=3)
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
FAILED (remote: 90 hboot pre-update! please flush image again immediately )
finished. total time: 6.036s

It didn't restart into RUU Mod, turned off indefinitely.

Here's how to fix it, thanks to @nkk71 and @Mikee4fun

Unzip the firmware on your PC with 7zip.
In the firmware there is a partition file. It tells you the partition names.
Partition Info:[0.20]
board_info board_info.bin 32 90
mfg mfg.bin 512 115
pg1fs none 8192 93
pg2fs none 48510 91
xbl xbl.img 4096 77
tz tz.img 4096 70
rpm rpm.img 1024 71
pmic pmic.img 1024 79
hyp hyp.img 1024 78
aboot aboot.img 8192 80
hosd hosd.img 131072 113
tool_diag none 20480 98
devinfo none 2 119
devcfg devcfg.img 256 120
lksecapp lksecapp.img 256 121
cmnlib32 cmnlib32.img 512 122
cmnlib64 cmnlib64.img 512 123
apdp apdp.img 512 124
msadp none 512 125
dpo none 2 126
sp1 none 20480 52
ddr none 2048 171
cdt none 2 127
rfg_0 none 2048 116
rfg_1 none 2048 116
rfg_2 rfg_2.img 2048 116
rfg_3 none 2048 116
rfg_4 none 2048 116
fsg none 4096 172
radio radio.img 143360 73
adsp adsp.img 40960 73
fp fp.img 4096 73
slpi slpi.img 20480 73
mdtp none 65536 73
dip none 2048 128
venus venus.img 4096 131
reserve1 none 8762 98
misc misc.nb0 2048 118
modemst1 modemst1.img 4096 74
modemst2 modemst2.img 4096 75
fataldevlog none 40960 25
devlog none 61440 25
local none 2562 51
extra none 128 131
fsc none 2 173
rfg_8 none 2048 116
ssd none 16 174
persist none 65536 83
sec none 256 82
frp none 1024 134
ramdump none 20480 84
skylink none 2 131
carrier none 92160 87
keystore none 1024 112
keymaster keymaster.img 1024 135
mota none 2048 133
dsp none 32768 73
reserve2 none 26730 98
boot boot.img 131072 72
recovery recovery.img 131072 113
cache none 458752 131
system system_raw.img 7831552 131
###LAST###
userdata none 20676608 131
cradio cradio.img 131072 73
apppreload none 122880 53
cota none 122880 55


Start at the top one at a time
Paste all the firmware files in your fast boot directory (except the ones that say none of course)

Plug in your phone to the charger
Not your computer
Hold down the power button and then hold down volume up and down keys
Keep holding them until you see the bootloader
The HTC10 is a finicky device
Sometimes you have to wait a bit

Now hook up to your PC

Then in the cmd prompt of the directory start flashing one at a time
DO NOT FLASH ABOOT THOUGH
I REPEAT DO NOT DO IT

flash everything else
So, example fastboot flash radio radio.img, fastboot flash modemst1 modemst1.img, etc....
Good luck!
 

emrug

Senior Member
Jul 28, 2013
175
65
Thank you very!!

Here's how to fix it, thanks to @nkk71 and @Mikee4fun

Unzip the firmware on your PC with 7zip.
In the firmware there is a partition file. It tells you the partition names.
Partition Info:[0.20]
board_info board_info.bin 32 90
mfg mfg.bin 512 115
pg1fs none 8192 93
pg2fs none 48510 91
xbl xbl.img 4096 77
tz tz.img 4096 70
rpm rpm.img 1024 71
pmic pmic.img 1024 79
hyp hyp.img 1024 78
aboot aboot.img 8192 80
hosd hosd.img 131072 113
tool_diag none 20480 98
devinfo none 2 119
devcfg devcfg.img 256 120
lksecapp lksecapp.img 256 121
cmnlib32 cmnlib32.img 512 122
cmnlib64 cmnlib64.img 512 123
apdp apdp.img 512 124
msadp none 512 125
dpo none 2 126
sp1 none 20480 52
ddr none 2048 171
cdt none 2 127
rfg_0 none 2048 116
rfg_1 none 2048 116
rfg_2 rfg_2.img 2048 116
rfg_3 none 2048 116
rfg_4 none 2048 116
fsg none 4096 172
radio radio.img 143360 73
adsp adsp.img 40960 73
fp fp.img 4096 73
slpi slpi.img 20480 73
mdtp none 65536 73
dip none 2048 128
venus venus.img 4096 131
reserve1 none 8762 98
misc misc.nb0 2048 118
modemst1 modemst1.img 4096 74
modemst2 modemst2.img 4096 75
fataldevlog none 40960 25
devlog none 61440 25
local none 2562 51
extra none 128 131
fsc none 2 173
rfg_8 none 2048 116
ssd none 16 174
persist none 65536 83
sec none 256 82
frp none 1024 134
ramdump none 20480 84
skylink none 2 131
carrier none 92160 87
keystore none 1024 112
keymaster keymaster.img 1024 135
mota none 2048 133
dsp none 32768 73
reserve2 none 26730 98
boot boot.img 131072 72
recovery recovery.img 131072 113
cache none 458752 131
system system_raw.img 7831552 131
###LAST###
userdata none 20676608 131
cradio cradio.img 131072 73
apppreload none 122880 53
cota none 122880 55


Start at the top one at a time
Paste all the firmware files in your fast boot directory (except the ones that say none of course)

Plug in your phone to the charger
Not your computer
Hold down the power button and then hold down volume up and down keys
Keep holding them until you see the bootloader
The HTC10 is a finicky device
Sometimes you have to wait a bit

Now hook up to your PC

Then in the cmd prompt of the directory start flashing one at a time
DO NOT FLASH ABOOT THOUGH
I REPEAT DO NOT DO IT

flash everything else
So, example fastboot flash radio radio.img, fastboot flash modemst1 modemst1.img, etc....
Good luck!
Thank you very much for your response, i will try it later today and get back to you.
 

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,743
7,572
50
Beirut
Here's how to fix it, thanks to @nkk71 and @Mikee4fun

Unzip the firmware on your PC with 7zip.
In the firmware there is a partition file. It tells you the partition names.
Partition Info:[0.20]


Start at the top one at a time
Paste all the firmware files in your fast boot directory (except the ones that say none of course)

Plug in your phone to the charger
Not your computer
Hold down the power button and then hold down volume up and down keys
Keep holding them until you see the bootloader
The HTC10 is a finicky device
Sometimes you have to wait a bit

Now hook up to your PC

Then in the cmd prompt of the directory start flashing one at a time
DO NOT FLASH ABOOT THOUGH
I REPEAT DO NOT DO IT

flash everything else
So, example fastboot flash radio radio.img, fastboot flash modemst1 modemst1.img, etc....
Good luck!
Small overkill about "all the partitions" imho, I would stay away from sensitive ones
(mfg, board_info, etc)
;)


I need your help Guys. I've flashed Firmware(s) before and its been successful but this time my Phone decided to brick or retire.
(S-OFF and Rooted)
This is what i did:
-Download Mode
-fastboot oem rebootRUU
-fastboot flash zip firmware.zip

After this it normally shows fail, restart itself into RUU mod and then we immediately run fastboot flash zip firmware.zip command again. But my Phone decided not to restart, it just went black and does not respond to anything. Even if i press the buttons forever, charging led does not show, the PC does not recognize it. I mean it is in total sleep, not sure if it'll wake up anytime soon.


C:\Users\manue\Desktop\HTC10\ADB FASTBOOT FILES WINDOWS>fastboot oem rebootRUU
...
OKAY [ 0.203s]
finished. total time: 0.203s

C:\Users\manue\Desktop\HTC10\ADB FASTBOOT FILES WINDOWS>fastboot flash zip "C:\Users\manue\Desktop\HTC10\ADB FASTBOOT FILES WINDOWS\firmware.zip"
sending 'zip' (94569 KB)...
OKAY [ 4.122s]
writing 'zip'...
(bootloader) HOSD CL#831921
(bootloader) Perform pre-update
(bootloader) get 11 images from zip(zip_type=3)
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
FAILED (remote: 90 hboot pre-update! please flush image again immediately )
finished. total time: 6.036s

It didn't restart into RUU Mod, turned off indefinitely.

Thank you very much for your response, i will try it later today and get back to you.

I really doubt you were flashing anything taken from this thread, because this looks wrong:
(bootloader) get 11 images from zip(zip_type=3)

(as well as a couple of other things)

looks like you were flashing an firmware.zip extracted from and ota.zip, and didn't do it incrementally, which is bad (as you have noticed unfortunately)
 
  • Like
Reactions: xunholyx

razor54

Member
Jan 7, 2015
27
1
I am currently on FW 1.95.401.3, can I upgrade directly to 2.28.401.6 or I have to take the .4 first?
 
Last edited:

emrug

Senior Member
Jul 28, 2013
175
65
Small overkill about "all the partitions" imho, I would stay away from sensitive ones
(mfg, board_info, etc)
;)






I really doubt you were flashing anything taken from this thread, because this looks wrong:
(bootloader) get 11 images from zip(zip_type=3)

(as well as a couple of other things)

looks like you were flashing an firmware.zip extracted from and ota.zip, and didn't do it incrementally, which is bad (as you have noticed unfortunately)
That's right @nkk71, it wasn't from this thread. It was from OTA which i flashed before and it flushed successfully, I don't know what went wrong this time.

In case I make it to the Boatloader which sensitive files should I avoid?

---------- Post added at 08:28 PM ---------- Previous post was at 08:20 PM ----------

Here's how to fix it, thanks to @nkk71 and @Mikee4fun

Unzip the firmware on your PC with 7zip.
In the firmware there is a partition file. It tells you the partition names.
Partition Info:[0.20]
board_info board_info.bin 32 90
mfg mfg.bin 512 115
pg1fs none 8192 93
pg2fs none 48510 91
xbl xbl.img 4096 77
tz tz.img 4096 70
rpm rpm.img 1024 71
pmic pmic.img 1024 79
hyp hyp.img 1024 78
aboot aboot.img 8192 80
hosd hosd.img 131072 113
tool_diag none 20480 98
devinfo none 2 119
devcfg devcfg.img 256 120
lksecapp lksecapp.img 256 121
cmnlib32 cmnlib32.img 512 122
cmnlib64 cmnlib64.img 512 123
apdp apdp.img 512 124
msadp none 512 125
dpo none 2 126
sp1 none 20480 52
ddr none 2048 171
cdt none 2 127
rfg_0 none 2048 116
rfg_1 none 2048 116
rfg_2 rfg_2.img 2048 116
rfg_3 none 2048 116
rfg_4 none 2048 116
fsg none 4096 172
radio radio.img 143360 73
adsp adsp.img 40960 73
fp fp.img 4096 73
slpi slpi.img 20480 73
mdtp none 65536 73
dip none 2048 128
venus venus.img 4096 131
reserve1 none 8762 98
misc misc.nb0 2048 118
modemst1 modemst1.img 4096 74
modemst2 modemst2.img 4096 75
fataldevlog none 40960 25
devlog none 61440 25
local none 2562 51
extra none 128 131
fsc none 2 173
rfg_8 none 2048 116
ssd none 16 174
persist none 65536 83
sec none 256 82
frp none 1024 134
ramdump none 20480 84
skylink none 2 131
carrier none 92160 87
keystore none 1024 112
keymaster keymaster.img 1024 135
mota none 2048 133
dsp none 32768 73
reserve2 none 26730 98
boot boot.img 131072 72
recovery recovery.img 131072 113
cache none 458752 131
system system_raw.img 7831552 131
###LAST###
userdata none 20676608 131
cradio cradio.img 131072 73
apppreload none 122880 53
cota none 122880 55


Start at the top one at a time
Paste all the firmware files in your fast boot directory (except the ones that say none of course)

Plug in your phone to the charger
Not your computer
Hold down the power button and then hold down volume up and down keys
Keep holding them until you see the bootloader
The HTC10 is a finicky device
Sometimes you have to wait a bit

Now hook up to your PC

Then in the cmd prompt of the directory start flashing one at a time
DO NOT FLASH ABOOT THOUGH
I REPEAT DO NOT DO IT

flash everything else
So, example fastboot flash radio radio.img, fastboot flash modemst1 modemst1.img, etc....
Good luck!

Prayed for my luck all day, unfortunately it still doesn't want to work. Pressed down Power, Volume Up and Down buttons together almost forever (like 20 mins) while plugged to the Charger and nothing came up. :confused:
Will keep trying!! Thanks, will let you if it works.
 
Last edited:

Sneakyghost

Senior Member
Jul 24, 2008
8,305
13,584
InMyHead
I knew these things were coming and I didn't like the idea of it. I am sorry for the guys breaking their phones. Seriously.
There are three things I would like to say in relation to that:

1.) Thank you guys for providing vital info, especially helping to clear up which scenarios exactly lead to bricks.
2.) Going through my information and actually taking it serious would have prevented at least the last brick. This is because: I clearly state that I am making my firmware packs full versions, not incremental ones, because we know at least since the M7 that "Frankenbuilds" (non-incremental flashing, mixed firmware generations of any kind) occasionally create bricks. Not always, but occasionally. The HTC10's behaviour reminds me of the M7 quite a lot in regards to this. @nkk71 calls it a "finicky device" - meaning, it doesn't like procedures off the official tracks.
3.) I suggest everyone coming here from now on observes what happens on the thread very closely and sticks to the suggested procedures to the T. Very simple. Use my full packs, do not mix, do not use the OTA firmwares if you are not 100% certain you know what you do. Try to avoid downgrades for now if not absolutely necessary (I am right now up- and downgrading a lot because of incompatible TWRP, but this is not good). Also make sure you use the sdcard method if your fastboot environment (USB drivers etc) is unstable. If your sdcard has had the "sdcard was unexpectedly removed" issue, if it keeps unmounting while you are using your phone, it has bad NAND and should NOT be used for flashing. Get a good sdcard or use the fastboot method as suggested on page 1. Do not frequently work with a method you know is unreliable. The HTC10 is a finicky device. Do not forget that. It doesn't forgive mistakes as much as the M8 and M9 did.

[EDIT]
Oh and one more thing:
Many, many thanks to the people providing solid support here. I am very sorry but I cannot be here much these days. Work is absolutely eating up all my time and the little off time I have I need to use for my private life. Thank you for understanding.
I do NOT provide support to individual people on private messaging. Please refrain from asking for help privately.

Thank you @xunholyx, @Kratos90 and @Black-FR from Team Venom and all my regular, polite helping visitors.
 
Last edited:

Fredz

Senior Member
Oct 23, 2006
131
6
Hello guys. I'm facing the problem that I'm not able to restart the phone into recovery or into system after 2.28.401.6 firmware update (I've flashed it twice and finished OK). I flash back 1.95.401.4 firmware (the firmware I come from) and I'm now able to go into recovery and system. But the system doesn't recognize my pin code and the gsm signal doesn't seems to work. I'm currently trying to do a clean installation of ICE ROM (full wipe). I'll let you know the result.

[EDIT] I Confirm, that now, I can start my phone and that I recover the gsm signal.
Hope this can help.
 
Last edited:

ThePhoneGeek

Senior Member
May 13, 2012
1,271
582
An Undisclosed Location
Here's how to fix it, thanks to @nkk71 and @Mikee4fun

Unzip the firmware on your PC with 7zip.
In the firmware there is a partition file. It tells you the partition names.
Partition Info:[0.20]
board_info board_info.bin 32 90
mfg mfg.bin 512 115
pg1fs none 8192 93
pg2fs none 48510 91
xbl xbl.img 4096 77
tz tz.img 4096 70
rpm rpm.img 1024 71
pmic pmic.img 1024 79
hyp hyp.img 1024 78
aboot aboot.img 8192 80
hosd hosd.img 131072 113
tool_diag none 20480 98
devinfo none 2 119
devcfg devcfg.img 256 120
lksecapp lksecapp.img 256 121
cmnlib32 cmnlib32.img 512 122
cmnlib64 cmnlib64.img 512 123
apdp apdp.img 512 124
msadp none 512 125
dpo none 2 126
sp1 none 20480 52
ddr none 2048 171
cdt none 2 127
rfg_0 none 2048 116
rfg_1 none 2048 116
rfg_2 rfg_2.img 2048 116
rfg_3 none 2048 116
rfg_4 none 2048 116
fsg none 4096 172
radio radio.img 143360 73
adsp adsp.img 40960 73
fp fp.img 4096 73
slpi slpi.img 20480 73
mdtp none 65536 73
dip none 2048 128
venus venus.img 4096 131
reserve1 none 8762 98
misc misc.nb0 2048 118
modemst1 modemst1.img 4096 74
modemst2 modemst2.img 4096 75
fataldevlog none 40960 25
devlog none 61440 25
local none 2562 51
extra none 128 131
fsc none 2 173
rfg_8 none 2048 116
ssd none 16 174
persist none 65536 83
sec none 256 82
frp none 1024 134
ramdump none 20480 84
skylink none 2 131
carrier none 92160 87
keystore none 1024 112
keymaster keymaster.img 1024 135
mota none 2048 133
dsp none 32768 73
reserve2 none 26730 98
boot boot.img 131072 72
recovery recovery.img 131072 113
cache none 458752 131
system system_raw.img 7831552 131
###LAST###
userdata none 20676608 131
cradio cradio.img 131072 73
apppreload none 122880 53
cota none 122880 55


Start at the top one at a time
Paste all the firmware files in your fast boot directory (except the ones that say none of course)

Plug in your phone to the charger
Not your computer
Hold down the power button and then hold down volume up and down keys
Keep holding them until you see the bootloader
The HTC10 is a finicky device
Sometimes you have to wait a bit

Now hook up to your PC

Then in the cmd prompt of the directory start flashing one at a time
DO NOT FLASH ABOOT THOUGH
I REPEAT DO NOT DO IT

flash everything else
So, example fastboot flash radio radio.img, fastboot flash modemst1 modemst1.img, etc....
Good luck!

Question...
My device is a US unlocked ver that was running 1.95.401.4 and had been hung up in bootloop during initial boot after loading Viper 4 but before the FW upgrade. Ultimately what I needed to do was flash the FULL Wipe FW 1.96.617.20 (after changing CID/MID back to US unl), then load TWRP, then load Viper 4, boot, then upgrade to FW 2.28.617.8.

Ultimately I'd like to go back to the .401 FW because the .617 radio is horrible. Is the process you've outlined suitable for this or is it feasible to just flash the radio from the .401 FW?

Thx to the group for all the time and effort you invest!
 

xunholyx

Recognized Contributor
Dec 3, 2012
7,692
5,235
Vancouver
Google Pixel 2 XL
Google Pixel 5
[/HIDE]
Question...
My device is a US unlocked ver that was running 1.95.401.4 and had been hung up in bootloop during initial boot after loading Viper 4 but before the FW upgrade. Ultimately what I needed to do was flash the FULL Wipe FW 1.96.617.20 (after changing CID/MID back to US unl), then load TWRP, then load Viper 4, boot, then upgrade to FW 2.28.617.8.

Ultimately I'd like to go back to the .401 FW because the .617 radio is horrible. Is the process you've outlined suitable for this or is it feasible to just flash the radio from the .401 FW?

Thx to the group for all the time and effort you invest!

You should be able to flash just the radio.img I think. It isn't something I've ever tried myself, but I don't see any reason why it wouldn't work. I'm pretty sure I've seen posts from others who have done it.
 
Last edited:
  • Like
Reactions: Sneakyghost

Top Liked Posts

  • There are no posts matching your filters.
  • 103
    Post_Header_Sneakyghost_FIRMWARE.png

    FIRST THINGS FIRST:
    • This is for GSM PHONES which have been set S-OFF - no CDMA (Sprint & Verizon) here! S-ON people: Please refer to HTC RUU methods or "Stock Backup and OTA" method. (not provided here).
    • Read from top to bottom. No skipping of stuff or you will be confused.
    • I cannot accept any liability and/or responsibility for these firmware packs. I am not able to go through the time consuming process of testing each pack, hence community members are called to test these on their own. I am gladly accepting constructive feedback.

    Purpose of this thread:
    • Suitable methods for flashing firmware when S-OFF.
    • Error handling strategies - collection of known errors and their meanings (Post 3).
    • Reliable background information for safe flashing (Post 5 mainly).
    • Providing FULL, non-incremental firmware files (Post 2) to update coming from ANY version (applies to my FullStock as well as NoWipe packs!).
    • Providing a simple ADB environment with a basic batch script (Post 4)


    Flashing methods:
    • The safest way is still HTCs RUU and OTA method. US RUUs can be accessed via HTC's US Support Site. Jump to your device, then click "View" and scroll down for the download-link. The page has Dev/Unlocked (617), Sprint (651), AT&T (502) and T-Mobile US (531) covered. RUU's are superior to other flashing methods because they carry lab tested combinations of partition images and the method itself is also known to work well (plus the psychological advantage).
      Other than HTC's original OTA's which are "incremental", My packages are always FULL packages (applies to my NoWipe as well! It can also be considered a FULL update as opposed to incremental) - with these you can safely jump from a very old firmware right up to the newest. Following this original RUU / OTA method, come the methods most suitable for my packs:
    • My preferred method is the "Fastboot method", which needs a PC or Mac or Linux computer. I will be detailing how to fastboot flash firmware further down.
    • The "SDCard Method" can be considered the fastest and most suitable for people without a PC. I will be detailing how to SDCard flash firmware further down.

    An explainer to the ZIP variants provided here:
    • Full Stock WIPE ZIPs:
      NOTICE: FullStock zips currently permanently break the phones ability to receive HTC stock OTA's - to restore your OTA functionality, refer to post #5 for more information!
      Only System removed (and encryption broken) - Everything else stock! This type of zip also re-flashes the /data partition with HTC's DZDATA files (meaning you loose everything on your internal SDCARD). Also replaces the Kernel, recovery and Splash1 with latest stock images! The /system partition will not be touched. (Else this would be a RUU.zip). It also includes the "apppreload.img" with all the carrier-bloatware (WWE has no bloat in there!).
      Be sure to put a ROM onto your EXTERNAL SD before proceeding with a Full WIPE ZIP! If you forgot to put a zip on your sdcard: you can reflash TWRP with Fastboot (use my batch tool) and then choose between ADB file push, MTP transfer or even USB mass storage transfer mode. Last but not least you can take out the sdcard and use a card-reader with your computer. Phone will NOT boot without ROM reflash after using this!
    • NoWipe ZIPs:
      These packages are modified. This type of ZIP updates basic Firmware partitions, does not touch the /data partition, leaves kernel, splash and ramdisk (in order to support custom ROM's modifying ramdisk) alone. The "apppreload.img" is removed, the bloatware partition will remain unchanged (to remove already existing bloat permanently flash apppreload.img from International/WWE/401, it is an empty image). Recovery will be replaced with the current TWRP. Phone should in most cases boot normally after using this.
    • And what you won't get here (fine print):
      Since this is a Firmware Update Thread and not a ROM thread, you do NOT EVER get a ROM (a.k.a "System.img" or plain: "System" here. You understand and agree that you cannot have this from me. You also acknowledge that I cannot be blamed for your non-booting phone due to you not reading or not understanding this. You may find stock system backups here


    How to flash firmware.zip's using fastboot

    Prerequisites:

    You need ADB and Fastboot on your PC. To get ADB and Fastboot up and running I strongly suggest you use my "Batch Tool" setup, because it contains an updated htc_fastboot, which is 100% working with the HTC 10 . This is important: the generic Google fastboot from SDK API Level 24 (latest at time of writing) is NOT FULLY COMPATIBLE.

    The method outlined here does apply to my zips as well as HTC signed zips. The difference is, that for my zips, S-OFF is mandatory, while HTC signed zips can under certain conditions also be flashed to S-ON phones, however, different prerequisites and risks apply there. I will not cover HTC signed zips here as they are fundamentally different in some aspects while the flashing method remains the same.

    Note: use "htc_fastboot" with my batch tool. If you use another ADB/Fastboot set, it will probably be Google Fastboot and then the commands should be starting with "fastboot".


    Step-By-Step:
    1. If device is booted into Android, reboot into download mode by running:
    Code:
    adb reboot download

    NOTICE: adb reboot download is new since the M9 for those who come from earlier HTC devices - zips can be flashed in download mode or RUUMode, both work. The on-screen status report is more detailed in download mode. This making it the preferred flashing mode for now.

    1.a Or else, if your device is in a different state or you just prefer the button method:
    In Android: Press and hold Power and VolDown at the same time for approx. 15 seconds, when the screen and charging LED go dark immediately let go of power, keep holding VolDown a little longer.
    During Boot and sometimes when booted into Recovery: Press and hold Power, VolDown and VolUp at the same time for approx. 15 seconds, when the screen and charging LED go dark immediately let go of power and VolUp, keep holding VolDown a little longer.

    When in download mode, use the VolUp and VolDown buttons to navigate up and down and use Power to confirm.

    2. Now place the Firmware_xx.zip into your adb/fastboot folder (which will be "C:\Android\com" if you use my Batch Tool).

    3. Followed by:
    Code:
    htc_fastboot flash zip Firmware_xx.zip
    (replace "Firmware_xx.zip" with the name of your zip)

    4. Now check the console output. It should approximately look like this log:

    NOTICE: this flash log is taken from a NoWipe (not all images included) flash on my HTC 10. New is also (compared to M7, M8) that the checking routine is way more sophisticated and Controller Firmware for e.g. the touch panel or the Infra Red Remote (One Series only, not available on the HTC10) and the like do NOT get flashed if the checks determine that they are already up-to-date. Images that do not get flashed show "BYPASSED", which is NOT an error.

    Microsoft Windows [Version 10.0.10586]
    (c) 2015 Microsoft Corporation. Alle Rechte vorbehalten.

    C:\Android\com>htc_fastboot flash zip rom.zip
    htc_fastboot v3.0.9.2 (2015-05-29)
    target reported max download size of 800000000 bytes
    sending 'zip' (85525 KB)...
    OKAY [ 4.307s]
    writing 'zip'...
    (bootloader) HOSD CL#738269
    (bootloader) GPT is up-to-dated. [17408]
    (bootloader) Perform pre-update
    (bootloader) [email protected]
    (bootloader) [email protected]%
    (bootloader) [email protected]
    (bootloader) [email protected]
    (bootloader) [email protected]
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]
    (bootloader) [email protected]
    (bootloader) [email protected]%
    (bootloader) [email protected]
    (bootloader) [email protected]
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]
    (bootloader) [email protected]
    (bootloader) [email protected]
    (bootloader) [email protected]%
    (bootloader) [email protected]
    (bootloader) [email protected]
    (bootloader) [email protected]
    (bootloader) [email protected]%
    (bootloader) [email protected]
    (bootloader) [email protected]
    (bootloader) [email protected]
    (bootloader) [email protected]%
    (bootloader) [email protected]
    (bootloader) [email protected]
    (bootloader) [email protected]
    (bootloader) [email protected]%
    (bootloader) [email protected]
    FAILED (remote: 90 hboot pre-update! please flush image again immediately )
    finished. total time: 6.004s
    htc_fastboot finished. total time: 6.110s

    C:\Android\com>htc_fastboot flash zip rom.zip
    htc_fastboot v3.0.9.2 (2015-05-29)
    target reported max download size of 800000000 bytes
    sending 'zip' (85525 KB)...
    OKAY [ 5.312s]
    writing 'zip'...
    (bootloader) HOSD CL#738269
    (bootloader) GPT is up-to-dated. [17408]
    (bootloader) [email protected]
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]%
    (bootloader) [email protected]
    (bootloader) [email protected]
    (bootloader) [email protected]
    (bootloader) [email protected]
    (bootloader) Update zip file OK
    (bootloader) [email protected]
    OKAY [ 15.235s]
    finished. total time: 20.547s
    htc_fastboot finished. total time: 25.326s

    C:\Android\com>


    Important: Should you decide to flash in RUUMode (instead of Download Mode like suggested further up), the flash process halts at around 90% on phone screen! This is normal and a safety precaution! The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output to make sure it is safe to reboot! The bar will only fill up to 100% once you type:
    Code:
    htc_fastboot  reboot
    Important: Download Mode flashes finish at 100% on phone screen and in console and ask you to hit Power to return to Download Mode screen.

    IF you encounter any errors which are not "FAIL90", have a look into Post #3 or ask in the thread! DO NOT reboot the device until you have an idea what happened!

    5a.
    Code:
    htc_fastboot reboot-bootloader
    or press Power to return to Download Mode screen - depending on the mode you used to flash the zip. In Download Mode and Bootloader you can go to either regular reboot or shut-down the device via button navigation.

    5b. Optional:
    Code:
    htc_fastboot reboot
    to just reboot the phone to Android.​



    How to flash firmware using SDCard Method
    Prerequisites:
    • Compatible SDCard, should be formatted with FAT32 for older firmware, newer firmware can also handle ExtFS formatted cards.
    • A firmware.zip you would like to flash, taken from Post #2 (Downloads)
    • Phone charged up at least 30% (will fail with low power warning if lower than 30%)

    Step-By-Step:
    1. Rename your firmware.zip to exactly "2PS6IMG.zip" - make sure you enable "show file extensions" in Windows Explorer, if you rename it on your PC. Else you might end up with a "2PS6IMG.zip.zip" which won't flash.

    2. Copy your "2PS6IMG.zip" over to the root of your SDCard. Use a cardreader, or MTP protocol in Android or Recovery, or USB Mass Storage protocol in Recovery, or ADB push the file in Android or Recovery - many methods available.

    3. Now, if device is booted into Android, reboot into download mode by running:
    Code:
    adb reboot download

    3.a Or else, if your device is in a different state or you just prefer the button method:
    In Android: Press and hold Power and VolDown at the same time for approx. 15 seconds, when the screen and charging LED go dark immediately let go of power, keep holding VolDown a little longer.
    During Boot and sometimes when booted into Recovery: Press and hold Power, VolDown and VolUp at the same time for approx. 15 seconds, when the screen and charging LED go dark immediately let go of power and VolUp, keep holding VolDown a little longer.

    4. Once Download Mode starts, it will "see" the 2PS6IMG.zip and ask you (yellow text at bottom of screen) if you want to flash the firmware. Press VolUp to confirm and proceed with the flash, or press VolDown to cancel and continue into Download Mode UI.


    5. Now check the screen while it flashes. It should stop at "end UI updating. Press Power to continue" - the phone will now shut off! To turn it back on, press and briefly hold power again.
    47
    Downloads

    Post_Header_Sneakyghost_DOWNLOADS.png
    Recent additions
    Please remember: you're writing to boot-critical parts of your phone. If anything goes wrong along the way, your phone might be bricked.
    • PMEWL_2.51.617.21_Unlocked_FullStock
    • PMEWL_2.51.617.21_Unlocked_TWRP3110_NoWipe
    • PMEWL_2.51.531.21_Unlocked_FullStock
    • PMEWL_2.51.531.21_Unlocked_TWRP3110_NoWipe
    • PMEWL_2.51.617.11_Unlocked_FullStock
    • PMEWL_2.51.617.11_Unlocked_TWRP3110_NoWipe
    • PMEWL_2.51.617.1_Unlocked_FullStock
    • PMEWL_2.51.617.1_Unlocked_TWRP3110_NoWipe
    • PMEWL_2.50.617.2_Unlocked_FullStock
    • PMEWL_2.50.617.2_Unlocked_NoWipe_TWRP3110
    • PMEUHL_2.48.841.3_TELSTRA_FullStock
    • PMEUHL_2.48.841.3_TELSTRA_NoWipe_TWRP3110
    • PMEUHL_2.41.401.41_WWE_FullStock
    • PMEUHL_2.41.401.41_WWE_TWRP3110_NoWipe
    • PMEUL_2.41.531.44_TMUS_FullStock
    • PMEUL_2.41.531.44_TMUS_NoWipe_TWRP3110
    • PMEWL_2.46.617.2_Unlocked_FullStock
    • PMEWL_2.46.617.2_Unlocked_TWRP3101_NoWipe
    • PMEUHL_2.41.401.4_WWE_FullStock
    • PMEUHL_2.41.401.4_WWE_TWRP3030_NoWipe
    • PMEWL_2.41.617.3_Unlocked_FullStock
    • PMEWL_2.41.617.3_Unlocked_TWRP3030_NoWipe
    • PMEUHL_1.92.709.1_Asia-TW_FullStock
    • PMEUHL_1.92.709.1_Asia-TW_TWRP3030_NoWipe
    • PMEUHL_1.98.709.5_R_Asia-TW_FullStock
    • PMEUHL_1.98.709.5_R_Asia-TW_TWRP3030_NoWipe
    • PMEUHL_2.41.709.3_Asia-TW_FullStock
    • PMEUHL_2.41.709.3_Asia-TW_NoWipe_TWRP3030
    • PMEUL_2.37.531.5_TMUS_FullStock
    • PMEUL_2.37.531.5_TMUS_NoWipe_TWRP3030
    • PMEUHL_2.28.401.9_WWE_TWRP3027_NoWipe
    • PMEUHL_2.28.401.6_WWE_TWRP3027_NoWipe
    • PMEWL_2.28.617.8_Unlocked_TWRP3027_NoWipe
    • PMEUHL_2.28.401.9_WWE_FullStock
    • PMEUHL_2.28.401.6_WWE_FullStock
    • PMEWL_2.28.617.8_Unlocked_FullStock

    Download

    Notice:

    • The WWE/401 versions are usually tested by me before release. US Unlocked / 617 is usually tested by at least someone from Venom Beta. Other zips will be flagged completely untested when applicable. Please keep a lookout for my "Notes" in the release posts so you know whether or not a specific zip was tested!
    • REQUESTS: If you want some NoWipe or FullWipe firmware package added, send me the original untouched HTC base files required, either on thread (preferred) or via PM.

    Credits

    I have long lost track of my firmware sources. I am sorry i cannot name you guys all personally. The most common source would be @LlabTooFeR, @djluisbento, @AndroidFileHost (androidruu.com) HTCDev and some occasional random sources that come and go.
    I would also like to express my deepest gratitude to Team Venom, who aren't only good friends but also let me use their graphical stuff as base for my own stuff. Thank you!
    Lately, the biggest props go out to @nkk71 and @Captain_Throwback
    because of their fantastic script that makes running Unruu, Bruutveal and Ruuveal so much easier. Thank you so much for saving me a ton of time and helping users do their own firmware packages! That is quite an example you set there for the community!
    And last but not least: without the work of Team SunShine, firmware flashing like this wouldn’t be possible! Not to be forgotten!
    If you find your stuff here and want to be included in the credits please contact me. I am very grateful for everyone busy providing dumps and direct leaks.


    Disclaimer

    You are aware that writing to security protected, boot-critical partitions 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 well tested, however you are the brains behind the wheel and you are solely responsible for the execution of the process. I will not accept any liability. The method itself is developed by Google and HTC, I only provide access and information to it and I am trying my best to make it understandable and simple. Do not use this if you have difficulties understanding what this is!

    You understand that you should not do it if you are not willing to accept this risk.
    38
    Post_Header_Sneakyghost_BATCH.png

    The Batch Tool - a thing i am using for myself since 2012 and which i am sharing just because i have it. It is neither good nor special, but its the way i work and people who follow the instructions here might find it easier to use the same setup as we do.
    It also has the "FUU" method included - details on that method will be added at a later stage. We do not consider the FUU a good option to flash Firmware anymore because we realized that getting away from ADB and Fastboot with toolkits makes troubleshooting harder at a later stage - people relying entirely on toolkits and tools will mostly not understand what is happening and helping there is much harder.

    Since everything i do basically works out of the C:\Android\com path, all my zipped-up stuff extracts to that location. The FUU and the Task-Batch-Script both work from that location. This is simply to enable easier and faster creation of new zip’s if they all use the same base structure.
    If you prefer to work from a different location. you can specify a different path in the installer. However, the batch scripts do not adjust automatically, which means if you use another path, you might need to open up the scripts in an editor and adjust some paths manually.


    Preview:
    TNnMNV9fhjOdwNBxcVmZSH86pNdGK7K8mz-1mDciD7W00MoNlpJ95MOm5qEgOnFa_6g5FkTosxGlvFm7wJf2IDoyZBm2b3bnSPyTOKKBLLOZ7UCkMK26yeo3wtCCShFYLl-4BVXY8UQ0ZIbgnD6yalaF3OEOCTG5MdM4uvKmuH7zOsdCjjikC6vbOP_WaHGmO0uliygwAg3tq2kKsTtYqnQXrabcKhdWlkTfhYgkhWgeXIKQr7W5HhWbT7CLbQGhZesrNmm6HDuryzsRTTggjPrxevooS4u0hw4JCX_tVJsh2vkfR8RZnscIrMOdOlarnpN6j4eNXLBdHnISUf7N2eg9AJio63K38_6TWwct2rC1Vk-3JzU2Ujy0NaV8iKOShnrKA96iP3AA7EmlBBJ-waGXebBG1AXWtaTIAwM2Lshr5mN1BwFsbfMYTr1Aq1mpbMjFpU3QUtcOl6JWViBre8-fRAl-5fLJ3NvPmHH63QPXsfNZVaSJbT4pYStzqNuuVRZtLwNadkx_LamADlCLHixDNSvs9JN4Lly7jTDCsZPOmkTta8tgf1EU1IqoR9aHcaQX3xzz3mMY24gUnP4WFgxsePto2Ju3NtudLtzDwBM=w728-h677-no


    DOWNLOAD
    MD5: 240ddf273ab211e9fdc65c684b828d75​

    The installer is just a simple WinRAR self extracting archive - there is NOTHING BAD in there i swear! Open it with WinRAR 5 and look inside. You will see if you don't trust me.

    Changelog:


    • 1.4.2
    • Updated partition images (stock and custom recoveries)
      1.4.1
    • Updated partition images (stock and custom recoveries)

    • 1.4.0
    • Updated partition images and flashing for HTC10
    • Updated Splash Screen converter for new res and location
    • Updated raw dump (DD) script for GSM model (No Sprint, No VZW!)
    • Updated ADB and its api with the version from US Unlocked 1.53.617.5 RUU.
    • Removed kernel flashing option and replaced with Insecure ADB patched kernel option.
    Previous versions (HTC One M9/8/7):

    • 1.3.1
    • Updated TWRP to 3.0.2-
      1.3.0
    • Updated stock recovery to 3.35.401.12 and TWRP to 3.0.0-2
      1.2.9
    • Updated ARUWizard to 3.0.4.2015 from HTC’s One M8 DevEd Marshmallow RUU.
    • Swapped out stock recovery for 3.35.401.10 (WWE Marshmallow release).
      1.2.8
    • Splash1 converter works now. Flashing Splash1 now needs a reboot to Bootloader - it's not working in Download Mode! (limited DD support on the M9 and general flashing system changes).
    • Swapped out recoveries for newer versions.
    • Finally added the complete file set from RUU 3.0.1.2015 - the newest M9 RUU. ADB and Fastboot are identical to the previous version from Llabtoofer though.
    • Screenrecord removed - can’t be bothered figuring out why it doesn’t work anymore. Probably SELinux and general Android 5.x security like with the screenshot function. Not really needed either. There are other solutions.
      1.2.7
    • Swapped out recoveries for newer versions.
    • Swapped out ADB and Fastboot for a newer pack (thanks @LlabTooFeR) - now this Tool is fully M9 compatible and even flashes large RUU.zips.
      1.2.6
    • Changed everything to M9 files and methods. I HOPE I didn't oversee anything. Please test carefully!
    • Added stock_recovery_1.32.401.8.img
    • Added TWRP Recovery 2.8.6.0 fixed version from Captain_Throwback SOURCE Post #2 Beta version
    • Added original HIMA Splash1 - S-OFF phones only!
      1.2.5
    • Added TWRP Recovery 2.8.5.2 from Captain_Throwback (All M8 devices)
    • Fixed Recovery Screenshot option (20)
      1.2.4
    • Added newer RUU structure (2.0.16.2014 - from 4.16.1540.8 Dev Edition RUU)
    • Added Stock Recovery 4.16.401.10.img (WWE)
    • Changed the License and SFX texts again (Installer) - never happy with it.
      1.2.3
    • Fixed some serious crap nobody reported. I just found out myself.
    • Added Stock Recovery 4.16.1540.8 (sorry still don't have the WWE recovery, but i guess they are identical)
    • Added TWRP 2.8.4.0 from the M8 tree of Dees_Troy.
      1.2.2
    • Added Stock Recovery 3.28.401.7
      1.2.1
    • Added Microsoft's vcredist_x86_2008_SP1.exe to the installer because the ARUWizard is build on the x86 Visual Studio 2008 runtime. This resolves the "side-by-side configuration" error.
    • Added 3.28.401.6 stock recovery and splash
    • Added newer RUU structure (doesn't do any difference though, just keeping it up to date)
    • Added TWRP 2.8.0.3 (it still has slight issues with MTP which will be fixed soon but for now, this is good enough)
    • Changed a few lines in the script (minor, cosmetical stuff)
    • Updated the INFO PDF (option 24)

    Known Issues:

    • [20] Screenshot (Res: FullHD, PxFormat: RGB8888), check \dump\ Folder - Not adjusted! Won't work!
    • [21] Screenrecord (drops file to /dump folder) STOP recording with CTRL+C - Not adjusted! Won't work!
    31
    Wwe oreo 3.16.401.2 firmware

    Recent Firmware Additions from santod040
    (SneakyGhost is not responsible for the files in this post, nor did he ask that I post them. He did however give me permission to post them here)
    Downloads are currently located directly in this post and are not indexed in the OP.


    WARNINGS:

    1. All new files are untested by me personally but are verified to be working.
      You understand that you are choosing to flash these files at your own risk and nobody is to blame if something should go wrong.
      Please see notes below.

    2. This firmware is for OREO ONLY
      Once you update to Oreo, you will no longer have a baseband if you try to return to Nougat.
      No RUU will fix it.
      Only upon returning to Oreo will you have a baseband again!
      YOU HAVE BEEN WARNED


    NOTES:
    I have provided 3 different zips for the Oreo WWE 3.16.401.2 firmware
    Please pay attention to the details and choose the proper package for your situation.

    CREDITS: All the HTC Legends out there ;)

    Other stuff
    1. This stuff, that stuff, and some more stuff....


    ENJOY! :good:
    31
    Rcent additions: 2.41.401.3

    Take a Look at my Profile Flag, then you will See that my native language is german.

    But What was wrong with my comment?


    Gesendet von iPhone mit Tapatalk

    Man I'll send @j to the 4n your way. He lives just around your corner. He'll teach you XDA nettiquette. He knows Kung Fu.

    Recent Additions

    • PMEUHL_2.41.401.3_WWE_FullStock
    • PMEUHL_2.41.401.3_WWE_TWRP3030_NoWipe

    WARNINGS:

    1. NoWipe tested. Working. See my log.
      Code:
      sending 'zip' (91393 KB)...
      OKAY [  3.967s]
      writing 'zip'...
      (bootloader) HOSD CL#857212
      (bootloader) GPT (gpt_main_32g.img) is up-to-dated. [17408]
      (bootloader) WARN Skip partition_info due to unmatched partition name
      (bootloader) get 32 images from zip(zip_type=3)
      (bootloader) [email protected]
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]%
      (bootloader) [email protected]
      (bootloader) [email protected]
      (bootloader) [email protected]
      (bootloader) [email protected]
      (bootloader) Update zip file OK
      (bootloader) [email protected]
      OKAY [ 19.052s]
      finished. total time: 23.019s
      htc_fastboot finished. total time: 23.136s
      
      C:\Android\com>
    2. FullStock tested. Working. Thank you @ivicask (I nearly shat myself. Too funny. Next time before flashing something, ask what it does :laugh:)
    3. Might cause another reboot after first boot and a "new SIM inserted" message. This is normal!

    NOTES:
    • Dunno... nuffin?

    CREDITS: Dunno? Guess the usual suspect... And sorry mate for not checking in with you first. I made a mistake. Apologies. Will be more observant next time.

    Other stuff
    1. I'll update this tomorrow... **yaaaaawn!**... or not.