Database Users

[Firmware] HTC ONE M7_UL | Firmware 5.11.401.10 | No Red Text | Radio 4T.27.3218.14

This is the latest firmware for HTC ONE M7 extracted from official OTA OTA_M7_UL_K44_SENSE60_MR_HTC_Europe_5.11.401.10-4.19.401.11_release_372404wj19h95c0x6oa19n.zip
You need unlocked bootloader and S-OFF
Removed Red Warning Text and flashed successfully on my phone.
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.
The zip contain:
- firmware 5.11.401.10
- hboot 1.57.0000
- radio 4T.27.3218.14
Flash only if you have firmware v4.xx (download v4 from here) and hboot 1.56.000 not older or you'll get a bricked phone!!!
Download file and copy to your adb folder:
Download links in post 133
DON'T REBOOT THE PHONE UNTIL YOU GET A SUCCESS MESSAGE​
1 - Reboot bootloader
Code:
adb reboot bootloader
2 - Reboot to RUU
Code:
fastboot oem rebootRUU
3 - Flash firmware
Code:
fastboot flash zip firmware_name.zip
Very important!!! One more time (press up arrow on your PC keyboard then press ENTER)
Code:
fastboot flash zip firmware_name.zip
4 - Reboot to bootloader and verify version
Code:
fastboot reboot-bootloader
5 - Reboot to system
Code:
fastboot reboot
6 - Enjoy
WARNING
Flash at your own risk, I can't be held responsible if you didn't follow all steps and brick the phone!!!​
Stock unmodified firmware
MD5 3b7b13b52f75ed516c888b827710f29a
Zip contain stock kernel and recovery!!!
If your phone get bricked because you didn't follow the guide or flashed over a v3.xx firmware, go to HTC Unbricking Project thanx @dexter93

Only for M7_UL:
modelid: PN0710000
cidnum: HTC__001
cidnum: HTC__Y13
cidnum: HTC__E11
cidnum: HTC__102
cidnum: HTC__203
cidnum: HTC__405
cidnum: HTC__304
cidnum: HTC__A07
cidnum: HTC__032
cidnum: HTC__J15
cidnum: HTC__016

TeHashX said:
If case you need original firmware for:
modelid: PN0711000
modelid: PN0713000
modelid: PN0712000
modelid: PN0714000
modelid: PN0710000
modelid: PN071****
cidnum: HTC__***
cidnum: CWS__001
cidnum: H3G__***
cidnum: O2___***
cidnum: ORANG***
cidnum: TELNZ001
cidnum: OPTUS001
cidnum: T-MOB***
cidnum: TELST001
cidnum: VODAP***
cidnum: BM___001
cidnum: BS_US***
cidnum: GLOBA001
cidnum: ROGER001
cidnum: TELUS001
cidnum: TIM__***
The zip contain:
- firmware 5.11.1540.9
- hboot 1.57.0000
- radio 4T.27.3218.14
- the new splash screen "powered by android"
- stock boot
- stock recovery
http://goo.gl/V3yzDF
MD5 ef0cc76134c170e4230804ca1c9edf02
Click to expand...
Click to collapse
Dear friend:
Could you tell me if this firmware supports M7_UL with SuperCID????
This is the ORIGINAL format the "SD"???
Thank you very much and excuse my English

Yes, you can flash with super cid and will not format sdcard but always is better to save contents.

Thank you sir, everything went nice here m7ul supercid.

Is it cool to use this firmware on ViperOne 6.2.1? I know its not using the latest base. Shouldn't hurt though, right?

So I'm on AT&T with s-off and super CID. Can I flash this?

DrRyder said:
Is it cool to use this firmware on ViperOne 6.2.1? I know its not using the latest base. Shouldn't hurt though, right?
Click to expand...
Click to collapse
Yes
aceroller said:
So I'm on AT&T with s-off and super CID. Can I flash this?
Click to expand...
Click to collapse

TeHashX said:
Yes
Click to expand...
Click to collapse
Awesome. Thanks. Flashing here in a minute.

THX for firmware :highfive:
all set all done with no problem
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1540.9
(bootloader) version-misc: PVT SHIP S-OFF

