Verizon M8 CM12.1 - 4G/GPS not working - One (M8) Q&A, Help & Troubleshooting

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.

Related

WiFi will not turn on after custom ROM installs

So, just for a bit of background info:
I found out about the release of Lollipop for the HTC One M8 is in February. Me, being the kinda impatient type, wanted it sooner! So, having never messed around with android devices before, thought "Why not now?" And dived in to some tutorials. After unlocking my bootloader, installing TWRP as the recovery, and installing a new ROM to do the S-Off with firewater, I learned a few things: Firewater doesn't work anymore, the next best (and seemingly only) alternative costs $25, my phone wasn't booting up anymore, and I hadn't made a backup.
So yeah, that sucked. After attempting to side load the ROM and a few different ROMS, I finally managed to find a stock ROM that worked on the first load and actually booted successfully at an acceptable rate.
<b>SO WHERE I'M AT NOW</B>
Everything is fine and dandy now, with the exception of one thing: the WiFi will not turn on. I will press the WiFi "switch," and it will only become greyed out. All of my other wireless connections will work, and I am not on airplane mode (I have even switched that on and off plenty of times as well). The only solution I could find through searching was to flash the boot.img that came in the ROM, and that didn't work.
As for specs, I'm a little inexperienced, so I don't know what to provide other than this:
HTC One M8
Carrier: AT&T
Not rooted, and don't plan on it
Boot loader is unlocked
I believe it is on a stock ROM
Does anybody know how to fix this? Any help would be appreciated!
Sent from my HTC One_M8 using XDA Free mobile app
Your firmware is mismatched with the ROM you flashed.
Either flash a ROM that matches your firmware, or RUU back to stock (need to relock bootloader with s-on to run RUU).
Also, why do so many folks skip the step of not making a nandroid backup? This should be a mandatory step before doing any mods or flashing a ROM. I don't ever leave my phone without a known good nandroid or at least a known good ROM.zip.
redpoint73 said:
Also, why do so many folks skip the step of not making a nandroid backup? This should be a mandatory step before doing any mods or flashing a ROM. I don't ever leave my phone without a known good nandroid or at least a known good ROM.zip.
Click to expand...
Click to collapse
OK, so I didn't exactly NOT make a backup... I just made the wrong type of backup. I'm new to all this, and for some reason my mind thought it was OK to back up all my DATA, not to make a backup image. I feel pretty stupid about that, and you're allowed to feel the same way about me.
Also, would you have instructions on finding a ROM that fits the firmware? Like I've said, I'm new to this and I also can't find anything about it - everything assumes that I know everything there is to know already! And the fact that'll AT&T doesn't release the M8 RUUs doesn't help either.
Sent from my HTC One_M8 using XDA Free mobile app
hardcore_spaghetti said:
OK, so I didn't exactly NOT make a backup... I just made the wrong type of backup. I'm new to all this, and for some reason my mind thought it was OK to back up all my DATA, not to make a backup image. I feel pretty stupid about that, and you're allowed to feel the same way about me.
Also, would you have instructions on finding a ROM that fits the firmware? Like I've said, I'm new to this and I also can't find anything about it - everything assumes that I know everything there is to know already! And the fact that'll AT&T doesn't release the M8 RUUs doesn't help either.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Who told you there were no RUUs for AT&T?
Here ya go:
http://dl3.htc.com/application/RUU_...20.51A.4198.01L_F_release_387305_signed_2.exe
---------- Post added at 07:38 PM ---------- Previous post was at 07:14 PM ----------
redpoint73 said:
Your firmware is mismatched with the ROM you flashed.
Either flash a ROM that matches your firmware, or RUU back to stock (need to relock bootloader with s-on to run RUU).
Also, why do so many folks skip the step of not making a nandroid backup? This should be a mandatory step before doing any mods or flashing a ROM. I don't ever leave my phone without a known good nandroid or at least a known good ROM.zip.
Click to expand...
Click to collapse
People don't like to follow instructions. I ALWAYS have a recent backup. If stuff goes bad, you can go back to the way it was before you screwed stuff up. It is the most basic step when flashing/modding; and it is always step #1 on any ROM/mod thread, but people like to skip it for some reason. I guess people like to learn the hard way.
xunholyx said:
Who told you there were no RUUs for AT&T?
Click to expand...
Click to collapse
Me and the people who were looking for AT&T-branded RUUs, not Cingular! I'll give it a try, thanks a lot!
Sent from my HTC One_M8 using XDA Free mobile app
EDIT:
It worked! Thank you so much for that RUU. My phone is running great now.
hardcore_spaghetti said:
Me and the people who were looking for AT&T-branded RUUs, not Cingular! I'll give it a try, thanks a lot!
Click to expand...
Click to collapse
I don't know why they still use the "Cingular" name in the RUU title. But regardless, you will find the AT&T RUUs listed in a variety of places, including the HTC website:
http://www.htc.com/us/support/htc-one-m8-att/news/
---------- Post added at 09:19 AM ---------- Previous post was at 09:10 AM ----------
hardcore_spaghetti said:
OK, so I didn't exactly NOT make a backup... I just made the wrong type of backup. I'm new to all this, and for some reason my mind thought it was OK to back up all my DATA, not to make a backup image. I feel pretty stupid about that, and you're allowed to feel the same way about me.
Click to expand...
Click to collapse
Well, at least you thought to make a backup of some sort, which is better than a lot of folks. My rant was aimed at folks who (all too often) know well that they should make a backup, and don't bother to do so. Than are all "Uh oh, I can't boot now and didn't make a backup. What should I do?"
Modding the phone with no backup plan and no plan to recover = a bad idea.
hardcore_spaghetti said:
Also, would you have instructions on finding a ROM that fits the firmware? Like I've said, I'm new to this and I also can't find anything about it - everything assumes that I know everything there is to know already!
Click to expand...
Click to collapse
The information is all here if you read and search enough; but I'll admit the concept of "firmware" is a bit confusing.
The short answer: Boot into bootloader, and unless you've tampered with hboot in some way (not possible with s-on) the hboot number will correspond with your current firmware version, which will also tell you what software based ROMs you can run properly:
hboot 3.16 = 1.x software
hboot 3.18 = 2.x software
hboot 3.19 = 3.x software
If you look at the title or top post of each custom ROM, they will usually call out what software version the ROM is based. So you just need to find one that corresponds to your hboot number, flash it, and everything should work find. If you are looking at a specific ROM, and still can't determine what software version its based, just post a link here and we will answer that.
If you are currently on hboot 3.16 (1.x firmware) you can also relock the bootloader and run the 2.23 RUU to update to the 2.x firmware; and then be able to run 2.x software based ROMs. But with s-on, you can't update to 3.x firmware yet, until AT&T releases the corresponding OTA and/or RUU. There are methods to update to 3.x firmware with s-off.
You can read more technical info about firmware here: http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
redpoint73 said:
Your firmware is mismatched with the ROM you flashed.
Either flash a ROM that matches your firmware, or RUU back to stock (need to relock bootloader with s-on to run RUU).
Also, why do so many folks skip the step of not making a nandroid backup? This should be a mandatory step before doing any mods or flashing a ROM. I don't ever leave my phone without a known good nandroid or at least a known good ROM.zip.
Click to expand...
Click to collapse
Hey about that your firmware doesn't match the rom HOW COULD I KNOW?
Void tracer said:
Hey about that your firmware doesn't match the rom HOW COULD I KNOW?
Click to expand...
Click to collapse
You would only know by reading or searching. But its discussed on many threads, including the various custom ROM threads (sometimes in one of the top posts of the ROM thread).
For the most part, if you are changing to a higher software number (first number in the string: 1.x to 2.x, 3.x , etc.) you will need to update your firmware accordingly. This goes mostly for Sense ROMs; although some GPE or AOSP ROMs also require certain firmwares or at least an updated hboot. Again, check the specific ROM thread for details.
redpoint73 said:
You would only know by reading or searching. But its discussed on many threads, including the various custom ROM threads (sometimes in one of the top posts of the ROM thread).
For the most part, if you are changing to a higher software number (first number in the string: 1.x to 2.x, 3.x , etc.) you will need to update your firmware accordingly. This goes mostly for Sense ROMs; although some GPE or AOSP ROMs also require certain firmwares or at least an updated hboot. Again, check the specific ROM thread for details.
Click to expand...
Click to collapse
i still don't understand .... i went for a rom called revolutionhd and got stuck in boot loop,, spent around 8 hours trying different things , after that i got lucky that a rom called maxiumushd worked , i am s-on the dev says S-on will probably face a certain problems one of them is camera issue and files disappeared , that i fixed by the way he mentioned it should be fixed , but the wifi fix You must update firmware to latest 4.xx.xxx.x i don't understand , by installing his rom didn't i update to that version? the 4.xx.xxx.x ? or i must be at the same version before i flash a rom with that version? if yes, now roms are modding the current software? not also upgrading? and in my case i was 4.4.4 i think what should i do? i can't upgrade to lolipop? i didn't study for my finals thinking the device got bricked please help me out this is the second day ...
Void tracer said:
i still don't understand .... i went for a rom called revolutionhd and got stuck in boot loop,, spent around 8 hours trying different things , after that i got lucky that a rom called maxiumushd worked , i am s-on the dev says S-on will probably face a certain problems one of them is camera issue and files disappeared , that i fixed by the way he mentioned it should be fixed , but the wifi fix You must update firmware to latest 4.xx.xxx.x i don't understand , by installing his rom didn't i update to that version? the 4.xx.xxx.x ? or i must be at the same version before i flash a rom with that version? if yes, now roms are modding the current software? not also upgrading? and in my case i was 4.4.4 i think what should i do? i can't upgrade to lolipop?.
Click to expand...
Click to collapse
Your confusion is a bit understandable. The term "firmware" is confusing. Its true that in the past, the term "firmware" has sometimes been used interchangeably with "ROM". However in this case (and most frequently when talking about this phone), we are not talking about the ROM; but rather we are talking about a number of other modules including hboot, radio, recovery, WiFi, Bluetooth and others that actually do not get flashed with the ROM. And in fact, most of these modules can't be modified by "unofficial" means unless you have s-off.
HTC has also developed a somewhat contrived situation on their recent devices, in that while they claim to be "friendly to the mod community" by letting users unlock the bootloader and flash ROMs; they also have been in the habit of making significant updates to the firmware for every major software update (update from from Android 4.4.2 to 4.4.3, etc). And if you don't update the firmware when flashing a ROM of a higher software base, you are going to run into some major issues as you have seen (most commonly broken WiFi and extreme long boot times).
For a little more explanation on firmware vs. ROM, the following link has some good info: http://forum.xda-developers.com/showthread.php?p=52484527
You can still update the firmware with s-on by installing your version's OTA of (if available) RUU. You can also flash a firmware.zip if one has been posted for your CID that is still HTC signed/encrypted. But many firmware zips are not signed, and in that case you can't flash it unless you have s-off.
Void tracer said:
i didn't study for my finals thinking the device got bricked please help me out this is the second day ...
Click to expand...
Click to collapse
You can erase the notion in your mind that this phone is ever bricked, if the screen comes on. As long as the screen comes on, this phone is virtually always recoverable. And usually not that hard, just involves knowing the correct steps.
Also one of the cardinal rules of flashing ROMs, is always have a known good nandroid backup before flashing. Having a known-good nandroid to revert to resolves a lot of "OMG I bricked the phone" moments.
redpoint73 said:
Your confusion is a bit understandable. The term "firmware" is confusing. Its true that in the past, the term "firmware" has sometimes been used interchangeably with "ROM". However in this case (and most frequently when talking about this phone), we are not talking about the ROM; but rather we are talking about a number of other modules including hboot, radio, recovery, WiFi, Bluetooth and others that actually do not get flashed with the ROM. And in fact, most of these modules can't be modified by "unofficial" means unless you have s-off.
HTC has also developed a somewhat contrived situation on their recent devices, in that while they claim to be "friendly to the mod community" by letting users unlock the bootloader and flash ROMs; they also have been in the habit of making significant updates to the firmware for every major software update (update from from Android 4.4.2 to 4.4.3, etc). And if you don't update the firmware when flashing a ROM of a higher software base, you are going to run into some major issues as you have seen (most commonly broken WiFi and extreme long boot times).
For a little more explanation on firmware vs. ROM, the following link has some good info: http://forum.xda-developers.com/showthread.php?p=52484527
You can still update the firmware with s-on by installing your version's OTA of (if available) RUU. You can also flash a firmware.zip if one has been posted for your CID that is still HTC signed/encrypted. But many firmware zips are not signed, and in that case you can't flash it unless you have s-off.
You can erase the notion in your mind that this phone is ever bricked, if the screen comes on. As long as the screen comes on, this phone is virtually always recoverable. And usually not that hard, just involves knowing the correct steps.
Also one of the cardinal rules of flashing ROMs, is always have a known good nandroid backup before flashing. Having a known-good nandroid to revert to resolves a lot of "OMG I bricked the phone" moments.
Click to expand...
Click to collapse
Thanks you big time for explaining this to me i did go to a nandroid backup of my same cid/mid and everything was good , restored using twrp i still have the wifi issue ... i tried to flash the latest OTA and it failed (after going to stock) i really don't know what to do googled everything .. do u think i should make a thread for it?
Void tracer said:
Thanks you big time for explaining this to me i did go to a nandroid backup of my same cid/mid and everything was good , restored using twrp i still have the wifi issue ... i tried to flash the latest OTA and it failed (after going to stock) i really don't know what to do googled everything .
Click to expand...
Click to collapse
You probably installed the nandroid that didn't match with your firmware, so you are going to have the same issue as with a custom ROM: Your current firmware version doesn't match the software (OS) version.
What CID, what hboot number? What nandroid did you restore?
Void tracer said:
do u think i should make a thread for it?
Click to expand...
Click to collapse
We've already been back and forth on your issue on this thread, and its relevant to this thread's topic. So NO I don't think you should make a new thread.
redpoint73 said:
You probably installed the nandroid that didn't match with your firmware, so you are going to have the same issue as with a custom ROM: Your current firmware version doesn't match the software (OS) version.
What CID, what hboot number? What nandroid did you restore?
We've already been back and forth on your issue on this thread, and its relevant to this thread's topic. So NO I don't think you should make a new thread.
Click to expand...
Click to collapse
I believe its correct here is the link to the thread : http://forum.xda-developers.com/showthread.php?t=2701376
go to nandroid backups then all other CIDS i grabbed the htc__59 here is my phone info :
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__059
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Void tracer said:
I believe its correct here is the link to the thread : http://forum.xda-developers.com/showthread.php?t=2701376
go to nandroid backups then all other CIDS i grabbed the htc__59
Click to expand...
Click to collapse
Yes, but which one did you use exactly? There are 3 different software numbers available for your CID on the stock nandroid thread: 1.54, 2.22 and 3.32.
redpoint73 said:
Yes, but which one did you use exactly? There are 3 different software numbers available for your CID on the stock nandroid thread: 1.54, 2.22 and 3.32.
Click to expand...
Click to collapse
newest which is 3.32
Void tracer said:
newest which is 3.32
Click to expand...
Click to collapse
Your hboot (3.18) corresponds with 2.22, you want to restore that nandroid.
The 3.32 nandroid doesn't match with your 2.22 firmware. That is why WiFi is still broken.
redpoint73 said:
Your hboot (3.18) corresponds with 2.22, you want to restore that nandroid.
The 3.32 nandroid doesn't match with your 2.22 firmware. That is why WiFi is still broken.
Click to expand...
Click to collapse
so i download 2.2 and i am good to go?
Void tracer said:
so i download 2.2 and i am good to go?
Click to expand...
Click to collapse
Yes, you should be.
redpoint73 said:
Yes, you should be.
Click to expand...
Click to collapse
Hey man just installed it everything works TY big time , but umm now i want to update to the maximushd rom and i have to update as i understood to match the android version of the rom itself , i am s-on and unlocked, now i have to re-lock to flash it ? and then unlock again to flash the rom??
Void tracer said:
Hey man just installed it everything works TY big time , but umm now i want to update to the maximushd rom and i have to update as i understood to match the android version of the rom itself , i am s-on and unlocked, now i have to re-lock to flash it ? and then unlock again to flash the rom??
Click to expand...
Click to collapse
What you want to do now, is apply any available OTA updates available for your CID. You will need to update to 3.x software (Android 4.4.4) than to 4.x (Android 5.0, Lollipop). Do you know if Lollipop has been rolled out for your version?
The OTA will also update your firmware (not just the ROM). Then once you are on Lollipop firmware, you will be able to run any custom Lollipop ROMs.
You do not need to relock the bootloader to install the OTA. And I do not recommend you do so (its better unlocked).
Reason for that, once you are OTA updated to Lollipop, you can then re-install custom recovery (you need an unlocked bootloader for that) then you can install a custom ROM (such as MaximumHD as you asked).

