Bootloop other than with Stock. - HTC Sensation

So I went through S-off, superCID, installing the signed su. But when I try to flash a ROM (I've tried both Virtuous Inquisition & OnceICS). I upped CWM to 5.0.0.8 like both of these ROMs require. Is there ANY step I skipped? Possible explanations for this bootloop? the HBOOT was set back to 1.17._____ (currently restoring back to stock after another try at flashing VI).
Any help would be wonderful!

Related

Please help :(

This is my problem: I can only boot the Android Revolution HD (version number doesn't matter) on my Sensation. No other ROM, not even STOCK, will boot. Don't know why.
I tried reflashing the RUU to see if maybe THAT would boot... no luck. Now I'm stuck with HBOOT 1.17.0.0008 (or whatever; stock HBOOT), NOT revolutionary S-OFF, but I AM indeed S-OFF. Stock Recovery. CID is stock as well. And can't get the system to boot.
I'm currently trying to revert back to my previous setup. But, trying to flash the CWR 5.0.2.0 via fastboot is giving me a "not allowed" fail message. Trying to flash a radio gives me the same message.
I'm stumped... Is this a call for S-ON and warranty return?

[Q] Help Flashing ROM constant bootloop and reboot?

Please help me! I have spent the past two days trying to fix and flash a custom ROM to my phone...
First, I followed this guide to root and S-OFF. I did everything it said including SuperCID.
I then copied this ROM, Virtuous Inquisition , to my SD Card and attempted to flash it with CWM. (Yes I wiped data, cache and dalvik cache) All that happened was it went to the HTC logo, then the Virtuous logo, then reboot. I had to restore from a backup but ther was an "md5 mismatch error" so I used a guide to fix using adb.
I then moved on to ARHD 6.1.0 I flashed the kernel recommended radio (using the adb method required) and flashed the SuperWipe then the ROM. I got stuck at the bootloader but then I realised I needed 4EXT not CWM, so I got 4EXT and I still get stuck at boot (30mins +)
Any ideas?
did you get the required firmware 3.12 or 3.24 v2.1 requries3.12 and v3.0 requries 3.24 should be hboot 1.23 or 1.27
http://forum.xda-developers.com/showthread.php?t=1412618
Ahh no didnt see that thank you my hboot is 1.17 but that still doesnt explain the Virtuous errors?
the rom will not boot if your not on the current firmware. if you download the firmware on the rom page then flash the rom it should work and stop the boot loop
my phone, now restored from the backup, no longer has SuperUser and randomly reboots

[HELP] Trying to get back to stock HTC Sense

Unlocked bootleader. S-ON. Hboot 1.27.0000. Firmware 3.32.531.14. CID TMOB010.
I was originally on T-mobile's ICS 4.0.4 with Sense 3.6. I backed this up and then flashed CM9 on my phone, successfully. Battery life was poor so I decided to go back to HTC Sense. Except when I tried to restore the backup, I got stuck in a bootloop on the "Stick Together" Screen. So I downloaded the a stock ICS build from here: http://forum.xda-developers.com/showthread.php?t=1654347, flashed it, still got stuck on the "Stick Together" Screen. Then I tried to use the Revolutionary ROM, I used Superwipe, flashed the ROM, same result. However, I can still flash any CM rom with no problem, it just seems that anything that has HTC Sense gets stuck in a bootloop. Help? Should I try the RUU next?
kevinni73 said:
Unlocked bootleader. S-ON. Hboot 1.27.0000. Firmware 3.32.531.14. CID TMOB010.
I was originally on T-mobile's ICS 4.0.4 with Sense 3.6. I backed this up and then flashed CM9 on my phone, successfully. Battery life was poor so I decided to go back to HTC Sense. Except when I tried to restore the backup, I got stuck in a bootloop on the "Stick Together" Screen. So I downloaded the a stock ICS build from here: http://forum.xda-developers.com/showthread.php?t=1654347, flashed it, still got stuck on the "Stick Together" Screen. Then I tried to use the Revolutionary ROM, I used Superwipe, flashed the ROM, same result. However, I can still flash any CM rom with no problem, it just seems that anything that has HTC Sense gets stuck in a bootloop. Help? Should I try the RUU next?
Click to expand...
Click to collapse
Hi,
Because you are S-ON your phone didnt restore the boot.img from stock. boot.img contains kernel and ramdisk. Kernel for AOSP/CM builds are different from sense builds so you need to manually flash a kernel.
To do this, download a sense rom and extract the boot.img from it, then use:
fastboot flash boot boot.img
command to flash it and it should be ok. Alternatively you can S-OFF then just reflash the ROM
Thanks!
Jonny said:
Hi,
Because you are S-ON your phone didnt restore the boot.img from stock. boot.img contains kernel and ramdisk. Kernel for AOSP/CM builds are different from sense builds so you need to manually flash a kernel.
To do this, download a sense rom and extract the boot.img from it, then use:
fastboot flash boot boot.img
command to flash it and it should be ok. Alternatively you can S-OFF then just reflash the ROM
Click to expand...
Click to collapse
Two things:
1. I pressed the Thanks button.
2. I love you.
kevinni73 said:
Two things:
1. I pressed the Thanks button.
2. I love you.
Click to expand...
Click to collapse
Lol, Two things
1. I'm glad it worked for you.
2. I have a gf so sorry

[Q] HTC Sensation bootloop PLS Help

hi there,
I hope you can help me
I use on my HTC Sensation VenomS 1.4.1
Everything was fine, I tried different Kernels and stay at last at Bricked 1.4.
Today I tried again PYDX but then become a bootloop .
i have
hboot 1.27 and s-on
flashed with 4ext SmartFlash
still have access to bootloader and 4EXT.
Can anyone help me?
Try to flash newest RUU 3.33.401.6 with radio while in fastboot, then try to flash the desired rom again with kernel.
If you cant, you must do s-off, set the supercid 11111111, and then try to flash RUU (safest way to update firmware,radio...) and then try to flash the rom.
If you dont want to do that, just flash any rom with stock kernel (like ARHD 6.8) and you'll be ready to go.
Hope it helps
menfisher said:
hi there,
I hope you can help me
I use on my HTC Sensation VenomS 1.4.1
Everything was fine, I tried different Kernels and stay at last at Bricked 1.4.
Today I tried again PYDX but then become a bootloop .
i have
hboot 1.27 and s-on
flashed with 4ext SmartFlash
still have access to bootloader and 4EXT.
Can anyone help me?
Click to expand...
Click to collapse
From recovery factory reset/ wipe data +cache and then reinstall the rom. Sorted
thank you for the quick answers. i will try these tomorrow.
EDIT: I solved the problem: flashed Stock Boot.img and bricked kernel 1.4 (per pc/fastboot)
thx for your help

How to go to CM10 try, and return to stock.

So guys, I have the latest update on my phone from yesterday. but I would like to try cm10.
But if i won't like it I would like to go back to Stock.
But the problem is that I have no idea how I should do all that stuff like s-off, and SuperCID.
My only rooting and flashing experience is with samsung phones. And I am a bit scared to ruin my HTC One S S4
PS. I have read alot about all that stuff on the forums, but it still isn't clear for me
You don't need s-off, altho it's nice to have.
Just unlock and flash a recovery. Then before you flash a custom ROM, make a nandroid backup in recovery. After you played with your custom ROM, you can restore your nandroid backup and you're back.
For details on how to unlock, fastboot, backup, restore, flash, etc.. read around.
-Jobo
touch of jobo said:
You don't need s-off, altho it's nice to have.
Just unlock and flash a recovery. Then before you flash a custom ROM, make a nandroid backup in recovery. After you played with your custom ROM, you can restore your nandroid backup and you're back.
For details on how to unlock, fastboot, backup, restore, flash, etc.. read around.
-Jobo
Click to expand...
Click to collapse
Yeah but with SuperCID I read about issues like bricking when going back to stock.
You don't need S-Off to flash custom recoveries and ROMs.
If you do get S-Off, you can then change CID (back) to HTC__001
Bricking on superCID has only happened when accepting JB OTA as far as I know.
touch of jobo said:
You don't need S-Off to flash custom recoveries and ROMs.
If you do get S-Off, you can then change CID (back) to HTC__001
Bricking on superCID has only happened when accepting JB OTA as far as I know.
Click to expand...
Click to collapse
Thanks, I am now: S-OFF, ROOTED, SUPERCID and CUSTOM ROM!

Categories

Resources