Develop Bugs

Problem firmware and OS in my m8

Hey guys, if somebody could help me resolve my problem i´ll be eternally gratefully. A couple of days before i bought an international version of the htc m8 (0P6BIMG100), it had kitkat 4.4.4, and i want to upgrate the sistem to marshmallow, so, reading in the multiple forums i found a tread in this site that teaches how to convert the phone to google edition, when i started the fastboot it was locked (i unlocked it) and S-off with supercid 11111111 (the phone came rooted). I follow the instructions step by step and after the installation of the RUU finished, the phone boots in to the black google screen and enter in fastboot. So, i tried reversing the process and go to the sense version again, a friend (who happen to have an htc m8) help me do it and we manage to restore de backup that i made in TWRP. After that, he toldme to install a custom rom, i decide to install the Insert Coin Enhaced "ice-8.2.2_M8_UHL_MM60_SENSE80GP_HTC_WWE_6.12.401.4". And for my surprise, it worked!! However, the phone didn´t recognice de wifi antena, the sim, the front camera, etc and the imei, baseband, and all that stuff said "not available", after a few minutes, the phone began to reboot. Looking through different XDA forums many said it was the kernel, so i let my friend flash the google edition kernel (i still don´t know why i let him do that). After that, the phone simply reboots in the fastboot screen, so again reading in the forums i found that maeby was not a kernel issue, but a firmware thing. So, i been installing a hell of firmwares and one by one trying to install the rom, but it jus´t don´t work. The last upgrate that i did via "ext_card" (i rename it 0P6BIMG) end saying in red letters "device halted due to large image update fail" (i wipe de data of the microsd, i change the microsd for ahother one, and nothing) and a red flag appeared saying "image update fail!". After this, no matter which firmware i try to install it, i cant find the right one, besides, now in the fastboot getvar all command the "version-main: " is blank, it shows nothing. I also found the RUU.exe trends and i tried some of them, but they get stock in the "sending information 0/7 screen". After a while i enter again in the fastode screen with the abd command. So if anybody could help me i´ll be glad to invite the beers, i need the phone for work and it´s been a hell of 5 straight days without resolving this issue, these are the specs that are showed in the fastboot mode screen:
*** Software status official ***
*** UNLOCKED ***
M8_WLV PVT SHIP S-OFF
CID - 11111111
HBOOT-3.19.0.0000
RADIO-1.25.214500021.06G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-
eMMC-boot 2048MB
------------------------------------
These are the specs in the "fastboot getvar all":
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.25.214500021.06G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: HT445SF02290
imei: ***************
imei2: Not Support
meid: **************
product: m8_wlv
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 3aa067db
hbootpreupdate: 11
gencheckpt: 0
Does anyone know what can i do? Apologies for the language, i´m not a native english speaker

Your device is not International GSM (m8_ul or m8_uhl) but it is a Verizon CDMA device (m8_wlv).
Those ROMs you tried are for m8_ul or m8_uhl, won't work on your device.
Read this on how to fix it - https://forum.xda-developers.com/htc-one-m8/help/m8-bricked-flash-rom-neither-restore-t3535671

Well...
ckpv5 said:
Your device is not International GSM (m8_ul or m8_uhl) but it is a Verizon CDMA device (m8_wlv).
Those ROMs you tried are for m8_ul or m8_uhl, won't work on your device.
Read this on how to fix it - https://forum.xda-developers.com/htc-one-m8/help/m8-bricked-flash-rom-neither-restore-t3535671
Click to expand...
Click to collapse
But if is a CDMA why does the phone have a nanosim entry?
I follow the given istructions but none of them works, after keep reading other answers in other post i found the 1.57.114.2 firmware sugestion, i rename it to "0P6BIMG.ZIP" and was able to run it in the HBOOT menu, now these are the specs that are showed in the bootloader screen:
M8_WLV PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.2133156.UA10G
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.57.114.2
eMMC-BOOT 2048MB
Apr 10 2014, 01:18:21.1
----------------------------------------------------------------
These are the specs showed in the ´fastboot getvar all´ command:
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.16.2133156.UA10G
version-cpld: None
version-microp: None
version-main: 1.57.114.2
version-misc: PVT SHIP S-OFF
serialno: HT445SF02290
imei: ***************
imei2: Not Support
meid: ***************
product: m8_wlv
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: c3d94491
hbootpreupdate: 11
gencheckpt: 0
--------------------------------------------------
I tried to install again the Insert Coin Enhaced "ice-8.2.2_M8_UHL_MM60_SENSE80GP_HTC_WWE_6.12.401.4", for my surprise the TWRP flashed it quick, but after the reboot it was stuck in the white screen with the HTC logo in green color, so...., i wipe it all, reinstall de "1.57.114.2.zip" and well, i´m still reading posts about the subject, any idea of what can i do sir?. By the way, thank you very much for the orientation

No matter what GSM firmware that you install, they won't work on your CDMA device.
You can install those GSM firmware like 1.57.114.2 because the MID is 0P6B10000
If you ever successful install a ROM on these firmware, you won't get any signal, your SIM won't work. Flashing these GSM firmware on CDMA device may brick your radio permanently.
What you need to do :
1. Change back the MID 0P6B10000 to original 0P6B20000
read this - https://forum.xda-developers.com/showpost.php?p=70504345&postcount=35
2. Install correct firmware to fix the radio first
https://forum.xda-developers.com/showpost.php?p=70502435&postcount=31
3. Install Marshmallow firmware which already include TWRP - https://www.androidfilehost.com/?fid=24438995911973227
4. Install your custom ROM that you want.
GPE - install this and select Verizon while in Aroma - https://forum.xda-developers.com/ve...ment/rom-vzw-stock-gpe-5-1-lmy47o-h9-t3212413
Or you can install any ROM in this section - https://forum.xda-developers.com/verizon-htc-one-m8/development
Or you can install some ROM with Verizon support in this section - https://forum.xda-developers.com/htc-one-m8/development
And I believe all the Nougat ROM support Verizon too.

