Database Info

CID error after flash generic rom, stuck in boot loader

Right, had desire s from three, alpharevx'd it installed clockwork mod, flashed eng hboot. Tried to flash RUU 1.47 europe on it, and it started to work and go through process, updated radio fine, then came up with CID error. No option to do anything but exit. Now I have a desire s that will boot into Bootloader, which has now s-on'd itself and upgraded to 0.98.0002.
Only method of comms seems to be via fastboot.
Now i cant flash the h3g one cos its too low a bootloader version, and i cant upgrade to a newer version cos one don't exist. Can anyone come up with a solution please??
Cheers.

What does HBOOT screen say (in full)?
Are you still able to get into recovery? If yes, then have you tried loading a custom ROM onto the SD card and simply flashing that using the flash zip from sd card option of CWM (clock work mod)?

Unfortunately I am unable to get into recovery, only bootloader, nothing else works. Hboot is displaying a security error at the top highlighted in pink, followed by the version number as described

You should have stuck with the alpharev hboot, which does not allow itself to be overwritten by RUU installs.
Anyway, you need to:
- install hboot 0.980000 (so you can run alpharevx again and get S-OFF)
- run alpharevx and reinstall CWM at the end
- DO NOT install the eng hboot
- flash whatever rom whichever way you want. Your hboot is safe
Follow the instructions on:
http://forum.xda-developers.com/showthread.php?t=1187231

How can I run alpharevx when I can only boot into bootloader tho?

Try running it while in bootloader. Never tryed it that way, but I'm pretty sure it only needs the USB comms to be up, same as adb. Which they should be anyway in bootloader...

Have you tried to re-setup your phone by executing one of the RUU.exe?

k, as i expected, with no access to adb in bootloader mode, i am unable to do anything. Remember, i only have bootloader to work from. I don't eve3n have a recovery partition installed, it just comes back to bootloader whatever i choose, well, bootloader and fastboot anyway.

yup, tried running the ruu again but to no avail. Just get cid error. And i can't make a goldcard either cos i cant get the code. Might just send it back i think and act dumb :/

What about using the "normal" upadte procedure? Placing the PG88(whatever).zip on the root of the sdcard, and have the bootloader install it?
Of courtse with S-ON, it must be a signed version...

If all else fails s-off with xtc clip then flash custom rom
Sent from my HTC Desire S using XDA Premium App

Have you tried to use the original RUU for your phone/network? I'm not sure if it would take care of the CID error.
Any of these:
http://forum.xda-developers.com/showthread.php?t=1002506

Clivectmob said:
yup, tried running the ruu again but to no avail. Just get cid error. And i can't make a goldcard either cos i cant get the code. Might just send it back i think and act dumb :/
Click to expand...
Click to collapse
I do not expect this to work, but you said you are able to get into recovery, correct?
Well, I would try to enter fastboot mode and try to flash cwm via fastboot -> fastboot flash recovery XXXXXXXX.img
Correct (windows) drivers installed?
Edit:
lowveld said:
What about using the "normal" upadte procedure? Placing the PG88(whatever).zip on the root of the sdcard, and have the bootloader install it?
Of courtse with S-ON, it must be a signed version...
Click to expand...
Click to collapse
Good suggestion! Try this one first.

The problem with trying my original ruu for my network is that it contains the lower hboot version, when i flashed the generic ruu earlier, it actually started the update and flashed the radio part, then informed me the cid error, of course, by this time it had updated the hboot too. So now i have a desire s with an upgraded hboot so i can't flash a new one because of cid error and i can;t go back cos it reports a hboot version error. Where do i look on the system for the p88ing.zip now? can't remember now!

I haven't run a RUU in years, but I think that when you run it on a windows machine, it extracts a bunch of files to a directory. Cancel the process, find the directory, find th PG88... in the directory... You get the drift.

Clivectmob said:
The problem with trying my original ruu for my network is that it contains the lower hboot version, when i flashed the generic ruu earlier, it actually started the update and flashed the radio part, then informed me the cid error, of course, by this time it had updated the hboot too. So now i have a desire s with an upgraded hboot so i can't flash a new one because of cid error and i can;t go back cos it reports a hboot version error. Where do i look on the system for the p88ing.zip now? can't remember now!
Click to expand...
Click to collapse
It is not relevant which network you are using !!! Just try newest RUU to get control over your phone again in the first place!
Even if you don't get any network access after setup newest RUU you will definitely be abte to execute alpharevx again, flash cwm and flash any stuff you want to.

