Develop Bugs

ROM for ATT One M8 OS:3.11.1700.5

Hello XDA forums. First off I would like to apologize if a thread or something like this already exists, but I already spent way too much time trying to unroot my friend's phone since his vibration motor stopped working. Basically all that I am looking for, is a rom that can be flashed on an ATT HTC One M8 with OS version: 3.11.1700.5 and HBOOT: 3.19. I tried flashing many Sense roms already, but they all don't work. What I think is that the rom's base firmware's second section after the initial number has to match the phone's OS version. An example of this would be with the Skydragon rom, where it is based on the 4.04.1700.4 firmware. But it still works even though it has a higher version number. So what it all comes down to, is that I need to find a rom that supports the x.1700 firmware line so I can flash it restore to stock (mostly at least) Also instructions for returning to complete stock while S-ON would be helpful. Last the stock rom would be the most preffered, since then I can use the stock recovery and relock the bootloader.

ssclanker said:
Hello XDA forums. First off I would like to apologize if a thread or something like this already exists, but I already spent way too much time trying to unroot my friend's phone since his vibration motor stopped working. Basically all that I am looking for, is a rom that can be flashed on an ATT HTC One M8 with OS version: 3.11.1700.5 and HBOOT: 3.19. I tried flashing many Sense roms already, but they all don't work. What I think is that the rom's base firmware's second section after the initial number has to match the phone's OS version. An example of this would be with the Skydragon rom, where it is based on the 4.04.1700.4 firmware. But it still works even though it has a higher version number. So what it all comes down to, is that I need to find a rom that supports the x.1700 firmware line so I can flash it restore to stock (mostly at least) Also instructions for returning to complete stock while S-ON would be helpful. Last the stock rom would be the most preffered, since then I can use the stock recovery and relock the bootloader.
Click to expand...
Click to collapse
Skydragon isn't Sense, it's AOSP.
Try ViperOneM8 3.2.1.
Download link here.
Thread link here.
Or if you want to go back to stock, there are stock ROM/recovery threads here, or you could run the latest RUU from HTC's website.

xunholyx said:
Skydragon isn't Sense, it's AOSP.
Try ViperOneM8 3.2.1.
Download link here.
Thread link here.
Click to expand...
Click to collapse
I already tried that. It doesn't work since the firmware base is not the correct one.

ssclanker said:
I already tried that. It doesn't work since the firmware base is not the correct one.
Click to expand...
Click to collapse
Yes, you are right. Sorry. I'm trying to communicate through hangouts, and helping a few people here.
The RUU is your best/only option to convert back to Sense. The instructions are in the link I provided, and the download is at the bottom of the page. Make sure to back up anything important, because this will wipe the phone.

I tried out the RUU, but it failed saying that it is incompatible with this phone. I did download the appropriate version for the phone (AT&T) but still it failed. This was also from the official HTC website. This is why I think I have to download a version that has an x.x.1700 in its version number. A Skydragon rom that is based on 4.04.1700 works on the phone, even though the phone has version 3.28.1700 so I think that any rom that is based on the x.x.1700 line will work. I did try out some other Sense roms, but they failed since they were based on a different firmware (x.x.502).
xunholyx said:
Yes, you are right. Sorry. I'm trying to communicate through hangouts, and helping a few people here.
The RUU is your best/only option to convert back to Sense. The instructions are in the link I provided, and the download is at the bottom of the page. Make sure to back up anything important, because this will wipe the phone.
Click to expand...
Click to collapse

ssclanker said:
I tried out the RUU, but it failed saying that it is incompatible with this phone. I did download the appropriate version for the phone (AT&T) but still it failed. This was also from the official HTC website. This is why I think I have to download a version that has an x.x.1700 in its version number. A Skydragon rom that is based on 4.04.1700 works on the phone, even though the phone has version 3.28.1700 so I think that any rom that is based on the x.x.1700 line will work. I did try out some other Sense roms, but they failed since they were based on a different firmware (x.x.502).
Click to expand...
Click to collapse
So, do you have Dev Ed phone, or did you convert it?
There are no Dev Ed RUUs that I know of.
Would I be correct in assuming that you changed you CID/MID? And would I also be correct in assuming you are S-Off?
---------- Post added at 06:12 PM ---------- Previous post was at 06:09 PM ----------
By re-reading the thread, if no conversion took place, you need to flash the stock Dev Ed ROM and recovery to allow for HTCs OTA updates.

The phone is not S-OFF, it is merely bootloader unlocked and is bought from ATT, so it is the ATT version of the phone with the appropriate AT&T branding. The phone was never S-OFF'ed and has no capabilities to do so, since it came out of the box with a patched firmware. And we are not going to pay 20$ for Sunshine, not because we think that it is a rip-off but it is quite hard to convince parents to spend money on phone that they do not know is rooted. I imagine that my friend's dad would be greatly agitated if he found out about him having rooted his phone.
Personal note:
I do not think that sunshine is a rip-off, as I understand that trying to crack the most basic level of a security on a phone is really quite hard and there are a lot of expenses involved.
xunholyx said:
So, do you have Dev Ed phone, or did you convert it?
There are no Dev Ed RUUs that I know of.
Would I be correct in assuming that you changed you CID/MID? And would I also be correct in assuming you are S-Off?
Click to expand...
Click to collapse

