Develop Bugs

[SOLVED] - [Q] Htc m8 Wifi wont turn on.

Hi to all, recently i got my m8 but wifi wont turn on at all. I got soff, unlocked by htcdev, rooted and arhd rom and elemental kernel.
I need help pls i read in a thread about flashing boot. Img for fixing my issue but im confused.

all-in said:
Hi to all, recently i got my m8 but wifi wont turn on at all. I got soff, unlocked by htcdev, rooted and arhd rom and elemental kernel.
I need help pls i read in a thread about flashing boot. Img for fixing my issue but im confused.
Click to expand...
Click to collapse
Check your firmware against your installed rom version - happens when firmware needs update

Htc
Forgot to mention that it wouldnt turn on since it came out the box.
Kernel - 3.4.0 elemental
Baseband - 1.19.21331147a1
Build numb - 3.28.401.9

Htc
Hboot - 3.18.0.0000
Radio- 1.19.21331147a1
Os - doesn't mention anything at all

all-in said:
Forgot to mention that it wouldnt turn on since it came out the box.
Kernel - 3.4.0 elemental
Baseband - 1.19.21331147a1
Build numb - 3.28.401.9
Click to expand...
Click to collapse
Yeah, that baseband is wrong against that 3.28.401.9, update firmware, should be 1.22.223.....

So which firmware you suggest, any link to download a zip to flash?
What about the os that is empty?

all-in said:
So which firmware you suggest, any link to download a zip to flash?
What about the os that is empty?
Click to expand...
Click to collapse
OS is blank because you got custom recovery, probably TWRP - flash firmware from within fastboot -- http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One_M8/401/3.28.401.9.zip

ill try this and let u know with what i came up.
i got a message : sending 'zip' (43011 KB)... OKAY [ 4.162s]
writing 'zip'... INFOadopting the signature contained in this image
FAILED (remote: not allowed)

all-in said:
ill try this and let u know with what i came up.
i got a message : sending 'zip' (43011 KB)... OKAY [ 4.162s]
writing 'zip'... INFOadopting the signature contained in this image
FAILED (remote: not allowed)
Click to expand...
Click to collapse
You gotta do - fastboot oem rebootRUU and only then execute the next command