just tried flashing via fastboot, got a remote bootloader signature fail response (recovery)

Clivectmob said:
just tried flashing via fastboot, got a remote bootloader signature fail response (recovery)
Click to expand...
Click to collapse
I guess that means you tried flashing recovery via fastboot?
Then concentrate on our RUU-suggestions.

Yes, as i said, flashed via fastboot, and i already explained that i cant up/down grade via ruu method because of bootloader version. I can't think of a way out of this as it stands. The only thing that may work is doing it via the p88img method with my original 3uk rom, but i cant find it in my temp files, searched everywhere for it. I've seen it's location posted on here before now, and i've searched it to death and can't seem to find it now

I'm going to extract and upload your 3GUK-PG88*.img although I think you'll need an newer one. Just a few minutes of patience.

[Q] PG58IMG.zip can't be installed

My hboot version is 1.23, s-on. My phone can't install PG58IMG.zip, bootloader always shows no image or wrong image, i tried different zip file but non of them works. I know this has a close relationship with s on. But what can i do? I would appriciate if you could give me some advice.
Problem is my phone can't boot into system,

pmbldc said:
My hboot version is 1.23, s-on. My phone can't install PG58IMG.zip, bootloader always shows no image or wrong image, i tried different zip file but non of them works. I know this has a close relationship with s on. But what can i do? I would appriciate if you could give me some advice.
Click to expand...
Click to collapse
Hi,
What exactly are you trying to do?

malybru said:
Hi,
What exactly are you trying to do?
Click to expand...
Click to collapse
My phone can't boot into system and now s-on, so i want to do something to make it work

pmbldc said:
My phone can't boot into system and now s-on, so i want to do something to make it work
Click to expand...
Click to collapse
Hi,
Were you s-off before?
What did you flash to make you s-on?

Last night I unlocked the bootloader n been having the same problem but mind say S-on n I don't know what's next
Sent from my HTC Sensation 4G using XDA App

? im at a lost here little more detail
what did you use to unlock bootloader?
where you ever s-off?
where you rooted?
why did you flash the IMG.zip?
if you unlocked it then go to fastboot and make your CID 11111
and hopefully that will get you back on where you wanted to do?
cant give much help unless you give some details on what was your state of phoen before and what you wanted to do with it

ilostchild said:
? im at a lost here little more detail
what did you use to unlock bootloader?
where you ever s-off?
where you rooted?
why did you flash the IMG.zip?
if you unlocked it then go to fastboot and make your CID 11111
and hopefully that will get you back on where you wanted to do?
cant give much help unless you give some details on what was your state of phoen before and what you wanted to do with it
Click to expand...
Click to collapse
I have similar problem, hboot 1.20, was S-OFF, flashed orig RUU ICS,changed CID to HTC___001 than I made stupid mistake and changed back to S-ON (wanted to send my phone to the shop, problems with reception and sound quality) now only ROM that my phone accepts is LeeDroid 5.01, cant change cid to supercid via fastboot some error SMART_IO.CRD not found on sdcard. Tried to flash orig RUU (1.45, 1.29, ICS etc.) error 155 when hboot is locked and error 132 signarure error when relocked. Also tried changing android-info.txt to my cid and mid no luck, tried flashing via RUU and bootloader no luck.
Any help would be appreciated

malybru said:
Hi,
Were you s-off before?
What did you flash to make you s-on?
Click to expand...
Click to collapse
Sorry to reply so late.
Previously, my phone was eng s-off and got super cid.
After i flash ICS firmware, bootloader was then locked.
After that i did some stupid things, the bootloader turned into "locked", "security warning" and s-on. I succeeded to unlock bootloader by htcdev and get rid of "security warning", at that time i can boot into recovery normally and wipe or flash roms. But it just can't boot into system. I tried fastboot commands to flash but failed just because "it is not allowed in the remote devices".
i tried PG58IMG files but the bootloader shows no image or wrong image.
Can you give me some advice? Thank you very much

