Develop Bugs

[Q] [URGENT] Hanged on Bootloader what to do

Hi,
I just became stupid again. I got my phone hanged upped on BOOTLOADER. after trying "fastboot oem writecid HTC__044"
i got this message.
(bootloader) elite_init_sd, SD card already power on
(bootloader) sdhw_7xxx_open: id=0
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) 902910 902E20
FAILED (status read failed (No such file or directory))
finished. total time: 1.273s
I noticed its hanging now, I did this with unlocked bootloader
how do i know if this is still workable? how can I get out of the bootloader. I promise not to do anything stupid If i get passed after this :crying:

You can't write a cid on a s-on hox !
Post the outcome of :
Fastboot getvar version-main
Sent from my HTC One X using XDA Premium 4 mobile app

Tmo Htc One M8 error 12 "Remote Signature verify failed"

I am fixing a TMO Htc One M8 for a friend. He currently has TWRP recovery but nothing will wipe or flash. I have posted the get var information and the log below along with all the steps I've taken, please share any insight into the matter.
Here is the Get VAR Information. I have tried to fix this device by relocking the Bootloader, flashing stock RUU RUU_M8_TMOUS_1.57.531.7 , Flashing modified firmware.zip, flashing recovery.img, nothing. Then unlocking the bootloader, flashing Philz recovery.img, Twrp.img, still same error. Current TWRP recovery registers nothing but errors. No wiping data, cache, system, etc. No installing backup nandroid, no flashing new rom through external SD card or adb sideload. Literally the phone won't flash anything and the error is error 12, "Remote signature verifiey failed" What kinda insight do you have into this? Anyway to get back to stock?
Thanks!
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA446WM02874
(bootloader) imei: 352628060329457
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
LOG: D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash TMOUS-M8-1.12.53
1.19.recovery.img
sending 'flash' (24576 KB)...
OKAY [ 1.691s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.953s
D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash philz_touch_6.48
.4-m8.img
sending 'flash' (14436 KB)...
OKAY [ 1.467s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.293s
D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash T_Mo_1.57.531.7_
recovery.img
sending 'flash' (24576 KB)...
OKAY [ 1.688s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.753s
D:\All Android Devices\T Mobile HTC One M8>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.132s

twill1987 said:
I am fixing a TMO Htc One M8 for a friend. He currently has TWRP recovery but nothing will wipe or flash. I have posted the get var information and the log below along with all the steps I've taken, please share any insight into the matter.
Here is the Get VAR Information. I have tried to fix this device by relocking the Bootloader, flashing stock RUU RUU_M8_TMOUS_1.57.531.7 , Flashing modified firmware.zip, flashing recovery.img, nothing. Then unlocking the bootloader, flashing Philz recovery.img, Twrp.img, still same error. Current TWRP recovery registers nothing but errors. No wiping data, cache, system, etc. No installing backup nandroid, no flashing new rom through external SD card or adb sideload. Literally the phone won't flash anything and the error is error 12, "Remote signature verifiey failed" What kinda insight do you have into this? Anyway to get back to stock?
Thanks!
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA446WM02874
(bootloader) imei: 352628060329457
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
LOG: D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash TMOUS-M8-1.12.53
1.19.recovery.img
sending 'flash' (24576 KB)...
OKAY [ 1.691s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.953s
D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash philz_touch_6.48
.4-m8.img
sending 'flash' (14436 KB)...
OKAY [ 1.467s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.293s
D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash T_Mo_1.57.531.7_
recovery.img
sending 'flash' (24576 KB)...
OKAY [ 1.688s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.753s
D:\All Android Devices\T Mobile HTC One M8>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.132s
Click to expand...
Click to collapse
okay I'm wondering why the bootloader is 3.18. I just converted my T-Mobile HTC one m8 to dev edition and that's what my bootloader is now.
That device must have been s-off before if it has the 3.18 bootloader. the problem is now you're s-on with the wrong bootloader in the phone. So it's not gonna verify something it can't. U need to unlock the bootloader then try to s-off again. Let me know if u need more help

twinnfamous said:
okay I'm wondering why the bootloader is 3.18. I just converted my T-Mobile HTC one m8 to dev edition and that's what my bootloader is now.
That device must have been s-off before if it has the 3.18 bootloader. the problem is now you're s-on with the wrong bootloader in the phone. So it's not gonna verify something it can't. U need to unlock the bootloader then try to s-off again. Let me know if u need more help
Click to expand...
Click to collapse
Yes, I think the device was S-off before was well. But how can I get the device S-off when I can't load any rom to establish an internet connection?
There's no way to get back to stock, or get an internet connection through the device to obtain S-off. I can unlock the boot-loader,
I've done that a few times, but how to get S-Off when the only two screens I can access are the bootloader and twrp? When bootloader is unlocked. I have used firewater before for S-off and it requires active internet connection on device.
Thanks again for helping

twill1987 said:
Yes, I think the device was S-off before was well. But how can I get the device S-off when I can't load any rom to establish an internet connection?
There's no way to get back to stock, or get an internet connection through the device to obtain S-off. I can unlock the boot-loader,
I've done that a few times, but how to get S-Off when the only two screens I can access are the bootloader and twrp? When bootloader is unlocked. I have used firewater before for S-off and it requires active internet connection on device.
Thanks again for helping
Click to expand...
Click to collapse
Unlock bootloader try to flash the latest open twrp recovery and try to install another Rom or backup. If you can see the roms in the sdcard then you should be able to flash the roms or backup.
If there was a way to get into adb YOU would be able to s-off again.

twinnfamous said:
Unlock bootloader try to flash the latest open twrp recovery and try to install another Rom or backup. If you can see the roms in the sdcard then you should be able to flash the roms or backup.
If there was a way to get into adb YOU would be able to s-off again.
Click to expand...
Click to collapse
I've tried to flash TWRP but I get that error. I tried to flash the newest twrp but it wouldn't flash.
I think the system is no longer mounted, that's why I get this error :"E: Unable to mount 'data'" and "E: Unable to mount internal storage"

twill1987 said:
I've tried to flash TWRP but I get that error. I tried to flash the newest twrp but it wouldn't flash.
I think the system is no longer mounted, that's why I get this error :"E: Unable to mount 'data'" and "E: Unable to mount internal storage"
Click to expand...
Click to collapse
Is there any option in recovery to format? if so have u tried to format each partition manually?
Then try and see if it will flash. Just need something to boot so you can s-off .
You need to get s-off again so you can flash a ruu with lower hboot if formatting doesn't work or you can try to flash the new 4.4.3 ruu when it becomes available. They said the ota should be out on the 11th.
I'll keep looking for ways to s-off without adb .

Well first your doing the wrong command. Its fastboot flash recovery recovery.img, not fastboot flash flash recovery.img.

x714x said:
Well first your doing the wrong command. Its fastboot flash recovery recovery.img, not fastboot flash flash recovery.img.
Click to expand...
Click to collapse
Yes, that was a typo. Every fastboot flash ends with error 12. Remote Signature.
I have tried literally everything with this device. Tried flashing new TWRP, Radio, Firmware, Etc. Nothing works.
Inside TWRP everything finishes with "failed" or "E: Unable to mount cache"
I tried to select cache under the mount in TWRP and it's greyed out. I fastboot erase cache, and it is literally
the only thing that worked for me. But still no way to restore previous Android. Tried flashing stock RUU's for 4.4.2 and 4.4.3, no dice.
Both RUU's get to 6 percent and then say failed. I'm wondering if the device thinks it's a different phone possibly a GPE edition so it won't
go back to stock? Just a thought. I have unlocked, and relocked the bootloader a million times trying different methods as well, not
sure what else there is to do next. This might be the end of the road for this customers phone.

twinnfamous said:
Is there any option in recovery to format? if so have u tried to format each partition manually?
Then try and see if it will flash. Just need something to boot so you can s-off .
You need to get s-off again so you can flash a ruu with lower hboot if formatting doesn't work or you can try to flash the new 4.4.3 ruu when it becomes available. They said the ota should be out on the 11th.
I'll keep looking for ways to s-off without adb .
Click to expand...
Click to collapse
Yes, that was a typo. Every fastboot flash ends with error 12. Remote Signature.
I have tried literally everything with this device. Tried flashing new TWRP, Radio, Firmware, Etc. Nothing works.
Inside TWRP everything finishes with "failed" or "E: Unable to mount cache"
I tried to select cache under the mount in TWRP and it's greyed out. I fastboot erase cache, and it is literally
the only thing that worked for me. But still no way to restore previous Android. Tried flashing stock RUU's for 4.4.2 and 4.4.3, no dice.
Both RUU's get to 6 percent and then say failed. I'm wondering if the device thinks it's a different phone possibly a GPE edition so it won't
go back to stock? Just a thought. I have unlocked, and relocked the bootloader a million times trying different methods as well, not
sure what else there is to do next. This might be the end of the road for this customers phone.

twinnfamous said:
Is there any option in recovery to format? if so have u tried to format each partition manually?
Then try and see if it will flash. Just need something to boot so you can s-off .
You need to get s-off again so you can flash a ruu with lower hboot if formatting doesn't work or you can try to flash the new 4.4.3 ruu when it becomes available. They said the ota should be out on the 11th.
I'll keep looking for ways to s-off without adb .
Click to expand...
Click to collapse
Under TWRP the only option is to format data. I formatted, but it did nothing that I'm aware of.

twill1987 said:
Under TWRP the only option is to format data. I formatted, but it did nothing that I'm aware of.
Click to expand...
Click to collapse
I just tried to reformat data again and it says same error in TWRP E: Cannot mount cache
I am able to flash Viper Rom though, but because it is S ON the rom won't boot past start up screen.
What a bizarre issue

twill1987 said:
Under TWRP the only option is to format data. I formatted, but it did nothing that I'm aware of.
Click to expand...
Click to collapse
There should be a way now that the new T-Mobile update to flash ruu if we can find one.
Edit: found one
http://www.htcdev.com/devcenter/downloads/P00
Just select T-Mobile as carrier and USA as region then you Wil see the latest ruu to download.

twinnfamous said:
There should be a way now that the new T-Mobile update to flash ruu if we can find one.
Click to expand...
Click to collapse
I flashed the 4.4.3 RUU update at HTCDEV.com It failed at the 6 percent mark. http://www.htcdev.com/devcenter/downloads

twill1987 said:
I just tried to reformat data again and it says same error in TWRP E: Cannot mount cache
I am able to flash Viper Rom though, but because it is S ON the rom won't boot past start up screen.
What a bizarre issue
Click to expand...
Click to collapse
the latest viper is from New firmware base so it takes 15 to 20 minutes to boot. Have you waited that long?
---------- Post added at 10:27 PM ---------- Previous post was at 10:24 PM ----------
twill1987 said:
I flashed the 4.4.3 RUU update at HTCDEV.com It failed at the 6 percent mark. http://www.htcdev.com/devcenter/downloads
Click to expand...
Click to collapse
Sorry it seems I'm getting posts in different orders.
Flash viper and wait 15 to 20 minutes. And we can go from there.
I'm pretty sure we can get this resolved.

twinnfamous said:
the latest viper is from New firmware base so it takes 15 to 20 minutes to boot. Have you waited that long?
---------- Post added at 10:27 PM ---------- Previous post was at 10:24 PM ----------
Sorry it seems I'm getting posts in different orders.
Flash viper and wait 15 to 20 minutes. And we can go from there.
I'm pretty sure we can get this resolved.
Click to expand...
Click to collapse
I'll try to flash the latest Viper. The 1.6.0 it says everything flashed correctly, but gets stuck at the HTC boot screen.
I just flashed the 1.8.0 OTA update and everything installs but it sticks at the boot screen.
I see the 2.2.0 update is out so I'm downloading that now, I'll flash and see how it goes.
I'll update, thanks for your help!

Ruu requires the bootloader be locked
Sent from my HTC One_M8 using XDA Free mobile app

Danger can't change my CID overwroted

hello i can't change ma cid overwroted from supercid to 12345678 just for trayin
now i'am stuck i can't change no more pliiiz what i can do for it
this what it tell 's me on CMD
C:\Users\houssam\Desktop\htc>fastboot oem writecid CWS__001
...
(bootloader) elite_init_sd, SD card already power on
(bootloader) sdhw_7xxx_open: id=0
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) 902910 902E20
FAILED (status read failed (No such file or directory))
finished. total time: 1.266s

HTC One M8 stuck in bootloader

I've got this phone for a while now but since i updated it to official marsmallow it's been stuck into bootloader. The phone is stock, still locked and S-ON. I've tried to unlock it so i can use a custom rom but when i do the official bootloader unlock from htc it goes all okay until it should promp me on the phone screen to confirm bootloader unlock, i can't find a way to make it work. I also tried to use the RUU but when it's rebooting my phone into bootloader (witch it is already) it doesn't reboot the phone goes stand by and the program stops. I the tried to get the zip RUU into an SD but the CID doesn't match since i got the Vodafone UK one so my cid is VODAP001 and i can't find the right RUU for this version. Can someome please help, i'm desperate.
I've tried to use the RUU.zip file from cmd using comand fastboot oem rebootRUU bur it gives me this message:
...
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.058s]
finished. total time: 10.058s

BlackMambo90 said:
I've got this phone for a while now but since i updated it to official marsmallow it's been stuck into bootloader. The phone is stock, still locked and S-ON. I've tried to unlock it so i can use a custom rom but when i do the official bootloader unlock from htc it goes all okay until it should promp me on the phone screen to confirm bootloader unlock, i can't find a way to make it work. I also tried to use the RUU but when it's rebooting my phone into bootloader (witch it is already) it doesn't reboot the phone goes stand by and the program stops. I the tried to get the zip RUU into an SD but the CID doesn't match since i got the Vodafone UK one so my cid is VODAP001 and i can't find the right RUU for this version. Can someome please help, i'm desperate.
I've tried to use the RUU.zip file from cmd using comand fastboot oem rebootRUU bur it gives me this message:
...
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.058s]
finished. total time: 10.058s
Click to expand...
Click to collapse
same issue here
did you find the solution?

skierr said:
same issue here
did you find the solution?
Click to expand...
Click to collapse
Yeah I had to send it to support since it had a hardware problem with the memory ( I've pinpointed the problem to the ROM) if you your warranty is expired maybe you should try replacing the motherboard

skierr said:
same issue here
did you find the solution?
Click to expand...
Click to collapse
You have the same sector/emmc errors? Of you just have the problem of stuck in bootloader? Those are two very different things. With the second one being quite possibly fixable.
You need to be specific if you want any meaningful help. Saying you have the "same issue" is never sufficient for folks to give help; and is just going to end up confusing you and others.
Assuming it is not a hardware emmc failure, and you want some direction, please provide the following:
- If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
- If you don't know how to do fastboot, what OS number and radio number does it say on the phone's bootloader screen?
- Bootloader locked or unlocked?
- Any other mods (TWRP, custom ROM, etc.).
- What events led to the current condition? Did you try to flash something, or update OS? Or just happened spontaneously?
- Exact names/version numbers of files you installed, or tried to flash.
The more detail you can give, the better.

[SOLVED] Need some help update my phone from 5.0.1 to 6.0

Hi.
first off i have to say im completely new to this, and been googling all day for how to update my phone from 5.0.1 to 6.0 as it doesnt get it automatic but cant find what i feel is the right way for me. so i feel pretty stuck
this far i figure i most likely have an asian modell of m8, would like to upgrade it so i later on will get automatic updates (if it will ever be more coming for this one )
so as a noob i need some help on how to solve this issue
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.708.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: **************
(bootloader) imei: **************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

you can update it using RUU.zip
however you have s-off device which is heavily modified ( supercid,dev ed or t mobile mid and Asian firmware )
so if you want t update the current firmware then
downoad this RUU
https://mega.nz/#!nQUTEQgS!705whK7tyPvtUgUQwLenweGTJepoHQDeBgsiHhrYVlQ
and follow this instruction to flash it
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
start from "2. Download htc_fastboot.exe" all the steps and files before this step is not for you
p.s backup your files before flashing as the RUU will wipe your internal storage

that didnt work to well, tryed several times (even with different usb ports, same result)
C:\htc>htc_fastboot.exe flash zip RUU.zip
sending 'zip'... (53966 KB) OKAY
sending time = 3.056 secs
writing 'zip'... (bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
Execution time is 3(s)

rmhalvorsen said:
that didnt work to well, tryed several times (even with different usb ports, same result)
C:\htc>htc_fastboot.exe flash zip RUU.zip
sending 'zip'... (53966 KB) OKAY
sending time = 3.056 secs
writing 'zip'... (bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
Execution time is 3(s)
Click to expand...
Click to collapse
try the other method to flash the RUU
rename the RUU to 0P6BIMG.zip then put it in sd card ( formatted as fat32 ) and reboot to bootloader ( hboot )
it will scan for the file and asks to flash it just confirm
let's see how this goes

uhm, nope thats not working eighter
cant see/mount card when booted normally eighter

rmhalvorsen said:
uhm, nope thats not working eighter
cant see/mount card when booted normally eighter
Click to expand...
Click to collapse
try to flash this firmware first ( flash using the same commands i the earlier guide i linked above )
https://mega.nz/#!bMpgkRrY!74hn2pGPKaX6aQhNDchSany6JmRtROm-zeozzhoSWac
note: if you are not on the stock rom/kernel flashing the firmware will wipe the os so you will need to flash the firmware then flash the RUU
after flash the firmware with success reboot to bootloader then reboot to RUU mode and flash the RUU again
if you see this error “Error 90 hboot pre-update..." repeat the flashing command again immediately

Failed
C:\htc>htc_fastboot flash zip fw_6.16.708.1.zip
sending 'zip'... (53849 KB) OKAY
sending time = 3.025 secs
writing 'zip'... (bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAIL41 model id check fail
FAILED (remote: 41 model id check fail)
Execution time is 4(s)

rmhalvorsen said:
Failed
C:\htc>htc_fastboot flash zip fw_6.16.708.1.zip
sending 'zip'... (53849 KB) OKAY
sending time = 3.025 secs
writing 'zip'... (bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAIL41 model id check fail
FAILED (remote: 41 model id check fail)
Execution time is 4(s)
Click to expand...
Click to collapse
that's because your mid is 0P6B13000 and cid supercid
the right mid for this firmware is 0P6B63000 and cid HTC__622
you have tow options
1- flash the developer edition marshmallow firmware and RRU.exe
2-change the MID to 0P6B63000 and flash the asian firmware/RUU again
your choice and i think both options are valid for you
option 1
flash this firmware https://mega.nz/#!iZJHDKZK!wKL6TkHz8u5eXA6HfhUfgPDdfeTcCZMxygc9Mm_GGg8
then reboot to bootloader and run this RUU.exe from your pc as a normal app http://www.htc.com/us/support/htc-one-m8/news/
direct link for the RUU.exe
http://dl3.htc.com/application/RUU_...2.1540.4.exe?_ga=1.5739063.5870829.1473114560
option 2
change the mid to 0P6B63000
reboot to twrp ( flash it if you don't yet ) and connect your device to pc
type this 4 commands in cmd window ( press enter after each command )
adb shell
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x36\x00\x33\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
the above command is very sensitive and long command just copy and paste it not write it your self
exit
adb reboot bootloader
then flash the firmware again and followed by the RUU
source for change mid https://forum.xda-developers.com/showthread.php?t=2708581
your mid command isn't available in this thread i edited a close one to be valid for 0P6B63000 ( i'm not an expert )
and i recommend you to choose option 1 ( any way it's your choice following my own command or use the most trusted option 1 )

flash firmware was sucessful.
but the ruu.exe loads up and i accept the terms and hit next, then the app just dies/quits, only thing i see is that languagebar icon flashes when this happends
im running genuine windows 7 64bit, does it need to be runned in a compability mode of some sort ?

rmhalvorsen said:
flash firmware was sucessful.
but the ruu.exe loads up and i accept the terms and hit next, then the app just dies/quits, only thing i see is that languagebar icon flashes when this happends
im running genuine windows 7 64bit, does it need to be runned in a compability mode of some sort ?
Click to expand...
Click to collapse
Try again with RUU and if possible reboot both devices ( pc and phone )
try with another usb port
Windows 7 is the most compatible os to run the RUU so try again
Sent from my HTC M8 using XDA Labs

still a no go, tried all 4 availible usb ports and rebooted between them all, downloaded ruu once more . still app just dies when i accept and hit next

now i have tried from another two computers, with just the same result, ruu.exe dies upon accepting terms and hitting next.

rmhalvorsen said:
now i have tried from another two computers, with just the same result, ruu.exe dies upon accepting terms and hitting next.
Click to expand...
Click to collapse
you are missing some libraries
download and install this
https://www.microsoft.com/en-us/download/details.aspx?id=26368
then run the RUU again

there it goes, worked perfectly and now up and running updated
thanks a lot for your time struggeling with my noobyness, would not have get this done right without you.
atleast now i know what to do next time i buy a new phone on ebay
just one last question, if i now go into meny or hboot and do factory reset, will it restores it to current flashed image again or mess things up? just so i dont mess this up in a year or so, if things starts to hang up

rmhalvorsen said:
there it goes, worked perfectly and now up and running updated
thanks a lot for your time struggeling with my noobyness, would not have get this done right without you.
Click to expand...
Click to collapse
there is a button for that
rmhalvorsen said:
just one last question, if i now go into meny or hboot and do factory reset, will it restores it to current flashed image again or mess things up? just so i dont mess this up in a year or so, if things starts to hang up
Click to expand...
Click to collapse
no worry you are on complete stock state anytime you will make a factory reset it will just wipe the user data
but no need for that now as it already wiped everything on the device :good:

Good to know
Guess this thread can me marked as SOLVED! :good:

rmhalvorsen said:
Guess this thread can me marked as SOLVED! :good:
Click to expand...
Click to collapse
If you like, you can do that yourself, by going to the top post and editing the thread title to add [SOLVED].
The mods don't go around looking for threads to mark as solved.

will it be possible to flash my phone with this one ? 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
.zip
maybe im wrong but i think maybe this would be my solution to get lte/4g working for telenor norway, as it wont connect to other then gprs/hspa now.
??

rmhalvorsen said:
will it be possible to flash my phone with this one ? 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
.zip
maybe im wrong but i think maybe this would be my solution to get lte/4g working for telenor norway, as it wont connect to other then gprs/hspa now.
??
Click to expand...
Click to collapse
Looks like you already answered this question yourself based on the thread you started here: https://forum.xda-developers.com/htc-one-m8/help/help-to-change-radio-basebands-htc-one-t3582804
Please try to avoid bouncing around to different threads. Or at a minimum, if you answer your own question, go back and post what the solution was, so folks don't waste time trying to help you with a question which was already self answered.

noted edited this to solved
well, can atleast say that the rom worked on my phone....(but did not solve the problem in my other thread.)