Related
I flashed a custom rom, and I have TWRP for the recovery mode, I'm assuming its because I didn't wipe the dalvik cache.
It turns on and is on the HTC screen (with powered by android at the bottom, the one it shows when turning on) but it stays on it forever and holding down the power button does nothing, do I just wait for the battery to run out, and boot to recovery and try again?
Vsolon7 said:
I flashed a custom rom, and I have TWRP for the recovery mode, I'm assuming its because I didn't wipe the dalvik cache.
It turns on and is on the HTC screen (with powered by android at the bottom, the one it shows when turning on) but it stays on it forever and holding down the power button does nothing, do I just wait for the battery to run out, and boot to recovery and try again?
Click to expand...
Click to collapse
to reboot to recovery:
Press and hold Power and volume Up until the phone shuts off
When the screen shuts off, let go of power/volume up and press and hold volume down until bootloader comes up.
Select recovery.
exad said:
to reboot to recovery:
Press and hold Power and volume Up until the phone shuts off
When the screen shuts off, let go of power/volume up and press and hold volume down until bootloader comes up.
Select recovery.
Click to expand...
Click to collapse
Okay, that works, I guess its just the ROM that's messed up. I'm going to try a new one and see how that goes
htc m8 bootloop how to solve ?
Have a HTC M8 that stucks in bootlop, here the details
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.25.21331147A1.06G
version-cpld: None
version-microp: None
version-main: 4.19.166.2
version-misc: PVT SHIP S-ON
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
I found the correct firmware and flashed it, Flash seems to be successful I see errors concerning sbl1
fastboot flash zip firmware.zip
At the end I see
OKAY [ 20.115s]
finished. total time: 23.271s
I see signature verifly failed sbl1
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=4
Here the complete output
< waiting for device >
target reported max download size of 1826418688 bytes
sending 'zip' (52102 KB)...
OKAY [ 3.125s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) total_image_number=12
(bootloader) start image[adsp] unzipping & flushing...
(bootloader) [RUU]UZ,adsp,0
(bootloader) [RUU]UZ,adsp,11
(bootloader) [RUU]UZ,adsp,21
(bootloader) [RUU]UZ,adsp,33
(bootloader) [RUU]UZ,adsp,43
(bootloader) [RUU]UZ,adsp,55
(bootloader) [RUU]UZ,adsp,66
(bootloader) [RUU]UZ,adsp,76
(bootloader) [RUU]UZ,adsp,88
(bootloader) [RUU]UZ,adsp,98
(bootloader) [RUU]UZ,adsp,100
(bootloader) [RUU]WP,adsp,0
(bootloader) [RUU]WP,adsp,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,11
(bootloader) [RUU]UZ,boot,23
(bootloader) [RUU]UZ,boot,35
(bootloader) [RUU]UZ,boot,48
(bootloader) [RUU]UZ,boot,59
(bootloader) [RUU]UZ,boot,70
(bootloader) [RUU]UZ,boot,81
(bootloader) [RUU]UZ,boot,95
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,99
(bootloader) [RUU]WP,boot,100
(bootloader) ...... Successful
(bootloader) current_image_number=1
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,6
(bootloader) [RUU]UZ,recovery,12
(bootloader) [RUU]UZ,recovery,19
(bootloader) [RUU]UZ,recovery,26
(bootloader) [RUU]UZ,recovery,32
(bootloader) [RUU]UZ,recovery,38
(bootloader) [RUU]UZ,recovery,52
(bootloader) [RUU]UZ,recovery,57
(bootloader) [RUU]UZ,recovery,63
(bootloader) [RUU]UZ,recovery,70
(bootloader) [RUU]UZ,recovery,77
(bootloader) [RUU]UZ,recovery,83
(bootloader) [RUU]UZ,recovery,89
(bootloader) [RUU]UZ,recovery,97
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,99
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) current_image_number=2
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) current_image_number=3
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=4
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=5
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) current_image_number=6
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=7
(bootloader) start image[sensor_hub] unzipping & flushing...
(bootloader) [RUU]UZ,sensor_hub,0
(bootloader) [RUU]UZ,sensor_hub,100
(bootloader) ...... Successful
(bootloader) current_image_number=8
(bootloader) start image[wcnss] unzipping & flushing...
(bootloader) [RUU]UZ,wcnss,0
(bootloader) [RUU]UZ,wcnss,24
(bootloader) [RUU]UZ,wcnss,45
(bootloader) [RUU]UZ,wcnss,68
(bootloader) [RUU]UZ,wcnss,96
(bootloader) [RUU]UZ,wcnss,100
(bootloader) [RUU]WP,wcnss,0
(bootloader) [RUU]WP,wcnss,100
(bootloader) ...... Successful
(bootloader) current_image_number=9
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,11
(bootloader) [RUU]UZ,radio,18
(bootloader) [RUU]UZ,radio,27
(bootloader) [RUU]UZ,radio,36
(bootloader) [RUU]UZ,radio,44
(bootloader) [RUU]UZ,radio,49
(bootloader) [RUU]UZ,radio,54
(bootloader) [RUU]UZ,radio,62
(bootloader) [RUU]UZ,radio,67
(bootloader) [RUU]UZ,radio,76
(bootloader) [RUU]UZ,radio,81
(bootloader) [RUU]UZ,radio,89
(bootloader) [RUU]UZ,radio,94
(bootloader) [RUU]UZ,radio,100
(bootloader) trying to rename MBA
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,35
(bootloader) [RUU]WP,radio,71
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) current_image_number=10
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]WP,rcdata,0
(bootloader) ...... Successful
(bootloader) current_image_number=11
OKAY [ 20.115s]
finished. total time: 23.271s
When I extract the boot.img from firmware.zip and only Flash the boot.img I get following error signature verify fail
fastboot flash boot boot.img
target reported max download size of 1826418688 bytes
sending 'boot' (8782 KB)...
OKAY [ 1.031s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.375s
Calculating the Image CRC the following Output, is 0x0 for sb2 and sb3 correct ?
rpm: 0xD0AD2083
sbl1: 0xE3DB0B9A
sbl2: 0x0
sbl3: 0x0
tz: 0x7A5540112
radio: 0x53CED4FB
hboot: 0x5E7000B5
boot:: 0x83481B7F
recovery: 0xA92185E2
system: 0xF7612432
Can you give me a hint how to solve the problem ?
Any idea how or where to get RUU Image for version 4.19.166.2 ?
Is it possible to downgrade the Firmware, but how to I know what are previous version to 4 .19.166.2 ?
Is there a way to unlock the device manually (APP can't be used in this Status) and to install a custom ROM ?
Your help is really appreciated, thx.
matti68 said:
Have a HTC M8 that stucks in bootlop, here the details
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.25.21331147A1.06G
version-cpld: None
version-microp: None
version-main: 4.19.166.2
version-misc: PVT SHIP S-ON
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
I found the correct firmware and flashed it, Flash seems to be successful I see errors concerning sbl1
fastboot flash zip firmware.zip
At the end I see
OKAY [ 20.115s]
finished. total time: 23.271s
I see signature verifly failed sbl1
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=4
Here the complete output
< waiting for device >
target reported max download size of 1826418688 bytes
sending 'zip' (52102 KB)...
OKAY [ 3.125s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) total_image_number=12
(bootloader) start image[adsp] unzipping & flushing...
(bootloader) [RUU]UZ,adsp,0
(bootloader) [RUU]UZ,adsp,11
(bootloader) [RUU]UZ,adsp,21
(bootloader) [RUU]UZ,adsp,33
(bootloader) [RUU]UZ,adsp,43
(bootloader) [RUU]UZ,adsp,55
(bootloader) [RUU]UZ,adsp,66
(bootloader) [RUU]UZ,adsp,76
(bootloader) [RUU]UZ,adsp,88
(bootloader) [RUU]UZ,adsp,98
(bootloader) [RUU]UZ,adsp,100
(bootloader) [RUU]WP,adsp,0
(bootloader) [RUU]WP,adsp,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,11
(bootloader) [RUU]UZ,boot,23
(bootloader) [RUU]UZ,boot,35
(bootloader) [RUU]UZ,boot,48
(bootloader) [RUU]UZ,boot,59
(bootloader) [RUU]UZ,boot,70
(bootloader) [RUU]UZ,boot,81
(bootloader) [RUU]UZ,boot,95
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,99
(bootloader) [RUU]WP,boot,100
(bootloader) ...... Successful
(bootloader) current_image_number=1
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,6
(bootloader) [RUU]UZ,recovery,12
(bootloader) [RUU]UZ,recovery,19
(bootloader) [RUU]UZ,recovery,26
(bootloader) [RUU]UZ,recovery,32
(bootloader) [RUU]UZ,recovery,38
(bootloader) [RUU]UZ,recovery,52
(bootloader) [RUU]UZ,recovery,57
(bootloader) [RUU]UZ,recovery,63
(bootloader) [RUU]UZ,recovery,70
(bootloader) [RUU]UZ,recovery,77
(bootloader) [RUU]UZ,recovery,83
(bootloader) [RUU]UZ,recovery,89
(bootloader) [RUU]UZ,recovery,97
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,99
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) current_image_number=2
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) current_image_number=3
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=4
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=5
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) current_image_number=6
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=7
(bootloader) start image[sensor_hub] unzipping & flushing...
(bootloader) [RUU]UZ,sensor_hub,0
(bootloader) [RUU]UZ,sensor_hub,100
(bootloader) ...... Successful
(bootloader) current_image_number=8
(bootloader) start image[wcnss] unzipping & flushing...
(bootloader) [RUU]UZ,wcnss,0
(bootloader) [RUU]UZ,wcnss,24
(bootloader) [RUU]UZ,wcnss,45
(bootloader) [RUU]UZ,wcnss,68
(bootloader) [RUU]UZ,wcnss,96
(bootloader) [RUU]UZ,wcnss,100
(bootloader) [RUU]WP,wcnss,0
(bootloader) [RUU]WP,wcnss,100
(bootloader) ...... Successful
(bootloader) current_image_number=9
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,11
(bootloader) [RUU]UZ,radio,18
(bootloader) [RUU]UZ,radio,27
(bootloader) [RUU]UZ,radio,36
(bootloader) [RUU]UZ,radio,44
(bootloader) [RUU]UZ,radio,49
(bootloader) [RUU]UZ,radio,54
(bootloader) [RUU]UZ,radio,62
(bootloader) [RUU]UZ,radio,67
(bootloader) [RUU]UZ,radio,76
(bootloader) [RUU]UZ,radio,81
(bootloader) [RUU]UZ,radio,89
(bootloader) [RUU]UZ,radio,94
(bootloader) [RUU]UZ,radio,100
(bootloader) trying to rename MBA
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,35
(bootloader) [RUU]WP,radio,71
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) current_image_number=10
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]WP,rcdata,0
(bootloader) ...... Successful
(bootloader) current_image_number=11
OKAY [ 20.115s]
finished. total time: 23.271s
When I extract the boot.img from firmware.zip and only Flash the boot.img I get following error signature verify fail
fastboot flash boot boot.img
target reported max download size of 1826418688 bytes
sending 'boot' (8782 KB)...
OKAY [ 1.031s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.375s
Calculating the Image CRC the following Output, is 0x0 for sb2 and sb3 correct ?
rpm: 0xD0AD2083
sbl1: 0xE3DB0B9A
sbl2: 0x0
sbl3: 0x0
tz: 0x7A5540112
radio: 0x53CED4FB
hboot: 0x5E7000B5
boot:: 0x83481B7F
recovery: 0xA92185E2
system: 0xF7612432
Can you give me a hint how to solve the problem ?
Any idea how or where to get RUU Image for version 4.19.166.2 ?
Is it possible to downgrade the Firmware, but how to I know what are previous version to 4 .19.166.2 ?
Is there a way to unlock the device manually (APP can't be used in this Status) and to install a custom ROM ?
Your help is really appreciated, thx.
Click to expand...
Click to collapse
Follow this guide and make sure to repeat the command for flashing the firmware twice.
Wait a couple seconds after the error appears and repeat the command. It will work the second time.
matti68 said:
I found the correct firmware and flashed it, Flash seems to be successful I see errors concerning sbl1
Can you give me a hint how to solve the problem ?
Click to expand...
Click to collapse
How are you so sure its the correct firmware? Where did you get it from?
Unless the firmware is signed and encrypted, and matches your CID; then you need s-off to flash it.
matti68 said:
Is it possible to downgrade the Firmware, but how to I know what are previous version to 4 .19.166.2 ?
Click to expand...
Click to collapse
Yes, its possible, but only with s-off.
I also don't see the point in doing so.
xbiggyl said:
Follow this guide and make sure to repeat the command for flashing the firmware twice.
Wait a couple seconds after the error appears and repeat the command. It will work the second time.
Click to expand...
Click to collapse
To flash this firmware S-OFF is required and I don't know how to achieve this.
---------- Post added at 08:45 PM ---------- Previous post was at 08:38 PM ----------
redpoint73 said:
How are you so sure its the correct firmware? Where did you get it from?
Unless the firmware is signed and encrypted, and matches your CID; then you need s-off to flash it.
Yes, its possible, but only with s-off.
I also don't see the point in doing so.
Click to expand...
Click to collapse
Found an OTA update zip on the Internet that contains the firmware.zip. When I flash the firmware.zip the signitature verification succeeds, so for me it seems the firmware is signed and has correct Version otherwise I would get an error.
Besides that if I unlock the device I get an error which is the case if the firmware.zip is signed.
matti68 said:
To flash this firmware S-OFF is required and I don't know how to achieve this.
Click to expand...
Click to collapse
I forgot to include the link to the guide I was pointing you to. I added the link to the post above as well as down below:
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
In this case. Can I flash boot.img via flastboot to solve this?
toanlaptop said:
In this case. Can I flash boot.img via flastboot to solve this?
Click to expand...
Click to collapse
Are you running a custom ROM? If so, flashing a custom ROM already flashes boot.img. No need or benefit in doing it separately by fastboot.
Otherwise, its hard to know what exactly is causing the bootloop, and whether flashing boot.img will solve it or not.
And you already said you tried to flash boot.img, and it failed.
exad said:
to reboot to recovery:
Press and hold Power and volume Up until the phone shuts off
When the screen shuts off, let go of power/volume up and press and hold volume down until bootloader comes up.
Select recovery.
Click to expand...
Click to collapse
I bet you get a lot of thanks button for xda hits because of this issue,huh? Thank you,the same thing happened to me and luckily I was home and plugged it up to my computer and luckily got adb reboot recovery to get me out of it. Hopefully I won't need this again but thanks for the info if I do.?
exad said:
to reboot to recovery:
Press and hold Power and volume Up until the phone shuts off
When the screen shuts off, let go of power/volume up and press and hold volume down until bootloader comes up.
Select recovery.
Click to expand...
Click to collapse
How can I turn off the phone if vol + doesn't works?
Hello all
I downloaded the following:
ARHD Lollipop (Android 5.0.1 + HTC Sense 6.0)
Download Android Revolution HD 34.6
I used to be on Kit Kat... after upgrading the rom, not realising I went to lollipop.. anyway, I get an error where it tries to connect to wifi and you get 'error' and also mobile data turns on but doesn't work at all... I've tried so many firmwares and none had fix the issue.
I'm using Telstra HTC m8 and no, my CID is still using TELST001 which is from my carrier, I'm not interested in going through process changing my CID, i've tried that and it fails.. I need this issue fixed as it's driving me nuts, 1 hour searching on threads produce no fix at all. Any help is appreciated, thank you.
My specs
S-OFF
(my hboot is 3.19.0.0000
Radio 1.25.214500021.06G)
bloodclaw said:
Hello all
I downloaded the following:
ARHD Lollipop (Android 5.0.1 + HTC Sense 6.0)
Download Android Revolution HD 34.6
I used to be on Kit Kat... after upgrading the rom, not realising I went to lollipop.. anyway, I get an error where it tries to connect to wifi and you get 'error' and also mobile data turns on but doesn't work at all... I've tried so many firmwares and none had fix the issue.
I'm using Telstra HTC m8 and no, my CID is still using TELST001 which is from my carrier, I'm not interested in going through process changing my CID, i've tried that and it fails.. I need this issue fixed as it's driving me nuts, 1 hour searching on threads produce no fix at all. Any help is appreciated, thank you.
My specs
S-OFF
(my hboot is 3.19.0.0000
Radio 1.25.214500021.06G)
Click to expand...
Click to collapse
Good day. This sounds like a firmware mismatch issue. If you go to the downloads for ARHD:
http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
More specifically 4.16.401.10:
http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One_M8/401/
They have the recommended firmware for the Rom. You will continue to have connectivity issues using a Lollipop Rom with Kitkat firmware.
Hope this helps.
Madcat8686 said:
Good day. This sounds like a firmware mismatch issue. If you go to the downloads for ARHD:
http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
More specifically 4.16.401.10:
http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One_M8/401/
They have the recommended firmware for the Rom. You will continue to have connectivity issues using a Lollipop Rom with Kitkat firmware.
Hope this helps.
Click to expand...
Click to collapse
Thank you very much. I have to say, the firmware list by date is confusing as! can you let me know which version number I should be downloading? Thank you
From flashing so may firmwares (lost count) in the end.. mobile data works but wifi gets a 'error' when it tries to connect, to turn on/off is sorta greyed out...
I dont want to do a complete wipe over this, I think it's to do with certain firmwares not being a fan of the rom I'm using or vice versa, so if anyone can help, it would be much appreciated
bloodclaw said:
From flashing so may firmwares (lost count) in the end.. mobile data works but wifi gets a 'error' when it tries to connect, to turn on/off is sorta greyed out...
I dont want to do a complete wipe over this, I think it's to do with certain firmwares not being a fan of the rom I'm using or vice versa, so if anyone can help, it would be much appreciated
Click to expand...
Click to collapse
Go to the second link I posted and find the 4.16.401.10 firmware. That is the correct firmware according to the ARHD folks.
I say this with the assumption you are S-Off. You can flash this firmware. I know thi can be frustrating sometimes but it's important to get the right Rom/Firmware match. I am S-Off as well and I have the developer Lollipop firmware. I can verify that it works with this Rom as well (4.16.1540.8)
Nevermind, you did list your carrier. The WWE firmware should work (4.16.401.10)
Madcat8686 said:
Go to the second link I posted and find the 4.16.401.10 firmware. That is the correct firmware according to the ARHD folks.
I say this with the assumption you are S-Off. You can flash this firmware. I know thi can be frustrating sometimes but it's important to get the right Rom/Firmware match. I am S-Off as well and I have the developer Lollipop firmware. I can verify that it works with this Rom as well (4.16.1540.8)
Nevermind, you did list your carrier. The WWE firmware should work (4.16.401.10)
Click to expand...
Click to collapse
Thanks, have updated to the firmware 4.16.401.10 yet still cant get wifi to work at all.. still showing error and when you go into wifi, it's just blank
results from firmware flash
C:\android-sdk-windows\platform-tools>fastboot flash zip firmware
< waiting for device >
target reported max download size of 1826418688 bytes
sending 'zip' (52100 KB)...
OKAY [ 2.699s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) total_image_number=12
(bootloader) start image[adsp] unzipping & flushing...
(bootloader) [RUU]UZ,adsp,0
(bootloader) [RUU]UZ,adsp,11
(bootloader) [RUU]UZ,adsp,21
(bootloader) [RUU]UZ,adsp,33
(bootloader) [RUU]UZ,adsp,43
(bootloader) [RUU]UZ,adsp,55
(bootloader) [RUU]UZ,adsp,66
(bootloader) [RUU]UZ,adsp,76
(bootloader) [RUU]UZ,adsp,88
(bootloader) [RUU]UZ,adsp,98
(bootloader) [RUU]UZ,adsp,100
(bootloader) [RUU]WP,adsp,0
(bootloader) [RUU]WP,adsp,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,12
(bootloader) [RUU]UZ,boot,24
(bootloader) [RUU]UZ,boot,35
(bootloader) [RUU]UZ,boot,47
(bootloader) [RUU]UZ,boot,59
(bootloader) [RUU]UZ,boot,70
(bootloader) [RUU]UZ,boot,81
(bootloader) [RUU]UZ,boot,94
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,99
(bootloader) [RUU]WP,boot,100
(bootloader) ...... Successful
(bootloader) current_image_number=1
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,6
(bootloader) [RUU]UZ,recovery,13
(bootloader) [RUU]UZ,recovery,19
(bootloader) [RUU]UZ,recovery,26
(bootloader) [RUU]UZ,recovery,32
(bootloader) [RUU]UZ,recovery,38
(bootloader) [RUU]UZ,recovery,53
(bootloader) [RUU]UZ,recovery,58
(bootloader) [RUU]UZ,recovery,63
(bootloader) [RUU]UZ,recovery,70
(bootloader) [RUU]UZ,recovery,77
(bootloader) [RUU]UZ,recovery,83
(bootloader) [RUU]UZ,recovery,89
(bootloader) [RUU]UZ,recovery,96
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,99
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) current_image_number=2
(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) current_image_number=3
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=4
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=5
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=6
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1,0
(bootloader) [RUU]WP,sbl1,100
(bootloader) ...... Successful
(bootloader) current_image_number=7
(bootloader) start image[sensor_hub] unzipping & flushing...
(bootloader) [RUU]UZ,sensor_hub,0
(bootloader) [RUU]UZ,sensor_hub,100
(bootloader) ...... Successful
(bootloader) current_image_number=8
(bootloader) start image[wcnss] unzipping & flushing...
(bootloader) [RUU]UZ,wcnss,0
(bootloader) [RUU]UZ,wcnss,24
(bootloader) [RUU]UZ,wcnss,45
(bootloader) [RUU]UZ,wcnss,68
(bootloader) [RUU]UZ,wcnss,96
(bootloader) [RUU]UZ,wcnss,100
(bootloader) [RUU]WP,wcnss,0
(bootloader) [RUU]WP,wcnss,100
(bootloader) ...... Successful
(bootloader) current_image_number=9
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,11
(bootloader) [RUU]UZ,radio,18
(bootloader) [RUU]UZ,radio,23
(bootloader) [RUU]UZ,radio,31
(bootloader) [RUU]UZ,radio,40
(bootloader) [RUU]UZ,radio,49
(bootloader) [RUU]UZ,radio,58
(bootloader) [RUU]UZ,radio,67
(bootloader) [RUU]UZ,radio,76
(bootloader) [RUU]UZ,radio,81
(bootloader) [RUU]UZ,radio,89
(bootloader) [RUU]UZ,radio,94
(bootloader) [RUU]UZ,radio,100
(bootloader) trying to rename MBA
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,35
(bootloader) [RUU]WP,radio,71
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) current_image_number=10
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,100
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,100
(bootloader) ...... Successful
(bootloader) current_image_number=11
OKAY [ 15.928s]
finished. total time: 18.629s
Click to expand...
Click to collapse
bloodclaw said:
Thanks, have updated to the firmware 4.16.401.10 yet still cant get wifi to work at all.. still showing error and when you go into wifi, it's just blank
results from firmware flash
Click to expand...
Click to collapse
That's a good flash. To eliminate the Rom being an issue, you could try another Lolipop sense Rom. Maybe Insertcoin or Skydragon? They use the same base firmware you got with the RUU (4.16.401.10 WWE). It's worth a shot. Hopefully it's not a hardware issue.
Oh and when flashing firmware like this, I usually flash twice. Sometimes it makes a difference.
Thank you, I'll see how it goes.. thanks again for helping and guiding me, so much appreciation :fingers-crossed:
Okay, I managed to get it working.. after reflashing rom and doing a factory reset.. now I have a new problem, all my apps that require to use SD card is not reading it.
Example when i try to take a screenshot it tells me 'couldnt capture screenshot due to limited storage space'.. or snapchat 'connect a SD to view snapchat'... my snapchat is fine and even ive done a format to it just to make sure it's working. I swear I've come across lollipop issues more than kit kat
Hello Friends.
my HTC ONE M8 (M8_UL) originally had the OS KitKat 4.4.4. I update the GPE cm-12.1-20150901-SNAPSHOT-YOG4PAO23A-m8. The phone worked well a couple of months, then suddenly stopped working.
Then try to repair installing the firmware sense of KitKat, but after this attempt the recovery stopped working. Currently you install a firmware GPE again, but the phone is still not working. The custon recovery not working.
If I restart the phone, the HTC logo appears and the phone is turned off.
If the logo appears on HTC bootloader recovery selected and the phone is turned off.
These are the solutions I've tried:
1) fastboot flash recovery recovery.img (recovery.img = OpenRecovery-TWRP-2.7.0.1-m8.img, OpenRecovery-TWRP-2.7.1.0-m8.img, OpenRecovery-TWRP-2.8.5.0-m8.img).
2) fastboot flash boot boot.img (boot.img = boot.img Extracted to ATT444firmware.zip, or UCP-HTC_One_ (M8) _GPe_Marshmallow-6.0_MRA58K.H6_5.07.1700.6_0p6bdiag.zip)
3) relocked fastboot and install RUU_M8[email protected]50319A_40.45.C33065.00_F_release_446225_signed_2.exe
Nothing has worked. I still recovery. I try turns off so soon.
This video show the problem!!! search in youtube "M8 AT&T, bootloop, recovery doesn't work. HBOOT work fine"
This is my actual configuration:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.A13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.07.1700.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT46KWM01362
(bootloader) imei: -------------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 11459804
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 19(ms)
gemejiar said:
Then try to repair installing the firmware sense of KitKat, but after this attempt the recovery stopped working. Currently you install a firmware GPE again, but the phone is still not working. The custon recovery not working.
Click to expand...
Click to collapse
What firmware, where did you get it and what is the file name and version number?
What happened when you flashed it, what was the result and what were the error messages?
gemejiar said:
2) fastboot flash boot boot.img (boot.img = boot.img Extracted to ATT444firmware.zip, or UCP-HTC_One_ (M8) _GPe_Marshmallow-6.0_MRA58K.H6_5.07.1700.6_0p6bdiag.zip)
Click to expand...
Click to collapse
If you didn't get a working Sense ROM on the phone in the first place, flashing the boot.img won't help anything.
gemejiar said:
3) relocked fastboot and install RUU_M8[email protected]50319A_40.45.C33065.00_F_release_446225_signed_2.exe
Click to expand...
Click to collapse
Relocking bootloader is not required to RUU when s-off; and its not recommended. It doesn't help anything, and will hamper or needlessly complicate recovery efforts.
Again, what were the specific details of the results of running the RUU? How did the phone react, what did the RUU do, error messages, etc.
Thanks very much for your help!!
redpoint73 said:
What firmware, where did you get it and what is the file name and version number?
Click to expand...
Click to collapse
The firmware file is firmware_4.16.401.9.zip, but I install the GPE firmware version to.
redpoint73 said:
What happened when you flashed it, what was the result and what were the error messages?
Click to expand...
Click to collapse
the firmware is installed correctly and without errors, but the phone does not boot
redpoint73 said:
If you didn't get a working Sense ROM on the phone in the first place, flashing the boot.img won't help anything.
Relocking bootloader is not required to RUU when s-off; and its not recommended. It doesn't help anything, and will hamper or needlessly complicate recovery efforts.
Click to expand...
Click to collapse
I am not expert, please help me!
redpoint73 said:
Again, what were the specific details of the results of running the RUU? How did the phone react, what did the RUU do, error messages, etc.
Click to expand...
Click to collapse
The RUU instalation is normal, no errors appear.
What tests do you recommend me to diagnose the problem?
What commands can I use in bootloader mode?
gemejiar said:
The firmware file is firmware_4.16.401.9.zip, but I install the GPE firmware version to.
the firmware is installed correctly and without errors, but the phone does not boot
Click to expand...
Click to collapse
The Sense firmware definitely did not install correctly. Otherwise, you would have a white bootloader screen to match the Sense firmware.
Also, 4.16.401 is Euro firmware, not AT&T. If its signed firmware, it won't flash with the wrong CID and MID on the device. But I can't tell what you are trying to flash, exactly; since I asked where you got the firmware from, and you never answered.
I would suggest running a GPE RUU (especially if the intent is to stay on GPE). Otherwise try to flash one of the AT&T firmwares included on the following, then try the AT&T RUU again: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Really I do not remember where I download a firmware .
I will make the changes That you suggest me and tell you.
Thank you again
I followed the instructions of this page:
http://forum.xda-developers.com/att...-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Results of this process are:
C:\fastboot>fastboot oem rebootRUU
... (bootloader) Start Verify: 0
OKAY
Execution time is 20(ms)
C:\fastboot>fastboot flash zip 428_firmware.zip
sending 'zip'... (36029 KB) OKAY
sending time = 2.235 secs
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) total_image_number=8
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
(bootloader) current_image_number=1
(bootloader) current_image_number=2
(bootloader) current_image_number=3
(bootloader) current_image_number=4
(bootloader) current_image_number=5
(bootloader) current_image_number=6
(bootloader) current_image_number=7
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
For "hboot-preupdate" response, restart the same procedure for device HT46KWM01
62...
sending 'zip'... (36029 KB) OKAY
sending time = 2.239 secs
writing 'zip'... (bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) total_image_number=11
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,13
(bootloader) [RUU]UZ,boot,23
(bootloader) [RUU]UZ,boot,36
(bootloader) [RUU]UZ,boot,49
(bootloader) [RUU]UZ,boot,59
(bootloader) [RUU]UZ,boot,69
(bootloader) [RUU]UZ,boot,81
(bootloader) [RUU]UZ,boot,93
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
(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) current_image_number=1
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=2
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=3
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1,0
(bootloader) [RUU]WP,sbl1,100
(bootloader) ...... Successful
(bootloader) current_image_number=4
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=5
(bootloader) start image[sensor_hub] unzipping & flushing...
(bootloader) [RUU]UZ,sensor_hub,0
(bootloader) [RUU]UZ,sensor_hub,100
(bootloader) [RUU]WP,sensor_hub,0
(bootloader) [RUU]WP,sensor_hub,4
(bootloader) [RUU]WP,sensor_hub,8
(bootloader) [RUU]WP,sensor_hub,12
(bootloader) [RUU]WP,sensor_hub,16
(bootloader) [RUU]WP,sensor_hub,20
(bootloader) [RUU]WP,sensor_hub,24
(bootloader) [RUU]WP,sensor_hub,28
(bootloader) [RUU]WP,sensor_hub,32
(bootloader) [RUU]WP,sensor_hub,36
(bootloader) [RUU]WP,sensor_hub,40
(bootloader) [RUU]WP,sensor_hub,44
(bootloader) [RUU]WP,sensor_hub,48
(bootloader) [RUU]WP,sensor_hub,52
(bootloader) [RUU]WP,sensor_hub,56
(bootloader) [RUU]WP,sensor_hub,60
(bootloader) [RUU]WP,sensor_hub,64
(bootloader) [RUU]WP,sensor_hub,68
(bootloader) [RUU]WP,sensor_hub,72
(bootloader) [RUU]WP,sensor_hub,76
(bootloader) [RUU]WP,sensor_hub,80
(bootloader) [RUU]WP,sensor_hub,84
(bootloader) [RUU]WP,sensor_hub,88
(bootloader) [RUU]WP,sensor_hub,92
(bootloader) [RUU]WP,sensor_hub,96
(bootloader) [RUU]WP,sensor_hub,100
(bootloader) ...... Successful
(bootloader) current_image_number=6
(bootloader) start image[tz] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) current_image_number=7
(bootloader) start image[wcnss] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) current_image_number=8
(bootloader) start image[radio] unzipping & flushing...
(bootloader) trying to rename MBA
(bootloader) ...... Successful
(bootloader) current_image_number=9
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) current_image_number=10
OKAY
Flash Zip Complete
Execution time is 58(s)
C:\fastboot>fastboot reboot-bootloader
rebooting into bootloader... OKAY
Execution time is 14(ms)
C:\fastboot>fastboot flash recovery twrp-2.8.6.0-m8.img
sending 'recovery' (17034 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 3(s)
C:\fastboot>
When i want to enter in recovery mode (TWRP), the phone turns off.
Please you see the video in youtube with this title "M8 AT&T, boot loop, recovery doesn't work. HBOOT work fine V2"
this other video show the previos state of cellphone (see in youtube "M8 AT&T, boot loop, recovery doesn't work. HBOOT work fine")
What do you think?
Can I install a Stock Backups?
the stock backups restores partitions correctly?
Help me please, i do not know what I need to do!!
gemejiar said:
I followed the instructions of this page:
http://forum.xda-developers.com/att...-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Results of this process are:
C:\fastboot>fastboot oem rebootRUU
... (bootloader) Start Verify: 0
OKAY
Execution time is 20(ms)
C:\fastboot>fastboot flash zip 428_firmware.zip
sending 'zip'... (36029 KB) OKAY
sending time = 2.235 secs
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) total_image_number=8
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
(bootloader) current_image_number=1
(bootloader) current_image_number=2
(bootloader) current_image_number=3
(bootloader) current_image_number=4
(bootloader) current_image_number=5
(bootloader) current_image_number=6
(bootloader) current_image_number=7
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
For "hboot-preupdate" response, restart the same procedure for device HT46KWM01
62...
sending 'zip'... (36029 KB) OKAY
sending time = 2.239 secs
writing 'zip'... (bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) total_image_number=11
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,13
(bootloader) [RUU]UZ,boot,23
(bootloader) [RUU]UZ,boot,36
(bootloader) [RUU]UZ,boot,49
(bootloader) [RUU]UZ,boot,59
(bootloader) [RUU]UZ,boot,69
(bootloader) [RUU]UZ,boot,81
(bootloader) [RUU]UZ,boot,93
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
(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) current_image_number=1
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=2
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=3
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1,0
(bootloader) [RUU]WP,sbl1,100
(bootloader) ...... Successful
(bootloader) current_image_number=4
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=5
(bootloader) start image[sensor_hub] unzipping & flushing...
(bootloader) [RUU]UZ,sensor_hub,0
(bootloader) [RUU]UZ,sensor_hub,100
(bootloader) [RUU]WP,sensor_hub,0
(bootloader) [RUU]WP,sensor_hub,4
(bootloader) [RUU]WP,sensor_hub,8
(bootloader) [RUU]WP,sensor_hub,12
(bootloader) [RUU]WP,sensor_hub,16
(bootloader) [RUU]WP,sensor_hub,20
(bootloader) [RUU]WP,sensor_hub,24
(bootloader) [RUU]WP,sensor_hub,28
(bootloader) [RUU]WP,sensor_hub,32
(bootloader) [RUU]WP,sensor_hub,36
(bootloader) [RUU]WP,sensor_hub,40
(bootloader) [RUU]WP,sensor_hub,44
(bootloader) [RUU]WP,sensor_hub,48
(bootloader) [RUU]WP,sensor_hub,52
(bootloader) [RUU]WP,sensor_hub,56
(bootloader) [RUU]WP,sensor_hub,60
(bootloader) [RUU]WP,sensor_hub,64
(bootloader) [RUU]WP,sensor_hub,68
(bootloader) [RUU]WP,sensor_hub,72
(bootloader) [RUU]WP,sensor_hub,76
(bootloader) [RUU]WP,sensor_hub,80
(bootloader) [RUU]WP,sensor_hub,84
(bootloader) [RUU]WP,sensor_hub,88
(bootloader) [RUU]WP,sensor_hub,92
(bootloader) [RUU]WP,sensor_hub,96
(bootloader) [RUU]WP,sensor_hub,100
(bootloader) ...... Successful
(bootloader) current_image_number=6
(bootloader) start image[tz] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) current_image_number=7
(bootloader) start image[wcnss] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) current_image_number=8
(bootloader) start image[radio] unzipping & flushing...
(bootloader) trying to rename MBA
(bootloader) ...... Successful
(bootloader) current_image_number=9
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) current_image_number=10
OKAY
Flash Zip Complete
Execution time is 58(s)
C:\fastboot>fastboot reboot-bootloader
rebooting into bootloader... OKAY
Execution time is 14(ms)
C:\fastboot>fastboot flash recovery twrp-2.8.6.0-m8.img
sending 'recovery' (17034 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 3(s)
C:\fastboot>
When i want to enter in recovery mode (TWRP), the phone turns off.
Please you see the video in youtube with this title "M8 AT&T, boot loop, recovery doesn't work. HBOOT work fine V2"
this other video show the previos state of cellphone (see in youtube "M8 AT&T, boot loop, recovery doesn't work. HBOOT work fine")
What do you think?
Can I install a Stock Backups?
the stock backups restores partitions correctly?
Help me please, i do not know what I need to do!!
Click to expand...
Click to collapse
I can help you pm me and i will help you out over teamviewer.
step 1 well i reflash the gpe rooted rom
step 2 i change his mid to dev edtion one
step 3 change his cid to super cid
step 4 i flash 1.54.401.5-W_Splash and let him wipe data and cache in stock recovery
step 5 change his cid to dev
step 6 ran dev ruu the lateset
http://forum.xda-developers.com/showthread.php?t=2733523
gemejiar said:
C:\fastboot>fastboot flash recovery twrp-2.8.6.0-m8.img
sending 'recovery' (17034 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 3(s)
C:\fastboot>
When i want to enter in recovery mode (TWRP), the phone turns off.
Click to expand...
Click to collapse
What I suggested, was to flash the firmware, (don't install TWRP) then try a Sense AT&T RUU.
I can not turn on the cellphone. I can not input in boot loader mode. I probe vol up + vol down + power buttom per 2 min. What things I can do?
toysoldierq said:
I can help you pm me and i will help you out over teamviewer.
step 1 well i reflash the gpe rooted rom
step 2 i change his mid to dev edtion one
step 3 change his cid to super cid
step 4 i flash 1.54.401.5-W_Splash and let him wipe data and cache in stock recovery
step 5 change his cid to dev
step 6 ran dev ruu the lateset
http://forum.xda-developers.com/showthread.php?t=2733523
Click to expand...
Click to collapse
What's with the PMs and TeamViewer?
That's not the way things are done on XDA.
Help him in this thread with instructions, so that others that might have the same issue can find the solution by searching.
I believe this has already been mentioned to you in the past, and that you agreed to stop posting "PM & TeamViewer"
Bought this M8 stuck at the bootloader screen, unlocked the bootloader and installed a recovery and then installed Leedroid rom, it installed fine but upon rebooting it black screened, connected it to my PC to see a new device QHSUSB__BULK now if I leave it for a few minutes it eventually boots the rom, I also don't see the charging screen like you would if it was powered off, seems every time it powers down or reboots it enter QLOAD mode
The next problem is my baseband and IMEI are unknown/missing from the settings page, here is the getvar info
C:\Users\ando>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.161.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH4BEWM01981
(bootloader) imei: (this does show a imei number, i've removed it for obvious reasons)
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 255f41e7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Do I need to relock and RUU?
Tried to get this RUU to work but it doesn't even run RUU_M8_UL_L50_SENSE60_MR_Vodafone_UK_4.19.161.2_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417184_signed
tried on different computers all the same result, guess this is corrupted.
I think seeing QHSUSB__BULK on PC is normal, if the phone is not powered on. No charging animation is another matter, as it isn't normal.
What TWRP recovery version number are you using?
---------- Post added at 08:58 AM ---------- Previous post was at 08:56 AM ----------
ando_uk said:
Tried to get this RUU to work but it doesn't even run RUU_M8_UL_L50_SENSE60_MR_Vodafone_UK_4.19.161.2_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417184_signed
tried on different computers all the same result, guess this is corrupted.
Click to expand...
Click to collapse
Not sure what that means, "doesn't even run". Is there an error message, or does it hang at a certain point (always be specific as possible when posting)?
It would be normal for that RUU to fail. You can't a lower version number RUU (in this case 4.19.161.2) than the main version shown in getvar, unless you have s-off.
redpoint73 said:
I think seeing QHSUSB__BULK on PC is normal, if the phone is not powered on. No charging animation is another matter, as it isn't normal.
What TWRP recovery version number are you using?
---------- Post added at 08:58 AM ---------- Previous post was at 08:56 AM ----------
Not sure what that means, "doesn't even run". Is there an error message, or does it hang at a certain point (always be specific as possible when posting)?
It would be normal for that RUU to fail. You can't a lower version number RUU (in this case 4.19.161.2) than the main version shown in getvar, unless you have s-off.
Click to expand...
Click to collapse
Sorry should of explained, the program crashes just after running it with this error "InstallScript Setup Laucnher has stopped working"
So if i'm on a 161.3 how do I restore as I can't find a RUU for this, s-off only option?
Also I was running twrp-3.0.2-0, but flashed a stock rom back so im now back at stock
That RUU is corrupted. The size is too small for M8 RUU.
What you can do is restore non-rooted 4.19.161.3 backup and install 4.19.161.3 stock recovery then OTA to Marshmallow 6.12.161.4. This should fix the missing baseband problem.
ando_uk said:
Also I was running twrp-3.0.2-0, but flashed a stock rom back so im now back at stock
Click to expand...
Click to collapse
This is confusing. You never stated flashing any sort of stock ROM, aside from the RUU that failed. Your top post says you are on LeeDroid. Its not clear what "stock ROM" you flashed.
But in any case, ckpv5 gave you a good suggestion for the way forward.
ckpv5 said:
That RUU is corrupted. The size is too small for M8 RUU.
What you can do is restore non-rooted 4.19.161.3 backup and install 4.19.161.3 stock recovery then OTA to Marshmallow 6.12.161.4. This should fix the missing baseband problem.
Click to expand...
Click to collapse
Ok, i'm already on stock non rooted 4.19.161.3, how do I OTA?
Tried in the update screen but only get app updates
redpoint73 said:
This is confusing. You never stated flashing any sort of stock ROM, aside from the RUU that failed. Your top post says you are on LeeDroid. Its not clear what "stock ROM" you flashed.
But in any case, ckpv5 gave you a good suggestion for the way forward.
Click to expand...
Click to collapse
Sorry was a stock twrp backup Vodafone 4.19.161.3
I think i'm there, no longer get that QHSUSB__BULK when powered off and plugged in, I also now see the battery percentage screen when off and plugged in and charging, just the stock rom doesn't seem to boot now
Did I do this correctly? I chose the vodafone one linked here by ckpv5 CID VODAP001, VODAP102, VODAPE17, VODAP405, VODAP304, VODAPD18
MID 0P6B10000
fw_6.12.161.4 http://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
C:\Users\ando>fastboot flash zip C:\Users\ando\Downloads\fw_
sending 'zip' (53848 KB)...
OKAY [ 2.597s]
writing 'zip'...
(bootloader) adopting the signature contained in this image.
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) total_image_number=13
(bootloader) start image[adsp] unzipping & flushing...
(bootloader) [RUU]UZ,adsp,0
(bootloader) [RUU]UZ,adsp,10
(bootloader) [RUU]UZ,adsp,21
(bootloader) [RUU]UZ,adsp,33
(bootloader) [RUU]UZ,adsp,43
(bootloader) [RUU]UZ,adsp,54
(bootloader) [RUU]UZ,adsp,65
(bootloader) [RUU]UZ,adsp,76
(bootloader) [RUU]UZ,adsp,88
(bootloader) [RUU]UZ,adsp,98
(bootloader) [RUU]UZ,adsp,100
(bootloader) [RUU]WP,adsp,0
(bootloader) [RUU]WP,adsp,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,8
(bootloader) [RUU]UZ,boot,15
(bootloader) [RUU]UZ,boot,20
(bootloader) [RUU]UZ,boot,25
(bootloader) [RUU]UZ,boot,30
(bootloader) [RUU]UZ,boot,35
(bootloader) [RUU]UZ,boot,40
(bootloader) [RUU]UZ,boot,50
(bootloader) [RUU]UZ,boot,55
(bootloader) [RUU]UZ,boot,65
(bootloader) [RUU]UZ,boot,70
(bootloader) [RUU]UZ,boot,80
(bootloader) [RUU]UZ,boot,86
(bootloader) [RUU]UZ,boot,95
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,99
(bootloader) [RUU]WP,boot,100
(bootloader) ...... Successful
(bootloader) current_image_number=1
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,6
(bootloader) [RUU]UZ,recovery,11
(bootloader) [RUU]UZ,recovery,17
(bootloader) [RUU]UZ,recovery,22
(bootloader) [RUU]UZ,recovery,28
(bootloader) [RUU]UZ,recovery,33
(bootloader) [RUU]UZ,recovery,39
(bootloader) [RUU]UZ,recovery,44
(bootloader) [RUU]UZ,recovery,56
(bootloader) [RUU]UZ,recovery,61
(bootloader) [RUU]UZ,recovery,66
(bootloader) [RUU]UZ,recovery,72
(bootloader) [RUU]UZ,recovery,79
(bootloader) [RUU]UZ,recovery,89
(bootloader) [RUU]UZ,recovery,95
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,89
(bootloader) [RUU]WP,recovery,99
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) current_image_number=2
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) current_image_number=3
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=4
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) current_image_number=5
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=6
(bootloader) start image[sensor_hub] unzipping & flushing...
(bootloader) [RUU]UZ,sensor_hub,0
(bootloader) [RUU]UZ,sensor_hub,100
(bootloader) [RUU]WP,sensor_hub,0
(bootloader) [RUU]WP,sensor_hub,4
(bootloader) [RUU]WP,sensor_hub,8
(bootloader) [RUU]WP,sensor_hub,12
(bootloader) [RUU]WP,sensor_hub,16
(bootloader) [RUU]WP,sensor_hub,20
(bootloader) [RUU]WP,sensor_hub,24
(bootloader) [RUU]WP,sensor_hub,28
(bootloader) [RUU]WP,sensor_hub,32
(bootloader) [RUU]WP,sensor_hub,36
(bootloader) [RUU]WP,sensor_hub,40
(bootloader) [RUU]WP,sensor_hub,44
(bootloader) [RUU]WP,sensor_hub,48
(bootloader) [RUU]WP,sensor_hub,52
(bootloader) [RUU]WP,sensor_hub,56
(bootloader) [RUU]WP,sensor_hub,60
(bootloader) [RUU]WP,sensor_hub,64
(bootloader) [RUU]WP,sensor_hub,68
(bootloader) [RUU]WP,sensor_hub,72
(bootloader) [RUU]WP,sensor_hub,76
(bootloader) [RUU]WP,sensor_hub,80
(bootloader) [RUU]WP,sensor_hub,84
(bootloader) [RUU]WP,sensor_hub,88
(bootloader) [RUU]WP,sensor_hub,92
(bootloader) [RUU]WP,sensor_hub,96
(bootloader) [RUU]WP,sensor_hub,100
(bootloader) ...... Successful
(bootloader) current_image_number=7
(bootloader) start image[sp1] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) current_image_number=8
(bootloader) start image[tz] unzipping & flushing...
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) current_image_number=9
(bootloader) start image[wcnss] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) current_image_number=10
(bootloader) start image[radio] unzipping & flushing...
(bootloader) trying to rename MBA
(bootloader) ...... Successful
(bootloader) current_image_number=11
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) current_image_number=12
OKAY [ 65.223s]
finished. total time: 67.820s
C:\Users\ando>fastboot reboot
rebooting...
ando_uk said:
Did I do this correctly? I chose the vodafone one linked here by ckpv5 CID VODAP001, VODAP102, VODAPE17, VODAP405, VODAP304, VODAPD18
MID 0P6B10000
fw_6.12.161.4 http://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Click to expand...
Click to collapse
You definitely did not do that correctly (at least not what ckpv5 was suggesting).
You flashed a signed firmware, which is not a ROM. Firmware just contains hboot, radio, and several other modules (needed to make a ROM work), but does not contain the actual ROM/OS itself. That is why your phone isn't booting.
How you chose to flash that, is puzzling to me. The fact the firmware you flashed was only around 80 MB should have been a clue that it wasn't a full ROM backup (which is over 1 GB).
You should still be able to get the phone working (and updated to MM) but it will take more steps now. What I think you can do now, is download the TWRP backup for 6.12.161.4 from Post #3 of that same thread. Then unlock bootloader again, flash TWRP back on the phone, and install the 6.12.161.4 backup per instructions in Post #1 of that thread.
So I didn't reinstall stock again, installed leedroid, took a while but it booted and sim was recognised and all now working, baseband imei all show now
Thanks for all the help
Hi! So, I bought a new HTC One M8 "carrier-free" without more details... After making sure it booted, I thought I could try my hand at installing a custom ROM. I've done this before with several other devices (HTC One X, Moto G, Nexus 5, Galaxy S4), so I thought I'd have no issues. And at first, I didn't. But after flashing ARHD 53.1, I found out it was stuck on the HBOOT screen. So I asked in that thread, and, judging by the info provided through fastboot getvar all, one of the recommendations was that I update my firmware... little did I know, Verizon has at least two models, and mine is, naturally, the most rare: M8_WLV. I didn't know it at the time, but after trying many methods, I somehow managed to update the firmware to 6.21.605.3... which should not be possible, if what I've read since then is correct. I know I messed around with changing the MID and CID at some point (then reverted it). I downloaded and tried to / flashes countless stock ROMs, firmwares, a few RUUs and recoveries, everything I could get my hands on.
I somehow managed to flash a stock Verizon ROM which for whatever worked fine (but, naturally, didn't recognize my SIM). I used TWRP to wipe the device entirely so that I could start over...
I now have an abomination that has a mixed sense of identity regarding firmware, radio and OS versions (I have none installed, the only thing in my phone at the moment is the TWRP folder).
Is there a way to salvage this? Even if it means having to use 4.4.4?
The fastboot getvar all info I had before messing with the phone:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.09.20.0926
version-cpld: None
version-microp: None
version-main: 3.31.512.2
version-misc: PVT SHIP S-OFF
serialno:
imei:
imei2: Not Support
meid: 99000499736679
product: m8_wlv
platform: hTCBmsm8974
modelid: 0P6B20000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 2e9b7c51
hbootpreupdate: 11
gencheckpt: 0
My current info:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.29.214500021.24_2G
version-cpld: None
version-microp: None
version-main: 6.12.1540.4
version-misc: PVT SHIP S-OFF
serialno:
imei:
imei2: Not Support
meid: 99000499736679
product: m8_wlv
platform: hTCBmsm8974
modelid: 0P6B20000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 76df2b54
hbootpreupdate: 11
gencheckpt: 0
Any and all suggestions are welcome. The more detailed, the better, so I don't mess up again. If not... I guess I now have a very expensive paper weight.
Read this - https://forum.xda-developers.com/htc-one-m8/help/help-friends-t3402398
You can try the RUU linked on post #5 and see whether the mobile data is fixed.
ckpv5 said:
Read this - https://forum.xda-developers.com/htc-one-m8/help/help-friends-t3402398
You can try the RUU linked on post #5 and see whether the mobile data is fixed.
Click to expand...
Click to collapse
Hi ckpv5, thank you for your reply! You're everywhere! (And that's a good thing )
I had already tried with that file, but I wasn't able to flash it because I got the following error:
target reported max download size of 1826418688 bytes
sending 'zip' (1424880 KB)...
OKAY [ 59.431s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 59.582s
According to some research on that code, it would seem that the cause was because the android-info.txt file inside had a different CID than mine. Some recommendations were to modify that file, but I couldn't do it because WinRAR reported the file as corrupted when I tried to update it. I changed my phone's CID to match, but it still didn't work.
Thanks to your reply, I realized that I needed to use a different fastboot, htc_fastboot. However, I couldn't get it to work. When installing adb-setup-1.4.3, I got error messages about Windows not able to find the specified path. So, before delving any deeper into that, I tried flashing (with great thanks to your helpful guide and alternatives), a ROM I found on another thread: DOTTAT_VZWM8_S_OFF_5.0.1_RUU.zip (https://www.androidfilehost.com/?fid=95916177934538677)
AND IT WORKED! After the process was done, my phone now has a Verizon Lollipop stock ROM, even though that file was supposed to be for the VZW model (no mention of my WLV). AND I HAVE A WORKING DATA CONNECTION! So you saved my phone!
Now comes the last part, where I want to push my luck once again (unless you recommend me not to, but at least if I do it, it would be with proper guidance): if I wanted to install the ARHD ROM, you mentioned I needed to flash a Verizon-compatible firmware immediately after flashing the custom ROM. Do I have to extract the "boot.img" file from the ROM I found to accomplish that?
Once again, thank you IMMENSELY for saving my phone! You are the best!
Zombielicious said:
I know I messed around with changing the MID and CID at some point (then reverted it). I downloaded and tried to / flashes countless stock ROMs, firmwares, a few RUUs and recoveries, everything I could get my hands on.
I somehow managed to flash a stock Verizon ROM which for whatever worked fine (but, naturally, didn't recognize my SIM). I used TWRP to wipe the device entirely so that I could start over...
Click to expand...
Click to collapse
Maybe you've already somewhat figured this: But be aware, that messing with the MID on the Verizon (in your case LRA - Verizon variant) version, with intent to flash another version's firmware or RUU is a bad idea. It caused the radio problem you witnessed. Usually fixable with the Verizon (LRA) RUU, but we've also seen permanent radio bricks from flashing wrong firmware/RUU to the Verizon (LRA) M8. So consider yourself lucky.
Simply put, the CDMA versions of the M8 (Verizon/LRA and Sprint) are peculiar, in that they are not compatible with firmware from other M8 versions. And a radio brick (possibly permanent) may result. So only the respective firmware/RUU (in you case Verizon/LRA) should ever be installed.
---------- Post added at 10:26 AM ---------- Previous post was at 10:20 AM ----------
Zombielicious said:
Now comes the last part, where I want to push my luck once again (unless you recommend me not to, but at least if I do it, it would be with proper guidance): if I wanted to install the ARHD ROM, you mentioned I needed to flash a Verizon-compatible firmware immediately after flashing the custom ROM. Do I have to extract the "boot.img" file from the ROM I found to accomplish that?
Click to expand...
Click to collapse
What ROM are you talking about (extracting the boot.img)? I don't know what you mean by "the ROM you found". It needs to be a boot.img for a ROM that is compatible with Verizon version M8. Reason being, the Verizon version uses a different kernel from most other M8 versions.
redpoint73 said:
Maybe you've already somewhat figured this: But be aware, that messing with the MID on the Verizon (in your case LRA - Verizon variant) version, with intent to flash another version's firmware or RUU is a bad idea. It caused the radio problem you witnessed. Usually fixable with the Verizon (LRA) RUU, but we've also seen permanent radio bricks from flashing wrong firmware/RUU to the Verizon (LRA) M8. So consider yourself lucky.
Simply put, the CDMA versions of the M8 (Verizon/LRA and Sprint) are peculiar, in that they are not compatible with firmware from other M8 versions. And a radio brick (possibly permanent) may result. So only the respective firmware/RUU (in you case Verizon/LRA) should ever be installed.
---------- Post added at 10:26 AM ---------- Previous post was at 10:20 AM ----------
What ROM are you talking about (extracting the boot.img)? I don't know what you mean by "the ROM you found". It needs to be a boot.img for a ROM that is compatible with Verizon version M8. Reason being, the Verizon version uses a different kernel from most other M8 versions.
Click to expand...
Click to collapse
Hi Redpoint73, thanks for your reply. I did learn the "soft" way that MID and cross-platform firmware upgrades are a bad idea in general. I was lucky to not do permanent damage to my phone, and I know now better than to mess with that stuff.
Regarding the boot.img I mention, I was referencing user ckpv5's response to a question I posted in another thread. It was my bad for not linking to it: https://forum.xda-developers.com/showthread.php?t=2694917&page=3102
In essence, there's a Custom ROM I really wanted to try, Android Revolution HD 53.1, and since my particular device is not supported by the ROM, both users ckpv5 and Einwod suggested that I found a ROM with a kernel compatible to my device, and that I flashed said kernel immediately after flashing the ARHD ROM. Since I did manage to flash a stock RUU on my phone, I was asking if I could extract the kernel from that ZIP (https://www.androidfilehost.com/?fid=95916177934538677) to use in that procedure. I also realize now that this may be better suited for the ROM's specific thread, so my apologies for that as well.
Thank you all for helping me. Cheers!
Zombielicious said:
Now comes the last part, where I want to push my luck once again (unless you recommend me not to, but at least if I do it, it would be with proper guidance): if I wanted to install the ARHD ROM, you mentioned I needed to flash a Verizon-compatible firmware immediately after flashing the custom ROM. Do I have to extract the "boot.img" file from the ROM I found to accomplish that?
Click to expand...
Click to collapse
1. You need to use htc_fastboot to install RUU.zip. In the link I provided above there is another link in it that tell 3 different method to install RUU. Since you already solved data problem, keep that LRA RUU is a safe place.
2. You're lucky because you didn't flash a GSM firmware but CDMA firmware. GSM firmware may permanently brick the radio. AFAIK the reason why your data was not working is because of rcdata (radio config) from MM firmware is not compatible with your LRA device. It's good to know a Lollipop Verizon can fix it.
3. I cannot guarantee this will work. I don't have anyone to test. Since you have a working RUU which is Lollipop stock Verizon and also LRA RUU, if you want to, you can try this to install MM Verizon firmware.
a) If that's a signed firmware, you need to use 7-zip to extract it. Winrar won't work on a signed firmware. After you extract it, delete the rcdata.img, boot.img & recovery.img
b) Re-zip the firmware and flash that .. this will update your firmware to MM and the mobile data should work.
4. To install ARHD, you can't use the boot.img from Lollipop stock ROM or firmware. You need the MM boot.img, either get it from the extracted firmware or stock MM Verizon ROM (the one from 6.21.605.3_M8_WL_M60_SENSE70_VZW_MR_AROMA-FINAL.zip)
5. As now you're on Lollipop firmware, you can install any MM ROM without updating firmware to MM. Only KitKat firmware you will have some problem like wifi not working.
ckpv5 said:
1. You need to use htc_fastboot to install RUU.zip. In the link I provided above there is another link in it that tell 3 different method to install RUU. Since you already solved data problem, keep that LRA RUU is a safe place.
2. You're lucky because you didn't flash a GSM firmware but CDMA firmware. GSM firmware may permanently brick the radio. AFAIK the reason why your data was not working is because of rcdata (radio config) from MM firmware is not compatible with your LRA device. It's good to know a Lollipop Verizon can fix it.
3. I cannot guarantee this will work. I don't have anyone to test. Since you have a working RUU which is Lollipop stock Verizon and also LRA RUU, if you want to, you can try this to install MM Verizon firmware.
a) If that's a signed firmware, you need to use 7-zip to extract it. Winrar won't work on a signed firmware. After you extract it, delete the rcdata.img, boot.img & recovery.img
b) Re-zip the firmware and flash that .. this will update your firmware to MM and the mobile data should work.
4. To install ARHD, you can't use the boot.img from Lollipop stock ROM or firmware. You need the MM boot.img, either get it from the extracted firmware or stock MM Verizon ROM (the one from 6.21.605.3_M8_WL_M60_SENSE70_VZW_MR_AROMA-FINAL.zip)
5. As now you're on Lollipop firmware, you can install any MM ROM without updating firmware to MM. Only KitKat firmware you will have some problem like wifi not working.
Click to expand...
Click to collapse
Thank you very much for this information! The ROM (6.21.605.3_M8_WL_M60_SENSE70_VZW_MR_AROMA-FINAL.zip) actually worked, and I managed to install the ARHD custom ROM after that as well! Phone is now working! Cheers!
Zombielicious said:
the most rare: M8_WLV. I didn't know it at the time, but after trying many methods, I somehow managed to update the firmware to 6.21.605.3... which should not be possible, if what I've read since then is correct. I know I messed around with changing the MID and CID at some point (then reverted it).
Click to expand...
Click to collapse
How did you mange to revert MID??
Zombielicious said:
a ROM I found on another thread: DOTTAT_VZWM8_S_OFF_5.0.1_RUU.zip (https://www.androidfilehost.com/?fid=95916177934538677)
AND IT WORKED! After the process was done...
Click to expand...
Click to collapse
sending 'zip'... (1726320 KB) OKAY
sending time = 51.184 secs
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) total_image_number=23
(bootloader) start image[adsp] unzipping & flushing...
(bootloader) [RUU]UZ,adsp,0
(bootloader) [RUU]UZ,adsp,11
(bootloader) [RUU]UZ,adsp,22
(bootloader) [RUU]UZ,adsp,32
(bootloader) [RUU]UZ,adsp,43
(bootloader) [RUU]UZ,adsp,54
(bootloader) [RUU]UZ,adsp,65
(bootloader) [RUU]UZ,adsp,76
(bootloader) [RUU]UZ,adsp,87
(bootloader) [RUU]UZ,adsp,98
(bootloader) [RUU]UZ,adsp,100
(bootloader) [RUU]WP,adsp,0
(bootloader) [RUU]WP,adsp,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,12
(bootloader) [RUU]UZ,boot,24
(bootloader) [RUU]UZ,boot,38
(bootloader) [RUU]UZ,boot,51
(bootloader) [RUU]UZ,boot,61
(bootloader) [RUU]UZ,boot,73
(bootloader) [RUU]UZ,boot,86
(bootloader) [RUU]UZ,boot,97
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,99
(bootloader) [RUU]WP,boot,100
(bootloader) ...... Successful
(bootloader) current_image_number=1
(bootloader) start image[dzdata] unzipping & flushing...
(bootloader) [RUU]UZ,dzdata,0
(bootloader) [RUU]UZ,dzdata,6
(bootloader) [RUU]UZ,dzdata,14
(bootloader) [RUU]UZ,dzdata,21
(bootloader) [RUU]UZ,dzdata,31
(bootloader) [RUU]UZ,dzdata,39
(bootloader) [RUU]UZ,dzdata,45
(bootloader) [RUU]UZ,dzdata,50
(bootloader) [RUU]UZ,dzdata,57
(bootloader) [RUU]UZ,dzdata,62
(bootloader) [RUU]UZ,dzdata,69
(bootloader) [RUU]UZ,dzdata,76
(bootloader) [RUU]UZ,dzdata,82
(bootloader) [RUU]UZ,dzdata,88
(bootloader) [RUU]UZ,dzdata,95
(bootloader) [RUU]UZ,dzdata,100
(bootloader) [RUU]WP,dzdata,0
(bootloader) [RUU]WP,dzdata,7
(bootloader) [RUU]WP,dzdata,14
(bootloader) [RUU]WP,dzdata,23
(bootloader) [RUU]WP,dzdata,31
(bootloader) [RUU]WP,dzdata,39
(bootloader) [RUU]WP,dzdata,45
(bootloader) [RUU]WP,dzdata,51
(bootloader) [RUU]WP,dzdata,57
(bootloader) [RUU]WP,dzdata,62
(bootloader) [RUU]WP,dzdata,74
(bootloader) [RUU]WP,dzdata,79
(bootloader) [RUU]WP,dzdata,89
(bootloader) [RUU]WP,dzdata,95
(bootloader) [RUU]WP,dzdata,100
(bootloader) ...... Successful
(bootloader) current_image_number=2
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,50
(bootloader) [RUU]UZ,hboot,100
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) current_image_number=3
(bootloader) start image[pg2fs_spcustom] unzipping & flushing...
(bootloader) [RUU]UZ,pg2fs_spcustom,0
(bootloader) [RUU]UZ,pg2fs_spcustom,23
(bootloader) [RUU]UZ,pg2fs_spcustom,45
(bootloader) [RUU]UZ,pg2fs_spcustom,67
(bootloader) [RUU]UZ,pg2fs_spcustom,88
(bootloader) [RUU]UZ,pg2fs_spcustom,100
(bootloader) ...... Successful
(bootloader) current_image_number=4
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,7
(bootloader) [RUU]UZ,recovery,14
(bootloader) [RUU]UZ,recovery,26
(bootloader) [RUU]UZ,recovery,35
(bootloader) [RUU]UZ,recovery,49
(bootloader) [RUU]UZ,recovery,58
(bootloader) [RUU]UZ,recovery,64
(bootloader) [RUU]UZ,recovery,70
(bootloader) [RUU]UZ,recovery,75
(bootloader) [RUU]UZ,recovery,81
(bootloader) [RUU]UZ,recovery,87
(bootloader) [RUU]UZ,recovery,93
(bootloader) [RUU]UZ,recovery,99
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,93
(bootloader) [RUU]WP,recovery,99
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) current_image_number=5
(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) current_image_number=6
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1-1,0
(bootloader) [RUU]WP,sbl1-1,100
(bootloader) ...... Successful
(bootloader) current_image_number=7
(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) current_image_number=8
(bootloader) start image[sbl1-3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-3,0
(bootloader) [RUU]UZ,sbl1-3,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=9
(bootloader) start image[sbl1-4] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-4,0
(bootloader) [RUU]UZ,sbl1-4,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=10
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=11
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=12
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1,0
(bootloader) [RUU]WP,sbl1,100
(bootloader) ...... Successful
(bootloader) current_image_number=13
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=14
(bootloader) start image[sdi] unzipping & flushing...
(bootloader) [RUU]UZ,sdi,0
(bootloader) [RUU]UZ,sdi,100
(bootloader) [RUU]WP,sdi,0
(bootloader) [RUU]WP,sdi,100
(bootloader) ...... Successful
(bootloader) current_image_number=15
(bootloader) start image[sensor_hub] unzipping & flushing...
(bootloader) [RUU]UZ,sensor_hub,0
(bootloader) [RUU]UZ,sensor_hub,100
(bootloader) ...... Successful
(bootloader) current_image_number=16
(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) current_image_number=17
(bootloader) start image[system] unzipping & flushing...
(bootloader) ...... Failed
(bootloader) current_image_number=18
(bootloader) start image[tp] unzipping & flushing...
(bootloader) [RUU]UZ,tp,0
(bootloader) [RUU]UZ,tp,100
(bootloader) ..... Bypassed
(bootloader) current_image_number=19
(bootloader) start image[wcnss] unzipping & flushing...
(bootloader) [RUU]UZ,wcnss,0
(bootloader) [RUU]UZ,wcnss,24
(bootloader) [RUU]UZ,wcnss,45
(bootloader) [RUU]UZ,wcnss,69
(bootloader) [RUU]UZ,wcnss,92
(bootloader) [RUU]UZ,wcnss,100
(bootloader) [RUU]WP,wcnss,0
(bootloader) [RUU]WP,wcnss,100
(bootloader) ...... Successful
(bootloader) current_image_number=20
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,9
(bootloader) [RUU]UZ,radio,18
(bootloader) [RUU]UZ,radio,27
(bootloader) [RUU]UZ,radio,36
(bootloader) [RUU]UZ,radio,41
(bootloader) [RUU]UZ,radio,50
(bootloader) [RUU]UZ,radio,59
(bootloader) [RUU]UZ,radio,68
(bootloader) [RUU]UZ,radio,73
(bootloader) [RUU]UZ,radio,82
(bootloader) [RUU]UZ,radio,91
(bootloader) [RUU]UZ,radio,100
(bootloader) trying to rename MBA
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,36
(bootloader) [RUU]WP,radio,72
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) current_image_number=21
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,100
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,100
(bootloader) ...... Successful
(bootloader) current_image_number=22
FAIL54 image size is too large
FAILED (remote: 54 image size is too large)
Execution time is 83(s)
This is what i get. What should i do for FAILED (remote: 54 image size is too large) error
Happyfox15 said:
sending 'zip'... (1726320 KB) OKAY
sending time = 51.184 secs
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) total_image_number=23
(bootloader) start image[adsp] unzipping & flushing...
(bootloader) [RUU]UZ,adsp,0
(bootloader) [RUU]UZ,adsp,11
(bootloader) [RUU]UZ,adsp,22
(bootloader) [RUU]UZ,adsp,32
(bootloader) [RUU]UZ,adsp,43
(bootloader) [RUU]UZ,adsp,54
(bootloader) [RUU]UZ,adsp,65
(bootloader) [RUU]UZ,adsp,76
(bootloader) [RUU]UZ,adsp,87
(bootloader) [RUU]UZ,adsp,98
(bootloader) [RUU]UZ,adsp,100
(bootloader) [RUU]WP,adsp,0
(bootloader) [RUU]WP,adsp,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,12
(bootloader) [RUU]UZ,boot,24
(bootloader) [RUU]UZ,boot,38
(bootloader) [RUU]UZ,boot,51
(bootloader) [RUU]UZ,boot,61
(bootloader) [RUU]UZ,boot,73
(bootloader) [RUU]UZ,boot,86
(bootloader) [RUU]UZ,boot,97
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,99
(bootloader) [RUU]WP,boot,100
(bootloader) ...... Successful
(bootloader) current_image_number=1
(bootloader) start image[dzdata] unzipping & flushing...
(bootloader) [RUU]UZ,dzdata,0
(bootloader) [RUU]UZ,dzdata,6
(bootloader) [RUU]UZ,dzdata,14
(bootloader) [RUU]UZ,dzdata,21
(bootloader) [RUU]UZ,dzdata,31
(bootloader) [RUU]UZ,dzdata,39
(bootloader) [RUU]UZ,dzdata,45
(bootloader) [RUU]UZ,dzdata,50
(bootloader) [RUU]UZ,dzdata,57
(bootloader) [RUU]UZ,dzdata,62
(bootloader) [RUU]UZ,dzdata,69
(bootloader) [RUU]UZ,dzdata,76
(bootloader) [RUU]UZ,dzdata,82
(bootloader) [RUU]UZ,dzdata,88
(bootloader) [RUU]UZ,dzdata,95
(bootloader) [RUU]UZ,dzdata,100
(bootloader) [RUU]WP,dzdata,0
(bootloader) [RUU]WP,dzdata,7
(bootloader) [RUU]WP,dzdata,14
(bootloader) [RUU]WP,dzdata,23
(bootloader) [RUU]WP,dzdata,31
(bootloader) [RUU]WP,dzdata,39
(bootloader) [RUU]WP,dzdata,45
(bootloader) [RUU]WP,dzdata,51
(bootloader) [RUU]WP,dzdata,57
(bootloader) [RUU]WP,dzdata,62
(bootloader) [RUU]WP,dzdata,74
(bootloader) [RUU]WP,dzdata,79
(bootloader) [RUU]WP,dzdata,89
(bootloader) [RUU]WP,dzdata,95
(bootloader) [RUU]WP,dzdata,100
(bootloader) ...... Successful
(bootloader) current_image_number=2
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,50
(bootloader) [RUU]UZ,hboot,100
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) current_image_number=3
(bootloader) start image[pg2fs_spcustom] unzipping & flushing...
(bootloader) [RUU]UZ,pg2fs_spcustom,0
(bootloader) [RUU]UZ,pg2fs_spcustom,23
(bootloader) [RUU]UZ,pg2fs_spcustom,45
(bootloader) [RUU]UZ,pg2fs_spcustom,67
(bootloader) [RUU]UZ,pg2fs_spcustom,88
(bootloader) [RUU]UZ,pg2fs_spcustom,100
(bootloader) ...... Successful
(bootloader) current_image_number=4
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,7
(bootloader) [RUU]UZ,recovery,14
(bootloader) [RUU]UZ,recovery,26
(bootloader) [RUU]UZ,recovery,35
(bootloader) [RUU]UZ,recovery,49
(bootloader) [RUU]UZ,recovery,58
(bootloader) [RUU]UZ,recovery,64
(bootloader) [RUU]UZ,recovery,70
(bootloader) [RUU]UZ,recovery,75
(bootloader) [RUU]UZ,recovery,81
(bootloader) [RUU]UZ,recovery,87
(bootloader) [RUU]UZ,recovery,93
(bootloader) [RUU]UZ,recovery,99
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,93
(bootloader) [RUU]WP,recovery,99
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) current_image_number=5
(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) current_image_number=6
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1-1,0
(bootloader) [RUU]WP,sbl1-1,100
(bootloader) ...... Successful
(bootloader) current_image_number=7
(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) current_image_number=8
(bootloader) start image[sbl1-3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-3,0
(bootloader) [RUU]UZ,sbl1-3,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=9
(bootloader) start image[sbl1-4] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-4,0
(bootloader) [RUU]UZ,sbl1-4,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=10
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=11
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=12
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1,0
(bootloader) [RUU]WP,sbl1,100
(bootloader) ...... Successful
(bootloader) current_image_number=13
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=14
(bootloader) start image[sdi] unzipping & flushing...
(bootloader) [RUU]UZ,sdi,0
(bootloader) [RUU]UZ,sdi,100
(bootloader) [RUU]WP,sdi,0
(bootloader) [RUU]WP,sdi,100
(bootloader) ...... Successful
(bootloader) current_image_number=15
(bootloader) start image[sensor_hub] unzipping & flushing...
(bootloader) [RUU]UZ,sensor_hub,0
(bootloader) [RUU]UZ,sensor_hub,100
(bootloader) ...... Successful
(bootloader) current_image_number=16
(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) current_image_number=17
(bootloader) start image[system] unzipping & flushing...
(bootloader) ...... Failed
(bootloader) current_image_number=18
(bootloader) start image[tp] unzipping & flushing...
(bootloader) [RUU]UZ,tp,0
(bootloader) [RUU]UZ,tp,100
(bootloader) ..... Bypassed
(bootloader) current_image_number=19
(bootloader) start image[wcnss] unzipping & flushing...
(bootloader) [RUU]UZ,wcnss,0
(bootloader) [RUU]UZ,wcnss,24
(bootloader) [RUU]UZ,wcnss,45
(bootloader) [RUU]UZ,wcnss,69
(bootloader) [RUU]UZ,wcnss,92
(bootloader) [RUU]UZ,wcnss,100
(bootloader) [RUU]WP,wcnss,0
(bootloader) [RUU]WP,wcnss,100
(bootloader) ...... Successful
(bootloader) current_image_number=20
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,9
(bootloader) [RUU]UZ,radio,18
(bootloader) [RUU]UZ,radio,27
(bootloader) [RUU]UZ,radio,36
(bootloader) [RUU]UZ,radio,41
(bootloader) [RUU]UZ,radio,50
(bootloader) [RUU]UZ,radio,59
(bootloader) [RUU]UZ,radio,68
(bootloader) [RUU]UZ,radio,73
(bootloader) [RUU]UZ,radio,82
(bootloader) [RUU]UZ,radio,91
(bootloader) [RUU]UZ,radio,100
(bootloader) trying to rename MBA
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,36
(bootloader) [RUU]WP,radio,72
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) current_image_number=21
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,100
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,100
(bootloader) ...... Successful
(bootloader) current_image_number=22
FAIL54 image size is too large
FAILED (remote: 54 image size is too large)
Execution time is 83(s)
This is what i get. What should i do for FAILED (remote: 54 image size is too large) error
Click to expand...
Click to collapse
You need to either use HTC's fastboot or the SD card method. Regular fastboot doesn't work with larger files like RUUs. The easiest is the SD card method:
Rename the RUU.zip to 0P6BIMG, put it onto the root of your extSD, boot to bootloader and follow the on-screen prompts.
xunholyx said:
You need to either use HTC's fastboot or the SD card method. Regular fastboot doesn't work with larger files like RUUs. The easiest is the SD card method:
Rename the RUU.zip to 0P6BIMG, put it onto the root of your extSD, boot to bootloader and follow the on-screen prompts.
Click to expand...
Click to collapse
I tried both of methods sir but it's not working. Even sd card method is saying image size is too large...
Happyfox15 said:
I tried both of methods sir but it's not working. Even sd card method is saying image size is too large...
Click to expand...
Click to collapse
Not clear what your main problem is (or was to begin with). What did you do to the phone, what is the current state, etc.? Describe in detail, step by step, with as much specific info as possible.
It seems you changed your MID (based on a previous response above) but changed it to what? Did you flash firmware for another MID (very dangerous on the Verizon version M8, which you have).
Also, do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see current details about the device.
redpoint73 said:
Not clear what your main problem is (or was to begin with). What did you do to the phone, what is the current state, etc.?
It seems you changed your MID (based on a previous response above) but changed it to what? Did you flash firmware for another MID (very dangerous on the Verizon version M8, which you have).
Do fastboot getvar all, and post the results (delete IMEI and serial number).
Click to expand...
Click to collapse
Yes i did flash the firmware based on this treadhttps://forum.xda-developers.com/htc-one-m8/development/guide-htc-one-m8-to-developer-edition-t3331854 and M8 start to stuck at htc logo. Recently i flashed the ruu and the firmware that mentioned by Zombielicious in #3 post but still M8 stuck at the htc logo. here's the getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.12.20.1211
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.17.605.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000429272904
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: f2489bd1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 39(ms)
(in bootloader os shows like this OS-4.17.605.5 (4.17.605.5), i also changed the ruu mid to 0P6B12000 to match with mine, also when i tried sd card method system is show like this SYSTEM-FAIL-SC)
will i still able to fix this or is this already a brick???
You can try the other Verizon RUUs from here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Do not try firmware or RUU from any other versions. Doing so may cause permanent damage (radio brick). Sometimes the radio brick can be reversed by flashing old Verizon version RUU. But not always.
Guide to change back to Verizon MID here: https://forum.xda-developers.com/showthread.php?t=2708581
redpoint73 said:
You can try the other Verizon RUUs from here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Click to expand...
Click to collapse
i already tried that ruu sir. (lollipop version)
Happyfox15 said:
i already tried that ruu sir. (lollipop version)
Click to expand...
Click to collapse
There are at least 4 different RUUs posted on the link I provided.
If you tried one of the RUUs in the link I provided, you never said so (the one in Post #3 is a hacked RUU, not a signed one).
I can't help you if you don't give complete details on what you've done so far.
---------- Post added at 11:54 AM ---------- Previous post was at 11:48 AM ----------
Hold on. You have the LRE version, not the "regular" Verizon version.
I only know this by looking at another post you made to a different thread: https://forum.xda-developers.com/showpost.php?p=78280918&postcount=191
Only RUUs for LRE (version numbers x.xxx.512.x
ckpv5 already linked you to LRE version RUUs. If they don't work, you are out of luck, and the phone is probably bricked.
This is a perfect example of why you should be making multiple posts in different threads, or creating multiple threads.
Stick to one thread, and give all the relevant details. For one thing, the fact yours is a "512" LRE version is extremely important, and not mentioned at all in this thread!!!!
redpoint73 said:
ckpv5 already linked you to LRE version RUUs. If they don't work, you are out of luck, and the phone is probably bricked.
Click to expand...
Click to collapse
the ruu ckpv5 linked download size is 1.36gb but when i extract it using 7zip or winrar it only depressed to 11mb and its only got 6 files. i think the uploaded file was corrupted. ( i downloaded it 2 times but same result)
(also sorry again for make same question in multiple treads)
Happyfox15 said:
the ruu ckpv5 linked download size is 1.36gb but when i extract it using 7zip or winrar it only depressed to 11mb and its only got 6 files. i think the uploaded file was corrupted.
Click to expand...
Click to collapse
You've got it all mixed up. Nowhere in any instructions, will you see it says to extract anything from the zip. The RUU zips are typically encrypted, and trying to extract anything from it will not work. Nor does the install process involve extracting the zip.
Flash the zip with SD card method or htc_fastboot.
The fact you do not understand this, makes me very skeptical that you tried the mentioned methods, as you claimed previously in this thread (Post #11 above).
---------- Post added at 12:36 PM ---------- Previous post was at 12:28 PM ----------
Also, in your reply to ckvp5, does it say anything like what you said here (you tried to extract the zip). You only mentioned "my phone is now not starting" which implies that this occurred after you flashed the RUU (when clearly you didn't).
https://forum.xda-developers.com/showpost.php?p=78297405&postcount=195
Seriously, your posting patter is extremely confusing. Hopping around different threads, posting incomplete, even misleading info. Not sure how you expect anyone to be able help under these conditions????
redpoint73 said:
You've got it all mixed up. Nowhere in any instructions, will you see it says to extract anything from the zip. The RUU zips are typically encrypted, and trying to extract anything from it will not work. Nor does the install process involve extracting the zip.
Flash the zip with SD card method or htc_fastboot.
The fact you do not understand this, makes me very skeptical that you tried the mentioned methods, as you claimed previously in this thread (Post #11 above).
---------- Post added at 12:36 PM ---------- Previous post was at 12:28 PM ----------
Also, in your reply to ckvp5, does it say anything like what you said here (you tried to extract the zip). You only mentioned "my phone is now not starting" which implies that this occurred after you flashed the RUU (when clearly you didn't).
https://forum.xda-developers.com/showpost.php?p=78297405&postcount=195
Seriously, your posting patter is extremely confusing. Hopping around different threads, posting incomplete, even misleading info. Not sure how you expect anyone to be able help under these conditions????
Click to expand...
Click to collapse
No no man i already tried that ruu without extracting, i extracted it becuase i wanted to change mid from android info in that zip file. I also tried after changing the mid but it's not working
(Can you say method to change mid without adb.exe because i can't enable usb debugging)
Happyfox15 said:
No no man i already tried that ruu without extracting, i extracted it becuase i wanted to change mid from android info in that zip file. I also tried after changing the mid but it's not working
(Can you say method to change mid without adb.exe because i can't enable usb debugging)
Click to expand...
Click to collapse
If I recall properly, you can run adb while booted to TWRP custom recovery.
So you can try to flash TWRP (easy, as long as the bootloader is unlocked), boot into TWRP, and you should be able to run the adb commands.
I've never hacked the RUUs to change the MID in the RUU itself. I've seen folks do it. But I don't know if it works on encrypted/signed RUUs.
My opinion, it's best your device be changed back to the correct MID, anyway.