Develop Bugs

Verizon M8 CM12.1 - 4G/GPS not working

Hey everybody,
Don't know if this is in the right place, but hopefully you all can direct me to the right place if need be.
I've got a Verizon M8 with S-OFF running the relatively recent Cyanogenmod 12.1 snapshot. All was well until about a week ago. I was having some issues with not getting 4G LTE reception prior to this, but about a week ago it completely died. I'm in the middle of a major city, where I should have no problem getting 4G reception. My phone is only on 3G at all times, and sometimes loses connection completely. Along with this, my GPS will lock initially get a first signal but not lock on at all.
I've tried clean flashing CM again, going back to complete Verizon stock using the HTC RUU, factory resetting, etc. I even went to the Verizon store and tried a new SIM card. Nothing has helped or changed this issue. Nobody else in my area is having any problems with Verizon.
I'm really unsure what to do. Is my phone completely borked? Is there any diagnostic utility I can run in order to test my phone's network ability? I was reading earlier about some "secret codes" to put in, but am unsure.
Thanks in advance for all of your help.
Sent from my m8wl using XDA Free mobile app

You'll need to RUU back to 4.2. Its the only way to fix it and no you won't loose your unlock or s-off by doing it. If your not fermiliar with RUU, its discussed in the forum.

I'm having the same problem. I found this page:
http://www.htcdev.com/devcenter/downloads
But it only shows as far back as 4.4.2. Is that what I should use? If not, could you point me to the right file? Thanks!

komi_9 said:
I'm having the same problem. I found this page:
http://www.htcdev.com/devcenter/downloads
But it only shows as far back as 4.4.2. Is that what I should use? If not, could you point me to the right file? Thanks!
Click to expand...
Click to collapse
Not sure, (so you should confirm first) but I think the previous person mean software number 4.20.531, not Android 4.2. There is no Android 4.2 on this phone, and downgrading to Android 4 is not a good idea, since CM12 will not actually flash if you downgrade the hboot.
Further, you wont' find an official Verizon RUU on the HTC Dev website. I think the previous person meant the "hacked" RUU posted here: http://forum.xda-developers.com/showthread.php?t=2727831
But again, you should confirm that is what was meant. Hopefully, bigeddthemonk can clarify.

I'm on Sprint, so they have my RUU. If I did go back to 4.4.2, should that work OK? Like will it break my phone at all? And will I just be able to upgrade everything back up to restore my CM12.1?
Right now I can't get LTE or GPS working, so I'm pretty desperate to try something, so long as there's some chance it might work.

komi_9 said:
I'm on Sprint
Click to expand...
Click to collapse
That's why folk on here need to stop posting "I have the same problem" when you in fact do not have the same conditions. And in fact, there are so many variables (carrier variants, different firmwares, different custom ROM, etc. etc. etc) that the conditions will never be exactly the same. So literally, typing "I have the same problem" on XDA is a waste of time and means nothing.
If you want real help, always list all the specifics when asking for assistance: CID, main version, hboot, TWRP version, etc. Its recommended to do a getvar all, and post the output (delete IMEI and serial numbers) as that takes care of a whole lot of the specifics.
komi_9 said:
If I did go back to 4.4.2, should that work OK? Like will it break my phone at all? And will I just be able to upgrade everything back up to restore my CM12.1?
Click to expand...
Click to collapse
What I said before still applies. You downgrade hboot below 3.19, and CM12.1 won't flash. So that will be broken. If you are then going to "upgrade" back (you need to explain specifically what you mean by that, as its not clear), what was the point in downgrading, anyway?
I don't ever recommend "downgrading" that far down to an Android version that has been obsolete for a year and a half. And again, I don't think downgrading is actually what the previous post meant.
You might try the current Lollipop Sprint RUU.

I'm been busy with power outages and stuff, so It's taken me a while to get back to this. And sorry for being non-specific before.
Here's the results of getvar all (sans what you recommended):
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.25.651.18
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: XXXXXXXXXXXXXXXXXXXX
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_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: 0f94b3b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
redpoint73 said:
What I said before still applies. You downgrade hboot below 3.19, and CM12.1 won't flash. So that will be broken. If you are then going to "upgrade" back (you need to explain specifically what you mean by that, as its not clear), what was the point in downgrading, anyway?
Click to expand...
Click to collapse
I just don't understand how this all works. I have this idea of getting back to some golden version of stock and then running GPS and LTE and seeing if it works. Then I'd do whatever steps I need to do to get back to CM12.1 because that what I like running. I'm hoping that will fix it, but I'm not sure. Right now, LTE and GPS just don't work and I have no idea why. At first, it was just LTE that was broken, but in my various efforts to fix that, GPS is now broke as well.
redpoint73 said:
You might try the current Lollipop Sprint RUU.
Click to expand...
Click to collapse
How do I know if it's Lollipop? I've successfully installed this one:
RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_4.25.651.18_Radio_1.09.20.0209_NV_SPCS_1.52_003_release_446215_signed_2
LTE did not work there. GPS was able to find my locations, but I didn't try to see if it was accurate enough to work for turn-by-turn navigation. After going back to CM12.1, GPS still doesn't work.
Also, is there a way to restore the factory lock on the phone? My one other option for fixing LTE was to use this stock install and take it to a Sprint store and ask them to fix it. I was worried that they would check if the factory lock was broken and then just refuse to help me.

komi_9 said:
How do I know if it's Lollipop? I've successfully installed this one:
RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_4.25.651.18_Radio_1.09.20.0209_NV_SPCS_1.52_003_release_446215_signed_2
Click to expand...
Click to collapse
The number "4.25.651..." means its Lollipop. The number "4" being the important one in this instance. HTC software 4.xx for the M8 corresponds to Lollipop. This fact is a rather esoteric one, it only applies to the M8; as HTC uses different hardware numbers for different devices; and doesn't relate to how Google or other phone manufacturers number their software versions. So you would only from experience or research.
komi_9 said:
LTE did not work there. GPS was able to find my locations, but I didn't try to see if it was accurate enough to work for turn-by-turn navigation. After going back to CM12.1, GPS still doesn't work.
Click to expand...
Click to collapse
Did LTE ever work on this phone, on your network? You are using Sprint as your provider?
komi_9 said:
Also, is there a way to restore the factory lock on the phone? My one other option for fixing LTE was to use this stock install and take it to a Sprint store and ask them to fix it. I was worried that they would check if the factory lock was broken and then just refuse to help me.
Click to expand...
Click to collapse
"Factory lock" doesn't mean anything particular, its not a commonly used term for this device. Do you mean make the bootloader locked? There is a method for this in the Development section. But it requries s-off. And you should also confirm it works for the Sprint version (before trying it) as the Sprint version has some significant peculiarities versus other M8 versions.
---------- Post added at 09:41 AM ---------- Previous post was at 09:37 AM ----------
komi_9 said:
I just don't understand how this all works. I have this idea of getting back to some golden version of stock and then running GPS and LTE and seeing if it works. Then I'd do whatever steps I need to do to get back to CM12.1 because that what I like running. I'm hoping that will fix it, but I'm not sure. Right now, LTE and GPS just don't work and I have no idea why. At first, it was just LTE that was broken, but in my various efforts to fix that, GPS is now broke as well.
Click to expand...
Click to collapse
I can't say I understand how the GPS "fix" for CM12 works either; and I mostly just jumped in on this thread to provide some basic knowledge regarding RUUs, software numbers, etc. I'm not a user of CM on this device, so again the help I provide is unfortunately limited. All I can recommend is keep reading, or post to the applicable thread, to see if you can obtain any further help or other "fixes".
I'm guessing that RUU to stock replaces some GPS library or other type files, that then is not wiped when you flash CM onto the system partition. But I'm just guessing there.
At least RUU'ing back to stock verifies the GPS hardware works, and eliminates that as the cause of your GPS problem.