ilostchild said:
? im at a lost here little more detail
what did you use to unlock bootloader?
where you ever s-off?
where you rooted?
why did you flash the IMG.zip?
if you unlocked it then go to fastboot and make your CID 11111
and hopefully that will get you back on where you wanted to do?
cant give much help unless you give some details on what was your state of phoen before and what you wanted to do with it
Click to expand...
Click to collapse
My phone had been rooted and end s-off before things happened.
i flash IMG.zip to try to flash a rom( Somebody post that ICS rom can be flash by IMG.zip) or fix the bootloader problem. It's almost the only way to flash a rom for me
I checked the cid and it is still 11111111(Got super cid before) although bootloader is s-on.
Now the state of the bootloader is
1, unlocked
2,s-on
3,cid is 11111111
4,can boot into recovery
5,can't install PG58IMG.zip
6,fastboot command can't write anyting
7,if flash some rom, phone will be stuck at the splash screen which seems splash partition is writable
Thank you!

greenhtc982 said:
I have similar problem, hboot 1.20, was S-OFF, flashed orig RUU ICS,changed CID to HTC___001 than I made stupid mistake and changed back to S-ON (wanted to send my phone to the shop, problems with reception and sound quality) now only ROM that my phone accepts is LeeDroid 5.01, cant change cid to supercid via fastboot some error SMART_IO.CRD not found on sdcard. Tried to flash orig RUU (1.45, 1.29, ICS etc.) error 155 when hboot is locked and error 132 signarure error when relocked. Also tried changing android-info.txt to my cid and mid no luck, tried flashing via RUU and bootloader no luck.
Any help would be appreciated
Click to expand...
Click to collapse
i don't know how to do either, but during solving my problem, i found something may be useful. If you want to unlock bootloader you can try htcdev. This can't s-off but just unlock bootloader.
And since your hboot is 1.20, you can try the zip file attached by this link http://forum.xda-developers.com/showpost.php?p=20681060&postcount=22.
Because my hboot is 1.23 and isn't supported according to the above link, i didn't know whether it will help or not. You can take it into consideration
Hope you can solve your problem

ok find hboot 1.17 PD58IMG.zip, your truly not s-on, format your sdcard, then place the img in sdcard, and boot into bootloader, and you should be able run fastboot commands, you should still have custom recovery right?

ilostchild said:
ok find hboot 1.17 PD58IMG.zip, your truly not s-on, format your sdcard, then place the img in sdcard, and boot into bootloader, and you should be able run fastboot commands, you should still have custom recovery right?
Click to expand...
Click to collapse
I format the sdcard in fat32 format and place img that revert to hboot 1.17 in sdcard. Reboot into bootloader, but it shows "no image or wrong image".
I also try fastboot command but i don't know the command format. Would you give me an example please? Just a fastboot command to install img no matter s-on or s-off. Such as "fastboot flash hboot hboot.img".
My device is now s-on.

pmbldc said:
i don't know how to do either, but during solving my problem, i found something may be useful. If you want to unlock bootloader you can try htcdev. This can't s-off but just unlock bootloader.
And since your hboot is 1.20, you can try the zip file attached by this link http://forum.xda-developers.com/showpost.php?p=20681060&postcount=22.
Because my hboot is 1.23 and isn't supported according to the above link, i didn't know whether it will help or not. You can take it into consideration
Hope you can solve your problem
Click to expand...
Click to collapse
Thanks for the link, but i tried that already, I've read whole bunch of treads and tried everything i can think off but nothing seems to work. Problem is S-on and with hboot 1.20 locked or unlocked i cant flash any rom except leedroid.

greenhtc982 said:
Thanks for the link, but i tried that already, I've read whole bunch of treads and tried everything i can think off but nothing seems to work. Problem is S-on and with hboot 1.20 locked or unlocked i cant flash any rom except leedroid.
Click to expand...
Click to collapse
You mean you can flash leedroid now, don't you?
Can you boot into system？

pmbldc said:
You mean you can flash leedroid now, don't you?
Can you boot into system？
Click to expand...
Click to collapse
Yes its working, but i would like to flash other ROM's

Same Problem
Hi, I can't flash PG85IMG.zip wither except that I have S-Off??

Unlocked Unlocked bootloader S-ON, rooted, can I put custom ROM or pre-rooted ROM