fastboot oem rebootRUU command doesnt do anything so i booted in fastboot my own and this message came up. wana smash the phone on the wall. really omg.
target reported max download size of 1830612992 bytes
sending 'zip' (43011 KB)...
OKAY [ 2.599s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.858s

the baseband is still 1.19.21.....

is baseband = radio? cant get this to work.

soff
Ok what i need is s-off as i thought i had it. firewater doesnt work anymore as it mentiones in thread. there is sunshine method but it costs 25 dollars. lolz no way. is there another way to gain s off?

Im a bit confused . Please some help guys. I got s-on,does that mean i cant flash another firmware to get my wifi to work?

all-in said:
Im a bit confused . Please some help guys. I got s-on,does that mean i cant flash another firmware to get my wifi to work?
Click to expand...
Click to collapse
I would really recommend you S-Off your device, if you want to flash firmware
otherwise:
1- flash signed firmware incrementally, signed firmware expects previous updates to already be there, so if you skip directly to the last, you'll end up stuck with a high version firmware, but missing previous updates!!!!!!
2- you need to relock your bootloader, for fastboot oem rebootRUU mode flashes to work

Thanks for the response.
i tryed to s-off with firewater but i think this service has stopped?or does it still work as a method?
Device is s-on with unlocked bootloader. I read that with s-on u cant flash kernels-radios-baseband. Is radio equal to baseband? a guy in earlier post said that to get my wifi working i have to update the firmware. Exactly he said that baseband is wrong against that 3.28.401.9, update firmware, should be 1.22.223.
So how do i get that firmware + how i flash it + in what state should the device be?
thats what im asking

all-in said:
Thanks for the response.
i tryed to s-off with firewater but i think this service has stopped?or does it still work as a method?
Device is s-on with unlocked bootloader. I read that with s-on u cant flash kernels-radios-baseband. Is radio equal to baseband? a guy in earlier post said that to get my wifi working i have to update the firmware. Exactly he said that baseband is wrong against that 3.28.401.9, update firmware, should be 1.22.223.
So how do i get that firmware + how i flash it + in what state should the device be?
thats what im asking
Click to expand...
Click to collapse
hi, just a quick FYI, you need to quote (ie reply) or mention (for example @ nkk71 <- without the space) someone, for them to get notified ... otherwise it may go unnoticed.
anyway,
1- firewater is discontinued and in either case was not very suited for the M8 anyway, except for some of the very early models it would have failed. sunshine ($25) is the only known software solution for s-off
2- the response earlier about what you see in Settings->About (3.28.401.9) only refers to the version the ROM (not firmware) is based on
3- the firmware you get from a "fastboot getvar all" from version-main; if that's missing (a bug in some twrp versions), you can make an educated guess by looking at hboot version + radio + date in bootloader
4- radio is equal to baseband, but not equal to firmware.... firmware contains a lot more than just hboot and radio
5- with s-on, you can only flash signed firmwares (these are usually extracted from OTA.zips), and have to match your MID and CID... you also need to have bootloader relocked for RUU mode flash to work
^^ plus, since those are updates, they will only contain whatever was changed from the previous OTA update, that's why if you intend on staying s-on, you should flash those incrementally, and not skip a version
(for example, the "latest" signed firmware could just be an update to hboot or something, but missing all the previous radio, touchscreen, etc updates.... because and official update [by definition] implies all the previous updates were already installed)
hope that helps a bit

nkk71 said:
hi, just a quick FYI, you need to quote (ie reply) or mention (for example @ nkk71 <- without the space) someone, for them to get notified ... otherwise it may go unnoticed.
anyway,
1- firewater is discontinued and in either case was not very suited for the M8 anyway, except for some of the very early models it would have failed. sunshine ($25) is the only known software solution for s-off
2- the response earlier about what you see in Settings->About (3.28.401.9) only refers to the version the ROM (not firmware) is based on
3- the firmware you get from a "fastboot getvar all" from version-main; if that's missing (a bug in some twrp versions), you can make an educated guess by looking at hboot version + radio + date in bootloader
4- radio is equal to baseband, but not equal to firmware.... firmware contains a lot more than just hboot and radio
5- with s-on, you can only flash signed firmwares (these are usually extracted from OTA.zips), and have to match your MID and CID... you also need to have bootloader relocked for RUU mode flash to work
^^ plus, since those are updates, they will only contain whatever was changed from the previous OTA update, that's why if you intend on staying s-on, you should flash those incrementally, and not skip a version
(for example, the "latest" signed firmware could just be an update to hboot or something, but missing all the previous radio, touchscreen, etc updates.... because and official update [by definition] implies all the previous updates were already installed)
hope that helps a bit
Click to expand...
Click to collapse
Ok for start ill relock the device and i come back for further steps.i hope we can fix this.

all-in said:
Ok for start ill relock the device and i come back for further steps.i hope we can fix this.
Click to expand...
Click to collapse
i relocked my device.so what steps do i follow now?
any thread i should follow to get this updates step by step to reach the latest firware.
after some search on the forum i found these http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC%2FHTC_One_M8%2F which i think is the right step, but im confused in which folder should i pick and which firmware updates should i download and flash.
this is my getvar command layout :
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH4ADWM03441
(bootloader) imei: ----------------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__304
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

all-in said:
i relocked my device.so what steps do i follow now?
any thread i should follow to get this updates step by step to reach the latest firware.
after some search on the forum i found these http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC%2FHTC_One_M8%2F which i think is the right step, but im confused in which folder should i pick and which firmware updates should i download and flash.
this is my getvar command layout :
C:\adb>fastboot getvar all
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_ul
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__304
Click to expand...
Click to collapse
your hboot+baseband version would indicate you are either on 2.22.401.4 or .5 (minor difference)
you should flash in increasing order:
3.28.401.6.zip
3.28.401.7.zip
3.28.401.9.zip
from here: http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One_M8/401/
fastboot oem rebootRUU
fastboot flash zip 3.28.401.6.zip
fastboot flash zip 3.28.401.6.zip <- yes twice, make sure it says successful/finished
fastboot reboot-bootloader
once you are back in bootloader, make sure the OS- line has been updated to the version you flashed, and is not in red (if it is in red, that means the flash didnt complete properly)
then repeat the above commands for the 2 other firmwares
Note: the higher the firmware, the less chances of getting S-OFF, just to let you know

[Solved] Cannot install CM12 due to outdated bootloader

Hello.
I am currently running ParanoidAndroid 4.6Beta5. Since PA's developement for M8 seems to be dead, I wanted to try CM12.
When I tried to install latest nightly build of CM12 I got a message that my bootloader (3.16) is not supported, and that I need to update it to 3.18 or 3.19.
I googled a bit and found out that in order to update it, I need to restore latest official ROM.
I managed to restore official ROM (3.28.401.6, based on android 4.4.4) but the WiFi wasn't working, so I couldn't do much there. I relocked bootloader and flashed official recovery, and then tried to run RUU.
RUU failed with code [315]. I ran out of ideas and google results to browse.
I unlocked my bootloader again, flashed clockworkmod recovery back, and restored my backup of ParanoidAndroid.
Right now the phone is in the same state as when I was starting.
Here is some basic info about my phone:
Model: HTC ONE M8 16GB Unlocked (purchased on amazon; network free)
CID: HTC_001
Bootloader: Unlocked
Recovery: Clockworkmod Touch v6.0.4.8
S status: S-ON
Click to expand...
Click to collapse
So the basic question is: how to flash CM12 on HTC One M8? I spent so many hours on it without any result, so this thread is my last chance.
Edit: SOLVED!
See http://forum.xda-developers.com/showpost.php?p=58859881&postcount=13 for solution.

ProTofik said:
Hello.
I am currently running ParanoidAndroid 4.6Beta5. Since PA's developement for M8 seems to be dead, I wanted to try CM12.
When I tried to install latest nightly build of CM12 I got a message that my bootloader (3.16) is not supported, and that I need to update it to 3.18 or 3.19.
I googled a bit and found out that in order to update it, I need to restore latest official ROM.
I managed to restore official ROM (3.28.401.6, based on android 4.4.4) but the WiFi wasn't working, so I couldn't do much there. I relocked bootloader and flashed official recovery, and then tried to run RUU.
RUU failed with code [315]. I ran out of ideas and google results to browse.
I unlocked my bootloader again, flashed clockworkmod recovery back, and restored my backup of ParanoidAndroid.
Right now the phone is in the same state as when I was starting.
Here is some basic info about my phone:
So the basic question is: how to flash CM12 on HTC One M8? I spent so many hours on it without any result, so this thread is my last chance.
Click to expand...
Click to collapse
Since you are S-On, you can't just flash the firmware, which is the easiest way. But you can use this method.
I'll give you an RUU to flash. But before you flash it, backup everything that is important to you, because this will wipe your phone.
Download this.
Rename it to 0P6BIMG.zip (that's a zero not the letter)
Put it onto the root of your extSD (By root of I mean just on the card and not a folder)
Boot into bootloader and choose hboot.
Follow the prompts (vol up to flash, power button to reboot when done)
Congratulations! You now have the latest lollipop firmware.
Make sure you delete the renamed zip from your extSD when you are done. If you don't delete it, it will try to update again every time you go back to hboot.

Since you are S-On, you can't just flash the firmware
Click to expand...
Click to collapse
What do you mean by firmware. Bootloader or ROM? I did 'just' flash PA without a problem.
I guess the ROM you liked is the latest official one. By installing it I will get my bootloader updated and then I will be able to flash CM12. Do I get this right? or will I get stuck on stock forever?
Edit: I just tried to flash your image using hboot but it didn't work. Check file attached.
I checked MD5 checksum just to make sure that it did download correctly and it does match with the one on the download page. However, I did notice that when I'm trying to open that zip file on my PC I'm getting an error saying that the archive is corrupted.

ProTofik said:
What do you mean by firmware. Bootloader or ROM? I did 'just' flash PA without a problem.
I guess the ROM you liked is the latest official one. By installing it I will get my bootloader updated and then I will be able to flash CM12. Do I get this right? or will I get stuck on stock forever?
Edit: I just tried to flash your image using hboot but it didn't work. Check file attached.
I checked MD5 checksum just to make sure that it did download correctly and it does match with the one on the download page. However, I did notice that when I'm trying to open that zip file on my PC I'm getting an error saying that the archive is corrupted.
Click to expand...
Click to collapse
It probably didn't work because you are S-On. The method I gave you is generally used by S-Off users to flash firmware, but since it was a signed zip, I thought it might work.
Rename the download I gave you to ROM.zip at put it into your fastboot/platform-tools folder on your PC. Then hook your phone up to your PC and fastbooot.
fastboot devices to make sure your phone and PC are properly connected. (letters and numbers/ser. #)
fastboot oem rebootRUU
fastboot flash zip ROM.zip
EDIT: If you respond here, please use the reply button, I will get a notification that way. I just stumbled back to this thread by chance.

xunholyx said:
It probably didn't work because you are S-On. The method I gave you is generally used by S-Off users to flash firmware, but since it was a signed zip, I thought it might work.
Rename the download I gave you to ROM.zip at put it into your fastboot/platform-tools folder on your PC. Then hook your phone up to your PC and fastbooot.
fastboot devices to make sure your phone and PC are properly connected. (letters and numbers/ser. #)
fastboot oem rebootRUU
fastboot flash zip ROM.zip
EDIT: If you respond here, please use the reply button, I will get a notification that way. I just stumbled back to this thread by chance.
Click to expand...
Click to collapse
Sorry, doesn't work either. I'm getting this error on 3rd command:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip ROM.zip
target reported max download size of 1830711296 bytes
error: cannot load 'ROM.zip'
Click to expand...
Click to collapse

ProTofik said:
Sorry, doesn't work either. I'm getting this error on 3rd command:
Click to expand...
Click to collapse
Okay. There must be something I am not aware of.
In fastboot: fastboot getvar all and post the readout here. But delete the serial number and IMEI for your own safety. Never post those on a public forum.

xunholyx said:
Okay. There must be something I am not aware of.
In fastboot: fastboot getvar all and post the readout here. But delete the serial number and IMEI for your own safety. Never post those on a public forum.
Click to expand...
Click to collapse
There you go:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: TOP SECRET
(bootloader) imei: TOP SECRET
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
Click to expand...
Click to collapse

ProTofik said:
There you go:
Click to expand...
Click to collapse
It should work. Try this download instead. https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view
It's pretty much the same one. Maybe the other one is screwed somehow? Try with this one instead and hopefully you can get updated.

xunholyx said:
It should work. Try this download instead. https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view
It's pretty much the same one. Maybe the other one is screwed somehow? Try with this one instead and hopefully you can get updated.
Click to expand...
Click to collapse
Didn't work but I got a different error this time
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip ROM
.zip
target reported max download size of 1830711296 bytes
sending 'zip' (1536838 KB)...
OKAY [ 43.198s]
writing 'zip'...
(bootloader) zip header checking...
FAILED (remote: 32 header error)
finished. total time: 43.510s
Click to expand...
Click to collapse
Is it not possible to just restore whatever ROM my phone came with and then just do the OTA update?

ProTofik said:
Didn't work but I got a different error this time
Is it not possible to just restore whatever ROM my phone came with and then just do the OTA update?
Click to expand...
Click to collapse
LOL!
Yes. I got caught up in this method. You will also need the stock recovery (more important than the ROM) to use the OTAs. Plus your system partition has to be unmodified. That means no Xposed modules. If you have them, delete them using Xposed framework, then uninstall that as well.

xunholyx said:
LOL!
Yes. I got caught up in this method. You will also need the stock recovery (more important than the ROM) to use the OTAs. Plus your system partition has to be unmodified. That means no Xposed modules. If you have them, delete them using Xposed framework, then uninstall that as well.
Click to expand...
Click to collapse
So if I get this right, I just need to restore my factory ROM and Recovery image, then update it through OTA to lollipop. After that I will be able to flash my custom recovery and ROMs once again, right?
Do you have any links to the ROM and Recovery to my phone?

ProTofik said:
So if I get this right, I just need to restore my factory ROM and Recovery image, then update it through OTA to kitkat. After that I will be able to flash my custom recovery and ROMs once again, right?
Do you have any links to the ROM and Recovery to my phone?
Click to expand...
Click to collapse
Yes. Sorry for the confusion I have caused.

xunholyx said:
LOL!
Yes. I got caught up in this method. You will also need the stock recovery (more important than the ROM) to use the OTAs. Plus your system partition has to be unmodified. That means no Xposed modules. If you have them, delete them using Xposed framework, then uninstall that as well.
Click to expand...
Click to collapse
Success. For future generations, here is what I did:
Using fastboot getvar all command I found out that my phone was still mentally stuck on stock rom 1.54.401.5. Using this info, I downloaded matching nandroid backup of that ROM from here and restored it using my custom recovery.
Then, downloading from the same thread, I flashed back stock recovery image using HTC One 2014 (M8) All-In-One Toolkit V2.0.
I was back on my original ROM with original recovery, so I started doing OTA updates until I got to the official android 5.0.1. These updates updated my bootloader to version 3.19.
Having the bootloader that I needed, I flashed custom recovery and installed CM12 without any problem.
Thanks for help!

Hey, I just found this as I am having the same problem. I am trying to follow your solution, but hit a road block and was wondering if you could help. I ran the command "fastboot getvar all" in fastboot and got output similar to yours. Following your advice I looked at the line (bootloader) version-main: 1.55.605.2 which is different than yours, but okay I just need to find a matching one. But when I go to the link that you had provided I can't find a backup that matches mine (or at least I think I can't). What does it mean for it to match anyway? I'm getting so close! I want cm12!!

I did it over like 6 months ago. I can't remember any more. Sorry.
Anyway, CM12 has way too many problem on HTC ONE M8 to be used as a daily driver. I am using GPE Rom now, which I can recommend.

I just need to find some way to update my bootloader so I can get lollipop up and running. Thanks tho

noo_too_droid said:
Following your advice I looked at the line (bootloader) version-main: 1.55.605.2 which is different than yours, but okay I just need to find a matching one. But when I go to the link that you had provided I can't find a backup that matches mine (or at least I think I can't). What does it mean for it to match anyway?
Click to expand...
Click to collapse
The number needs to match exactly to restore to stock and OTA update the software/firmware (and therefore update hboot).
You can try to post on the following thread, and ask if someone can post the stock nandroid for 1.55.605.2 :http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Otherwise (if you can't get a stock nandroid) you may need to resort to getting s-off in order to update hboot (actually I recommend updating all firmware, not just hboot).

ProTofik said:
Success. For future generations, here is what I did:
Using fastboot getvar all command I found out that my phone was still mentally stuck on stock rom 1.54.401.5.
Click to expand...
Click to collapse
Hi there! I have a problem with my One M8 (S-OFF) - I cant flash any ROM on it. I can restore backups from a CM11 4.4.4 and an ARHD 41.0 but can't upgrade from either. I was looking at your solution and noticed that my ROM number is blank when I run fastboot getvar all. Is this a matter of concern? How can I flash a ROM again?

raghuchary said:
Hi there! I have a problem with my One M8 (S-OFF) - I cant flash any ROM on it. I can restore backups from a CM11 4.4.4 and an ARHD 41.0 but can't upgrade from either. I was looking at your solution and noticed that my ROM number is blank when I run fastboot getvar all. Is this a matter of concern? How can I flash a ROM again?
Click to expand...
Click to collapse
Your version-main is blank because of a bug in some older TWRPs. Update to 2.8.7.0. Flashing the new recovery won't fix version-main being blank until you flash new firmware though.
Also, you probably do have to update your firmware. You say you can't flash any ROMs, but you give no details.

xunholyx said:
Your version-main is blank because of a bug in some older TWRPs. Update to 2.8.7.0. Flashing the new recovery won't fix version-main being blank until you flash new firmware though.
Also, you probably do have to update your firmware. You say you can't flash any ROMs, but you give no details.
Click to expand...
Click to collapse
Apologies, newbie here. I was looking for the correct place to place my request for help, when I found this thread and asked. I will put it up in the Q&A section.

Brick?

Hi,
I have a big problem with my HTC one M8.
I was tring to back sense from GPE conversion, and now I do not know how to proceed. Maybe bricked my phone.
My situation is as follows:
Relocked. Adb can't find my device so I can not unlock again.
No recovery, no ROM installed. So, I can not flag USB debug. Can't proceed since relocked. Any suggestion?
Matteo

mtt_73 said:
Hi,
I have a big problem with my HTC one M8.
I was tring to back sense from GPE conversion, and now I do not know how to proceed. Maybe bricked my phone.
My situation is as follows:
Relocked. Adb can't find my device so I can not unlock again.
No recovery, no ROM installed. So, I can not flag USB debug. Can't proceed since relocked. Any suggestion?
Matteo
Click to expand...
Click to collapse
im going to assume your phones is s-off?

Yes s-off. Not sure how, but I am in recovery. Something looks like stock, I think. What can I do from here? Should I install twrp recovery? Or what else?
Thank you.
Sent from my Nexus 4 using XDA Free mobile app

mtt_73 said:
Yes s-off. Not sure how, but I am in recovery. Something looks like stock, I think. What can I do from here? Should I install twrp recovery? Or what else?
Click to expand...
Click to collapse
You can't install custom recovery with a (re)locked bootloader.
With s-off, you shouldn't ever relock the bootloader, as its no longer a requirement to RUU once s-off. But that's neither here nor there at this point, just info for future reference.
Any response to: fastboot devices
Make sure the phone is in fastboot mode.
Try to run the GPE RUU with phone in fastboot mode, to get the phone back up and running at least. Assuming you are still on the GPE CID and MID.

How can I flash ruu gpe with boot loader relocked? Is it possible? It gives me error.
Sent from my Nexus 4 using XDA Free mobile app

mtt_73 said:
How can I flash ruu gpe with boot loader relocked? Is it possible? It gives me error.
Click to expand...
Click to collapse
I think you've got it backwards. With s-on the bootloader actually needs to be relocked (or locked) in order to RUU.
With s-off, RUU will run whether the bootloader is unlocked, relocked, or locked.
In other words, the bootloader being relocked is not the problem.
What is the error message?
Did you change the CID/MID yet (what are they currently)? The CID and MID need to match the RUU.

Hi guys,
I have a problem with my one m8 at&t, unlocked, and i can only navigate in hboot in hboot & fastboot modes. no htc logo screens or sth like this.
when i try to go to recovery or do factory reset i get three android skaters on the screen for cca 0.2 sec and it returns to fastboot usb mode.
Its friends phone so i dont know what he had done to it, but i just want to make it work again, wiping data is not the problem.. can you tell me what should i do to get recovery( TWRP/ CWM) working, thats all i need for now because im going to s-off later. i tried to do something but it didnt work.
some things i have tried in that order:
1)flashing twrp via fastboot:
C:\adb>fastboot flash recovery C:\adb\openrecovery-twrp-2.8.5.0-m8.img
target reported max download size of 1830727680 bytes
sending 'recovery' (16086 KB)...
OKAY [ 1.438s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.500s
2) flashing stock recovery via fastboot( i dont know if i had the right one):
C:\adb>fastboot flash recovery C:\adb\recovery.img
target reported max download size of 1830727680 bytes
sending 'recovery' (14109 KB)...
OKAY [ 1.262s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.277s
3) 'booting' same stock recovery- what changed now are 3 android skaters for cca 0.2 sec when i try to enter recovery or start factory reset from bootloader, before it just went to fastboot usb mode.
C:\adb>fastboot boot recovery.img
creating boot image...
creating boot image - 14450688 bytes
downloading 'boot.img'...
OKAY [ 1.273s]
booting...
OKAY [ -0.000s]
finished. total time: 1.273s
Can please anyone help me? Thanks in advance
Here is data about the phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT.............8
(bootloader) imei: 35...........30
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

redpoint73 said:
I think you've got it backwards. With s-on the bootloader actually needs to be relocked (or locked) in order to RUU.
With s-off, RUU will run whether the bootloader is unlocked, relocked, or locked.
In other words, the bootloader being relocked is not the problem.
What is the error message?
Did you change the CID/MID yet (what are they currently)? The CID and MID need to match the RUU.
Click to expand...
Click to collapse
I will try again later. If I am not wrong the error is about partition problem. It does not recognize the zip.
Sent from my Nexus 4 using XDA Free mobile app

mtt_73 said:
I will try again later. If I am not wrong the error is about partition problem. It does not recognize the zip.
Click to expand...
Click to collapse
When you get a chance, you should list exactly (in detail, and in order) what you have done to the phone to get to this point.
I can't tell how far you go in the conversion (GPE>Sense) but it seems you at least got partway (if you indeed got a partition size error).
Also need to know current CID and MID.
---------- Post added at 12:35 PM ---------- Previous post was at 12:31 PM ----------
mato123 said:
I have a problem with my one m8 at&t, unlocked, and i can only navigate in hboot in hboot & fastboot modes. no htc logo screens or sth like this.
when i try to go to recovery or do factory reset i get three android skaters on the screen for cca 0.2 sec and it returns to fastboot usb mode.
Its friends phone so i dont know what he had done to it, but i just want to make it work again, wiping data is not the problem.. can you tell me what should i do to get recovery( TWRP/ CWM) working, thats all i need for now because im going to s-off later. i tried to do something but it didnt work.
some things i have tried in that order:
Click to expand...
Click to collapse
I would highly suggest not to post to another user's troubleshooting thread like this, as it doesn't look like the same problem at all (and in my experience rarely is, even when folks will post "I have the same issue"). You really should have just started your own thread, and would have been justified doing so IMO. Posting here just confuses matters for you, the OP and those trying to help.
But DON'T start another thread now (and add even more confusion). I'll ask the mods if they can move this post to its own thread.

ok, sorry

redpoint73 said:
When you get a chance, you should list exactly (in detail, and in order) what you have done to the phone to get to this point.
I can't tell how far you go in the conversion (GPE>Sense) but it seems you at least got partway (if you indeed got a partition size error).
Also need to know current CID and MID.
Click to expand...
Click to collapse
Thanks for reply.
I went now in fastoob mode and tried to flash the RUU GPE again.
The error is:
macbooks-MacBook-Proownloads macbook$ ./fastboot-mac flash RUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip
unknown partition 'RUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip'
error: cannot determine image filename for 'RUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip'
Just to clarify. I successfully when in GPE (with conversation). The problem was when going back to Sense. I do not know exactly what I did wrong.
My CID is 11111111
My MID is 0P6B10000
Really do not know how to proceed.
M

I unfortunately don't know jack about how to use fastboot and other actions on a Mac. I'm also not that familiar with running the RUU as a zip (I always do it on a PC with the RUU .exe).
But it looks like you just have the command syntax wrong. I think it should be:
fastboot oem rebootRUU
fastboot flash zip filename.zip
But it also look to me like nothing is actually "wrong" (aside from adb not working?). The phone not booting after relocking the bootloader is normal and intentional. You should just be able to run the desired Sense RUU, provided you have the right MID.

I am back to GPE!
Stupid me! I missed a "zip" in the fastboot command...
Thank you for support!
I will try again to go back to Sense.
M

mtt_73 said:
I am back to GPE!
Stupid me! I missed a "zip" in the fastboot command...
Thank you for support!
I will try again to go back to Sense.
M
Click to expand...
Click to collapse
hehe try watch this movie: https://www.youtube.com/watch?v=CCGj0rOuiR4
Most important is the firmware flash... so partition layout etc is changed to sense like after that you can flash sense roms etc. (for example viper rom as in video)

0kk0 said:
Most important is the firmware flash... so partition layout etc is changed to sense
Click to expand...
Click to collapse
Some folks have had to do this, some haven't. But yes, if the RUU fails and gives a image size error, flashing the Sense firmware manually (then RUU) is the right thing to do.
This part has never made sense to me, since the RUU flashes firmware anyway, by definition. All I can guess, is that it has to do with the sequence in which the firmware is flashed (versus other partitions) in the RUU.

redpoint73 said:
Some folks have had to do this, some haven't. But yes, if the RUU fails and gives a image size error, flashing the Sense firmware manually (then RUU) is the right thing to do.
This part has never made sense to me, since the RUU flashes firmware anyway, by definition. All I can guess, is that it has to do with the sequence in which the firmware is flashed (versus other partitions) in the RUU.
Click to expand...
Click to collapse
So, even if the sense RUU is available, to go back to sense I need to flash the firmware before to flash the RUU. Right?
Sent from my HTC One_M8 using xda Forum

mtt_73 said:
So, even if the sense RUU is available, to go back to sense I need to flash the firmware before to flash the RUU. Right?
Click to expand...
Click to collapse
I just said in the post you quoted: some folks are fine just running the RUU (to convert from GPE to Sense); but when the RUU alone doesn't work, run the firmware manually first, then the RUU.
Running the firmware manually first (then RUU) has a higher chance of working, I'd say.

redpoint73 said:
I just said in the post you quoted: some folks are fine just running the RUU (to convert from GPE to Sense); but when the RUU alone doesn't work, run the firmware manually first, then the RUU.
Running the firmware manually first (then RUU) has a higher chance of working, I'd say.
Click to expand...
Click to collapse
I did it. I am back to Sense now.
Any advice to remove tell HTC problem? I mean it says that I have a testing device. Is it because I am s-off? Should I go for s-on again? And how?
TY!

HELP PLS! Bootloader OS version and software number not the same

Hi All,
I'm not sure how I managed to do this but I think I bricked my phone
My bootloader was unlocked and the phone was rooted. I wanted to bring the phone back to stock in order to be able to install an OTA update.
I flashed the stock ROM and was able to install the OTA update.
After this I ran into a problem where the phone would boot and upgrade apps then right before finishing the boot it would reboot and start the process all over again. Looping everytime that the upgrade apps would finish.
Log story short I ended up restarting the process of going back to stock to try everything from scratch again. Things were not working so I foolishly relocked the bootloader thinking it wouldn't be an issue to unlock again with the unlock_code.bin file that I had used previously.
Now the phone will boot into the bootloader and into download mode but not into recovery.
Ive tried flashing the stock recovery and the TWRP recovery and even the recovery from the OTA update but none will flash as the bootloader is locked.
I tried to unlock the bootloader again but cannot and here is the reason why.
The bootloader thinks my OS is 5.1 but really the OS on the phone is 5.0.2
C:\Users\Dan\Desktop\HTC One\One M9>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 2.11.666.2
(bootloader) boot-mode: RUU
(bootloader) version-baseband: 01.02_U11440601_77.04.50715G_2_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: BM___001
all:
finished. total time: 0.033s
Software number on my phone is 1.32.666.30 but version-main is 2.11.666.2
Fastboot oem unlock does not work as the bootloader is looking for a flag that is set by selecting the developer option of unlock bootloader but that developer option only exists in android 5.1+
Being as the OS on my phone is 5.0.2 I don't have that option in my developer options.
When I boot into RUU with "fastboot oem rebootRUU" and I try to flash my stock rom I now get this.
C:\Users\Dan\Desktop\HTC One\One M9>htc_fastboot flash zip 0PJAIMG.zip
sending 'zip'... (94347 KB) OKAY
sending time = 5.298 secs
writing 'zip'... (bootloader) HOSD CL#579410
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
FAIL19: fail to flash via downloadzip
FAILED (remote: 19: fail to flash via downloadzip)
Execution time is 10(s)
I found a tool called misctool which can change the main version to whatever I choose - If I could change the main version back to 1.32.666.30 I'm assuming this would allow me to flash the stock ROM again and get me back up and running.
The problem is that misctool requires root and I cannot get root without unlocking the bootloader which I cannot unlock because the OS on my phone does not have the option to do so
I read about using nautilus within ubuntu to be able to push files into root areas of my phone and have tried to go this route but I cant get my phone to appear in ubuntu while its in download mode.
Sigh if only I could find a way to get root to be able to change the version-main I think my troubles would be a thing of the past
Can anyone shed any light on my dismal situation?

Your phone is bricked until there is a ruu for your cid/mid. You've made the same mistake as many people before you, which was relocking your bootloader before ticking the allow oem unlock option.
Sent from my HTC One M9 using Tapatalk

iElvis said:
Your phone is bricked until there is a ruu for your cid/mid. You've made the same mistake as many people before you, which was relocking your bootloader before ticking the allow oem unlock option.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
How.. He didnt have the option to begin with. Like many others dont as 5.1 is the version with the unlock option. 5.0.1/.2 don't have the option so you cannot tick unlock, update and unlock the bl.
If you cannot see the logic, please explain your method.
I wish I stole my HTC M9. It's a pile of ****.

Thats the thing,
I was never able to boot into 5.1. As I mentioned in my OP the phone kept rebooting at finishing boot after optimizing the apps.
I figured flashing the stock ROM back on to the phone would let me start over again..
It wasn't until after I relocked the bootloader and started to get errors when trying to unlock it again that I read about the "Allow OEM Unlock" option within the developer options of the phone.
Now that the original ROM is back on the phone that option does not exist in my develop options as the OS version is 5.0.2
I'm wondering why flashing the stock ROM didn't put the stock bootloader version back on the phone at the same time.
All I know now is that the bootloader requires the "Allow OEM Unlock" option to be checked (as it seems to think my software number is 2.11.666.2) in order to let me unlock my bootloader which I cannot do as I the option does not exist in the developer options of 5.0.2.
If only I could gain root while in the adb shell. With that I could use misctool to set the software version back to 1.32.666.30 which I think would then allow me to re-flash my stock ROM, put the bootloader back to what it was, and allow me to unlock it again.
Who creates the RUUs? HTC? HTC and my carrier? Waiting for that to come around is a terrible outcome. I think I will have better luck waiting for a root shell exploit to come around.
Ahhhh what a crappy situation.
shivadow said:
I wish I stole my HTC M9. It's a pile of ****.
Click to expand...
Click to collapse
Mwahahahaha I'm starting to feel the same way!

Of course you could not have ticked the oem unlock option before starting the process. That wasn't what I meant.
The problem is that you upgraded to 5.1 via ota (that's why your version-main says 2.11), so now you have to tick it to unlock. It was locking after the ota but before getting your OS straightened out that was the mistake. Now you're stuck.
There seems to be a problem with the 2.11 update that causes this boot loop issue. I have not seen a fix since I don't believe HTC has released a RUU for 2.11. But, as you recognized in the OP, relocking in the middle of this was not the solution.

I was able to flash the firmware from the 2.11.666.2 OTA.
Now I can no longer boot into the 1.32.666.30 OS but I can boot into the stock recovery but there is not much I can do from there.
I've tried to sideload the OTA but of course it doesnt work because of the changes to the system partition from when I was rooted.
Ive tried to flash a twrp system.emmc.win from a stock backup of the 1.32.666.30 but it errors out with signature verification failed. Im assuming because its a backup of the 1.32.666.30 and not the 2.11.666.2?
Would it make sense that if I could find a system img of the Bell Mobility 2.11.666.2 I would be able to sideload it? Maybe that would fix the issues with the system partition and allow the OTA to complete s that I could then at least boot into the phone ?
Or am I looking at smashing this thing and going to buy another one?

Try to S-Off your phone. Though it probably won't work without root.

omar302 said:
Try to S-Off your phone. Though it probably won't work without root.
Click to expand...
Click to collapse
Thanks Omar. I don't think I can go for S-OFF as my bootloader is relocked and I can't re unlock it.
Root is gone too except for the mess that it made to the system partition. Which is why I cant sideload the OTA.
If only I could get rid of the OTA verification. It would install and I think my phone would let me boot into the os where I could finally choose the "Enable OEM Unlock" option in the developer options.
Right now im trying to find an OTA for Bell Mobility that updated the OS to 5.0.2 if I could find that I could flash that firmware which would probably put the bootloader back to 1.32.666.30.
That way I could unlock the bootloader through adb etc.
I seriously think Im screwed unless if I could find that firmware or find out a way to fool the OTA into believing nothing changed with the system partition so that it would complete the install sigh

You might try an earlier ruu.zip for your CID and see if you can load it from the sdcard in Download mode. This would downgrade you to something functional. You can downgrade firmware on the M9 even with s-on as long as the aboot has not changed. Not sure if this will work for you, but it's worth a shot.
If it works, get root and s-off, then just flash everything manually. I've seen too many people screw up their phones trying to revert to stock to get OTAs.

iElvis said:
You might try an earlier ruu.zip for your CID and see if you can load it from the sdcard in Download mode. This would downgrade you to something functional. You can downgrade firmware on the M9 even with s-on as long as the aboot has not changed.
Click to expand...
Click to collapse
Sadly that's not true. What I learned during the last weeks (from trying to help others like Amr Nasser or Denis Meissner) is that a downgrade with S-ON is only possible if the first and the second version number are the same before and after the downgrade. That means a downgrade from 1.32.xxx.15 to 1.32.xxx.8 is possible but from 1.40.xxx.8 to any 1.32 version is not. The same applies to downgrades from 2.xx versions.

Flippy498 said:
Sadly that's not true. What I learned during the last weeks (from trying to help others like Amr Nasser or Denis Meissner) is that a downgrade with S-ON is only possible if the first and the second version number are the same before and after the downgrade. That means a downgrade from 1.32.xxx.15 to 1.32.xxx.8 is possible but from 1.40.xxx.8 to any 1.32 version is not. The same applies to downgrades from 2.xx versions.
Click to expand...
Click to collapse
Probably because the aboot version has changed between those versions. At least that was how it was explained to me by someone more knowledgable a while back.

iElvis said:
Probably because the aboot version has changed between those versions. At least that was how it was explained to me by someone more knowledgable a while back.
Click to expand...
Click to collapse
According to my phone it's still version 1.0.0.0000. That's why I don't understand why a downgrade is impossible.
D:\Root>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 2.10.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__102
all:
finished. total time: 0.016s
Edit: Don't get me wrong. I don't want to start an argument. I'm just trying to understand this phone.

Flippy498 said:
Edit: Don't get me wrong. I don't want to start an argument. I'm just trying to understand this phone.
Click to expand...
Click to collapse
No that's what I thought. Someone else insisted the aboot version was what mattered. But I haven't tried it myself so I'm just passing on what I was told.

Htc one m8 unable to find correct firmware and rom

THANKS IN ADVANCE
hi being long period user of android phone still facing many problems to get OTA update on my phone. I was excited about my phone HTC one M8 and wanted to install OTA update there was not any software update option in my phone and than i ran for internet search spent regular three days to find correct firmware get back to stock which totally different from samsung phones. I gone through all the the threads and option provided on internet tried to get back to stock. I need help of professional
who can sort out this problem. HTC PHONE IS NOW BOOTLOADER LOCKED S-OFF KITKAT INSTALLED SUPERCID software number 1.54.651.8
PLEASE GIVE LINK TO GET STOCK RECOVERY AND HOW TO INSTALL OR FLASH IT.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.05.20.0321_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.651.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ***********
(bootloader) imei: ***********
(bootloader) imei2: Not Support
(bootloader) meid: **************
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(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: 8a0f02ff
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.094s

http://forum.xda-developers.com/showthread.php?t=2729173

http://forum.xda-developers.com/show....php?t=2729173
Click to expand...
Click to collapse
THANKS ckpv5 I WILL GIVE YOU WHOLE INFO. ABOUT MY PROBLEM
As i changed my MID and flashed wrong zip of HTC europe rom on HTC SPRINT which drained everything including my custom TWRP. I was totally new to HTC totally messed up everything. its been more than five days my phone had stuck at hboot screen i know you guy are genius can save my hundard of BUCKs as its new phone bought 15 days ago it was rooted.
I WAS TRYING TO INSTALL SPRINT FIRMWARE TOO BECAUSE I HAD ALREADY FLASHED THAT FIRMWARE ACCORDING TO EUROPE ROM. NOW THE PROBLEM IS THAT I AM UNABLE TO FLASH FIRMWARE DUE TO CHANGED MID (talked earlier) CANNOT UNDERSTAND WHAT TO DO.

Do you still have TWRP installed ?
If no, install one
If yes,
Boot to TWRP recovery, select mount - system
open command prompt from your adb/fastboot folder then run command
adb shell
then this code
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x37\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
Make sure you copy the code, not write it yourself
then exit
then select reboot - bootloader
then run
fastboot getvar mid
you should see your mid now read 0P6B70000
(you don't need "su" command)
Now you can install Sprint RUU - http://www.htc.com/us/support/htc-one-m8-sprint/news/
or check those in Sprint section that I linked above
Note : You will get your device running again but you maybe lost the 3G/4G and only can get 2G. Reason is you flashed wrong radio meant for GSM on your CDMA, this usually brick the radio. If you're lucky enough, this is not happening.

ckpv5 said:
Do you still have TWRP installed ?
If no, install one
If yes,
Boot to TWRP recovery, select mount - system
open command prompt from your adb/fastboot folder then run command
adb shell
then this code
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x37\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
Make sure you copy the code, not write it yourself
then exit
then select reboot - bootloader
then run
fastboot getvar mid
you should see your mid now read 0P6B70000
(you don't need "su" command)
Now you can install Sprint RUU - http://www.htc.com/us/support/htc-one-m8-sprint/news/
or check those in Sprint section that I linked above
Note : You will get your device running again but you maybe lost the 3G/4G and only can get 2G. Reason is you flashed wrong radio meant for GSM on your CDMA, this usually brick the radio. If you're lucky enough, this is not happening.
Click to expand...
Click to collapse
this is what now comes up when i try to flash TWRP
C:\Users\USER\Desktop\fastboot_adb\fastboot_adb>fastboot flash recovery "twrp-2.8.5.0-m8_whl.img."
target reported max download size of 1826418688 bytes
sending 'recovery' (16086 KB)...
OKAY [ 1.501s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.516s
i'm brain dead nothing works SUGGEST SOMETHING
EVEN UNABLE TO UNLOCK BOOTLOADER NOW

You can't fastboot flash recovery while the bootloader is locked/relocked.
You need a microSD.
Download the 0P6BIMG.zip that I posted here : http://forum.xda-developers.com/showpost.php?p=67526388&postcount=387
No need to worry what OS it is written for now, it will get fixed when you install RUU.
Place the 0P6BIMG.zip on root of microSD (means not in any folder)
Then put your phone on hboot, it will scan the file. Volume up to update (install). Once done, it will ask you to reboot but you know that your device is bootlooping, just put the device on bootloader (remove the microSD to delete the 0P6BIMG.zip)
Now you can boot to TWRP recovery and do the rest as described above.

ckpv5 said:
You can't fastboot flash recovery while the bootloader is locked/relocked.
You need a microSD.
Download the 0P6BIMG.zip that I posted here : http://forum.xda-developers.com/showpost.php?p=67526388&postcount=387
No need to worry what OS it is written for now, it will get fixed when you install RUU.
Place the 0P6BIMG.zip on root of microSD (means not in any folder)
Then put your phone on hboot, it will scan the file. Volume up to update (install). Once done, it will ask you to reboot but you know that your device is bootlooping, just put the device on bootloader (remove the microSD to delete the 0P6BIMG.zip)
Now you can boot to TWRP recovery and do the rest as described above.
Click to expand...
Click to collapse
:fingers-crossed: Thanks man you are really great now these are the outcomes
C:\Users\USER\Desktop\fastboot_adb\fastboot_adb>fastboot getvar mid
mid: 0P6B70000
finished. total time: -0.000s
Now it want follow your command give me further steps. Thanks Again
Moreover, i made mistake that i also had flashed firmware file according to htc europe rom. Now which one should choose.

Doesn't matter about the firmware now .. just install RUU.
That was the guide written above.
1. Change MID
2. Install RUU exe that is linked above.
Make sure you have windows PC with usb2.0 and the latest htc usb drivers are installed.
HTC USB drivers - Install HTC Sync Manager - http://www.htc.com/us/support/software/htc-sync-manager.aspx
- it will install the needed drivers then uninstall the HTC Sync Manager but leave the drivers.
Or you can use RUU zip
0P6BIMG_Sprint_HTC_One_M8_6.20.651.3_RUU.zip that you can get in Sprint thread.
Rename it to 0P6BIMG.zip and install the same way as you installed TWRP above (microSD method)

ckpv5 said:
Doesn't matter about the firmware now .. just install RUU.
That was the guide written above.
1. Change MID
2. Install RUU
Make sure you have windows PC with usb2.0 and the latest htc usb drivers are installed.
HTC USB drivers - Install HTC Sync Manager - http://www.htc.com/us/support/software/htc-sync-manager.aspx
- it will install the needed drivers then uninstall the HTC Sync Manager but leave the drivers.
Click to expand...
Click to collapse
0P6BIMG_Sprint_HTC_One_M8_6.20.651.3_RUU
sorry it could be silly but which one is right one in both of it or give the link to particular one because i am afraid don't mess anything again. Thanks man
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4

What's this RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.154 0.4 got do with your device ?
All my links are referred to RUU 6.20.651.3 on post #2, #4 & #8

ckpv5 said:
What's this RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.154 0.4 got do with your device ?
All my links are referred to 6.20.651.3 on post #2, #4 & #8
Click to expand...
Click to collapse
Sorry bro i sent you by mistake i got it i will flash 0P6BIMG_Sprint_HTC_One_M8_6.20.651.3_RUU file through HBOOT and i will post the outcome whatever there will be but you are great. You saved me. Thanks a lot bro
It says that Device halted due large image update file
What do you suggest now.

Then install 6.20.651.3 Signed Full Firmware first, see whether it can be installed.
Rename it to 0P6BIMG.zip and install it microSD method. If successful then install RUU.
(This is the problem .. I don't have Sprint device, unable to test)

ckpv5 said:
Then install 6.20.651.3 Signed Full Firmware first, see whether it can be installed.
Rename it to 0P6BIMG.zip and install it microSD method. If successful then install RUU.
(This is the problem .. I don't have Sprint device, unable to test)
Click to expand...
Click to collapse
There is another problem occured i flashed signed firmware now phone only shows the HTC logo and unable to restart what should do now???

Was the firmware installation successful ? This is important.
When you reboot, there is no OS, you need to put back to bootloader then install RUU.
(Same way after you installed TWRP before)
I think this is easier.. instead of going to Marsmallow, install the lollipop first just to get your phone up & running.
Install this 0P6BIMG_Sprint_HTC_One_M8_4.25.651.18_RUU.zip, for this you don't need to install firmware.
Once successful, then you can try again to install Marshmallow 0P6BIMG_Sprint_HTC_One_M8_6.20.651.3_RUU.zip but
you need to install 6.20.651.3 Firmware first.

ckpv5 said:
Was the firmware installation successful ? This is important.
When you reboot, there is no OS, you need to put back to bootloader then install RUU.
(Same way after you installed TWRP before)
I think this is easier.. instead of going to Marsmallow, install the lollipop first just to get your phone up & running.
Install this 0P6BIMG_Sprint_HTC_One_M8_4.25.651.18_RUU.zip, for this you don't need to install firmware.
Once successful, then you can try again to install Marshmallow 0P6BIMG_Sprint_HTC_One_M8_6.20.651.3_RUU.zip but
you need to install 6.20.651.3 Firmware first.
Click to expand...
Click to collapse
Thanks man we made it IT IS FINALLY WORKING you are really great Man this info will HELP SOMEONE AS WELL..

Great ..
Now I can sleep well.. it's 1.00 am here... good night

ckpv5 said:
Great ..
Now I can sleep well.. it's 1.00 am here... good night
Click to expand...
Click to collapse
Thanks you spent much time to solve my problem rest of the phone is working fine and it shows one error of something that attached a screenshot also attached screenshot of networks please tell there is 3g and 4g Thank you great man
There is also portable wifi hotspot is missed. Need help where to find it.

karamghumaan said:
There is also portable wifi hotspot is missed. Need help where to find it.
Click to expand...
Click to collapse
Did you find it? And how did you changed WiFi and signal status bar icon? Which htc theme did you use?
Sent from my HTC One_M8 using Tapatalk

Zile995 said:
Did you find it? And how did you changed WiFi and signal status bar icon? Which htc theme did you use?
Click to expand...
Click to collapse
Hello mate No it is till missing and official theme and i also want change that icon but i couldn't find that option too. Are you able to give me that solution how i can do it. More there is activating device window at start up how can i remove that?

karamghumaan said:
Thanks you spent much time to solve my problem rest of the phone is working fine and it shows one error of something that attached a screenshot also attached screenshot of networks please tell there is 3g and 4g Thank you great man
Click to expand...
Click to collapse
SO you have no cell data access?
What bands does your carrier uses for 3G and LTE (what band for each of those - they are 2 different things).
karamghumaan said:
There is also portable wifi hotspot is missed. Need help where to find it.
Click to expand...
Click to collapse
Hotspot is locked out on most US carrier versions. If you don't see Hotspot as an available "tile" in the notification quick settings, and no Hotspot widget, than the feature has been disabled on your stock ROM.
Easiest way to enable Hotspot is with the proper custom ROM (supports Sprint version M8).