I may have broken my M8_WLV?

Zombielicious · Aug 25, 2017

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:

My current info:

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.

ckpv5 · Aug 25, 2017 at 6:35 AM

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.

Zombielicious · Aug 24, 2017 9 1 0

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.

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!

redpoint73 · Aug 25, 2017

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

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?

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.

Zombielicious · Aug 24, 2017 9 1 0

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.

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!

ckpv5 · Aug 25, 2017

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?

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.

Zombielicious · Aug 24, 2017 9 1 0

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.

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!

Happyfox15 · Nov 28, 2018 23 0 0

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

How did you mange to revert MID??

Happyfox15 · Nov 28, 2018 23 0 0

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

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

xunholyx · Dec 1, 2018 at 4:35 PM

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

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.

Happyfox15 · Nov 28, 2018 23 0 0

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.

I tried both of methods sir but it's not working. Even sd card method is saying image size is too large...

redpoint73 · Dec 4, 2018

Happyfox15 said:
I tried both of methods sir but it's not working. Even sd card method is saying image size is too large...

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.

Happyfox15 · Nov 28, 2018 23 0 0

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

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

redpoint73 · Dec 4, 2018 at 4:39 PM

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

Happyfox15 · Nov 28, 2018 23 0 0

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

i already tried that ruu sir. (lollipop version)

redpoint73 · Dec 4, 2018 at 4:54 PM

Happyfox15 said:
i already tried that ruu sir. (lollipop version)

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

Happyfox15 · Nov 28, 2018 23 0 0

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.

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)

redpoint73 · Dec 4, 2018 at 5:36 PM

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.

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

Happyfox15 · Dec 4, 2018

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

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)

redpoint73 · Dec 5, 2018 at 3:51 PM

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)

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.

I may have broken my M8_WLV?

Member

Recognized Contributor

Member

Recognized Contributor

Member

Recognized Contributor

Member

Member

Member

Recognized Contributor

Member

Recognized Contributor

Member

Recognized Contributor

Member

Recognized Contributor

Member

Recognized Contributor

Member

Recognized Contributor