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] PLEASE HELP! random rebooting about every 5 min

random rebooting after flashing CM9 nightly roms. seems to be some kind of bug every time i start an application or turn on mobile data it cuases a reboot. i have flashed all of the following roms in an attempt to fix the problem:
PkMn ROM 4.1 Charmander
OrDroid V6.0.0
and the latest official cyanogenmod nightly
i did a restore to an ics lee droid rom i previously backed up before
and it seemed to run without a problem but after that i re flashed PkMn ROM for the sensation and now it performs a hot reboot instead. if anyone could help it would be greatly apprieciated as the problem seems to worsen after every reboot.
some times it would just go into a bootloop.

bryancruzdr said:
random rebooting after flashing CM9 nightly roms. seems to be some kind of bug every time i start an application or turn on mobile data it cuases a reboot. i have flashed all of the following roms in an attempt to fix the problem:
PkMn ROM 4.1 Charmander
OrDroid V6.0.0
and the latest official cyanogenmod nightly
i did a restore to an ics lee droid rom i previously backed up before
and it seemed to run without a problem but after that i re flashed PkMn ROM for the sensation and now it performs a hot reboot instead. if anyone could help it would be greatly apprieciated as the problem seems to worsen after every reboot.
some times it would just go into a bootloop.
Click to expand...
Click to collapse
I think some partition is still corrupted.. I recommend you to do a wipe from recovery rather than scripts (if using 4ext then wipe/format ->>format all partitions except sdcard) and then flash another rom Again
If that didn't solved the issue RUU is the next thing.. If you are soff and supercid then get any ics RUU and run it.. It completely formats through phone and takes everything to stock.. But still retains soff.. So you revert back to normal once you do a ruu run(remember ruu run should be done with device in fastboot)
Sent from my pyramid.. Through blazing fast sonic waves

Thank You so much!
i will try this, but which RUU do you recommend i run?

bryancruzdr said:
Thank You so much!
i will try this, but which RUU do you recommend i run?
Click to expand...
Click to collapse
RUU is just to clean the partitions.. So just get any.. If you want one get the Europe umbranded one(latest)
Check in pyramid shipped rom collections thread in sensation Android Development section
Sent from my pyramid.. Through blazing fast sonic waves

Before you look into a partition problem, which is a pain to fix, check to make sure the battery is securely seated in the phone.
The batteries can become loose over time. Not very loose, but just enough to break electrical contact. And if the electrical contact is broken and restored quickly, a reboot is likely.
Open the phone and see if the battery wiggled. See if you can create the reboot problem by jiggling the battery. If you can, there are a few things to try to make the battery tighter.

Skipjacks said:
Before you look into a partition problem, which is a pain to fix, check to make sure the battery is securely seated in the phone.
The batteries can become loose over time. Not very loose, but just enough to break electrical contact. And if the electrical contact is broken and restored quickly, a reboot is likely.
Open the phone and see if the battery wiggled. See if you can create the reboot problem by jiggling the battery. If you can, there are a few things to try to make the battery tighter.
Click to expand...
Click to collapse
Thanks for your suggestion. i saw a post on this yesturday, and this doesnt seem to be my issue, althought i tried the trick that is mentioned on the post, about putting a business card to make it tighter, and it deffinitely made it very tight, but the issue remained. thanks for your help though
such a friendly and helpful community

bryancruzdr said:
random rebooting after flashing CM9 nightly roms. seems to be some kind of bug every time i start an application or turn on mobile data it cuases a reboot. i have flashed all of the following roms in an attempt to fix the problem:
PkMn ROM 4.1 Charmander
OrDroid V6.0.0
and the latest official cyanogenmod nightly
i did a restore to an ics lee droid rom i previously backed up before
and it seemed to run without a problem but after that i re flashed PkMn ROM for the sensation and now it performs a hot reboot instead. if anyone could help it would be greatly apprieciated as the problem seems to worsen after every reboot.
some times it would just go into a bootloop.
Click to expand...
Click to collapse
I always use super wipe when flashing new roms
Sent from my HTC Sensation using xda premium

OreoBoyVa said:
I always use super wipe when flashing new roms
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Formatting all partitions is better than SuperWipe. It will ensure everything is completely cleaned out.

ganeshp said:
RUU is just to clean the partitions.. So just get any.. If you want one get the Europe umbranded one(latest)
Check in pyramid shipped rom collections thread in sensation Android Development section
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
While Running RUU i get "Error [156] Image Error" ive downloaded atleast 4 different ics ruu's and get the same error. perhaps this is the initial problem?