Hello, I have Unlocked bootloader, S-ON and rooted telephone , can I put custom ROM, or pre-rooted RUU-ICS, Version HBOOT is 2.00.02.
I Know that must downgrade on 09.000.02 hboot-a, that I have S-off.
Can I put custom ROM, or RUU, or pre-rooted ROM, I want ICS-RUU. on phone with this caracteristics.
I really confused because S-ON, did I can do this.
Thanks advanced.

dejanxxxx said:
Hello, I have Unlocked bootloader, S-ON and rooted telephone , can I put custom ROM, or pre-rooted RUU-ICS, Version HBOOT is 2.00.02.
I Know that must downgrade on 09.000.02 hboot-a, that I have S-off.
Can I put custom ROM, or RUU, or pre-rooted ROM, I want ICS-RUU. on phone with this caracteristics.
I really confused because S-ON, did I can do this.
Thanks advanced.
Click to expand...
Click to collapse
Yes you can. You don't need to achieve S-OFF to install custom ROM. I don't recommend you to install Official RUU ICS because it has been reported many times to be buggy and laggy. If you want a better feeling of that, you should install IceDS or IceCreamSaga ROMs.

I have another problem. I wanted put RUU-ICS, but always get message ERROR 155. Every time, I dont know why. I am from Serbia, and people from HTC send me a link for RUU - ICS, and when I start with proces- eject ERROR 155-every time, after I tried another RUU-ICS again error 155, I tried 4 RUU- ics, and always error 155.
Why I get always this message, and what I do?. S-ON, bootloader-relocked, rooted phone.

i tried this and i flashed a custom rom with s-on and it just keeps booting into recovery mode

dejanxxxx said:
I have another problem. I wanted put RUU-ICS, but always get message ERROR 155. Every time, I dont know why. I am from Serbia, and people from HTC send me a link for RUU - ICS, and when I start with proces- eject ERROR 155-every time, after I tried another RUU-ICS again error 155, I tried 4 RUU- ics, and always error 155.
Why I get always this message, and what I do?. S-ON, bootloader-relocked, rooted phone.
Click to expand...
Click to collapse
Is your phone branded to any mobile carrier- by any chance?
Because if it was, to override the branded version by WWE 4.0.4
( world wide english )
you should use < gold card >
http://forum.xda-developers.com/showthread.php?t=1248095
If i remember correctly, error 155 refers to CID mismatch- wrong RUU version
But in your best interest is to double check what others say
Edit: unles something has changed,
there was only one ics ruu version for desire s
to be found on htcdev website..
How come you found four of them?

seagheart89 said:
i tried this and i flashed a custom rom with s-on and it just keeps booting into recovery mode
Click to expand...
Click to collapse
Did you flash the boot.img?
"If I were two-faced, would I be wearing this one?"
- Abraham Lincoln (1809-1865)

jugg1es said:
Did you flash the boot.img?
"If I were two-faced, would I be wearing this one?"
- Abraham Lincoln (1809-1865)
Click to expand...
Click to collapse
it didnt give me an option for boot.img it used the aroma installer

message ERROR 155 for original RUU ICS - means that you have unlocked bootlocker.
You must relock bootlocker with fastboot and start installation again - it will work.
Commant: "fastboot oem lock"
BR.

continiven said:
message ERROR 155 for original RUU ICS - means that you have unlocked bootlocker.
You must relock bootlocker with fastboot and start installation again - it will work.
Commant: "fastboot oem lock"
BR.
Click to expand...
Click to collapse
I have this problem. Because my girl friend dont want custom ROM, I install RUU-ICS. But always when start flashing,eject 155 error, bootloader first unlocked, after before process I locked again bootloader,and in HBOOT writing RELOCKED-you say this is mistake because bootloader is unlocked, it not true- on my case.
After I use HTC SYNC- register phone and recognized, everything pass easy,and ROM is installed.

seagheart89 said:
it didnt give me an option for boot.img it used the aroma installer
Click to expand...
Click to collapse
Since your device is still s-on you need flash the boot.img manually.
Extract the boot.img from the rom, boot your device into fastboot and enter
Code:
fastboot flash boot boot.img

