[SOLVED][Q] BootLoop on almost every boot!? - HTC One S

Okay, so the other day I flashed CM10.2, everything was working fine until I turned off the phone, but after about the 3rd time. I rebooted and the bootanimation started to skip and stuff, then the phone rebooted before bootup
It did it again about 3 more times, then it started to boot. When it reached the lockscreen I tried to unlock, but phone was frozen! Then it rebooted and kept doing this!
I read somewhere that if you keep letting it do so it would correct itself
I did so, no correction. Finally I tried to boot into the bootloader to boot cwm. The phone started to boot into bootloader then it rebooted. This time the rom was acting fine But just to test, I rebooted and the process started all over...
So I thought it was a issue with the nightly, but also had this issue with beanstalk rom. What is this and how do I fix!!
I'm rooted with S-ON, this is how my bootloader looks:
*** TAMPERED ***
*** UNLOCKED ***
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.13.50.05.31
OpenDSP-v31.1.0.45.0815
eMMC-boot

Hi,
I am fighting with this for 3 days. I have S-OFF, hboot 2.15.0000. Everytime I flash ROM with android 4.3 it boots for first time fine, but rebooting or flashing updates brings same problem you're having. Boot frozen or multiple reboots on bootanimation. Try flashing some ROM with android 4.2.2. This works for me oldo I am sad I cannot have night builds.
My bootloader says same information as yours, except tampered which dissapeared after flashing stock RUU.

skiller21 said:
Hi,
I am fighting with this for 3 days. I have S-OFF, hboot 2.15.0000. Everytime I flash ROM with android 4.3 it boots for first time fine, but rebooting or flashing updates brings same problem you're having. Boot frozen or multiple reboots on bootanimation. Try flashing some ROM with android 4.2.2. This works for me oldo I am sad I cannot have night builds.
My bootloader says same information as yours, except tampered which dissapeared after flashing stock RUU.
Click to expand...
Click to collapse
Tried flashing cm10.1, same issue Its not a 4.3 issue...

Did you guys flash boot.IMG?
Sent from my HTC One S using xda app-developers app

abracadabra11 said:
Did you guys flash boot.IMG?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
yeah, fastbooting the boot.img solved everything. I still get issue where bootanimation sometimes doesn't fully boot and the phone reboots, but thats a issue that everyone has with S-on and S-off.

Related

[Q] Stuck in bootloop can not escape

I hadn't flashed a new rom in awhile so I thought I'd give it a go and start with the pac-man halo or w.e
went through the steps and ended up in a bootloop. Figured why I was in a bootloop and it was because I had S-ON which I thought was off.
So then I tried facepalm s-off method and used steps 1 though 6 and now I'm stuck in a bootloop again.
reflashed a recovery tried reboot into it and it goes into a bootloop
Any ideas?
No Rom installed
S-ON RL
Hboot - 1.09.0000
radio - 0.16.31501S.16_2
Try updating your hboot version with a RUU. That's what fixed my bootloop when installing the PAC Man rom.
xbeast45 said:
Try updating your hboot version with a RUU. That's what fixed my bootloop when installing the PAC Man rom.
Click to expand...
Click to collapse
Where would I find a direct download for an RUU?
This is the one I used to update my hboot.
http://forum.xda-developers.com/showthread.php?t=1941402
AustinAce said:
I hadn't flashed a new rom in awhile so I thought I'd give it a go and start with the pac-man halo or w.e
went through the steps and ended up in a bootloop. Figured why I was in a bootloop and it was because I had S-ON which I thought was off.
So then I tried facepalm s-off method and used steps 1 though 6 and now I'm stuck in a bootloop again.
reflashed a recovery tried reboot into it and it goes into a bootloop
Any ideas?
No Rom installed
S-ON RL
Hboot - 1.09.0000
radio - 0.16.31501S.16_2
Click to expand...
Click to collapse
Go here and follow these instructions... Make sure you use the correct firmware..
http://forum.xda-developers.com/showthread.php?p=42544590
Sent from my One S using xda premium

[Q] Phone won't boot into recovery. Goes Black!

