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.

Change frequency band 900 Mhz in M8 T Mobile

Good
I have a htc one m8 Mobile operator T; changing operator in my country of origin and previously used frequency 850 mhz and 1900; and the new operator uses frequency band 3G and 4G to 900 mhz and m8 T Mobile does not accept that band there any possibility to change this frequency.
I am root, S-Off, super CID Android 6
Some help.
greeting
Enviado desde mi hTC One_M8

You're s-off, so this isn't too hard. You can either flash another carrier versions firmware.zip, or RUU. Euro and Asia versions should support 900 Mhz for both 3G and LTE (at least in theory - see more below regarding LTE).
You may need to change MID, depending on what route you want to go, and what file you use.
But it should also be noted, that I've seen a number of folks that properly changed to a firmware (or full RUU conversion) containing the radio which supports their carrier's LTE band. But they still were not able to get LTE service. I don't know the reason for this, and have not seen any solution. So be aware, that there is a possibility you may not get LTE, even after adding the proper band support. But you should at least be able to get 3G on 900 MHz.
Firmwares (and info on flashing) are posted here: http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
RUUs are posted in a variety of places. But I can advise, depending on what variant you want to "convert" to (Asia or Euro) if you want to go RUU route. You'll also need to change MID if you decide this route.

redpoint73 said:
You're s-off, so this isn't too hard. You can either flash another carrier versions firmware.zip, or RUU. Euro and Asia versions should support 900 Mhz for both 3G and LTE (at least in theory - see more below regarding LTE).
You may need to change MID, depending on what route you want to go, and what file you use.
But it should also be noted, that I've seen a number of folks that properly changed to a firmware (or full RUU conversion) containing the radio which supports their carrier's LTE band. But they still were not able to get LTE service. I don't know the reason for this, and have not seen any solution. So be aware, that there is a possibility you may not get LTE, even after adding the proper band support. But you should at least be able to get 3G on 900 MHz.
Firmwares (and info on flashing) are posted here: http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
RUUs are posted in a variety of places. But I can advise, depending on what variant you want to "convert" to (Asia or Euro) if you want to go RUU route. You'll also need to change MID if you decide this route.
Click to expand...
Click to collapse
Thank you for this valuable info!

guorium said:
Thank you for this valuable info!
Click to expand...
Click to collapse
Tread carefully. The information I gave was for the original poster's specific case. It may or may not apply in your case, and even be dangerous! For instance, if you have the Sprint or Verizon version M8, trying to flash a different radio or firmware will result in a radio brick (possibly permanent)! And you can't always easily tell if it a Sprint/Verizon version - we've seen these devices modified by third party vendors to appear "unbranded".
For the best info and help, please post your specific device info. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

redpoint73 said:
Tread carefully. The information I gave was for the original poster's specific case. It may or may not apply in your case, and even be dangerous! For instance, if you have the Sprint or Verizon version M8, trying to flash a different radio or firmware will result in a radio brick (possibly permanent)! And you can't always easily tell if it a Sprint/Verizon version - we've seen these devices modified by third party vendors to appear "unbranded".
For the best info and help, please post your specific device info. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
Yes I read the unlock qualcomm post and it looks like a dozen GSM handsets failed and only CDMA devices successed. I am just trying to change the radio of mine which getvar reports to be a china mobile issued phone (certainly GSM). The Chinese radio does not support it vital 3G band (900MHz my carrier uses) in my home suburb. Apparently from some digging I did on the Australian forum whirlpool, all three carriers in Australia got different firmware versions but the radio img is all the same and the same radio means all 3 carriers are supported by m8 running the aussie radio in Australia. So I am doing soff on my handset to modify MID and CID so I can flash a Australian firmware to my phone and have full reception at home.
Funny enough I cannot get those firmwares from all three carriers nor htc australia. Their online chat support all refused to offer firmware to me. They did not even tell what the firmware versions are so I could look for it (wasted my time but my research paid off). Fellows on whirlpool offered their RUU in zip form for download. I can't easily tell if the Aussie radio support the bands I needed without using one of the fellow's imei to search for band support spec on imei.info. So yeah not hiding it helped me. I really want to just flash the aussie radio on top of the Chinese firmware I already got though. No one has the radio image for download. Do you know how to extract it from a 0P6BIMG.zip? I kinda wanna avoid having to extract the radio myself... it takes a while to put the Aussie firmware on and after that, extracting radio image would be almost pointless since it is already installed.