I I flash this firmware and after:
c:\HTC>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.047s
c:\HTC>fastboot flash zip firmware_5.11.1540.9_noredwarn.
target reported max download size of 1514139648 bytes
sending 'zip' (24706 KB)...
OKAY [ 1.981s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image a
finished. total time: 3.604s
c:\HTC>fastboot flash zip firmware_5.11.1540.9_noredwarn.
target reported max download size of 1514139648 bytes
sending 'zip' (24706 KB)...
OKAY [ 2.044s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-3,0
(bootloader) [RUU]UZ,sbl1-3,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1-3,0
(bootloader) [RUU]WP,sbl1-3,100
(bootloader) ...... Successful
(bootloader) start image[sp1] unzipping & flushing...
(bootloader) [RUU]UZ,sp1,0
(bootloader) [RUU]UZ,sp1,26
(bootloader) [RUU]UZ,sp1,50
(bootloader) [RUU]UZ,sp1,75
(bootloader) [RUU]UZ,sp1,100
(bootloader) [RUU]WP,sp1,0
(bootloader) [RUU]WP,sp1,100
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,5
(bootloader) [RUU]UZ,radio,11
(bootloader) [RUU]UZ,radio,17
(bootloader) [RUU]UZ,radio,23
(bootloader) [RUU]UZ,radio,28
(bootloader) [RUU]UZ,radio,34
(bootloader) [RUU]UZ,radio,40
(bootloader) [RUU]UZ,radio,46
(bootloader) [RUU]UZ,radio,52
(bootloader) [RUU]UZ,radio,57
(bootloader) [RUU]UZ,radio,63
(bootloader) [RUU]UZ,radio,69
(bootloader) [RUU]UZ,radio,75
(bootloader) [RUU]UZ,radio,80
(bootloader) [RUU]UZ,radio,86
(bootloader) [RUU]UZ,radio,92
(bootloader) [RUU]UZ,radio,98
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,23
(bootloader) [RUU]WP,radio,46
(bootloader) [RUU]WP,radio,69
(bootloader) [RUU]WP,radio,92
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,42949671
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,42949671
(bootloader) ...... Successful
OKAY [ 13.915s]
finished. total time: 15.959s
c:\HTC>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
After that my phone won't boot up, black screen and nothing more :crying: no red light after plug charger...

working fine here
many thanks :good:

Just finished flashing mine. I think now it's as good as brick. It won't come up after step 4. When connecting the charger - no light. Here is all the output I got:
Code:
C:\adb>adb reboot-bootloader
C:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.106s]
finished. total time: 0.110s
C:\adb>fastboot flash zip firmware_5.11.1540.9_noredwarn.zip
sending 'zip' (24706 KB)...
OKAY [ 2.082s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 4.335s
C:\adb>fastboot flash zip firmware_5.11.1540.9_noredwarn.zip
sending 'zip' (24706 KB)...
OKAY [ 2.078s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-3,0
(bootloader) [RUU]UZ,sbl1-3,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1-3,0
(bootloader) [RUU]WP,sbl1-3,100
(bootloader) ...... Successful
(bootloader) start image[sp1] unzipping & flushing...
(bootloader) [RUU]UZ,sp1,0
(bootloader) [RUU]UZ,sp1,26
(bootloader) [RUU]UZ,sp1,50
(bootloader) [RUU]UZ,sp1,75
(bootloader) [RUU]UZ,sp1,100
(bootloader) [RUU]WP,sp1,0
(bootloader) [RUU]WP,sp1,100
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,5
(bootloader) [RUU]UZ,radio,11
(bootloader) [RUU]UZ,radio,17
(bootloader) [RUU]UZ,radio,23
(bootloader) [RUU]UZ,radio,28
(bootloader) [RUU]UZ,radio,34
(bootloader) [RUU]UZ,radio,40
(bootloader) [RUU]UZ,radio,46
(bootloader) [RUU]UZ,radio,52
(bootloader) [RUU]UZ,radio,57
(bootloader) [RUU]UZ,radio,63
(bootloader) [RUU]UZ,radio,69
(bootloader) [RUU]UZ,radio,75
(bootloader) [RUU]UZ,radio,80
(bootloader) [RUU]UZ,radio,86
(bootloader) [RUU]UZ,radio,92
(bootloader) [RUU]UZ,radio,98
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,23
(bootloader) [RUU]WP,radio,46
(bootloader) [RUU]WP,radio,69
(bootloader) [RUU]WP,radio,92
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,42949671
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,42949671
(bootloader) ...... Successful
OKAY [ 15.458s]
finished. total time: 17.544s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.106s]
finished. total time: 0.109s
C:\adb>
Any ideas? Of course I had S-OFF...

simaka said:
Just finished flashing mine. I think now it's as good as brick. It won't come up after step 4. When connecting the charger - no light. Here is all the output I got:
Code:
C:\adb>adb reboot-bootloader
C:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.106s]
finished. total time: 0.110s
C:\adb>fastboot flash zip firmware_5.11.1540.9_noredwarn.zip
sending 'zip' (24706 KB)...
OKAY [ 2.082s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 4.335s
C:\adb>fastboot flash zip firmware_5.11.1540.9_noredwarn.zip
sending 'zip' (24706 KB)...
OKAY [ 2.078s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-3,0
(bootloader) [RUU]UZ,sbl1-3,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1-3,0
(bootloader) [RUU]WP,sbl1-3,100
(bootloader) ...... Successful
(bootloader) start image[sp1] unzipping & flushing...
(bootloader) [RUU]UZ,sp1,0
(bootloader) [RUU]UZ,sp1,26
(bootloader) [RUU]UZ,sp1,50
(bootloader) [RUU]UZ,sp1,75
(bootloader) [RUU]UZ,sp1,100
(bootloader) [RUU]WP,sp1,0
(bootloader) [RUU]WP,sp1,100
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,5
(bootloader) [RUU]UZ,radio,11
(bootloader) [RUU]UZ,radio,17
(bootloader) [RUU]UZ,radio,23
(bootloader) [RUU]UZ,radio,28
(bootloader) [RUU]UZ,radio,34
(bootloader) [RUU]UZ,radio,40
(bootloader) [RUU]UZ,radio,46
(bootloader) [RUU]UZ,radio,52
(bootloader) [RUU]UZ,radio,57
(bootloader) [RUU]UZ,radio,63
(bootloader) [RUU]UZ,radio,69
(bootloader) [RUU]UZ,radio,75
(bootloader) [RUU]UZ,radio,80
(bootloader) [RUU]UZ,radio,86
(bootloader) [RUU]UZ,radio,92
(bootloader) [RUU]UZ,radio,98
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,23
(bootloader) [RUU]WP,radio,46
(bootloader) [RUU]WP,radio,69
(bootloader) [RUU]WP,radio,92
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,42949671
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,42949671
(bootloader) ...... Successful
OKAY [ 15.458s]
finished. total time: 17.544s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.106s]
finished. total time: 0.109s
C:\adb>
Any ideas? Of course I had S-OFF...
Click to expand...
Click to collapse
I have the same i also had S-off and unlocked bootloader.
Now my phone is recognized as QHSUSB_DLOAD on Win7

alien44 said:
I have the same i also had S-off and unlocked bootloader.
Now my phone is recognized as QHSUSB_DLOAD on Win7
Click to expand...
Click to collapse
I think most likely both of us didn't have superCID. I am not sure whether I set it or not after set-off (it was a while ago)... No way to check it now ....
OP, why didn't you specificially input in your thread that superCID is required for this update? It makes sense, of course, but you should have put this there...

My phone is also bricked now damn..

Super CID is definitely NOT required, I successfully flashed this firmware and no super CID

Flashed on International M7, didn't brick.

simaka said:
I think most likely both of us didn't have superCID. I am not sure whether I set it or not after set-off (it was a while ago)... No way to check it now ....
OP, why didn't you specificially input in your thread that superCID is required for this update? It makes sense, of course, but you should have put this there...
Click to expand...
Click to collapse
I had super CID, S-OFF, Unlocker bootloader. What now?

Worked
Worked fine here, I did have Super-CID though....

HTC m9+ boot loop white screen (after a bad attempt to obtain root privileges)

Then I got a ring to restart with a white screen HTC
######
I had a file from an older version of Android, and old bootloader OS 1.90.401.3.
I was stupid and took advantage of it from TWRP im restored my old arhive files
Now im have:
HTC One M9 Plus
With Android 5.02
Sense 6 .....
--
LK-1.01.0000
!OS-2.27.401.1
__________
And now I can not return to STOCK 1.90.401.3 (version bootloader is now higher)
attempts to flash error:
--
fastboot flash zip 0PK7IMG.zip
sending 'zip'... (79262 KB) OKAY
sending time = 3.912 secs
writing 'zip'... (bootloader) HOSD CL#809431
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
FAIL19 RU_MAIN_VER_FAIL os-version in android-info missing or i
FAILED (remote: 19 RU_MAIN_VER_FAIL os-version in android-info missing or i)
Execution time is 7(s)
--
And I can not install an update to the sixth version
im stay put ...
I do not know what to do now
Help me please if you know how to downgrade the bootloader or another way.
LAST:
fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_hiau_ml_tuhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 2.27.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000
(bootloader) mid: 0PK711000
(bootloader) cid: HTC__A07

It turns out not working GSM Writes
........
RADIO-UNKNOWN
OpenDSP-UNKNOWN
cowax said:
Then I got a ring to restart with a white screen HTC
######
Click to expand...
Click to collapse

I have the same situation. Did you solve it?

Bootloop after trying to root M9+

Hello,
my M9+ is stuck in a bootloop after i followed this guide to root the device.
I succesfully flashed the "recovery-twrp-2.8.7.0-htc_m9pw-english.img" . After i installed the "BETA-SuperSU-v2.48.zip" from recovery, my phone is stuck in bootloop. Phone model is htc_hiau_ml_tuhl XC S-ON, version 2.30.707.1. Any ideas?

try the new,stable version of supersu.

yvtc75 said:
try the new,stable version of supersu.
Click to expand...
Click to collapse
Thanks for the reply. I managed to make my htc one m9+ working again. Installing the newest SuperSU (2.82) in via TWRP seems to work without errors, but when i power on and check root, it says there is no root and there is nor SuperSU App.
My recovery: recovery-twrp-2.8.7.0-htc_m9pw-english
My software: 2.27.401.1
S-OFF Bootloader unlocked.
(bootloader) kernel: lk
(bootloader) product: htc_hiau_ml_tuhl
(bootloader) version: 1.0
(bootloader) imei: 3574***********
(bootloader) version-main: 2.27.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000
(bootloader) mid: 0PK711000
(bootloader) cid: 11111111
Click to expand...
Click to collapse
Any ideas?

can u mail me recovery. i cant download in site .. plzz . ima stuck at rooting my phone thankyou.

Jaysompura said:
can u mail me recovery. i cant download in site .. plzz . ima stuck at rooting my phone thankyou.
Click to expand...
Click to collapse
Here you go.

DarthLuda said:
Hello,
my M9+ is stuck in a bootloop after i followed this guide to root the device.
I succesfully flashed the "recovery-twrp-2.8.7.0-htc_m9pw-english.img" . After i installed the "BETA-SuperSU-v2.48.zip" from recovery, my phone is stuck in bootloop. Phone model is htc_hiau_ml_tuhl XC S-ON, version 2.30.707.1. Any ideas?
Click to expand...
Click to collapse
DarthLuda said:
Thanks for the reply. I managed to make my htc one m9+ working again. Installing the newest SuperSU (2.82) in via TWRP seems to work without errors, but when i power on and check root, it says there is no root and there is nor SuperSU App.
My recovery: recovery-twrp-2.8.7.0-htc_m9pw-english
My software: 2.27.401.1
S-OFF Bootloader unlocked.
(bootloader) kernel: lk
(bootloader) product: htc_hiau_ml_tuhl
(bootloader) version: 1.0
(bootloader) imei: 3574***********
(bootloader) version-main: 2.27.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000
(bootloader) mid: 0PK711000
(bootloader) cid: 11111111
Any ideas?
Click to expand...
Click to collapse
Since you have s-offed,I would recommend you settle the software and firmware on the same version.
About root issue, flash back stock boot image and re-root it.

yvtc75 said:
Since you have s-offed,I would recommend you settle the software and firmware on the same version.
About root issue, flash back stock boot image and re-root it.
Click to expand...
Click to collapse
Thanks for the hint, didn't think of that. Do you know where i can get a RUU or backup for the 2.30.707.1 version?

htc_hiau_ml_tuhl XC. What varian is it? Asia WWE? Asia TW? Asia HK? Europe? Please answer. I might find proper RUU for you in case you want to back to official ROM

antonmandara said:
htc_hiau_ml_tuhl XC. What varian is it? Asia WWE? Asia TW? Asia HK? Europe? Please answer. I might find proper RUU for you in case you want to back to official ROM
Click to expand...
Click to collapse
It is Asia WWE.

DarthLuda said:
It is Asia WWE.
Click to expand...
Click to collapse
.........................................
-------------------

Many thanks for providing the download link. However, putting it on a micro sd (fat32) and renaming it to 0PK7IMG.zip didn't work. it just skips installation with "EXIT".
Which recovery do i need for flashing this?
Do i need S-OFF to flash?
Is relocking the bootloader required?
I am currently using CleanSlate Asia ver. with Android 5 with root since it is the only rom that can be flashed over TWRP.

M9+ pw ruu
Hi antonmandara. do you have european ruu for htc m9+ pw?
marashmallow ruu?

..

__

Crazypit23 said:
Hi antonmandara. do you have european ruu for htc m9+ pw?
marashmallow ruu?
Click to expand...
Click to collapse
Is this what you need?
https://drive.google.com/file/d/0B6l0uYJfNaAlOXRwbUR3LUE3dFU/view?usp=sharing
(0PK7IMG_HIAU_ML_TUHL_M60_SENSE70_MR_HTC_Europe_2.30.401.1_Radio_1.1550V70.2501.0304_HT[W.T]_release_490382_combined_signed)
The download link will active for one week only. Goodluck.

DarthLuda said:
Many thanks for providing the download link. However, putting it on a micro sd (fat32) and renaming it to 0PK7IMG.zip didn't work. it just skips installation with "EXIT".
Which recovery do i need for flashing this?
Do i need S-OFF to flash?
Is relocking the bootloader required?
I am currently using CleanSlate Asia ver. with Android 5 with root since it is the only rom that can be flashed over TWRP.
Click to expand...
Click to collapse
Yes, I think so. You need to relock bootloader. S-On is just fine, just have to relock.

The zip file of the rom has to be by 3 orders in fastboot:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Now if you can do the zip with that order i'll be happy.
if you cant then let me do it and explain to me how to convert to
three images of boot.img recovery.img and system.img. it has to be this way inside the zip file.
many thanks. :good:

I have same problem. Sucessfuly instal TWRP, reboot ok, instal BETA-SuperSU-v2.48 and bootloop ))
(bootloader) kernel: lk
(bootloader) product: htc_hiau_ml_tuhl
(bootloader) version: 1.0
(bootloader) imei: xxxxxxxxxxxx
(bootloader) version-main: 2.30.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000
(bootloader) mid: 0PK711000
(bootloader) cid: HTC__A07
How to extract system.img ?
zip_1.zip and so on. Archivers issue an error
help please
---------- Post added at 06:10 AM ---------- Previous post was at 05:38 AM ----------
zip is downloaded above 0PK7IMG_HIAU_ML_TUHL_M60_SENSE70_MR_HTC_Europe_2.30.401.1_Radio_1.1550V70.2501.0304_HT[W.T]_release_490382_combined_signed.zip and renamed to 0PK711000.zip
c:\adb>fastboot flash zip 0PK711000.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2488462141 is not a multiple of
the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2488462141 is not a multiple of
the block size 4096
error: write_sparse_skip_chunk: don't care size 2488462141 is not a multiple of
the block size 4096
OKAY [ 1.014s]
writing 'zip' 1/1...
(bootloader) HOSD CL#821792
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_i
(bootloader) sSvfy
FAILED (remote: 99 RU_UNKNOWN_FAIL terrible mishap )
finished. total time: 13.135s