Flashing pacman into my friend's desire s , after unlocking it, i tried every recovery, formatting every partition manually, and flashing the boot.img using fast boot, but could not get beyond the white HTC screen. I wonder why it was being so... I own a one s, and have used multiple sense and aosp based ROMs on it without a hiccup (am s-on).
Any help would be really appreciated
Thanks a lot
Sent from my One S using xda premium

syed.shoaib said:
Flashing pacman into my friend's desire s , after unlocking it, i tried every recovery, formatting every partition manually, and flashing the boot.img using fast boot, but could not get beyond the white HTC screen. I wonder why it was being so... I own a one s, and have used multiple sense and aosp based ROMs on it without a hiccup (am s-on).
Any help would be really appreciated
Thanks a lot
Sent from my One S using xda premium
Click to expand...
Click to collapse
This might be the reason http://forum.xda-developers.com/showthread.php?t=1943524
[OFF-TOPIC] Non-Sony screen panel DS users lounge
"Happiness is good health and a bad memory."
- Ingrid Bergman (1917-1982)

[Q] Phone stuck in a boot loop, plus other problems

My phone, HTC Sensation XE, is S-ON, on default ROM, and has HBOOT 1.29.000. Needless to say, my phone is not rooted.
The phone is on a boot loop ever since I last took off the battery and placed it back. I sometimes get a message that my Android system is getting upgraded, terminating with an error "System UI has stopped working" before the phone restarts itself again.
I don't know if this is a hardware issue or software.
How do I get my phone to a normal state? I don't mind rooting the phone if I need to for the purpose of installing default/custom ROM. But I don't know if this would be possible because I only have access to boot screen at present.
Please suggest me suitable solutions. Thank you

jiteshgawali said:
My phone, HTC Sensation XE, is S-ON, on default ROM, and has HBOOT 1.29.000. Needless to say, my phone is not rooted.
The phone is on a boot loop ever since I last took off the battery and placed it back. I sometimes get a message that my Android system is getting upgraded, terminating with an error "System UI has stopped working" before the phone restarts itself again.
I don't know if this is a hardware issue or software.
How do I get my phone to a normal state? I don't mind rooting the phone if I need to for the purpose of installing default/custom ROM. But I don't know if this would be possible because I only have access to boot screen at present.
Please suggest me suitable solutions. Thank you
Click to expand...
Click to collapse
if you are completely stock then i think you only option is to use a ruu.exe
http://forum.xda-developers.com/showthread.php?t=1672425
find the one which corresponds with your region and cid

rzr86 said:
if you are completely stock then i think you only option is to use a ruu.exe
http://forum.xda-developers.com/showthread.php?t=1672425
find the one which corresponds with your region and cid
Click to expand...
Click to collapse
Thanks rzr86
I looked into the thread you suggested. For my region and CID, I was not able to get the RUU from the thread. What I could get was this - an OTA zip file that matches my software version exactly (3.33.720.106) from this thread: http://forum.xda-developers.com/showthread.php?t=1764025
How do I proceed further with this zip file, since I don't have an executable RUU file?
I am hoping you can be of help -)
(The zip file contains -- META-INF, patch, system, firmware.zip, fotaBoot, version.txt)

Get s off
Install custom recovery(4ext)
and flash any ics / jelly bean custom Rom

Itsakash said:
Get s off
Install custom recovery(4ext)
and flash any ics / jelly bean custom Rom
Click to expand...
Click to collapse
I was of the same opinion itsakash, but I am not sure if I can SOFF from the bootloader screen because I have only that option available with me. Can you please refer to me a good guide on this forum where I can SOFF from bootloader?

jiteshgawali said:
I was of the same opinion itsakash, but I am not sure if I can SOFF from the bootloader screen because I have only that option available with me. Can you please refer to me a good guide on this forum where I can SOFF from bootloader?
Click to expand...
Click to collapse
Yes u can s off from bootloader
Use KGS utility or ganeshp one click root. ,s off method Check general section in sensation forum
Connect mobile to pc on bootloader screen( mobile should say fastboot USB )
And follow instruction carefully
:thumbup:

Itsakash said:
Yes u can s off from bootloader
Use KGS utility or ganeshp one click root. ,s off method Check general section in sensation forum
Connect mobile to pc on bootloader screen( mobile should say fastboot USB )
And follow instruction carefully
:thumbup:
Click to expand...
Click to collapse
When I try and do SOFF using KGS utility, it restarts my phone because my phone is not HTC dev unlocked. (My phone's motherboard was replaced some time ago, and so I cannot unlock my phone.)
ganeshp's one click root requires SOFF. I can't SOFF using his technique because temp_root.bat doesn't work in bootloader screen.
I am in trouble, and don't look like getting out of it

jiteshgawali said:
When I try and do SOFF using KGS utility, it restarts my phone because my phone is not HTC dev unlocked. (My phone's motherboard was replaced some time ago, and so I cannot unlock my phone.)
ganeshp's one click root requires SOFF. I can't SOFF using his technique because temp_root.bat doesn't work in bootloader screen.
I am in trouble, and don't look like getting out of it
Click to expand...
Click to collapse
@ganeshp's one click root doesn't require htc dev unlock (meaning no prequisite permanent root; the guide has steps for temproot).
You just need one boot.
Do this: get the boot.img of your current (stock rom) and type fastboot boot boot.img.

jiteshgawali said:
My phone, HTC Sensation XE, is S-ON, on default ROM, and has HBOOT 1.29.000. Needless to say, my phone is not rooted.
The phone is on a boot loop ever since I last took off the battery and placed it back. I sometimes get a message that my Android system is getting upgraded, terminating with an error "System UI has stopped working" before the phone restarts itself again.
I don't know if this is a hardware issue or software.
How do I get my phone to a normal state? I don't mind rooting the phone if I need to for the purpose of installing default/custom ROM. But I don't know if this would be possible because I only have access to boot screen at present.
Please suggest me suitable solutions. Thank you
Click to expand...
Click to collapse
I know its a long shot, but you should try doing a factory-reset from the bootloader, just in case it works.
Otherwise run an RUU from the bootloader.

firstly Itsakash he can't S-OFF because the device must be booted to the OS
secondly Far_SighT the command is fastboot flash boot boot.img
thirdly as raz0rf1sh suggested factory reset is a good idea and
fourthly jiteshgawali can you post your bootloader details?

It really is great to see your input guys.
@Far_SighT: I have tried doing the temp_root method, but it doesn't work for me. I could successfully run temp_root.bat just once (luckily, even in boot loop), but next when I tried doing the Juopunutbear SOFF it missed detecting my phone (again, because of the bootloop)
I don''t know where I can get a boot.img file from; for what it's worth, I could only get an OTA zip file for my region/CID from this thread: http://forum.xda-developers.com/showthread.php?t=1764025
@raz0rf1sh: I have done factory reset several times from bootloader, doesn't help friend. I don't have an RUU for my region/CID, all I have is an OTA zip file for my phone from the link I have specified right above this. Can't seem to get an RUU for firmware base 3.33, and CID HTC__038.
@rzr86: Posting all the details I am aware of currently:
PYRAMID PVT SHIP S-ON RL
HBOOT - 1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
CID - HTC__038
Software version - 3.33.720.106

rzr86 said:
firstly Itsakash he can't S-OFF because the device must be booted to the OS
secondly Far_SighT the command is fastboot flash boot boot.img
thirdly as raz0rf1sh suggested factory reset is a good idea and
fourthly jiteshgawali can you post your bootloader details?
Click to expand...
Click to collapse
Nope
Not necessary to boot into os for s off

Itsakash said:
Nope
Not necessary to boot into os for s off
Click to expand...
Click to collapse
It would help if you can tell me how to do this or direct me to any specific guide

jiteshgawali said:
I have tried doing the temp_root method, but it doesn't work for me. I could successfully run temp_root.bat just once (luckily, even in boot loop), but next when I tried doing the Juopunutbear SOFF it missed detecting my phone (again, because of the bootloop)
Click to expand...
Click to collapse
Did u connected mobile to pc from bootloader??
If yes then I'm helpless may b rzr was right
But in s off section I read somewhere that it doesn't require boot into android
Anyway do PM to Ganeshp he is good guy. I'm damn sure he will help u

jiteshgawali said:
I don''t know where I can get a boot.img file from; for what it's worth, I could only get an OTA zip file for my region/CID from this thread: http://forum.xda-developers.com/showthread.php?t=1764025
Click to expand...
Click to collapse
For stock rom go http://forum.xda-developers.com/showthread.php?t=1923629.
Get the rom and extract boot.img.
Then use the earlier command I posted.

Yes I haven't seen Indian version ruu until now ..so ruu is out of question AFAIK
Now the factory reset over boot loader should help if you have software problems but as per your replies it didn't work it seems
Tried HTC Dev unlock ? Even if the motherboard is replaced its worth a try
If htcdev unlock failed
Then try to go to recovery first ..from boot loader and if you went to recovery properly let me know
The other solution I propose is try to do change the cid ..even on locked bootloader sometimes it works
Try these commands one by one
fastboot oem writecid HTC__001
Then
fastboot reboot-bootloader
Then check cid using this command
fastboot getvar cid
If cid changed that's a good sign
Sent from my Nexus 7 using XDA Premium 4 mobile app

rzr86 said:
secondly Far_SighT the command is fastboot flash boot boot.img
Click to expand...
Click to collapse
I said fastboot boot boot.im instead of fastboot flash boot booti.img as the previous one boots the rom with with the new image but doesn't attempt to write that to the boot partition. Hence it might get him a much needed boot to s-off.

jiteshgawali said:
It really is great to see your input guys.
@Far_SighT: I have tried doing the temp_root method, but it doesn't work for me. I could successfully run temp_root.bat just once (luckily, even in boot loop), but next when I tried doing the Juopunutbear SOFF it missed detecting my phone (again, because of the bootloop)
I don''t know where I can get a boot.img file from; for what it's worth, I could only get an OTA zip file for my region/CID from this thread: http://forum.xda-developers.com/showthread.php?t=1764025
@raz0rf1sh: I have done factory reset several times from bootloader, doesn't help friend. I don't have an RUU for my region/CID, all I have is an OTA zip file for my phone from the link I have specified right above this. Can't seem to get an RUU for firmware base 3.33, and CID HTC__038.
@rzr86: Posting all the details I am aware of currently:
PYRAMID PVT SHIP S-ON RL
HBOOT - 1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
CID - HTC__038
Software version - 3.33.720.106
Click to expand...
Click to collapse
as you stated your current is 3.33.720.106 so the OTA update is unnecessary
do as ganeshp suggested
Itsakash said:
Did u connected mobile to pc from bootloader??
If yes then I'm helpless may b rzr was right
But in s off section I read somewhere that it doesn't require boot into android
Anyway do PM to Ganeshp he is good guy. I'm damn sure he will help u
Click to expand...
Click to collapse
both S-OFF guides say that stock rom is required in order to follow the S-OFF procedure

ganeshp said:
Yes I haven't seen Indian version ruu until now ..so ruu is out of question AFAIK
Now the factory reset over boot loader should help if you have software problems but as per your replies it didn't work it seems
Tried HTC Dev unlock ? Even if the motherboard is replaced its worth a try
If htcdev unlock failed
Then try to go to recovery first ..from boot loader and if you went to recovery properly let me know
The other solution I propose is try to do change the cid ..even on locked bootloader sometimes it works
Try these commands one by one
fastboot oem writecid HTC__001
Then
fastboot reboot-bootloader
Then check cid using this command
fastboot getvar cid
If cid changed that's a good sign
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for responding Ganesh. HTC Dev Unlock never worked for me post change of motherboard, but thanks for the suggestion.
I am able to browse the recovery option from bootloader properly.
And it gives me a little satisfaction to let you know that I was able to change the CID to HTC__001 following your steps. Can you suggest what I should be doing next?

jiteshgawali said:
Thanks for responding Ganesh. HTC Dev Unlock never worked for me post change of motherboard, but thanks for the suggestion.
I am able to browse the recovery option from bootloader properly.
And it gives me a little satisfaction to let you know that I was able to change the CID to HTC__001 following your steps. Can you suggest what I should be doing next?
Click to expand...
Click to collapse
Great now just download the HTC wwe ruu and install it... I'll link it up in a second.. Watch this space
Here is the link
http://htc.vi8.info/Sensation-XE/RU...0U-11.24A.3504.31-M-release-281004-signed.exe
Sent from my HTC Sensation 4G using XDA Premium 4 mobile app

[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