Database Info

One S new OTA update ?

Hi
Today i got a message that there is a new firmware ready for my ONE S.
It says it includes 4.0.4 and sense 4.1 plus wifi enhancements and ea games.
The wifi enhancements and ea games was also offered on a different update not too long ago.
Problem is that whenever i download and try to install it reboots and goes into CWM which stops with an error that it cannot find the file.
When i try to install the file manually from the download directory with the signature verification off (if on it fails at once) i get :
assert failed: check_cid(getprop("ro.cid"), "00000000", "11111111", "22222222", 3 4 5 6 7 etc ........
Error in sdcard/download/OTA_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5-2.21.401.10_release_275774cltf0sxl730g7fp1.zip
Status 7...
My phone is S-off via htcdev and rooted to be able to install adblocker and a few other things.
I have seen some sites and explanations for "status 7" but they are mostly linked to people flashing homemade roms, i am trying to flash a rom that supposedly is directly coming from HTC...
Anyone know what is wrong ?

1) You had to search how to proceed before asking...
2) You're not S-OFF...
3) You have to unroot, use stock recovery (and maybe relock bootloader, there are some discussions about it...) to apply an OTA.
4) You're not S-OFF, you'll be flamed for what you said...

Antubis said:
1) You had to search how to proceed before asking...
2) You're not S-OFF...
3) You have to unroot, use stock recovery (and maybe relock bootloader, there are some discussions about it...) to apply an OTA.
4) You're not S-OFF, you'll be flamed for what you said...
Click to expand...
Click to collapse
Ok, will there be a "modified stock" that i can flash without having to remove CWM and install stock recovery.

Antubis said:
1) You had to search how to proceed before asking...
2) You're not S-OFF...
3) You have to unroot, use stock recovery (and maybe relock bootloader, there are some discussions about it...) to apply an OTA.
4) You're not S-OFF, you'll be flamed for what you said...
Click to expand...
Click to collapse
could you give me link, where it describes, how to unroot and get stock recovery?

OP, you may need to change your CID first, there are threads and posts on this. Esp now with 2.31 out
And for FYI--some people did get s-off phones--not saying OP does--

rugmankc said:
OP, you may need to change your CID first, there are threads and posts on this. Esp now with 2.31 out
And for FYI--some people did get s-off phones--not saying OP does--
Click to expand...
Click to collapse
Stiflerlv said:
could you give me link, where it describes, how to unroot and get stock recovery?
Click to expand...
Click to collapse
I changed my CID, Re-Locked boot-loader and installed stock recovery. I'm on 2.21 my phone can't even find the ota so there must be other factors

That's why I never do OTA's, just wait for it in next rom like TD or Axiom etc

sharpinator said:
I changed my CID, Re-Locked boot-loader and installed stock recovery. I'm on 2.21 my phone can't even find the ota so there must be other factors
Click to expand...
Click to collapse
Your phone needs to be on 1.78 so you could get this 2.23 OTA. I am on 2.21 and don't have OTA either. We will need to wait for RUU file of 2.23

Why does my phone isn't updated ?

Hello!
I have a HTC One S. It's unlocked and completely unlinked from any carrier. I bought it like this and I never hacked the bootloader/installed custom ROM (not on this one ^^).
My software version is 2.21.401.10 and here's the OTA update : http://fotadl.htc.com/OTA_Ville_U_I....21.401.10_release_275774cltf0sxl730g7fp1.zip
But when I go in the software update menu and I check the updates, it says 'no update available'.
So my questions are :
1. Why?
2. Is there a way to install this OTA update manually (but keeping it an 'official' way) ?
Thanks!

jafar57 said:
Hello!
I have a HTC One S. It's unlocked and completely unlinked from any carrier. I bought it like this and I never hacked the bootloader/installed custom ROM (not on this one ^^).
My software version is 2.21.401.10 and here's the OTA update : http://fotadl.htc.com/OTA_Ville_U_I....21.401.10_release_275774cltf0sxl730g7fp1.zip
But when I go in the software update menu and I check the updates, it says 'no update available'.
So my questions are :
1. Why?
2. Is there a way to install this OTA update manually (but keeping it an 'official' way) ?
Thanks!
Click to expand...
Click to collapse
This OTA update is for phones with 1.78 version that is why it doesn't detect any updates.

Charkatak said:
This OTA update is for phones with 1.78 version that is why it doesn't detect any updates.
Click to expand...
Click to collapse
If you look at the URL correctly, you'll see that's the version to update from 2.21.401.10 and not from 1.78...
This one only weighs ~39Mo (against >150Mo for the other one)