redpoint73 said:
The number "4.25.651..." means its Lollipop. The number "4" being the important one in this instance. HTC software 4.xx for the M8 corresponds to Lollipop. This fact is a rather esoteric one, it only applies to the M8; as HTC uses different hardware numbers for different devices; and doesn't relate to how Google or other phone manufacturers number their software versions. So you would only from experience or research.
Click to expand...
Click to collapse
Ah. Thanks!
redpoint73 said:
Did LTE ever work on this phone, on your network? You are using Sprint as your provider?
Click to expand...
Click to collapse
Yes, LTE worked just fine for a little while, both on the original stock, and on CM12. Then it stopped working. At first it would make weird APN choices, and then I could go in there and switch it back to the Sprint APN. Then as part of flipping back and forth from stock, I reset the APNs, thinking it would undo anything I might have mistakenly done while fiddling with the settings. After this, the APN listing has been blank. In CM12, it says that APN settings are not available for this user. In stock, it just seems to go searching and failing for LTE over and over.
redpoint73 said:
"Factory lock" doesn't mean anything particular, its not a commonly used term for this device. Do you mean make the bootloader locked? There is a method for this in the Development section. But it requries s-off. And you should also confirm it works for the Sprint version (before trying it) as the Sprint version has some significant peculiarities versus other M8 versions.
Click to expand...
Click to collapse
Yes, bootloader locked. When I boot to the bootloader, it says that my phone is unlocked, and when I relock it, it says "relocked". So anyone looking there will know I've unlocked it (which I suppose it the point of this ). I was just wondering if I could restore it to the original factory lock so that one wouldn't be able to tell.
Basically this is for if I go to a Sprint store to get help with LTE, they don't just refuse me because of having an unlocked bootloader. But I don't want to spend to much work on restoring this until I know it's causing me trouble. If I do go to the Sprint store, I'll probably just restore with the RUU and see how it goes.
redpoint73 said:
I can't say I understand how the GPS "fix" for CM12 works either; and I mostly just jumped in on this thread to provide some basic knowledge regarding RUUs, software numbers, etc. I'm not a user of CM on this device, so again the help I provide is unfortunately limited. All I can recommend is keep reading, or post to the applicable thread, to see if you can obtain any further help or other "fixes".
I'm guessing that RUU to stock replaces some GPS library or other type files, that then is not wiped when you flash CM onto the system partition. But I'm just guessing there.
At least RUU'ing back to stock verifies the GPS hardware works, and eliminates that as the cause of your GPS problem.
Click to expand...
Click to collapse
I'll need to redo the RUU and then actually try navigating around. It's hard to tell if it's accurate enough when I'm just in one place. What other ROM do you suggest I try to see if this is CM dependent, or if it's something more basic on my phone?
Thanks for the help!