ssclanker said:
The phone is not S-OFF, it is merely bootloader unlocked and is bought from ATT, so it is the ATT version of the phone with the appropriate AT&T branding. The phone was never S-OFF'ed and has no capabilities to do so, since it came out of the box with a patched firmware. And we are not going to pay 20$ for Sunshine, not because we think that it is a rip-off but it is quite hard to convince parents to spend money on phone that they do not know is rooted. I imagine that my friend's dad would be greatly agitated if he found out about him having rooted his phone.
Personal note:
I do not think that sunshine is a rip-off, as I understand that trying to crack the most basic level of a security on a phone is really quite hard and there are a lot of expenses involved.
Click to expand...
Click to collapse
I'm not suggesting you get s-off, I'm asking if you are.
Your phone is a Dev Ed model. You will need a stock Dev Ed ROM and recovery to update via OTA.
Go here, and search for both. They are available in that thread.

Yeah, the developer RUU didn't work either. I looked at that page but I can't find any roms or RUU's with the x.1700 firmware. I have tried multiple times to restore from a Nandroid backup that had the same CID as me but different firmware version but it always failed.
Sorry if that came out as aggressive before.
xunholyx said:
I'm not suggesting you get s-off, I'm asking if you are.
Your phone is a Dev Ed model. You will need a stock Dev Ed ROM and recovery to update via OTA.
Go here, and search for both. They are available in that thread.
Click to expand...
Click to collapse

Developers Edition, unable to update.

Hey all, im not very software proficient, and I need some help in updating my HTC One M9 to Marshmallow.
I recently purchased it from my friend, and apparently, its an International version that is also the developers edition.
It came with TWRP already installed, but I flashed the stock recovery so that I could install the update from HTC itself, But everytime it finishes downloading the update, it gives me an error about it not downloading the correct file. I dont get it, cause its pretty much downloading it by itself, how can it not download the right version.
Is there anyway for me to check and find out exactly what version of the phone this is. Can someone please send me a reliable download link for the official Marshmallow update (already tried using the file on the official HTC website, but apparently had a file size flash limit, this was when using TWRP, not the official recovery) and detailed steps on how to flash it. I have tried multiple ways and have always stumbled upon several errors. Really hoping that nothing is wrong with my phone.
Thank you in advance.

Are you sure it's a developer edition, how do you know this?.
Beamed in by telepathy.

shivadow said:
Are you sure it's a developer edition, how do you know this?.
Beamed in by telepathy.
Click to expand...
Click to collapse
I dont know if it is or not, because when I got the phone, on startup it would give me text in red saying "developers edition, this phone is not for resale of distribution outside blah blah" I dont remember the exact text. But after I flashed the official recovery file, it doesnt give me that anymore.
So lets say its not a developers edition, how do I go about updating it?

Trafalgar747 said:
...on startup it would give me text in red saying "developers edition, this phone is not for resale of distribution...
Click to expand...
Click to collapse
That text is an indication that the bootloader got unlocked and that someone flashed something so that the phone is modified and not stock, anymore. It has nothing to do with the developer edition of the M9. The developer edition is just a US version of the M9 which gets delivered with a factory unlocked bootloader. Therefore chances are high that you flashed the wrong (in other words an incompatible) stock recovery. You need to find out the current firmware version of the phone and restore everything to stock by using a TWRP backup or a RUU. My signature contains a link to my google sheet. There you'll find instructions how to find and flash the correct RUU or how to find and correctly restore a corresponding TWRP backup. If you don't follow the instructions you won't be able to update your phone. Updates for the M9 and every other HTC phone that is newer are different than the ones for older HTC phones. My sheet might not contain a RUU for your firmware or a corresponding backup since I don't support every existing firmware. However you can find additional files in my thread (which is linked in the sheet, too, or can be found by visiting the general section). If no one contributed the files you need here on xda you'll need to use Llabtoofer's RUU service. Be aware that it's not for free.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
That text is an indication that the bootloader got unlocked and that someone flashed something so that the phone is modified and not stock, anymore. It has nothing to do with the developer edition of the M9. The developer edition is just a US version of the M9 which gets delivered with a factory unlocked bootloader. Therefore chances are high that you flashed the wrong (in other words an incompatible) stock recovery. You need to find out the current firmware version of the phone and restore everything to stock by using a TWRP backup or a RUU. My signature contains a link to my google sheet. There you'll find instructions how to find and flash the correct RUU or how to find and correctly restore a corresponding TWRP backup. If you don't follow the instructions you won't be able to update your phone. Updates for the M9 and every other HTC phone that is newer are different than the ones for older HTC phones. My sheet might not contain a RUU for your firmware or a corresponding backup since I don't support every existing firmware. However you can find additional files in my thread (which is linked in the sheet, too, or can be found by visiting the general section). If no one contributed the files you need here on xda you'll need to use Llabtoofer's RUU service. Be aware that it's not for free.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Sorry for sounding so noobish, but how do I find the exact firmware of my phone, I can move forward from there then. If its in about device, what particular detail do I need to keep in mind when finding the exact stock rom for my phone?

Trafalgar747 said:
Sorry for sounding so noobish, but how do I find the exact firmware of my phone, I can move forward from there then. If its in about device, what particular detail do I need to keep in mind when finding the exact stock rom for my phone?
Click to expand...
Click to collapse
It's explained in my sheet. And no, "settings > about" is not (always) the correct place if you want find out your firmware version.
Sent from my HTC One S using XDA Labs

Flippy498 said:
It's explained in my sheet. And no, "settings > about" is not (always) the correct place if you want find out your firmware version.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
So according to your chart, and my software number which is 1.32.61.15 it would mean that I have the a.bb.61.d - Orange UK (United Kingdom) version? Am I deducing this correctly?

Trafalgar747 said:
So according to your chart, and my software number which is 1.32.61.15 it would mean that I have the a.bb.61.d - Orange UK (United Kingdom) version? Am I deducing this correctly?
Click to expand...
Click to collapse
Correct. You're lucky. There is a RUU for your version on androidruu. Just google for "androidruu" and "HTC M9". You can use the instructions in my sheet for flashing it.
Sent from my HTC One S using XDA Labs