lalomayen said:
But if is a CDMA why does the phone have a nanosim entry?
Click to expand...
Click to collapse
When we say "CDMA version" M8, it means it supports CDMA in addition to GSM and LTE networks. Mainly, so Verizon customers can use other carrier nanoSIMs while travelling to foreign countries.
The presence of the nanoSIM slot does not make it the "GSM" variant of the M8.
You have the Verizon CDMA version M8. There is not question about it.
lalomayen said:
I follow the given istructions but none of them works, after keep reading other answers in other post i found the 1.57.114.2 firmware sugestion
Click to expand...
Click to collapse
There is no reason to believe this firmware will work with your device.
You need to follow the advice given by ckpv5, he knows what he is talking about. If you get stuck with the process, tell us specifically what step, what the specific results were, error messages, etc. (just saying it didn't work, isn't goo enough) If you got stuck, it was likely pilot error; and we can probably troubleshoot, and see what went wrong, and properly advise you.

Ok, so i am in a somewhat similar situation to you. There are a few differences though. The first is that the phone has S-on. The owner said that the phone never had the bootloader unlocked, neither was it rooted. When the phone is turned on, it says:
*** Software status: Modified ***
*** Locked ***
***Security Warning ***
M8QL_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
[email protected]
OS-2.10.771.1
eMMC-boot 2048MB
Apr 22 2016,12:28:26.0
When i connected it to the pc and ran fastboot getvar all, I got:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.771.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *
(bootloader) imei: *
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: H3G__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: 0b9a12e3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
Any ideas what steps to take? Thanks in advance

ze410t said:
Ok, so i am in a somewhat similar situation to you. There are a few differences though. The first is that the phone has S-on. The owner said that the phone never had the bootloader unlocked, neither was it rooted.
Click to expand...
Click to collapse
Respectfully, your situation bears little, if any, similarity to the OP. His is s-off, with custom recovery, and trying to install custom ROMs. Further, he has the Verizon version (which as a lot of unique peculiarities versus other variants), with botched install of another version's firmware; which on the Verizon version in particular, results in broken radio (no SIM).
You have a very different M8 version, and a very different situation (close to stock - although I think root was at least attempted). And you haven't actually described what your question or issue is. The OP's problem is the wrong firmware, and custom ROMs don't work; but those issues don't apply to you.
I see you've started another thread here. I'd suggest sticking to that thread, rather than posting to this one. There are too many differences between your phone and situation to the OPs. Further discussion here (while also helping the OP in parallel) will probably result in unnecessary confusion.

redpoint73 said:
Respectfully, your situation bears little, if any, similarity to the OP. His is s-off, with custom recovery, and trying to install custom ROMs. Further, he has the Verizon version (which as a lot of unique peculiarities versus other variants), with botched install of another version's firmware; which on the Verizon version in particular, results in broken radio (no SIM).
You have a very different M8 version, and a very different situation (close to stock - although I think root was at least attempted). And you haven't actually described what your question or issue is. The OP's problem is the wrong firmware, and custom ROMs don't work; but those issues don't apply to you.
I see you've started another thread here. I'd suggest sticking to that thread, rather than posting to this one. There are too many differences between your phone and situation to the OPs. Further discussion here (while also helping the OP in parallel) will probably result in unnecessary confusion.
Click to expand...
Click to collapse
Oh ok :/ sorry about that. This was the only post that i found that i thought was similar. My apologies. Carry on!

ze410t said:
Oh ok :/ sorry about that. This was the only post that i found that i thought was similar. My apologies. Carry on!
Click to expand...
Click to collapse
No worries. I posted in the thread you started, and will try to help you there.