komi_9 said:
Yes, LTE worked just fine for a little while, both on the original stock, and on CM12. Then it stopped working. At first it would make weird APN choices, and then I could go in there and switch it back to the Sprint APN. Then as part of flipping back and forth from stock, I reset the APNs, thinking it would undo anything I might have mistakenly done while fiddling with the settings. After this, the APN listing has been blank. In CM12, it says that APN settings are not available for this user. In stock, it just seems to go searching and failing for LTE over and over.
Click to expand...
Click to collapse
I don't have much guidance here (again, not a CM user) except that when you return to stock, it should have the right Sprint APN. If not, try to enter the proper/current APN. I don't see any reason why it wouldn't work with the proper APN (aside from the unlikely event of a hardware failure).
komi_9 said:
Yes, bootloader locked. When I boot to the bootloader, it says that my phone is unlocked, and when I relock it, it says "relocked". So anyone looking there will know I've unlocked it (which I suppose it the point of this ). I was just wondering if I could restore it to the original factory lock so that one wouldn't be able to tell.
Click to expand...
Click to collapse
As I mentioned, there is a thread for making the bootloader flag read LOCKED. However, it requires s-off, and this is the only way to make it say LOCKED. Otherwise, it will only say RELOCKED, and that is intentional (as you've already seem to have figured out).
Also, if you decide to s-off and try this, you need to research and confirm this hack works for the Sprint version, as there are a good number of mods that don't work for Sprint (or may need to be modified). In particular, the command modifies a very specific memory block. And the partitioning on the Sprint version is very different from other M8 versions. Meaning you probably need a Sprint specific command, otherwise you risk a brick.
http://forum.xda-developers.com/showthread.php?t=2708571
komi_9 said:
I'll need to redo the RUU and then actually try navigating around. It's hard to tell if it's accurate enough when I'm just in one place. What other ROM do you suggest I try to see if this is CM dependent, or if it's something more basic on my phone?
Click to expand...
Click to collapse
Stock RUU is your best bet, really. Other ROMs that support the Sprint version should be fine. I'd tend toward Sense or GPE based ROMs; as these are based on stock HTC software, tend to be more reliable with things like GPS.

Thanks for the help. I think I'll just run the RUU and give Sprint a call. Hopefully that will work.

For my specific Sprint case (not Verizon like the OP), my solution was to use the RUU and take it to Sprint. They gave me a new Sim card. Now I have it restored to CM12.1 and it seems to be working.
Of course, this is the same point that I was when I initially started having problems. LTE worked, but then stopped working. I had a repeat of that once, and I restored back to the stock ROM (I had backed it up with TWRP) and ran updates. Now it's been a few days and LTE is still going strong. So I'm hopefully I'm past this issue.

Kinda F**ked Up Real Bad !

First Of all hey Guys ! Ive been i daily user of xda for years now ! and you all do a great a job !
I dont know from where to start ! i kinda messed up and ive been into sh*t for a while ! im tired of trying anymore !
Need your help guys , and this is the full story of what happend ! bare with me . its gonna be a bit a little long !
2 months ago i buy A Htc One M8 from a guy that lived in thailand ! , m8 was a fantasy for a while now and i did find it with a good price ! so i said okey im gonna put my saving in it and get it !
after a pruchase it i faced the first problem and with it start it a chain of problems that put me into hell
I was getting only EDGE ! No 4G / No 3G ! Only slow af EDGE no matter what config a change !
**To Get Things Clear** Up to this Point Phone Work S-OFF , Bootloader Unlocked , Lineage rom, and with TWRP 3.0**
so I tell okey im gonna fix this ! i searched for a while and find that m8 only work in same region that phone brought from ! the phone from thailand and i live in west africa !
first i tried the diag mode ! but i failed , No Code or command will let me into diag mode !
Then i come uppon this thread trying to unlock all bands :
https://forum.xda-developers.com/htc-one-m8/general/how-to-convert-cdma-m8-sprint-vzw-gsm-t3303812
i did Everything then When I try flash a new costum rom everytime i go to recovery mode it bring back to bootloader ! i said wtf ! what happend !?
i flashed twrp agian with fastboot .. still wont boot into recovery !
after trying so many twrp ! only one work ! **twrp-2.8.1.0-m8_wlv.img**
i was like okey , an older twrp ! but no problemo ! lets try to flash a new rom
And when i enter recovery mode i was hit by the next problem ! ... Cant mount data , system and i think cache ! it was cant mount problem !
okey how i fix this ? by doing this stupid video : https://www.youtube.com/watch?v=HQM6KIDr4-k
Now My Partitions are all missed up ! Cache Is bigger than system ffs ** Photos Below **
I Tried To Sideload GPe marshmellow rom as a last sulotion ! but that didnt work either ! stuck at htc logo !
I Just want My phone Back ! Help me fix my partions and get my twrp Back And flash a nice rom ! I really frustrated of all this ! i Have no warnety so i have to deal with ! and i never been this lost !
And One last thing I dont what My M8 Model is actually .. everytime i discover something that make go wait what !
dont say what a noob or smth , i check my model name and go by that , but there are differnt infos that make confused !
My Model Is M8_WLV ! i searched for that and apparently thats mean Verzion US ! But my Model On the Back (0P6B100) google tell me that it is M8 Unlocked worldwide ! I dont even know it was GSM or CMDA ! This confusing !
This Is Getvar ( mid and cid are modified )
(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: 3.28.605.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT43ESF01224
(bootloader) imei: XXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 99000499842424
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B2000000***************
(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 PHOTOS HERE **
https://imgur.com/a/XzYc4

It's a Verizon phone.
I can tell by your MEID (which you should delete by the way ~ the MEID is the same as the IMEI minus the last number).
I did a search using your MEID and it's a Verizon model. For your phone, the last number in you IMEI is "0"
The number on the back (0P6B100) is probably because the back cover was replaced when sent for repairs.

xunholyx said:
It's a Verizon phone.
I can tell by your MEID (which you should delete by the way ~ the MEID is the same as the IMEI minus the last number).
I did a search using your MEID and it's a Verizon model. For your phone, the last number in you IMEI is "0"
The number on the back (0P6B100) is probably because the back cover was replaced when sent for repairs.
Click to expand...
Click to collapse
thanks for your reply mate ! do you know any way to get my partitions right again ?

neyoatashi said:
i did Everything then When I try flash a new costum rom everytime i go to recovery mode it bring back to bootloader ! i said wtf ! what happend !?
i flashed twrp agian with fastboot .. still wont boot into recovery !
after trying so many twrp ! only one work ! **twrp-2.8.1.0-m8_wlv.img**
i was like okey , an older twrp ! but no problemo ! lets try to flash a new rom
Click to expand...
Click to collapse
Wrong. Old TWRP version is a big problemo. Not compatible with current ROMs, and serious problems are sure to result.
Also, your firmware is old (as shown by main version 3.28.605.4 which is Kitkat) and therefore is not going to be compatible with current ROMs, either. You need to update your firmware (and TWRP version).
Also, you have the Verizon version M8. That versions uses a different kernel for most other M8 versions. So you should only use ROMs which specifically support the Verizon version. Otherwise, that is another reason a ROM won't boot.
My suggestion, would be to re-write all partitions to factory state using RUU. This will hopefully fix any memory corruption issues, as well as update you to the latest firmware.
https://forum.xda-developers.com/ve...zw-m8-master-ruu-firmware-collection-t2946473
Then go from there to get 3G working, flash latest TWRP (3.1 or 3.2 just came out a few days ago). etc.
neyoatashi said:
My Model Is M8_WLV ! i searched for that and apparently thats mean Verzion US ! But my Model On the Back (0P6B100) google tell me that it is M8 Unlocked worldwide ! I dont even know it was GSM or CMDA ! This confusing !
Click to expand...
Click to collapse
You can't go by what is on the back cover. We've frequently seen the back covers swapped, US versions in particular, to remove the carrier logos. In this case, the back cover was swapped to remove the Verizon logo.
---------- Post added at 01:26 PM ---------- Previous post was at 01:18 PM ----------
neyoatashi said:
I was getting only EDGE ! No 4G / No 3G ! Only slow af EDGE no matter what config a change !
so I tell okey im gonna fix this ! i searched for a while and find that m8 only work in same region that phone brought from ! the phone from thailand and i live in west africa !
Click to expand...
Click to collapse
This isn't strictly true, that "the M8 will only work for the same region it was bought". The Verizon version is SIM unlocked out of the box. Even if not, s-off gives SIM unlock. So from there, it's a matter of whether the M8 version supports the proper bands (used by your local carrier) for 3G or not.
What band (or bands) does your carrier use for 3G?
I wouldn't get your hopes up about 4G (LTE). It's proven very difficult (maybe impossible) to get the M8 working in another region on LTE.
But 3G may be possible.

redpoint73 said:
Wrong. Old TWRP version is a big problemo. Not compatible with current ROMs, and serious problems are sure to result.
Also, your firmware is old (as shown by main version 3.28.605.4 which is Kitkat) and therefore is not going to be compatible with current ROMs, either. You need to update your firmware (and TWRP version).
Also, you have the Verizon version M8. That versions uses a different kernel for most other M8 versions. So you should only use ROMs which specifically support the Verizon version. Otherwise, that is another reason a ROM won't boot.
My suggestion, would be to re-write all partitions to factory state using RUU. This will hopefully fix any memory corruption issues, as well as update you to the latest firmware.
https://forum.xda-developers.com/ve...zw-m8-master-ruu-firmware-collection-t2946473
Then go from there to get 3G working, flash latest TWRP (3.1 or 3.2 just came out a few days ago). etc.
You can't go by what is on the back cover. We've frequently seen the back covers swapped, US versions in particular, to remove the carrier logos. In this case, the back cover was swapped to remove the Verizon logo.
---------- Post added at 01:26 PM ---------- Previous post was at 01:18 PM ----------
This isn't strictly true, that "the M8 will only work for the same region it was bought". The Verizon version is SIM unlocked out of the box. Even if not, s-off gives SIM unlock. So from there, it's a matter of whether the M8 version supports the proper bands (used by your local carrier) for 3G or not.
What band (or bands) does your carrier use for 3G?
I wouldn't get your hopes up about 4G (LTE). It's proven very difficult (maybe impossible) to get the M8 working in another region on LTE.
But 3G may be possible.
Click to expand...
Click to collapse
I did get my phone back to working again ! its seems that my mid was 4 zeros longer ! and by knowing how hex and shell commands work i was able to fix it ! then was able to flash twrp 3.1 and flash a vzw sense 7 based on stock verzion costum rom !
now the only problem is that annoying edge !
supported 3g bands in my country are B1 (2100) And B8 (900 GSM)
im trying to unlocking my bands by DFS but thats seems to do nothing actually ! if this wont do nothing i will flash modem bins from older roms !
and thank you for reply mate ♥

neyoatashi said:
now the only problem is that annoying edge !
supported 3g bands in my country are B1 (2100) And B8 (900 GSM)
im trying to unlocking my bands by DFS but thats seems to do nothing actually ! if this wont do nothing i will flash modem bins from older roms !
Click to expand...
Click to collapse
The Verizon version M8 should support 3G bands 900 and 2100 out of the box. So you shouldn't need to mess with unlocking any bands. Are you sure you have APN properly configured for your carrier? And the SIM works in another device for 3G?
Whatever you do, do NOT flash any radios from any M8 version except Verizon. The Verizon version is not compatible with radios from other versions, and doing so will result in a radio brick!

redpoint73 said:
The Verizon version M8 should support 3G bands 900 and 2100 out of the box. So you shouldn't need to mess with unlocking any bands. Are you sure you have APN properly configured for your carrier? And the SIM works in another device for 3G?
Whatever you do, do NOT flash any radios from any M8 version except Verizon. The Verizon version is not compatible with radios from other versions, and doing so will result in a radio brick!
Click to expand...
Click to collapse
i get the idea from another one who had the same problem here in xda ! he was able to fix it by flashing older modem ! he has a verzion phone and flashed older verizon modem from a kitkat stock rom !
i checked those bands in DFS ! and 900 And 2100 was not checked ! so i checked them and write !
now once in so many tries when i select LTE/GSM/UMTS mode and LTE/WCMDA in Service Mode Hspa Go for a sec then i get disconnected ( Emergency calls only )
Im getting crazy here mate ! Maybe this is the night that my phone meet the wall in a beautiful strike

neyoatashi said:
i get the idea from another one who had the same problem here in xda ! he was able to fix it by flashing older modem ! he has a verzion phone and flashed older verizon modem from a kitkat stock rom !
Click to expand...
Click to collapse
It's worthy trying. As long as you stick with Verizon M8 radios, you should be relatively safe, and you can go back and forth to older or current (Marshmallow) radios. So there is minimal risk in trying. Although any radio or firmware flash should be taken seriously. There is always some risk. If for instance, anything goes wrong while writing radio, a permanent radio brick is possible. But again, the risk should be minimal.
But is your present main version due to trying another radio (Kitkat) or firmware? Since the number you show 3.28.605.4 is Kitkat firmware.
Were you ever on Lollipop or Marshmallow firmware (main version 4.xx or 6.xx, respectively)?

redpoint73 said:
It's worthy trying. As long as you stick with Verizon M8 radios, you should be relatively safe, and you can go back and forth to older or current (Marshmallow) radios. So there is minimal risk in trying. Although any radio or firmware flash should be taken seriously. There is always some risk. If for instance, anything goes wrong while writing radio, a permanent radio brick is possible. But again, the risk should be minimal.
But is your present main version due to trying another radio (Kitkat) or firmware? Since the number you show 3.28.605.4 is Kitkat firmware.
Were you ever on Lollipop or Marshmallow firmware (main version 4.xx or 6.xx, respectively)?
Click to expand...
Click to collapse
Number Means Nothing in this Phone ! I was Going back and forth between marshmellow and nogat ! but number tells its kitkat ! my phone is really missed up xDD
But Finnaly I Was Able to fix the problem ! after unlocking the 2 bands by DFS ! i did a clean Marshmellow costum rom flash ! ... Then i go to Service mode to select Lte/WCMDA mode ! H become to apear for sec The go Disconnected ! I was like oh Probebly This is the end ! But the whole trick was In Sercive mode ! I must select LTE/WCMDA mode And directly exit service mode before i get disconnected ! now my phone is stable on 3g for aout 24h now ! Im Happy with what i learned in this couple of days and what i achieved ! Thanks a lot for the support man ! And thanks for this wonderful site that provied people a platform to solve all kind of problems !
Peace ♥

neyoatashi said:
Number Means Nothing in this Phone ! I was Going back and forth between marshmellow and nogat ! but number tells its kitkat ! my phone is really missed up
Click to expand...
Click to collapse
The main version definitely means something. You just don't understand what it means.
The main version in getvar (also same as OS number on bootloader screen) is your firmware number, which refers to hboot, radio, etc. This is not the same as the ROM version; and firmware does not change when you flash a new ROM. You need to update (to Marshmallow) your firmware either by flashing signed (Verizon) firmware or Verizon RUU.
If you are flashing Marshmallow and Nougat ROMs, using your old Kitkat firmware; that may be the cause of your radio/band support issues. You need to update your firmware.

Help finding stock ROM

Hello guys.
I have the HTC one M8. in forums, i found that the htc_wlv references to verizon version, but my htc is not a verizon phone.
I tried to flash with verizon firmware, so that, i get some issues like getting verizon bootscreen (in my original firmware only htc one boot screen shown with a ring), getting warning message which says that "The SIM card is from an unknown source" and the main issue that only Edge network working, i have no 3G/4G.
Here is the
Code:
fastboot getvar all
output:
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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT43ESF01224
(bootloader) imei: 352090060253192
(bootloader) imei2: Not Support
(bootloader) meid: 99000499842424
(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!
I hope that you can help me to find the correct firmware.
and thanks

Your device seems to be Verizon.

lucyr03 said:
Your device seems to be Verizon.
Click to expand...
Click to collapse
May also be the LRA version, which is a variant of Verizon, and uses different RUUs and firmware. Might explain why some things are broken after flashing Verizon firmware.
But can't really say for sure if it's "normal flavor" Verizon or LRA, since the version main is wiped out in the getvar output. This is usually due to using an outdated version TWRP, or some custom ROMs.
---------- Post added at 09:27 AM ---------- Previous post was at 09:24 AM ----------
djamiirr said:
I tried to flash with verizon firmware, so that, i get some issues like getting verizon bootscreen (in my original firmware only htc one boot screen shown with a ring), getting warning message which says that "The SIM card is from an unknown source" and the main issue that only Edge network working, i have no 3G/4G.
Click to expand...
Click to collapse
But what was the condition before you flashed Verizon firmware? Any issues with 3G/4G or anything else wrong?
What exactly did you flash (version number, actual/exact file name) when you say "Verizon firmware"? As that term can mean half a dozen things or more. And did it install correctly (aside from the problems you stated), or did you get any error messages?
The firmware either didn't install correctly, or you did something else afterwards. Since version-main being blank in getvar is not a normal result after flashing firmware.

redpoint73 said:
May also be the LRA version, which is a variant of Verizon, and uses different RUUs and firmware. Might explain why some things are broken after flashing Verizon firmware.
But can't really say for sure if it's "normal flavor" Verizon or LRA, since the version main is wiped out in the getvar output. This is usually due to using an outdated version TWRP, or some custom ROMs.
---------- Post added at 09:27 AM ---------- Previous post was at 09:24 AM ----------
But what was the condition before you flashed Verizon firmware? Any issues with 3G/4G or anything else wrong?
What exactly did you flash (version number, actual/exact file name) when you say "Verizon firmware"? As that term can mean half a dozen things or more. And did it install correctly (aside from the problems you stated), or did you get any error messages?
The firmware either didn't install correctly, or you did something else afterwards. Since version-main being blank in getvar is not a normal result after flashing firmware.
Click to expand...
Click to collapse
Ok, first, thank you very much for your reply .
I have flashed an RUU from here https://forum.xda-developers.com/verizon-htc-one-m8/general/downgrade-s-sunshine-purposes-t3202237
My original phone firmware was perfect and i flashed it to remove root and some files on /system created by root apps (such as busybox) and 3G/4G were working smoothly.
I just feel that i flashed a wrong firmware with new added verizon bootscreen and no working 3G/4G.
i tried to flash revolution HD from here android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html but the phone enter directly to fastboot when i turned on the phone after flashing Revolution HD so that i returned to Verizon version to turn on my phone.
I have S-OFF, SuperCID and unlocked bootloader.
please help me what should i do? i'm very new to htc and this is my first experiance with this brand.
What should i do?

djamiirr said:
I have S-OFF, SuperCID and unlocked bootloader.
Click to expand...
Click to collapse
Did you do these yourself, or were any of these already done before you owned the phone?
If you aren't actually on the Verizon carrier, I'll assume the phone had some mods to it to "debrand" it prior to being owned by you (which we've seen on these forums a good number of times). The phone has probably also had it's back cover swapped to remove the Verizon logo. You may notice that the model number on the phone's back cover doesn't match what is given by getvar (with getvar being the more reliable information).
djamiirr said:
but the phone enter directly to fastboot when i turned on the phone after flashing Revolution HD so that i returned to Verizon version to turn on my phone.
Click to expand...
Click to collapse
Android Revolution ROM does not support the Verizon version M8, which uses a different kernel from most other M8 variants. You can try a ROM which specifically supports Verizon M8.
But I also suspect your SIM issue may be due to flashing the Verizon RUU on an LRA version phone (which breaks the radio). I can't be sure of this. So if flashing another ROM doesn't help, you may try the LRA RUU:
https://forum.xda-developers.com/showpost.php?p=66044439&postcount=37

redpoint73 said:
Did you do these yourself, or were any of these already done before you owned the phone?
If you aren't actually on the Verizon carrier, I'll assume the phone had some mods to it to "debrand" it prior to being owned by you (which we've seen on these forums a good number of times). The phone has probably also had it's back cover swapped to remove the Verizon logo. You may notice that the model number on the phone's back cover doesn't match what is given by getvar (with getvar being the more reliable information).
Android Revolution ROM does not support the Verizon version M8, which uses a different kernel from most other M8 variants. You can try a ROM which specifically supports Verizon M8.
But I also suspect your SIM issue may be due to flashing the Verizon RUU on an LRA version phone (which breaks the radio). I can't be sure of this. So if flashing another ROM doesn't help, you may try the LRA RUU:
https://forum.xda-developers.com/showpost.php?p=66044439&postcount=37
Click to expand...
Click to collapse
i successfully booted to Revolution HD by restoring only boot from verizon rom backup
i have no verizon logo on my cover
i have no idea about default SuperCID cause i purshased a used phone
can i flash Developers Edition radio on this phone? or can enter to DM service to add 3,4 LTE band?? cause ##3424# didn't work.
and thanks.

djamiirr said:
i successfully booted to Revolution HD by restoring only boot from verizon rom backup
Click to expand...
Click to collapse
Yeah, so you replaced the kernel with a Verizon one. So that is exactly in line with what I said about compatible kernels. I said to stick to Verizon compatible ROMs, as I didn't want to further confuse the issue to someone who clearly does not fully understand the nuances of this particular (Verizon or LRA device).
djamiirr said:
can i flash Developers Edition radio on this phone?
Click to expand...
Click to collapse
Doing so will radio brick the phone.
Your device is only compatible with either Verizon or LRA radio, RUU or firmware. And Verizon radio (RUU, or firmware) only for the Verizon version. LRA radio (RUU, firmware) only for the LRA version. Meaning that also the Verizon and LRA radios/RUU/firmware are not interchangeable, from what we have seen.
Flashing radio, RUU or firmware for any other version M8 will result in a radio brick. The radios are not compatible. The radio brick is sometimes fixed by flashing the right RUU, but sometimes it is permanent. And nothing good can come from flashing the Dev Ed radio, so do NOT do it.
djamiirr said:
or can enter to DM service to add 3,4 LTE band?? cause ##3424# didn't work.
Click to expand...
Click to collapse
If you are getting SIM error messages, I think you have more going on that just band support. Again, as I already mentioned, I suspect you may have LRA version M8. Which might explain why things went wrong after flashing Verizon RUU. But I can't be completely sure you have the LRA version. If I were you, I would try the LRA RUU as I already posted. It is at your own risk, as any advice given on this forum. And there may be a slight risk, at that.

redpoint73 said:
If you are getting SIM error messages, I think you have more going on that just band support. Again, as I already mentioned, I suspect you may have LRA version M8. Which might explain why things went wrong after flashing Verizon RUU. But I can't be completely sure you have the LRA version. If I were you, I would try the LRA RUU as I already posted. It is at your own risk, as any advice given on this forum. And there may be a slight risk, at that.
Click to expand...
Click to collapse
So if i flash the LRA firmware can my radio be bricked permanently?

djamiirr said:
So if i flash the LRA firmware can my radio be bricked permanently?
Click to expand...
Click to collapse
It's a possibility, and I won't say there isn't. If the phone is in fact the LRA version, it's safe; as it's the firmware meant for your device. If it's the Verizon version, and you flash LRA firmware, it will cause problems, but probably reversible by flashing the Verizon firmware. Probably a lot safer than flashing "GSM" firmware (any other firmware for M8 but Verizon/LRA), which in most cases is even reversible.

redpoint73 said:
It's a possibility, and I won't say there isn't. If the phone is in fact the LRA version, it's safe; as it's the firmware meant for your device. If it's the Verizon version, and you flash LRA firmware, it will cause problems, but probably reversible by flashing the Verizon firmware. Probably a lot safer than flashing "GSM" firmware (any other firmware for M8 but Verizon/LRA), which in most cases is even reversible.
Click to expand...
Click to collapse
Ok i flashed the LRA version on my HTC but "Cellular network type" is still detected as "EDGE". i can pass/receive phone calls without problems. What should i do?? :crying:

djamiirr said:
Ok i flashed the LRA version on my HTC but "Cellular network type" is still detected as "EDGE". i can pass/receive phone calls without problems. What should i do?? :crying:
Click to expand...
Click to collapse
That is strange that you are getting only EDGE on the stock LRA and Verizon RUUs.
Are you sure you entered the APN info for your carrier correctly?
Do you know what band your carrier uses for 3G?
And LTE was also working before, it sounds like (Bands 3 and 4, from what you mentioned before).
---------- Post added at 11:45 AM ---------- Previous post was at 11:44 AM ----------
Also, are you still getting the error message "The SIM card is from an unknown source"?

redpoint73 said:
That is strange that you are getting only EDGE on the stock LRA and Verizon RUUs.
Are you sure you entered the APN info for your carrier correctly?
Do you know what band your carrier uses for 3G?
And LTE was also working before, it sounds like (Bands 3 and 4, from what you mentioned before).
---------- Post added at 11:45 AM ---------- Previous post was at 11:44 AM ----------
Also, are you still getting the error message "The SIM card is from an unknown source"?
Click to expand...
Click to collapse
I don't know which 3G bands in my coutry but as i said before LTE working bands in my coutry are 3 and 4
These are tsted firmwares/roms
* One_M8_4.16.401.10_stock_system_dump.zip
*0P6BIMG_M8_WL_M60_SENSE70_VZW_MR_VERIZON_WWE_6.21.605.3_HSM_Radio_1.14.20.0930_CNV_CNV_VZW_2.93_002_release_470486_signed
*0P6BIMG_M8_WL_L50_SENSE60_MR_LRA_US_4.21.512.4_Radio_1.12.20.1211_NV_VZW_2.11_002_release_429732_combined_signed_2_4_7
*RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 (exe RUU).
but no one of them working with 3G/4G :crying:

Verizon M8 support these 4G bands: LTE band 3(1800), 4(1700/2100), 7(2600), 13(700)
And these 3G bands: HSDPA 850 / 900 / 1900 / 2100

lucyr03 said:
Verizon M8 support these 4G bands: LTE band 3(1800), 4(1700/2100), 7(2600), 13(700)
And these 3G bands: HSDPA 850 / 900 / 1900 / 2100
Click to expand...
Click to collapse
Thank you, in my country, working lte bands are 3 and 4, but the phone didn't detect them and cellular network type is still detected as "EDGE". Is this a firmware issue?

djamiirr said:
Thank you, in my country, working lte bands are 3 and 4, but the phone didn't detect them and cellular network type is still detected as "EDGE". Is this a firmware issue?
Click to expand...
Click to collapse
In settings -> mobile data, what says at network type?

djamiirr said:
I don't know which 3G bands in my coutry
Click to expand...
Click to collapse
If you contact your local provider, they should be able to tell you.
Or tell us what country and carrier, and we may be able to look it up. But the most accurate answer will likely come from your provider.
Further comments below in red font:
djamiirr said:
These are tsted firmwares/roms
* One_M8_4.16.401.10_stock_system_dump.zip
This likely would not boot on your device, as this is the Euro system dump, which uses a kernel not compatible with the Verizon M8.
*0P6BIMG_M8_WL_M60_SENSE70_VZW_MR_VERIZON_WWE_6.21.605.3_HSM_Radio_1.14.20.0930_CNV_CNV_VZW_2.93_002_release_470486_signed
*0P6BIMG_M8_WL_L50_SENSE60_MR_LRA_US_4.21.512.4_Radio_1.12.20.1211_NV_VZW_2.11_002_release_429732_combined_signed_2_4_7
*RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 (exe RUU).
I clearly told you that this is a bad idea to try this (Dev Edition) RUU. Did you run it anyway, despite the warning?
Again, do not flash any other RUU, firmware or radio except those specifically for VZN or LRA!
Click to expand...
Click to collapse

lucyr03 said:
In settings -> mobile data, what says at network type?
Click to expand...
Click to collapse
It's global mode, if switch it to another type i will get no signal.
and if you talking about settings -> about -> network cellular network type shows only "EDGE"

redpoint73 said:
If you contact your local provider, they should be able to tell you.
Or tell us what country and carrier, and we may be able to look it up. But the most accurate answer will likely come from your provider.
Further comments below in red font:
Click to expand...
Click to collapse
Thaks for your reply, i'm living in Tunisia, and i want to unlock Orange and Ooredoo 3G/4G bands.
I finally made my phone detected as a port (COM3) using this method:
Code:
adb shell
su
setprop sys.usb.config mtp,mass_storage,adb,diag
but DFS software always showing "HTC Diagnosting Interface (COM3) device offline" when i double click on htc in main screen (screenshot attached).

djamiirr said:
Thaks for your reply, i'm living in Tunisia, and i want to unlock Orange and Ooredoo 3G/4G bands.
Click to expand...
Click to collapse
Based on the following website, the 3G bands used in Tunisia are 2100 and 900 Mhz: https://www.worldtimezone.com/gsm.html
These bands are already supported by your device, according to what lucry03 posted above (Post #13).
This leads me to believe the issue is not going to be solved by unlocking the bands in diag mode. But suggests to me, that the issue is related to APN, firmware or ROM.

redpoint73 said:
Based on the following website, the 3G bands used in Tunisia are 2100 and 900 Mhz: https://www.worldtimezone.com/gsm.html
These bands are already supported by your device, according to what lucry03 posted above (Post #13).
This leads me to believe the issue is not going to be solved by unlocking the bands in diag mode. But suggests to me, that the issue is related to APN, firmware or ROM.
Click to expand...
Click to collapse
Probably his device is sprint? Idk if it's possible to flash verizon on sprint, but they're CDMA both and maybe the partition scheme is the same.

Access to restricted LTE bands

Hi there,
I'll start with the essentials
(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: 6.20.502.5
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: xxxxxxxxx
(bootloader) imei: 35xxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000d f/e/lc/mbkp s1se=68
x
(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
all: Done!
So my phone is originally a Rogers from Canada and I am using it in India. This device does not pick up LTE bands in India and my assumption was that it was because of Rogers somehow restricting the phone as HTC m8 does in fact support the bands present in India (3,5,40). I assumed that if I flashed a different region RUU where those bands are supported then it would solve my problem. I had been running Lineage OS on it and over the weekend I get S-off, SuperCID. Then I went back to Rogers Stock through this thread https://forum.xda-developers.com/showthread.php?t=2710735
From there I went to AT&T latest RUU as mentioned in this thread https://forum.xda-developers.com/ht...ance-jio-volte-m8-t3566379/page9#post75932527
For this I needed to change my MID to 0P6B12000
On it, I flashed the RR 6.0
Now I hoped it would solve my problem but this has presumably locked my network to AT&T as no other carrier or network is getting recognized. I understand how I can revert to a different stock ROM, but doing that has still not helped the 4G problem. Would be great if someone could guide me on this. Have tried reading as many guides and how to but now I feel utterly confused.
[EDIT] - Have I bricked my Radio? Is there a sure way of finding that out?
Thanks in advance.

abhijin said:
This device does not pick up LTE bands in India and my assumption was that it was because of Rogers somehow restricting the phone as HTC m8 does in fact support the bands present in India (3,5,40). I assumed that if I flashed a different region RUU where those bands are supported then it would solve my problem.
Click to expand...
Click to collapse
We've seen a lot of folks on this forum, with a lot of trouble getting LTE working on devices not specifically intended for their region/carrier.
First of all, while the Snapdragon 801 chipset is capable of support most GSM, 3G, and LTE bands worldwide; the specific bands supported by the M8 model is determined by the radio baseband firmware.
For instance, in you case, I believe the Rogers version has the same band support as the AT&T version (due to the history of the countries and companies). In that case, the Rogers version only supports LTE bands 2,4,5,7, and 17. Of the LTE bands you desire, it only includes LTE band 5.
Additionally (as mentioned), we've seen many cases, where even on the proper firmware, folks have had trouble getting LTE on their local carrier (as mentioned, on devices not specifically intended for their region, but "converted" with RUU).
abhijin said:
Now I hoped it would solve my problem but this has presumably locked my network to AT&T as no other carrier or network is getting recognized.
Click to expand...
Click to collapse
Are you saying, after flashing the AT&T RUU, that no network is recognized at all, even voice service?
Flashing AT&T RUU does not carrier lock the phone (SIM lock). But lack of service, even voice service; may indeed indicate an issue with the radio baseband firmware.
abhijin said:
For this I needed to change my MID to 0P6B12000
(bootloader) modelid: 0P6B12000d f/e/lc/mbkp s1se=68
x
Click to expand...
Click to collapse
Your MID shouldn't look like that. Something went wrong when you tried to change it. Try the command again, to change it properly to AT&T MID, and let's see what the result is.

redpoint73 said:
We've seen a lot of folks on this forum, with a lot of trouble getting LTE working on devices not specifically intended for their region/carrier.
First of all, while the Snapdragon 801 chipset is capable of support most GSM, 3G, and LTE bands worldwide; the specific bands supported by the M8 model is determined by the radio baseband firmware.
For instance, in you case, I believe the Rogers version has the same band support as the AT&T version (due to the history of the countries and companies). In that case, the Rogers version only supports LTE bands 2,4,5,7, and 17. Of the LTE bands you desire, it only includes LTE band 5.
Additionally (as mentioned), we've seen many cases, where even on the proper firmware, folks have had trouble getting LTE on their local carrier (as mentioned, on devices not specifically intended for their region, but "converted" with RUU).
Click to expand...
Click to collapse
Yes I have come across this often in the forums. Still thought it is worth a shot.
redpoint73 said:
Are you saying, after flashing the AT&T RUU, that no network is recognized at all, even voice service?
Flashing AT&T RUU does not carrier lock the phone (SIM lock). But lack of service, even voice service; may indeed indicate an issue with the radio baseband firmware.
Click to expand...
Click to collapse
Yes, this is when the no network problem started. I tracked the radio baseband firmware (from this thread https://forum.xda-developers.com/showthread.php?p=52770589#post52770589) and flashed that too but with no luck. In fact the phone now has become extremely volatile, it reboots often, crashes often. Sometimes just tapping the home button will push it to reboot.
redpoint73 said:
Your MID shouldn't look like that. Something went wrong when you tried to change it. Try the command again, to change it properly to AT&T MID, and let's see what the result is.
Click to expand...
Click to collapse
Had the same feeling. Had tried it right then but it still gave the same result. I think I might try changing it to something else. This happened just before flashing the AT&T RUU, wonder if this is the cause of all problems. Shall get back after trying tonight. Do let me know if you have any other suggestions. Thanks!

abhijin said:
Yes, this is when the no network problem started. I tracked the radio baseband firmware (from this thread https://forum.xda-developers.com/showthread.php?p=52770589#post52770589) and flashed that too but with no luck. In fact the phone now has become extremely volatile, it reboots often, crashes often. Sometimes just tapping the home button will push it to reboot.
Click to expand...
Click to collapse
None of the radios in the post you linked, correspond to the current firmware number (6.20.502.5). And al the radios on that post are rather old. Newest is Lollipop, with most others being even older.
I also would recommend against flashing radio baseband, without replacing the whole firmware and ROM as well. The crashes and reboots are probably due to incompatibility between the radio and the firmware and/or ROM.
I would suggest to flash the firmware 6.20.502.5 from the following thread. I always user fastboot (RUU mode) Method 32 personally. Be sure to flash it twice:
https://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
Then see if you have any change.
abhijin said:
Had the same feeling. Had tried it right then but it still gave the same result. I think I might try changing it to something else. This happened just before flashing the AT&T RUU, wonder if this is the cause of all problems.
Click to expand...
Click to collapse
That is what I would try: try to change to another MID (a known one, such as Euro), than back to AT&T.
It's possible the "no network" problem may be linked to the MID being screwed up. I can't say for sure. But I know SuperCID enables SIM unlock. So maybe it's possible that a broken MID will break some other things (like the network).

redpoint73 said:
None of the radios in the post you linked, correspond to the current firmware number (6.20.502.5). And al the radios on that post are rather old. Newest is Lollipop, with most others being even older.
I also would recommend against flashing radio baseband, without replacing the whole firmware and ROM as well. The crashes and reboots are probably due to incompatibility between the radio and the firmware and/or ROM.
I would suggest to flash the firmware 6.20.502.5 from the following thread. I always user fastboot (RUU mode) Method 32 personally. Be sure to flash it twice:
https://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
Then see if you have any change.
That is what I would try: try to change to another MID (a known one, such as Euro), than back to AT&T.
It's possible the "no network" problem may be linked to the MID being screwed up. I can't say for sure. But I know SuperCID enables SIM unlock. So maybe it's possible that a broken MID will break some other things (like the network).
Click to expand...
Click to collapse
Hey I tried to to flash through fastboot RUU but at the htc_fastboot oem rebootRUU command it gives me an error saying dns server not authoritative for zone
No clue how to proceed further into this.
Should I just try to get a stock nanodroid backup and restore that?

abhijin said:
Hey I tried to to flash through fastboot RUU but at the htc_fastboot oem rebootRUU command it gives me an error saying dns server not authoritative for zone
No clue how to proceed further into this.
Should I just try to get a stock nanodroid backup and restore that?
Click to expand...
Click to collapse
Hey I was successful in flashing the AT&T by the RUU method by using fastboot commands instead of htc_fastboot but for some reason I got stuck in bootloops post that and it kept booting to recovery.

redpoint73 said:
None of the radios in the post you linked, correspond to the current firmware number (6.20.502.5). And al the radios on that post are rather old. Newest is Lollipop, with most others being even older.
I also would recommend against flashing radio baseband, without replacing the whole firmware and ROM as well. The crashes and reboots are probably due to incompatibility between the radio and the firmware and/or ROM.
I would suggest to flash the firmware 6.20.502.5 from the following thread. I always user fastboot (RUU mode) Method 32 personally. Be sure to flash it twice:
https://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
Then see if you have any change.
.
Click to expand...
Click to collapse
Hey, so it finally came through. Now I am on the Dev Edition and running RR 6 on it but for some reason no sim card is being recognized. Has the worst happened then? Does this mean that I have bricked the radio and there would be no way to change it?

abhijin said:
Hey, so it finally came through. Now I am on the Dev Edition and running RR 6 on it but for some reason no sim card is being recognized. Has the worst happened then? Does this mean that I have bricked the radio and there would be no way to change it?
Click to expand...
Click to collapse
Can't say, with info (or lack of info) given by you. I never said to flash Dev Edition, so I don't really understand what you did, or trying to do (I see from above you had trouble with the AT&T RUU, but that still doesn't tell the whole story). I can't tell whether you flashed the Dev Edition firmware, or RUU or both.
I also advised to try to fix the MID, but you don't mention if you tried, or were successful or not.
I also don't understand why you are running RR6. Did the SIM work after flashing Dev Edition (before flashing RR6). I don't recommend messing with custom ROMs until you get the radio/SIM worked out, as custom ROMs add another layer of complexity and possible bugs.

redpoint73 said:
Can't say, with info (or lack of info) given by you. I never said to flash Dev Edition, so I don't really understand what you did, or trying to do (I see from above you had trouble with the AT&T RUU, but that still doesn't tell the whole story). I can't tell whether you flashed the Dev Edition firmware, or RUU or both.
Click to expand...
Click to collapse
I flashed both. Also returned back to stock.
redpoint73 said:
I also advised to try to fix the MID, but you don't mention if you tried, or were successful or not.
Click to expand...
Click to collapse
I did try but nothing has changed. The initial parts change i.e. 0P6B12000d will change but the latter f/e/lc/mbkp s1se=68 doesn't change at all.
redpoint73 said:
I also don't understand why you are running RR6. Did the SIM work after flashing Dev Edition (before flashing RR6). I don't recommend messing with custom ROMs until you get the radio/SIM worked out, as custom ROMs add another layer of complexity and possible bugs.
Click to expand...
Click to collapse
Honestly, I'm just trying a few different things just to see if something will work out

abhijin said:
I flashed both. Also returned back to stock.
Click to expand...
Click to collapse
Stock what? Firmware? RUU? Stock for your device would be Rogers.
When you returned to "stock" (whatever that means) did the SIM still not work?
After flashing the Dev Edition firmware and RUU, did the SIM work or not?
Really, I'm just asking the same kinds of questions over and over. But you fail to properly answer them.

Just can't get the Phone to work properly....help please..

Hi Guys,
So I have an M9 which I bought on eBay brand new from China.
It came with an USA Rom which had been tweaked to work in the UK.
Anyhoo, I unlocked the bootloader, S-Off using Sunshine, installed a recovery, Rooted and SuperCID it.
They I replace the Rom with the international Rom:
0PJAIMG_HIMA_UHL_N70_SENSE80_MR_HTC_Europe_4.28.401.3_Radio_01.01_U114401011_117.00.61117G_2_F_release_498151_signed_2.zip
I had to change my MID from 0PJA11000 to 0PJA10000 for it to work.
Well it all works beautifully except the Phone.
I am sure I have the wrong Radio for the UK.
The signal is weak and cuts out, I know I'm in a very strong signal area and all my other phones work fine. Indeed I had the same problem with my M8 until I changed Radios.
Now I have used (or tried to use) every Radio in this thread:
https://forum.xda-developers.com/one-m9/general/recovery-flashable-radio-zip-t3122983
But none of them stick, sure they go through the motions of flashing and even say they had finished (Using TWRP) but they don't actually change the Radio.
Currently my Radio is:
01.01_U114401011_117.00.61117G_2
Im in the UK and I'm on the O2 network so I need a Radio specific for that.
I downloaded this Rom:
0PJAIMG_HIMA_UHL_M60_SENSE70_MR_O2_UK_3.35.206.13_Radio_01.01_U11440792_93.00.51117G_F_release_464855_signed
But I get Error 12 whilst trying to install.
Do I have to just change my MID back to 0JPA11000?
If it's not that I'm at a loss as to what the problem is.
Here is my Getvar:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) serialno: ***************
(bootloader) current-slot:
(bootloader) imei: *******************
(bootloader) version-main: 4.28.401.3
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U114401011_117.00.61117G_2_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: 11111111
Please help me get this sorted, its such a great phone..
Thanks

Oh joy....
Well I've been up all night after soft bricking my phone.
Eventually managed to install the O2 RUU I wanted!!
Had to format a 8GB microsd to fat32 so the phone would see it even though the hboot said it was on 4.xx firmware.
I also couldn't write mid or cid, they wouldn't change.
Anyhoo formatted microsd copied RUU onto it renamed OPJAIMG and it worked!!
BUT NOW....
Well now I want the OTA which it downloads then says my software's not official...
So do I have to relock it, s-on it and unroot it for the ota or can I just flash it from somewhere?
All I know is I've got the correct Radio installed.
So that's good!
Any help from the Pro's would be much appreciated.

I believe what I will do is update the firmware in increments no-wipe using the firmware thread...it's got the correct O2 ones on there.......If only I could find it..

No that won't work...the firmwares are older than what I already have installed...
Anyone got any ideas?
I just want to receive the OTA really, how do I convince my phone its genuine?
OR
Where does it download it to so I can rename it and flash it? (Can I do that?)

Well guys I'm getting there, I have found the OTA on this site so am downloading now.
Hopefully that will be that and I can get some sleep!

Now I'm getting Error 12...
How do I sort that?
In the error listings 12 is not sure what it is...

So in my wisdom(!) I thought it couldn't make a giant leap from firmware 3 to 4.
I figured(!) It need the firmware in between.
4.14.617.6 So I downloaded that and whilst trying to flash it sdcard method I get error code 7
All I know is that the M7 and M8 were a lot easier to do!

My New Getvar:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: ************
(bootloader) version-main: 3.35.206.13
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_93.00.51117G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: O2___001

Well I've now changed my MID to 0PJA10000 and that's not worked even though that is the right MID and so I then changed the CID from the correct O2 one to Super CID which I believe is 8 1's...so 11111111.
But that hasn't worked...
What have I got to do guys, it's not this difficult ever, what's going wrong?
I know I'm not rooted any more and I don't have a custom recovery but that shouldn't matter or does it?
I hope this isn't one of those threads that just sits here...
Why I had an O2 UK RUU that gave me a MID of 0PJA11000 makes no sense if it's supposed to be 0PJA10000...and that one worked!!

I'm stuck as to what to do......

Well I've gone in a big loop only to end up with the international version back on my phone. Its the latest one, the O2 ones although they have the right radio are stuck on Lolipop or Marshmallow. They want to update but cant as my phone software is not recognised as official due to being rooted....
So I have the phone back up and running on WWE but the signal is dire.
If anyone can tell me how to extract the radio from the O2RUU and apply it to my phone it would be appreciated...if not I will just send my phone back to HTC and get them to do it.
I've never seen such scrappy out of date software.

I'll just start at your first post and reply to everything that catches my eyes since you already created that many posts in this thread. In general I highly recommend you to carefully read the ReadMe thread.
In general: Are you sure that you bought a GSM variant and not a CDMA one? These technologies aren't compatible with each other an flashing GSM files on a CDMA device or vice cersa always leads to headaches (worst case: unrecoverable hardware damages).
Post 1: It doesn't matter whether you use the unbranded 401 baseband or the O2 branded 206 one. The reception should be the same. (CDMA devices can't read their own IMEI anymore and lose all reception if you flash GSM RUUs on them, though.)
SCID isn't recommended to be used anymore. It prevents your phone from installing OTAs and it won't make your phone ignore MID mismatches with RUUs like it did on the M8 and older HTC devices.
Post 2: The M9 and all newer devices don't have an hboot, anymore. There's the download mode and the aboot which replace what you know as hboot from older HTC devices.
Never re-lock this phone or re-S-ON it unless you know for 100000000000000 % that it's absolutely 100 % stock and completely unmodified. There are security checks which will prevent the phone from booting if it's modified and you e.g. re-lock the bootloader.
Post 6: Error 12 indicates that you tried to flash a RUU with a different encryption key than the one your phone's current firmware is using.
Post 7: I haven't seen error 7, before. Since you already had problems with flashing the other RUU via your SD card while the SD card wasn't formatted to fat32 I assume it might indicate some SD card hardware issue.
Post 9: RUUs can't change your MID. That's something you need to do manually via fastboot commands.
Post 11: If the OTAs fail although you directly used a RUU beforehand than you're either using the wrong MID or an incorrect CID. The only other possible reason might be that you're suffering from the first symptoms of a nand death. Like all smartphones with the Snapdragon 810, the M9's hardware can suddenly die due to the hardware damages that get caused by the heat of the infamous processor.

Flippy498 said:
I'll just start at your first post and reply to everything that catches my eyes since you already created that many posts in this thread. In general I highly recommend you to carefully read the ReadMe thread.
In general: Are you sure that you bought a GSM variant and not a CDMA one? These technologies aren't compatible with each other an flashing GSM files on a CDMA device or vice cersa always leads to headaches (worst case: unrecoverable hardware damages).
Post 1: It doesn't matter whether you use the unbranded 401 baseband or the O2 branded 206 one. The reception should be the same. (CDMA devices can't read their own IMEI anymore and lose all reception if you flash GSM RUUs on them, though.)
SCID isn't recommended to be used anymore. It prevents your phone from installing OTAs and it won't make your phone ignore MID mismatches with RUUs like it did on the M8 and older HTC devices.
Post 2: The M9 and all newer devices don't have an hboot, anymore. There's the download mode and the aboot which replace what you know as hboot from older HTC devices.
Never re-lock this phone or re-S-ON it unless you know for 100000000000000 % that it's absolutely 100 % stock and completely unmodified. There are security checks which will prevent the phone from booting if it's modified and you e.g. re-lock the bootloader.
Post 6: Error 12 indicates that you tried to flash a RUU with a different encryption key than the one your phone's current firmware is using.
Post 7: I haven't seen error 7, before. Since you already had problems with flashing the other RUU via your SD card while the SD card wasn't formatted to fat32 I assume it might indicate some SD card hardware issue.
Post 9: RUUs can't change your MID. That's something you need to do manually via fastboot commands.
Post 11: If the OTAs fail although you directly used a RUU beforehand than you're either using the wrong MID or an incorrect CID. The only other possible reason might be that you're suffering from the first symptoms of a nand death. Like all smartphones with the Snapdragon 810, the M9's hardware can suddenly die due to the hardware damages that get caused by the heat of the infamous processor.
Click to expand...
Click to collapse
Thanks Flippy, I learn so much every time I post here you are truly experts.
I will look at all my posts as questions solved by the last post!
I'm pretty sure it's GSM but would love to know how to check.
I have through chance, luck and what I thought was knowledge secured a good running International RUU....
I am rooted, unlocked, supercid and running beautifully.
Yet my Radio is wrong.
I try and try (this was the start of the post and is still the end) to try and install a new Radio.
When using the old O2 RUU it was clear that was the correct Radio.
An old one!
However I have not been able to flash any other Radio from the M9 Radio post.
This as you can imagine is a huge problem as much that we all like to use our phones as superfast little Chromebooks, they are first and foremost Phones!!!
If I cannot find a good Radio I must get HTC to sort it for me.
It would be wonderful if I could find a tutorial on how to pull the Radio from a firmware Rom as I have the old O2 RUU that has a Radio (all be it old) that suits my needs.
I've not been able to find such a Radio and unfortunately the RUU that would have been exactly what I was looking for turned out to be German and as such had the incorrect Radio.
I can't believe (but believe I must) that HTC UK do not support rooted phone and provide the software as they do for the USA....but there you go they don't.
They have however offered to "fix" my phone...i.e. replace the software...for a price I may add, rather than providing me with software and allowing me to do the 5 second operation for free...
That's where I'm up to Flippy, its kept me awake for over 36hrs and ruined my weekend.
Thank goodness for Bank Holidays.
May I add that the M9 is my favorite HTC so far, I have played with the SPV (Very slow but very cool!!) One X (Popular but over rated), One X+(great phone for the time), the M7 (Equally an excellent phone), the M8 (lasted me for years, amazing) and now the M9. I don't like the M10 because of the iPhone/Samsung One button and I haven't been privy to the U11/U12/U12+ but don't much rate anything you have to squeeze...let alone get a decent case for so your £700 (I can buy a car for that) phone doesn't get a scratch....at the end of the day a Nokia Dumb phone was good enough and a Laptop was a laptop.
I know it's going to progress to jewelry, glasses and smart clothes...then onto holographic VR and Thought(!) and Implants(!) but all I want is a phone that does a few things, first and foremost PHONE people!
God bless technology and God bless the back engineering from downed UFO's.
But technology and the concept of God doesn't sit right.
So thank Science!

eskimosound said:
I've not been able to find such a Radio and unfortunately the RUU that would have been exactly what I was looking for turned out to be German and as such had the incorrect Radio.
Click to expand...
Click to collapse
As already explained in your other thread. There is no "German" RUU. HTC got rid of a whole bunch of SKUs with the M9. Several countries now share the same SKU (and therefore the same firmware) while only the CID differs. You were using the correct baseband after you had flashed the 4.27.206.4 RUU. Officially, it's even labeled as O2 UK RUU by HTC.
However, I took a closer look at the latest O2/206 and the latest unbranded European/401 RUU. Both use the exact same baseband/radio version. So whatever your issue is, it's not baseband related.
eskimosound said:
I can't believe (but believe I must) that HTC UK do not support rooted phone and provide the software as they do for the USA....but there you go they don't.
Click to expand...
Click to collapse
They never provided RUUs outside the US. And HTC even stopped providing RUUs for all of their newer phones. The HTC 10 is the latest model for which you can find RUUs on their US website.
Finding out whether you own a CDMA device or a GSM one can be quite easy if no one has ever replaced the backplate of the phone. There's a small engraving with the MID at the bottom of the backplate. If the backplate got replaced it's impossible to say which version you own, though. With S-OFF you can cross-flash GSM files on CDMA devices and vice versa after you manually changed the MID since S-OFF means nothing else than all Security checks being set OFF. And after cross-flashing, there's no way to find out which version you own via the software.

Flippy498 said:
I'll just start at your first post and reply to everything that catches my eyes since you already created that many posts in this thread. In general I highly recommend you to carefully read the ReadMe thread.
In general: Are you sure that you bought a GSM variant and not a CDMA one? These technologies aren't compatible with each other an flashing GSM files on a CDMA device or vice cersa always leads to headaches (worst case: unrecoverable hardware damages).
Post 1: It doesn't matter whether you use the unbranded 401 baseband or the O2 branded 206 one. The reception should be the same. (CDMA devices can't read their own IMEI anymore and lose all reception if you flash GSM RUUs on them, though.)
SCID isn't recommended to be used anymore. It prevents your phone from installing OTAs and it won't make your phone ignore MID mismatches with RUUs like it did on the M8 and older HTC devices.
Post 2: The M9 and all newer devices don't have an hboot, anymore. There's the download mode and the aboot which replace what you know as hboot from older HTC devices.
Never re-lock this phone or re-S-ON it unless you know for 100000000000000 % that it's absolutely 100 % stock and completely unmodified. There are security checks which will prevent the phone from booting if it's modified and you e.g. re-lock the bootloader.
Post 6: Error 12 indicates that you tried to flash a RUU with a different encryption key than the one your phone's current firmware is using.
Post 7: I haven't seen error 7, before. Since you already had problems with flashing the other RUU via your SD card while the SD card wasn't formatted to fat32 I assume it might indicate some SD card hardware issue.
Post 9: RUUs can't change your MID. That's something you need to do manually via fastboot commands.
Post 11: If the OTAs fail although you directly used a RUU beforehand than you're either using the wrong MID or an incorrect CID. The only other possible reason might be that you're suffering from the first symptoms of a nand death. Like all smartphones with the Snapdragon 810, the M9's hardware can suddenly die due to the hardware damages that get caused by the heat of the infamous processor.
Click to expand...
Click to collapse
Flippy498 said:
As already explained in your other thread. There is no "German" RUU. HTC got rid of a whole bunch of SKUs with the M9. Several countries now share the same SKU (and therefore the same firmware) while only the CID differs. You were using the correct baseband after you had flashed the 4.27.206.4 RUU. Officially, it's even labeled as O2 UK RUU by HTC.
However, I took a closer look at the latest O2/206 and the latest unbranded European/401 RUU. Both use the exact same baseband/radio version. So whatever your issue is, it's not baseband related.
They never provided RUUs outside the US. And HTC even stopped providing RUUs for all of their newer phones. The HTC 10 is the latest model for which you can find RUUs on their US website.
Finding out whether you own a CDMA device or a GSM one can be quite easy if no one has ever replaced the backplate of the phone. There's a small engraving with the MID at the bottom of the backplate. If the backplate got replaced it's impossible to say which version you own, though. With S-OFF you can cross-flash GSM files on CDMA devices and vice versa after you manually changed the MID since S-OFF means nothing else than all Security checks being set OFF. And after cross-flashing, there's no way to find out which version you own via the software.
Click to expand...
Click to collapse
Thanks Flippy, very informative.
It's a new phone, came in a sealed box.
Marking on the back of phone:
Model: 0PJA100 FCC ID: NM80PJA100 M9u
I can't find what I need, so I will send to HTC.
I didn't want to root this M9 but had to as supplied with USA software. But have conceded and will let HTC deal with it.
Thanks for your time.

According to everything you described it's impossible that you bought a new phone. And I wouldn't trust a seller just because the device got shipped sealed. Breaking a seal and re-sealing the box at a later point isn't that difficult.
Assuming that the backplate didn't get replaced, the MID on the backside indicates that you own the international hardware variant. Without tinkering (in other words: without opening the box and breaking the seal) it's not possible to flash US firmware on that device.
And if we assume that the backplate indeed got replaced it's even less possible that you bought a "new" phone.
Sent from my HTC U12+ using XDA Labs

Flippy498 said:
According to everything you described it's impossible that you bought a new phone. And I wouldn't trust a seller just because the device got shipped sealed. Breaking a seal and re-sealing the box at a later point isn't that difficult.
Assuming that the backplate didn't get replaced, the MID on the backside indicates that you own the international hardware variant. Without tinkering (in other words: without opening the box and breaking the seal) it's not possible to flash US firmware on that device.
And if we assume that the backplate indeed got replaced it's even less possible that you bought a "new" phone.
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
I might right it off then and go for a U11.
Will see what HTC say and yeah I don't trust the company I bought it from, once I unlocked it I was sure there was tampering......

Wwe works just as good as o2 firmware. Can you flash an m9u with m9 firmware?.

The M9u is the M9. The u only indicates that you're talking about one of the GSM variants and not about one of the CDMA ones (M9w).
Sent from my HTC U12+ using XDA Labs

Flippy498 said:
The M9u is the M9. The u only indicates that you're talking about one of the GSM variants and not about one of the CDMA ones (M9w).
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Just been told by HTC that the phone is a counterfeit!
The IMEI and Serial Numbers just don't exist.
Thankfully I'm covered by PayPal who are now dealing with it, but really...!!!
First time in the 10 years I've been doing this that I've bought fake...