sm_vl said:
I have same problem. Sucessfuly instal TWRP, reboot ok, instal BETA-SuperSU-v2.48 and bootloop ))
(bootloader) kernel: lk
(bootloader) product: htc_hiau_ml_tuhl
(bootloader) version: 1.0
(bootloader) imei: xxxxxxxxxxxx
(bootloader) version-main: 2.30.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000
(bootloader) mid: 0PK711000
(bootloader) cid: HTC__A07
How to extract system.img ?
zip_1.zip and so on. Archivers issue an error
help please
---------- Post added at 06:10 AM ---------- Previous post was at 05:38 AM ----------
zip is downloaded above 0PK7IMG_HIAU_ML_TUHL_M60_SENSE70_MR_HTC_Europe_2.30.401.1_Radio_1.1550V70.2501.0304_HT[W.T]_release_490382_combined_signed.zip and renamed to 0PK711000.zip
c:\adb>fastboot flash zip 0PK711000.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2488462141 is not a multiple of
the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2488462141 is not a multiple of
the block size 4096
error: write_sparse_skip_chunk: don't care size 2488462141 is not a multiple of
the block size 4096
OKAY [ 1.014s]
writing 'zip' 1/1...
(bootloader) HOSD CL#821792
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_i
(bootloader) sSvfy
FAILED (remote: 99 RU_UNKNOWN_FAIL terrible mishap )
finished. total time: 13.135s
Click to expand...
Click to collapse
Was having the same issue with fastboot methode. Then I used SD card method, after having reinstall stock recovery and relock the bootloader (S-On). Now I live with stock ROM.