bryancruzdr said:
While Running RUU i get "Error [156] Image Error" ive downloaded atleast 4 different ics ruu's and get the same error. perhaps this is the initial problem?
Click to expand...
Click to collapse
no no are you SOFF ?
if you are not SOFF but has unlocked bootloader..then relock it before running RUU
(fastboot oem lock)
then run the RUU..with phone connected in bootloader

i am s-off
if it helps heres what it says on the bootloader:
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
i put it on fastboot and connect it to my computer when running RUU. am i missing anything?

bryancruzdr said:
i am s-off
if it helps heres what it says on the bootloader:
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
i put it on fastboot and connect it to my computer when running RUU. am i missing anything?
Click to expand...
Click to collapse
ok we do it different way then
first extract the rom.zip from any ICS RUU (choose one )
here is the guide to extract the rom.zip
http://www.htcsensationforum.com/htc-sensation-rooting/how-to-extract-rom-zip-from-ruu/
then keep the rom.zip in adb folder
keep the phone in fastboot
and connect it to pc (mobile reads "fastboot usb")
now type these commands one by one
1.fastboot erase cache
2.fastboot oem rebootRUU
3.fastboot flash zip rom.zip
4.fastboot reboot
if worked fine otherwise
im particularly interested in the complete output of the third command
so use PASTEBIN to paste the output and then repost the url with the pasted output

ganeshp said:
no no are you SOFF ?
if you are not SOFF but has unlocked bootloader..then relock it before running RUU
(fastboot oem lock)
then run the RUU..with phone connected in bootloader
Click to expand...
Click to collapse
Check point 4 of my RUU guide. You can link all such questions there. Detailed explanation & methods.
I'm just suggesting because you gave him a very short explanation.
EDIT: Sorry, I probably didn't see that this is solved.
ganeshp said:
keep the phone in fastboot
and connect it to pc (mobile reads "fastboot usb")
now type these commands one by one
1.fastboot erase cache
2.fastboot oem rebootRUU
3.fastboot flash zip rom.zip
4.fastboot reboot
Click to expand...
Click to collapse
Some questions. The method from above is the same one used for flashing engineering bootloader after JB S Off
So, what exactly is this RUU mode? And does it bypass CID and fw version checks?
Also, what are the requirements for this mode to work (i.e. S-Off, unlocked bootloader)?
What are the benefits of using this over renaming rom.zip to PG58IMG.zip and flashing?
Thanks a lot for this. It will surely come in handy sometime & will definitely go into my guide.

kgs1992 said:
Some questions. The method from above is the same one used for flashing engineering bootloader after JB S Off
So, what exactly is this RUU mode? And does it bypass CID and fw version checks?
Also, what are the requirements for this mode to work (i.e. S-Off, unlocked bootloader)?
What are the benefits of using this over renaming rom.zip to PG58IMG.zip and flashing?
Thanks a lot for this. It will surely come in handy sometime & will definitely go into my guide.
Click to expand...
Click to collapse
its the same way as flashing via PG58IMG way
to bluntly say the PG58IMG flashing ..internally does the flashing the same way I've put it
RUU mode is the lowest level(visible) mode where flashing of bootloader,firmware,radio and even ROM is possible but the file format should be of PG58IMG zip
so simply put any PG58IMG.zip file which is not being parsed by bootloader properly can be manually flashed the above way
the same requirements that apply for PG58IMG.zip file applies over here too
i.e SOFF (irrespective of type of bootloader)
or unlocked bootloader with SON ...(remember in this case as only recovery,boot,data,system partitions are opened only those partitions can be flashed )

ganeshp said:
its the same way as flashing via PG58IMG way
to bluntly say the PG58IMG flashing ..internally does the flashing the same way I've put it
RUU mode is the lowest level(visible) mode where flashing of bootloader,firmware,radio and even ROM is possible but the file format should be of PG58IMG zip
so simply put any PG58IMG.zip file which is not being parsed by bootloader properly can be manually flashed the above way
the same requirements that apply for PG58IMG.zip file applies over here too
i.e SOFF (irrespective of type of bootloader)
or unlocked bootloader with SON ...(remember in this case as only recovery,boot,data,system partitions are opened only those partitions can be flashed )
Click to expand...
Click to collapse
Thanks a lot Ganesh! Very useful info. So you mean that in this mode CID check is bypassed. That's nice.