I have an HTC One X from AT&T. I recently got root and started playing. I flashed Clean Rom 6.5 using clockwordmod and it went well. Used it about a week and got bored. (Later I saw that TWRP was needed for that.) I decided I wanted to try a Cyanogen Mod but realized later after research that my phone received the OTA update that only allows Sense ROMS on my phone. After I flashed Cyanogen 10 with clockwordmod the touch screen wouldn't work. I tried to get back to Clean Rom 6.5 and tied to flash TWRP as my bootloader. It went bad from there. Now I cannot get to recovery. It appeas I don't have a bootloader flashed. I used FastbootFlasher_V2.4 and flashed TWRP. It said it was sent. Still won't go to recovery. I downloaded the RUU.exe and tried that process. It failed too. After I tried to restore the RUU it said to reboot. I did and then the cyanogen logo came on and hung. I went to fastboot and typed in fastboot erase cache. No help. Here's my screen info if that helps:
****TAMPERD****
****UNLOCKED****
EVITA PVT SHIP S-ON RL
HBOOT- 2.14.0000
RADIO- 0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Vov 26 2012, 18:37:14:-1
Is it bricked??
marcadams67 said:
I have an HTC One X from AT&T. I recently got root and started playing. I flashed Clean Rom 6.5 using clockwordmod and it went well. Used it about a week and got bored. (Later I saw that TWRP was needed for that.) I decided I wanted to try a Cyanogen Mod but realized later after research that my phone received the OTA update that only allows Sense ROMS on my phone. After I flashed Cyanogen 10 with clockwordmod the touch screen wouldn't work. I tried to get back to Clean Rom 6.5 and tied to flash TWRP as my bootloader. It went bad from there. Now I cannot get to recovery. It appeas I don't have a bootloader flashed. I used FastbootFlasher_V2.4 and flashed TWRP. It said it was sent. Still won't go to recovery. I downloaded the RUU.exe and tried that process. It failed too. After I tried to restore the RUU it said to reboot. I did and then the cyanogen logo came on and hung. I went to fastboot and typed in fastboot erase cache. No help. Here's my screen info if that helps:
****TAMPERD****
****UNLOCKED****
EVITA PVT SHIP S-ON RL
HBOOT- 2.14.0000
RADIO- 0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Vov 26 2012, 18:37:14:-1
Is it bricked??
Click to expand...
Click to collapse
Slow up.... What if anything can you access on phone? Can you access hboot
Power on + volume down
Being your s-on it's near impossible to kill the bootloader
Sent from my HTC One XL using xda premium
You've given us your bootloader info so I doubt you've killed the bootloader. If it turns on it's far from bricked. Did you mean you can't get into recovery? Have you tried flashing a recovery to fix it?
Sent from my Evita
timmaaa said:
You've given us your bootloader info so I doubt you've killed the bootloader. If it turns on it's far from bricked. Did you mean you can't get into recovery? Have you tried flashing a recovery to fix it?
Sent from my Evita
Click to expand...
Click to collapse
Didn't make much sense and he hasn't been back maybe he relaxed and got it running lol
Sent from my HTC One XL using xda premium
Either that or he ran over it with his truck and claimed insurance
Sent from my Evita
Sorry I got it working again.
timmaaa said:
Either that or he ran over it with his truck and claimed insurance
Sent from my Evita
Click to expand...
Click to collapse
I got it back later that night. Sorry I didn't respond, had a panic attack and did some reading. You guys rock!
Thanks for the reply guys.
I got it later that evening. I'm sure I'll need help in the future. Thanks again,

[Q] After Venom 3.1.4 OTA update my Sensation wont boot

Hi,
I have a Sensation, been using VEnom 3.1.2 for a while and decided to OTA to 3.1.3 and that worked like a charm..
Then I found 3.1.4 and tried OTA that one.
ANd it installed and when it was rebooting for the first time it got stuck in a loop.
Only see HTC logo, (not Quietly brilliant) and for a few secs the screen is lit.
then turns black and after a few it turns back on, HTC logo and then blac etc.
Tried to go back to 3.1.2 and 3.1.3 and then the new 5.0.0. Tried the CM 10.1 and 10.2 ROM too.
Tried formating everything in recovery 4eXT is the one I am using.
tried formating the SD-Card, reinstalling ROM and nothing works.
You guys have and suggestions?
my phone:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
eMMC-boot
Going mental here.
Enable smart flash from recovery
Or
Flash boot.img by adb
Or
Get s off and flash rom
Itsakash said:
Enable smart flash from recovery
Or
Flash boot.img by adb
Or
Get s off and flash rom
Click to expand...
Click to collapse
You are amazing!
Did the boot.img option and ta-da!! Thank you soo soo much
zajko said:
You are amazing!
Did the boot.img option and ta-da!! Thank you soo soo much
Click to expand...
Click to collapse
Would you consider s-offing your Sensation? You will not have to worry about this anymore if you do.

HELP! Nothing works when installing rom!