Bootloop Sollution : from ext SD via TWRP I install SU v 2.78 (befor was installed v2.48 = bootloop)
After that the phone start normally ))
Through the Play Market updated the #SU to 2.82, everything is fine

slot-count not found, slot-suffixes not found,bootloaer working fine

Hello,
I've recently tried to flash stock recovery to be able to receive update . I had TWRP installed already . But whenever I type fastboot command , I get error like slot-count not found .
And that's not the case . I've tried with flashing bootloader and gpt.bin as well and get the same error ! My bootloader is working fine! Also whenever I try these steps, I end up losing my WiFi/hotspot connectivity !
Here take a look . I get these errror in ADB :
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
C:\Windows\system32\cmd.exe O
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery "C:\User
s\MAYUR Desktop\New folder recovery.img"
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
bootloader) slot-suffixes: not found
(bootloader) has-slot recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.529s]
writing 'recovery'..
<bootloader) Image signed with key bad key
OKAY [ 9.668s]
finished. total time: 1.204s
rs\MAYUR\Desktop\New folder\gpt.bin"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition "C:\Use
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
<bootloader) slot-suffixes: not found
(bootloader) has-slot: partition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.008s]
writing partition'.
(bootloader) Flashing prinary GPT image..
(bootloader) Flashing backup GPT image...
OKAY [ 9.093s]
finished. total time: 0.106s
C:\Program Files (x86)\Minimal ADB and Fastboot >fastboot flash bootloader "C:\US
ers\MAYUR Desktop\New folder\bootloader.img'
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
bootloader) slot-suffixes: not found
(bootloader) has-slot: bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.124s]
writing 'bootloader'.
(bootloader) validating: bootloader.default.xml
(bootloader will pass: flash:aboot
<bootloader) will pass: flash:tz
(bootloader) will pass: flash: rpm
(bootloader) will pass: flash: hyp
(bootloader will pass: flash: keymaster
(bootloader) will pass: flash:cmnlib
(bootloader will pass: flash sbli
(bootloader) committing: bootloader.default.xml
bootloader> flashing 'emmc_apps boot.mbn' to 'abooty
(bootloader) flashing 'tz.mbn' to 'tz'
<bootloader) flashing rpm.mbn' to rpm'
(bootloader) flashing 'hyp.mbn' to 'hyp'
(bootloader flashing 'keymaster.mbn' to 'keymaster'
bootloader) flashing 'canlib.mbn' to 'canlib'
OKAY [ 0.608s]
(bootloader) flashing 'sbll.mbn' to sbli'
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
(Getvar all) returned this : ?
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
C:\Windows\system32\cmd.exe
C:\Users\MAYUR\Desktop\New folder>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
<bootloader) version: 0.5
(bootloader) version-bootloader: moto-nsm8952-B1.07
bootloader) product: athene 16mp
<bootloader board: athene_16mp
<bootloader) secure yes
<bootloader) hwrey: P2A
<bootloader) radio: 4
<bootloader) storage-type ennc
<bootloader) emnc 16GB SAMSUNG QE13MB RU-08 PU-7 FU-OOOOOOOOOOOOOOOD
<bootloader) ran: 2GB SAMSUNG LP3 DIE=8Gb M501 M6-05 M2=00 M8 -17
(bootloader) cpu MSM8952
(bootloader) serialno: *protected*
<bootloader) cid: Ox0032
<bootloader) channelid: Oxco
(bootloader) uid: 2E2FAAOOOOOOOOOOOOOOOOOOO000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvo id: yes
(bootloader) reason: Volume down key pressed
bootloader> max-download-size: 536870912,
<bootloader) meid:
(bootloader) imei: *protected*
<bootloader) date: 05-31-2016
<bootloader) sku: XT1643
<bootloader) battid: SNN5966A
bootloader> max-sparse-size: 268435456
<bootloader) iccid:
<bootloader) cust_md5:
(bootloader> current-time "'Sat Apr 30 0:19:14 UTC 2016"
(bootloader) ro.build.fingerprint [0]: motorola/athene/athene:2.0/NPJS25.
bootloader) ro.build.fingerprint(1): 93-14-18/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.236.3.athene.reta
bootloader) ro.build.version.full[1]: il.en.US
bootloader) version-baseband: M8952_70030.25.03.62.02R DFLT_FSG
(bootloader) kernel.version [1]: 2526f <hudsoncneilclbld72) (gcc version
<bootloader) ro.build.version.qcon: LA.BR.1.3.6-01210-8926.0
bootloader) kernel.version [0]: Linux version 3.10.84-ge03508d-00131-944,
bootloader) kernel.version [2]: 4.8 (GCC) > 111 SMP PREEMPT Wed Mar 28 06
(bootloader) kernel.version [3]: :58:16 CDT 2018
(bootloader) tz.git: git-69dd24b-dirty
(bootloader) rpm.git: [email protected]
<bootloader) sbl1.git: git-MBM-NG-UB1.07-6-952d1343
(bootloader) hyp.git: git-69dd24b-dirty
(bootloader) cmnlib.git:git-69dd24b-dirty
(bootloader) aboot.git: git-MBM-NG-UB1.07-0-9f9b89ba
bootloader> keymaster-git: git-69dd24b-dirty
(bootloader) ro.carrier: retin
(bootloader) frp-state: no protection (0)
<bootloader> qe: qe 0/1
all: listed above
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
I've read all the related forum but none of them is similar to mine ! They say we've have to blank flash the bootloader . But mines working fine . Do I really need to blank flash or something else would work fine ? If i really need to blank flash , then pls guide me !
Thank you very much in advance !
Have a great day ?
P.S. = sorry if the related thread already exist !