kgs1992 said:
Thanks a lot Ganesh! Very useful info. So you mean that in this mode CID check is bypassed. That's nice.
Click to expand...
Click to collapse
no please don't get me wrong
at the end the zip we are flashing requires android-info.txt too (PG58IMG.zip has it too) which has cid and mid to it
the cid check is bypassed only when you are SOFF or has unlocked bootloader (for unlocked bootloader ..we still require cid signed radio,hboot (firmware) to update them via this method ..this is required as they are still secured [SON])
the above way of flashing gives you much more detail of whats happening when on command prompt..where we can identify the problem ..when flashing RUU..precisely

ganeshp said:
no please don't get me wrong
at the end the zip we are flashing requires android-info.txt too (PG58IMG.zip has it too) which has cid and mid to it
the cid check is bypassed only when you are SOFF or has unlocked bootloader (for unlocked bootloader ..we still require cid signed radio,hboot (firmware) to update them via this method ..this is required as they are still secured [SON])
the above way of flashing gives you much more detail of whats happening when on command prompt..where we can identify the problem ..when flashing RUU..precisely
Click to expand...
Click to collapse
Thanks for the clarifications. I will add it to the guide because this is really a nice method.

Help - stuck, hopefully didn't brick my phone

Hi all,
I hope one of you masterminds is able to help me out.
I tried to root my sensation without s-off with hecdev.com (using One_X_All-In-One_Kit_v1.0) and then tried to install cm9 from one the links here via revcovery with CWM 5.8.0.9.
But then I was stuck with the loading animation...
I cannot run Android now, so I cannot flash a stock RUU.
I can enter bootloader, which seems to be unlocked, here's the info:
"Unlocked"
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012,17:33:34
I was on the latest official ROM (ICS, via OTA) before trying that.
I have not succeeded in flashing a ROM anymore.
Do I need to get S-Off first?
Or is HBOOT to new? Do I have to revert? How?
I tried older HBOOT, but it wouldn'T do anything after PArsing
Please help, any hint is appreciated =/

PS: I would be more than happy to have a stock rom again...as mentioned, cannot use a ruu.exe file, as it seems fastboot usb ist not recognizable by ruu.exe
Edit: After the 4th or 5th try, RUU recognized the phone when in fastboot usb mode, but update fdailed, cwm saif "security fail" ... sigh, seems I really blew it this time

the_bmg said:
PS: I would be more than happy to have a stock rom again...as mentioned, cannot use a ruu.exe file, as it seems fastboot usb ist not recognizable by ruu.exe
Edit: After the 4th or 5th try, RUU recognized the phone when in fastboot usb mode, but update fdailed, cwm saif "security fail" ... sigh, seems I really blew it this time
Click to expand...
Click to collapse
Hi,
Start again using THIS GUIDE

Flash the boot.img from your ROM through fastboot.
Extra step 1 from this guide: http://forum.xda-developers.com/showthread.php?p=25587345
Be sure to use the boot.img from your ROM.
Then make a clean install of the ROM again.
Also, read that thread for the sake of understanding what you're doing.
There is NO need yet to flash an RUU.

Latest OTA comes with hboot 1.29 which is locked.
You might not be in the latest one, perhaps start with an RUU with.the latest fw (3.33).
Sent from my HTC Sensation using xda premium

thanks malybru & kgs1992 - tried that, and the 4ext touch recoery said both superwipe and the rom installed correctly.
but when rebooting the white screen with the green htc logo appears right away and nothing more happens...any idea? I may have messed up the kernel before, but when asked by ext4 recovery whether to flash a kernel, tried both custom and stock, none changed the problem with booting up

@Raven2k: Manually installing boot.img with fastbok seemed to help, at least I come over the white screen, am stuck with the beatsaudio logo right now - thanks so far =)

the_bmg said:
thanks malybru & kgs1992 - tried that, and the 4ext touch recoery said both superwipe and the rom installed correctly.
but when rebooting the white screen with the green htc logo appears right away and nothing more happens...any idea? I may have messed up the kernel before, but when asked by ext4 recovery whether to flash a kernel, tried both custom and stock, none changed the problem with booting up
Click to expand...
Click to collapse
Can you try this again
Flash boot.img again as kgs explained
Then flash the rom again... Don't do any wipe
Sent from my pyramid.. Through blazing fast sonic waves

