Hello guys, I'm unable to update my m9 with an ruu from android 5.1 to android 7. I keep getting an error message during the ruu setup; error 132 signature error. My phone was S-off by default.
it is htc hima uhl with radio version 01.04_U11440601_71.02.50709G_F. Flashed 3 diff ruu's and I get the same error..please help me friends. Just bought it yesterday.
I even have supercid and should be able to flash all compatible roms right? I dont know why I keep getting the error.
Please read the ReadMe thread. Especially the RUU section.
II have been reading through but still facing the same problem. Can you perhaps guide me a little? I will really owe you one bro. Thanks
You can't use 4.x RUUs on any non-4.x firmware. That's why you're facing the signature error. And the reason why the SuperCID isn't helping you at all is described in the RUU section, as well.
Sent from my HTC One M9 using XDA Labs
Just finished reading. Thanks bro. Answer this last question and i wont bother you again. I will have no problems flashing 3x RUUs on my 2x platform right?
Correct
Sent from my HTC One M9 using XDA Labs
Thanks again
Related
How do I unroot, restore default ROM, restore default hboot and go back to S-ON. Basically 100% stock since I need to send my phone back to the provider due to hardware issues. Many thanks.
Sent from my HTC Desire using Tapatalk
Download and run the latest ruu. Check the Desire Index thread.
Sent from CM7
Actually, you need to download the latest RUU for YOUR Desire. Did you make a note of it before flashing a new ROM?
You can find everything in this thread
http://forum.xda-developers.com/showthread.php?t=696189
so flashing the ruu restores default hboot and S-ON?
Yes it does
EddyOS said:
Actually, you need to download the latest RUU for YOUR Desire. Did you make a note of it before flashing a new ROM?
Click to expand...
Click to collapse
What do you mean. I haven't taken note of anything
Sent from my HTC Desire using Tapatalk
He means the RUU specific for your carrier and handset, im guessing this would be the 3 UK one based on your avatars.
Oh thanks! Its actually vodafone handset with 3 UK similar card. Thanks folks
Sent from my HTC Desire using Tapatalk
correct RUU link needed for H3G UK three mobile
Hi
I will be grateful if you could give me the correct link for three mobile uk H3GUK for latest RUU, AS I had .93 bootloader and not sure about SLCD/AMOLED, was using miui rom 1.4.B1 and clockwork mode recovery 3.0.0.0 and radio rom 32.44 something.
I will be more than happy n thankful if someone could help me to get latest RUU for H3G UK.
when i tried to flash other RUU's it says , completed n phone is ready to use now, but screen is just black n do not work
I flashed
RUU_Bravo_H3G_UK_1.22.771.1_Radio_32.36.00.28U_4.06.00.02_2_release_127568_signed and
and
RUU_Bravo_HTC_WWE_1.21.405.2_T2_Radio_32.41.00.32U_4.08.00.09_release_137222_signed
from
www.shippedroms.com
Please help me
Cheers
Raj
There isn't a new 3 UK RUU available so you're stuck
correct RUU link needed for H3G UK three mobile
Hi
Thanks for ur reply
can u suggest any RUU, which u think will work on my phone
thanks
Any can work, but you won't be able to send it back to HTC without it being the original
EddyOS said:
Any can work, but you won't be able to send it back to HTC without it being the original
Click to expand...
Click to collapse
Hi
When I tried H3G uk its saying ur phone ready to use but screen not working when i tried WWE(world wide english), it stated the customer id prob, install correct RUU.
You need a gold card for a non-3 UK RUU - sounds ike you have an SLCD screen and flashed an AMOLED RUU, hence the black screen
Out of interest, if you run available 3uk ruu and check for updates, won't it update it for you? Mine was 3uk before root and custom ROM, so might need this info at some point. Thanks
Sent from my HTC Desire using XDA App
tinky1 said:
Out of interest, if you run available 3uk ruu and check for updates, won't it update it for you? Mine was 3uk before root and custom ROM, so might need this info at some point. Thanks
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
That seems logical - I will be interested in this answer also!
Yes, but if you can't see what you're doing it'll be hard to do it
I see what you mean lol. In old Nokia days we used to change language to Chinese on the friend phones. After having it done to me a few time I could change it back with my eyes closed. LOL
Sent from my HTC Desire using XDA App
http://www.mobileunderground.info/showthread.php?t=24294
17th from bottom to top
RUU_Bravo_Froyo_H3G_UK_2.25.771.1_Radio_32.48.00.3 2U_5.11.05.14_release_149217_signed.exe
http://www.multiupload.com/J230M5J8UD
Eddy, is that a correct one?
Hi, im a new htc one m9 user. I have htc one m9 with software 2.10.111.6. Is there any update yet? I saw file update on flippy498, downloading 2.10.111.180, put on sdcard and rename it to 0PJAIMG.zip, but failed to flash it, even in fastboot too. Is there any clue? Thanks alot for any help ?
Anyone? Please?
What company is your phone ? to ? You can go to the HTC website and download the OFFICAL Ruu from there and run Marshmallow on your ?
Sent from my HTC One M9 using XDA-Developers mobile app
I think its unlocked, but the cid is tmob101 x.xx.111.x software. I cant find marshmallow RUU in htcdev site, only OTA zip file which i dont know why i cant flash it. Strange isnt it. My phone is locked bootloader and S-on btw..any clue ? Thanks for replying
http://www.htc.com/us/support/rom-downloads.html
Sent from my HTC One M9 using XDA-Developers mobile app
Im already there, but cant find marshmallow 3.35.111.14 RUU because thats my phone supossed RUU. My software number right now is 2.10.111.6 btw, still in 5.1.
Thanks for replying
Unlock your bootloader
Okay, i'll try it. I'll post if any progress.
Thanks for replying
Okay, marshmallow update just come in this afternoon. Thanks in advance for everyone that replying.
Cheers
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, I have a stock HTC T-Mobile M9 5.1 on 2.7.531.6.
For months I have tried updating this thing via OTA (No Updates Available) and through the manual update to Nougat 4.30.617.12. For some reason I keep getting error error [132]: Signarure error. What am I doing wrong??????? Can someone help me please!?
UPDATE: I have sucessfully updated from 2.7.531.6 Android Lollipop to 3.39.531.41. Now that I'm trying to update from 3.39.531.41 to 4.27.531.6 I still get the same [132] error.
How did you update from 2.7 to 3.39? I can't get it pass 2.7 and having exactly the same error 132, even with the misspelled word (Signarure) in there (I can't believe HTC allows software with misspelled texts come out to public)
Please read the ReadMe thread. It explains why you can't flash 4.x RUUs on non-4.x firmwares.
That's not the only typo in HTC software. If you manually flash RUUs via fastboot/HTC_fastboot you'll get asked to "flush" the RUU immediately, again, and not to "flash" it. But let's be honest, the majority of HTC users doesn't even know what a RUU is. Therefore, I can understand quite well why HTC doesn't bother correcting those mistakes. The RUUs are working nonetheless...
Sent from my HTC One M9 using XDA Labs
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