Stuck
ckpv5 said:
No matter what GSM firmware that you install, they won't work on your CDMA device.
You can install those GSM firmware like 1.57.114.2 because the MID is 0P6B10000
If you ever successful install a ROM on these firmware, you won't get any signal, your SIM won't work. Flashing these GSM firmware on CDMA device may brick your radio permanently.
What you need to do :
1. Change back the MID 0P6B10000 to original 0P6B20000
read this - https://forum.xda-developers.com/showpost.php?p=70504345&postcount=35
2. Install correct firmware to fix the radio first
https://forum.xda-developers.com/showpost.php?p=70502435&postcount=31
3. Install Marshmallow firmware which already include TWRP - https://www.androidfilehost.com/?fid=24438995911973227
4. Install your custom ROM that you want.
GPE - install this and select Verizon while in Aroma - https://forum.xda-developers.com/ve...ment/rom-vzw-stock-gpe-5-1-lmy47o-h9-t3212413
Or you can install any ROM in this section - https://forum.xda-developers.com/verizon-htc-one-m8/development
Or you can install some ROM with Verizon support in this section - https://forum.xda-developers.com/htc-one-m8/development
And I believe all the Nougat ROM support Verizon too.
Click to expand...
Click to collapse
Ohh, ok, got it now, i don´t know if 0P6B20000 was the original, but i follow the instructions in step 1, the TWRP 2.8.7.0 didn´t started in my phone, the 2.0.7.2 version did (i don´t know why), i follow the instructions: boot to recovery
Mount - system
then open command prompt from your adb/fastboot folder
then type
adb shell
follow by comand: echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x32\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
i get an error message ""dd" no se reconoce como un comando interno o externo, programa o archivo por lotes ejecutable." ("Dd" is not recognized as an internal or external command, Program or executable batch file")

redpoint73 said:
When we say "CDMA version" M8, it means it supports CDMA in addition to GSM and LTE networks. Mainly, so Verizon customers can use other carrier nanoSIMs while travelling to foreign countries.
The presence of the nanoSIM slot does not make it the "GSM" variant of the M8.
You have the Verizon CDMA version M8. There is not question about it.
There is no reason to believe this firmware will work with your device.
You need to follow the advice given by ckpv5, he knows what he is talking about. If you get stuck with the process, tell us specifically what step, what the specific results were, error messages, etc. (just saying it didn't work, isn't goo enough) If you got stuck, it was likely pilot error; and we can probably troubleshoot, and see what went wrong, and properly advise you.
Click to expand...
Click to collapse
I see, i´m new in this subject, thanks for the observations, i´ll submint the issues in the order that they appear

lalomayen said:
I see, i´m new in this subject, thanks for the observations
Click to expand...
Click to collapse
No problem. The Verizon version is pretty peculiar, so its easy to get confused by it. In fact, for this reason I typically do not recommend anyone buy this or the Sprint variant, unless they are located in the US actually using that particular carrier (Verizon or Sprint).

Can Only Install 1 ROM - Corrupted Phone?

Hey guys,
So I believe I somehow managed to corrupt my phone or something?
I've tried several different ROMS, all to which give me an error upon installation.
The only ROM that will actually install successfully is WOLLA V7.
I've tried several other GPE based ROMS, and several TW all to which fail during install.
Could someone possibly give me an explanation to what happened, I used to be able to install any ROM now I'm stuck using WOLLA.
Here is my GETVAR ALL.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.12.20.1211
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.17.605.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) imei2: Not Support
(bootloader) meid: 99000499864898
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: f2489bd1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.098s
I'm not quite sure what other information you guys may need in order to solve this problem of mine.
Thanks in advance​ for all those who leave some feedback or an explanation, I would love to find a solution!

Trytohaxme said:
(bootloader) version-main: 4.17.605.5
(bootloader) product: m8_wlv
(bootloader) modelid: 0P6B20000
[/CODE]
Click to expand...
Click to collapse
The above items indicate that you have the Verizon version M8. This version uses different kernel from other M8 versions, so you should only try ROMs specifically intended for the Verizon M8. So stick to the Verizon M8 Development section, or you can also flash ROMs from the "general" development section only if they specifically state that Verizon M8 is supported.
Also note that this has nothing to do with the actual local cell carrier you are using (folks often confuse this). The Verizon M8 is actually different in hardware, radio, partitioning, etc. from most all other M8 versions. So the reference to the Verizon version is actually referring to the device itself.
Another note of caution, I see you have the Verizon version with s-off and SuperCID; and may not be familiar with the peculiarities of the Verizon version. This combination is somewhat risky, in that you need to be sure never to flash firmware.zip or RUU from another version M8, as they are not compatible and permanent damage is possible!

redpoint73 said:
The above items indicate that you have the Verizon version M8. This version uses different kernel from other M8 versions, so you should only try ROMs specifically intended for the Verizon M8. So stick to the Verizon M8 Development section, or you can also flash ROMs from the "general" development section only if they specifically state that Verizon M8 is supported.
Also note that this has nothing to do with the actual local cell carrier you are using (folks often confuse this). The Verizon M8 is actually different in hardware, radio, partitioning, etc. from most all other M8 versions. So the reference to the Verizon version is actually referring to the device itself.
Another note of caution, I see you have the Verizon version with s-off and SuperCID; and may not be familiar with the peculiarities of the Verizon version. This combination is somewhat risky, in that you need to be sure never to flash firmware.zip or RUU from another version M8, as they are not compatible and permanent damage is possible!
Click to expand...
Click to collapse
Hmm, that may be my problem than as I did flash a new firmware package though it was primarily for international variants I believe.
Am I not able to use a RUU and get my phone back to normal now, if so can you locate the proper RUU that I would need for my model?

Trytohaxme said:
Hmm, that may be my problem than as I did flash a new firmware package though it was primarily for international variants I believe.
Am I not able to use a RUU and get my phone back to normal now, if so can you locate the proper RUU that I would need for my model?
Click to expand...
Click to collapse
The version main number 4.17.605.5 in the getvar data you posted, would indicate that you are on the Verizon firmware (the "605" is unique to Verizon). Unless you previously flashed an international firmware, then subsequently the Verizon 4.17.605.5 firmware?
In any case, it's not a bad idea to RUU back to full stock Verizon "baseline" and see if that fixes the problem. Particularly, if you think you flashed the wrong firmware before.
You can find Verizon RUUs here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Note that the US Marshmallow RUUs have a peculiar requirement, in that you need to flash the firmware (6.21.605.3) before you can flash the RUU. If you try RUU 6.21.605.3 and get an Error (155 I believe) this is the case, and you need to find and flash the firmware, then RUU. Not sure where to find the 6.21.605.3 firmware, but you might look around the M8 Verizon forum section.

redpoint73 said:
The version main number 4.17.605.5 in the getvar data you posted, would indicate that you are on the Verizon firmware (the "605" is unique to Verizon). Unless you previously flashed an international firmware, then subsequently the Verizon 4.17.605.5 firmware?
In any case, it's not a bad idea to RUU back to full stock Verizon "baseline" and see if that fixes the problem. Particularly, if you think you flashed the wrong firmware before.
You can find Verizon RUUs here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Note that the US Marshmallow RUUs have a peculiar requirement, in that you need to flash the firmware (6.21.605.3) before you can flash the RUU. If you try RUU 6.21.605.3 and get an Error (155 I believe) this is the case, and you need to find and flash the firmware, then RUU. Not sure where to find the 6.21.605.3 firmware, but you might look around the M8 Verizon forum section.
Click to expand...
Click to collapse
I honestly and truly appreciate all the help you have giving me, but I have one last question.
I believe using a RUU would be my best bet, starting from scratch is never a bad idea.
Would using a RUU fix/format any and or all partitions, cause I believe my data partition may be corrupted