Flippy498 said:
Correct. You're lucky. There is a RUU for your version on androidruu. Just google for "androidruu" and "HTC M9". You can use the instructions in my sheet for flashing it.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
Just to be sure, if my friend who was previously using this phone, flashed another rom on it with the incorrect version, wouldnt the software number also change? Is there no other way to confirm the version of the phone?
Also, do I use the official TWRP download link in your sheet, is it the correct version for my phone?

Trafalgar747 said:
Just to be sure, if my friend who was previously using this phone, flashed another rom on it with the incorrect version, wouldnt the software number also change? Is there no other way to confirm the version of the phone?
Click to expand...
Click to collapse
The number in settings > about changes with the rom you're flashing. The one located in the download mode only changes if you update the phone with an official OTA or if you set your phone S-OFF via sunshine (which costs 25 bucks) and flash a RUU (or one of sneakyghost's firmware packs) with a different sku afterwards. However if the phone is S-OFF it wouldn't matter which RUU he flashed since with S-OFF almost every RUU can be used with your phone. Only CDMA versions (e.g. Verizon ones) stay incompatible.
Tl;dr: Just flash the 1.32.61.15 one. It's either way compatible with the phone.
Sent from my HTC One S using XDA Labs

Flippy498 said:
The number in settings > about changes with the rom you're flashing. The one located in the download mode only changes if you update the phone with an official OTA or if you set your phone S-OFF via sunshine (which costs 25 bucks) and flash a RUU (or one of sneakyghost's firmware packs) with a different sku afterwards. However if the phone is S-OFF it wouldn't matter which RUU he flashed since with S-OFF almost every RUU can be used with your phone. Only CDMA versions (e.g. Verizon ones) stay incompatible.
Tl;dr: Just flash the 1.32.61.15 one. It's either way compatible with the phone.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
You are a helpful genius mate, thank you. Just waiting for the download to finish, then will follow your steps. Will let you know how it goes. Thank you again.

I have a T-mobile HTC One M9. Can I update to nougat using the unlocked RUU?

Hi, I was wondering if it is possible for me to use the stock RUU to update to nougat on my htc one m9 rather than waiting for t-mobile to release a verified rom later in the year?

Yes u can. Just make sure that u are s-off and bootloader unlocked and then flash the dev edition ruu and u will get nougat.

Faisal0000 said:
Yes u can. Just make sure that u are s-off and bootloader unlocked and then flash the dev edition ruu and u will get nougat.
Click to expand...
Click to collapse
Not quite. To flash the developer RUU on a T-Mobile branded M9, you'll need to change your MID & CID to match the SKU of the developer edition RUU. If you don't know about these acronyms, stop what you are doing and read up. The FAQ section of the M9 readme thread, question 9, walks you through converting GSM phones (like the T-Mobile version) to the developer edition.

Faisal0000 said:
Yes u can. Just make sure that u are s-off and bootloader unlocked and then flash the dev edition ruu and u will get nougat.
Click to expand...
Click to collapse
Hi, And me I have htc one m9 sprint i can flash ruu nougat???

EKB8789 said:
Hi, And me I have htc one m9 sprint i can flash ruu nougat???
Click to expand...
Click to collapse
Not until Sprint releases the Android Nougat update.
The only update the is currently available is for the developer edition of the M9, a GSM model. Sprint is a CDMA carrier and incompatible with GSM.

Thanks for clarifying.
And you cannot flash on sprint or cdma phones. The ruu is only for gsm phones.

computerslayer said:
Not quite. To flash the developer RUU on a T-Mobile branded M9, you'll need to change your MID & CID to match the SKU of the developer edition RUU. If you don't know about these acronyms, stop what you are doing and read up. The FAQ section of the M9 readme thread, question 9, walks you through converting GSM phones (like the T-Mobile version) to the developer edition.
Click to expand...
Click to collapse
Thanks for linking me that. It also solved my question about why I was experiencing a bootloop, and gave me the method I had been searching for to crossflash

boredherobrine13 said:
Thanks for linking me that. It also solved my question about why I was experiencing a bootloop, and gave me the method I had been searching for to crossflash
Click to expand...
Click to collapse
Wonderful! Always nice when we find a solution. Kudos go to Flippy498, who created that thread and updates it as things come out, and to the many XDA members who have contributed to it.

computerslayer said:
Wonderful! Always nice when we find a solution. Kudos go to Flippy498, who created that thread and updates it as things come out, and to the many XDA members who have contributed to it.
Click to expand...
Click to collapse
Yup, now my next question is...how do i flash firmware v4...as I did CID/MID conversion to the Dev/Unlocked version, but now need the firmware, not just the RUU to flash

boredherobrine13 said:
Yup, now my next question is...how do i flash firmware v4...as I did CID/MID conversion to the Dev/Unlocked version, but now need the firmware, not just the RUU to flash
Click to expand...
Click to collapse
RUUs have the firmware along with everything else. While I'm pretty sure there's a way to flash individual components (radio, firmware, et cetera), that is beyond me. I stick to using the RUUs, and recommend them heartily. The easiest method is the SD card method - outlined in that same post. You'll end up wiping your internal phone storage (so back up what you care about), but it'll get you to the latest and greatest for the M9.

computerslayer said:
RUUs have the firmware along with everything else. While I'm pretty sure there's a way to flash individual components (radio, firmware, et cetera), that is beyond me. I stick to using the RUUs, and recommend them heartily. The easiest method is the SD card method - outlined in that same post. You'll end up wiping your internal phone storage (so back up what you care about), but it'll get you to the latest and greatest for the M9.
Click to expand...
Click to collapse
Really? I read that you couldn't use an RUU because verify key on firmware v1-3 is different from the one on v4, so you need v4 firmware to use a v4 RUU, which requires using a method. So I converted to dev/ATT/unlocked, flashed a v3 RUU I found online, and now I'm going to try to update to v4 which is apparently safer. If this fails, I'll try the RUU. After all, this is all vanilla to HTC so it should tell me if it won't work.