See my responses below in red font:
guorium said:
I am just trying to change the radio of mine which getvar reports to be a china mobile issued phone (certainly GSM). The Chinese radio does not support it vital 3G band (900MHz my carrier uses) in my home suburb.
So I am doing soff on my handset to modify MID and CID so I can flash a Australian firmware to my phone and have full reception at home.
If it is the Chinese M8 variant I'm thinking of, I don't think this will work.
Further, s-off is only possible with sunshine app ($25 US), which is probably wasted money for the above reason.
Please post your getvar data (deleting IMEI and serial number before posting) as previously requested, so we can advise more properly.
Funny enough I cannot get those firmwares from all three carriers nor htc australia. Their online chat support all refused to offer firmware to me. They did not even tell what the firmware versions are so I could look for it
I've never heard of HTC supplying firmware that way. Most they will do is send the RUU for your phone version. They will not support you changing your M8 to another version (different CID, MID) and therefore not supply those files. Also, there are a lot of CIDs that do not even have RUU.
No one has the radio image for download. Do you know how to extract it from a 0P6BIMG.zip? I kinda wanna avoid having to extract the radio myself... it takes a while to put the Aussie firmware on and after that, extracting radio image would be almost pointless since it is already installed.
I don't recommend only flashing the radio. img. Better to flash the whole firmware.zip, to make sure all the partitions are compatible. When I saw "firmware.zip" this is a small package that contains radio, hboot, and a few other partitions, but does not contain the ROM.
Then you say "firmware" it sounds like you are referring to the RUU or ROM, in which case please just say RUU or ROM, to avoid confusion.
Click to expand...
Click to collapse