Trytohaxme said:
Would using a RUU fix/format any and or all partitions, cause I believe my data partition may be corrupted
Click to expand...
Click to collapse
Yes, RUU in theory should format all partitions, and will often fix data partition corruption.
Although, if you still have TWRP installed, I would suggest booting to TWRP, and tapping the "Format data" button/option before trying the RUU. Reason being, this will often fix data corruption. And not sure, but I think in some cases I've seen RUU fail due to data corruption. So fixing it in TWRP may prevent you from having to go around in circles to get the RUU to work.

Need help updating M8 to Marshmallow

I have a 'new in the box' M8 that appears to be an AT&T UK model
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.401.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B63000
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
OTA does not show any updates available (I am in the USA), and none of the RUU or ROM.zip files I can find for AT&T, unlocked, sense, Google, etc will run without failing.
Can anyone please walk help me find the necessary files, fix any settings already in the phone and walk me through updating/changing the phone to US AT&T or, preferably, Sense Marshmallow.
Thanks.

dale_j said:
I have a 'new in the box' M8 that appears to be an AT&T UK model
Click to expand...
Click to collapse
I think you mean "US model" as there is no AT&T UK model.
dale_j said:
(bootloader) version-main: 3.28.401.9
(bootloader) modelid: 0P6B63000
OTA does not show any updates available (I am in the USA), and none of the RUU or ROM.zip files I can find for AT&T, unlocked, sense, Google, etc will run without failing.
Click to expand...
Click to collapse
I think your main problem is that your firmware number (3.28.401.9) doesn't jive with your model ID (0P6B63000), therefore preventing any OTA updates, or RUUs from being run.
dale_j said:
Can anyone please walk help me find the necessary files, fix any settings already in the phone and walk me through updating/changing the phone to US AT&T or, preferably, Sense Marshmallow.
Click to expand...
Click to collapse
Is AT&T your carrier. And do you want the AT&T branded stock ROM, or no?
---------- Post added at 10:06 AM ---------- Previous post was at 10:05 AM ----------
You should also delete your IMEI and serial number from your post, as these are private info.

redpoint73 said:
I think you mean "US model" as there is no AT&T UK model.
I think your main problem is that your firmware number (3.28.401.9) doesn't jive with your model ID (0P6B63000), therefore preventing any OTA updates, or RUUs from being run.
Is AT&T your carrier. And do you want the AT&T branded stock ROM, or no?
---------- Post added at 10:06 AM ---------- Previous post was at 10:05 AM ----------
You should also delete your IMEI and serial number from your post, as these are private info.
Click to expand...
Click to collapse
According to HTC's warranty site, the serial belongs to an AT&T phone from the UK/Europe.
My carrier is US AT&T through NET10, so I need the AT&T APN info, but would prefer either plain vanilla android or HTC's SENSE version, and can edit that info once the phone is running Marshmallow.
Following another thread here, I tried using adb shell to change the MID to 0p6b61000. The shell went to a $ prompt and not the # prompt the instructions called for. I tried 'us' as suggested and got a 'not found' response. I still tried the lengthy command listed, and got a restricted/locked/no permission/etc. (can't remember exact wording) response.
I joined HTC's DEV, so I could unlock the bootloader, and tried everything above and all the ROM files I have both as RRU and as ROM.zip on the SD card with the bootloader locked, unlocked and again with it relocked.
I did try editing out the serial and imei yesterday. I will try again after replying here.
I have an email into HTC's tech and so far no response from them.
Thanks again,
Dale

dale_j said:
According to HTC's warranty site, the serial belongs to an AT&T phone from the UK/Europe.
Click to expand...
Click to collapse
Probably a mistake. No AT&T in UK or Europe. And your product code m8_ul_ca signifies AT&T US or US Developer's Edition.
Doesn't really matter, in any case.
dale_j said:
My carrier is US AT&T through NET10, so I need the AT&T APN info, but would prefer either plain vanilla android or HTC's SENSE version, and can edit that info once the phone is running Marshmallow.
Click to expand...
Click to collapse
Based on that description, I'd suggest the US Developer's Edition RUU (6.12.1540.4). It is unbranded Sense, but already has the proper radio bands and APN setup for AT&T.
dale_j said:
Following another thread here, I tried using adb shell to change the MID to 0p6b61000. The shell went to a $ prompt and not the # prompt the instructions called for. I tried 'us' as suggested and got a 'not found' response. I still tried the lengthy command listed, and got a restricted/locked/no permission/etc. (can't remember exact wording) response.
Click to expand...
Click to collapse
Is the phone rooted? It needs to be, to change the MID. I'm guessing that is why you aren't getting the # prompt.
dale_j said:
I joined HTC's DEV, so I could unlock the bootloader, and tried everything above and all the ROM files I have both as RRU and as ROM.zip on the SD card with the bootloader locked, unlocked and again with it relocked.
Click to expand...
Click to collapse
If using the SD card install method, did you rename the RUU to 0P6BIMG.zip
With s-off, the RUUs will work whether the bootloader is locked or not. So it's kind of a waste of time changing it back and forth. I'd suggest leaving it unlocked, as that gives you the most options.
Also, most the Marshmallow RUUs for the US versions, have a weird requirement, where the firmware (hboot, radio, etc.) need to be updated, before the RUU will work.
So my suggestion would be:
1) Root and fix the MID to be AT&T/US Dev Edition
2) Flash the 6.12.1540.4 firmware from here: https://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
3) Flash the 6.12.1540.4 RUU

