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.
Related
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.
Hi all,
Just took the 3.35.401.32 update and now I'd like to grab the stock recovery and RUU for the same version (3.35.401.32). I've checked the usual suspects but they don't seem to have the files, so are they available for download or I have to hold off a little longer until they are?
Cheers all.
I'm pretty sure that the recovery is already available here on xda. However even if it wasn't you could have grabbed it by yourself while creating a backup for that firmware version (and providing it for others afterwards ). There's a guide how to do so in my google sheet. (And that is linked in my signature.)
Unless it's made for a US carrier, every RUU is leaked and not provided by HTC officially. That means that no one knows if or when a RUU for a new firmware version gets available. (E.g. the SKU 708 has only one single RUU for one of the 1.x firmware versions.) Therefore you shouldn't waste your time and wait too long for a RUU but look for other methods that can get you back to stock.
Edit: And here's the link to the recoveries that have been contributed so far.
Sent from my HTC One S using XDA Labs
Thanks for the info Flippy.
Flippy498 said:
I'm pretty sure that the recovery is already available here on xda. However even if it wasn't you could have grabbed it by yourself while creating a backup for that firmware version (and providing it for others afterwards ). There's a guide how to do so in my google sheet. (And that is linked in my signature.)
Unless it's made for a US carrier, every RUU is leaked and not provided by HTC officially. That means that no one knows if or when a RUU for a new firmware version gets available. (E.g. the SKU 708 has only one single RUU for one of the 1.x firmware versions.) Therefore you shouldn't waste your time and wait too long for a RUU but look for other methods that can get you back to stock.
Edit: And here's the link to the recoveries that have been contributed so far.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
i extracted the file name before updating my device but have no idea about the correct address to be added before
/OTA_HIMA_UHL_M60_SENSE70_MR_HTC_Europe_3.35.401.32-3.35.401.12_release_4872506s7i993jqhhc4rv7.zip
maemow said:
i extracted the file name before updating my device but have no idea about the correct address to be added before
/OTA_HIMA_UHL_M60_SENSE70_MR_HTC_Europe_3.35.401.32-3.35.401.12_release_4872506s7i993jqhhc4rv7.zip
Click to expand...
Click to collapse
That's the OTA not a RUU. Both, recovery and OTA, are already available in my thread.
Sent from my HTC One M9 using XDA Labs
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?
i was triying to update mi at&t m9 to the nougat official rom using the Ruu fromj htc web page, first i updated to 3.38.502.41 as the at&t update page says, and then i tried the nougat Ruu, but i keep getting the "error 132: signature error". any idea why this happens?
PS: my device its S-on, carrier unlocked(cant download OTA) and not rooted.
XsaucerX said:
i was triying to update mi at&t m9 to the nougat official rom using the Ruu fromj htc web page, first i updated to 3.38.502.41 as the at&t update page says, and then i tried the nougat Ruu, but i keep getting the "error 132: signature error". any idea why this happens?
PS: my device its S-on, carrier unlocked(cant download OTA) and not rooted.
Click to expand...
Click to collapse
Read this topic - https://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
And post #5!
Golv said:
Read this topic - https://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
And post #5!
Click to expand...
Click to collapse
Does that means that i can't flash the nougat Ruu? Im s-on and i cant get OTA updates. Maybe using the SD card method.
PS: thanks for the reply.
Sent from my HTC One (M9) using XDA Labs
XsaucerX said:
Does that means that i can't flash the nougat Ruu? Im s-on and i cant get OTA updates. Maybe using the SD card method.
PS: thanks for the reply.
Sent from my HTC One (M9) using XDA Labs
Click to expand...
Click to collapse
You can flash Nougat RUU but you need flash FULL stock signed Nougat firmware for your CID before (all data will be deleted). Then you can flash Nougat RUU for your CID using the SD card method.
Golv said:
You can flash Nougat RUU but you need flash FULL stock Nougat firmware for your CID before (all data will be deleted). Then you can flash Nougat RUU for your CID using the SD card method.
Click to expand...
Click to collapse
Thats the problem i cant flash the stock nougat Ruu
Sent from my HTC One (M9) using XDA Labs
XsaucerX said:
Thats the problem i cant flash the stock nougat Ruu
Sent from my HTC One (M9) using XDA Labs
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=64299817&postcount=5
It seems like HTC changed its encryption keys between firmware 3.x and 4.x. Therefore, you cant flash 4.x RUUs if your phone is currently using a 3.x firmware. You either need to flash a NoWipe/Full-Wipe Firmware Pack beforehand (only possible with S-OFF) or you need to use a 3.x RUU for the same SKU and install the 4.x OTA, afterwards.
Already installed the 3.38.502.41(the prerequisite to get the nougat OTA) but i cant get the OTA, my phone its the at&t m9 but carrier unlocked and s-on
Sent from my HTC One (M9) using XDA Labs
XsaucerX said:
Already installed the 3.38.502.41(the prerequisite to get the nougat OTA) but i cant get the OTA, my phone its the at&t m9 but carrier unlocked and s-on
Sent from my HTC One (M9) using XDA Labs
Click to expand...
Click to collapse
Ever find a solution to this? I have a similar situation.
tiger1999 said:
Ever find a solution to this? I have a similar situation.
Click to expand...
Click to collapse
I'm still waiting for the OTA update to come, asked about this in the readme thread and one of the mods told me that i don't need an at&t service to get the update, just wait.
Ps: you can't update using the Ruu because of the new encryption, have to use the OTA.
Sent from my HTC One (M9) using XDA Labs
Please don't forget that mods are just humans and therefore not all knowing. We make mistakes, too.
I made a further research and it looks like I was wrong. AT&T actually seems to request users to have one of their sim cards inserted if you want their OTAs. Sorry for the bad news. This was the first time that I read about that. (And I thought European carriers would be an annoyance...)
Theoretically, you should be able to install the OTA manually if someone uploads it somewhere or posts HTC's download link. However, it looks like no one uploaded the file or published the official link, yet.
Flippy498 said:
Please don't forget that mods are just humans and therefore not all knowing. We make mistakes, too.
I made a further research and it looks like I was wrong. AT&T actually seems to request users to have one of their sim cards inserted if you want their OTAs. Sorry for the bad news. This was the first time that I read about that. (And I thought European carriers would be an annoyance...)
Theoretically, you should be able to install the OTA manually if someone uploads it somewhere or posts HTC's download link. However, it looks like no one uploaded the file or published the official link, yet.
Click to expand...
Click to collapse
Dont worry about it man, thanks for trying to help! I'll just wait 1-2 weeks and get a go phone sim card from amazon, its just like 2-5 bucks anyways.
Does anyone have OTA backup?
Please could someone upload OTA update? (3.38.502.41 to 4.27.502.7)
XsaucerX said:
I'll just wait 1-2 weeks and get a go phone sim card from amazon, its just like 2-5 bucks anyways.
Click to expand...
Click to collapse
Hi! So did it work for you? You received this OTA with att sim card?
Hi guys.
I'm having the same error (132) signature error.
My device:
UNLOCKED
htc_himaulatt PVT S-OFF
CID: 11111111
LK-1.0.0.0000
RADIO-01.01_U11440792_97.00.51203G_F
OpnDSP-15.6.1.00522.8994_1026
os-3.35.617.31
NO OTA Updates.
Now running 3.35.617.31 trying to update with RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.14.617.6.exe or any other 4.XX.XXX.X
RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.exe was applied with no problem but when trying to apply the 4.14.617.6 error (132) shows.
I have downloaded all updates and try to apply:
4.14.617.6
4.23.617.1
4.30.617.2
4.30.617.12
None of the RUUs works, shows error (132)
All RUUs was downloaded from htc / us / support / rom-downloads
Can someone give me some hints on how solve this issue???
Thanks in advance.
mollon said:
Hi guys.
I'm having the same error (132) signature error.
My device:
UNLOCKED
htc_himaulatt PVT S-OFF
CID: 11111111
LK-1.0.0.0000
RADIO-01.01_U11440792_97.00.51203G_F
OpnDSP-15.6.1.00522.8994_1026
os-3.35.617.31
NO OTA Updates.
Now running 3.35.617.31 trying to update with RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.14.617.6.exe or any other 4.XX.XXX.X
RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.exe was applied with no problem but when trying to apply the 4.14.617.6 error (132) shows.
I have downloaded all updates and try to apply:
4.14.617.6
4.23.617.1
4.30.617.2
4.30.617.12
None of the RUUs works, shows error (132)
All RUUs was downloaded from htc / us / support / rom-downloads
Can someone give me some hints on how solve this issue???
Thanks in advance.
Click to expand...
Click to collapse
What is your M.I.D number?
S-OFF users should be aware that the phone's CID and MID need to correspond to the SKU of the RUU you want to flash. The SCID (11111111) won't make your phone ignore mismatches between those ID numbers as it did on older HTC devices
Pfaffinator said:
What is your M.I.D number?
S-OFF users should be aware that the phone's CID and MID need to correspond to the SKU of the RUU you want to flash. The SCID (11111111) won't make your phone ignore mismatches between those ID numbers as it did on older HTC devices
Click to expand...
Click to collapse
Thanks Pfaffinator.
Actually I was able to solve the issue changing the CID to BS_US001 and then applying the OTA update using stock recovery, after that I was able to use the latest RUU.exe with latest HTC SW release.
Thanks for your kind support!!!
Pfaffinator said:
S-OFF users should be aware that the phone's CID and MID need to correspond to the SKU of the RUU you want to flash. The SCID (11111111) won't make your phone ignore mismatches between those ID numbers as it did on older HTC devices
Click to expand...
Click to collapse
The MID is irrelevant in this situation. As already explained in this thread (c.f. the first page) and my ReadMe thread you can't flash 4.x RUUs while your phone is using firmware 3.x or lower. The encryption keys got changed.
And the SCID not only "lost" the ability to make the phone ignore MID mismatches it additionally prevents the M9 from being able to receive OTAs.
A general request to everyone who needs help with his/her M9: Please read the ReadMe thread. There's a reason why it's pinned above the normal threads in the General and the Q&A section. 99% of all questions are already answered there. Reading the first two pages of that thread takes less time than creating a new thread and waiting for someone to respond.
?
Flippy498 said:
The MID is irrelevant in this situation. As already explained in this thread (c.f. the first page) and my ReadMe thread you can't flash 4.x RUUs while your phone is using firmware 3.x or lower. The encryption keys got changed.
And the SCID not only "lost" the ability to make the phone ignore MID mismatches it additionally prevents the M9 from being able to receive OTAs.
A general request to everyone who needs help with his/her M9: Please read the ReadMe thread. There's a reason why it's pinned above the normal threads in the General and the Q&A section. 99% of all questions are already answered there. Reading the first two pages of that thread takes less time than creating a new thread and waiting for someone to respond.
Click to expand...
Click to collapse
That paragraph is from your thread.
Yeah, I know. Nonetheless, the MID isn't the problem in this case. It's the SCID preventing the OTA download (as explained in the OTA section of the ReadMe thread) and the encryption keys of the RUUs being different between firmware 3.x and 4.x (resulting in error 132 as described on page 1 in this thread, the RUU and the RUU error section in the ReadMe thread).
Sent from my HTC One M9 using XDA Labs
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