Database Info

Signature verify fail

I need help. I am trying to revert back to stock but when I run RUU for my HTC One S T-Mobile USA it stops every time when trying to verify the signature. I locked my bootloader and tried unlocking it and the same thing happened when verifying my signature it said it failed. I don't know what to do please help me.

Did you flash a signed stock recovery before locking the bootloader?

reverting from a higher firmware version to lower is not possible until the s-off is achieved for htc s

touch of jobo said:
Did you flash a signed stock recovery before locking the bootloader?
Click to expand...
Click to collapse
im not quite sure I'm using a trickdroid rom. Is there anyway that i can still do that?

In order to run a RUU, your must have a signed stock recovery [ <-- Edit: That may not be true, according to post below this one. ] and a locked bootloader. However, in order to flash a recovery, you must have an unlocked bootloader.
So if you are locked but still have a custom recovery, you have to unlock again so that you can flash a stock recovery. Then lock and RUU.
Also, like mughalgxt said, you can not run a RUU with an oler hboot than you have now.

touch of jobo said:
In order to run a RUU, your must have a signed stock recovery and a locked bootloader. However, in order to flash a recovery, you must have an unlocked bootloader.
So if you are locked but still have a custom recovery, you have to unlock again so that you can flash a stock recovery. Then lock and RUU.
Also, like mughalgxt said, you can not run a RUU with an oler hboot than you have now.
Click to expand...
Click to collapse
Just relocking the bootloader is sufficient to enable an RUU install. The RUU will re-install the stock recovery (wether you want it or not)

bobsie41 said:
Just relocking the bootloader is sufficient to enable an RUU install. The RUU will re-install the stock recovery (wether you want it or not)
Click to expand...
Click to collapse
But I have tried to update with a re locked bootloader and every time it fails at the signature verification

touch of jobo said:
In order to run a RUU, your must have a signed stock recovery [ <-- Edit: That may not be true, according to post below this one. ] and a locked bootloader. However, in order to flash a recovery, you must have an unlocked bootloader.
So if you are locked but still have a custom recovery, you have to unlock again so that you can flash a stock recovery. Then lock and RUU.
Also, like mughalgxt said, you can not run a RUU with an oler hboot than you have now.
Click to expand...
Click to collapse
I've tried to unlock the bootloader again but it says something is wrong with signature I don't know what it is though

milkshakes said:
I've tried to unlock the bootloader again but it says something is wrong with signature I don't know what it is though
Click to expand...
Click to collapse
Having the same problem. Was able to RELOCK but still won't flash RUU. Would really appreciate any help. Almost as much as I now appreciate a removable SD card.

i have this same problem, orginal bootloader etc boot loader relock and still nothing always finish with error checksum failed
FAILED (remote: 12 signature verify fail)
Click to expand...
Click to collapse
Any other solution
CID to H3G__001
version-baseband 1.11.50.05.28
version bootloader 2.13.0000
Regards

Chances are you're using the wrong RUU. Google one specific to Three UK.
Sent from my HTC One S using xda premium

kylepont said:
Chances are you're using the wrong RUU. Google one specific to Three UK.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
now i have error 155 it look like wrong bootloader or recovery
i change couple times recovery and boot (taken from OTA update) and still nothing
this two firmware i try :
RUU_Ville_U_H3G_UK_1.78.771.5_Radio_0.16.31501S.19_2_10.23.31501S.10L_release_258982_signed
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed
Regards