As far as I know, those slot error messages are normal, and are more informational. The message relate to the flashing slots found on A/B partitioned devices (e.g Google pixels and newer device). We don't have that (G4 plus only had the one set of partitions) and so you expect to see that message on our device. For a newer device, fastboot may try to determine which update slot (either A or B) to flash to.
Flashing recovery or boot (kernel, not bootloader) will usually show image signed with bad key if your bootloader is unlocked. That is normal under that condition.
I'm not entirely sure where the idea to blank flash came from - that method is really only to be used if you've corrupted your bootloader and you cannot boot into the bootloader normally. It's a method of last resort and as you've got a working bootloader and GPT, you really have no need of it.
Your getvar looks mostly okay too, the information you have there matches what we expect from the April 2018 firmware. The odd thing is that your baseband is reporting DFLT_FSG rather than the expected ATHENE_INDIA suffix, which may explain the loss of radio. Can I ask if you flashed any other stock firmware before hand? You may wish to have a look through this thread for more information https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-pluss-model-changed-to-g4-lost-t3496912

Sir I've flashed RR, INVICTA,and many other ROMs but... Didn't face this issue before ... I've recently flashed stock firmware provided by @rajatgupta1998 in this thread https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138/amp/ .. and ended up here !! The thread you provided as reference is an older discussion where he downgraded his bootloader by flashing ROM from different Android version ... But I've done nothing like that ! Please help me how to het the radio working ! Thanks in advance sir !

