Database Info

[Q] Stuck in bootloop after 6 months of smooth sailing, can't access recovery

Hi everyone!
I've been searching and reading around trying to solve a bootloop problem on my HTC Desire S/Saga (or at least I think it is a bootloop problem) but, so far, I've had no luck.
Here's what has happened and what's going on:
1) S-off and got hboot 6.98.1002 through revolutionary
2) phone worked normally for six months and suddenly, without any changes or flashes, it rebooted and started a boot loop, ie, I can't get into any in-OS menus.
3) Choosing recovery of factory settings from hboot menu just reboots the phone and restarts the loop.
4) I've tried flashing (both through fastboot and android flasher) the eng hboot 0.98.0000 and clockworkmod recovery images but neither had any effect.
Phone was vodafone-locked, running a vanilla Android 2.3.4.
hboot menu data:
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3822.10.08.04_M
eMMC-boot
I don't have any backup data from pre-revolutionary, either :|
I'm knocking my head against the walls, hoping that the phone's only temporarily bricked... any ideas?
Thanks in advance for helping a n00b...

Doesn't sound like a hboot problem you me, but that could just be me. And I don't think flashing the stock hboot will help.
Are you sure you are flashing the ENG hboot? It's 0.98.2000. 0.98.0000 is most likely your stock hboot and can't be flashed over revolutionary hboot in most cases.
So to get back to stock stock..... You will need to run your RUU after the new hboot has been flashed.
Another option is for you to install a custom ROM and avoiding the RUU. I still suggest you flash the ENG hboot though.

Head for this thread for help
http://forum.xda-developers.com/showthread.php?t=1488672

Thanks everybody!
I've been away for the last few days so I haven't been able to test anything, but tomorrow evening I'll test both suggestions and post feedback.
Thanks again!

So, I've trying out your suggestions and...
foX2delta said:
Doesn't sound like a hboot problem you me, but that could just be me. And I don't think flashing the stock hboot will help.
Are you sure you are flashing the ENG hboot? It's 0.98.2000. 0.98.0000 is most likely your stock hboot and can't be flashed over revolutionary hboot in most cases.
So to get back to stock stock..... You will need to run your RUU after the new hboot has been flashed.
Another option is for you to install a custom ROM and avoiding the RUU. I still suggest you flash the ENG hboot though.
Click to expand...
Click to collapse
So I tried to flash the ENG hboot from this thread, using android flasher and later using this method, but adb never lists my Saga.
Fastboot lists it correctly, though. I *think* I had USB debugging on, if I recall correctly.
Using androidflasher I get a flash ok notice and then the bootloop just restarts...
Any ideas?
mOh19973 said:
Head for this thread for help
http://forum.xda-developers.com/showthread.php?t=1488672
Click to expand...
Click to collapse
Thanks moh19973, I'll leave feedback at your thread (no luck, though..)
thanks again to everybody

Opalid said:
Hi everyone!
I've been searching and reading around trying to solve a bootloop problem on my HTC Desire S/Saga (or at least I think it is a bootloop problem) but, so far, I've had no luck.
Here's what has happened and what's going on:
1) S-off and got hboot 6.98.1002 through revolutionary
2) phone worked normally for six months and suddenly, without any changes or flashes, it rebooted and started a boot loop, ie, I can't get into any in-OS menus.
3) Choosing recovery of factory settings from hboot menu just reboots the phone and restarts the loop.
4) I've tried flashing (both through fastboot and android flasher) the eng hboot 0.98.0000 and clockworkmod recovery images but neither had any effect.
Phone was vodafone-locked, running a vanilla Android 2.3.4.
hboot menu data:
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3822.10.08.04_M
eMMC-boot
I don't have any backup data from pre-revolutionary, either :|
I'm knocking my head against the walls, hoping that the phone's only temporarily bricked... any ideas?
Thanks in advance for helping a n00b...
Click to expand...
Click to collapse
Your problem sounds exactly like the one on the thread linked below.... in which case, if you just try the steps from the concerned thread, and are still unable to fix your device, it can be written off as another dead eMMC...
Just follow the instructions on this thread...maybe you will have better luck than the OP?
http://forum.xda-developers.com/showthread.php?t=1507106

So did your hboot change or not? If hboot and recovery won't flash then I have to agree with above, fried emmc :-(