redpoint73 said:
See my responses below in red font:
Click to expand...
Click to collapse
Yes it is a 1.5G big boy. A RUU in 0P6BIMG.ZIP form. Changed to super CID and Australian MID. I am flashing it whole now. Keeps reporting large image update fail. Fastboot getvar all below
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311231.14G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.30.1403.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: nopenopenope
(bootloader) imei: nopenopenope
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_tl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(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!
Click to expand...
Click to collapse

Far as I know the Chinese variant isn't compatible with the RUU or firmware.zip for "standard" M8. It's product name is m8_tl
Where most other M8 variants are m8_ul
M8 variants that share the same product name M8_ul can be "converted" between each other using the RUU. M8 variants with different product name (like yours) in every case I've seen, the RUUs are not cross compatible.
Further, the "large image" error when flashing RUU is commonly seen when you try to flash an RUU for a different hardware.
Not sure if it is technically a different hardware, but I tend to think it is. From what I'm reading, China has a specific implementation of 3G, which probably required different hardware.
Moral of the story, I don't think you can mod this phone to add the desired band support.

redpoint73 said:
Far as I know the Chinese variant isn't compatible with the RUU or firmware.zip for "standard" M8. It's product name is m8_tl
Where most other M8 variants are m8_ul
M8 variants that share the same product name M8_ul can be "converted" between each other using the RUU. M8 variants with different product name (like yours) in every case I've seen, the RUUs are not cross compatible.
Further, the "large image" error when flashing RUU is commonly seen when you try to flash an RUU for a different hardware.
Not sure if it is technically a different hardware, but I tend to think it is. From what I'm reading, China has a specific implementation of 3G, which probably required different hardware.
Moral of the story, I don't think you can mod this phone to add the desired band support.
Click to expand...
Click to collapse
Ok thanks for the help. The phone appears to be limbo now. I tried to flash Aussie RUU as 0B6PIMG.zip and it gives me the large file error. Then I thought oh maybe it is because it is still unlock flag for bootloader (But I thought it should not matter sin Soff is there). So I used the fastboot oem lock command. It went to relock. I still cannot flash it. So I used fastboot flash zip RUU.zip to flash A small ~30MB Aussie firmware which actually when through fine, then I flashed the newer version of that firmware (the old one had to be done first). That turned my OS number in the bootloader to the Aussie one instead of Chinese.
Then I cannot flash any RUU in 0B6PIMG.zip anymore, not aussie not Chinese. I can only enter bootloader now. No recovery is present. Cannot flash recovery and cannot unlock bootloader with token. Both just tell me failed. If I try to flash 0B6PIMG.zip via usb cable with "fastboot flash zip 0B6PIMG.zip". It says "load_file: could not allocate blah blah bytes" when I am sure there is a lot of space left. AT&T RUU exe cannot write successfully too.
So I got a semi brick with bootloader only now haha. The 3 little androids look cute though.:cyclops:

guorium said:
So I got a semi brick with bootloader only now haha. The 3 little androids look cute though.:cyclops:
Click to expand...
Click to collapse
Maybe I wasn't clear, but you really should have stopped when I said your device is not compatible with other M8 firmware. It is almost certainly a different hardware, which means flashing the wrong firmware (anything but firmware for m8_tl) is not only going to not work (phone will not function properly), but may result in permanent damage.
Just because the firmware flashed, does not mean it is a good thing. You've removed all the safeguards by doing s-off, changing the CID/MID. So it will flash, no surprise there. But folks have previously done something similar with the US CDMA variants (m8_wlv and m8_whl) by trying to flash firmware for m8_ul (the "standard" M8, the most common product name) which results in a radio brick.
These variants are never partitioned the same. What you have done is overwritten the wrong partitions with the m8_ul firmware.zip. Unless there is an RUU or firmware zip for m8_tl, there probably is not a way to fix this.

redpoint73 said:
Maybe I wasn't clear, but you really should have stopped when I said your device is not compatible with other M8 firmware. It is almost certainly a different hardware, which means flashing the wrong firmware (anything but firmware for m8_tl) is not only going to not work (phone will not function properly), but may result in permanent damage.
Just because the firmware flashed, does not mean it is a good thing. You've removed all the safeguards by doing s-off, changing the CID/MID. So it will flash, no surprise there. But folks have previously done something similar with the US CDMA variants (m8_wlv and m8_whl) by trying to flash firmware for m8_ul (the "standard" M8, the most common product name) which results in a radio brick.
These variants are never partitioned the same. What you have done is overwritten the wrong partitions with the m8_ul firmware.zip. Unless there is an RUU or firmware zip for m8_tl, there probably is not a way to fix this.
Click to expand...
Click to collapse
Yes thanks for your advise. Very helpful indeed! I got good support from HTC China. They provided all RUUs including my model for everyone to download. I found out some other dude writing a blog post about how m8_tl can only use m8_tl's RUUs (there are two, one bring lighter with less carrier ****). No surprise my attempt to flash m8_ul's RUUs never succeeded. It will not even begin when I load up the 0P6BIMG.zip. I just unlocked bootloader again (needed a new token since MID was altered) so I can flash twrp and in turn use the adb shell to edit my MID back to orginal so I can put on the lighter version of stock RUU.
The lighter one still runs much better than China Mobiles tainted RUU. It cannot be done unless you soff. The soff was definitely worth it. I flashed some Australian radios and none of them give me the desired 3G band. It kinda behaved the same as the Chinese stock radio image. Very weird. Perhaps the Chinese GSM version of M8 are actually having different hardware compared to the international version. I just have not seen anyone rip a m8_tl apart and introduce us all the components.
I was very much aware that flashing CDMA RUU could do very bad things to a GSM M8. So I did not even think about it. Suppose my last hope of getting an extra 3G band is using QPST but that sounds very dangerous and I have just seen CDMA types succeeding. Will carefully read first...
UPDATE: I skimmed over all M8 related postes on that massive "Unlock all bands for Qualcomm" post. Apparently only the CDMA handsets worked. Those with GSM phones did not get it to work... Probably a hardware limitation. I will stay on my current state of my phone then. I came across a couple Chinese posts talking about replacing carrier_policy.xml with QPST on my exactly model m8t. That had no choice of specific bands. It simply sets the rules of network switching when various SIMs are inserted. Interesting none the less.

guorium said:
Yes thanks for your advise. Very helpful indeed! I got good support from HTC China. They provided all RUUs including my model for everyone to download. I found out some other dude writing a blog post about how m8_tl can only use m8_tl's RUUs (there are two, one bring lighter with less carrier ****). No surprise my attempt to flash m8_ul's RUUs never succeeded. It will not even begin when I load up the 0P6BIMG.zip. I just unlocked bootloader again (needed a new token since MID was altered) so I can flash twrp and in turn use the adb shell to edit my MID back to orginal so I can put on the lighter version of stock RUU.
The lighter one still runs much better than China Mobiles tainted RUU. It cannot be done unless you soff. The soff was definitely worth it. I flashed some Australian radios and none of them give me the desired 3G band. It kinda behaved the same as the Chinese stock radio image. Very weird. Perhaps the Chinese GSM version of M8 are actually having different hardware compared to the international version. I just have not seen anyone rip a m8_tl apart and introduce us all the components.
I was very much aware that flashing CDMA RUU could do very bad things to a GSM M8. So I did not even think about it. Suppose my last hope of getting an extra 3G band is using QPST but that sounds very dangerous and I have just seen CDMA types succeeding. Will carefully read first...
UPDATE: I skimmed over all M8 related postes on that massive "Unlock all bands for Qualcomm" post. Apparently only the CDMA handsets worked. Those with GSM phones did not get it to work... Probably a hardware limitation. I will stay on my current state of my phone then. I came across a couple Chinese posts talking about replacing carrier_policy.xml with QPST on my exactly model m8t. That had no choice of specific bands. It simply sets the rules of network switching when various SIMs are inserted. Interesting none the less.
Click to expand...
Click to collapse
I ended up testing possibility on my machine. The Chinese method in changing policy file with EFS explorer did not give me 900MHz. I then edited NV values with QXDM to enable 900MHz and again it did not give me reception even when the edits were sticking. Just to test I removed 2100MHz as well and sure that killed the 3G reception. My lesson is the TDSCDMA version of m8 just has different hardware compared to the global version. It is incapable of picking up 900MHz. I reflashed the stock RUU and everything is normal again. No brick.:good:

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.

HTC One M8 stuck at HTC logo screen

Hi,
First of all, this was supposed to be my first flash. So I am very new and confused. (I get that you probably have loads of those... I am sorry)
I got a HTC One M8 that was already rooted and S-OFF, had SuperCID and everything. And I hate the 4.4.4 Android, plus no OTA updates are available to me (when I tried to check, it gets stuck). So I wanted to flash in a LineageOS 16.0. I unlocked the bootloader, got TWRP 2.8.7.0, pasted the Lineage 16.0 ZIP file, and wanted to flash it. But, I got an error "Error executing updater binary in zip [zip filename]", and so I went to check the instructions to install.
https://forum.xda-developers.com/htc-one-m8/development/rom-lineageos-16-0-htc-one-m8-t3837538
Here it says this:
- Reboot to recovery (TWRP by @Captain_Throwback) - Direct link
- Wipe /system, /data and /cache
- Install LineageOS zip package
and I did that to see if it changes anything, Nope, it didn't. I tried to reboot the phone to get it fixed (someone in another thread suggested getting an md5 file for it).
And after the reboot I am stuck on HTC logo screen, can't shut it down at all. I can't use ADB because it doesn't see the device, so I can't getvar all. I do remember that my version-bootloader was 3.19.0.0000, but that's all.
I am not asking for a full guide on what to do, because it's probably impossible, but can anyone at least tell me how to proceed next? I'd love to turn off the phone and at least try to do something with TWRP. (I didn't have a backup, yes I am an idiot)
EDIT: Holding volume up and power button to do the reset just turns off the screen for a few secs then goes to HTC logo screen again.

Okay, I waited for it to discharge so I can get to the bootloader. I will post getvar when it charges.
EDIT: here we go
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.08.20.0916
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.30.651.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8a0f02ff
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I basically just want anything to work now, even stock will be okay (but 6.0 at least)

1st edit your last post & remove your IMEI/MEID unless you want it stolen...
when you wiped /system in TWRP & your zip didn't flash, u lost your ROM
easiest way to get the phone back up & working is to flash the RUU, looks like you currently have 3.30.651.2 (very old)
here is the 3.30.651.2 exe version: https://androidfilehost.com/?fid=95784891001604379
or to update to the latest version 6.20.651.3:
http://dl3.htc.com/application/RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.exe

OMJ said:
1st edit your last post & remove your IMEI/MEID unless you want it stolen...
Click to expand...
Click to collapse
Yeah, I forgot, thanks for reminding.
So do I just run the .exe with my phone plugged in my PC while in bootloader? Or do you mean TWRP/adb flashing?

gr0za said:
Yeah, I forgot, thanks for reminding.
So do I just run the .exe with my phone plugged in my PC while in bootloader? Or do you mean TWRP/adb flashing?
Click to expand...
Click to collapse
yes, run exe from pc while connected to phone

OMJ said:
yes, run exe from pc while connected to phone
Click to expand...
Click to collapse
3.30.651.2 worked, 6.20.651.3 did not ( I tried it first). To be honest I'm so damn glad it works, because I ain't a Sprint user, but somehow Orange works. Got all the bloaty Google Aps that I don't give an f about, but at least it's working. Hopefully I can go to 6.20 next, I'm gonna try. BTW, will flashing GApps remove all the unnecessary Sprint apps? Or do I have to do something different with it? (I don't need neither the GApps not the Sprint apps, but this phone seems to be a Sprint one and I guess I have to deal with it)
EDIT: yeah, 6.20 doesn't work, it gives me Error 155 - Error updating ROM. I remember hitting up HTC live support once in desperation, and the guy told me I have to upgrade to Lollipop first. But where do I even find a RUU for that?

gr0za said:
3.30.651.2 worked, 6.20.651.3 did not ( I tried it first). To be honest I'm so damn glad it works, because I ain't a Sprint user, but somehow Orange works. Got all the bloaty Google Aps that I don't give an f about, but at least it's working. Hopefully I can go to 6.20 next, I'm gonna try. BTW, will flashing GApps remove all the unnecessary Sprint apps? Or do I have to do something different with it? (I don't need neither the GApps not the Sprint apps, but this phone seems to be a Sprint one and I guess I have to deal with it)
EDIT: yeah, 6.20 doesn't work, it gives me Error 155 - Error updating ROM. I remember hitting up HTC live support once in desperation, and the guy told me I have to upgrade to Lollipop first. But where do I even find a RUU for that?
Click to expand...
Click to collapse
yeah I vaguely recall the RUU checks your current version & must be a certain level, so you'll probably need to flash a 4.x.651.x RUU 1st
GApps probably only adds Google apps, I doubt it removes anything. once you get up to 6.20, you can root the phone (I recommend Magisk) then use a file explorer like Root Explorer to mount /system & then delete the bloat u dont want. You can also do this in twrp.
the other option is to flash a custom ROM that removes the bloat....my ROM removes bloat but retains pertinent Sprint apps