echo92 said:
As far as I know, those slot error messages are normal, and are more informational. The message relate to the flashing slots found on A/B partitioned devices (e.g Google pixels and newer device). We don't have that (G4 plus only had the one set of partitions) and so you expect to see that message on our device. For a newer device, fastboot may try to determine which update slot (either A or B) to flash to.
Flashing recovery or boot (kernel, not bootloader) will usually show image signed with bad key if your bootloader is unlocked. That is normal under that condition.
I'm not entirely sure where the idea to blank flash came from - that method is really only to be used if you've corrupted your bootloader and you cannot boot into the bootloader normally. It's a method of last resort and as you've got a working bootloader and GPT, you really have no need of it.
Your getvar looks mostly okay too, the information you have there matches what we expect from the April 2018 firmware. The odd thing is that your baseband is reporting DFLT_FSG rather than the expected ATHENE_INDIA suffix, which may explain the loss of radio. Can I ask if you flashed any other stock firmware before hand? You may wish to have a look through this thread for more information https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-pluss-model-changed-to-g4-lost-t3496912
Click to expand...
Click to collapse
Hello ! I've tried to flash dsp,bootloader,and modem
In adb in twrp .. but my device doesn't detect when I type adb devices in TWRP ! Elsewhere it detects my device ... Be it when I do this while my device is on or in fasboot mode.... could you pls help me with that !!??
Without the radio it's nothing more than a iPod ... Sorry if didn't follow the steps mentioned correctly... pls help me with that ... I'd be very much thankful !
Waiting for your reply ??

