Develop Bugs

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

Cant update from: 3.35.617.31, Getting errors with RUU, Cant OTA

Hello,
I have bought HTC One M9 off Aliexpress.
I bought it as developer version. When it came I started OTA upgrade. It downloads and then it says update cannot be performed because of modified system.
I cant even use RUU to get it working, I receive error 132. While chatting to HTC support their run my IMEI by their system. It came back as T-Mobile (US) version. Even though on back of my phone is engraved -
Model: OPJA110 which should mean it is developer version.
On my download mode it states: S-on, official system and locked bootloader.
Can anyone give me some tips how to get the newest system installed?
I have been trying for past 2 days without any luck to figure it out.
Any help is appreciate.
EDIT: Forgot CID:11111111 MID: 0PJA11000
Thank you very much.

Please read the ReadMe thread. It'll explain the causes of your issues and contains the needed files and instructions for fixing it. (C.f. the conversion guide, the RUU and the OTA section)
The most important infos: OTAs aren't installable while the phone is using the SuperCID and firmware 4.x RUUs aren't flashable on phones with firmware 3.x or lower due to new encryption keys.
Sent from my HTC One M9 using XDA Labs

Thanks for your time.

Flippy498 said:
Please read the ReadMe thread. It'll explain the causes of your issues and contains the needed files and instructions for fixing it. (C.f. the conversion guide, the RUU and the OTA section)
The most important infos: OTAs aren't installable while the phone is using the SuperCID and firmware 4.x RUUs aren't flashable on phones with firmware 3.x or lower due to new encryption keys.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I have read ReadMe.
So that means I need to S-OFF my phone using SunShine (other oprions?)
Then changing CID to BS_US001 (because Im running .617. system)
Then I can flash RUU (3.35.617.31)
And after that I can use OTA updates?
Do I need to unlock bootloader through HTCdev or is enough to check OEM Unlocking under developer options?
Thank you again for your time.

Oh, I missed that you're S-ON. Follow the unlocking/rooting guide in the same thread.
If you're lucky the previous owner used Sunshine, as well, so that you don't have to pay, again. (The license is saved on their servers and gets linked to the device.) The alternatives to Sunshine are a Java card, an XTC clip or similar tools which are way more expensive.
It doesn't matter which of the CIDs that belong to SKU 617 you use. They both work fine.
Alternatively, you could send the device back to the seller and ask for a refund. He obviously modified the phone and didn't restore the phone to a stock state properly before he sold it. The phone definetly was S-OFF in the past since no HTC phone gets shipped with the SuperCID. And if the IMEI belongs to a T-Mobile M9 according to HTC then the MID got changed with the help of S-OFF, as well. The backside can actually get replaced, too, if you know how to do it.
After you restored a CID that corresponds to your SKU you should be able to receive OTAs, again. Just for safety reasons I'd flash a 3.x RUU, as well, if I were you. The differences between the GSM versions of the M9 are so minor that you can convert the phone from one version to another. Therefore, you don't need to use the T-Mobile firmware and can stick with the dev one if you want.

Flippy498 said:
Oh, I missed that you're S-ON. Follow the unlocking/rooting guide in the same thread.
If you're lucky the previous owner used Sunshine, as well, so that you don't have to pay, again. (The license is saved on their servers and gets linked to the device.)
It doesn't matter which of the CIDs that belong to SKU 617 you use. They both work fine.
Alternatively, you could send the device back to the seller and ask for a refund. He obviously modified the phone and didn't restore the phone to a stock state properly before he sold it. The phone definetly was S-OFF in the past since no HTC phone gets shipped with the SuperCID. And if the IMEI belongs to a T-Mobile M9 according to HTC then the MID got changed with the help of S-OFF, as well. The backside can actually get replaced, too, if you know how to do it.
After you restored a CID that corresponds to your SKU you should be able to receive OTAs, again. Just for safety reasons I'd flash a 3.x RUU, as well, if I were you. The differences between the GSM versions of the M9 are so minor that you can convert the phone from one version to another. Therefore, you don't need to use the T-Mobile firmware and can stick with the dev one if you want.
Click to expand...
Click to collapse
Ok, Im gona pay that 25 bucks, it doesnt really matter.
So, I should start with unlocking bootloader via HTCdev.
After that I need to use SunShine.
Changing CID.
Flashing 3.x RUU.
And then doing OTA.
Is that all correct?
And should I install TWRP or stay on stock recovery after unlocking bootloader?
Really appreciate your time.