OMJ said:
yeah I vaguely recall the RUU checks your current version & must be a certain level, so you'll probably need to flash a 4.x.651.x RUU 1st
GApps probably only adds Google apps, I doubt it removes anything. once you get up to 6.20, you can root the phone (I recommend Magisk) then use a file explorer like Root Explorer to mount /system & then delete the bloat u dont want. You can also do this in twrp.
the other option is to flash a custom ROM that removes the bloat....my ROM removes bloat but retains pertinent Sprint apps
Click to expand...
Click to collapse
Alright, once I flashed the Sprint RUU, all of a sudden I have OTA updates. I'm getting to 6.20 now, so everything's fine.
Yeah, I will consider removing them the way you said. Also, I don't really need any Sprint apps, as I am not a Sprint client anyway, but I reckon some are better left unchecked. Much, much appreciated for the help and the links.

gr0za said:
(bootloader) version-main: 3.30.651.2
Click to expand...
Click to collapse
This was the main problem with flashing Lineage, your firmware (hboot, radio, etc.) was much too old. The current ROMs are not compatible with the old firmware. Now that you're updated to Marshmallow, I'll bet Lineage will install correctly (of course, you need to install TWRP again, etc.).
---------- Post added at 01:01 PM ---------- Previous post was at 12:59 PM ----------
gr0za said:
Holding volume up and power button to do the reset just turns off the screen for a few secs then goes to HTC logo screen again.
Click to expand...
Click to collapse
Hold vol up and power button to force a reboot. The moment the screen goes dark, signaling it is about to reboot, slide your finger from vol up, to vol down, and don't let go. This should get you into bootloader.
As long as the screen comes on, you can get into bootloader. Exception is, if your vol rocker is broken!
---------- Post added at 01:04 PM ---------- Previous post was at 01:01 PM ----------
OMJ said:
yeah I vaguely recall the RUU checks your current version & must be a certain level, so you'll probably need to flash a 4.x.651.x RUU 1st
Click to expand...
Click to collapse
Version check is okay if the RUU is same or greater version number (and skipping versions is usually okay). You can't go backwards (downgrade), is all.
There was a peculiar requirement on Marshmallow RUUs for US carrier versions of the M8. It is required to flash the appropriate Marshmallow firmware by fastboot, before the RUU would work, if coming from Lollipop or lower.