Vs1607 said:
Hello ! I've tried to flash dsp,bootloader,and modem
In adb in twrp .. but my device doesn't detect when I type adb devices in TWRP ! Elsewhere it detects my device ... Be it when I do this while my device is on or in fasboot mode.... could you pls help me with that !!??
Without the radio it's nothing more than a iPod ... Sorry if didn't follow the steps mentioned correctly... pls help me with that ... I'd be very much thankful !
Waiting for your reply
Click to expand...
Click to collapse
Does your computer detect your device when you connect via USB whilst booted in TWRP (does your device appear in Device Manager if you're using Windows?) and what version of TWRP are you using? What version of fastboot/ADB do you have installed on your computer?
I'm not that familiar with helping to losing baseband - that's why I referred you to that thread - though it's old and perhaps not exactly what happened to your device, there may be some useful information as to fixing your device.

Another noobie needs assistance - HTC upgrade gone wrong.

Hello, and thank you in advance for your assistance.
I bought a "new" Verizon HTC 10 off Ebay. It seemed to be a stock phone, with version 2.4xxxx; I am not exactly sure which version. I have bought my 2 daughters HTC 10's as well. There's are fine. They both have version 3.xxxx. I thought to upgrade my phone to somewhere around their version, because my phone seemed to have connectivity issues when both Wi-Fi and Data were enabled at the same time. However, the OS said they were no new updates for the phone. I checked the HTC site and they had the 2.51.617.32 RUU available. It said it would wipe all data, but that was no consequence to me because I didn't want to save anything. I didn't make a recovery backup (Stupid)! I downloaded the RUU, started it, and it errored out at about 90%; Erro 155: Unknown Error - The ROM update utility cannot update your Android phone. Please get the correct ROM update utility and try again. After that, on reboot the phone constantly reboots. I stop it by booting into download mode. Then choosing "power off". Since then, I have tried the RUU several more times, I have downloaded it again just to make sure I had an uncorrupted exe, I put in on my SD card and tried to update it that way: E: Signature Verification failed - error 21. I have tried the 3.6xxxx update from one of the people on this site. I get all the same messages. Also, I have used htc_fastboot to see if that would work. It errors out at 90% as well at tp_syn3708.img error. I have taken it to a repair shop, but they weren't able to fix it. I have chatted back and forth with HTC support. They had me change the CID to BS_US001. That did nothing. I read more on this forum and changed the CID to VZ_001. That didn't change anything. At this point, what are my options? I'm using an older backup phone, but I hope I can "reboot" this one. Thanks again.

Byrdman2b said:
Hello, and thank you in advance for your assistance.
I bought a "new" Verizon HTC 10 off Ebay. It seemed to be a stock phone, with version 2.4xxxx; I am not exactly sure which version. I have bought my 2 daughters HTC 10's as well. There's are fine. They both have version 3.xxxx. I thought to upgrade my phone to somewhere around their version, because my phone seemed to have connectivity issues when both Wi-Fi and Data were enabled at the same time. However, the OS said they were no new updates for the phone. I checked the HTC site and they had the 2.51.617.32 RUU available. It said it would wipe all data, but that was no consequence to me because I didn't want to save anything. I didn't make a recovery backup (Stupid)! I downloaded the RUU, started it, and it errored out at about 90%; Erro 155: Unknown Error - The ROM update utility cannot update your Android phone. Please get the correct ROM update utility and try again. After that, on reboot the phone constantly reboots. I stop it by booting into download mode. Then choosing "power off". Since then, I have tried the RUU several more times, I have downloaded it again just to make sure I had an uncorrupted exe, I put in on my SD card and tried to update it that way: E: Signature Verification failed - error 21. I have tried the 3.6xxxx update from one of the people on this site. I get all the same messages. Also, I have used htc_fastboot to see if that would work. It errors out at 90% as well at tp_syn3708.img error. I have taken it to a repair shop, but they weren't able to fix it. I have chatted back and forth with HTC support. They had me change the CID to BS_US001. That did nothing. I read more on this forum and changed the CID to VZ_001. That didn't change anything. At this point, what are my options? I'm using an older backup phone, but I hope I can "reboot" this one. Thanks again.
Click to expand...
Click to collapse
VZ__001
That's two underscores, not one.
That should work using the Verizon Oreo RUU, if it's indeed a Verizon model and the MID matches.
Although I feel you've already done too many changes for this information to be accurate, paste the output of:
fastboot getvar all
Remove the serial and imei for security purposes.
Sent from my Pixel 3 XL using Tapatalk

santod040 said:
VZ__001
That's two underscores, not one.
That should work using the Verizon Oreo RUU, if it's indeed a Verizon model and the MID matches.
Although I feel you've already done too many changes for this information to be accurate, paste the output of:
fastboot getvar all
Remove the serial and imei for security purposes.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
(bootloader) kernel: lk
(bootloader) product: htc_pmewl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno:
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei:
(bootloader) version-main: 3.18.605.13
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS650000
(bootloader) cid: VZW__001
all:
finished. total time: 0.004s
htc_fastboot finished. total time: 1.244s

Byrdman2b said:
(bootloader) kernel: lk
(bootloader) product: htc_pmewl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno:
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei:
(bootloader) version-main: 3.18.605.13
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS650000
(bootloader) cid: VZW__001
all:
finished. total time: 0.004s
htc_fastboot finished. total time: 1.244s
Click to expand...
Click to collapse
You need the VZW Oreo RUU.
https://forum.xda-developers.com/showthread.php?p=70340077
Sent from my Pixel 3 XL using Tapatalk

santod040 said:
You need the VZW Oreo RUU.
https://forum.xda-developers.com/showthread.php?p=70340077
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Yes - I have already tried this one. Using htc_fastboot, this is the one that errors out on tp_syn3708. Should I download the file again and repeat the procedure?

Byrdman2b said:
Yes - I have already tried this one. Using htc_fastboot, this is the one that errors out on tp_syn3708. Should I download the file again and repeat the procedure?
Click to expand...
Click to collapse
Try using SD card method and verify the md5 sum of the download and/or redownload if need be.
Sent from my Pixel 3 XL using Tapatalk

​
santod040 said:
Try using SD card method and verify the md5 sum of the download and/or redownload if need be.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
What is the command to verify the md5 sum of the download?

Byrdman2b said:
​
What is the command to verify the md5 sum of the download?
Click to expand...
Click to collapse
On Linux:
md5sum filename.zip
Replace filename with actual name of file.
On Windows:
CertUtil -hashfile <path to file> MD5
Sent from my Pixel 3 XL using Tapatalk

santod040 said:
On Linux:
md5sum filename.zip
Replace filename with actual name of file.
On Windows:
CertUtil -hashfile <path to file> MD5
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Here is what I get after downloading (again), MD5sum checking, and sending the file through fastboot:
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 3.18.605.13
found large-zip header, file count: 29
processing file 1/29...
sending 'zip' (113449 KB)...
OKAY [ 5.377s]
writing 'zip'...
(bootloader) HOSD CL#1016573
(bootloader) GPT (gpt_main_32g.img) is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) WARN Skip partition_info due to unmatched partition name
(bootloader) WARN Skip lockbooter.img due to unmatched partition name
(bootloader) WARN Skip backup_android-info.txt due to unmatched partitio
(bootloader) n 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) boot_sign[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: 7.979s
preupdate done, rebooting...
resending command...
< waiting for device >
sending 'zip' (113449 KB)...
OKAY [ 5.427s]
writing 'zip'...
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_s
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP ERROR CODE, 22
FAILED (remote: 22 RU_HEADER_ERROR )
finished. total time: 7.544s
htc_fastboot finished. total time: 32.112s
I'll get in on the SD card and try it as well.

Byrdman2b said:
Here is what I get after downloading (again), MD5sum checking, and sending the file through fastboot:
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 3.18.605.13
found large-zip header, file count: 29
processing file 1/29...
sending 'zip' (113449 KB)...
OKAY [ 5.377s]
writing 'zip'...
(bootloader) HOSD CL#1016573
(bootloader) GPT (gpt_main_32g.img) is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) WARN Skip partition_info due to unmatched partition name
(bootloader) WARN Skip lockbooter.img due to unmatched partition name
(bootloader) WARN Skip backup_android-info.txt due to unmatched partitio
(bootloader) n 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]
FAILED (remote: 90 hboot pre-update! please flush image again immediately )
finished. total time: 7.979s
preupdate done, rebooting...
resending command...
< waiting for device >
sending 'zip' (113449 KB)...
OKAY [ 5.427s]
writing 'zip'...
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_s
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP ERROR CODE, 22
FAILED (remote: 22 RU_HEADER_ERROR )
finished. total time: 7.544s
htc_fastboot finished. total time: 32.112s
I'll get in on the SD card and try it as well.
Click to expand...
Click to collapse
Update-
When trying to update from SD card, I get the message:
E: footer is wrong
Update Package verification took 0.2 s (result 1)
E: Signature verification failed
E: Error 21
Installation aborted