Correct.
Just follow the guides in the ReadMe thread starting from this post till the end of the conversion guide. (Theoretically, you can skip the backup part and save some time since you should be able to use the 3.x RUU even with the SuperCID on your phone.)

Flippy498 said:
Correct.
Just follow the guides in the ReadMe thread starting from this post till the end of the conversion guide. (Theoretically, you can skip the backup part and save some time since you should be able to use the 3.x RUU even with the SuperCID on your phone.)
Click to expand...
Click to collapse
Thanks,
is there a point in TWRP backup? Wont it stop OTA updates? On my other phone (Ulefone Metal) It is not possible to get OTA with custom recovery.

It actually is possible on the M9 and newer HTC phones as long as the system partition doesn't get modified, beforehand. (Further info can be found in the OTA section of the ReadMe thread.)
However, flashing a RUU restores everything on the phone back to stock (including the recovery). That's why I suggested flashing one after changing the CID.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
It actually is possible on the M9 and newer HTC phones as long as the system partition doesn't get modified, beforehand. (Further info can be found in the OTA section of the ReadMe thread.)
However, flashing a RUU restores everything on the phone back to stock (including the recovery). That's why I suggested flashing one after changing the CID.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thank you, I did as I said.
After flashing 3.x RUU OTA was successful.
That updated my system to: 4.16.617.6.
After that I continued by flashing latest RUU (4.30.617.12).
Everything went well. Until this point. When I booted the device I got to choose language. But there are just few (20 or so) available.
Unfortunately no Czech which I want. On previous version (4.16.617.6) there was huge list to choose from, including Czech.
Im still using 617 edition.
Where is the problem? Is here a way to get Czech lang. working again?
One again thank you for your time and effort

HTC probably removed the languages from the selection. Don't ask me why. I have no clue.
You could try setting up the phone in English and then switching to Czech via the app MoreLocal2. There's a thread about the app somewhere hidden on xda (sorry, I don't have a direct link at hand). You should be able to find it via google.
Sent from my HTC One M9 using XDA Labs

HTC One M9 - Stock Recovery Needed to get OTA Nougat Update

Hi,
I'm looking for a stock recovery.img for my HTC One M9. I'm trying to update to Android 7.0 Nougat, but TWRP is preventing me from completing the OTA install. I'm on stock 3.41.651.41 ROM with an unlocked bootloader, TWRP.
Basically I want the whole phone back to stock and able to take the Android 7.0 OTA update has released. I just bought this phone and it has TWRP recovery installed and running stock 3.41.651.41
I tried to update using the RUU exe downloaded from the HTC link above, but i got the error 132 (signature error).
Whenever i try to install the available OTA update it just boots into TWRP and nothing happens. I want the stock recovery image so that i could flash it in TWRP (or any other way) so that i would be able to install the OTA.
at
Info:
Sotware status Official
UNLOCKED
S-OFF
HTC DOWNLOAD MODE
UNLOCKED
(bootloader) product: htc_himaulatt PVT S-OFF
CID: 11111111
LK-1.0.0.0000
RADIO-3 00.C1144084060114
OPENDSP 15-6.1.00522.8994.1026
OS : 3.41.651.41
Nov 2 2016

Please take a look at the ReadMe thread (especially the RUU, the stock recovery and the OTA section). You'll find all needed information and files there.
Sent from my HTC One M9 using XDA Labs

Hello
Thanks for your reply , Please can you help to get the direct link for the tutorial to get a stock recovery on my HTC One m9 and to get the OTA Update.
Thanks

It's not that hard to find. ? I'm sure you'll directly see it if you either visit the General or the Q&A section.
Sent from my HTC One M9 using XDA Labs