yeah it could be an emmc problem, you may want to check the sticky in the development forum, if this is the real problem there is a possibility for a fix, not necessarily emmc replacement

enigmaamit said:
Your problem sounds exactly like the one on the thread linked below.... in which case, if you just try the steps from the concerned thread, and are still unable to fix your device, it can be written off as another dead eMMC...
Just follow the instructions on this thread...maybe you will have better luck than the OP?
http://forum.xda-developers.com/showthread.php?t=1507106
Click to expand...
Click to collapse
Thanks, tried everything and had the exact same results. Fried eMMC, I guess..
This is really wierd, I got a phonecall, turned the call off, the phone rebooted and entered the bootloop.
Nothing fishy or wierd, no flashing erros, just a regular phonecall from my boss. Damn :|
If only I could get the normal hboot on I could repair it under warranty
Well, thanks everybody

Try going for warranty repair, for a few guys over here at xda no one checked (or din not care) whether the phone was rooted or s-off when they went to service their phone. Maybe you'll get lucky too. Good luck!

[Q] Question about HBOOT update with CyanogenMod installed

Recently I had to have my phone JTAGed, because I wanted to update the bootloader. I failed to read about S-ON/S-OFF, and ended up with a brick. When I sent my phone in, I requested that they do the update and install CyanogenMod for me, so that I wouldn't end up with a paperweight again, because obviously I am too impatient.
So after I got my phone back, I noticed that the installed version was a nightly build. No biggie. I went about with this for a little while, until the other day I noticed that a few of my apps were crashing, and I got the idea to update the phone.
Well, already long story short, when I tried to run the update I got the assert failed getprop( ro.bootloader ) error. Someone else said this is because HBOOT isn't the correct version, and lo, it was not.
Ok, now we're to the issue. When the people who JTAGed my phone sent it back, they relocked the bootloader. Can I unlock the bootloader through traditional means, and then attempt the HBOOT update with the RUU? I also asked them to make the phone S-OFF, so hopefully when I unlock the bootloader it will show me that information.
I'm just trying to be sure that I don't brick my phone again. I wouldn't even be bothering with all of this if the OS was on a stable version, but it isn't.
Any help?

You haven't provided your bootloader details. Post them please.
Sent from my Evita