Byrdman2b said:
Update-
When trying to update from SD card, I get the message:
E: footer is wrong
Update Package verification took 0.2 s (result 1)
E: Signature verification failed
E: Error 21
Installation aborted
Click to expand...
Click to collapse
You're using Download mode to install via SD card method, as stated in my stock thread, where firmware is posted, right?
Sounds like you're trying to flash via stock recovery, which is not the correct procedure...
Sent from my Pixel 3 XL using Tapatalk

I used Recovery mode (not download mode) to apply the update from SD card. Is this the correct procedure?

Byrdman2b said:
I used Recovery mode (not download mode) to apply the update from SD card. Is this the correct procedure?
Click to expand...
Click to collapse
No, check my post for flashing firmware via SD card method in the same thread, second post.
Same process applies to flashing an RUU.
Sent from my Pixel 3 XL using Tapatalk

santod040 said:
No, check my post for flashing firmware via SD card method in the same thread, second post.
Same process applies to flashing an RUU.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Success!!!!!!! Success!!!!! I flashed it from SD, from bootloaded mode, and it worked properly. My phone is up and running now. Wow, I thought I would have to purchase another one. I am very grateful to you Sir. You are the 3rd person that I have worked with in order to get this phone working. I even took it to a shop where they repair phones, but they still couldn't get it working. Thank you for your help.

Byrdman2b said:
Success!!!!!!! Success!!!!! I flashed it from SD, from bootloaded mode, and it worked properly. My phone is up and running now. Wow, I thought I would have to purchase another one. I am very grateful to you Sir. You are the 3rd person that I have worked with in order to get this phone working. I even took it to a shop where they repair phones, but they still couldn't get it working. Thank you for your help.
Click to expand...
Click to collapse
No problem.
I'm glad to hear it worked out for you. [emoji106]
Sent from my Pixel 3 XL using Tapatalk

I know that it might be wrong to post here but, also i got one from eBay too. Phone was on Nougat and working fine, updated to Oreo when i turned on the Wifi on home. Oreo update begins and was working fine, except that on the lockscreen it was showing two cities instead of one... I tried everything to set it one one city but i couldn't figure what was wrong. So i decided to wipe it to factory reset. And then the problems begins... I notice that the battery drains so fast that i don't know why or what is causing that stuff... I charge it by quick charge and low charge and it's the same battery life just go around 11 or less hours. And it is always warn doing nothing, just lying around there. I had wiped and even installed the RUU from an external SD and the issue continues...
Also i had to rename the zip because i had the same error 21 and i changed the name and worked