boredherobrine13 said:
Really? I read that you couldn't use an RUU because verify key on firmware v1-3 is different from the one on v4, so you need v4 firmware to use a v4 RUU, which requires using a method. So I converted to dev/ATT/unlocked, flashed a v3 RUU I found online, and now I'm going to try to update to v4 which is apparently safer. If this fails, I'll try the RUU. After all, this is all vanilla to HTC so it should tell me if it won't work.
Click to expand...
Click to collapse
I'm pretty sure the issues about keys has to do with trying to downgrade. But that's above my knowledge level.
I know for sure that you can apply the Nougat RUU after the Marshmallow RUU without issue because I have done this myself.

computerslayer said:
I'm pretty sure the issues about keys has to do with trying to downgrade. But that's above my knowledge level.
I know for sure that you can apply the Nougat RUU after the Marshmallow RUU without issue because I have done this myself.
Click to expand...
Click to collapse
Really? Well..I've already applied v3.0 and am going through all the updates. But Its certainly worth a try I suppose.

computerslayer said:
I'm pretty sure the issues about keys has to do with trying to downgrade. But that's above my knowledge level.
I know for sure that you can apply the Nougat RUU after the Marshmallow RUU without issue because I have done this myself.
Click to expand...
Click to collapse
Just tried. Got an err.

boredherobrine13 said:
Just tried. Got an err.
Click to expand...
Click to collapse
Are you trying to take OTA updates or using an RUU?
Also, what's the error message?

computerslayer said:
Are you trying to take OTA updates or using an RUU?
Also, what's the error message?
Click to expand...
Click to collapse
Tried to use an RUU. Got a signature error of some sort. Can't remember the number. RN it is taking OTA updates smoothly. Now, it will either get to v4 eventually through the OTA updates, or it will cut off at the top of v3 (in which case I have done something horribly wrong). I will try to flash RUU after I get v4 through OTA, just for fun and for the sake of the community
Edit 1: v4 finally showed up through OTA. 2GB Downloading currently. Will still RUU to double check compatibility. Will post back with success or not.
Edit 2: v4 was successful, device convered to HIMAULATT. Now flashing the Dev RUU, which works. It didn't work on v3. Therefor I was correct, and RUU v3 -> v4 isn't compatible.

