[HELP] Trying to get back to stock HTC Sense

kevinni73

New member
Sep 19, 2011
2
0
0
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?
 

Jonny

Retired Forum Moderator
Jul 22, 2011
9,285
9,606
263
Birmingham
jonathonfitch.com
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?
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
 
  • Like
Reactions: kevinni73

kevinni73

New member
Sep 19, 2011
2
0
0
Thanks!

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
Two things:
1. I pressed the Thanks button.
2. I love you.