Database Info

[Guide] Solved Problem - Error flashing RUU + Guide

Hey Guys,
My Problem:
got a little Problem with the TMO Europe RUU.
I have to go back to Stock due to a warrenty issue. Thus I wanted to do this with the above mentioned RUU.
I first was on ICS with new 3.25 firmware. So i went back to old 3.12 FW and the 1.17 HBOOT. After that I installed the ARHD 4.x.x
When I now try to update it says update from 2.0.8,... to 1.45
but when it about to Start there is this 155~159 Error which says that it is not the right RUU
My Sensation was shipped with TMO Branding thats the reason why i tried it with this RUU
I also tried some other setting like:
super cid' ed again
3.24 firmware
different RUU
...
Can someone help me please​
Solution that worked for me:
You have to be sure that you took the right RUU otherwise it's no good
Do this on your own risk ! For me it worked without any problems
start the ruu an continue till the step where it says update from X.X.xXX to your y.y.yyy
change the view of your Windows folders the way that you can see the hidden files
go to c:\User\YOURNAME\appdata\local\temp
there search in one of the last edited folders (which has to be name cryptic like :{18abb736-d55c-4fa4-a3e5-7c78512fa924} for Rom.zip
copy it to somewhere you'll find again
name it to PG58IMG.zip
put it on your sdcard
restart into bootloader and it will update to your chosen ruu
Possible helpful Links:
[Guide] to Installing S-off, Unlocking, ClockWork, Root, SuperCID & S-on
[DEV] HTC Sensation & HTC Sensation XE firmware | Partitions Info | [22.01.2012]
[Firmware][Jan 29]User-Friendly Firmware 1.17/3.12/3.24 Unlocked(No need to SuperCID)
[ROM]Shipped Pyramid ROM Collection

H89P said:
Hey Guys,
My Problem is solved
got a little Problem with the TMO Europe RUU.
I have to go back to Stock due to a warrenty issue. Thus I wanted to do this with the above mentioned RUU.
I first was on ICS with new 3.25 firmware. So i went back to old 3.12 FW and the 1.17 HBOOT. After that I installed the ARHD 4.x.x
When I now try to update it says update from 2.0.8,... to 1.45
but when it about to Start there is this 155~159 Error which says that it is not the right RUU
My Sensation was shipped with TMO Branding thats the reason why i tried it with this RUU
I also tried some other setting like:
super cid' ed again
3.24 firmware
different RUU
...
Can someone help me please
Click to expand...
Click to collapse
Hey, Please how did you solve your problem? Ive got a similar issue with my sensation

Try going to fastboot and run the RUU from there.
Sent from my HTC Sensation 4G using XDA App

slimldj said:
Hey, Please how did you solve your problem? Ive got a similar issue with my sensation
Click to expand...
Click to collapse
What I dit is the following. But you have to be sure that you took the right RUU otherwise it's no good
Do this on your own risk ! For me it worked without any problems
start the ruu an continue till the step where it says update from X.X.xXX to your y.y.yyy
change the view of your Windows folders the way that you can see the hidden files
go to User\YOURNAME\appdata\local\temp
there search in one of the last edited folders (which has to be name cryptic like :{18abb736-d55c-4fa4-a3e5-7c78512fa924} for Rom.zip
copy it to somewhere you'll find again
name it to PG68IMG.zip
put it on your sdcard
restart into bootloader and it will update to your chosen ruu
hope this helps

Almost exactly what I did at the time, only difference is I renamed it to PG58IMG, and not PG68IMG.

Trekest said:
Almost exactly what I did at the time, only difference is I renamed it to PG58IMG, and not PG68IMG.
Click to expand...
Click to collapse
Thanks, changing,...

H89P said:
Hey Guys,
My Problem:
got a little Problem with the TMO Europe RUU.
I have to go back to Stock due to a warrenty issue. Thus I wanted to do this with the above mentioned RUU.
I first was on ICS with new 3.25 firmware. So i went back to old 3.12 FW and the 1.17 HBOOT. After that I installed the ARHD 4.x.x
When I now try to update it says update from 2.0.8,... to 1.45
but when it about to Start there is this 155~159 Error which says that it is not the right RUU
My Sensation was shipped with TMO Branding thats the reason why i tried it with this RUU
I also tried some other setting like:
super cid' ed again
3.24 firmware
different RUU
...
Can someone help me please​
Solution that worked for me:
You have to be sure that you took the right RUU otherwise it's no good
Do this on your own risk ! For me it worked without any problems
start the ruu an continue till the step where it says update from X.X.xXX to your y.y.yyy
change the view of your Windows folders the way that you can see the hidden files
go to c:\User\YOURNAME\appdata\local\temp
there search in one of the last edited folders (which has to be name cryptic like :{18abb736-d55c-4fa4-a3e5-7c78512fa924} for Rom.zip
copy it to somewhere you'll find again
name it to PG58IMG.zip
put it on your sdcard
restart into bootloader and it will update to your chosen ruu
Possible helpful Links:
[Guide] to Installing S-off, Unlocking, ClockWork, Root, SuperCID & S-on
[DEV] HTC Sensation & HTC Sensation XE firmware | Partitions Info | [22.01.2012]
[Firmware][Jan 29]User-Friendly Firmware 1.17/3.12/3.24 Unlocked(No need to SuperCID)
[ROM]Shipped Pyramid ROM Collection
Click to expand...
Click to collapse
you are god

H89P said:
Hey Guys,
My Problem:
got a little Problem with the TMO Europe RUU.
I have to go back to Stock due to a warrenty issue. Thus I wanted to do this with the above mentioned RUU.
I first was on ICS with new 3.25 firmware. So i went back to old 3.12 FW and the 1.17 HBOOT. After that I installed the ARHD 4.x.x
When I now try to update it says update from 2.0.8,... to 1.45
but when it about to Start there is this 155~159 Error which says that it is not the right RUU
My Sensation was shipped with TMO Branding thats the reason why i tried it with this RUU
I also tried some other setting like:
super cid' ed again
3.24 firmware
different RUU
...
Can someone help me please​
Solution that worked for me:
You have to be sure that you took the right RUU otherwise it's no good
Do this on your own risk ! For me it worked without any problems
start the ruu an continue till the step where it says update from X.X.xXX to your y.y.yyy
change the view of your Windows folders the way that you can see the hidden files
go to c:\User\YOURNAME\appdata\local\temp
there search in one of the last edited folders (which has to be name cryptic like :{18abb736-d55c-4fa4-a3e5-7c78512fa924} for Rom.zip
copy it to somewhere you'll find again
name it to PG58IMG.zip
put it on your sdcard
restart into bootloader and it will update to your chosen ruu
Possible helpful Links:
[Guide] to Installing S-off, Unlocking, ClockWork, Root, SuperCID & S-on
[DEV] HTC Sensation & HTC Sensation XE firmware | Partitions Info | [22.01.2012]
[Firmware][Jan 29]User-Friendly Firmware 1.17/3.12/3.24 Unlocked(No need to SuperCID)
[ROM]Shipped Pyramid ROM Collection
Click to expand...
Click to collapse
Thankyou very much!

i just flashed it while im in fastboot and everything when good untl i got the error saying:
error[110] file open error.
what can i do now, i dont have a bootloader or fastboot cant do anything with my phone its all dead!!
stuck at the HTC silver black screen and thats all please help me.

Lawrence7 said:
i just flashed it while im in fastboot and everything when good untl i got the error saying:
error[110] file open error.
what can i do now, i dont have a bootloader or fastboot cant do anything with my phone its all dead!!
stuck at the HTC silver black screen and thats all please help me.
Click to expand...
Click to collapse
ok ...you have blaack screen with silver htc right ?
you need to open a command prompt from your adb/fastboot folder
and type
fastboot reboot-bootloader
to get out of this ...you will be taken to bootloader btw

Lawrence7 said:
i just flashed it while im in fastboot and everything when good untl i got the error saying:
error[110] file open error.
what can i do now, i dont have a bootloader or fastboot cant do anything with my phone its all dead!!
stuck at the HTC silver black screen and thats all please help me.
Click to expand...
Click to collapse
Doesn't Sound good
Did you change you try everything I Did?
before you tried to flash the RUU?
If Not there is a solution:
Have a look here:
[UNBRICK] HTC Unbricking Project
Sent from my HTC One X using xda premium

H89P said:
Doesn't Sound good
Did you change you try everything I Did?
before you tried to flash the RUU?
If Not there is a solution:
Have a look here:
[UNBRICK] HTC Unbricking Project
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
he is stuck at RUU mode thats all (black screen with silver HTC )
he is not bricked
he can simply get out of it using fastboot commands
(fastboot reboot-bootloader -> to go back to bootloader)
BTW ..awesome app drawers ..it would have been great if you do it for SENSATION too

[Q] Vodafone RUU

Hi, i need to revert to stock and want to know if the Vodafone UK RUU will work on my device with the cid VODAP102 (Vodafone Germany) ? Has anyone tried? Or is there a RUU Vodafone DE?
Thanks in advance!
Sent from my HTC Desire S using xda app-developers app

Hi,
The Vodafone uk ruu works perfect.
Gesendet von meinem HTC Desire S mit Tapatalk 2

petjo said:
Hi, i need to revert to stock and want to know if the Vodafone UK RUU will work on my device with the cid VODAP102 (Vodafone Germany) ? Has anyone tried? Or is there a RUU Vodafone DE?
Thanks in advance!
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
When you have the RUU, run it without a device first. When the first window of the RUU opens, drag it to the side of your screen, open Explorer and search your windows drive for "rom.zip". When you find it copy it to another location and close the RUU window.
Open rom.zip archive and you will find a file called "android-info.txt" open it and see if your cid is listed there. If it is present you can flash this RUU safely.

Yep, it's in there. Thank you guys!
Sent from my HTC Desire S using xda app-developers app

Same in reverse ...
petjo said:
Yep, it's in there. Thank you guys!
Click to expand...
Click to collapse
Conversely, that should mean that I can use the Vodafone UK RUU RUU_Saga_Vodafone_UK_1.32.161.1_Radio_20.28b.30.0805U_38.03.02.15_M_release_179398_signed.exe to downgrade my Vodafone DE Desire S (Android 2.3.5, Hboot 2.00.0002, Software 2.10.161.5) using this method here? - http://forum.xda-developers.com/showpost.php?p=20535265&postcount=26

amidabuddha said:
When you have the RUU, run it without a device first. When the first window of the RUU opens, drag it to the side of your screen, open Explorer and search your windows drive for "rom.zip". When you find it copy it to another location and close the RUU window.
Open rom.zip archive and you will find a file called "android-info.txt" open it and see if your cid is listed there. If it is present you can flash this RUU safely.
Click to expand...
Click to collapse
What is the significance of HBOOT Preupdate? All the RUUs have a Preupdate value 13, my phone has a Preupdate value of 12. That doesn't matter probably?

Medhavi said:
Conversely, that should mean that I can use the Vodafone UK RUU RUU_Saga_Vodafone_UK_1.32.161.1_Radio_20.28b.30.0805U_38.03.02.15_M_release_179398_signed.exe to downgrade my Vodafone DE Desire S (Android 2.3.5, Hboot 2.00.0002, Software 2.10.161.5) using this method here? - http://forum.xda-developers.com/showpost.php?p=20535265&postcount=26
Click to expand...
Click to collapse
Medhavi said:
What is the significance of HBOOT Preupdate? All the RUUs have a Preupdate value 13, my phone has a Preupdate value of 12. That doesn't matter probably?
Click to expand...
Click to collapse
I don't know u guys are gonna get a RUU now.... HTC is destroying every RUU Web on earth now....
Sent from my supercharged tank

Dear Guys,
Does anybody have this RUU?
Voda_UK_2.10.161.5
I can not unbrick my friend's phone without this, because it's "s-on" and the above version is installed, but while tring to install custom rom an error occoured. The device doesn't boot, stops at HTC logo...
Thanks in advance

http://www.tsar3000.com/Joomla/inde...-stock-roms&catid=65:htc-downloads&Itemid=107
Try this, not sure if the ruu is there but is one of the few sites still open
“Without deviation from the norm, progress is not possible.”*―*Frank Zappa

Thanks for your help, but it's not there. Is there any way to restore DS without this RUU? It's bootloader unlocked, rooted, has the custom recovery. unfortunately the "misc version" was not uploaded in adb mode, thus I cannot change the main version, to be able to downgrade it. But since the main version is "too high" (2.10.161.5) and there is no adb mode and I dont have the original RUU there is nothing to do. Is it possible somehow to change the main version in fastboot???? I think this would be the only chance without the the ruu.

Try this site http://www.androidfiles.org/ruu/?developer=Saga
“I've had great success being a total idiot. ”*―*Jerry Lewis

pezus1 said:
Dear Guys,
Does anybody have this RUU?
Voda_UK_2.10.161.5
I can not unbrick my friend's phone without this, because it's "s-on" and the above version is installed, but while tring to install custom rom an error occoured. The device doesn't boot, stops at HTC logo...
Thanks in advance
Click to expand...
Click to collapse
Guess you forgot to fastboot flash boot boot.img
Also, why would you need a RUU anyway? You can still enter recovery, can't you? Heck, of course you can: even if you couldn't you could always fastboot flash recovery recovery.img a working one.
I fail to see why a RUU would be necessary here.

Aquous said:
Guess you forgot to fastboot flash boot boot.img
Also, why would you need a RUU anyway? You can still enter recovery, can't you? Heck, of course you can: even if you couldn't you could always fastboot flash recovery recovery.img a working one.
I fail to see why a RUU would be necessary here.
Click to expand...
Click to collapse
Thanks for your help, but I dont really understand what u say..... Right now there is clockwork 5.0.2.0 on it, we tried to install custom roms, which seemed to be done, but the phone stops at HTC logo after flashing. I guess I could flash back the original recovery (actually I only have one from RUU 1.32.161.1), but how would it solve my problem? How about the other image files, like system, hboot etc? Please exlain it to me a bit more detailed! Thx

pezus1 said:
Thanks for your help, but I dont really understand what u say..... Right now there is clockwork 5.0.2.0 on it, we tried to install custom roms, which seemed to be done, but the phone stops at HTC logo after flashing. I guess I could flash back the original recovery (actually I only have one from RUU 1.32.161.1), but how would it solve my problem? How about the other image files, like system, hboot etc? Please exlain it to me a bit more detailed! Thx
Click to expand...
Click to collapse
have you done
Code:
fastboot flash boot boot.img
?
Sent from my supercharged :tank:

hisname said:
have you done
Code:
fastboot flash boot boot.img
?
Sent from my supercharged :tank:
Click to expand...
Click to collapse
Lets see again: bootloader unlocked, cwm 5.0.2.0 installed, as you adviced I flased an official 1.32.161.1(older than the original 2.10.161.5) boot.img, then tried to install from recovery the custom rom, which still seems to be ok, but the phone freezes at htc logo during boot. This custom rom is a well known working version, there shouldnt be any problem. What else can I do without the RUU?

pezus1 said:
Lets see again: bootloader unlocked, cwm 5.0.2.0 installed, as you adviced I flased an official 1.32.161.1(older than the original 2.10.161.5) boot.img, then tried to install from recovery the custom rom, which still seems to be ok, but the phone freezes at htc logo during boot. This custom rom is a well known working version, there shouldnt be any problem. What else can I do without the RUU?
Click to expand...
Click to collapse
What? You flashed the boot.img from a RUU and expected it to work with a custom ROM??
Why don't you just flash the boot.img that's included with the custom ROM...?

Aquous said:
What? You flashed the boot.img from a RUU and expected it to work with a custom ROM??
Why don't you just flash the boot.img that's included with the custom ROM...?
Click to expand...
Click to collapse
Thanks guys, problem solved!!

pezus1 said:
Thanks guys, problem solved!!
Click to expand...
Click to collapse
Can you mark thread title solved, thanks.
“Pressure is something you feel when you don't know what the hell you're doing.”*―*Peyton Manning

[Q] Phone won't boot up normally and cannot flash RUU

Hi,
First of all, sorry if this has already been answered somewhere else but I literally spent the last 3 days gathering information on xda reading threads more of less related to my specific problem. I would appreciate any new piece of information that I could have missed.
I had a custom ROM (ARHD 7.1). I wanted to go back to stock ROM for my provider (Bell Mobility). I successfully went back to GB 2.3.4 by flashing my provider's RUU. My phone would not take OTA update to ICS (4.0.3). I changed my SuperCID back to carrier-specific and phone took OTA update. However, it didn't reboot properly. I thought that this was because I was S-OFF and unlocked. I changed to S-ON but that bricked the phone (not even powering on). I found a tool to unbrick the phone that flashes a proper HBOOT (1.17 in my case). That fixed the brick problem and I could get back to bootloader. Since then, I'm stucked with a phone that doesn't boot into the ROM and cannot get into recovery. I can get into bootloader but given that I am S-ON, I'm very limited to what I can do.
I have tried re-flashing my 1.45.666.1 RUU but it looks like some time ago (don't ask me why...), I changed my MID to PG5810000 and the RUU is expecting PG5811000 so it is not possible to use RUU. I even tried modifying the android-info.txt with my MID but then RUU failed for another reason (bad signature I think).
So, this is very confusing but if I could summarize, I would say
*Cannot boot into stock ROM (it should be GB 2.3.4 from Bell Mobility)
*Can boot in bootloader
*S-ON
*MID=PG581000 (should be PG5811000 according to my provider Bell Mobility)
*CID=BM____001 (it is the correct one for Bell Mobility)
Bootloader information
PYRAMID PVT SHIP S-ON RLo
HBOOT-1.17.0008
RADIO-10.14.9035.01_M
eMMC-boot
May 13 2011.21:04:57
Is there any thing I can do to recover? Getting S-OFF would help of course but I cannot use Revolutionary tool normally as it requires you to boot in your ROM. Maybe there are some backdoor commands that Revolutionary uses that I can call with fastboot?
My last resort is to contact HTC or Bell but I'd like to avoid this as I am out of the warranty period, which my messing around would have voided anyway. Thanks for your help.
Fred

fdavidson said:
Hi,
First of all, sorry if this has already been answered somewhere else but I literally spent the last 3 days gathering information on xda reading threads more of less related to my specific problem. I would appreciate any new piece of information that I could have missed.
I had a custom ROM (ARHD 7.1). I wanted to go back to stock ROM for my provider (Bell Mobility). I successfully went back to GB 2.3.4 by flashing my provider's RUU. My phone would not take OTA update to ICS (4.0.3). I changed my SuperCID back to carrier-specific and phone took OTA update. However, it didn't reboot properly. I thought that this was because I was S-OFF and unlocked. I changed to S-ON but that bricked the phone (not even powering on). I found a tool to unbrick the phone that flashes a proper HBOOT (1.17 in my case). That fixed the brick problem and I could get back to bootloader. Since then, I'm stucked with a phone that doesn't boot into the ROM and cannot get into recovery. I can get into bootloader but given that I am S-ON, I'm very limited to what I can do.
I have tried re-flashing my 1.45.666.1 RUU but it looks like some time ago (don't ask me why...), I changed my MID to PG5810000 and the RUU is expecting PG5811000 so it is not possible to use RUU. I even tried modifying the android-info.txt with my MID but then RUU failed for another reason (bad signature I think).
So, this is very confusing but if I could summarize, I would say
*Cannot boot into stock ROM (it should be GB 2.3.4 from Bell Mobility)
*Can boot in bootloader
*S-ON
*MID=PG581000 (should be PG5811000 according to my provider Bell Mobility)
*CID=BM____001 (it is the correct one for Bell Mobility)
Bootloader information
PYRAMID PVT SHIP S-ON RLo
HBOOT-1.17.0008
RADIO-10.14.9035.01_M
eMMC-boot
May 13 2011.21:04:57
Is there any thing I can do to recover? Getting S-OFF would help of course but I cannot use Revolutionary tool normally as it requires you to boot in your ROM. Maybe there are some backdoor commands that Revolutionary uses that I can call with fastboot?
My last resort is to contact HTC or Bell but I'd like to avoid this as I am out of the warranty period, which my messing around would have voided anyway. Thanks for your help.
Fred
Click to expand...
Click to collapse
you sure the RUU you are using is correct ?
if so then best solution is to try revolutionary
try the tool with phone connected in fastboot ...it might work (i remember one guy doing that )

ganeshp said:
you sure the RUU you are using is correct ?
if so then best solution is to try revolutionary
try the tool with phone connected in fastboot ...it might work (i remember one guy doing that )
Click to expand...
Click to collapse
Thanks ganeshp for the quick answer. I am pretty confident about the RUU as it is the same one I originally ran to move from custom ICS ROM to stock 2.3.4 ROM.
For Revolutionary, even in fastboot, it is stuck in "Waiting for devices..." I think it is because it issues "adb devices" command and expects some answer before carrying on to the bootloader. I would need it to skip this step. Are there any argument to revolutionary to do that?
Fred

A little more update on RUU failure. If I change the modelid in android-info.txt, this means that I have to re-package the files back into ROM.zip. I am doing this with WinZip. Even without editing any file, just extracting the files from original ROM.zip from RUU back to another version of ROM.zip (no change), I noticed that file size is not the same. Maybe that explain with the signature check fails when flashing RUU. Now, I don't know what to use to re-package files into a ROM.zip archive to use RUU.
Fred

fdavidson said:
A little more update on RUU failure. If I change the modelid in android-info.txt, this means that I have to re-package the files back into ROM.zip. I am doing this with WinZip. Even without editing any file, just extracting the files from original ROM.zip from RUU back to another version of ROM.zip (no change), I noticed that file size is not the same. Maybe that explain with the signature check fails when flashing RUU. Now, I don't know what to use to re-package files into a ROM.zip archive to use RUU.
Fred
Click to expand...
Click to collapse
Short answer - you cannot touch or do anything to ROM.zip if you want to use RUU, changing anything changes MD5 sum hence the signature error.
What you should do is run an ICS RUU compatible with your MID

Jonny said:
Short answer - you cannot touch or do anything to ROM.zip if you want to use RUU, changing anything changes MD5 sum hence the signature error.
What you should do is run an ICS RUU compatible with your MID
Click to expand...
Click to collapse
Thanks Jonny, that is good information. My problem with this is that I have a provider-specific CID (BM_0001) and not superCID. If I can find an ICS RUU for my MID (the one wrongly change for my device, i.e. PG5810000), would the CID affect anything?
Fred

fdavidson said:
Thanks Jonny, that is good information. My problem with this is that I have a provider-specific CID (BM_0001) and not superCID. If I can find an ICS RUU for my MID (the one wrongly chance for my device, i.e. PG5810000), would the CID affect anything?
Fred
Click to expand...
Click to collapse
Mate MID/CID are checked prior to flashing rom, so if the MID/CID are not "correct" installation will not take place

dublinz said:
Mate MID/CID are checked prior to flashing rom, so if the MID/CID are not "correct" installation will not take place
Click to expand...
Click to collapse
Thanks everyone for taking some of your time to help me. From the information that I've received, it looks that I will not be able to recover my phone, That's bad because I thought I was just a few steps away, maybe by being able to flash an unlocked S-OFF H-Boot 1.17 and by some way tweak RUU so that it would work. I'll wait one or two days in case someone suggests something different and then see if HTC can help. It will be interesting (or embarassing) to hear what they have to say.
Cheers,
Fred

fdavidson said:
Thanks everyone for taking some of your time to help me. From the information that I've received, it looks that I will not be able to recover my phone, That's bad because I thought I was just a few steps away, maybe by being able to flash an unlocked S-OFF H-Boot 1.17 and by some way tweak RUU so that it would work. I'll wait one or two days in case someone suggests something different and then see if HTC can help. It will be interesting (or embarassing) to hear what they have to say.
Cheers,
Fred
Click to expand...
Click to collapse
Change back the android-info.txt and run the ruu again.. From phone connected in fastboot.. And let me know what error it showed
Edit: or simply run the ruu you have.. With phone connected to pc in bootloader/fastboot
Sent from my HTC Sensation 4G using xda premium

ganeshp said:
Change back the android-info.txt and run the ruu again.. From phone connected in fastboot.. And let me know what error it showed
Edit: or simply run the ruu you have.. With phone connected to pc in bootloader/fastboot
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
ganeshp,
Without modifying android-info.txt (just running the RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe), I am getting "ERROR [130]: MODEL ID ERROR. This is expected as my MID (modelID is incorrect. My phone is at PG5810000 when RUU expects PG5811000).
When I modify the android-info.txt in ROM.zip to have my correct MID, it goes a little bit further down the process. However, I am getting "ERROR [132]: SIGNATURE ERROR". Below is the related content of ruu_log.txt:
<T084503><DEBUG><CMD>fastboot -s SH16KV601188 flash zip "C:\Documents and Settings\fred\Local Settings\Temp\{A20F8D10-D7EB-4B01-91D2-68167E319F81}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T084503>
<T084609><DEBUG><OUT>sending 'zip' (416943 KB)... OKAY</OUT>
</DEBUG></T084609>
<T084609><DEBUG><OUT>writing 'zip'... INFOsignature checking...</OUT>
</DEBUG></T084609>
<T084722><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>
</DEBUG></T084722>
This is also expected as someone already pointed out earlier in this thread that ROM.zip cannot be modified because of different MD5 checksum. On this point, I am wondering if there would be some tool to re-generate a correct MD5 checksum.
Fred

fdavidson said:
ganeshp,
Without modifying android-info.txt (just running the RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe), I am getting "ERROR [130]: MODEL ID ERROR. This is expected as my MID (modelID is incorrect. My phone is at PG5810000 when RUU expects PG5811000).
When I modify the android-info.txt in ROM.zip to have my correct MID, it goes a little bit further down the process. However, I am getting "ERROR [132]: SIGNATURE ERROR". Below is the related content of ruu_log.txt:
<T084503><DEBUG><CMD>fastboot -s SH16KV601188 flash zip "C:\Documents and Settings\fred\Local Settings\Temp\{A20F8D10-D7EB-4B01-91D2-68167E319F81}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T084503>
<T084609><DEBUG><OUT>sending 'zip' (416943 KB)... OKAY</OUT>
</DEBUG></T084609>
<T084609><DEBUG><OUT>writing 'zip'... INFOsignature checking...</OUT>
</DEBUG></T084609>
<T084722><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>
</DEBUG></T084722>
This is also expected as someone already pointed out earlier in this thread that ROM.zip cannot be modified because of different MD5 checksum. On this point, I am wondering if there would be some tool to re-generate a correct MD5 checksum.
Fred
Click to expand...
Click to collapse
ok RUU way is closed for you then
now if you can unlock your bootloader ..things can be better for you
try HTC-DEV unlock ...once done ..you need to flash a custom GB rom from recovery

ganeshp said:
ok RUU way is closed for you then
now if you can unlock your bootloader ..things can be better for you
try HTC-DEV unlock ...once done ..you need to flash a custom GB rom from recovery
Click to expand...
Click to collapse
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred

fdavidson said:
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
Click to expand...
Click to collapse
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
edit: i just read your first post
so you can not use revolutionary

fdavidson said:
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
Click to expand...
Click to collapse
ahh even that got stuck huh ...try revolutionary again ..with phone boot-looping or when stuck at splash screen ..if revolutionary finds the device all good ..otherwise all doors closed
rzr86 said:
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
Click to expand...
Click to collapse
he tried revolutionary already ..and he currently didnt have a booting rom ..so it might not work

rzr86 said:
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
Click to expand...
Click to collapse
That was my original attempt but it looks like revolutionary expects the phone to be fully booted so it can set it himself in bootloader/fastboot through adb command. Since I can get into fastboot myself, If I could skip that part from revolutionary and have it do the next steps, I think I'd get a successful S-OFF. Any idea on how to do that?
Fred

wait if revolutionary wants a working adb then we will give it an adb
do this
get the recovery.img from this link (extract it)
copy it to fastboot
and try this command
fastboot boot recovery.img
if it booted ..then run revolutionary

ganeshp said:
wait if revolutionary wants a working adb then we will give it an adb
do this
get the recovery.img from this link (extract it)
copy it to fastboot
and try this command
fastboot boot recovery.img
if it booted ..then run revolutionary
Click to expand...
Click to collapse
I am getting:
downloading 'boot.img'... OKAY [ 1.706s]
booting... FAILED (remote: not allowed)
Is it because I am S-ON? I seem to remember that S-ON will not allow me to write to some partitions. I hope I'm wrong.

fdavidson said:
I am getting:
downloading 'boot.img'... OKAY [ 1.706s]
booting... FAILED (remote: not allowed)
Is it because I am S-ON? I seem to remember that S-ON will not allow me to write to some partitions. I hope I'm wrong.
Click to expand...
Click to collapse
we are not writing but we are trying to read ..
but is the command you typed is
fastboot boot recovery.img ? (coz in the output its saying downloading boot.img )

ganeshp said:
we are not writing but we are trying to read ..
but is the command you typed is
fastboot boot recovery.img ? (coz in the output its saying downloading boot.img )
Click to expand...
Click to collapse
Yes, my mistake. I sent the same command (fastboot boot recovery.img), so the problem is with reading as you said.

fdavidson said:
Yes, my mistake. I sent the same command (fastboot boot recovery.img), so the problem is with reading as you said.
Click to expand...
Click to collapse
then im out of ideas
one last try
try changing cid
fastboot oem writecid HTC__001
then
fastboot reboot-bootloader
then verify it
fastboot getvar cid
EDIT: if this worked then ..immediately flash the european unbranded 3.33 rom

[Q] No Way back - ERROR 155

cheers!
Status of my HTC:
Now it's RELOCKED
It has the original Recovery and Super CID (11111111)
BUT:
I can't flash any Stock rom! I always get the error 155! The bad thing is, I am not able to use a custom rom because, some of the Stock rom erased my flash!
but but but! the best thing is , I can't unlock the bootloader now! With the old unlock_boot.bin I will get an error and if I want to get a new Code from HTCDEV.com I also get an Error on the side, and they say, that the code is too long or not right (but I know how to copy and paste the text )
Why I want to go back to Stock?
First of all, I had an Wlan problem, which I solved but after that, i always got the Error (with Custom Roms) that the Android Keyboard (AOSP) will be closed, so I had no keyboard to work with
What can I do?
I only want to go back to my Custom Rom or the Stock ROM!!!!!

thesoldier16 said:
cheers!
Status of my HTC:
Now it's RELOCKED
It has the original Recovery and Super CID (11111111)
BUT:
I can't flash any Stock rom! I always get the error 155! The bad thing is, I am not able to use a custom rom because, some of the Stock rom erased my flash!
but but but! the best thing is , I can't unlock the bootloader now! With the old unlock_boot.bin I will get an error and if I want to get a new Code from HTCDEV.com I also get an Error on the side, and they say, that the code is too long or not right (but I know how to copy and paste the text )
Why I want to go back to Stock?
First of all, I had an Wlan problem, which I solved but after that, i always got the Error (with Custom Roms) that the Android Keyboard (AOSP) will be closed, so I had no keyboard to work with
What can I do?
I only want to go back to my Custom Rom or the Stock ROM!!!!!
Click to expand...
Click to collapse
Well, I imagine with the RUU you got back to a stock ROM... At any rate, you could try reflashing the RUU, or attempt to flash a different RUU (since you have SuperCID) and then see if your still having issues with getting a new unlock_boot.bin.
I imagine your 100% sure you know how to cut and paste? LOL I have to ask (even though you said it)... I was able to unlock my bootloader after flashing a newer RUU and didnt have this issue.
AKToronto

Well, I imagine with the RUU you got back to a stock ROM... At any rate, you could try reflashing the RUU, or attempt to flash a different RUU (since you have SuperCID) and then see if your still having issues with getting a new unlock_boot.bin.
Click to expand...
Click to collapse
Good aspect, but (now I love this word ) I tested nearly every Europe RUU and I always get the 155!
Some people said, that one of the latest RUU works with the CID :
RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
At tis moment I found this rom, I will test it tomorrow!
I imagine your 100% sure you know how to cut and paste? LOL I have to ask (even though you said it)... I was able to unlock my bootloader after flashing a newer RUU and didnt have this issue.
Click to expand...
Click to collapse
Come on man! I unlocked the bootloader Soooo this is not the problem for me!
I read in some threads, that you can't generate a new .bin file with htcdev when you have on working Rom on your phone haha funny, yeah and I am not able to put a normal stock rom on the phone

This is a long shot, but if you still have a custom recovery, try loading it up and flashing this: http://www.mediafire.com/?l35x37414jhwual
That package will set your mainver to the lowest possible number, which combined with SuperCID will allow flashing of any RUU.
If that doesn't work, you'll have to keep trying the htcdev to get your unlock code. It's possible that the website could be having some temporary problems. If all else fails, shoot an e-mail to HTC Support with screenshots of the errors on the website, the fastboot errors, a picture of your phone's HBOOT, your old unlock_code.bin and your identifier token.
Edit: Oops, just read that you had the original recovery :/ Yeah, try the absolute latest RUU and if that doesn't work, you'll need a new unlock code to have any progress.

what is your hboot version?

thesoldier16 said:
I only want to go back to my Custom Rom or the Stock ROM!!!!!
Click to expand...
Click to collapse
The unlock_code.bin file you get from HTC is generated using fingerprints on your phone. When you changed your CID it's like changing a fingerprint. All you have to do is go through the unlocking process again and get a NEW unlock_code.bin from HTC Dev.
thesoldier16 said:
I always get the error 155! The bad thing is, I am not able to use a custom rom because, some of the Stock rom erased my flash!
Click to expand...
Click to collapse
Most likley you are trying to use a RUU that have a lower hboot then yours. You can only use an RUU that has the same version or a higher hboot.
thesoldier16 said:
It has the original Recovery and Super CID (11111111)
I can't flash any Stock rom!
Click to expand...
Click to collapse
If you have the original recovery you need to flash a custom recovery first. Find TWRP and flash that.

what is your hboot version?
Click to expand...
Click to collapse
It's the version 1.14.0002
Ok these roms don'tt work for me:
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed.exe -> I tried this rom with my old CID , it was H3G__106
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
EDIT EDIT EDIT:
I got a new code from htcdev!
my problem was, I paste the text with the "info" . ok it was my fault, but now i have to try, to get my custom Recovery back!
One question, if I replace the SUPER CID with the HTC__001 one, can I flash the HTC Europe ones? (the 1.53 or the 1.78?)
Click to expand...
Click to collapse

thesoldier16 said:
It's the version 1.14.0002
Ok these roms don'tt work for me:
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed.exe -> I tried this rom with my old CID , it was H3G__106
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
EDIT EDIT EDIT:
I got a new code from htcdev!
my problem was, I paste the text with the "info" . ok it was my fault, but now i have to try, to get my custom Recovery back!
One question, if I replace the SUPER CID with the HTC__001 one, can I flash the HTC Europe ones? (the 1.53 or the 1.78?)
Click to expand...
Click to collapse
The problem is that you trying to use RUU's with a lower Hboot then what you got it will never work without a downgrade. Its has to be the same or higher then what you got.

[Q] S3 Villec2 OTA update

I've got an HTC One S [s3]. CID is HTC__622 Asia HK
I have unlocked bootloader, TWRP recovery and superSU loaded as well as Rom Manger
Tonight there is an OTA update available. So I want to use it. I downloaded it and
ran command: fastboot oem lock
and tried to run the update. It just keeps booting into my fastboot menu.
I heard that I need to install stock recovery tfor this to work but I don't know where I can find it.
I do have a reovery_signed.img file that I saved from somewhere that is 5,957 kb. Not sure if I flash that if it would give me stock recovery.
Can someone give me a direction to go. I have spent last 12 hours just reading stuff and still don't know what to do.

Htc_asia_hk Stock Recovery File
Does anyone know where I can find the stock recovery file for my One S [S3]
Its Htc_asia_hk the CID is HTC__622 ???
The beginning of the file name should look like this:
RUU_VILLEC2_U_ICS_40_HTC_ASIA_HK_

Flash stock recovery
Lock bootloader
Then run the ota update.
Sent from a HTC

Try This RUU in fastboot
http://forum.xda-developers.com/showthread.php?t=2011598

Quills88 said:
Does anyone know where I can find the stock recovery file for my One S [S3]
Its Htc_asia_hk the CID is HTC__622 ???
The beginning of the file name should look like this:
RUU_VILLEC2_U_ICS_40_HTC_ASIA_HK_
Click to expand...
Click to collapse
you dont need to flash stock recovery because RUU does ...

luxandroid said:
you dont need to flash stock recovery because RUU does ...
Click to expand...
Click to collapse
The problem is I didn't take a backup before I unlocked my bootloader and flashed twrp recovery so I don't have a stock recovery to go back to.
The RUU for HTC__044 has a different CID and won't work on my device unless I can extract just the stock recovery from the RUU without having to install it. Is that possible?

same
Quills88 said:
The problem is I didn't take a backup before I unlocked my bootloader and flashed twrp recovery so I don't have a stock recovery to go back to.
The RUU for HTC__044 has a different CID and won't work on my device unless I can extract just the stock recovery from the RUU without having to install it. Is that possible?
Click to expand...
Click to collapse
i also have htc__622 CID and i didn't make backup before fiddling with the innards.

What you have to do is
1. Flash stock recovery
2. Lock your bootloader
3. Enter fastboot and run the RUU for your phone
Your phone will then be just as it was when you bought it and then you can run the OTA. Make sure you find the right RUU for your phone. I have been searchiing for one for days and couldnt find it. Hope this helped

nez762 said:
What you have to do is
1. Flash stock recovery
2. Lock your bootloader
3. Enter fastboot and run the RUU for your phone
Your phone will then be just as it was when you bought it and then you can run the OTA. Make sure you find the right RUU for your phone. I have been searchiing for one for days and couldnt find it. Hope this helped
Click to expand...
Click to collapse
I have the same problem, so I have few questions....
Where can I find stock recovery for HTC One S c2?
How to lock bootloader?
THANK YOU!

I have a question.
I already flash 4.1.1 via OTA and use some bloody init.d script for R/W system, that doesnt work and gives me reboot after I enter into supersu app.
My question is... how can i flash 4.1.1 again (i wanna clean system, just for better feeling.) If Im using TWRP recovery? Because, ota file doesnt contain stock recovery as RUU does and I didnt find any ruu for 4.1.1 CID_032 | villec2.
sorry, for my bad english.

Privremeni said:
I have the same problem, so I have few questions....
Where can I find stock recovery for HTC One S c2?
How to lock bootloader?
THANK YOU!
Click to expand...
Click to collapse
Hi,
You can lock your bootloader with next command in fastboot:
fastboot oem lock
But question remains
Where can I find stock recovery for HTC One S c2?
Somebody cab help us?
Thanks!

Impo5sible said:
I have a question.
I already flash 4.1.1 via OTA and use some bloody init.d script for R/W system, that doesnt work and gives me reboot after I enter into supersu app.
My question is... how can i flash 4.1.1 again (i wanna clean system, just for better feeling.) If Im using TWRP recovery? Because, ota file doesnt contain stock recovery as RUU does and I didnt find any ruu for 4.1.1 CID_032 | villec2.
sorry, for my bad english.
Click to expand...
Click to collapse
You cant flash OTA trough TWRP, thats my problem also. My CID is 032 as yours. If you find RUU JB, send me the link please!

Privremeni said:
You cant flash OTA trough TWRP, thats my problem also. My CID is 032 as yours. If you find RUU JB, send me the link please!
Click to expand...
Click to collapse
Maybe a stock recovery of JB would be enough.

Hello guys,
Try this:
Step 1: relock the bootloader (start your phone in fastboot, open cmd, got to folder where are fastboot files, type "fastboot oem lock" )
Step 2: find your desired stock jb or ics online. http://filesdownload.net/showthread.php?70-HTC-One-S-(-RUU_VILLE-)-(-RUU_VILLEC2-)
Step 3: connect your phone to the pc in fastboot (make sure you have the htc drivers installed).
Step 4: run the RUU or stock file as an exe. An installation guide will follow, just follow it through.
Step 5: Now you are in stock ROM
It should work after this!
On my HTC One S [S3] , CID HTC_032 works

splanet.info has something interesting
At least ota is there for htc__622

Nez is right
nez762 said:
What you have to do is
1. Flash stock recovery
2. Lock your bootloader
3. Enter fastboot and run the RUU for your phone
Your phone will then be just as it was when you bought it and then you can run the OTA. Make sure you find the right RUU for your phone. I have been searchiing for one for days and couldnt find it. Hope this helped
Click to expand...
Click to collapse
After I locked my bootloader and tried running the OTA update I tried a few things that didn't work.
But what did work for me was when I unlocked bootloader again
And used Hasoon's Toolkit for One S
and reflashed the recovery file. I used the recovery_signed.img file (5,957 kb) that I had saved from when I was rooting it the first time and renamed it to a one word name per Hasoon's instructions, then flashed it.
Then I relocked bootloader and did a factory reset and ran the OTA update and it worked.
I was lucky that I had that recovery file saved. Still not sure where I got it from. But one thing for sure is that it was hard to find a RUU file for my CID. Hasoon's toolkit does have links to a website with a list of RUUs on it but mine wasn't on the list.
If you want me to email you my signed_recovery.img file send me a pm with your email address and I'll send it.

Privremeni said:
I have the same problem, so I have few questions....
Where can I find stock recovery for HTC One S c2?
How to lock bootloader?
THANK YOU!
Click to expand...
Click to collapse
I have attached the stock recovery just use fastboot to flash it