Hi
I have tried many Roms updates without any results , Please if you can help me directly i will be soo reconized .
Thanks

Discliamer: Don't get the following message wrong. It neither means that I'm annoyed nor pissed. This is an honest question since I really don't understand it and you're by far not the only person that makes me ask myself the following:
Why does nobody read the ReadMe thread? It's pinned above all normal threads in the General and the Q&A section. In other words it's not hidden at all. Is it due to its naming? If so how do I need to rename it so that people actually read it? Or is it due to the length of its guides? Well, it's not possible to shorten them without deleting important information.
If people would read the ReadMe thread at least 90% of the questions in this section wouldn't get posted since the answers are already covered there*.
* E.g. the RUU section tells you exactly which RUU to use and why RUUs with firmware 4.x (like the ones on HTC's website) can't be used on phones with older firmware versions (version 3.x and below). If people read it they didn't need to "try many roms/RUUS" without success like you did. Then, the OTA section explains that the SuperCID shouldn't be used if you want install OTAs. In addition, the OTA and Stock Recovery sections both explain that simply unrooting and flashing the Stock Recovery isn't enough for being able to install OTAs. And with the explanation of the SKU that can be found above all downloads and with the MID/CID/SKU list in the further reading section you can find out which kind of firmware you're using (branded/unbranded and/or the country/continent that it belongs to). Btw, it's Sprint in your case so be careful with what you're trying to flash on that phone since it's a CDMA device (c.f. the warnings that can be found all over the ReadMe thread).

Hello Back ;
im following this guide :
rename firmware to 0PJAIMG.zip
-copy 0PJAIMG.zip to ext_sd card
-boot into bootloader or download mode
-it will scan your ext_sd card, then ask if you want to start the update
-press volume up & let it do it's thing...
When i press volume up and confirm update i get this error message
HTC ONE M9 fail 22 RU HEADER ERROR
Please help me to solve this issue.

Did you read the post with the most common RUU errors in the ReadMe thread?

Flippy498 said:
Did you read the post with the most common RUU errors in the ReadMe thread?
Click to expand...
Click to collapse
Yes , i have found this guide and i get theses errors

Flippy498 said:
Please take a look at the ReadMe thread (especially the RUU, the stock recovery and the OTA section). You'll find all needed information and files there.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
But aren't the links to all the T-Mobile stock files linked to from the HTC One M9 ReadMe thread are dead, and have been for well over a year (since I got my HTC One M9)?
[Edit: Nevermind, I might be stupid.]

48roses said:
But aren't the links to all the T-Mobile stock files linked to from the HTC One M9 ReadMe thread are dead, and have been for well over a year (since I got my HTC One M9)?
[Edit: Nevermind, I might be stupid.]
Click to expand...
Click to collapse
Are you sure that you're talking about the ReadMe thread? When I checked it the last time all links were working...
Sent from my HTC One M9 using XDA Labs

Can someone please point me in the direction....

Of the last/latest/final?? UK HTC M9 RUU Full stock.
Is there such a thing or do I have to use some mutated version of it?
I know the US have Fullstock RUU's but I cant find a UK one.
I'm expecting around 2GB size. With all the firmware, full wipe etc...
Thanks in advance!

Indeed there is for the wwe version (401) https://androidfilehost.com/?fid=817550096634758268
I have the file on my external sdcard for those moments where your phone thinks it's a toaster.
A lot will depend on whether your phone is locked to carrier or not. Carrier versions are hard to find.

shivadow said:
Indeed there is but I don't have any links. I have the file on my external sdcard for those moments where your phone thinks it's a toaster.
A lot will depend on whether your phone is locked to carrier or not. Carrier versions are hard to find.
Click to expand...
Click to collapse
Lol, I've Super CID it so no it's not locked to carrier.
I've Googled and only managed to find the US version from the HTC support site.
I've emailed HTC support so will wait for them.
Thanks

Htc has never provided and is never going to provide RUUs for their non-US devices. They even stopped providing US RUUs since the U11. If you own a non-US HTC device or a US model that is at least as young as the U11 then you rely on the files that get leaked on websites like ir-file or easy-firmware. The file that is linked above is a re-upload of such a leaked RUU since ir-file and easy-firmware require you to pay per download.
Sent from my HTC U12+ using XDA Labs

Flippy498 said:
Htc has never provided and is never going to provide RUUs for their non-US devices. They even stopped providing US RUUs since the U11. If you own a non-US HTC device or a US model that is at least as young as the U11 then you rely on the files that get leaked on websites like ir-file or easy-firmware. The file that is linked above is a re-upload of such a leaked RUU since ir-file and easy-firmware require you to pay per download.
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Thanks Flippy, and I don't suppose the M9 is getting Oreo either...so I might as well stick with the last unlocked/developer edition RUU that I got from HTC/US/Support and root my phone again, yes?
And is there any way of getting rid of that Emergency app thing....?

eskimosound said:
I don't suppose the M9 is getting Oreo either...
Click to expand...
Click to collapse
Every HTC flagship reaches its EOL state two years after its launch. For the M9, this date was in spring 2017. In other words, unless you plan to flash an Oreo-based custom rom you won't see Android 8 on your M9.
eskimosound said:
so I might as well stick with the last unlocked/developer edition RUU that I got from HTC/US/Support and root my phone again, yes?
Click to expand...
Click to collapse
Aternatively, you can use the RUU that got linked above. It's the latest unbranded European RUU. It doesn't matter which SKU you use. The differences are almost non-existent.
(Sidenote: There is no WWE SKU. SKU 401 equals the unbranded European version, 708 the unbranded Asian/Hongkong version, 709 the unbranded Asian/Taiwanese version, 710 the unbranded Australian version and 617 the unbranded US American version.)
eskimosound said:
And is there any way of getting rid of that Emergency app thing....?
Click to expand...
Click to collapse
Which emergency app are you talking about?

Flippy498 said:
Every HTC flagship reaches its EOL state two years after its launch. For the M9, this date was in spring 2017. In other words, unless you plan to flash an Oreo-based custom rom you won't see Android 8 on your M9.
Aternatively, you can use the RUU that got linked above. It's the latest unbranded European RUU. It doesn't matter which SKU you use. The differences are almost non-existent.
(Sidenote: There is no WWE SKU. SKU 401 equals the unbranded European version, 708 the unbranded Asian/Hongkong version, 709 the unbranded Asian/Taiwanese version, 710 the unbranded Australian version and 617 the unbranded US American version.)
Which emergency app are you talking about?
Click to expand...
Click to collapse
I will try that RUU linked above....
The emergency Red/Orange Triangle that is linked to E911 in settings....says it cannot be removed and I believe it is so USA citizens can get Red, Amber and Yellow terrorist threat alerts!!
Even when rooted I can't find it to remove and it seems to have cropped up in Marshmallow and Nougat HTC OS's

Wait, so you don't own a European M9? If that's the case and the phone is S-ON then you won't be able to use the 401 RUU. And in case it's an American CDMA variant, you won't be able to use that RUU without damaging the phone, either, even if the phone is S-OFF.
Please take a look at the ReadMe thread. It contains all information you'll need for finding the correct RUU for your phone.
I've never heard of such an app. I've never owned a US M9, either, though.
Sent from my HTC U12+ using XDA Labs

Flippy498 said:
Wait, so you don't own a European M9? If that's the case and the phone is S-ON then you won't be able to use the 401 RUU. And in case it's an American CDMA variant, you won't be able to use that RUU without damaging the phone, either, even if the phone is S-OFF.
Please take a look at the ReadMe thread. It contains all information you'll need for finding the correct RUU for your phone.
I've never heard of such an app. I've never owned a US M9, either, though.
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Thanks for your concern Flippy, no chill, I've got an International M9, (At leased that's whay the guy in China told me)
I've Unlocked Bootloader, S-Off (using Sunshine) and it was rooted until yesterday when I upgraded the Firmware to the Latest 4.30.617.12 and installed the RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.30.617.12 exe.
Now the phone has unrooted itself and got rid of TWRP, Software Status saying Official (Fabulous)
So yep, I am aware though that, that is a USA RUU that's why I wanted the European one, however that linked one above is an earlier version....so still not the latest but it might have OTA if its official...?