The url is actually linking to is OTA_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5-2.21.401.10_release_275774cltf0sxl730g7fp1.zip which would be the OTA from 2.21.401.10 to 2.31.401.5 so I'm downloading it now to give it a try.
The problem is most likely that your CID doesn't match the ones that the update has been enabled for. You can use https://play.google.com/store/apps/details?id=org.tritonsoft.cidgetter to find it out. One of the threads listed the CIDs that people had success with. You can try downloading that file, renaming it to update.zip and booting into recovery to install it, but it will probably show an error because of your CID. In which case, you have to wait for the OTA to be pushed to your phone, or wait for an RUU to be available.

will1987 said:
The url is actually linking to is OTA_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5-2.21.401.10_release_275774cltf0sxl730g7fp1.zip which would be the OTA from 2.21.401.10 to 2.31.401.5 so I'm downloading it now to give it a try.
The problem is most likely that your CID doesn't match the ones that the update has been enabled for. You can use https://play.google.com/store/apps/details?id=org.tritonsoft.cidgetter to find it out. One of the threads listed the CIDs that people had success with. You can try downloading that file, renaming it to update.zip and booting into recovery to install it, but it will probably show an error because of your CID. In which case, you have to wait for the OTA to be pushed to your phone, or wait for an RUU to be available.
Click to expand...
Click to collapse
Thanks
My CID is HTC__203 but I didn't find the CIDs list.