What is the easiest/safest way to root my M8?
Thanks,
Dale

dale_j said:
What is the easiest/safest way to root my M8?
Click to expand...
Click to collapse
With bootloader unlocked, flash TWRP 3.1.1 using fastboot. Then flash SuperSU 2.82 in TWRP.
https://twrp.me/devices/htconem8gsm.html
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703

Thank you for all the help.
I have Marshmallow DEV running on the new M8, but still have a couple questions and possible help issues.
Current getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.1540.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US002
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Should the bootloader version still be the same and not a newer version?
Is there a newer DEV version? AT&T ver is 6.2.................. DEV is 6.1...............
Will there be any connection issues with the baseband not matching the 4.0.U605................... version in my original AT&T M8?
Will it matter that the security patch level on the original AT&T M8 is 2016-13-01 and the new (now DEV) M8 is 2015-12-01?
What is the best free app to transfer everything between the phones?
I tried HTC's builtin app, but custom ringtones, alarms, WiFi connections and PWs, custom wallpapers and about 60% of my phone contacts did not transfer. I ran the app twice.
I also could not get the NFC transfer to work. WiFi, BT and NFC were all on on both phones, however following the instructions on the screen (tap and hold backs together until sound signals) did nothing with several tries and holding them together in excess of 5 minutes.
Thanks again for all the help,
Dale

My responses below, in red font:
dale_j said:
Is there a newer DEV version? AT&T ver is 6.2.................. DEV is 6.1...............
No newer Dev Ed version. 6.12 is the last (final) one. I wouldn't have suggested it, if there was a newer one.
The difference in the numbering between Marshmallow AT&T versus Dev Ed is probably not too significant. Probably based on the same software base, just that AT&T takes so darned long to test and approve the updates (plus adding their branding and bloat), so it was one of the last MM updates to be released. In other words, not really a newer "version" in any significant way. Just released later.
Will there be any connection issues with the baseband not matching the 4.0.U605................... version in my original AT&T M8?
I wouldn't expect any. AT&T and Dev Ed are supposed to support the same bands. I've often wondered why AT&T version uses the strange baseband numbers (most other use 1.25, 1.29, etc.). But again, I suspect the actual differences are minimal or none.
Will it matter that the security patch level on the original AT&T M8 is 2016-13-01 and the new (now DEV) M8 is 2015-12-01?
Not sure if the patch date for the Dev Ed is correct. It would mean the patch level was almost a year old (when the RUU was released Dec. 2015), which is a bit excessive.
In the big picture, we are using Android versions with patch levels that are over a year old (unless you run an AOSP based custom ROM). So technically, there are more vulnerabilities (newer patch level is better). But how much difference this actually makes in practice is debatable.
In any case, I wouldn't personally run the AT&T stock ROM, just because it has a newer patch level (if that is what you are thinking). I personally hate the AT&T branding and crappy bloatware, it just wouldn't be worth it to me.
What is the best free app to transfer everything between the phones?
I tried HTC's builtin app, but custom ringtones, alarms, WiFi connections and PWs, custom wallpapers and about 60% of my phone contacts did not transfer. I ran the app twice.
I would recommend storing your contacts via Google. This way, it's on the cloud, and always backed up (automatically, and requires no additional action by you), and easily accessed. When you setup a new Android phone, and login to your Google account, your contacts will automagically just sync to the phone. It's one of the great things about Android. Doing it this way, might not be for everyone (for instance, you might have work and personal contact you like to keep separate). But I personally love it.
Files such as ringtones and wallpapers can be easily migrated. Literally, you can just copy and paste them. But you'll need an intermediary place to put them. Whether that be on a computer, cloud, etc. is up to you. It can be as simply as connected the "old" phone to a PC, copy/paste the desired files. Then connect the "new" phone to PC, and drag/drop the files to the correct locations.
WiFi connections and passwords, I don't usually migrate. I don't have that many of them, so I literally just enter them in again, when migrating to a new phone. Titanium Backup (requires root) and some other apps can migrate such data (as well as apps and app data).
Click to expand...
Click to collapse