timmaaa said:
You haven't provided your bootloader details. Post them please.
Click to expand...
Click to collapse
Sorry about that.
***LOCKED***
EVITA PVT SHIP S-OFF RL (Guess that answers one question, didn't notice that before)
CID-22222222
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012,14:36:28
That's what it says in the bootloader window. Is any more information required?

Just go to htcdev and unlock your bootloader. Then run the 3.18 RUU, that will upgrade your firmware as required by CM. Then just flash TWRP recovery and you're good to go.
Sent from my Evita

Just finished running the 3.18 RUU and I now have the stock ROM running with the updated HBOOT. I also just finished installing the latest TWRP and am downloading the CM ROM now. Thank you so much for your help!

No problems.
Sent from my Evita

[Q] help, Need some clarification on flashing ROM

I am using an ATT HTC one X
unlocked rooted and supercid using All-in-one-toolkit
***TAMPERED***
***UNLOCKED***
EVITA PUT S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
Open DSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012, 18:37:14:-1
I have tried downloading ROMs through the goomanager and then flashing them via TWRP, but something always seems to go wrong. The phone gets stuck in a bootloop or just doesnt restart, the only way to get it working is run the stock RUU.
my questions are::
Will it be easier to flash ROMs with S-OFF?
Can I get rid of the ***TAMPERED*** tag?
I would really appreciate any help anyone can give, ive been at this for about a month learning very slowly...

Firstly, the tampered flag is completely normal for a modified phone. Secondly, are you flashing the boot.img via fastboot after flashing the ROM? You need to because you're s-on. This information is contained in the FAQ thread which is stickied at the top of the section you're posting in.
Sent from my Evita

See Questions 19 and 11:
http://forum.xda-developers.com/showthread.php?t=2136172
By far, the most common reason for bootloops after flashing a ROM.

[Q] What do I need to do to update to Kitkat with these?

*** LOCKED ***
M4_UL PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.18.0000
RADIO-1.17.40b.00.28
OpenDSP-v12.2.0268.0517
OS-1.06.999.01
eMMC-boot 1024MB
May 29 2013,22:23:21.0
I'm sorry, I've posted on several threads already but haven't gotten any responses yet. The details above are what appeared after I did the power + volume down thing. Can I upgrade to Kitkat with the instructions in this thread http://forum.xda-developers.com/showthread.php?t=2665746 without doing anything else?
I just got my phone 2 days ago. I'm totally clueless on HTC's workaround.

thats easy , go to htcdev , to get the token to unlock the bootloader then flash the recovery , after flashing the recovery , you can flash any rom

lateral18 said:
thats easy , go to htcdev , to get the token to unlock the bootloader then flash the recovery , after flashing the recovery , you can flash any rom
Click to expand...
Click to collapse
I'm stuck with TWRP!
Here's what I did. I unlocked the phone, updated HBOOT, installed TWRP and now I can't do anything.

Captain Cook said:
I'm stuck with TWRP!
Here's what I did. I unlocked the phone, updated HBOOT, installed TWRP and now I can't do anything.
Click to expand...
Click to collapse
i dont know , with mine : I never touch the Hboot , i cant help you there
why are you doing things without first reading or researching ,

I did follow what was here http://forum.xda-developers.com/showthread.php?t=2665746&highlight=locked
I updated to HBOOT 2.21 did everything there but now I'm stuck with boot loop.

Mods please close. Working perfect now.

[Q] Can't factory restore

Hello
Around a year ago, I began to try and get to the position where I could install a non-O2 ROM on my Sensation XE. It was the first time I had attempted such a thing. After carefully following a number of tutorials on xda-developers, I got an error that I was unable to resolve; no amount of google searches came up with a solution that worked. So I began to undo various changed that I had made up until that point and the phone has been fine.
Today I tried to factory reset the device, including wiping the SD card. Before the wipe, I backed up ONLY the documents/photos/media folders on the SD card.
Upon first try, the SD card was wiped, however the device was in a non-restored state. I instructed a restore again, and this time I got stuck in a bootloader loop, where I was unable to get out of the bootloader.
Taking the battery out/putting back in/powering on got me back into the operating system, but still with no restore taken place.
If I repeat the instruction to restore, I end up back at the bootloader. Factory Restore/Recover options in the bootloader have no effect.
Here is what the bootloader says:
Sensation XE - O2 UK
*** RELOCKED ***
*** Security Warning ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.23.3504.07_M2
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13, 2012, 17:33:34
FASTBOOT USB:
VOL UP...
VOL DOWN...
POWER...
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
---------------------
SLECTING BOOTLOADER THEN GIVES OPTIONS:
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
---------------------------------------
I have attached grabs of all the software versions I'm running.
So the phone itself works fine; I just can't get it to factory restore. I am guessing I have at some point, wiped the required data necessary for the restore to take place, but I have no idea if I am right, and if I am right, how on earth I go about fixing it!
Any help/advice would be gratefully received.

Have u tried changing the hboot maybe to hboot 1.29 cz wen u change the hboot it wipes everything
sent by v.konvict

v.konvict said:
Have u tried changing the hboot maybe to hboot 1.29 cz wen u change the hboot it wipes everything
sent by v.konvict
Click to expand...
Click to collapse
Hey. Sorry, do you mean did I try that before and that may be what has caused the issue, or do you mean I should now try and change the hboot version, as that may help?

oojafink said:
Hey. Sorry, do you mean did I try that before and that may be what has caused the issue, or do you mean I should now try and change the hboot version, as that may help?
Click to expand...
Click to collapse
Am saying you could try it now maybe it could help
sent by v.konvict

According to this post http://forum.xda-developers.com/showpost.php?p=27019794&postcount=2 I need to S-OFF before updating HBOOT, and it's the S-OFF part that I was unable to do last time because during the process I got the error that stopped me from progressing any further.

oojafink said:
According to this post http://forum.xda-developers.com/showpost.php?p=27019794&postcount=2 I need to S-OFF before updating HBOOT, and it's the S-OFF part that I was unable to do last time because during the process I got the error that stopped me from progressing any further.
Click to expand...
Click to collapse
i suggest to run a ruu.exe
or unlock the bootloader again and flash any rom from recovery(since you are on S-ON use 4ext recovery)
by the way don't search on sensation xl forums
they are completely different devices

Well I only had to unlocked the bootloader again, and the device successfully performed a Factory Restore
I have no intention of carrying on, so this thread can be closed/forgotten.
Thanks for the help!