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
Related
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
Hey there,
I own a HTC One M9 with Stock ROM, not rooted, nothing modified. Recently I got the Nougat OTA update as a notification (don't know why not earlier...).
It did update without any problems, but after it, it occured to me that it didn't get any signal. WiFi, bluetooth and everything else works fine, it even recognizes my SIM card.
In the settings, the "flight mode" is grey and permanently "setting off" and I can't set it on or off.
(But strangely, if I hold the power button, it says "airplane mode off", same within the status bar/quick settings.)
I don't know much about flashing etc (nearliy nothing), but I read as most threads which seemed to be similar as I could. Even if some people had the problem with the One X and M8, I couldn't find a solution for me...
I rebootet the phone several times, did the "battery pull out simulation" with power and volume keys, did a factory reset in the settings, wiped cache partition within the recovery mode. Even tried booting in safe mode and a factory reset within the recovery mode.
Nothing works, the airplane mode is still stuck at "setting off" and I don't get any cell phone signal or mobile internet.
Phone /software information:
- Model: HTC One M9; OPJA100
- Not rooted
- "LOCKED"
- htc_hiauhl PVT S-ON
- Software status: Official
- Android-Version: 7.0
- Software-Version: 4.18.111.2
- OpenDSP-20.7.3.00545.8994_1012
- Kernel-Version: 3.10.84-perf-ga97f624
[email protected] #1
SP PREEMPT
- Android safety-patch: 01. Nov. 2016
-Baseband-Version: 01.01_U114401011_117.00.61117G_2_F
- Build-Nr.: 4.18.111.2 CL839204 release-keys
I hope, that it will be fixed, if I flash the Stock ROM myself, but I didn't find one with the same software-version and do not know how to do this.
Any suggestions, what could be wrong and how I manage to fix it?
Thank you all for your help!
Flashing instrtructions can be found in the ReadMe thread. The catch is that no one contributed a RUU or a TWRP backup for your current firmware version, yet.
Therefore, I only see the following solutions at the moment (which all aren't available for free - sorry):
Getting S-OFF and flashing the 3.x RUU for your SKU. (Infos are located in the ReadMe thread.)
Contacting Llabtoofer's RUU service. (A link can be found in the further reading section of the ReadMe thread.)
Searching on sites like ir-file or easy-firmware for the needed RUU. (If you choose this option you'll need your phone's codename which is HIMA_UHL.)
I was able to unlock the Bootloader, flashed TWRP, got S-OFF (didn't get Root, but I don't know why...tried several SuperSU versions...) and changed the CID to be able to flash RUUs without the T-Mobile branding.
But I'm not sure which RUU I can use for flashing with a SD card.
Those I found were only 3.xx with SKU "111", but the actual version is 4.xx.
I thought with S-OFF I would be able to flash early every RUU?
Can someone explain this to me and give me an advice which RUU (preferably a non-branded Nougat one) I can flash and where to get it?
Thank you all in advance for you help!
As written in my last post, no one contributed 4.x files for your SKU, yet.
All needed information and files should be available in the ReadMe thread. There's a conversion guide, the RUU section contains all infos you might need in regard to RUUs and the further reading section contains a link to a spreadsheet with with all SKUs and their meanings.
Sent from my HTC One M9 using XDA Labs
Thanks again!
I did read those threads, but got a bit confused afterwards... :/
E .g. easy-firmware has a RUU 4.xxx with SKU "111", and as I understood, I can also use free 4.xxx RUUs with SKU "401", because I got S-OFF and changed the CID?
Sorry to bother
That's correct. You can use 401 RUUs thanks to S-OFF, now.
The catch with ir-file and easy-firmware is that their files aren't available for free. Most RUUs in the ReadMe thread got bought on one of those sites in the past.
Since you already paid for S-OFF I'd suggest you to not pay once more. Either convert to SKU 401 or use the infos in the RUU section of the ReadMe thread for flashing the 3.x RUU for your current SKU.
Sent from my HTC One M9 using XDA Labs
Now I got it, thank you!
I tried flashing it with a RUU_4.28.401.3 (worked on the second try, first one didn't find the file).
Flashing worked without problems (checked the phone info), but it's still stuck in the flight mode.
No changes there... :crying:
Is there a chance, that it's still a software issue, maybe with Nougat itself?
Or do I have to "bury" it, because sending to be repaired isn't worth it's value?
If it was a general Nougat problem on the M9 then there would be more threads like this one... Sorry, that I can't provide better news.
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
Where can I find a firmware update for hima and how do I update it??? Trying to upgrade to nougat.
Donnie267 said:
Where can I find a firmware update for hima and how do I update it??? Trying to upgrade to nougat.
Click to expand...
Click to collapse
Hi, all the needed information and related download links you can find it here going to Post #6 and then at RUU Section.
Marko Indaco said:
Hi, all the needed information and related download links you can find it here going to Post #6 and then at RUU Section.
Click to expand...
Click to collapse
I've tried using ruu. Keep getting error 132. Tried it in bootloader, download and recovery.
Please search for the key word "encryption key" in that post or read the post with the common RUU errors.
Sent from my HTC One M9 using XDA Labs
Thanks guys. Any chance y'all know if the firmware can be flashed with TWRP?
RUUs can't get flashed via TWRP. However, there are several flashing methods explained in the RUU section.
Sent from my HTC One M9 using XDA Labs
What about firmware? Those can be flashed with twrp, right?
Not really. TWRP doesn't have access to the partitions that would be needed to be overwritten. TWRP only has access to the system, the recovery partition and the boot partition. You might want to read the article that is linked as "the difference between rom and firmware" in the further reading section.
Once I have the firmware extracted, could I use adb to flash the firmware?
No, since ADB only works if the phone is booted to modes in which it won't accept the firmware files (the system or the recovery mode).
Why don't you keep things simple and use an OTA?
Sent from my HTC One M9 using XDA Labs
Ota keeps giving me an error saying my phone has been modified and ruu keeps giving me error 132 in both download and bootloader modes.
As written before, that error 132 occurs due to the new encryption keys.
You need to flash the RUU for your current firmware or to restore an "untouched" TWRP backup of that version and then you can take the OTA.
Sent from my HTC One M9 using XDA Labs
How am I supposed to ruu when it keeps giving me errors?
The newer 4.x RUU uses different encryption keys than your phone. You need to flash the RUU for your current firmware.
Sent from my HTC One M9 using XDA Labs
I know that. I keep asking for the ruu for my firmware but jeep getting the runaround instead of what I'm asking for.
That's what I'm running. Which ruu do I need?
Donnie267 said:
I know that. I keep asking for the ruu for my firmware but jeep getting the runaround
Click to expand...
Click to collapse
Really? Then, maybe you have to read rules FIRST instead of getting the runaround. And then read as well the ReadMe Thread (as already warned you).
Donnie267 said:
instead of what I'm asking for
Click to expand...
Click to collapse
Did I understand wrong or this seems like an order?
I've read the Readme a dozen times. Replied to the Readme asking questions. Nobody can give me a straight answer. How hard is it to tell me which file I need so I don't have to download every single file in the forum soft bricking my phone over and over again? All I'm asking is which file I need given my firmware. Which I've posted screenshots of.
help!
Okay,before any of you start. Yes I've read the forum Readme. Yes, I've read the rules. I've asked this question at least a dozen times on multiple threads and absolutely nobody can give me a straight answer telling me to read the readme/rules. And it's really getting frustrating. So here's my question one more time. How do I update my phone to nougat? Yes I've tried ruu in both download mode AND in bootloader mode AND in recovery mode in all 3 modes, I get error 132. Yes, I tried Ota update through phone settings and keep getting an error saying the my phone has been modified. Here are screenshots of my software info.
Donnie267 said:
I keep asking for the ruu for my firmware[...]
Click to expand...
Click to collapse
And in which of your posts did you mention your current firmware? You didn't even mention which version of the phone you own before 01:03 (MET), today. The fact that you get errors while trying to install OTAs gets mentioned the first time at 23:06 (MET), yesterday. We don't own crystal balls. How are we suposed to know these things?
Donnie267 said:
I've read the Readme a dozen times. Replied to the Readme asking questions.
Click to expand...
Click to collapse
You obviously didn't read a single guide in the RUU section. They all start with the same step:
Boot to download mode and look at the line with "OS" at the beginning for finding out your current firmware version.
The "firmware version" in "settings>about>software information>more" is only the base of the (custom) rom you are running and might therefore differ from the real one in the download mode.
Remember that you can always flash newer RUUs as long as they use the same encryption key as your current firmware. (c.f. the important notes in this post)
Click to expand...
Click to collapse
And a little bit further below in the same post:
Download Links:
Click to expand...
Click to collapse
Donnie267 said:
Nobody can give me a straight answer. How hard is it to tell me which file I need so I don't have to download every single file in the forum soft bricking my phone over and over again?
Click to expand...
Click to collapse
I already explained at the beginning of this post why you didn't get straighter answers. How hard is it to read what got written on the first pages of the ReadMe thread? (And it's not the first time that you completely ignore opening posts of a thread.)
Hello Guys!
My M9 has custom rom viperone and the phone is S-OFF i want to return to stock rom Can i while S is OFF ?
I can't find the 7.0 stock rom for my phone and i'm with Sasktel.
Hope you guys help me with that.
Thanks.
Taken from the ReadMe thread:
Flippy498 said:
Rom Update Utilities (RUUs) are *.exe or *.zip files with which you can reflash the stock system and the whole firmware of your phone quite easily.
Strictly speaking only the *.exe files are RUUs (which are nothing more than a *.zip file combined with a fancy installer and HTC_Fastboot files). However, people got used to call them both RUUs and since most of the files here are *.zip files I don't want to start nitpicking.
[*]The catch is that HTC only provides RUU.exe files for their US customers. All other RUUs which you can find in this post got leaked somehow and no one knows if or when new non-US RUUs are going to be available. That's why it might happen that non-US users can't find a publicly available RUU they could use with their phone.
Click to expand...
Click to collapse
Flippy498 said:
Q19: I couldn't find a RUU or a TWRP backup in this thread that are flashable on my phone. What shall I do now?
A: You have two choices (none of them is for free). If you choose the second one you could help the community a lot by re-uploading the RUU on AFH.
Use Llabtoofer's RUU Service
Try to find a suitable RUU on websites that leak them (e.g. easy-firmware)
Click to expand...
Click to collapse
In Canadian, flippy means "yes you can". S-off and unlocked bootloader makes no difference. Just flash a stock firmware of the exact same version (see "software version" in settings - software information) that you have now and accept the ota updates as they arrive. If you cannot find a firmware of the same version you are SOL.
There is 2 methods to flash stock firmware. I prefer the external sdcard method (.zip) but you can do it from pc with an RUU program (.exe) via USB.
As stated in the first post the problem is actually that the OP couldn't find a RUU they could use. I just explained why that is the case by quoting the ReadMe thread and highlighting the important parts in red.
And there are more than two methods for flashing a RUU. ?
Sent from my HTC One M9 using XDA Labs