Thanks again.
That is largely what I was thinking/hoping.
I also hate bloatware, and wanted the DEV edition instead of a branded AT&T (or anyone else's) version.
Unrelated to this thread:
For what I do, I really like the M8, plus it is within my price range now that it is a few years old. Have you tried any of the custom Android 7 ROMs? If so, is there one you would recommend for the M8. I thought I would play around with the old phone and Nougat now that I have a good running phone again.
I love tinkering and challenges, so I am also going to try replacing the battery and charging port in the old phone. According to the couple YouTube videos I watched., it looks like it is well within the scope of my skill set.
Many thanks for your help with my M8, and any future help.
Dale

dale_j said:
Have you tried any of the custom Android 7 ROMs?
Click to expand...
Click to collapse
I haven't. I have been mostly a Sense user on this device, therefore it's stuck on Marshmallow.
There is a thread in the M8 General forum section, discussing ROM recommendations. You might check that out.

Sprint M8 Stock Roms

Hi, I made this post in the Sprint section a few days ago, but figured I'd post here as well to see if maybe this section has more traffic. If that's not allowed, I apologize in advance.
https://forum.xda-developers.com/sprint-htc-one-m8/help/stock-roms-t3669676
Basically, I'm looking for a stock rom for Sprint that would work with 1.54.651.8 firmware. All the links I can find on the forums seem to be dead.
Alternatively, a nandroid backup or way to extract the rom from the 1.54.651.8 RUU I do have (but won't successfully flash for whatever reason)
Any help would be appreciated. Thanks!

A custom ROM would need to support the Sprint M8, and be based on 4.4.2. Most any newer (newer than KitKat) ROMs will suffer major incompatibility with your ancient firmware, including extreme long boot time or no boot, and broken WiFi.
Suggest stocking with updating the firmware. Is the device s-on or s-off?
Problems with the RUU while "sending" are usually on the PC side. Try to re-install HTC drivers, try another USB port (USB 2.0 works best), and try another cable. Or even try another PC if possible.

Yeah I was able to find one custom 4.4.4 ROM (It was labelled 4.4.2, but it works so I guess it's close enough). There are just a few issues with it and I've always been more of a stock person anyway so I'd rather use a stock rom if I have the option.
As far as updating firmware, I am S-ON - I only originally rooted for a wifi hotspot app, so I didn't have a need to go S-OFF.
I guess it wouldn't hurt to give the RUUs a shot on a different computer. I'll just have to talk a friend into letting me install the drivers and giving it a go. One thing I'm not sure about - is it safe to go straight to the lastest RUU on HTC's site? I was willing to try it back when I had no rom at all, but now that I have a custom rom that mostly works, I'd rather not totally crap the bed.

Fuhcue said:
I guess it wouldn't hurt to give the RUUs a shot on a different computer. I'll just have to talk a friend into letting me install the drivers and giving it a go. One thing I'm not sure about - is it safe to go straight to the lastest RUU on HTC's site?
Click to expand...
Click to collapse
You can "skip" RUUs, and go the latest. However, you may (probably) need to update to the Marshmallow firmware anyway, before you can RUU. There is a strange limitation on most US version M8, where the RUU will fail with Error 155, if you try to go to Marshmallow from any former version (be it Kitkat or Lollipop) without first updating the firmware.
So the steps would be:
1) Relock bootloader
2) Flash to Marshmallow signed firmware (Sprint), in fastbootRUU mode
3) RUU to Marshmallow
4) Unlock bootloader again
5) Flash TWRP, root, and do whatever mods you want
Seeing as RUU will also wipe the phone. All this might be more than you want to do, if you are fairly happy with the phone as it is.