redpoint73 said:
This was the main problem with flashing Lineage, your firmware (hboot, radio, etc.) was much too old. The current ROMs are not compatible with the old firmware. Now that you're updated to Marshmallow, I'll bet Lineage will install correctly (of course, you need to install TWRP again, etc.)
Click to expand...
Click to collapse
Are you sure of this? I have a Sprint variant. And I found conflicting info whether Lineage works on Sprint or doesn't work.

gr0za said:
Are you sure of this? I have a Sprint variant. And I found conflicting info whether Lineage works on Sprint or doesn't work.
Click to expand...
Click to collapse
Not 100%, as I don't personally own the Sprint version M8. But what I can say:
1) The Lineage 16 thread says: "Builds are compatible with all M8 single SIM variants (m8ul, m8vzw and m8spr)."
Now the identifier "m8spr" isn't a correct one I've ever seen attached to the M8. But I think they mean the Sprint variant. Correct product ID would be M8_whl.
2) Instance of custom ROMs not working on M8 CDMA variants (Sprint and Verizon) are mainly due to the fact that those variants use a different Sense kernel. So mostly only applied to Sense ROMs. AOSP ROMs (in particular Lineage) which use their own kernel, work okay with the CDMA variants, far as I've seen.
3) Your firmware is so out to day, it will not work with any of the current ROMs. And when I say current, I mean any from the past several years. You should definitely update the firmware in any case, as it will cause lots of problems with custom ROMs, and no good reason to stay on the old firmware. Once firmware is updated, it is not hard to flash TWRP and try Lineage again. I think it will work, and there is certainly no harm in trying, even if it doesn't. The worst case scenario is that you flash a more updated (Marshmallow) version of the stock Sprint ROM. Which is still better than where you started with all this.