Amazing, guys! Thanks for your help, my phone is back :good::fingers-crossed::laugh:

the_bmg said:
Amazing, guys! Thanks for your help, my phone is back :good::fingers-crossed::laugh:
Click to expand...
Click to collapse
good
and for thanks ..there is a button for that

Please Help!

Ok,
So I've used roms on my hd2 and one x, so I thought this would be simple on a friends sensation, oh how wrong was I.
I have unlocked the sensation via htcdev, installed clockworkmod and installed pyramids jellybean rom.
Now I have all sorts of issues, the rom boots then drops somehow straight to clockworkmod. I can't mount the sd card within clockworkmod to try a different rom and the phone is now useless, doh.
How can I fix this please guys?

Did you update the firmware? Are you s off or s on? If your s on you must flash boot image. Download 4 ext recovery, enable smart flash in 4ext. This way you can flash boot image. Please read flashing roms with s on. Also for that rom the firmware must also be upgraded. Let me link you to the guide to flashing roms with s on. This will help http://forum.xda-developers.com/showthread.php?t=1631861
Someone more knowledgeable than myself can give you step by step instructions to get you out of this pinch. But in the mean time read the link I posted about flashing with s on. It will help in the future. Best wishes not to worry I'm sure you can fix this.
Sent from my HTC Sensation using xda premium

daz1uk said:
Ok,
So I've used roms on my hd2 and one x, so I thought this would be simple on a friends sensation, oh how wrong was I.
I have unlocked the sensation via htcdev, installed clockworkmod and installed pyramids jellybean rom.
Now I have all sorts of issues, the rom boots then drops somehow straight to clockworkmod. I can't mount the sd card within clockworkmod to try a different rom and the phone is now useless, doh.
How can I fix this please guys?
Click to expand...
Click to collapse
HTC Dev doesn't really unlock it. It only partially unlocks it.
It doesn't s-off the device so you don't have access to the system partition, meaning you can't properly install a custom ROM without a few extra steps. And I don't think you can do it at all with clockworkmod. You need 4EXT Recovery which can flash a ROM with s-on. There's a few extra steps to doing it but it works.
You also have to make sure you have the correct firmware. So if the device was previously on a Gingerbread ROM and you didn't upgrade firmware, it won't work.
Now, the part where it boots then drops back into recovery is weird.
Tell us exactly what steps you did so we can better determine where something went flukely.
I'm CERTAIN it's fixable though.

realsis said:
Did you update the firmware? Are you s off or s on? If your s on you must flash boot image. Download 4 ext recovery, enable smart flash in 4ext. This way you can flash boot image. Please read flashing roms with s on. Also for that rom the firmware must also be upgraded. Let me link you to the guide to flashing roms with s on. This will help http://forum.xda-developers.com/showthread.php?t=1631861
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Thanks for responding.
I've got S-OFF and flashed boot.img with adb.
Will 4EXT allow me to mount the sd card?

Yes it should
Also some roms require 4ext it's a super easy touch recovery to use. You can download from here or the playstore.
Sent from my HTC Sensation using xda premium

Skipjacks said:
HTC Dev doesn't really unlock it. It only partially unlocks it.
It doesn't s-off the device so you don't have access to the system partition, meaning you can't properly install a custom ROM without a few extra steps. And I don't think you can do it at all with clockworkmod. You need 4EXT Recovery which can flash a ROM with s-on. There's a few extra steps to doing it but it works.
You also have to make sure you have the correct firmware. So if the device was previously on a Gingerbread ROM and you didn't upgrade firmware, it won't work.
Now, the part where it boots then drops back into recovery is weird.
Tell us exactly what steps you did so we can better determine where something went flukely.
I'm CERTAIN it's fixable though.
Click to expand...
Click to collapse
Yeah I'm certain it's fixable too , just not sure how, lol. I'll give 4EXT a shot. I have no idea how or why it drops straight to clockworkmod either, I would expect it to reboot to clockworkmod if anything, but it just kind of switches from the rom straight to it, very odd.
If you could point me to a firmware I might need I would be very grateful.

It is universal 3.33 let me get link also 3.32 will work on most ics roms but 3.33 is the newest I'm running jelly bean and use 3.33
http://forum.xda-developers.com/showthread.php?t=1459767
Sent from my HTC Sensation using xda premium

