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
Related
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
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.
Back in August, I got a HTC One M9 from Bluegrass Cellular. (The phone came with Android 5.1) I decided to root it and try a custom ROM. I downloaded a snapshot for CM13 himawl. (Since that's the variant according to Download mode) I flashed it in TWRP only to get an error about sbl1. I since found an unofficial nightly of cm12.1 himawl built on November 17, 2015. It flashed and works fine to this day, but I'd like to have newer features and better security. How would I go about doing this? I can't seem to find the correct RUU. I tried the unlocked RUU to see if it would work, but it was to no avail. I'm S-on if that helps.
purplekid97 said:
Back in August, I got a HTC One M9 from Bluegrass Cellular. (The phone came with Android 5.1) I decided to root it and try a custom ROM. I downloaded a snapshot for CM13 himawl. (Since that's the variant according to Download mode) I flashed it in TWRP only to get an error about sbl1. I since found an unofficial nightly of cm12.1 himawl built on November 17, 2015. It flashed and works fine to this day, but I'd like to have newer features and better security. How would I go about doing this? I can't seem to find the correct RUU. I tried the unlocked RUU to see if it would work, but it was to no avail. I'm S-on if that helps.
Click to expand...
Click to collapse
I'm pretty sure that in order to use a Marshmallow-based ROM (ie, CM 13), you need the Marshmallow firmware first. I imagine the same will be true for Nougat ROMs....though I don't think we've got anything beyond stock just yet.
I imagine that if you were able to achieve S-OFF on your phone, you could apply the appropriate RUU to get you up to the latest available firmware for your phone. To be clear, I don't know what that is (I'm not familiar with the himawl models) - but it should be possible.
computerslayer said:
I'm pretty sure that in order to use a Marshmallow-based ROM (ie, CM 13), you need the Marshmallow firmware first. I imagine the same will be true for Nougat ROMs....though I don't think we've got anything beyond stock just yet.
I imagine that if you were able to achieve S-OFF on your phone, you could apply the appropriate RUU to get you up to the latest available firmware for your phone. To be clear, I don't know what that is (I'm not familiar with the himawl models) - but it should be possible.
Click to expand...
Click to collapse
I believe that's what's going on here. I'm just trying to see if there are any alternatives or RUU's known to work with my s-on phone before I resort to the $25 investment of Sunshine.
purplekid97 said:
I believe that's what's going on here. I'm just trying to see if there are any alternatives or RUU's known to work with my s-on phone before I resort to the $25 investment of Sunshine.
Click to expand...
Click to collapse
Just for the fact you get an extra chance to unbrick if it goes wrong is worth the $25. IMO S-OFF is a necessity for htc phones.
Beamed in by telepathy.
I tried the test in the Sunshine app, but it said to flash stock or near stock rom. I mistakenly didn't backup my stock ROM before flashing cm12.1. Anyone know a ROM I could flash to s off?
purplekid97 said:
I tried the test in the Sunshine app, but it said to flash stock or near stock rom. I mistakenly didn't backup my stock ROM before flashing cm12.1. Anyone know a ROM I could flash to s off?
Click to expand...
Click to collapse
You're on Android 5, right? Android Revolution HD 14, which is built off of stock Android 5.1.0, should do the trick.
Very important sidenote: Don't change the MID/CID or the firmware of this device! It's a CDMA one and therefore not compatible with the GSM firmwares like the dev edition or the WWE one. Otherwise you'll end up with a fancy new paperweight. Just stay with the SKU (the three numbers between the second and the third dot in the firmware version) it is currently using since not even the different CDMA firmwares/devices are compatible with each other.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Very important sidenote: Don't change the MID/CID or the firmware of this device! It's a CDMA one and therefore not compatible with the GSM firmwares like the dev edition or the WWE one. Otherwise you'll end up with a fancy new paperweight. Just stay with the SKU (the three numbers between the second and the third dot in the firmware version) it is currently using since not even the different CDMA firmwares/devices are compatible with each other.
Click to expand...
Click to collapse
In my case, the SKU is 605. Is there a newer 605 I can update to access Marshmallow? I recall when I was stock, I tried to update to MM through OTA in settings, but apparently my carrier never approved the update. 5.1 appeared to be the "latest."
605 is the verizon-branded firmware. There definitely is an android m update for your phone.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
605 is the verizon-branded firmware. There definitely is an android m update for your phone.
Click to expand...
Click to collapse
Awesome! With my CID being LRA__001 would I be able to flash this?
0PJAIMG_HIMA_WL_M60_SENSE70_VZW_MR_VERIZON_WWE_3.3 [email protected]_CNV_1.26_002 _release_469809_signed_1 zip
The problem is it looks like it's WWE which you said wouldn't work.
purplekid97 said:
Awesome! With my CID being LRA__001 would I be able to flash this?
0PJAIMG_HIMA_WL_M60_SENSE70_VZW_MR_VERIZON_WWE_3.3 [email protected]_CNV_1.26_002 _release_469809_signed_1 zip
The problem is it looks like it's WWE which you said wouldn't work.
Click to expand...
Click to collapse
It's Verizon WWE. That's not the same as sku 401 (WWE).
Either you try that one or you download the exe from the HTC US website.
I can't say for sure whether it'll work. According to the sku the RUU should be flashable. You'll need to try by yourself. An alternative would be contacting llabtoofer's RUU service. However that one isn't for free. (Either search for it via google or use the direct link in my google sheet if you want to use that service.)
Sent from my HTC One M9 using XDA Labs
here's your RUU
KhurshidAbbas said:
I mistakenly flashed verizon firmware and now I've lost the network signals, My phone is currently in boot loop, restarting at it's own, I can't use open Mobile Networks App, My networks are not working at all, Some expert told me it's because I flashed wrong Radio.img along with rest of firmware.
Please provide me with stock firmware for Bluegrass Cellular.
I've lost every hope.
Click to expand...
Click to collapse
Source:
https://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Download:
https://www.androidfilehost.com/?fid=24591023225177985
Flippy498 did all the work. I just did some searching
rename to 0PJAIMG.zip place on sd card and reboot should fix it
Again its Flippy498's work
Started happen after I uninstalled MultiROM, the phone bricked and I had to RUU it. After RUU I tried all kinds of ROMS ( Viper One, CandySIX, ICE, LeeDrOid, Sky Dragon, etc... ) But most of them do not work ( boot loop ) and ones that work have unknown IMEI, unknown Baseband, and keeps searching for signal ( drains battery super quick ). I have superCID, S-OFF, Unlocked, Rooted everything. I am thinking I have corrupted of deleted my EFS partition, could someone please send me their backup so I can flash it?:crying:
Thank you so much for you help and have happy holidays,
You're probably trying to install a 3.35 rom on a 3.y firmware where y is not the same as 35.
I did try to install 3.35 firmware before installing ROM
Flippy498 said:
You're probably trying to install a 3.35 rom on a 3.y firmware where y is not the same as 35.
Click to expand...
Click to collapse
I tried all kinds of firmwares, even the newest from HTC site 3.42 if I remember right. I tried go all the way back to 1.xx to 2.xx and then to the 3.35 and 3.37 the most used ones. All of them are fine, just unknown IMEI and baseband, sim not found.
What was your original firmware?
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
What was your original firmware?
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I don't know what my original firmware was, if you mean the firmware when I bought it. If you mean the firmware before I ran into these problems, then it was 3.41 I think the newest from the HTC website at that time.
kazukazawa9 said:
I don't know what my original firmware was, if you mean the firmware when I bought it. If you mean the firmware before I ran into these problems, then it was 3.41 I think the newest from the HTC website at that time.
Click to expand...
Click to collapse
I meant the one before the problems. But 3.41 isn't the complete version it should be something like 3.41.xxx.yy. The part with xxx is the important part.
I think you might have flashed a GSM RUU on a CDMA device. The partition layouts of those two versions differ and flashing GSM on CDMA (or vice versa) may lead to unrecoverable damages.
3.35.xxx.yy is only available for GSM and the only US firmware with 3.41.xxx.yy I know is 3.41.651.yy (Sprint - CDMA).
Flippy498 said:
I meant the one before the problems. But 3.41 isn't the complete version it should be something like 3.41.xxx.yy. The part with xxx is the important part.
I think you might have flashed a GSM RUU on a CDMA device. The partition layouts of those two versions differ and flashing GSM on CDMA (or vice versa) may lead to unrecoverable damages.
3.35.xxx.yy is only available for GSM and the only US firmware with 3.41.xxx.yy I know is 3.41.651.yy (Sprint - CDMA).
Click to expand...
Click to collapse
ouch, then what should I do now? I didn't know there were two RUU versions, I might have done the exact thing you said. Is there no way to repair it except for hardware repair?
kazukazawa9 said:
ouch, then what should I do now? I didn't know there were two RUU versions, I might have done the exact thing you said. Is there no way to repair it except for hardware repair?
Click to expand...
Click to collapse
If you're lucky you can recover your phone by flashing the latest 651/Sprint RUU. But I can't guarantee for anything.
I have an M9 with Eragon rom flashed, which is android 5, if I try to flash ANY other rom, it never boots, I figured it was something about the firmware, but I have absolutely no idea what I'm looking for, I'm using the mexican M9, unlocked, S-ON (i don't really know what any of this means), I have access to TWRP but for the life of me I can't figure out what I need to download or flash, it's really frustrating (and yes, I've used the search funcion but like I said, I don't even know what I'm looking for.
Radamenenthil said:
I have an M9 with Eragon rom flashed, which is android 5, if I try to flash ANY other rom, it never boots, I figured it was something about the firmware, but I have absolutely no idea what I'm looking for, I'm using the mexican M9, unlocked, S-ON (i don't really know what any of this means), I have access to TWRP but for the life of me I can't figure out what I need to download or flash, it's really frustrating (and yes, I've used the search funcion but like I said, I don't even know what I'm looking for.
Click to expand...
Click to collapse
Read through the readme thread at the top of this forum. It has everything you need.
computerslayer said:
Read through the readme thread at the top of this forum. It has everything you need.
Click to expand...
Click to collapse
I did, but what am I looking for? I tried the SD thing and it failed
Radamenenthil said:
I did, but what am I looking for? I tried the SD thing and it failed
Click to expand...
Click to collapse
The rom version MUST MATCH THE FIRMWARE VERSION. If you need to flash stock then you need to get it back to stock condition by following the thread that flippy spent ages on, it is in the general section stickies.
Beamed in by telepathy.
But how do I know which rom version and firmware version I have? and do I have to go back to stock? I don't understand anything about the RUU stuff (i tried downloading one and using the SD method thing to flash it, but it gave me an error)
Radamenenthil said:
But how do I know which rom version and firmware version I have? and do I have to go back to stock? I don't understand anything about the RUU stuff (i tried downloading one and using the SD method thing to flash it, but it gave me an error)
Click to expand...
Click to collapse
The readme thread, particularly the section on RUUs is what you need.
You need to look up your OS version, identify the SKU and match that to the RUUs that are available. Then you can download and apply the correct software to your phone.
The readme thread explains this, step by step. Check it out and post any questions you have from there in this thread.
computerslayer said:
The readme thread, particularly the section on RUUs is what you need.
You need to look up your OS version, identify the SKU and match that to the RUUs that are available. Then you can download and apply the correct software to your phone.
The readme thread explains this, step by step. Check it out and post any questions you have from there in this thread.
Click to expand...
Click to collapse
I found the SKU, it's 600, should I just download that and try to flash it with the SD method thing?
computerslayer said:
The readme thread, particularly the section on RUUs is what you need.
You need to look up your OS version, identify the SKU and match that to the RUUs that are available. Then you can download and apply the correct software to your phone.
The readme thread explains this, step by step. Check it out and post any questions you have from there in this thread.
Click to expand...
Click to collapse
Radamenenthil said:
I found the SKU, it's 600, should I just download that and try to flash it with the SD method thing?
Click to expand...
Click to collapse
I just tried the SD method thing, with the correct SKU RUU, didn't work...
I get
"Failed: -2, 19: fail to flash via downloadzip"
three times, please i'm at a total loss of what to do
Radamenenthil said:
I just tried the SD method thing, with the correct SKU RUU, didn't work...
I get
"Failed: -2, 19: fail to flash via downloadzip"
three times, please i'm at a total loss of what to do
Click to expand...
Click to collapse
I don't know how to interpret the error code, but perhaps we can rule out the obvious. What is your current OS version?
---------- Post added at 09:42 AM ---------- Previous post was at 09:37 AM ----------
computerslayer said:
I don't know how to interpret the error code, but perhaps we can rule out the obvious. What is your current OS version?
Click to expand...
Click to collapse
Also, we're not talking about a phone error - you've got a perfectly working device. The problem is that your firmware is outdated and current ROMs require Marshmallow or Nougat firmware. From the looks of it, your SKU doesn't have any updates available.
Assuming you have correctly identified your SKU as 600, your best bet is to achieve S-OFF and change your phone SKU to the developer SKU so that you can update to the latest firmware for the M9. Keep in mind that you will lose any carrier specific features that may be included in the 600 SKU firmware (such as VoLTE, wifi calling).
Before taking that step, be sure that you've properly identified your SKU - if you turn out to have a CDMA phone/SKU, attempting to apply other firmware will almost certainly brick it.
computerslayer said:
I don't know how to interpret the error code, but perhaps we can rule out the obvious. What is your current OS version?
---------- Post added at 09:42 AM ---------- Previous post was at 09:37 AM ----------
Also, we're not talking about a phone error - you've got a perfectly working device. The problem is that your firmware is outdated and current ROMs require Marshmallow or Nougat firmware. From the looks of it, your SKU doesn't have any updates available.
Assuming you have correctly identified your SKU as 600, your best bet is to achieve S-OFF and change your phone SKU to the developer SKU so that you can update to the latest firmware for the M9. Keep in mind that you will lose any carrier specific features that may be included in the 600 SKU firmware (such as VoLTE, wifi calling).
Before taking that step, be sure that you've properly identified your SKU - if you turn out to have a CDMA phone/SKU, attempting to apply other firmware will almost certainly brick it.
Click to expand...
Click to collapse
I got desperate and I tried another SKU, 599, which had the same CID as mine (but apparently a higher version) and it actually worked, it started flashing and all, i'm on the "Android is starting... Optimizing apps" screen right now, somewhat relieved, I hope it works, I've been at this for like 3 days
and I can't pay for S-OFF, I'm totally broke (and I feel kinda salty because I already paid for that app once lol)
Radamenenthil said:
I got desperate and I tried another SKU, 599, which had the same CID as mine (but apparently a higher version) and it actually worked, it started flashing and all, i'm on the "Android is starting... Optimizing apps" screen right now, somewhat relieved, I hope it works, I've been at this for like 3 days
and I can't pay for S-OFF, I'm totally broke (and I feel kinda salty because I already paid for that app once lol)
Click to expand...
Click to collapse
Interesting and weird. I can't explain why a RUU of another SKU would work on your phone - unless your phone is actually SKU 599 and not 600. I am glad it worked, however!
My guess is that the reason for that being possible is the fact that those two SKUs share the same CID and MID. I don't even know the difference between the two SKUs (assuming that there actually is one). :silly:
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
My guess is that the reason for that being possible is the fact that those two SKUs share the same CID and MID. I don't even know the difference between the two SKUs (assuming that there actually is one). :silly:
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Apparently one is specifically from Mexico (Telcel) and the other one (that worked) was Latinamerica in general...
So now that I'm in stock android 6, how would I go about getting Nougat on it? or rooting? (I don't know if I should make a new thread for this)
Radamenenthil said:
Apparently one is specifically from Mexico (Telcel) and the other one (that worked) was Latinamerica in general...
Click to expand...
Click to collapse
Well, that info is taken from the naming of the RUUs. What I meant was the content. Why would HTC decide to use the same MID and CID for two SKUs. As far as I know this situation is unique. Have you been able to notice any differences of the two RUUs software.
The telcel one didn't work because it was probably too old for your phone. With S-ON downgrades are only possible in some rare cases.
Radamenenthil said:
So now that I'm in stock android 6, how would I go about getting Nougat on it? or rooting? (I don't know if I should make a new thread for this)
Click to expand...
Click to collapse
Not every SKU already received the Android N update. You may need to wait a bit longer.
If your bootloader is still unlocked you can flash TWRP and SuperSU. The correct versions for each firmware version of the M9 are stated in the ReadMe thread.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Well, that info is taken from the naming of the RUUs. What I meant was the content. Why would HTC decide to use the same MID and CID for two SKUs. As far as I know this situation is unique. Have you been able to notice any differences of the two RUUs software.
The telcel one didn't work because it was probably too old for your phone. With S-ON downgrades are only possible in some rare cases.
Not every SKU already received the Android N update. You may need to wait a bit longer.
If your bootloader is still unlocked you can flash TWRP and SuperSU. The correct versions for each firmware version of the M9 are stated in the ReadMe thread.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
thank you, after that, I should be ok flashing MM roms and stuff?