It is the latest build. The numbering always differs between the SKUs.
And RUUs overwrite every partition on your phone. That's why you lost root and TWRP and the phones status got reset to official by flashing the US RUU.
Sent from my HTC U12+ using XDA Labs

Flippy498 said:
It is the latest build. The numbering always differs between the SKUs.
And RUUs overwrite every partition on your phone. That's why you lost root and TWRP and the phones status got reset to official by flashing the US RUU.
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Thanks Flippy yep just rerooted now charging phone before I flash..

shivadow said:
Indeed there is for the wwe version (401) https://androidfilehost.com/?fid=817550096634758268
I have the file on my external sdcard for those moments where your phone thinks it's a toaster.
A lot will depend on whether your phone is locked to carrier or not. Carrier versions are hard to find.
Click to expand...
Click to collapse
Am I being stupid, I'm trying to flash this in TWRP, says file is corrupt....should I be adb sidelining it?

Please read the ReadMe thread. Being a *.zip archive doesn't equal being flashable via TWRP.
Sent from my HTC U12+ using XDA Labs

Flippy498 said:
Please read the ReadMe thread. Being a *.zip archive doesn't equal being flashable via TWRP.
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
It's not having it flippy, the zip file is corrupt. I've downloaded three times on three separate devices and I'm getting the same error.
More than that, I cannot actually extract the zip!