daz1uk said:
Thanks for responding.
I've got S-OFF and flashed boot.img with adb.
Will 4EXT allow me to mount the sd card?
Click to expand...
Click to collapse
If you are s-off you shouldn't have to flash boot.img separately. It will do all that with the ROM flash.
Maybe that's what's screwy. Though a borked up ROM still shouldn't affect SD card mounting in recovery...that is really weird. Do you have a card reader that you can use to check the card out in your computer? I'm wondering if somehow you screwed up the card when flashing the ROM. Maybe it wont' mount because the card isn't formatted properly anymore. Stuff like that has happened before.

daz1uk said:
Yeah I'm certain it's fixable too , just not sure how, lol. I'll give 4EXT a shot. I have no idea how or why it drops straight to clockworkmod either, I would expect it to reboot to clockworkmod if anything, but it just kind of switches from the rom straight to it, very odd.
If you could point me to a firmware I might need I would be very grateful.
Click to expand...
Click to collapse
Hi,
What does your bootloader say?
hboot etc.

Yes if your s off you simply flash from recovery without boot img. But do update your firmware.
Sent from my HTC Sensation using xda premium

malybru said:
Hi,
What does your bootloader say?
hboot etc.
Click to expand...
Click to collapse
Bootloader says:
S-ON

Ok, so I think I need to update the firmware?
I've installed EXT4, still cant mount sd, so can't revert to another rom.

daz1uk said:
Ok, so I think I need to update the firmware?
I've installed EXT4, still cant mount sd, so can't revert to another rom.
Click to expand...
Click to collapse
Hi,
If you are s-on,you cannot update your firmware.
What is your hboot?

malybru said:
Hi,
If you are s-on,you cannot update your firmware.
What is your hboot?
Click to expand...
Click to collapse
hboot 1.18.0000
Unlocked
S-ON
As far as I was aware S-ON just prevented the boot.img from being written via recovery, which can be done with adb. So the only reasons for these issues must be firmware version right?

daz1uk said:
hboot 1.18.0000
Unlocked
S-ON
Click to expand...
Click to collapse
Hi,
It is a pity you went to HTC to unlock your phone.
I wonder if you can still s-off using revolutionary.
You are going to need to run a RUU,and hopefully get a working phone again.
Try and find a RUU HERE that matches your area and carrier.

daz1uk said:
hboot 1.18.0000
Unlocked
S-ON
As far as I was aware S-ON just prevented the boot.img from being written via recovery, which can be done with adb. So the only reasons for these issues must be firmware version right?
Click to expand...
Click to collapse
Yup. If you have the 1.18 hboot you have Gingerbread firmware, which won't support Jellybean or ICS.
The good news is that you can flash a gingerbread rom and get the phone back to a working state right away if you need to get the phone back to the owner.
The RUU to restore is pretty simple. Then Revolutionary s-off proceedure is also extremely painless.
Reverting back to stock and starting over to s-off shouldn't take more than 15 minutes if you do it right. Then flashing the ICS/GB firmware (3.32 or 3.33) takes 3 minutes. Then the new rom takes 3 more minutes.
Just make sure you RUU to gingerbread and not to ICS. The ICS Hboots are harder to s-off. It's worth adding the extra step to flash the ICS/JB firmware later.

This is driving me nuts, tried 2 ruu's, both failed, if it was my phone it would be out the window!

daz1uk said:
This is driving me nuts, tried 2 ruu's, both failed, if it was my phone it would be out the window!
Click to expand...
Click to collapse
Hi,
Are you Sensation,or Sensation XE?

daz1uk said:
This is driving me nuts, tried 2 ruu's, both failed, if it was my phone it would be out the window!
Click to expand...
Click to collapse
Doh, my fault forgot to re-lock it, update is installing as I type, phew!
Sent from my HTC One X using Tapatalk 2

[Q] Desperate - Need Help