I followed the instructions to the letter for Maximus 10.0 ROM. My bootloader shows:
TAMPERED
UNLOCKED
VLE PVT SHIP S-OFF RL
CID-T-MOB010
HBOOT-2.16.0000
RADIO-1.20.50.06.16
OpenDSP-v33.1.0.45.1128
eMMC-boot
I even tried going back to stock with relocking and flashing 3 of the TMOUS RUUs with no luck.
Each time the phone boots it loops or gets stuck on a splash screen. Oddly, even after I try to return to stock I get the splash screen from the Maximus 10.0 rom.
Is there a way to completely ERASE everything on this phone and start from scratch using fastboot and adb?
You can wipe everything from recovery, firmware installation also wipes everything.
If you want more help please try to be more specific. For example what happened with maximus or RUUs? Did you get any errors or bootloops? Do you still want to install maximus or want to turn back to stock? etc.
Sent from my HTC One S
ka_55 said:
You can wipe everything from recovery, firmware installation also wipes everything.
If you want more help please try to be more specific. For example what happened with maximus or RUUs? Did you get any errors or bootloops? Do you still want to install maximus or want to turn back to stock? etc.
Sent from my HTC One S
Click to expand...
Click to collapse
Maximus loads up to a black screen with just the time, battery, and signal icons, then eventually goes into a bootloop. The RUUs did the same thing. Blows me away what is going on now.
I would like ANY rom to work.
My CID is TOM010 or whatever the TMOUS is. Does that matter?
Even tried to install an older unknown jb rom and it still boot loops!!!
there must be a way to make this device complete NEW STOCK!!!!! my god!
f10a said:
Even tried to install an older unknown jb rom and it still boot loops!!!
there must be a way to make this device complete NEW STOCK!!!!! my god!
Click to expand...
Click to collapse
First of all did u try flashing the boot.img that is in the Rom zip file??
If yes did u try superCid or s-off ????
f10a said:
Maximus loads up to a black screen with just the time, battery, and signal icons, then eventually goes into a bootloop. The RUUs did the same thing. Blows me away what is going on now.
I would like ANY rom to work.
My CID is TOM010 or whatever the TMOUS is. Does that matter?
Click to expand...
Click to collapse
I'm in the same boat... maximus messed up my partitions, leaving me with only 48mb of sdcard space... I managed to reclaim that, but now Maximus wont boot EVEN after doing a complete wipe, downgrading to hboot 2.15, and re-installing maximus with his step by step process.
I dunno what to do now
f10a said:
I followed the instructions to the letter for Maximus 10.0 ROM. My bootloader shows:
TAMPERED
UNLOCKED
VLE PVT SHIP S-OFF RL
CID-T-MOB010
HBOOT-2.16.0000
RADIO-1.20.50.06.16
OpenDSP-v33.1.0.45.1128
eMMC-boot
I even tried going back to stock with relocking and flashing 3 of the TMOUS RUUs with no luck.
Each time the phone boots it loops or gets stuck on a splash screen. Oddly, even after I try to return to stock I get the splash screen from the Maximus 10.0 rom.
Is there a way to completely ERASE everything on this phone and start from scratch using fastboot and adb?
Click to expand...
Click to collapse
I JUST did this... I RELOCKED, went back to S-ON, and put my CID back to T-MOB010, and then RUU'd my device. Now I'm able to USE my phone. The only problem at the moment is that my radio doesn't work. I'm gonna see how to fix that and follow up with that later.
Hope that helps.
EDIT: Radio works, it just needed to be manually connected to my network

One X restarts shortly after booting, please help!

Alright, so here is my problem. I have my One X rooted correctly, and I had CleanROM 7.0R rom installed. It worked for a few days, but then it started to randomly restart when opening anything. I thought a rom change can fix this so I installed MagioROM. Same error, and now I sometimes don't have time to even type in my pin code. And when it restarts, it just keeps restarting over and over and over again until I turn it off. Before it restarts after booting up, the screen brightness goes down for a moment, like when entering power saver mode.
What i tried? Several reinstalls of the rom, once a full wipe and then adb sideloading magiorom again, installing a custom kernel (ElementalX sense 5). Still doing the exact same thing. Any ideas? Thanks in advance.
Does it reboot like this when you're in recovery or the bootloader? What are your bootloader details?
Sent from my Evita
timmaaa said:
Does it reboot like this when you're in recovery or the bootloader? What are your bootloader details?
Sent from my Evita
Click to expand...
Click to collapse
It doesn't restart in bootloader, neither in cwm or twrp. My bootloader shows it's unlocked and tampered. Phone is S-ON.
others, might be important or not
HBOOT-2.14.0000
RADIO-0.23a.32.09.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
OK, does this problem occur on older Sense ROMs or aosp ROMs? Part of the problem could be that your firmware is outdated, you need to update it to run Sense 5 ROMs properly, but in order to do that you'll need s-off first.
Sent from my Evita

Categories

Resources