boredherobrine13 said:
Tried to use an RUU. Got a signature error of some sort. Can't remember the number. RN it is taking OTA updates smoothly. Now, it will either get to v4 eventually through the OTA updates, or it will cut off at the top of v3 (in which case I have done something horribly wrong). I will try to flash RUU after I get v4 through OTA, just for fun and for the sake of the community
Edit 1: v4 finally showed up through OTA. 2GB Downloading currently. Will still RUU to double check compatibility. Will post back with success or not.
Edit 2: v4 was successful, device convered to HIMAULATT. Now flashing the Dev RUU, which works. It didn't work on v3. Therefor I was correct, and RUU v3 -> v4 isn't compatible.
Click to expand...
Click to collapse
Going from Marshmallow to Nougat is definitely possible (I've done it myself) - I'm not sure why your phone gave you such troubles. But in any case, I'm glad your phone is fully updated! Congratulations.

computerslayer said:
Going from Marshmallow to Nougat is definitely possible (I've done it myself) - I'm not sure why your phone gave you such troubles. But in any case, I'm glad your phone is fully updated! Congratulations.
Click to expand...
Click to collapse
As I wrote before, was not successful with mine. I was not able to flash Su 2.79. How did that work for you.
Pls can you make a discription how to
Mine is S-on, is it neccessary first to s-off

Mobile data not available (disconnected)

Hi. I have a M9 with model id 0PJA100. I bought it unlocked and s-off. One day, I flashed this rom named ICE with android nougat. After that, I cannot use my mobile data. I installed back stock rom to this phone and it is still the same. I can answer call and sms but I cannot get any mobile data. Today, I flashed Viper M9 v6 (nougat) and during the setup, I got H+ signal only for a few second and then it dissapeared. I dont really understand the problem and managed to install a lot of rom before. If anyone have any idea that can possibly make this device working, please reply to this thread. I hate to use my 5s as daily driver.

abdinsyakirin said:
Hi. I have a M9 with model id 0PJA100. I bought it unlocked and s-off. One day, I flashed this rom named ICE with android nougat. After that, I cannot use my mobile data. I installed back stock rom to this phone and it is still the same. I can answer call and sms but I cannot get any mobile data. Today, I flashed Viper M9 v6 (nougat) and during the setup, I got H+ signal only for a few second and then it dissapeared. I dont really understand the problem and managed to install a lot of rom before. If anyone have any idea that can possibly make this device working, please reply to this thread. I hate to use my 5s as daily driver.
Click to expand...
Click to collapse
Has your phone's firmware been updated to Nougat? What OS version does your phone report?

computerslayer said:
Has your phone's firmware been updated to Nougat? What OS version does your phone report?
Click to expand...
Click to collapse
I came from marshmallow stock rom 3.37 firmware but verizon version since i thought that my phone is verizon edition. Do i need to flash stock nougat before changing to nougat based custom rom?

Access point names. Change it to what you carrier uses or get them to send it to your phone.
abdinsyakirin said:
I came from marshmallow stock rom 3.37 firmware but verizon version since i thought that my phone is verizon edition. Do i need to flash stock nougat before changing to nougat based custom rom?
Click to expand...
Click to collapse
Yes you do. If you flash a nougat based rom over marshmallow it wont boot.
Beamed in by telepathy.

shivadow said:
Access point names. Change it to what you carrier uses or get them to send it to your phone.
Yes you do. If you flash a nougat based rom over marshmallow it wont boot.
Beamed in by telepathy.
Click to expand...
Click to collapse
I've changed the apn but still the same. I will try flashing nougat based firmware and then give u my feedback. U have any link for the firmware?

abdinsyakirin said:
Hi. I have a M9 with model id 0PJA100.
Click to expand...
Click to collapse
abdinsyakirin said:
I came from marshmallow stock rom 3.37 firmware but verizon version since i thought that my phone is verizon edition.
Click to expand...
Click to collapse
That's not the Verizon MID. Don't flash anything unless you definetely know which version of the M9 you own.
abdinsyakirin said:
U have any link for the firmware?
Click to expand...
Click to collapse
Did Verizon already release the android N update? I haven't heard of it, yet.
shivadow said:
If you flash a nougat based rom over marshmallow it wont boot.
Click to expand...
Click to collapse
Are you sure? I know that this was the case when you tried to use an android M rom with an android L firmware. However, I haven't heard of such cases after people flashed an android N rom on an android M firmware. Sometimes newer HTC stock roms/stock-based custom roms are booting fine on older firmware versions (but that doesn't mean that there won't be any other issues due to the mismatch of the rom base and the current firmware).

Flippy498 said:
That's not the Verizon MID. Don't flash anything unless you definetely know which version of the M9 you own.
Did Verizon already release the android N update? I haven't heard of it, yet.
Are you sure? I know that this was the case when you tried to use an android M rom with an android L firmware. However, I haven't heard of such cases after people flashed an android N rom on an android M firmware. Sometimes newer HTC stock roms/stock-based custom roms are booting fine on older firmware versions (but that doesn't mean that there won't be any other issues due to the mismatch of the rom base and the current firmware).
Click to expand...
Click to collapse
Yes i just know that my phone is an international version. Before this i thought it was verizon m9. Verizon did not release any nougat based firmware. But i think there is international version of nougat available
For the marshmallow to nougat question, i encountered some issues with the other rom. Some roms doesnt boot up and some others stuck on setup wizard since wifi cannot be enable.
So do u think i need to flash international version of nougat on my phone? Will it fix this mobile network problem.

abdinsyakirin said:
So do u think i need to flash international version of nougat on my phone? Will it fix this mobile network problem.
Click to expand...
Click to collapse
If you already flashed a Verizon firmware then you definetely need to flash a GSM RUU and should hope that your phone didn't get damaged unrecoverably. GSM devices and CDMA firmware (or vice versa) aren't compatible with each other.
Did you change your CID or your MID somewhen in the past? If not then please boot to download mode and tell us what version is stated behind "OS". If you did then I hope you wrote down your original MID and CID. At the moment I'd recommend you to flash whatever RUU belongs to your original firmware version since the issues you describe shouldn't happen if you use the correct stock rom.
After all reception problems on the stock rom got solved we can think about updating your phone to android 7 but at the moment we should only make one step at a time.

Flippy498 said:
If you already flashed a Verizon firmware then you definetely need to flash a GSM RUU and should hope that your phone didn't get damaged unrecoverably. GSM devices and CDMA firmware (or vice versa) aren't compatible with each other.
Did you change your CID or your MID somewhen in the past? If not then please boot to download mode and tell us what version is stated behind "OS". If you did then I hope you wrote down your original MID and CID. At the moment I'd recommend you to flash whatever RUU belongs to your original firmware version since the issues you describe shouldn't happen if you use the correct stock rom.
After all reception problems on the stock rom got solved we can think about updating your phone to android 7 but at the moment we should only make one step at a time.
Click to expand...
Click to collapse
My phone has SuperCID. Based on download mode, the OS- 3.37.605.13. Model ID 0PJA100 as stated before. I think the OS version is vzw not wwe since i flashed the vzw before. Actually, I bricked this device after i had my "mobile data disconnected" problem and asked somebody to help me fix it, and he flashed that firmware version (it is my fault since i thought this phone is verizon m9).
So, should I fully flash the wwe 3.35 firmware? Or what?

That's odd. I would have expected the current MID to be 0PJA30000. Did the MID get changed back to its original state after you flashed the Verizon RUU? Normally the M9 shouldn't accept a RUU if the MID doesn't match. Even the SCID won't change this fact, anymore, as it did on older HTC phones. Or are you talking about the original MID of the phone that is stated on the backside of the phone? I assume the answer to this question is yes since the MID you're talking about is two zeros too short for being a digital MID. Only the engraving on the backside of the phone uses this short version of MIDs.
Revert the SCID to one of the CIDs that belong to SKU 401 (but don't choose the demo unit CID HTC__002), if needed revert the MID to the one that belongs to this SKU and then flash the 3.35.401.12 RUU. Instructions can be found in the FAQ section of the ReadMe thread (the stickied one in the Q&A section and the General section).
After you flashed the GSM RUU your phone should be working normally, again, if the Verizon RUU didn't damage it unrecoverably. In addition, you should be able to install two OTAs (the latter is the update for Android 7) via the software update function of the phone.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
That's odd. I would have expected the current MID to be 0PJA30000. Did the MID get changed back to its original state after you flashed the Verizon RUU? Normally the M9 shouldn't accept a RUU if the MID doesn't match. Even the SCID won't change this fact, anymore, as it did on older HTC phones. Or are you talking about the original MID of the phone that is stated on the backside of the phone? I assume the answer to this question is yes since the MID you're talking about is two zeros too short for being a digital MID. Only the engraving on the backside of the phone uses this short version of MIDs.
Revert the SCID to one of the CIDs that belong to SKU 401 (but don't choose the demo unit CID HTC__002), if needed revert the MID to the one that belongs to this SKU and then flash the 3.35.401.12 RUU. Instructions can be found in the FAQ section of the ReadMe thread (the stickied one in the Q&A section and the General section).
After you flashed the GSM RUU your phone should be working normally, again, if the Verizon RUU didn't damage it unrecoverably. In addition, you should be able to install two OTAs (the latter is the update for Android 7) via the software update function of the phone.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Oh yes the MID changed to 0PJA30000, sorry for my last reply, that one i referred to the back engraving of m9. Im gonna change the CID and flash the firmware version u talked about. I will give you an update once I done it.

Flippy498 said:
That's odd. I would have expected the current MID to be 0PJA30000. Did the MID get changed back to its original state after you flashed the Verizon RUU? Normally the M9 shouldn't accept a RUU if the MID doesn't match. Even the SCID won't change this fact, anymore, as it did on older HTC phones. Or are you talking about the original MID of the phone that is stated on the backside of the phone? I assume the answer to this question is yes since the MID you're talking about is two zeros too short for being a digital MID. Only the engraving on the backside of the phone uses this short version of MIDs.
Revert the SCID to one of the CIDs that belong to SKU 401 (but don't choose the demo unit CID HTC__002), if needed revert the MID to the one that belongs to this SKU and then flash the 3.35.401.12 RUU. Instructions can be found in the FAQ section of the ReadMe thread (the stickied one in the Q&A section and the General section).
After you flashed the GSM RUU your phone should be working normally, again, if the Verizon RUU didn't damage it unrecoverably. In addition, you should be able to install two OTAs (the latter is the update for Android 7) via the software update function of the phone.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I dont get any mobile network, even worse than before. I flashed 3.35.401.12 like u told so. Do i need to flash it manually by extracting the folder and flash all the img inside it independently? If u have any suggestion let me know.
UPDATE: Actually i dont think the problem is with verizon firmware since I had the problem after I flashed ICE nougat rom (I came from SDreamTeam Sense8 rom). After that I bricked the device and told other person to help me flash vzw firmware because I thought it was verizon m9. This problem is very weird and i dont know how to relate the ICE rom with my current problem. OP of ICE rom said the rom not compatible with verizon m9 but since this phone is not verizon m9, i dont think there should be a problem right?

The RUU needs to get flashed via the SD card method that is described in the ReadMe thread.
As written there and in some of my posts in this thread, GSM devices and CDMA firmware (or vice versa) aren't compatible with each other due to the different partition layouts. Therefore, cross-flashing can lead to unrecoverable damages.
I can't tell you what happened while you've been using ICE and therefore I can't tell you whether your phone had been in a recoverable state at that time. However, chances are high that flashing a Verizon RUU instead of the correct GSM RUU was the nail in the coffin of your phone. Sorry, that I don't have better news.
Edit: Oh, and please remove the quote from your last post. It's not necessary to quote me every time you post here.

Flippy498 said:
That's not the Verizon MID. Don't flash anything unless you definetely know which version of the M9 you own.
Did Verizon already release the android N update? I haven't heard of it, yet.
Are you sure? I know that this was the case when you tried to use an android M rom with an android L firmware. However, I haven't heard of such cases after people flashed an android N rom on an android M firmware. Sometimes newer HTC stock roms/stock-based custom roms are booting fine on older firmware versions (but that doesn't mean that there won't be any other issues due to the mismatch of the rom base and the current firmware).
Click to expand...
Click to collapse
Exactly that, it's not worth the risk seeing as many people have reported that their phone won't boot after mismatching roms to base firmware. Updating to a nougat custom rom to a marshmallow firmware would be bad as the api's are completely different and would explain the non booting situation.
So, until someone can confirm that flashing a nougat custom rom over a marshmallow base is 100% safe I'm going to swing with "yes I'm sure".
Beamed in by telepathy.

shivadow said:
So, until someone can confirm that flashing a nougat custom rom over a marshmallow base is 100% safe I'm going to swing with "yes I'm sure".
Click to expand...
Click to collapse
Re-read what I posted. I never said that it would be "100% safe" *. Of course there'll be problems due to the mismatch. I was only asking whether there have been reports about bootloops. (Btw, Android n and Android m don't differ as much as Android m and Android l did.) And according to this post the brick didn't happen directly after flashing the nougat rom.
However, I searched through the dev section yesterday and according to the Viper thread and the 4.x TWRP Backup thread people have been able to boot nougat roms on Android m. A lot of them faced problems. E.g. I have read about many user who used the old firmware and faced overheating and/or battery drain problems in the backup thread. They all needed to root their rom for getting rid of the problems. (Altough I personally can't explain why SuperSU should be able to fix those problems...) It seems like users with the newer firmware on the other hand don't necessarily have to face these issues. Take my phone as an example. It's running just fine without any heat and/or battery problems.
* Although I think that the usage of "safe" might imply that flashing a rom might damage your phone and that's not the case. The worst things that can happen are a bootloop or if the rom is booting fine some lags/bugs. Only flashing an incompatible firmware (via a RUU or a firmware pack) leads to damages.
Edit: Don't know how I could forget that but the answer to the OP's original problem with the reception on ICE is probably explained with Q1 of the FAQ section.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
After you flashed the GSM RUU your phone should be working normally, again, if the Verizon RUU didn't damage it unrecoverably. In addition, you should be able to install two OTAs (the latter is the update for Android 7) via the software update function of the phone.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Since u didn't reply, i assume my device now damaged unrecoverably right?
EDIT: SORRY, I DID NOT GET ANY NOTIFICATION AND DONT READ THIS FORUM. VERY SORRY MY BAD. I AM VERY NEWBIE IN THIS KIND OF THINK.

Flippy498 said:
Edit: Don't know how I could forget that but the answer to the OP's original problem with the reception on ICE is probably explained with Q1 of the FAQ section.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thanks for the reply. Again sorry for my previous quote just now. Yes i read that q&a section and i did not have any of the problem except no mobile internet data. I can receive and make a phone call. Only mobile internet data. I am from 3.35 firmware if i am not mistaken since there was no official update after I purchased the phone. But NOW, I faced the problem after flashed GSM RUU. I do it twice, through exe and sdcard method. I also changed my CID and MID as u told me to.

The thing is that we don't know your original CID and your original firmware version. Not every SKU had a 3.35.x firmware version. That's why I'm guessing what the first problem might have been. If you say that there hasn't been any update at that time you probably used one of the SKUs that didn't have a 3.35.x firmware since those are the majority of SKUs that received the Android n update at a later time. But again, I can only assume what happened.
The problems you're facing now are probably a consequence of the cross-flashing. If flashing a GSM RUU could fix them then they're unrecoverable.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
The thing is that we don't know your original CID and your original firmware version. Not every SKU had a 3.35.x firmware version. That's why I'm guessing what the first problem might have been. If you say that there hasn't been any update at that time you probably used one of the SKUs that didn't have a 3.35.x firmware since those are the majority of SKUs that received the Android n update at a later time. But again, I can only assume what happened.
The problems you're facing now are probably a consequence of the cross-flashing. If flashing a GSM RUU could fix them then they're unrecoverable.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
So if i can find my original firmware version, i can solve this problem (if the verizon does not damage it) by flashing that version on my phone right? The only thing that I remember on my phone after i bought it is, it does not have any bloatware such as kid mode app, and when i clicked on software update, it said "please connect to XXXX to check an update" or something like that. XXXX referred to service provider in usa but i dont remember what company it was. I think there are still hope to recover this device.

I don't think that we can recover the phone even if we knew it's original firmware. That's why they're called "unrecoverable" damages.
For a GSM M9 it doesn't matter which RUU you flash (as long as it isn't a CDMA RUU). So if one GSM RUU didn't fix the situation then a different one won't be able to do so, either. And that's the reason why the ReadMe thread warns everybody not to cross-flash firmware files.
That part of my last post you're referring to was an explanation why I think that you faced problems with ICE. It has nothing to do with your current situation.
Sent from my HTC One M9 using XDA Labs

After S-OFF can I go from 3.xx.yyy.xx to 4.xx.zzz.xx?

I've gone through the (extremely confusing) readme thread several times but would appreciate a concrete answer on dev edition conversion.
My phone is hima_ulatt / firmware v3.38.502.12 / OPJA11000 / CWS_001.
So my question is, once i:
unlock bootloader > s-off > write cid BS_US001,
can i install ruu 4.30.617.12 or would i have to stay within 3.xx.617.xx versions?

jbonetwo said:
I've gone through the (extremely confusing) readme thread several times but would appreciate a concrete answer on dev edition conversion.
My phone is hima_ulatt / firmware v3.38.502.12 / OPJA11000 / CWS_001.
So my question is, once i:
unlock bootloader > s-off > write cid BS_US001,
can i install ruu 4.30.617.12 or would i have to stay within 3.xx.617.xx versions?
Click to expand...
Click to collapse
As far as I know you can't install a 4.x Ruu on 3.x firmware.
The encryption is different.

bubba1601 said:
As far as I know you can't install a 4.x Ruu on 3.x firmware.
The encryption is different.
Click to expand...
Click to collapse
Is there no way to update to the 4.xx versions then? The AT&T software update won't let me upgrade at all (says no updates found).

jbonetwo said:
Is there no way to update to the 4.xx versions then? The AT&T software update won't let me upgrade at all (says no updates found).
Click to expand...
Click to collapse
Download a 4.x based rom, there are several in the rom thread including the latest development rom.
They are stock ROMs that you can flash through twrp.
This one I've used and had no issues with.
https://forum.xda-developers.com/on...m9-4-14-617-6-stock-root-twrp-backup-t3518149
But if you are locked to ATT (unlike me because I'm in Europe and the European M9 is a GSM version.
You might want to try this version (ATT)
https://forum.xda-developers.com/one-m9/development/rom-stock-nougat-4-23-617-1-unlocked-t3553470

bubba1601 said:
Download a 4.x based rom, there are several in the rom thread including the latest development rom.
They are stock ROMs that you can flash through twrp.
This one I've used and had no issues with.
https://forum.xda-developers.com/on...m9-4-14-617-6-stock-root-twrp-backup-t3518149
But if you are locked to ATT (unlike me because I'm in Europe and the European M9 is a GSM version.
You might want to try this version (ATT)
https://forum.xda-developers.com/one-m9/development/rom-stock-nougat-4-23-617-1-unlocked-t3553470
Click to expand...
Click to collapse
Thank you!!

Please elaborate a bit further which part of the ReadMe thread confuses you. It's meant to be a helpful resource and if it's confusing at some point then it might need to get overhauled.
Flashing a rom won't update the firmware. Therefore, the linked roms won't help you much. (C.f. the article that is linked as "the difference between rom and firmware" in the further reading section of the ReadMe thread.)
You need to update the phone with an unencrypted firmware pack (that means an OTA or one of Sneakyghost's firmware packs). As already explained in this thread, RUUs with firmware 4.x use new encryption keys and therefore can't be used for updating from firmware 3.x. In addition, AT&T won't let you install OTAs on their branded phones if you aren't using one of their sim cards.
Either you convert to the 3.x version of the dev firmware and install the available OTAs afterwards or you need to flash a 4.x AT&T firmware pack from Sneakyghost's thread before you convert if you want to directly use the latest dev edition RUU.
Sent from my HTC One M9 using XDA Labs

I got confused too. It's confusing because the paragraphs digress and don't just follow the basic procedures. Probably because the information is necessary but not formatted into idiot speak.. idiot speak is what i needed.
So i thought "fk it my phone is dying anyway so how bad can it get"?.
If you're changing the cid and mid via fastboot do it first and get the firmware.zip of the region you want, at the phones CURRENT firmware level.
Flash the zip version of the firmware from external sdcard. To do that you need to
S-OFF: DONT NEED TO CHANGE ANYTHING.
S-ON: LOCK BOOTLOADER?? (CLARIFY)/CHANGE NOTHING?
rename the firmware.zip* file to whatever the filename asks for at the bottom of download mode (voldown+power), eg 0PJA***.ZIP.
copy it to the external Sdcard (not in a folder, just on its own), reboot phone to download mode, follow prompts.
THE PHONE WILL REBOOT MANY TIMES AND SHOULD TAKE AROUND 30 MINS TO 1 HOUR TO COMPLETE. DO NOT TOUCH THE PHONE. DO NOT TURN IT OFF. DO NOT UNPLUG IT FROM THE CHARGER. Leave it alone!!.
Once that completes you can take the ota.

Well, not everyone owns an SD card and there are other methods for flashing RUUs. That's why the RUU section describes all methods and the conversion guide only has a link to the RUU section. (The steps you describe are all mentioned in the guide for the SD card method.) This way users can choose which method they want to use. And describing all methods in both posts doesn't seem to make sense in my eyes, either.
The infos above the instructions of each post are actually needed for understanding why things are how they are if you've never owned an HTC device before. I can add a title "general info" for making clearer that the posts don't start with instructions, though.
The fact that you don't need to re-lock or lock the bootloader (neither for RUUs nor for OTAs) is e.g. explained in these additional infos. It's not mentioned in the instructions since that info itself is not an instruction.
Btw, a RUU reboots the phone only once and the flash shouldn't take longer than a couple of minutes. OTAs on the other hand can take up to am hour and reboot the phone several times.
Sent from my HTC One M9 using XDA Labs

Yes you are correct as always flippy. The reflash back to stock takes minutes while ota takes an age. Forgot that bit.
You also redefined what i said.. the posts digress to cover all eventualities but it is overwhelming to eejits like myself.
If it was laid out basic THEN cover the eventualities it'd be easier to follow. The english can be a tad broken too, which confuses the fk out of native English speakers like myself.
My post is just the basic. Nothing more, nothing less. If you bork your phone with my instruction it will be a hardware or user fault.
The only thing I'm not sure of, because my phone is s-off, is whether or not the bootloader must be locked or relocked with s-on. Otherwise with s-off they dont matter.
Don't get me wrong, I'm not saying you're feeding false info, I'm just saying that non native english speakers seem to have better results following your instructions better than native speakers, for some reason..

Flippy498 said:
Please elaborate a bit further which part of the ReadMe thread confuses you. It's meant to be a helpful resource and if it's confusing at some point then it might need to get overhauled.
Click to expand...
Click to collapse
Thanks for the info @Flippy498. I'll be re-reading everything thoroughly before attempting anything as i don't want to end up with a brick.
The readme is indeed confusing. It captures the evolution of the m9 since fw 1.xx and the corresponding changes to modding procedures. While this makes for a great catalogue of all info, even a seasoned flash-o-phile would find it difficult to navigate the veritable minefield of do's and don't's.
I'd love to redo the logic of the thread myself but don't know enough about this device yet. but perhaps something that determines one's fw/mid/cid through fastboot first, followed by targeted instructions for achieving different goals based on those differences would be much more legible. (e.g. if fw v 3.xx, do this to unlock but warning about flashing 4.xx). As it stands, coming from v 3.xx, one has to read several disjointed notes peppered around the thread only some of which are relevant and this only adds to the confusion via information overload.

If you have s-off youre good to go in any circumstances. Just check the os that it is on and return it to stock of that version os OR
If you change the cid and mid just flash to stock of THAT version AND the region you change to. Like changing from 401 to 617 you flash the 617 because it matches the cid and mid you changed to. It must still match the os version the phone is on ie marshmallow 3.35.xxx.xx, making it the 3.35.617.xx firmware you'd be looking to flash to get stock marshmallow..
Then you just take the ota updates as far as you like.
I flashed 2 s-off phones back to stock in the last week in one sitting and it was easy, just as I explained.
It's just bootloader in s-on conditions that I personally don't know and that throws me a bit. I don't know if it's a requirement or not. I'd highly recommend buying s-off via sunshine in all cases but otherwise flippy would have to answer a simple yes or no to "bootloader locked for s-on flashing?" or you'd have to dredge it up on a search site. The other option is bite the bullet and flash anyway hoping it boots you out with an error.

shivadow said:
flippy would have to answer a simple yes or no to "bootloader locked for s-on flashing?"
Click to expand...
Click to collapse
It doesn't matter whether the bootloader is locked, re-locked or unlocked.
Sent from my HTC One M9 using XDA Labs

shivadow said:
If you have s-off youre good to go in any circumstances. Just check the os that it is on and return it to stock of that version os OR
Click to expand...
Click to collapse
Your method worked great! changed cid & mid to dev edition, flashed dev edition and then used 'software update' to catch up to latest version. couldn't be easier, thanks!
Now for that obnoxious red text...

I take no credit for anything. All I did was make the process clearer. Glad you're sorted!.