Two years ago I had this phone and I wanted to flash. I did. I don't remember all the details of it, but I do know that someone on here helped me flash it and it ended up with a European(?) flash on it and I remember he helped me do something with the radio in order that it would take the flash. I also remember that the reason for the flash was so that TMO wouldn't charge me for tethering. In any case, here's the current situation. I sold the phone and the person came and said they were having issues... so I was trying to restore it to a TMOUS ROM. Eventually, I bricked it, and got the qualcom download mode issue. I found the thread on that on how to fix it, and I did. Now the phone boots to the recovery screen and does nothing else. I am unable to flash ANY of TMO's RUU's, some of the PG58IMG.zip files that I've been able to find all fail... very frustrating.
I followed another thread that talked about how to unlock the bootloader, which involved copying the Identifier Token and sending it in to HTC. I received the response, and ran the command and was successful in unlocking it. When the device rebooted, it even showed the Tmobile animated logo. When I go back into the boot loader, it now reads:
My bootloader screen reads as follows:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT - 1.27.0000
eMMC-boot
JAN 13 2012.17:33:34
Software info shows:
Android Version: 4.0.3
HTC Sense Version: 3.6
Software number: Blitz_2.0.0
Kernel: 3.0.16-gda3fdfc
[email protected]#1
Baseband version: 11.76A3504300U_11.24A.3504.31_M
Build Number 3.33.401.106 CL391535 release-keys
Browser version: WebKit/534.30
At this point, I would try any flash, any rom, any thing to get this phone working for the guy again. I am skittish about flashing anything from this point so I don't mess up and have to start all over somewhere. Can I flash something working from this point? Can I flash a TMO RUU from here?
I have the RUU_Pyramid_TMOUS_1.27.531.2_RADIO_10.42.9007.00P_10.11.9007.15_M_release_192098_signed.exe as well as several others. Id' rather put this phone onto something stock from tmo but will do a custom as long as the phone is restored to working order.
I won't say I'm a newb... but having been away from flashing for a while, I could really use some step by steps to get going again.
The computer I am using to flash with is a Windows XP machine with all the HTC drivers working etc.
**** UPDATE ****
The phone now boots up as it did when this all started. After I did the token thing and got the bin file from HTC, I applied it and the result was the boot loader info above. It got past the tmobile animated logo and actually into the phone starting up as new including applying all the settings I want. Awesome that the phone now functions like a phone again, but I would still like to flash an official TMO Rom to it to restore it back to like out of the box condition. Any help is appreciated.

read this thread
http://forum.xda-developers.com/showthread.php?t=1672425

rzr86 said:
read this thread
http://forum.xda-developers.com/showthread.php?t=1672425
Click to expand...
Click to collapse
I actually have read that... like 6 times to make sure I'm not missing anything. I do remember having to flash the radio back when I did my original flashing, and I think that process is preventing me from using any of the RUU's that I find. Are there any posts/files/resources that will help me flash the radio back to its default, so that I can then flash the RUU?
Also, I am S-ON already, but ANY RUU that I try to flash fails. Do I need to go to S-OFF and then RUU, then back to S-ON?

sc.lord said:
I actually have read that... like 6 times to make sure I'm not missing anything. I do remember having to flash the radio back when I did my original flashing, and I think that process is preventing me from using any of the RUU's that I find. Are there any posts/files/resources that will help me flash the radio back to its default, so that I can then flash the RUU?
Also, I am S-ON already, but ANY RUU that I try to flash fails. Do I need to go to S-OFF and then RUU, then back to S-ON?
Click to expand...
Click to collapse
no you don't need S-OFF
post your cid

rzr86 said:
no you don't need S-OFF
post your cid
Click to expand...
Click to collapse
CID is 11111111
I think I have it licked now.
Used the universal firmware and the viper 5.2.1 flash and it loaded just fine. Never got S-OFF on it, but the viper flash so far is working excellent.

sc.lord said:
CID is 11111111
I think I have it licked now.
Used the universal firmware and the viper 5.2.1 flash and it loaded just fine. Never got S-OFF on it, but the viper flash so far is working excellent.
Click to expand...
Click to collapse
how do you have supercid with S-ON?
also how did you flashed the universal firmware while on S-ON?
those two things can be done only on S-OFF

rzr86 said:
how do you have supercid with S-ON?
also how did you flashed the universal firmware while on S-ON?
those two things can be done only on S-OFF
Click to expand...
Click to collapse
Wish I could tell you.... hence the reason for the original help request.
I can tell you that I hit softbrick on it once and had to unbrick in linux.
Then I got the LOCKED with Security Warning. Then I got the unlock bin file from HTC Dev, used that and got back to UNLOCKED, with no security warning. Then I tried Rumunner without any success at all, stayed S-ON.
in any case, after trying just about everything I could think of, I found the viper post, saw that you said you don't need S-OFF to flash new rom... so i gave it a shot. Updated EXT, flashed the firmware, then the rom and it all went very smoothly. Phone's been working fine since. <shrug>