Pretty new to this but I've deceided to upgrade my desire s to ics. I unlocked to bootloader via the instructions on the HTC dev site(did i need to do that). Went ok but when i tried to update to the wwe ics ruu it failed, came back 'ICS RUU security fail - update fail' error message 155- the blurb saying it could be the wrong rom or it's too big. I've definitely got the right rom. Don't understand. Anyone got any ideas? My phone is locked to the o2 network.
Many thanks. PS it recovered ok.
Search here, then if you can't find you answer post again there, you'll get better responses.
Apologies didn't realise this was in the desire and not desire s forum. posted in a rush. I've solved it now.... it seems htc stock roms can only be installed if the bootloader is locked. I relocked it and it was fine.
I bought a new HTC one M9 smart phone,
Software Number: 1.10.706.2
Android Version: 5.0.2
I tried to update the software directly from the phone, but it said that no updates available
I switched to
htc .com/us/support/htc-one-m9/news/
and I downloaded the latest RUU from HTC official site in order to update the phone's software
I followed the instructions under "Manual system update instructions" in the above mentioned link, but when the RUU starts the update progress, the ERROR 132: SIGNATURE ERROR pops up and the process is aborted.
How can I fix this error to complete the software update process?
mohammad_7 said:
I bought a new HTC one M9 smart phone,
Software Number: 1.10.706.2
Android Version: 5.0.2
I tried to update the software directly from the phone, but it said that no updates available
I switched to
htc .com/us/support/htc-one-m9/news/
and I downloaded the latest RUU from HTC official site in order to update the phone's software
I followed the instructions under "Manual system update instructions" in the above mentioned link, but when the RUU starts the update progress, the ERROR 132: SIGNATURE ERROR pops up and the process is aborted.
How can I fix this error to complete the software update process?
Click to expand...
Click to collapse
did you able to fix? i am getting it with my tmobile variant
Signature errors usually mean you need to download it again due to the file somehow becoming corrupt.
Beamed in by telepathy.
The lowest publicly available firmware for the M9 was 1.32.x and I haven't seen the SKU 706 in connection with the M9, before. Therefore, I'm not sure whether the OP actually owns a M9...
And aside from what got written by shivadow that error occurs if you try to update a M9 via RUU from firmware 3.x to firmware 4.x. As explained in the ReadMe thread the encryption keys of the older firmware versions aren't compatible with the newer ones.
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
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
Hi,
I'm totally new to this and I'm looking for help.
I have a HTC One (M9), unlocked. I realised since I got the handset (insurance replacement in 2016) I've never had an OTA update. I contacted HTC support who advised that I am running unofficial software and that is why I cannot get OTA updates. I've asked them to elaborate on what is "unofficial" about it as I have never rooted the handset or messed around in any way. They couldn't elaborate and advised I should send it to them to be flashed (at cost, as it's out of warranty).
Anyway, I want to put my handset into a condition where I can receive OTA updates & also ensure that I benefit from the latest software updates so I started looking into how I could do this. As a noob to Android the easiest method seemed to be via RUU exe. I've downloaded 2 different RUU's from HTC website but both errored with "incorrect version" when I tried to install. I then downloaded a ZIP which I followed the instructions to boot to recovery & install from phone storage, this also errored with "cannot find files".
As above I've tried going from Android v5 to v7 and that failed, I don't know whether I had the wrong RUU or I need to upgrade to v6 first.
I'm in the UK with I presume a UK handset but the RUUs were downloaded from htc.com not htc.com/uk as the UK one doesn't seem to provide this.
So long story short I'm looking for help getting the correct RUU for my handset and I'm having no luck. I'd appreciate any advice given.
HTC One M9
CID: HTC_001 (WWE)
Android: 5.0.2
HTC Sense: 7.0
SW: 1.32.401.17
S-ON
Cheers
Breezo
Firmware 1.32.401.17 only got distributed in one single country (I always forget which one it was - it definitely wasn't the UK). Therefore, the combination of that version together with the HTC__001 CID can only get achieved by tinkering with the phone.
You're actually using an official stock rom but you can't update your phone since the UK never was meant to receive this specific version and/or its OTAs.
You should be able to "return" to 1.32.401.15 without much hassle by following one of the guides in the ReadMe thread. Even with S-ON this little downgrade should be possible (c.f. the RUU section of the ReadMe thread).
If flashing the 1.32.401.15 RUU fails you'll have no choice but unlocking the bootloader, getting root, setting the phone S-OFF and retrying to flash the RUU. All needed steps are explained in the ReadMe thread, as well.
Sent from my HTC One M9 using XDA Labs
Hi Flippy498,
Thanks very much for the response and advise.
I've no idea how it ended up like that. I can only assume as it was an insurance replacement that it was initially branded then flashed incorrectly before it was issued to me.
I'll try your suggestions over the weekend.
Thanks again for the knowledge, its appreciated.
Cheers
Breezo
Hi Flippy498,
That worked perfectly thanks very much for your help. Took the software down from .17 to .15 and OTA updates kicked in immediately.
Now running on Android 7.0
Cheers again
Breezo
Flippy498 said:
Firmware 1.32.401.17 only got distributed in one single country (I always forget which one it was - it definitely wasn't the UK). Therefore, the combination of that version together with the HTC__001 CID can only get achieved by tinkering with the phone.
You're actually using an official stock rom but you can't update your phone since the UK never was meant to receive this specific version and/or its OTAs.
You should be able to "return" to 1.32.401.15 without much hassle by following one of the guides in the ReadMe thread. Even with S-ON this little downgrade should be possible (c.f. the RUU section of the ReadMe thread).
If flashing the 1.32.401.15 RUU fails you'll have no choice but unlocking the bootloader, getting root, setting the phone S-OFF and retrying to flash the RUU. All needed steps are explained in the ReadMe thread, as well.
Click to expand...
Click to collapse
Deffo not a UK phone. We went from 5.0.1 out of the box straight to 6.0.
I'm pretty sure that UK received Android 5.1, as well. No variant of the M9 skipped firmware 2.x.
Firmware 1.x = Android 5.0.2
Firmware 2.x = Android 5.1
Firmware 3.x = Android 6.0
Firmware 4.x = Android 7.0
Since the UK M9 is the "normal" European unbranded version (SKU 401) it received the following versions:
1.32.401.8
1.32.401.15
1.40.401.8
2.10.401.1
2.10.401.180*
3.35.401.12
3.35.401.32
4.14.401.7
4.28.401.3
In addition to that there are:
1.32.401.6 (a pre-release firmware shown on the MWC)
1.32.401.17 (which got distributed in only one country)
* Normally the three numbers behind the last dot indicate a beta firmware. Since the Nougat update couldn't be applied in one single update they had to distribute this version, as well.
Sent from my HTC One M9 using XDA Labs