redpoint73 said:
Seeing as RUU will also wipe the phone. All this might be more than you want to do, if you are fairly happy with the phone as it is.
Click to expand...
Click to collapse
I don't so much mind the wipe, but I am a bit nervous about updating the firmware since that sounds like it could leave me in limbo if the RUU still didn't want to work for whatever reason. I guess I'll search around for where I can get that firmware and the procedure of how to do it and see how comfortable I feel with it in case I go that route.
If I knew for sure that it would all go through, I'd be fine with the reset. But that seems to take the attractive part of the RUU away in that it's no longer an "all in one" or one step process. (Not counting unlocking/relocking the bootloader since that's a quick and easy thing).

Fuhcue said:
I guess I'll search around for where I can get that firmware and the procedure of how to do it and see how comfortable I feel with it in case I go that route.
Click to expand...
Click to collapse
The firmware is posted in the same thread as the RUUs. And instructions on how to flash, as well.
https://forum.xda-developers.com/showthread.php?t=2729173
Fuhcue said:
If I knew for sure that it would all go through, I'd be fine with the reset. But that seems to take the attractive part of the RUU away in that it's no longer an "all in one" or one step process. (Not counting unlocking/relocking the bootloader since that's a quick and easy thing).
Click to expand...
Click to collapse
You can also opt for the Lollipop RUU (does not require flashing the firmware first). While not the latest, it's obviously more updated than what you presently have. And most of the current MM ROMs should work with LP firmware. There isn't much difference in the firmware it seems, for LP versus MM. Much different from KK to LP, which causes the problems I mentioned earlier (if you try to run KK firmware with LP or MM ROMs).
For maximum compatibility, matching the firmware is usually best. But I was running LP firmware with MM ROMs for a while (was simply to lazy to flash the MM firmware or RUU).

Ok so it sounds like the easiest option for me at this point is to grab a Lollipop RUU and try to flash it from a new computer with a fresh install of all the drivers. That way, at least if it fails to recognize my phone like the newest one did, I'll still be where I currently am with the stock (though outdated) firmware and custom rom.
Otherwise, I'll keep my fingers crossed that someone stumbles across this thread that has a meticulous archive of all old stock Sprint roms
Thanks so much for all your help and answering my questions so quickly. Much appreciated.

Hi
This is Sudheer from INDIA
i got Sprint HTC one M8 Harman Kardon from my friend.
after jail break it's supported Indian GSM sims there after only outgoing calls are working incoming calls are not working.
after so much of web search i unlock boot loader using HTC All in one and i enter into twrp wipe all system,cache and data. now its' hang on startup white screen not booting. yesterday i am trying to install os from following reference.
forum.xda-developers.com/showthread.php?t=2729173
finally i got 155 error Unsupported RUU. Please help me to come out with step by step guide because i am new for installing android phones.

Krishna Sudheer said:
after jail break it's supported Indian GSM sims there after only outgoing calls are working incoming calls are not working.
Click to expand...
Click to collapse
"Jail break" is a term specific to only iPhones. There is not such thing as "jail break" on an Android device. I assume you mean s-off, or some other mod? I can only guess, if you don't use the specific and proper terminology.
Krishna Sudheer said:
after so much of web search i unlock boot loader using HTC All in one and i enter into twrp wipe all system,cache and data. now its' hang on startup white screen not booting.
Click to expand...
Click to collapse
All in one Toolkit is obsolete, you shouldn't be using it. It contains a very old version of TWRP which will cause problems for many folks.
System partition is the OS/ROM. Should be obvious, that wiping the system partition results in no OS. Can't boot to an OS that isn't there any more. If you didn't know what the result would be from wiping a partition, you should be touching it in the first place!!!! Those options are listed under "Advanced" for a reason. If you aren't an advanced user, don't mess with them, unless you are following directions form an experienced user, or know what the result is going to be.
Krishna Sudheer said:
forum.xda-developers.com/showthread.php?t=2729173
finally i got 155 error Unsupported RUU. Please help me to come out with step by step guide because i am new for installing android phones.
Click to expand...
Click to collapse
Not enough info to know why the RUU failed. You linked a post with multiple RUUs, so we don't know which one you tried. We also don't know your current phone configuration.
Which version number RUU did you try? For HK version, you typically will need to flash the one that contains the digits "654". The RUU with digits "651" is for non-HK Sprint version. Assuming CID/MID has not been modified (which we don't know, if you don't provide more info).
Post specific info about your phone. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
If the phone is s-on, you need to lock it in order to RUU. I don't know if you are s-on of s--off.
You can't run a lower number (downgrade) RUU unless you have s-off. Again, I don't know what version number RUU you tried, your current version number on the phone, or whether you are s-on or s-off.

Hi Sir,
Thank you for replying. Sim Unlocked from mobile store. actually I also don't know witch method they are using to unlock. After unlocking network signals showing in GSM mode. When I am changing to LTE mode again signals disappeared. In GSM mode incoming calls are not working. SMS both incoming and outgoing working fine.
I tried to change CID and s-off but it's not working.
TWRP I used version v2.7.0.2 these recovery installed from all in one twrp (sprint). when i come back in to bootloader it will asking No OS installed are you sure you wish to reboot?
My mobile model is HTC one M8 HK (831C) Sprint Internal storage is 32GB.
I download and used to flash following files.
1. signed_6.20.654.3_firmware.zip
2.RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe
3.0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip
What was I do is
First Re-locked bootloader using with all in one and rename firmware as 0P6BIMG.ZIP then flash from SD Card Installed Successfully. Bootloader also showing OS version 6.20.654.3
Next using exe file "RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe" everything going well when the process bar reaching to 100% then it's showing error 155. I Checked the error guide provide by exe file there Unsupported RUU please try again with supported RUU.
Next using with ZIP file "0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip" flash from SD Card it will showing not enough memory but internal is full empty.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
Kindly check and do the needful. Let me know how to install OS and where witch rom I use to install.

My responses below in red font:
Krishna Sudheer said:
After unlocking network signals showing in GSM mode. When I am changing to LTE mode again signals disappeared. In GSM mode incoming calls are not working. SMS both incoming and outgoing working fine.
LTE is difficult (maybe impossible) to get working in cases where the device is not intended for your region/carrier (which I assume is the case, that you are not located in US, on the Sprint carrier). GSM should work (as you indicated) as well as 3G (HSPA) provided that your carrier uses a band(s) supported by the Sprint version M8
I tried to change CID and s-off but it's not working. I don't know what that means "it's not working". Most folks who say they have trouble with getting s-off, are trying the hopeless waste of time, which is trying to usethe long obsolete "free" s-off method of firewater. It's never going to work.
Also, you should also be careful here, when changing CID. Only use a Sprint CID, or SuperCID with a Sprint firmware/RUU. Trying to use any other firmware or RUU will result in a radio brick (possibly permanent).
TWRP I used version v2.7.0.2 these recovery installed from all in one twrp (sprint). when i come back in to bootloader it will asking No OS installed are you sure you wish to reboot? That version is too old (over 4 years) and you should have used current TWRP. This was probably caused by using the toolkit (which I mentioned is not advised anymore). Old versions of TWRP was not compatible with Sprint M8 (it had it's own "CDMA" version TWRP) and it probably caused the wrong partition to be overwritten.
What was I do is
First Re-locked bootloader using with all in one and rename firmware as 0P6BIMG.ZIP then flash from SD Card Installed Successfully. Bootloader also showing OS version 6.20.654.3 Try flashing firmware again, the number should show up in getvar all (below) under "version-main". Flashing firmware twice is usually a good idea.
Next using exe file "RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe" everything going well when the process bar reaching to 100% then it's showing error 155. I Checked the error guide provide by exe file there Unsupported RUU please try again with supported RUU.
Error 155 is common, if flashing a US Marshmallow RUU, without being on the matching firmware. Flashing firmware again, as indicated above, may solve it.
Next using with ZIP file "0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip" flash from SD Card it will showing not enough memory but internal is full empty.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: firmware number should appear here
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
Click to expand...
Click to collapse

Two days of messing up with my M8, just getting worse, need help!!!

Two days of trying to find a solution here on xda and always banging my head in dead links and a load of information to try to understand I now have ended up with a hopefully not bricked device, I'm just stuck and need help.
This is the output of "fastboot getvar all" now.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA4A8SF00188
(bootloader) imei: 990004997721794
(bootloader) imei2: Not Support
(bootloader) meid: 99000499772179
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
This is the different lines in the output of the "fastboot getvar all" before
Code:
version-baseband: 1.12.20.1211
version-main 4.21.512.4
commitno-bootloader: 205bdca3
What I did was flashing "unsigned_firmware_6.12.401.4" and to make that work I had to change one line inside the android-info.txt from modelid: 0P6B10000 to modelid: 0P6B20000.
I'm not shure when the trouble started, and after two days of testing I don't remember all I did or not. exactly but I started to try a couple of different roms and the trying to go back to backup made by twrp "twrp-3.1.1-0-m8" there was sudden restarts and twrp got errors with carrier partition, I changed to an older twrp and got that working for a while but ten suddenly I got other errors from /cash and /data partitions when trying to whipe with twrp, tried different twrp:s trying to flash other firmwares and other roms and kernels, I'm stuck.
Now If I install lineage os, 14. .... the installation finish but with errors, I can start the phone but it will restart then and then, and if i shut it down it will not be shut down after some minutes it starts again by it self.
IF i go back to the backed up stock that I got the phone with it will do exactly the same with reboots and not being able to shut down properly.
Android version 4.4.4
HTC Sense-version 6.0
Program version 3.31.512.2
HTC SDK API level 6.25
PRI-version not available
PRL--version not available
Kernel version 3.4.g3e2305b [email protected]#1 SMP PREeMPT
Basebandvesion not available
Versionnumber 3.31.512.2 CL39569 release-keyes.
he phone is only stable in bootloader and in twrp, the twrp for the moment is 2.8.0.
Excuse me for messing up, but what shall I do now?
My goal is a working LineageOS on the phone
Edited: Oh, I forgot to tell that I prefer to use Linux when working on the phone. Somewhere I have a rarely used win10 machine also if needed.

You have a peculiar version of the M8, which is know as LRA (a Verizon variant). This is one of the "CDMA" M8 variants, which supports the Verizon LRA CDMA network (in addition to GSM, HSPA, LTE) and it differs from most other M8 versions. Therefore you can NOT flash firmware from any other version M8, such as the Euro firmware currently installed. The radio is not compatible, results in a radio brick, and that is probably why you have carrier partition errors.
Try flashing the proper RUU for LRA, and only this one: https://forum.xda-developers.com/showpost.php?p=66044439&postcount=37
I can't personally vouch for the above RUU. But I think others have verified it works on their LRA device. Hopefully, your phone boots after that, and the cell network functions. If so, you can install TWRP 3.1 (or at least 2.8.7) and a Verizon-compatible ROM. I don't know if Lineage qualifies, so I'll leave that up to you to research.

redpoint73 said:
You have a peculiar version of the M8, which is know as LRA (a Verizon variant). This is one of the "CDMA" M8 variants, which supports the Verizon LRA CDMA network (in addition to GSM, HSPA, LTE) and it differs from most other M8 versions. Therefore you can NOT flash firmware from any other version M8, such as the Euro firmware currently installed. The radio is not compatible, results in a radio brick, and that is probably why you have carrier partition errors.
Try flashing the proper RUU for LRA, and only this one: https://forum.xda-developers.com/showpost.php?p=66044439&postcount=37
I can't personally vouch for the above RUU. But I think others have verified it works on their LRA device. Hopefully, your phone boots after that, and the cell network functions. If so, you can install TWRP 3.1 (or at least 2.8.7) and a Verizon-compatible ROM. I don't know if Lineage qualifies, so I'll leave that up to you to research.
Click to expand...
Click to collapse
YEEEES thank you very much redpoint73, your answer led me to the solution. I got the phone back working
It didn't really work with the direct solution you pointed at (I don't know why), but after I red the whole thread RUU for bluegrass cellular variant I found a solution. There is a link to OTA
, I downloaded that, extracted the firmware from the zip and flashed it to my phone. Now it feel like new again. I'm not sure everything is back to normal but the version-baseband is back to where it started, the same with the version-main, but the bootloader? ie the commitno-bootloader is not changed back, will probably not only flashing firmware but so far i'ts working good. I just restored my lineageOS from previous backup.
I have wifi, radio and gps working and the lineageOS seams to work very well, maybe their version of M8 includes all versions?
Thank you again and again redpoint73

vildevilde said:
It didn't really work with the direct solution you pointed at (I don't know why), but after I red the whole thread, I downloaded that, extracted the firmware from the zip and flashed it to my phone. Now it feel like new again.
Click to expand...
Click to collapse
Not sure why the RUU didn't work, either. If the firmware from the OTA worked, the RUU should have worked. But RUU can be more finicky to things on the PC side, such as Windows version, if Visual C++ is installed, USB ports (2.0 vs. 3.0), etc. So nice job, working out a solution that worked.
vildevilde said:
I'm not sure everything is back to normal but the version-baseband is back to where it started, the same with the version-main, but the bootloader? ie the commitno-bootloader is not changed back,
Click to expand...
Click to collapse
The bootloader (3.19.0.0000) isn't different between LRA and Euro, or for that matter Lollipop versus Marshmallow. And since the firmware installed successfully, the bootloader would most likely match everything else installed by the firmware.zip (such as radio).
In other words, the bootloader number looks fine.
vildevilde said:
I just restored my lineageOS from previous backup.
I have wifi, radio and gps working and the lineageOS seams to work very well, maybe their version of M8 includes all versions?
Click to expand...
Click to collapse
I'm not a Lineage user on this device, so like I said before, I don't know either way whether it supports your LRA version M8.
If everything works on Lineage, I'd say it must support your LRA version device.

redpoint73 said:
Not sure why the RUU didn't work, either. If the firmware from the OTA worked, the RUU should have worked. But RUU can be more finicky to things on the PC side, such as Windows version, if Visual C++ is installed, USB ports (2.0 vs. 3.0), etc. So nice job, working out a solution that worked.
The bootloader (3.19.0.0000) isn't different between LRA and Euro, or for that matter Lollipop versus Marshmallow. And since the firmware installed successfully, the bootloader would most likely match everything else installed by the firmware.zip (such as radio).
In other words, the bootloader number looks fine.
I'm not a Lineage user on this device, so like I said before, I don't know either way whether it supports your LRA version M8.
If everything works on Lineage, I'd say it must support your LRA version device.
Click to expand...
Click to collapse
Yes, I'm using this as my daily phone now. Running LOS with microG support and everything works very good, easy updates every second day and no problems,