redpoint73 said:
2) Instance of custom ROMs not working on M8 CDMA variants (Sprint and Verizon) are mainly due to the fact that those variants use a different Sense kernel. So mostly only applied to Sense ROMs. AOSP ROMs (in particular Lineage) which use their own kernel, work okay with the CDMA variants, far as I've seen.
3) Your firmware is so out to day, it will not work with any of the current ROMs. And when I say current, I mean any from the past several years. You should definitely update the firmware in any case, as it will cause lots of problems with custom ROMs, and no good reason to stay on the old firmware. Once firmware is updated, it is not hard to flash TWRP and try Lineage again. I think it will work, and there is certainly no harm in trying, even if it doesn't. The worst case scenario is that you flash a more updated (Marshmallow) version of the stock Sprint ROM. Which is still better than where you started with all this.
Click to expand...
Click to collapse
I updated the firmware. I now have this:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-main: 6.20.651.3
But the SIM doesn't work with Lineage anyway, just flashed in anew and tried. The old Sprint 6.0 ROM that I RUU'd has the same issue. Could it be the radio version, or the firmware? Because it used to work, with some troubles, but still.

gr0za said:
Could it be the radio version, or the firmware? Because it used to work, with some troubles, but still.
Click to expand...
Click to collapse
The radio is part of the firmware. Not sure why your SIM would have troubles with the newer radio (if that is the case).
You can try this: https://forum.xda-developers.com/htc-one-m8/general/how-to-convert-cdma-m8-sprint-vzw-gsm-t3303812
Or you can try flashing back to RUU 3.30.651.2 and see if there is any change.

redpoint73 said:
The radio is part of the firmware. Not sure why your SIM would have troubles with the newer radio (if that is the case).
You can try this: https://forum.xda-developers.com/htc-one-m8/general/how-to-convert-cdma-m8-sprint-vzw-gsm-t3303812
Or you can try flashing back to RUU 3.30.651.2 and see if there is any change.
Click to expand...
Click to collapse
Omg, how come I didn't see this thread. Thanks so much, I will try once I get back home.
I hope this thread isn't problematic, because I moved the goalpost since creating it. But I'd rather not create a thread every time I have a problem...

gr0za said:
I hope this thread isn't problematic, because I moved the goalpost since creating it. But I'd rather not create a thread every time I have a problem...
Click to expand...
Click to collapse
The problems are all related, and probably the same root cause (Sprint version, firmware, etc.). I agree it is most appropriate to keep everything to this one thread.