jafar57 said:
Thanks
My CID is HTC__203 but I didn't find the CIDs list.
Click to expand...
Click to collapse
My cid is HTC__001 (which is one of the cid's in the zip) and I have placed the zip on the root of my sd card. When I boot into recovery nothing happens except it says something about sd not mounted.
How do I install this ota?
Running completely stock 2.21.401.10 from a RUU install.

I've 2.21 fw installed by RUU and bootloader locked. I try to install this update from recovery
(install update from external storage)
--Invalid Operation--
success rebooting by reasonem-00
CID 405
sorry for my bad english

jafar57 said:
Thanks
My CID is HTC__203 but I didn't find the CIDs list.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=30650526&postcount=6

Shouldn't super cid work I keep trying but won't install every time I choose apply update from external storage but it just errors and reboots
Sent from my HTC One S using xda premium

jafar57 said:
If you look at the URL correctly, you'll see that's the version to update from 2.21.401.10 and not from 1.78...
This one only weighs ~39Mo (against >150Mo for the other one)
Click to expand...
Click to collapse
I see what you mean, but when you open the zip file, there is txt, which indicates this: 1.78.401.2 CL58751 release-keys

Hey guys i have an S4 One S bought from Germany,shipped to Greece.I made the first OTA update from the 1st day and since then,my phone has this software number 1.77.111.5.My serial number is HT24WW405873.I have seen reports from people in my country, that they have got a notification for update to the newest 4.0.4 offered by HTC,but nothing on mine.Is it my serial number,or it is the software number(which is what i am most afraid of) fault?What to do to get updated if software number is the issue?

NickThess said:
Hey guys i have an S4 One S bought from Germany,shipped to Greece.I made the first OTA update from the 1st day and since then,my phone has this software number 1.77.111.5.My serial number is HT24WW405873.I have seen reports from people in my country, that they have got a notification for update to the newest 4.0.4 offered by HTC,but nothing on mine.Is it my serial number,or it is the software number(which is what i am most afraid of) fault?What to do to get updated if software number is the issue?
Click to expand...
Click to collapse
Is your phone locked to specific carriers or is it region free? As noted before the CID is important not the serial number. The CID identifies the device's locale. 1.77 is fairly old yes, my device is European (Netherlands) and it got an 1.78 update on the first day I got it. I only received 2.31 a few days ago so maybe best to just wait.

MattDN93 said:
Is your phone locked to specific carriers or is it region free? As noted before the CID is important not the serial number. The CID identifies the device's locale. 1.77 is fairly old yes, my device is European (Netherlands) and it got an 1.78 update on the first day I got it. I only received 2.31 a few days ago so maybe best to just wait.
Click to expand...
Click to collapse
I suppose it is locked to Deutsche Telekom or T-Mobile(dunno if they both exist in Germany),i get the purple T everytime i boot,before the "HTC one" screen.Its not written above the screen though.I downloaded the CID getter app and it says my CID is T-MOB101,but im confused that i dont get something similar to previous posters,like HTC_405 or HTC_203 ... Oh well,i will wait cos i don't wanna root etc. yet.

Successful flash OTA 2.31 on 2.21 RUU Europe
First make a backup of image/everything! i can not guarantee it will install with every CID on this planet. !!!OWN RISK!!!
I Just flashed the OTA 2.31 on RUU Europe 2.21.401.10. with CID HTC__E11 Netherlands.
You need an Unlocked and Rooted phone for this!
1. Change your CID to HTC__Y13 so that the OTA get triggered! (just do not install it yet! later!)
2. If you got SuperSu installed enable Survival mode!
3. Change your default CID Back and flash stock recovery! No ReLock needed! (you can update the phone now!)
[Important! default cid seems to be needed because of language files after the update i only got 4 languages DE/EN/FR/NL before arround 20?]
4. Reflash ClockWorkMod recovery.
5. After update install CWM-SuperSU-v0.95.zip with help of ClockWorkMod to regain root and turn off Survival mode later when booted!
Chainfire for SuperSU: http://forum.xda-developers.com/showthread.php?t=1538053
Wiki - [Tutorial]CID http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
- [Tutorial]Root, Unlock, Recovery http://forum.xda-developers.com/showthread.php?t=1583427
After this post i'm allowed to post in other categories, so i can make a tutorial if you guys want? with pictures etc...

CarstenDutch said:
First make a backup of image/everything! i can not guarantee it will install with every CID on this planet. !!!OWN RISK!!!
I Just flashed the OTA 2.31 on RUU Europe 2.21.401.10. with CID HTC__E11 Netherlands.
You need an Unlocked and Rooted phone for this!
1. Change your CID to HTC__Y13 so that the OTA get triggered! (just do not install it yet! later!)
2. If you got SuperSu installed enable Survival mode!
3. Change your default CID Back and flash stock recovery! No ReLock needed! (you can update the phone now!)
[Important! default cid seems to be needed because of language files after the update i only got 4 languages DE/EN/FR/NL before arround 20?]
4. Reflash ClockWorkMod recovery.
5. After update install CWM-SuperSU-v0.95.zip with help of ClockWorkMod to regain root and turn off Survival mode later when booted!
Chainfire for SuperSU: http://forum.xda-developers.com/showthread.php?t=1538053
Wiki - [Tutorial]CID http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
- [Tutorial]Root, Unlock, Recovery http://forum.xda-developers.com/showthread.php?t=1583427
After this post i'm allowed to post in other categories, so i can make a tutorial if you guys want? with pictures etc...
Click to expand...
Click to collapse
NickThess, Agrees this would be the only way to get that right...although CarstenDutch why did you flash the RUU as the OTA came out in Holland a few days ago?

MattDN93 said:
NickThess, Agrees this would be the only way to get that right...although CarstenDutch why did you flash the RUU as the OTA came out in Holland a few days ago?
Click to expand...
Click to collapse
If you are on 2.21 the OTA doesn't work. I am on 2.21 via the RUU and do not get any update.

Charkatak said:
I see what you mean, but when you open the zip file, there is txt, which indicates this: 1.78.401.2 CL58751 release-keys
Click to expand...
Click to collapse
No, the version.txt says "2.21.401.10 CL81535 release-keys"

CarstenDutch said:
First make a backup of image/everything! i can not guarantee it will install with every CID on this planet. !!!OWN RISK!!!
I Just flashed the OTA 2.31 on RUU Europe 2.21.401.10. with CID HTC__E11 Netherlands.
You need an Unlocked and Rooted phone for this!
1. Change your CID to HTC__Y13 so that the OTA get triggered! (just do not install it yet! later!)
2. If you got SuperSu installed enable Survival mode!
3. Change your default CID Back and flash stock recovery! No ReLock needed! (you can update the phone now!)
[Important! default cid seems to be needed because of language files after the update i only got 4 languages DE/EN/FR/NL before arround 20?]
4. Reflash ClockWorkMod recovery.
5. After update install CWM-SuperSU-v0.95.zip with help of ClockWorkMod to regain root and turn off Survival mode later when booted!
Chainfire for SuperSU: http://forum.xda-developers.com/showthread.php?t=1538053
Wiki - [Tutorial]CID http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
- [Tutorial]Root, Unlock, Recovery http://forum.xda-developers.com/showthread.php?t=1583427
After this post i'm allowed to post in other categories, so i can make a tutorial if you guys want? with pictures etc...
Click to expand...
Click to collapse
Some questions:
* My One S is rooted, but has the stock recovery. Do I need another recovery first? (edit: probably yes, because now it isnt unlocked?)
* I have SuperSU, but what do you mean with Survival method? Im from Belgium (Flandres), so I dont need more then the 4 languages you've got.
Thx for the advice!

MattDN93 said:
NickThess, Agrees this would be the only way to get that right...although CarstenDutch why did you flash the RUU as the OTA came out in Holland a few days ago?
Click to expand...
Click to collapse
I updated the 2.21 ota at the moment it was available for 1.78 with CID 11111111 because I couldn't wait! not so long ago, I am just a tweaker.
Ps. I installed the 2.21 ota over 1.78
and later on downloaded the 2.21 RUU to get a clean system after messing around with system files etc...
Tapatalk/Swiftkey
---------- Post added at 05:29 PM ---------- Previous post was at 05:00 PM ----------
superiscch said:
Some questions:
* My One S is rooted, but has the stock recovery. Do I need another recovery first? (edit: probably yes, because now it isnt unlocked?)
* I have SuperSU, but what do you mean with Survival method? Im from Belgium (Flandres), so I dont need more then the 4 languages you've got.
Thx for the advice!
Click to expand...
Click to collapse
*You can't be rooted with original recovery. Follow this, Unlock bootloader>Flash custom recovery>Flash SuperSu
*Survival mode means that it trys to stay rooted after ota update, after ota I need to flash the SuperSu.zip again to get permission rights to get it working again. So I guess it's not working really.
What CID are you on? Look for CID Getter on play store.
If you are not familiar with modifying just wait for official ota's or RUU (there is no huge/shocking improvement with 2.31 over 2.21. just a little smoother.
Tapatalk/Swiftkey

CarstenDutch said:
First make a backup of image/everything! i can not guarantee it will install with every CID on this planet. !!!OWN RISK!!!
I Just flashed the OTA 2.31 on RUU Europe 2.21.401.10. with CID HTC__E11 Netherlands.
You need an Unlocked and Rooted phone for this!
1. Change your CID to HTC__Y13 so that the OTA get triggered! (just do not install it yet! later!)
2. If you got SuperSu installed enable Survival mode!
3. Change your default CID Back and flash stock recovery! No ReLock needed! (you can update the phone now!)
[Important! default cid seems to be needed because of language files after the update i only got 4 languages DE/EN/FR/NL before arround 20?]
4. Reflash ClockWorkMod recovery.
5. After update install CWM-SuperSU-v0.95.zip with help of ClockWorkMod to regain root and turn off Survival mode later when booted!
Chainfire for SuperSU: http://forum.xda-developers.com/showthread.php?t=1538053
Wiki - [Tutorial]CID http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
- [Tutorial]Root, Unlock, Recovery http://forum.xda-developers.com/showthread.php?t=1583427
After this post i'm allowed to post in other categories, so i can make a tutorial if you guys want? with pictures etc...
Click to expand...
Click to collapse
The following was my Situation: 2.21.401.10 stock, unlocked stock recovery, rooted, Super CID (1111111). There were no update available. Even Downloading the above linked update, renaming it to update.zip and placing it on root of the sd, booting to recovery was no solution (got red triangle with exclamation in the recovery).
Changed my CID to HTC__001 which should work. (in the File I downloaded there is a list of CIDs which are allowed, HTC__001 is included). Rebooted to recovery tried to apply the update.zip. Again there was the red triangle with exclamation mark.
Now I changed my CID to the one mentioned from you HTC__Y13 and rebooted. And it works indeed. Now I was able to download the Software Update. Since I'm from Switzerland I didn't bother to change the CID again. So I choos to apply the Software-Update. But again ended in the recovery with the red triangle and exclamation mark.
EDIT: The stock recovery boots and there is a green bar below which fills quickly to approximately 1/4 then stopps and shows me a red triangle with exclamation mark.
any help is appreciated. thx in advance

[Q] TWRP 2.3.3.0 or lower not responding on XL

Anyone expert can advise a noob like me Recently got a One XL from a local telco in Singapore and I have the bootloader unlocked via htcdev.com.
However problem comes after I flash the latest TWRP 2.3.3.0; When I boot into TWRP recovery; the phone is not responding to any touch screen selection; thus I'm able to perform any anything such as "Backup" or whatever. Also the only way for me to get out of the recovery is to press and hold the power button.
I even tried an older version of the TWRP and it is still the same problem. Anyone can advise did I made any mistake ?
Here is my current bootloader status.
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.09.29
OpenDSP-v31.1.0.45.0015
eMMC-boot
Nov 26 2012, 18:37:14:9908
Current Software Info:
Android 4.1.1
Software number: 3.17.707.1

i have the same problem im looking for a fix but no luck

htcdaniel1 said:
i have the same problem im looking for a fix but no luck
Click to expand...
Click to collapse
I have the same...its because of the new hboot 2.14.....I have even tried downgrading with JET but unsuccessful.....CWM works but then any rom you flash will not respond to touch gesture.....they must have really locked this down....need the new RUU to get this back

I doubt it is a deliberate attempt at stopping custom things and more a side effect of some change to how the touchscreen works. With any luck the change was to improve something
Also it might be hboot but a whole bunch of firmware is changed beyond hboot with updates. You would need a good understanding of how the phone works before you could say if it is hboot or other related.

try running "fastboot erase cache"

Try installing goo mgr . It uses twrp and loads it directly from os
Sent from my HTC One XL using xda premium

Contact twrp developer I'm sure it's an easy fix for him to accommodate f9r you Telstra people

Im in the same boat.
Just bought this phone 2nd hand for some AOSP action and ive got as far as recovery to install a rom and no touch screen.
Someone above said that they used CWM which was an idea i had, but then the roms they flashed had no working touch screen!
Is it possible the firmware has actually changed the way the touchscreen works and therefore all roms/recoveries will no longer work?
It sounds like an H-boot downgrade may be the only way back. Someone here tried JET to downgrade and was unsuccessful.
Im starting to think there may be no way back, if something doesnt turn up soon i might just have to resell it on which is a real pity...
Any update on this?

hagenuk said:
Anyone expert can advise a noob like me Recently got a One XL from a local telco in Singapore and I have the bootloader unlocked via htcdev.com.
However problem comes after I flash the latest TWRP 2.3.3.0 When I boot into TWRP recovery; the phone is not responding to any touch screen selection; thus I'm able to perform any anything such as "Backup" or whatever. Also the only way for me to get out of the recovery is to press and hold the power button.
I even tried an older version of the TWRP and it is still the same problem. Anyone can advise did I made any mistake ?
Here is my current bootloader status.
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.09.29
OpenDSP-v31.1.0.45.0015
eMMC-boot
Nov 26 2012, 18:37:14:9908
Current Software Info:
Android 4.1.1
Software number: 3.17.707.1
Click to expand...
Click to collapse
up up up up up up

This is a known issue after updating by OTA to firmware 3.17 and hboot 2.14. Something in the OTA breaks TWRP.
You can use adb to run TWRP commands. The recovery works, its just the touchscreen that is not responsive within TWRP. Aside from that, you are pretty much stuck waiting for the devs to update TWRP to make it work. Might help to contact the devs, as demand from more users may prompt a quicker response.
I would not recommend CWM as a stopgap fix. CWM is known to cause some major issues on this device. And as a previous response indicates, doesn't really help in this case either.

j626914269 said:
up up up up up up
Click to expand...
Click to collapse
Dont do that, it is a well known issue.
A new update is available to support touch in twrp, but the next problem is no touch in ROM's. You have been warned!
http://forum.xda-developers.com/showthread.php?t=1677447

Danthemanz said:
Is it possible the firmware has actually changed the way the touchscreen works and therefore all roms/recoveries will no longer work?
Click to expand...
Click to collapse
Its not the firmware itself, as TWRP still works just fine with the stock rooted 3.17 ROMs posted in Development. And firmware itself shouldn't affect recovery. But it was something that deployed with the OTA, such as hboot, that broke TWRP.

I have the same problem. I cannot use TWRP and have also been unsuccessful in trying to get the OTA_EVITA_UL_JB_45_S_Telstra_WWE_3.17.841.2_0.23a.32.09.29_10.128.32.34a_release_2997538hizl4svcm80o4g1.zip properly flashed.
I was able to flash the firmware.zip component, but when I try to do the whole .zip through fastboot I get a signature error.
Can someone point me to a guide as to how to extract a flashable zip from the OTA that I can flash with the locked bootloader and fastboot? I think that the problem is that the system partition has not been flashed.
Thankx in anticipation

redpoint73 said:
Its not the firmware itself, as TWRP still works just fine with the stock rooted 3.17 ROMs posted in Development. And firmware itself shouldn't affect recovery. But it was something that deployed with the OTA, such as hboot, that broke TWRP.
Click to expand...
Click to collapse
It is almost certainly a change in the firmware itself, twrp 2.3.3.1 works because the kernel was updated to the kernel that 3.17 uses. The newer kernel supports the change in the firmware.
---------- Post added at 11:20 PM ---------- Previous post was at 11:18 PM ----------
fezzawinkle said:
I have the same problem. I cannot use TWRP and have also been unsuccessful in trying to get the OTA_EVITA_UL_JB_45_S_Telstra_WWE_3.17.841.2_0.23a.32.09.29_10.128.32.34a_release_2997538hizl4svcm80o4g1.zip properly flashed.
Click to expand...
Click to collapse
You cant just flash OTA from fastboot afaik.
You can download already prepared 3.17 ROM's here:
http://forum.xda-developers.com/showthread.php?t=2076361
http://forum.xda-developers.com/showthread.php?t=2055490
http://forum.xda-developers.com/showthread.php?t=2066023

twistedddx said:
Dont do that, it is a well known issue.
A new update is available to support touch in twrp, but the next problem is no touch in ROM's. You have been warned!
http://forum.xda-developers.com/showthread.php?t=1677447
Click to expand...
Click to collapse
Hi, i can't find the link to v2.3.3.1 Can you tell me where you found it?
Edit: found it - http://forum.xda-developers.com/showthread.php?t=1677447&page=43

[Q] *** Security Warning *** [solved]

hi guys
i have installed some old RUU and it stalled on me, so i'm stuck in bootloader with this.
*** Security Warning ***
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-38.03.02.11_M
eMMC-boot
What should i do?
BTW i have no goldcard and no way to create one since i can't get to adb (or at least i think so...)
Thanks in advance

I have three questions first:
1. Have you been previously htc dev unlocked
2..has RUU procedure ended successfuly,
or it's stopped with some error
3...why there in not adb access anymore
Name the symptoms
Edit: you hboot is unlockable by revolutionary ( s- off )
Which RUU exactly have you been attempting to install
Is your device branded by any carrier ( branded software or simlock)

tnx for quick reply
1. Yes, i was relocked
2. No, it ended with error
3. I'm stuck in bootloader, i have only fastboot access
edit:
- revolutionary stalls at "waiting for device", maybe it needs adb connection... or i'm doing something wrong...
- RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed
- not branded by carrier or simlocked...

nenad_l said:
tnx for quick reply
1. Yes, i was relocked
2. No, it ended with error
3. I'm stuck in bootloader, i have only fastboot access
Click to expand...
Click to collapse
If you're still keen on stock
You best check first whether your device is branded
if not, flash WWE version
Your hboot is one of those that might be s-offed by revolutionary
so, maybe,
it'd be a pity to upgrade it by RUU
Flashing RUU ended up in error because you cannot flash just about anything,
certainly not lower version on top of higher..
Ok, i'd suggest trying to s- off it
or find RUU version =/or < that your phone was shipped with
Was this error- you were having <131> by any chance?

ERROR [140]: BOOTLOADER VERSION ERROR
I'm not sure which RUU is the right one for my device... I have installed this same RUU long time ago when i wanted to downgrade my hboot.
I have intended to go full stock for a while... maybe sell my phone or something...

nenad_l said:
ERROR [140]: BOOTLOADER VERSION ERROR
I'm not sure which RUU is the right one for my device... I have installed this same RUU long time ago when i wanted to downgrade my hboot.
I have intended to go full stock for a while... maybe sell my phone or something...
Click to expand...
Click to collapse
If you wish to pass your device to other hands:
Either find some other higher version like
2.10.401.8,...
or even one of those with < 1 > at the beginning but higher than
one you're trying to flash at the moment,,
Or, go to:
http://forum.xda-developers.com/showthread.php?t=2143855
and ask there- it is help dedicated thread
You may find this interesting to read:
http://forum.xda-developers.com/showthread.php?p=31130746

i hoped to install this RUU, and then allow my device to OTA automatically...

nenad_l said:
i hoped to install this RUU, and then allow my device to OTA automatically...
Click to expand...
Click to collapse
The lattest OTA you'll be able to receive would be:
2.10.401.8... or 9 i do not remember...
You can grab ics 4.0.4 from htcdev site as well- as it has been
released as dev preview only ( no ota )-and flash it( that one probably should go fine)

yep, quietly brilliant greeted me with that famous and annoying sound but it also came as relief...
i have downloaded RUU_SAGA_ICS_35_S_HTC_Europe_14.01.401.2_Radio_20.76.30.0835_3831.19.00.110_release_275068_signed from http://www.htcdev.com/devcenter/downloads and it installed with no problems...
Thank you, asgardr

Cannot run Nougat RUU: Error 132 (signature error)

For some reason I am unable to install the ROM via RUU OR OTA update (manual or auto). I am getting a Error 132 (signature error). I am S-ON and RELOCKED.
Things I have already done/tried:
Made sure I have the correct RUU (it's the only one available as far as I know and it is for the HTC unlocked US variant).
Made sure my device is RELOCKED and stock recovery installed.
Tried multiple methods - including RUU (tried inside of the OS as well as in download mode/bootloader mode); OTA tried to flash manually inside of stock recovery, tried to download OTA (no update found), tried to flash firmware and OTA in custom recovery as well stock recovery.
Searched the forums relentlessly for answers to the 132 signature error. There doesn't seem to be a consensus answer.
Of note: My 'Software Status' is flagged as "MODIFIED," I'm wondering if that is preventing me from updating the HBOOT via RUU.
Please let me know if you can think of any solutions because I am stumped, and I'm sure the community could use a more definitive answer about the 132 Error as it seems to have been mention several times over the course of quite a few years.
Thanks guys

BrandonBaskin said:
For some reason I am unable to install the ROM via RUU OR OTA update (manual or auto). I am getting a Error 132 (signature error). I am S-ON and RELOCKED.
Things I have already done/tried:
Made sure I have the correct RUU (it's the only one available as far as I know and it is for the HTC unlocked US variant).
Made sure my device is RELOCKED and stock recovery installed.
Tried multiple methods - including RUU (tried inside of the OS as well as in download mode/bootloader mode); OTA tried to flash manually inside of stock recovery, tried to download OTA (no update found), tried to flash firmware and OTA in custom recovery as well stock recovery.
Searched the forums relentlessly for answers to the 132 signature error. There doesn't seem to be a consensus answer.
Of note: My 'Software Status' is flagged as "MODIFIED," I'm wondering if that is preventing me from updating the HBOOT via RUU.
Please let me know if you can think of any solutions because I am stumped, and I'm sure the community could use a more definitive answer about the 132 Error as it seems to have been mention several times over the course of quite a few years.
Thanks guys
Click to expand...
Click to collapse
You need to be S-OFF for flash the Firmware and the 2.18 will not run if you dont have flashed the firmware. If you have an Unlocked USA you need tu run the 1.57 (the last one before 7.0), the status will be OFFICIAL and you can just update whit OTA in setting, information, update like a normal device or flash ota in the recovery stock, but you steel need 1.57.617.60 version and OFFICIAL status.

salvy' said:
You need to be S-OFF for flash the Firmware and the 2.18 will not run if you dont have flashed the firmware. If you have an Unlocked USA you need tu run the 1.57 (the last one before 7.0), the status will be OFFICIAL and you can just update whit OTA in setting, information, update like a normal device or flash ota in the recovery stock, but you steel need 1.57.617.60 version and OFFICIAL status.
Click to expand...
Click to collapse
Hi, thanks for your response. I have run the latest RUU multiple times but it has failed to reset the software status to 'OFFICIAL.' I have even rolled back to the previous RUU, downloaded and installed the OTA for 1.57.617.60 and that too failed to reset the software status to official. Getting S-OFF for me is not currently an option so I'm wondering if there is a practicable alternative.
Thanks again

BrandonBaskin said:
Hi, thanks for your response. I have run the latest RUU multiple times but it has failed to reset the software status to 'OFFICIAL.' I have even rolled back to the previous RUU, downloaded and installed the OTA for 1.57.617.60 and that too failed to reset the software status to official. Getting S-OFF for me is not currently an option so I'm wondering if there is a practicable alternative.
Thanks again
Click to expand...
Click to collapse
Take the ota.zip file and try to install it via the stock recovery, and see what errors you get. That is how I figured out what was wrong with mine ( wrong CID)

MGfusion said:
Take the ota.zip file and try to install it via the stock recovery, and see what errors you get. That is how I figured out what was wrong with mine ( wrong CID)
Click to expand...
Click to collapse
OK. Attempted to flash OTA in recovery and it appeared to be successful, however after rebooting out of recovery there was no OS loaded. Do you know of any way to reset the software status to official - because running the RUU(s) for the current base doesn't seem to work.
Thanks

BrandonBaskin said:
OK. Attempted to flash OTA in recovery and it appeared to be successful, however after rebooting out of recovery there was no OS loaded. Do you know of any way to reset the software status to official - because running the RUU(s) for the current base doesn't seem to work.
Thanks
Click to expand...
Click to collapse
Flash 1.57 ota, and relock boot loader if unlocked. Unlocked boot loader might be what is making the software status say modified

MGfusion said:
Flash 1.57 ota, and relock boot loader if unlocked. Unlocked boot loader might be what is making the software status say modified
Click to expand...
Click to collapse
Bootloader status is: "RELOCKED"
1.57.617.60 RUU is installed
Software Status is still: "MODIFIED"
Could it be that there is no way of resetting this status while S-ON?

BrandonBaskin said:
Bootloader status is: "RELOCKED"
1.57.617.60 RUU is installed
Software Status is still: "MODIFIED"
Could it be that there is no way of resetting this status while S-ON?
Click to expand...
Click to collapse
I'm not sure, I don't understand what could still be "modified"

MGfusion said:
I'm not sure, I don't understand what could still be "modified"
Click to expand...
Click to collapse
I don't either. This is extremely frustrating just to get an update. If I've run the proper RUU I'm not sure how HTC doesn't make sure that it resets the software status.
At any rate, I will keep digging around the forums because I think this Error [132] deserves a proper solution.

BrandonBaskin said:
I don't either. This is extremely frustrating just to get an update. If I've run the proper RUU I'm not sure how HTC doesn't make sure that it resets the software status.
At any rate, I will keep digging around the forums because I think this Error [132] deserves a proper solution.
Click to expand...
Click to collapse
Try installing this zip file with the stock recovery and relocked bootloader. This is how I upgraded to nougat, no problem
https://drive.google.com/file/d/0B53pV_Dn96x1aDJZU2l5MWdmeFk/view
(This is the extracted ota zip file)

MGfusion said:
Try installing this zip file with the stock recovery and relocked bootloader. This is how I upgraded to nougat, no problem
https://drive.google.com/file/d/0B53pV_Dn96x1aDJZU2l5MWdmeFk/view
(This is the extracted ota zip file)
Click to expand...
Click to collapse
Thanks! I will try again with this file. Just curious... do you remember if you "Software Status" was 'MODIFIED'? And are you S-OFF?

BrandonBaskin said:
Thanks! I will try again with this file. Just curious... do you remember if you "Software Status" was 'MODIFIED'? And are you S-OFF?
Click to expand...
Click to collapse
Can't remember if it said modified or not, but I am definitely s-off.

MGfusion said:
Can't remember if it said modified or not, but I am definitely s-off.
Click to expand...
Click to collapse
It may literally be no way to update it with S-ON. It's cool because Sunshine is an option when I get a some extra cash but this seems to be a bit of a programming flaw on HTC's part.

BrandonBaskin said:
I don't either. This is extremely frustrating just to get an update. If I've run the proper RUU I'm not sure how HTC doesn't make sure that it resets the software status.
At any rate, I will keep digging around the forums because I think this Error [132] deserves a proper solution.
Click to expand...
Click to collapse
Try installing the OTA, then flashing ruu. Thats how I did I it.

BrandonBaskin said:
It may literally be no way to update it with S-ON. It's cool because Sunshine is an option when I get a some extra cash but this seems to be a bit of a programming flaw on HTC's part.
Click to expand...
Click to collapse
Oh, you are s-on? I would definitely try sunshine and then install ota or ruu then

The_scam said:
Try installing the OTA, then flashing ruin. Thats how I did I it.
Click to expand...
Click to collapse
Hey, thanks for the response. What is Ruin?

I've got S-OFF, Software Status: Official, Relocked boot loader, CID: BS_US001, Current ROM: 1.57.617.60
I've been getting the same "Error 132: Signature Error" when trying to flash the 2.18.617.1 RUU.
Attempted to flash the most recent RUU I had (1.57.617.41), which was successful. Attempted the 2.18.617.1 RUU again, same issue.
Tried changing the CID to 11111111 and tried flashing the RUU, still getting Error 132.
Tried pushing the 2.18.617.1 OTA via ADB Sideload and got "assert failed: check_cid("00000000", etc...)" error
Changed CID back to BS_US001 and started pushing the OTA updates (1.57.617.52, 1.57.617.60, 2.18.617.1) one by one via ADB Sideload
All of the OTA installs were successful.
Now, only getting the white screen with the HTC logo.
Ran 2.18.617.1 RUU again, ran fine this time.
Still only getting the white screen with the HTC logo.
Not terribly excited about the direction this is going...

kommoncents said:
I've got S-OFF, Software Status: Official, Relocked boot loader, CID: BS_US001, Current ROM: 1.57.617.60
I've been getting the same "Error 132: Signature Error" when trying to flash the 2.18.617.1 RUU.
Attempted to flash the most recent RUU I had (1.57.617.41), which was successful. Attempted the 2.18.617.1 RUU again, same issue.
Tried changing the CID to 11111111 and tried flashing the RUU, still getting Error 132.
Tried pushing the 2.18.617.1 OTA via ADB Sideload and got "assert failed: check_cid("00000000", etc...)" error
Changed CID back to BS_US001 and started pushing the OTA updates (1.57.617.52, 1.57.617.60, 2.18.617.1) one by one via ADB Sideload
All of the OTA installs were successful.
Now, only getting the white screen with the HTC logo.
Ran 2.18.617.1 RUU again, ran fine this time.
Still only getting the white screen with the HTC logo.
Not terribly excited about the direction this is going...
Click to expand...
Click to collapse
download the zip file I had given a link to above and try installing it with the stock system recovery

BrandonBaskin said:
Hey, thanks for the response. What is Ruin?
Click to expand...
Click to collapse
Lol sorry, meant to type ruu. Using my phone and autocorrect ?
---------- Post added at 01:46 PM ---------- Previous post was at 01:43 PM ----------
MGfusion said:
download the zip file I had given a link to above and try installing it with the stock system recovery
Click to expand...
Click to collapse
Try installing the TWRP, look around at the system files. Is anything there? You might have to wipe everything and try the ruu again.
Maybe try rebooting into "fastboot OEM rebootRUU" then once that loads, type "fastboot flash <name of your ruu.zip>" from your computer

The_scam said:
Lol sorry, meant to type ruu. Using my phone and autocorrect
---------- Post added at 01:46 PM ---------- Previous post was at 01:43 PM ----------
Try installing the TWRP, look around at the system files. Is anything there? You might have to wipe everything and try the ruu again.
Maybe try rebooting into "fastboot OEM rebootRUU" then once that loads, type "fastboot flash <name of your ruu.zip>" from your computer
Click to expand...
Click to collapse
lol ohh! ok...I thought it was something like Odin haha
so just so I'm clear:
Flash OTA (in Recovery)?
Then immediately start the RUU?