Develop Bugs

Please Help HTC One M8 Soft Bricked

Hello.i have HTC One M8.I install Sprint_HTC_One_M8_Harman_1.54.654.9_RUU but not finishing.giving me error code remote:41 model id check fail or ERROR 159 IMAGE ERROR
My Phone
Unlocked
M8-WHL PVT SHIP S-OFF
CID-11111111 HBOOT-3.16.0.0000
RADIO-1.16.2133156.UA15
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.54.401.10
Do you have friends who will help me in this regard

Did you find a solution to this problem?
murattari said:
Hello.i have HTC One M8.I install Sprint_HTC_One_M8_Harman_1.54.654.9_RUU but not finishing.giving me error code remote:41 model id check fail or ERROR 159 IMAGE ERROR
My Phone
Unlocked
M8-WHL PVT SHIP S-OFF
CID-11111111 HBOOT-3.16.0.0000
RADIO-1.16.2133156.UA15
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.54.401.10
Do you have friends who will help me in this regard
Click to expand...
Click to collapse
Hello Friend
Did you find a solution to this problem?

kh1led said:
Hello Friend
Did you find a solution to this problem?
Click to expand...
Click to collapse
You dug up a post from 9 months ago, that might not be your exact same issue.
The error messages imply that the wrong RUU is being run for the device. It needs to match your CID and MID. And if you are s-on, it has to be equal or more recent version RUU that was is installed on the phone (no "downgrading").
But you haven't stated what version (CID, MID) of the M8 you have, what RUU you are trying to run, and whether you are s-on or s-off.