No SIM Detected Suddenly

I know this is a common issue for the HTC One M8, but my phone stopped recognising any SIM card all of a sudden. It happened right after the battery got discharged fully (sudden power off), though I'm not ruling out the possibility that recent drops might have contributed to this.
I already tried the scotch tape solution to no avail as well as wiping cache and dalvik and rebooting a bunch of times with, without, and with other SIM cards in.
I'm running this Google Play Edition flashable ROM with the corresponding firmware, unrooted and s-on.
Should I go straight to re-flashing the same firmware and ROM? Is there anything I could attempt before having everything wiped?
One weird note that I've also noticed in another post: if I go to "phone info" the IMEI and phone number show as "unknown", but I can see them with fastboot getvar all. Also in "phone info", the "TURN OFF RADIO" button doesn't seem to be doing anything when pressed. Any alternative way to do it?
Thank you! :fingers-crossed:
AlexanderGrey said:
I'm running this Google Play Edition flashable ROM with the corresponding firmware, unrooted and s-on.
Should I go straight to re-flashing the same firmware and ROM? Is there anything I could attempt before having everything wiped?
Click to expand...
Click to collapse
The RUU provided in the GPE thread you linked, would be my suggestion. Should be same (or similar) to flashing the ROM and firmware. But with the RUU, you are sure to have all partitions (around 40) returned to "factory stock" (at least for GPE version) condition.
You might also try another RUU (return to Sense) or another ROM. But in any case, you should backup your data and prepared to fully wipe. Trying to migrate data across ROMs is only going to complicate matters, and you will never be sure that the SIM issue is due to the some incompatibility with your existing user data.
redpoint73 said:
The RUU provided in the GPE thread you linked, would be my suggestion. Should be same (or similar) to flashing the ROM and firmware. But with the RUU, you are sure to have all partitions (around 40) returned to "factory stock" (at least for GPE version) condition.
You might also try another RUU (return to Sense) or another ROM. But in any case, you should backup your data and prepared to fully wipe. Trying to migrate data across ROMs is only going to complicate matters, and you will never be sure that the SIM issue is due to the some incompatibility with your existing user data.
Click to expand...
Click to collapse
Thanks for the quick reply.
I haven't gone the GPe RUU route as that would require s-off, which I'm not planning to get. I forgot to mention I've been using this ROM & firmware for over 2 months without any issues.
I'm not very familiar with the topic of backup - although I've flashed ROMs in the past I've always done a clean install. Could you please elaborate? Would I be able to save installed apps with a backup via TWRP? Or would you advise against that?
AlexanderGrey said:
I haven't gone the GPe RUU route as that would require s-off, which I'm not planning to get. I forgot to mention I've been using this ROM & firmware for over 2 months without any issues.
Click to expand...
Click to collapse
You wouldn't have been able to flash the GPE firmware s-on, unless it is a signed zip and you have an actual GPE version M8 (correct CID and MID). The requirements for flashing the firmware are same as the RUU.
Please do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the device.
AlexanderGrey said:
I'm not very familiar with the topic of backup - although I've flashed ROMs in the past I've always done a clean install. Could you please elaborate? Would I be able to save installed apps with a backup via TWRP? Or would you advise against that?
Click to expand...
Click to collapse
There are lots of ways to backup data, each with their pros and cons. So how you do it is up to you.
A TWRP backup of app data is only going to work if you are just restoring the same ROM. So if you are flashing the RUU/ROM same as you have now, then it will work.
But if you try another ROM, it's usually not a good idea to try to "migrate" app data using TWRP. Different ROMs store their app data in different ways, and trying to migrate the data across different ROMs via TWRP backup is asking for trouble. In those cases, I use Titanium Backup for apps and app data (requires root). There are other options, but Titanium is tried and true (for most) and it is what I personally use.
Other data, like photos, videos you took, and any other media you want to keep (music, ringtones, porn) you can just copy to a computer, SD card, cloud solutions etc. Again, there are lots of options.
redpoint73 said:
You wouldn't have been able to flash the GPE firmware s-on, unless it is a signed zip and you have an actual GPE version M8 (correct CID and MID). The requirements for flashing the firmware are same as the RUU.
Please do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the device.
There are lots of ways to backup data, each with their pros and cons. So how you do it is up to you.
A TWRP backup of app data is only going to work if you are just restoring the same ROM. So if you are flashing the RUU/ROM same as you have now, then it will work.
But if you try another ROM, it's usually not a good idea to try to "migrate" app data using TWRP. Different ROMs store their app data in different ways, and trying to migrate the data across different ROMs via TWRP backup is asking for trouble. In those cases, I use Titanium Backup for apps and app data (requires root). There are other options, but Titanium is tried and true (for most) and it is what I personally use.
Other data, like photos, videos you took, and any other media you want to keep (music, ringtones, porn) you can just copy to a computer, SD card, cloud solutions etc. Again, there are lots of options.
Click to expand...
Click to collapse
Thanks for the info on backing up, I should have been more specific though. I've used Titanium Backup in the past a little bit, but recently I've opted to keep my phone unrooted mostly for some banking apps I use. Backing up with TWRP sounds good to me as I'd like to keep the same ROM (ideally) and would not want to go through reinstalling everything.
My phone is not a GPE version however the ROM I currently use is compatible with all M8 versions (except dual-sim) and with s-on. Here's the info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ********
(bootloader) imei: ********
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__002
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
AlexanderGrey said:
My phone is not a GPE version however the ROM I currently use is compatible with all M8 versions (except dual-sim) and with s-on. Here's the info:
(bootloader) version-main: 6.12.401.4
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__002
Click to expand...
Click to collapse
The GPE firmware never flashed (maybe you flashed it, and it failed to install). Otherwise, the version-main number would have changed to a GPE version number (5.07.1700.15 as noted in the firmwares you linked). And as mentioned, it isn't possible to flash GPE firmware while s-on (firmware for a different CID, MID).
Now, none of this explains your SIM issue. Maybe start by simply "dirty" flashing the GPE ROM (keep user data, just wipe cache and Dalvik) and see if there is any change.
redpoint73 said:
The GPE firmware never flashed (maybe you flashed it, and it failed to install). Otherwise, the version-main number would have changed to a GPE version number (5.07.1700.15 as noted in the firmwares you linked). And as mentioned, it isn't possible to flash GPE firmware while s-on (firmware for a different CID, MID).
Now, none of this explains your SIM issue. Maybe start by simply "dirty" flashing the GPE ROM (keep user data, just wipe cache and Dalvik) and see if there is any change.
Click to expand...
Click to collapse
Hmm you're right, my memory is playing tricks on me. I remember flashing a new firmware however, because I was having issues with the wi-fi and bluetooth before it. After some searching I think I used this one, am I right?
I'll try a quick firmware flash as you indicated, and will get back with the results a bit later. Thanks!
AlexanderGrey said:
Hmm you're right, my memory is playing tricks on me. I remember flashing a new firmware however, because I was having issues with the wi-fi and bluetooth before it. After some searching I think I used this one, am I right?
Click to expand...
Click to collapse
That would be my guess, yes.
AlexanderGrey said:
I'll try a quick firmware flash as you indicated, and will get back with the results a bit later. Thanks!
Click to expand...
Click to collapse
Flashing firmware requires you to relock the bootloader (since you are s-on) which will wipe your data.
As I mentioned in my last response, you might try to just "dirty flash" the GPE ROM (keep the current firmware) just to see what happens, before taking any measure which cause your data to be wiped.
I would still recommend to backup your data before even a dirty flash - you can't be too safe!
AlexanderGrey said:
Hmm you're right, my memory is playing tricks on me. I remember flashing a new firmware however, because I was having issues with the wi-fi and bluetooth before it. After some searching I think I used this one, am I right?
I'll try a quick firmware flash as you indicated, and will get back with the results a bit later. Thanks!
Click to expand...
Click to collapse
Unfortunately, no visible change . Still no SIM detected.
redpoint73 said:
That would be my guess, yes.
Flashing firmware requires you to relock the bootloader (since you are s-on) which will wipe your data.
As I mentioned in my last response, you might try to just "dirty flash" the GPE ROM (keep the current firmware) just to see what happens, before taking any measure which cause your data to be wiped.
I would still recommend to backup your data before even a dirty flash - you can't be too safe!
Click to expand...
Click to collapse
Sorry, I meant re-flashing the ROM. That's what I did so far.
AlexanderGrey said:
Sorry, I meant re-flashing the ROM. That's what I did so far.
Click to expand...
Click to collapse
You may consider flashing the Euro RUU 6.12.401.4 form here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
This will put your phone on a fully stock software/firmware "baseline" (for your phone's original configuration). If the SIM problem persists after that, I would have to think it was a hardware issue.
RUU as you know, will wipe the phone. So backup your data accordingly, before relocking the bootloader and running the RUU.
redpoint73 said:
You may consider flashing the Euro RUU 6.12.401.4 form here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
This will put your phone on a fully stock software/firmware "baseline" (for your phone's original configuration). If the SIM problem persists after that, I would have to think it was a hardware issue.
RUU as you know, will wipe the phone. So backup your data accordingly, before relocking the bootloader and running the RUU.
Click to expand...
Click to collapse
Thanks redpoint, that's the same one I have installed currently, right?
I guess ultimately I'll have to bite the bullet and try it if I want to figure out if it's a software or hardware issue.
AlexanderGrey said:
Thanks redpoint, that's the same one I have installed currently, right?
Click to expand...
Click to collapse
Same version number as the currently installed firmware. But what you flashed before is just firmware (about 80 MB) which includes hboot, radio, recovery, boot.img, and several others (maybe about 10 partitions?). The RUU (about 1.5 GB) will restore a complete factory image (every partition - about 40 of them).
redpoint73 said:
Same version number as the currently installed firmware. But what you flashed before is just firmware (about 80 MB) which includes hboot, radio, recovery, boot.img, and several others (maybe about 10 partitions?). The RUU (about 1.5 GB) will restore a complete factory image (every partition - about 40 of them).
Click to expand...
Click to collapse
Ah I understand now, I was not aware of that previously.
I was also planning to replace my battery so I might just do that first and have a look if anything looks unusual around the SIM card tray.
Thanks for all the help, I'll come back with a conclusion after a day or two when I get the chance .
redpoint73 said:
Same version number as the currently installed firmware. But what you flashed before is just firmware (about 80 MB) which includes hboot, radio, recovery, boot.img, and several others (maybe about 10 partitions?). The RUU (about 1.5 GB) will restore a complete factory image (every partition - about 40 of them).
Click to expand...
Click to collapse
Update: after replacing the battery I flashed the RUU and the same ROM back on.
Good news is the SIM card works now . I'm just a bit concerned about this happening again. Since you've seen quite a few cases on this forum I wanted to ask: do you think this is a common issue with that particular ROM?
I searched for SIM card issues in the thread of that ROM but the only legit ones I saw were the cases where people only installed the ROM without updating the firmware (so their wifi and bluetooth was not working either).
Cheers.
AlexanderGrey said:
Good news is the SIM card works now . I'm just a bit concerned about this happening again. Since you've seen quite a few cases on this forum I wanted to ask: do you think this is a common issue with that particular ROM?
Click to expand...
Click to collapse
Nothing that I am aware of. Running GPE ROM with Sense firmware might not be ideal. But I don't recall seeing any similar cases (no SIM).

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...

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.

Categories

Resources