Flippy498 said:
Please read the ReadMe thread. Being a *.zip archive doesn't equal being flashable via TWRP.
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
And what I also need to do is downgrade my firmware or at least change it to the international version but I can't do that because I am getting a weird error....10 but bot the 10 mentioned in sneakyghosts firmware thread.
It's saying something about wrong device or hardware..
But I think that's just because I've got US firmware in it

As said before, read the ReadMe thread. You can't flash RUUs via TWRP and you can't unzip them the normal way since they're encrypted. All you're describing is expected behavior. The file is working fine. I've already used it several times.
And error 10 indicates that you didn't change your MID. A step by step guide for converting your phone can be found in the ReadMe thread, as well.
Sent from my HTC U12+ using XDA Labs

Flippy498 said:
As said before, read the ReadMe thread. You can't flash RUUs via TWRP and you can't unzip them the normal way since they're encrypted. All you're describing is expected behavior. The file is working fine. I've already used it several times.
And error 10 indicates that you didn't change your MID. A step by step guide for converting your phone can be found in the ReadMe thread, as well.
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Hi Yep Flippy, thanks 10 RU_MODELID_FAIL.
Yeah, I have to change my MID using fastboot oem writemid and I think I have to change it to 0PJA10000 but I'm not entirely sure. At the moment the MID is 0PJA11000 (Dev Edition) for whatever reason I think the International version is 0PJA10000.
Can you or anyone confirm this or tell me how to determine?
I cannot extract the Zip file to have a look!

Yes, that's the correct MID. It's mentioned in above the downloads in the RUU section of the ReadMe thread, as well.

Flippy498 said:
Yes, that's the correct MID. It's mentioned in above the downloads in the RUU section of the ReadMe thread, as well.
Click to expand...
Click to collapse
Thank you Flippy, I have never been so happy to see the words "English (United Kingdom)"
As a quick note HTC said this:
Good day,
Thank you for contacting HTC Email support department.
Sadly we do not have an end user RUU's, if you need a software reflash you can do that through our repair center, you can double check the phone shipping country by replying back with the imei number or serial number and we will be able to provide more accurate information.
lol

shivadow said:
Indeed there is for the wwe version (401) https://androidfilehost.com/?fid=817550096634758268
I have the file on my external sdcard for those moments where your phone thinks it's a toaster.
A lot will depend on whether your phone is locked to carrier or not. Carrier versions are hard to find.
Click to expand...
Click to collapse
Hey thanks Shivadow, without your lovely RUU, I would not have been able to complete my mission. I am aware that you went out of your way to find that link so my most sincere gratitude.