HELP
Hello
first thank you for reply
i tried to flash "Android_Revolution_HD-One_M8_34.6_3703c7.zip" and its work but sometimes the device is restarting
and when i used "RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_Harman_4.20.654.10_Radio_1.09.20.0119_NV_SPCS_1.52_003_release_418492_signed_2.exe" its frozen at logo HTC on background black
and when i tried to flash by adb i get Z:\>fastboot oem writecid 11111111
... INFOStart Verify: 0
INFOInput CID is super CID
INFOStart Verify: 0
OKAY [ 0.029s]
finished. total time: 0.030s
Z:\>fastboot oem rebootRUU
... INFOStart Verify: 0
OKAY [ 0.022s]
finished. total time: 0.022s
Z:\>fastboot flash zip C:\Users\khaleds\Desktop\HTC\SPRINT\M8\firmware.zip
sending 'zip' (164729 KB)... OKAY [ 6.563s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 6.766s
Z:\>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 3.19.0.0000
INFOversion-baseband: 1.25.214500021.06G
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 4.16.401.10
INFOversion-misc: PVT SHIP S-OFF
INFOserialno: HT442S
INFOimei: 9900
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: m8_whl
INFOplatform: hTCBmsm8974
INFOmodelid: 0P6B10000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 3aa067db
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.047s

Did you modify your MID (model number)? Your product number (m8_whl) is right for Sprint, but the MID is for Europe GSM version (0P6B10000).
RUU is failing due to wrong MID.
To verify, you do have the Sprint version?

redpoint73 said:
Did you modify your MID (model number)? Your product number (m8_whl) is right for Sprint, but the MID is for Europe GSM version (0P6B10000).
RUU is failing due to wrong MID.
To verify, you do have the Sprint version?
Click to expand...
Click to collapse
As I already told him in the sticky Q&A, he most probably bought a second hand, already S-OFF phone., super CID.
m8_whl is sprint edition, regular one and is CDMA and he probably tried first to flash a GSM rom (ARHD doesn't support CDMA) and that RUU is for 4.20.654.10 (sprint) and you need one for 4.16.401.10 (international), and that is why the RUU failed. You or someone messed with this phone
He need a sprint recovery and a sprint rom and best bet is to go to sprint m8 forum.

TempestZ said:
and that RUU is for 4.20.654.10 (sprint) and you need one for 4.16.401.10 (international)
Click to expand...
Click to collapse
I follow what you are saying, with exception of this line. OP has Sprint version, so I believe he can flash RUU for either "regular" or HK editions with s-off (according to the Sprint RUU thread here). I don't see how the international RUU figures in, and he certainly should not install that.
It also seems the MID was changed to be the "international" MID, either by him or previous owner. Nothing good can come from this, so he should change back to Sprint MID.

redpoint73 said:
I follow what you are saying, with exception of this line. OP has Sprint version, so I believe he can flash RUU for either "regular" or HK editions with s-off (according to the Sprint RUU thread here). I don't see how the international RUU figures in, and he certainly should not install that.
It also seems the MID was changed to be the "international" MID, either by him or previous owner. Nothing good can come from this, so he should change back to Sprint MID.
Click to expand...
Click to collapse
Poor choice of words, was trying to explain that this is why the RUU failed. In fact, I think he bought the phone with 401 flashed already. Sprint firmware should be flashed, then just go with the usuall recovery and roms

TempestZ said:
Poor choice of words, was trying to explain that this is why the RUU failed. In fact, I think he bought the phone with 401 flashed already. Sprint firmware should be flashed, then just go with the usuall recovery and roms
Click to expand...
Click to collapse
I think you are right, the previous owner probably tried to flash 401 firmware. Its the only reason (albeit a very ill-advised one) I can see to change to the "international" MID.

[Q] TMOUS M8 accepted GPE hboot 3.18 - Am I busted?

It's been a long and wild ride, but I think my device is toasted.. sorta.
I unlocked via HTCDev, installed TWRP, rooted. All went well.
Wanted to test GPE ROM. Downloaded and installed 4.4.3.
It had an OTA. Flashed stock recovery to apply it. BAD MOVE!
Ever since, my white hboot is now black, says version 3.18. This is the GPE hboot.
Trying to manually write a new one with dd fails obviously, read only.
RUU fails, saying error 159 (Wrong RUU for this device. It isnt?)
RUU flashing hboot, "unknown error 99" - assuming because S-On.
Firewater s-off FAILED before this happened, because my device just wasn't compatible with it.
Now running the GPE hboot I tried it again, and it just force closes and kicks me back to a terminal after typing in "Yes"
Only AOSP based ROMs are booting now.
TWRP (Multiple versions) as well as PhilZ CWM both fail on most other roms with "set_perm: some changes failed"
And then kick me to a 2-3 bootloop back into recovery.
What are my options? Thanks guys.
Code:
(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: SUREWHYNOT
(bootloader) imei: YESSIR
(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

xHighAlert said:
It's been a long and wild ride, but I think my device is toasted.. sorta.
I unlocked via HTCDev, installed TWRP, rooted. All went well.
Wanted to test GPE ROM. Downloaded and installed 4.4.3.
It had an OTA. Flashed stock recovery to apply it. BAD MOVE!
Ever since, my white hboot is now black, says version 3.18. This is the GPE hboot.
Trying to manually write a new one with dd fails obviously, read only.
RUU fails, saying error 159 (Wrong RUU for this device. It isnt?)
RUU flashing hboot, "unknown error 99" - assuming because S-On.
Firewater s-off FAILED before this happened, because my device just wasn't compatible with it.
Now running the GPE hboot I tried it again, and it just force closes and kicks me back to a terminal after typing in "Yes"
Only AOSP based ROMs are booting now.
TWRP (Multiple versions) as well as PhilZ CWM both fail on most other roms with "set_perm: some changes failed"
And then kick me to a 2-3 bootloop back into recovery.
What are my options? Thanks guys.
Click to expand...
Click to collapse
You cant ruu because your CID is wrong you should supercid by doing ...
"fastboot oem readcid". Make a note of your original CID.
Then do
"fastboot oem writecid 11111111"
Not including parenthesis. Then try the ruu

iRunLinux said:
You cant ruu because your CID is wrong you should supercid by doing ...
"fastboot oem readcid". Make a note of your original CID.
Then do
"fastboot oem writecid 11111111"
Not including parenthesis. Then try the ruu
Click to expand...
Click to collapse
Reminder that I am S-On. All S-Off methods fail for me.
While in RebootRUU:
Code:
C:\Users\Cody\Desktop\ADB Fastboot>fastboot oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.001s]
finished. total time: 0.001s
C:\Users\Cody\Desktop\ADB Fastboot>fastboot oem writecid 11111111
...
(bootloader) SecuritySDInit: counter = 1
(bootloader) m8_init_sd, SD card already power on
(bootloader) [SPEW] GPIO 0 status is 1
(bootloader) [SD_ERR] No sd card inserted!
(bootloader) usb_hw_init
FAILED (status read failed (Too many links))
finished. total time: 0.053s
While in regular fastboot:
Code:
C:\Users\Cody\Desktop\ADB Fastboot>fastboot oem writecid 11111111
...
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
OKAY [ 0.002s]
finished. total time: 0.002s

xHighAlert said:
Reminder that I am S-On. All S-Off methods fail for me.
While in RebootRUU:
Code:
C:\Users\Cody\Desktop\ADB Fastboot>fastboot oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.001s]
finished. total time: 0.001s
C:\Users\Cody\Desktop\ADB Fastboot>fastboot oem writecid 11111111
...
(bootloader) SecuritySDInit: counter = 1
(bootloader) m8_init_sd, SD card already power on
(bootloader) [SPEW] GPIO 0 status is 1
(bootloader) [SD_ERR] No sd card inserted!
(bootloader) usb_hw_init
FAILED (status read failed (Too many links))
finished. total time: 0.053s
While in regular fastboot:
Code:
C:\Users\Cody\Desktop\ADB Fastboot>fastboot oem writecid 11111111
...
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
OKAY [ 0.002s]
finished. total time: 0.002s
Click to expand...
Click to collapse
Personally i would try to s-off u said firewater doesnt work but id just try sunshine s-off it costs money but its worth it.

iRunLinux said:
Personally i would try to s-off u said firewater doesnt work but id just try sunshine s-off it costs money but its worth it.
Click to expand...
Click to collapse
Sunshine wants you to get as close to stock as possible.
I'm running the wrong hboot, and can only boot AOSP roms.
But okay I'll give it a spin.

xHighAlert said:
Sunshine wants you to get as close to stock as possible.
I'm running the wrong hboot, and can only boot AOSP roms.
But okay I'll give it a spin.
Click to expand...
Click to collapse
Use the same method in which u flashed the black hboot to flash the stock hboot
---------- Post added at 03:47 AM ---------- Previous post was at 03:42 AM ----------
xHighAlert said:
Sunshine wants you to get as close to stock as possible.
I'm running the wrong hboot, and can only boot AOSP roms.
But okay I'll give it a spin.
Click to expand...
Click to collapse
And if not try flashing gpe stock rooted rom which should boot since your still using that firmware, then try and s-off with sunshine.

I'm in pretty much the same circumstance. Tried going GPE - installed GPE ROM, flashed GPE Recovery to get the 4.4.4 update and now neither GPE nor Sense Roms will install or boot. I had S-Off before, but I think the GPE Recovery put security back on and now I'm back to S-On.
I've tried GPE, Stock Sense, and custom Recoveries and Firmware - nothing is working... I'm stuck running CM11 at the moment.
If only there was an S-Off method that would actually work under CM.

[Q] Firmware issues on HTC one m8

Hi guys,
I've just updated my android rev 10.1 to 30.1 but it's stuck in a reboot cycle. Could be because I didn't update the firmware? Still on the older 3.x firmware.
So trying to update firmware - I have the 3.28.401.9 zip in my sdcards root folder but trying to install from zip (TWRP 2.8) it says unable to open zip file, error flashing.
If I try using fastboot flash:
C:\>fastboot flash zip c:\3.28.401.9.zip
sending 'zip' (43011 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
FAILED (remote: not allowed)
Key bits of information from my fastboot getvar shows something not right:
C:\>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 3.16.0.0000
INFOversion-baseband: 1.16.2133156.UA15G
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: xxxxxxxx
INFOimei: xxxxxxxxx
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: m8_ul
INFOplatform: hTCBmsm8974
INFOmodelid: 0P6B10000
INFOcidnum: O2___001
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: ab0efa49
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
Whats scary is that it doesn't even show my firmware version?! my phone is unlocked with htcdev - shows "unlocked" and "tampered" so I don't picture s-on is an issue.
Any suggestions on how to unbrick?

chamelion said:
Hi guys,
I've just updated my android rev 10.1 to 30.1 but it's stuck in a reboot cycle. Could be because I didn't update the firmware? Still on the older 3.x firmware.
So trying to update firmware - I have the 3.28.401.9 zip in my sdcards root folder but trying to install from zip (TWRP 2.8) it says unable to open zip file, error flashing.
If I try using fastboot flash:
C:\>fastboot flash zip c:\3.28.401.9.zip
sending 'zip' (43011 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
FAILED (remote: not allowed)
Key bits of information from my fastboot getvar shows something not right:
C:\>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 3.16.0.0000
INFOversion-baseband: 1.16.2133156.UA15G
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: xxxxxxxx
INFOimei: xxxxxxxxx
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: m8_ul
INFOplatform: hTCBmsm8974
INFOmodelid: 0P6B10000
INFOcidnum: O2___001
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: ab0efa49
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
Whats scary is that it doesn't even show my firmware version?! my phone is unlocked with htcdev - shows "unlocked" and "tampered" so I don't picture s-on is an issue.
Any suggestions on how to unbrick?
Click to expand...
Click to collapse
You can't flash firmware via recovery!
Search for vomers firmware thread all instructions are there.

You need an 02 firmware. The wwe ones don't work on your phone. And to flash firmwares you need to be in RUU mode.
But look for your official firmware first. Or return the phone to its original stock rom + recovery and update via official ota's

Thanks! So I had tried to flash via RUU mode but it had errored - presumably cause it rejected the ROM file.
My initial firmware update when I updated to rev10.1 from stock android was from vomer's guide. Should I be downloading 4.16.1540.8 without red text?

chamelion said:
Thanks! So I had tried to flash via RUU mode but it had errored - presumably cause it rejected the ROM file.
My initial firmware update when I updated to rev10.1 from stock android was from vomer's guide. Should I be downloading 4.16.1540.8 without red text?
Click to expand...
Click to collapse
basically this is what I get if I Try to flash the above in RUU mode:
C:\>fastboot flash zip c:\fw_4.16.1540.8_custom_without_red_text.zip
sending 'zip' (29494 KB)... OKAY
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)

You can not flash those firmwares on your device. The steps you are taking are all wrong !

Mr Hofs said:
You can not flash those firmwares on your device. The steps you are taking are all wrong !
Click to expand...
Click to collapse
Which one can I flash
I found http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One_M8/206/
but that's from 2008 and can't be right for an M8...
sorry to be such a bother - really am in a horrible spot and would really appreciate your help.

Anyone? Please?

Go to the general section and look for the stock backup thread. Have a real good read there and return your phone to FULL stock and update via ota.

This one is the latest O2 firmware: https://www.androidfilehost.com/?fid=95784891001603798
You cant install the Lollipop dev edition firmware when you are on the O2 cid. So or het s-off and change it or wait for OTA from O2.
Latest aviable stock backup: https://mega.co.nz/#F!odoimZRD!fXWN36-1i3AUdkAHcgfy_A

Petert87 said:
This one is the latest O2 firmware: https://www.androidfilehost.com/?fid=95784891001603798
You cant install the Lollipop dev edition firmware when you are on the O2 cid. So or het s-off and change it or wait for OTA from O2.
Latest aviable stock backup: https://mega.co.nz/#F!odoimZRD!fXWN36-1i3AUdkAHcgfy_A
Click to expand...
Click to collapse
yep latest o2 firmware didn't work either
sending 'zip' (52330 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
I'm going to try reverting back to the old version of android rev that I had and see if my phone gets out the reboot loop. If so I'll probably revisit flashing at some later point when I'm less frustrated, ideally first s-off my phone.
if that still doesn't work I'll probably have to return to stock

chamelion said:
yep latest o2 firmware didn't work either
sending 'zip' (52330 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
I'm going to try reverting back to the old version of android rev that I had and see if my phone gets out the reboot loop. If so I'll probably revisit flashing at some later point when I'm less frustrated, ideally first s-off my phone.
if that still doesn't work I'll probably have to return to stock
Click to expand...
Click to collapse
Maybe your firmware is newer then the link I gave. But with the O2 cid you cant use lollipop with sense. You cant Flash that firmware. So you have to go back on stock.
Verstuurd van mijn HTC One_M8

im with s-on
cidnum:HTC__K18
when im trying to flash the new firmware im getting this
C:\android-sdk-windows\platform-tools>fastboot flash zip firmware.zip
target reported max download size of 1826414592 bytes
sending 'zip' (29494 KB)...
OKAY [ 2.342s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.841s
any idea whats wrong ??

Petert87 said:
Maybe your firmware is newer then the link I gave. But with the O2 cid you cant use lollipop with sense. You cant Flash that firmware. So you have to go back on stock.
Verstuurd van mijn HTC One_M8
Click to expand...
Click to collapse
ah that sucks. ah well.
So to go back on stock, I wan tto use the "Method 2 - flashing RUU (ROM Update Utility)" method. It's not entirely clear on how to do this - do I download the stock recovery 1.54.2016.5 img and folder onto my pc and issue fastboot oem lock command? or does the folder go on the sdcard and the img on my computer? or neither??

chamelion said:
ah that sucks. ah well.
So to go back on stock, I wan tto use the "Method 2 - flashing RUU (ROM Update Utility)" method. It's not entirely clear on how to do this - do I download the stock recovery 1.54.2016.5 img and folder onto my pc and issue fastboot oem lock command? or does the folder go on the sdcard and the img on my computer? or neither??
Click to expand...
Click to collapse
Ah man really? What do you dont understand?
If you want to use that RUU to have that developer update to Lollipop you have to change the O2 cid. If you want to change the cid you have to be s-off. Are you not? Use sunshine.
Verstuurd van mijn HTC One_M8

resolved my issue:
- went back to android rev 11.1 (what i was previously using) and wiped device.
- once booted, installed sunshine and went s-off
- updated cid to supercid
- updated firmware to latest 4.x
- updated and wiped into andrdoid rev 30.1
Working like a charm now
Thanks everyone for the massive help!

chamelion said:
resolved my issue:
- went back to android rev 11.1 (what i was previously using) and wiped device.
- once booted, installed sunshine and went s-off
- updated cid to supercid
- updated firmware to latest 4.x
- updated and wiped into andrdoid rev 30.1
Working like a charm now
Thanks everyone for the massive help!
Click to expand...
Click to collapse
Glad to hear! Hope the $25 for sunshine was worth it
Verstuurd van mijn HTC One_M8

Petert87 said:
Glad to hear! Hope the $25 for sunshine was worth it
Verstuurd van mijn HTC One_M8
Click to expand...
Click to collapse
it's a lot of money for what it is, but to be fair $25 for having a working phone that I can now flash as I like and is now running lollipop was worth it!

chamelion said:
it's a lot of money for what it is, but to be fair $25 for having a working phone that I can now flash as I like and is now running lollipop was worth it!
Click to expand...
Click to collapse
I know and respect the work the sunshine team does. But normally Vodafone is quick with updates
Verstuurd van mijn HTC One_M8

Htc one X At&t Cid problém help me pliiiizz

help me to find a solution on my htc one x at&t
when i try to change cid from 12345678 that i 'v allready change it befor just to try now i can't change it to super cid or original cid
on my CMD
i rooted my phone and i have S-on
ofurtunatly lost system
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

Need STOCK 6.0 ROM for HTC One M8.. No Software Upgrade Option Available

I have HTC One M8 (M8_UL) (2nd Hand). I don't know whether it is genuine or not.
Android: 4.4.4
HTC Sense Version: 6.0
Software Number: 3.28.401.9
HTC SDK API Level: 6.25
CID-11111111
HBOOT-3.19.0.0000
KTU48P Release Keys
Recovery: Stock 3.28.401.9
Rooted
I want Stock Android 6.0 but there is no option to get Software Upgrade. I have tried RUU.exe but it failed.. Please help me. Country: Pakistan

Salman Akbar said:
I have HTC One M8 (M8_UL) (2nd Hand). I don't know whether it is genuine or not.
Android: 4.4.4
HTC Sense Version: 6.0
Software Number: 3.28.401.9
HTC SDK API Level: 6.25
CID-11111111
HBOOT-3.19.0.0000
KTU48P Release Keys
Recovery: Stock 3.28.401.9
Rooted
I want Stock Android 6.0 but there is no option to get Software Upgrade. I have tried RUU.exe but it failed.. Please help me. Country: Pakistan
Click to expand...
Click to collapse
What error message did you get when trying the RUU?
Is your software number from settings > about? What does it say next to "OS" in bootloader? Or alternatively, what do you get with fastboot getvar version-main?

Says that "get the correct ROM Update Utility for your device".
my model id is OP6B63000 and OS is 3.28.401.9

Salman Akbar said:
Says that "get the correct ROM Update Utility for your device".
my model id is OP6B63000 and OS is 3.28.401.9
Click to expand...
Click to collapse
help me please

Salman Akbar said:
Says that "get the correct ROM Update Utility for your device".
my model id is OP6B63000 and OS is 3.28.401.9
Click to expand...
Click to collapse
You can't just run any RUU, it has to be intended for your device's specific MID and CID.
You also have not stated what exact version number RUU you tried to run.
You haven't been clear about how you are determining the model ID (MID) or OS number.
How did you determine the MID? How did you determine the OS number?
Best way is fastboot getvar all
In fact, it's best to perform the command, and post the results (delete IMEI and serial number before posting).

I have tried to install v6.12.1540.4 (.exe) downloaded from the HTC website.
I have got this info through "fastboot getvar all" method

Salman Akbar said:
help me please
Click to expand...
Click to collapse
I'd like to help, but you need to reply/quote me so I get a notification.
---------- Post added at 09:16 AM ---------- Previous post was at 09:15 AM ----------
Salman Akbar said:
I have tried to install v6.12.1540.4 (.exe) downloaded from the HTC website.
I have got this info through "fastboot getvar all" method
Click to expand...
Click to collapse
Your getvar information is missing from this post

xunholyx said:
I'd like to help, but you need to reply/quote me so I get a notification.
---------- Post added at 09:16 AM ---------- Previous post was at 09:15 AM ----------
Your getvar information is missing from this post
Click to expand...
Click to collapse
version-microp: None
version-main: 3.28.401.9
version-misc: PVT SHIP S-OFF
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B63000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: df77f8b7
hbootpreupdate: 11
gencheckpt: 0

xunholyx said:
I'd like to help, but you need to reply/quote me so I get a notification.
---------- Post added at 09:16 AM ---------- Previous post was at 09:15 AM ----------
Your getvar information is missing from this post
Click to expand...
Click to collapse
Is this information enough.?

Salman Akbar said:
Is this information enough.?
Click to expand...
Click to collapse
Your MID is for the Asia version M8, while your current firmware is for Euro version.
So which stock 6.0 ROM (Asia or Euro) to install is somewhat up to you. But if it's working on the current Euro firmware, you might want to stick with Euro (flashing another region RUU will change network band support).
If you want to stay on Euro ROM, use the RUU and instructions here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Otherwise, if you want the Asia ROM, use the RUU zip for here (but use the same process with htc_fastboot as the previous method - just with the following RUU zip): https://forum.xda-developers.com/showpost.php?p=70983904&postcount=7616

redpoint73 said:
Your MID is for the Asia version M8, while your current firmware is for Euro version.
So which stock 6.0 ROM (Asia or Euro) to install is somewhat up to you. But if it's working on the current Euro firmware, you might want to stick with Euro (flashing another region RUU will change network band support).
If you want to stay on Euro ROM, use the RUU and instructions here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Otherwise, if you want the Asia ROM, use the RUU zip for here (but use the same process with htc_fastboot as the previous method - just with the following RUU zip): https://forum.xda-developers.com/showpost.php?p=70983904&postcount=7616
Click to expand...
Click to collapse
Ok I have downloaded the EURO version and I will try to flash it with the given method..
1 more question: Can I install this "RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe" on my device???
version-microp: None
version-main: 3.28.401.9
version-misc: PVT SHIP S-OFF
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B63000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: df77f8b7
hbootpreupdate: 11
gencheckpt: 0

redpoint73 said:
Your MID is for the Asia version M8, while your current firmware is for Euro version.
So which stock 6.0 ROM (Asia or Euro) to install is somewhat up to you. But if it's working on the current Euro firmware, you might want to stick with Euro (flashing another region RUU will change network band support).
If you want to stay on Euro ROM, use the RUU and instructions here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Otherwise, if you want the Asia ROM, use the RUU zip for here (but use the same process with htc_fastboot as the previous method - just with the following RUU zip): https://forum.xda-developers.com/showpost.php?p=70983904&postcount=7616
Click to expand...
Click to collapse
I opened command prompt from RUU folder (shift+right click) and typed this: " fastboot reboot-bootloader " (without quotations) but it says that: 'fastboot' is not recognized as internal or external command, operable program or batch file.
What to be done now?

Salman Akbar said:
I opened command prompt from RUU folder (shift+right click) and typed this: " fastboot reboot-bootloader " (without quotations) but it says that: 'fastboot' is not recognized as internal or external command, operable program or batch file.
What to be done now?
Click to expand...
Click to collapse
Try adb reboot-bootloader
You have to be in bootloader for fastboot commands to work. If you are booted to your system/ROM, then adb comands apply

xunholyx said:
Try adb reboot-bootloader
You have to be in bootloader for fastboot commands to work. If you are booted to your system/ROM, then adb comands apply
Click to expand...
Click to collapse
Ok this problem is solved.. now another problem:
-----------------------------------------------------------
E:\RUU>htc_fastboot flash zip RUU.zip
sending 'zip'... (53965 KB) OKAY
sending time = 2.832 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 3(s)
E:\RUU>
-----------------------------------------------------------

Reply please.. would I have to change the Model ID.??

Salman Akbar said:
Ok this problem is solved.. now another problem:
-----------------------------------------------------------
E:\RUU>htc_fastboot flash zip RUU.zip
sending 'zip'... (53965 KB) OKAY
sending time = 2.832 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 3(s)
E:\RUU>
-----------------------------------------------------------
Click to expand...
Click to collapse
I tried to flash the Euro version RUU.zip that was recommended by redpoind73 but it failed "FAIL41"

Salman Akbar said:
Reply please.. would I have to change the Model ID.??
Click to expand...
Click to collapse
With s-off and superCID you shouldn't have to.
What RUU are you trying to flash? Maybe give a link to where you downloaded it from.

xunholyx said:
With s-off and superCID you shouldn't have to.
What RUU are you trying to flash? Maybe give a link to where you downloaded it from.
Click to expand...
Click to collapse
The Guide:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
The download link:
https://www.androidfilehost.com/?fid=24369303960687057

Salman Akbar said:
The Guide:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
The download link:
https://www.androidfilehost.com/?fid=24369303960687057
Click to expand...
Click to collapse
My bootloader is RELOCKED. Should I UNLOCK it?

Salman Akbar said:
My bootloader is RELOCKED. Should I UNLOCK it?
Click to expand...
Click to collapse
This won't help the RUU to run. Unlocked bootloader would actually prevent the RUU from installing on a s-on device. Since your phone is s-off, it bypasses that limitation, so it doesn't matter either way (RELOCKED, LOCKED or UNLOCKED) and the RUU will still install if other requirements are met.
You probably need to change the MID. SuperCID usually bypasses the MID check, but not always. This appears to be one of the instances.