blackangel82 said:
version-baseband 1.11.50.05.28
version bootloader 2.13.0000
Click to expand...
Click to collapse
blackangel82 said:
this two firmware i try :
RUU_Ville_U_H3G_UK_1.78.771.5_Radio_0.16.31501S.19_2_10.23.31501S.10L_release_258982_signed
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed
Click to expand...
Click to collapse
Those RUUs are too old for you. (You can't run a RUU with an older hboot than you have.) If I remember correctly, 1.53.xx comes with hboot-1.06 and the 1.78.xx RUU has hboot-1.13
and you have hboot-2.13. If you are S-Off, you can flash an older stock hboot.
-Jobo

Having same problem. I flashed my recovery back to stock ICS recovery and relocked the bootloader. In hboot however, I still have TAMPERED at the top. Every time I try to flash back to stock RUU it fails with the message "FAILED (remote: 12 signature verify fail)". I've got a Bell Mobility One S and I'm using the BM RUU.

stoked said:
Having same problem. I flashed my recovery back to stock ICS recovery and relocked the bootloader. In hboot however, I still have TAMPERED at the top. Every time I try to flash back to stock RUU it fails with the message "FAILED (remote: 12 signature verify fail)". I've got a Bell Mobility One S and I'm using the BM RUU.
Click to expand...
Click to collapse
Use the Link in my signature.

khan.orak said:
Use the Link in my signature.
Click to expand...
Click to collapse
Thanks. I actually got my phone upgraded by reflashing the stock recovery, locking the bootloader and then running the ota update. Still not sure why I still have a tampered message in the hboot though.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

[Guide] [UPDATED07.04.2013] unbranding HTC ONE S S4

UNBRAND HTC ONE S THE RIGHT WAY​
I am not responsible for anything that goes wrong which messes up your device !
Things needed
1. HTC ONE S S4 variant
2. Common Sense and patience
Steps :-
1.Relock your bootloader using "fastboot oem lock"
2. RUU your device , for RUU files use this http://www.androidfiles.org/ruu/?dir=Ville
3. Unlock your bootloader via htcdev.com
4. Flash TWRP recovery by "fastboot flash recovery TWRPS4.img "
5. Flash any custom rom you want like viperones or trickdroid or cm anyone your preference
S-off your device using facepalm s-off http://forum.xda-developers.com/showthread.php?t=2155135
Once you have s-off issue this command to change your cid WWE EUROPE
"fastboot oem writecid HTC__001"
issue "fastboot reboot-bootloader"
then use "fastboot getvar all" to check if your and cid have changed to HTC__001
Download this Jellybean RUU and flash it , its already edited , so no mid problem
To flash it
Fastboot oem rebootRUU
Fastboot flash zip JB316_WWE_ville_decrypt_rom.zip
http://dl.dropbox.com/u/55211431/JB316_WWE_ville_decrypt_rom.zip (credits jamus28) go hit his thanks button
Feel free to ask any question here:good:

What is the point of locking the phone and then unlocking it again to S-Off? Why not just S-Off then lock the bootloader and then run the JB RUU.

Re: [Guide] unbranding HTC ONE S S4
To let the phone be fully stable on stock firmware
Sent from my HTC One S using xda app-developers app

aditya. said:
To let the phone be fully stable on stock firmware
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Waste of time as long as the rom is working you only need to S-Off and then flash the RUU. I know it been updated but at the time I had to use a RUU to get my phone working again and went to S-Off and couldn't in till I flashed Viper2.

Re: [Guide] unbranding HTC ONE S S4
I had a bad time soffing my device 3 days ! Brick jtag repair etc but now I can deal with s off ing any one s
Sent from my HTC One S using xda app-developers app

i was able to change cid but i keep getting error when changing model id, please help!

cyriantherockstar said:
i was able to change cid but i keep getting error when changing model id, please help!
Click to expand...
Click to collapse
try flashing Jellybean RUU directly without changing MID ! it will work ! Sorry that command is Invalid you can proceed anyway dont worry mybad

Re: [Guide] unbranding HTC ONE S S4
Any recommendations to get rid of the silver metallic "T-Mobile" branding above the screen?
Regards,
Opentang

Re: [Guide] unbranding HTC ONE S S4
Opentang said:
Any recommendations to get rid of the silver metallic "T-Mobile" branding above the screen?
Regards,
Opentang
Click to expand...
Click to collapse
Change your LCD screen ! It will cost around 120$ ! Or look for a dead HTC one s on eBay take off Its LCD ...
Sent from my HTC One S using xda app-developers app

aditya. said:
UNBRAND HTC ONE S THE RIGHT WAY​
I am not responsible for anything that goes wrong which messes up your device !
Things needed
1. HTC ONE S S4 variant
2. Common Sense and patience
Steps :-
1.Relock your bootloader using "fastboot oem lock"
2. RUU your device , for RUU files use this http://www.androidfiles.org/ruu/?dir=Ville
3. Unlock your bootloader via htcdev.com
4. Flash TWRP recovery by "fastboot flash recovery TWRPS4.img "
5. Flash Superuser to root your device !
S-off your device using facepalm s-off http://forum.xda-developers.com/showthread.php?t=2155135
Once you have s-off these two commands to change your cid and mid to WWE EUROPE
"fastboot oem writecid HTC__001"
issue "fastboot reboot-bootloader"
then use "fastboot getvar all" to check if your and cid have changed to HTC__001
Then flash JELLYBEAN RUU - http://www.shipped-roms.com/download.php?category=android&model=Ville&file=RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
You are unbranded !
Feel free to ask any question here:good:
Click to expand...
Click to collapse
hmmm....i didnt know that the htc one s got s-off (been busy with work lately).....i tried debranding before , using a method that doesnt involve s-off, i was able to change the CID but i could never install the RUU cause of the different MID.....is the different MID not a problem anymore ? also will you be able to get OTA updates after you debrand and flash stock Jelly Bean ROM

tried installing the JB RUU over my stock 2.31 ICS, but i get an unknown error ..im s-off already and changed cid to HTC__001, and i get the system notification for the JB OTA..is it safe to just install the OTA? coz i've read in another thread that some devices got bricked by installing the OTA (although they are using supercid when they upgraded..

anand_s said:
hmmm....i didnt know that the htc one s got s-off (been busy with work lately).....i tried debranding before , using a method that doesnt involve s-off, i was able to change the CID but i could never install the RUU cause of the different MID.....is the different MID not a problem anymore ? also will you be able to get OTA updates after you debrand and flash stock Jelly Bean ROM
Click to expand...
Click to collapse
After s-off the CID changing is easy and S-off disables signature checking so you can extract the rom.zip(ruu) and edit the android-info and change the mid in that text file save it and then add it to some.zip and flash it as RUU , it will work ! But remember you will need s-off, and you will get OTAs , Donot relock the bootloader ! the bootloader should be saying S-off and unlocked .

cyriantherockstar said:
tried installing the JB RUU over my stock 2.31 ICS, but i get an unknown error ..im s-off already and changed cid to HTC__001, and i get the system notification for the JB OTA..is it safe to just install the OTA? coz i've read in another thread that some devices got bricked by installing the OTA (although they are using supercid when they upgraded..
Click to expand...
Click to collapse
I recommend installing the RUU over the OTA , I have not tried the ota as my device was bricked by it earlier , the day i got it back from JTAG Repair I s-offed it and changed CID to htc__001 and flashed JB RUU it went smooth !
what error do you get ?

i get the image error

Re: [Guide] unbranding HTC ONE S S4
cyriantherockstar said:
i get the image error
Click to expand...
Click to collapse
Flash the Rom.zip from the ruu via fastboot flash zip Rom.zip after rebooting into ruu mode by fastboot oem rebootRUU , then post the exact error ! Try the 2.31 ruu if it works then just after the 2.31 ruu run the jb ruu
Sent from my HTC One S using xda app-developers app

i also tried to extract the rom.zip from the jb ruu, but i cant open it, winrar is saying it's corrupt so i cant edit the android-info

cyriantherockstar said:
i also tried to extract the rom.zip from the jb ruu, but i cant open it, winrar is saying it's corrupt so i cant edit the android-info
Click to expand...
Click to collapse
Its encrypted !

aditya. said:
UNBRAND HTC ONE S THE RIGHT WAY​
Then Download this JELLYBEAN RUU -
Extract it and then edit the android-info (edit the model id to PJ401100) then flash it !
Click to expand...
Click to collapse
Extract the .exe file on my pc? I don't see android-info in the files inside it, what should I be looking for and what should I edit it with?
Or do you mean install it onto the phone and then change something?

Re: [Guide] unbranding HTC ONE S S4
Hey can I ask if it is working for one s s3 variants? Because I really need to s-off
Sent from my HTC One S using xda app-developers app

Re: [Guide] unbranding HTC ONE S S4
dieseldane86 said:
Extract the .exe file on my pc? I don't see android-info in the files inside it, what should I be looking for and what should I edit it with?
Or do you mean install it onto the phone and then change something?
Click to expand...
Click to collapse
When you run the .exe file in the temporary folder you will see a file Rom.zip that's it copy and paste that to some location and inside that there is the android-info
Sent from my HTC One S using xda app-developers app

Can't unlock bootloader, flash RUU zip on HBOOT 1.54

So here's the story. I have a Butterfly X920D with the original CID of HTC__044 and the .707 WWE ROM.
I then did the S-OFF and my CID has changed to 11111111 and unlock bootloader to flash custom recovery so I can flash the .709 TW rom so I can install the Sense 5 leak.
Now I want to revert back to stock .707 WWE ROM but I cannot do it anymore. On fastboot it says 'status read failed, too many links' something like that, when I flash the PL99IMG.zip.
I'm still S-OFF.
Current HBOOT version is 1.54.

WPMan said:
So here's the story. I have a Butterfly X920D with the original CID of HTC__044 and the .707 WWE ROM.
I then did the S-OFF and my CID has changed to 11111111 and unlock bootloader to flash custom recovery so I can flash the .709 TW rom so I can install the Sense 5 leak.
Now I want to revert back to stock .707 WWE ROM but I cannot do it anymore. On fastboot it says 'status read failed, too many links' something like that, when I flash the PL99IMG.zip.
I'm still S-OFF.
Current HBOOT version is 1.54.
Click to expand...
Click to collapse
so you want to unlock bootloader (HBOOT version is 1.54) ?
now you have stock recovery or custom recovery installed ?

it2007me said:
so you want to unlock bootloader (HBOOT version is 1.54) ?
now you have stock recovery or custom recovery installed ?
Click to expand...
Click to collapse
I can unlock it anytime. I figured that I needed to request the token again. As of now, I'm on cwm recovery.
My main problem now is that I am getting the FAILED (status read failed (Too many links)) message when I flash the RUU.

WPMan said:
I can unlock it anytime. I figured that I needed to request the token again. As of now, I'm on cwm recovery.
My main problem now is that I am getting the FAILED (status read failed (Too many links)) message when I flash the RUU.
Click to expand...
Click to collapse
Try flashing the Rom in custom recovery if that dont work use the s-off tool and install the firmware
Sent from my HTC Butterfly using xda premium

[Q] !Help! - HTC Ville is stuck in bootloader bootloop

Hi,
I had the HTC Ville (S4) with o2 (DE) branding running on Cyanogenmod 10.0. Because the new stable version of CM 10.1.3 came out, I decided to flash the newer ROM.
To do this, I had to upgrade my HBOOT (Which currently still is 1.13.0000) with the help of this post:
http://forum.xda-developers.com/showthread.php?t=2322755
Sadly I've overread that this "How To" is only for unbranded devices and got the message: ( FAILED (remote: 41 model id check fail)).
Now my Phone has this Problems:
-Can't boot into my ROM (CM10)
-Bootloader is relocked
-When trying to boot into the recovery, I end up back in the bootloader.
-Unlocking the bootloader doesn't work. (Everytime I order a "Identifier Token" via "fastboot oem get_identifier_token", I get a different token (?!)).
Some details to my Phone:
HTC Ville (S4) with o2(DE) branding (CID = O2___102)
S-ON
HBoot = 1.13.0000
Radio = 0.16.31501S.17_2
What can I do ? - Please Help :crying:

Since there isn't a jelly bean ruu for your cid, run the ice cream sandwich ruu and get the OTA through settings.
Then you can go about unlocking and flashing a new Rom.
Sent from my HTC One S using Tapatalk

tivofool said:
Since there isn't a jelly bean ruu for your cid, run the ice cream sandwich ruu and get the OTA through settings.
Then you can go about unlocking and flashing a new Rom.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Thanks for reply,
I tried to flash this RUU (RUU_Ville_U_ICS_40_S_O2_UK_2.38.206.2_Radio_1.08es.50.02.16_10.09b.50.04L_release_278818_signed).
But I got this error: ERROR[131]: CUSTOMER ID ERROR
Think it's because the ruu is an UK version and I have a DE (German) device...
What now ? :/

LelloParker said:
Thanks for reply,
I tried to flash this RUU (RUU_Ville_U_ICS_40_S_O2_UK_2.38.206.2_Radio_1.08es.50.02.16_10.09b.50.04L_release_278818_signed).
But I got this error: ERROR[131]: CUSTOMER ID ERROR
Think it's because the ruu is an UK version and I have a DE (German) device...
What now ? :/
Click to expand...
Click to collapse
That stinks that we don't have a RUU for you to use.
With your cid, maybe you should think about supercid/s-off.
SuperCid
http://forum.xda-developers.com/showthread.php?t=1671643
S-off
http://forum.xda-developers.com/showthread.php?t=2155135
Once S-off you can easily change CID and flash that firmware or whatever RUU you want.

tivofool said:
That stinks that we don't have a RUU for you to use.
With your cid, maybe you should think about supercid/s-off.
SuperCid
http://forum.xda-developers.com/showthread.php?t=1671643
S-off
http://forum.xda-developers.com/showthread.php?t=2155135
Once S-off you can easily change CID and flash that firmware or whatever RUU you want.
Click to expand...
Click to collapse
Thought about that too. But how can I do this with a un-unlockable bootloader and no running OS ? Sounds hard to me.

LelloParker said:
Thought about that too. But how can I do this with a un-unlockable bootloader and no running OS ? Sounds hard to me.
Click to expand...
Click to collapse
Ya need to get that unlocked.
Either http://forum.xda-developers.com/showthread.php?t=1583427
resubmitting to get a new Unlock_code.bin
or using your old one you probably have on your pc.
http://forum.xda-developers.com/showthread.php?t=2471151 seems like a easy way to do it.

tivofool said:
Ya need to get that unlocked.
Either http://forum.xda-developers.com/showthread.php?t=1583427
resubmitting to get a new Unlock_code.bin
or using your old one you probably have on your pc.
http://forum.xda-developers.com/showthread.php?t=2471151 seems like a easy way to do it.
Click to expand...
Click to collapse
I've tried to unlock that bootloader thousend times...
But every time I request the Token ID from my phone, I'll get a different one.. :/ (since the failed hboot-flash attempt)

[Q] Update hboot from 2.13 to 2.15/2.16 (SOLVED)

UPDATE 30/11/2013:
This thread describes my efforts in updating my unlocked One S to a hboot higher than 2.13. The phone had an H3G CID but non of the RUU's (see thread) worked. For me the solution was to Super CID and S-OFF the phone. Iḿ now on hboot 2.16.
END UPDATE
After more than two years of using Android (Legend, Desire S) phones and rooting them, I now have to register to be able to ask a question on this great forum.
Yesterday I obtained a One S. It is a UK model (not sim-locked to a carrier). I unlocked the bootloader almost immediatly with the intention of running a 4.3 or 4.4 based ROM (cyanogenmod or codename lungo). Here are some of the getvar details:
Code:
version: 0.5
version-bootloader: 2.13.0000
version-baseband: 1.11.50.05.28
version-misc: PVT SHIP S-ON
cidnum: H3G__001
boot-mode: FASTBOOT
Both cyanogen 4.4 and lungo ended in a bootloop and I figured it had to do with the hboot version. Self assured as I was I did not do a nandroid backup in twrp when flashing cyanogen and lungo and I ended up looking for a rom that would boot. I was succesful with MagioRom_ONE_S_RC6. From that I intended to use a RUU to update my hboot. I tried several (including both the H3G's) from this resource. All ended up in errors (131, 132, 155, 170 and probably some more). After reading some threads I relocked the bootloader and flashed stock recovery. All to no avail, no RUU will install. After reading a bit more I concluded that SuperCID was my best option of getting my brand new One S to a higher hboot version. I decided to go with this tutorial, but I ended up in another frustration: adb is not working for me in both windows (7) and linux (ubuntu). I reinstall the drivers (under windows) and tried some other things, but nothing works.
This is where I am now. I hope someone is willing to help. I tried to be as complete in describing the things I tried and the information I have, but I'd be happy to provide any additional info.
Getting custom roms on the legend and desire s was a lot easier.

First I do not own a UK version One S, I have the TMOUS but these are some tips that I used to help get my phone back from a non booting state.
Couple things,
Make absolutely sure this is a Ville not a VilleC2 (aka S3 One S)
Are you at all able to boot the phone to a recovery program (TWRP/CWM etc)?
Ensure that you have followed these instructions to get adb and fastboot to work. Use the Unlock section. Its best to make sure you can fastboot or at least adb before doing anything with the phone.
If you can get to fastboot (Power and Vol Down button), connect your phone and run the command "fastboot devices" post output - keep in mind command shell has to be at the adb directory most of the time C:\adb or something similar.
Make sure you have the latest driver installed and to remove (completely uninstall it) HTC Sync or Sync Manager. Not needed if you don't keep the stock ROM on your phone IMO. If you are unsure, remove all HTC software and just reinstall the driver.
Make sure you are running the right RUU for your specific device. What carrier was this phone for when it was purchased? Assuming it is H3G this is the latest RUU available for that particular OneS. You will have to run either the same version F/W or later RUU, you cannot go backwards.
Once we get the phone back to stock rom. Then start over by unlocking bootloader and getting S-OFF THEN start to flash roms.
In order to run CM11 Beta you need to have l a certain recovery installed + a few other things. I think it would be best if you can get back on CM10.1.3 Stable first then attempt to go to CM11.
TL;DR
Verify carrier and version of phone
Lock Bootloader if not already done
Download and run carrier specific RUU while in fastboot mode (power +vol down)
Unlock Bootloader
S-OFF
Flash rom

@pyrocide
Thanks for the reply. I've been working through your post. First I wanna point out that the phone is in a working state know running the MagioRom and I can boot into TWRP recovery.
Here is the output for fastboot devices:
Code:
SH24PW402945 fastboot
I'm sure it is an s4. It is says Z520e and 1.5 ghz on the box. I got the phone from ebay, so I'm not 100% which carrier it was on, but there was a T-Mobile sim still in the phone :silly:. The CID reads H3G though and the phone is not locked to a carrier/network since my giffgaff sim works fine.
I got adb to work. Thanks for that :good:.
I relocked the bootloader with fastboot oem lock (it know says 'relocked'). Running the suggested RUU ends in an error 155 during the veryfiying signature step.

And you ran the RUU while you were in fastboot usb mode?
based on Google
"ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again."
So the RUU is wrong, we need to find out specifically what version of OneS it is.
run this command while in fasboot usb mode
Code:
fastboot getvar all
post modelid: XXXXXXXXXX

The output of that:
Code:
modelid: PJ4010000

http://androidforums.appforerunner....ed-problem-restoring-ruu-error-131-151-a.html
Guy had the same problem and same modelid
Used this RUU and was able to go back to stock.
Hopefully this works.

Thanks for the help. Appreciate it.
That RUU ended in an 131 error, unfortunately.

H2Oxide said:
Thanks for the help. Appreciate it.
That RUU ended in an 131 error, unfortunately.
Click to expand...
Click to collapse
At this point i would suggest doing all Euro RUUs. That should have worked considering the modelid is the same for that guy and it worked. Sorry man but I don't know what else to suggest other than to do each RUU. If none of them work then something is definitely wrong.

pyrocide said:
At this point i would suggest doing all Euro RUUs. That should have worked considering the modelid is the same for that guy and it worked. Sorry man but I don't know what else to suggest other than to do each RUU. If none of them work then something is definitely wrong.
Click to expand...
Click to collapse
Would I need to reflash a/the stock recovery to make for a successful RUU flash?

The list of the RUU's I tried. Non worked... Really frustrating.
Code:
RUU_Ville_U_BM_1.70.666.1_R_Radio_0.16.31501S.06_3_10.20.31501S.09L_release_255222_signed.exe
RUU_Ville_U_BM_1.84.666.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265369_signed.exe
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed.exe
RUU_Ville_U_H3G_UK_1.78.771.5_Radio_0.16.31501S.19_2_10.23.31501S.10L_release_258982_signed.exe
RUU_Ville_U_HTC_Europe_1.09.401.1_R_Radio_0.14.3059.14_2_release_243825_signed.exe
RUU_Ville_U_HTC_Europe_1.47.401.1_Radio_0.15.31501S.13_3_10.08.31501S.04L_release_250115_signed.exe
RUU_Ville_U_HTC_Europe_1.53.401.2_Radio_0.15.31501S.19_10.12.31501S.06L_release_251412_signed.exe
RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed.exe
RUU_Ville_U_ICS_40_S_BM_2.40.666.1_Radio_1.09ts.50.02.04_10.08g.50.04L_release_280275_signed.exe
RUU_Ville_U_ICS_40_S_HTC_Europe_2.21.401.10_Radio_1.06s.50.02.27_2_10.08.50.04L__release_271119_signed.exe
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe
RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed.exe
RUU_Ville_U_ICS_40_S_Vodafone_UK_2.38.161.6_Radio_1.08es.50.02.21_10.09c.50.04L_release_280400_signed.exe
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe
RUU_Ville_U_O2_UK_1.78.206.4_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258707_signed.exe
RUU_Ville_U_TMO_DE_1.77.111.5_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_259421_signed.exe
RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02_10.18.31501S.08L_release_262073_signed.exe
RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed.exe
RUU_Ville_U_Vodafone_UK_1.53.161.3_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251482_signed.exe
RUU_Ville_U_Vodafone_UK_1.78.161.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258386_signed.exe

H2Oxide said:
Would I need to reflash a/the stock recovery to make for a successful RUU flash?
Click to expand...
Click to collapse
No, running the RUU erases custom recovery & flashes stock recovery.
Did all of the downloads MD5 checkout correctly?
Also, just to make sure we are ruling everything out. Did you run the RUU by double clicking or right clicking and Run as Administrator? If you just did it by double clicking rerun the one I posted that fixed the other guys issue by using Run as Administrator. Again be sure to be in fastboot usb mode and that "fastboot devices" command shows your device in the output. Make sure you use a usb 2.0 port in case of compatibility issues and the cable that came with the phone if possible.

pyrocide said:
No, running the RUU erases custom recovery & flashes stock recovery.
Did all of the downloads MD5 checkout correctly?
Also, just to make sure we are ruling everything out. Did you run the RUU by double clicking or right clicking and Run as Administrator? If you just did it by double clicking rerun the one I posted that fixed the other guys issue by using Run as Administrator. Again be sure to be in fastboot usb mode and that "fastboot devices" command shows your device in the output. Make sure you use a usb 2.0 port in case of compatibility issues and the cable that came with the phone if possible.
Click to expand...
Click to collapse
I used another laptop. Running the suggested RUU again resulted in the same 131 error. I ran as admin and did an md5 check. I'd say the other RUU's will also result in an error again...

H2Oxide said:
I used another laptop. Running the suggested RUU again resulted in the same 131 error. I ran as admin and did an md5 check. I'd say the other RUU's will also result in an error again...
Click to expand...
Click to collapse
Did some digging.
Error 155 - usually wrong recovery.img /wrong boot.img
Error 140 - wrong bootloader / bootloader unlocked
Error 131 - wrong RUU for your device
So, if one is giving you the 155 error then try with the stock recovery and do the RUU.
The phone does say relocked in bootloader right? Try doing fastboot oem lock again and run the RUU that gave you the 155 error.

Wow, that still didn't work.
So I flashed stock recovery and relocked the bootloader. Then I tried three RUU's, both the H3G RUU's and the HTC Europe RUU mentoined before. The H3G's ended up in a 155 error, the HTC Europe in a 131.
So, still no succes. This is getting annoying, right... ? Any other suggestions besides flushing the One S down the toilet?
Regards.

H2Oxide said:
Wow, that still didn't work.
So I flashed stock recovery and relocked the bootloader. Then I tried three RUU's, both the H3G RUU's and the HTC Europe RUU mentoined before. The H3G's ended up in a 155 error, the HTC Europe in a 131.
So, still no succes. This is getting annoying, right... ? Any other suggestions besides flushing the One S down the toilet?
Regards.
Click to expand...
Click to collapse
Im at a loss man. At this point I would email HTC with the getvar all info and see what they say and which RUU they give you to try. If nothing else itll help narrow down exactly what model phone it is.

pyrocide said:
Im at a loss man. At this point I would email HTC with the getvar all info and see what they say and which RUU they give you to try. If nothing else itll help narrow down exactly what model phone it is.
Click to expand...
Click to collapse
Just a thought. Since the 155 error could point to both a wrong recovery.img or a wrong boot.img, I could try flashing another (stock) boot.img. Maybe the custom rom's boot.img is in the way. So what boot.img would I need?

So I did that. I extracted the boot.img from de H3G RUU and flashed it. I also extracted the recovery and flashed that. I then tried different scenario's with the H3G, the HTC Europe and the O2 UK RUU's. Non worked. The H3G ended up in 155, the others in 131.
Anyone else any ideas on this besides emailing HTC?

H2Oxide said:
Just a thought. Since the 155 error could point to both a wrong recovery.img or a wrong boot.img, I could try flashing another (stock) boot.img. Maybe the custom rom's boot.img is in the way. So what boot.img would I need?
Click to expand...
Click to collapse
You could try to decompile the 155 error exe and fastboot flash boot boot.img but I am very nervous that might screw something up. I still suggest contacting HTC directly to have their input on what exactly RUU is needed and if you do have the right one, why it is not working.

Code:
<T133845><DEBUG><OUT>FAILED (remote: 44 hboot version check fail)</OUT>
Got the line above out the RUU log files. This is the 155 error RUU.
This raises two question:
Is it possible to get the expected hboot version number out the decompiled RUU (decompiled = the stuff placed in user/temp)?
Is it possible to down/upgrade hboot with any of the hboot versions posted here or would I run the risk of softbricking my One S then?

Don't flash any of that hboots. You will brick.
Just try to s-off, follow facepalm method in dev forum.
After that you can flash any ruu.
Sent from my HTC One S using Tapatalk