Hey guys, I could really use some help right now. I think my Sensation just went into a boot loop. I've never had it happen to me before, but I was using the XDA app on my phone when all of a sudden the phone went to the CoreDroid boot animation. The animation plays for about 10 seconds, freezes, and then plays again, over and over. I've tried holding down the power button, which doesn't do anything, and I also tried to boot into recovery to no avail as well. I looked up how to to fix a boot loop on an Android phone but it seems like most sites say the first step is to boot the phone into recovery (and like I said, I can't do that). Do I have to pull the battery? I don't want to do that until someone says it's the right step to take because I'm worried that could seriously screw it up.
I'm on CoreDroid 2.4 and on faux's 0.1.2 1.56 GHz NoHz kernel btw. I could really use the help because I'm leaving tonight on a vacation.
OK, update, I ended up pulling the battery, putting it back in, booting into recovery, and rebooting the phone, and it actually worked! You can sure bet that I'm doing TB to back up all my apps/data right now and I might even do a nandroid even though I have a nandroid of CoreDroid 2.3 and a couple others. And boy is boot looping a battery hog! I had 98% right before it began, and after only like 10-15 minutes of boot looping it was at 66% lol (phone got extremely hot too).
Now I'm just curious if this happened because of the kernel or if it might be due to the beta battery monitor widget that I had just installed (I'm not sure if beta apps can cause problems).
Each phone and set up is different. Sounds like a kernel issue. I have read that if your phone reacts in the way described, you should just revert to stock kernel that can be found on coredroid's fixes post.
I have gotten bootloops with one of faux's kernels, I think it was the nohtz 1.7. Now on the JRCU 1.5 with coredroid 2.4.
If you are concerned with bootloops, besides the battery pull, which I personally like to avoid, I just plug it in the usb port and do a adb reboot recovery command from your cmd window. I recommend just reverting to the stock kernel for now until you are comfortable in troubleshooting away from a comp. And remember to always have a nandroid to revert to in case of any emergencies.
Related
Syndicate 1.2
Genocide 2
This has happened twice now. Turn the phone on, it boots, plays my boot animation (helix) and then sits at the end of the animation, and never starts up. It gets really hot, cpu not battery.
Tried fixing permissions, wiping and reflashing. Only Odin works (what I did the first time)
Thinking it is genocide, as I didn't have any issues until I upped to version 2, from 1.1.
Stupid forums, should be in Epic q/a.
I am trying to install HD2 NDT GINGER ROM Version 11.0. I tried 4 times, clean installation and it is always stack on "device loading".
I tried another one rom and its the same...
I have no phone for a week now and i don't know what to do!
Anyone knows a solution for this?
Hi guys, reasonable newbie here. My Galaxy S2 has stopped displaying anything after the initial logo. In fact it seems to turn the phone off as you can make repeated attempts to boot it within a few seconds.
I started by flashing an insecure sgs2 kernel from this site with odin, then used s2root.
I then played around with rom managed but found it wouldn't boot into clockworkmod (orange exclamation mark in a white triangle every time) I booted into it manually and started trying to flash cm7 which I had downloaded earlier.
I wiped the data etc and flashed the cm7 zip (plus the google apps zip). Rebooted and got into cm7 with everything seeming fine.
Next I thought I should probably flash back to the stock version of the insecure kernel. I rebooted the phone but got distracted and didn't start it up in download mode, I looked just in time to see the normal logo (with the yellow insecure triangle) and then nothing....just blank.
I tried rebooting afew times and nothing, even after yanking the battery. Then I tried getting back into clockworkmod to reflash cm7. Nope, same thing happens.
I can still get back into download mode but nothing I flash makes the slighest difference. Tried reflashing clockworkmod, insecure and stock kernels of various versions but I'm stuck.
This is almost a new phone and I can't believe I've already killed it I would be so grateful for any tips, I've included as much info as I can think of from the top of my head but I will do my best to answer anything you gurus might need.
Again, very grateful for any help...I don't want to have to explain to Orange how I've managed to brick this after 4 days
Ok after trying over and over again to get into recovery mode, it booted into the original (3e) recovery. I've just flash cwmod to it again and have just flash cm7.
After reading some posts about cyanogenmod sometimes not flashing correctly first time, I did it twice (and it did indeed take longer the second time) and twice for google apps.
Next I'll try to get back to the stock kernel. This is where it went wrong before but i'll cross my fingers.
Edit: Well, multiple reboots didn't cause a problem but flashing the stock kernel back does kill the handset again. I'm sure this stuff is all obvious to those with experience I guess I'll have to sit with an insecure kernel and the yellow triangle for the forseeable future. On a side note, s2root doesn't see the phone connected with cm7 (yes usb debugging was turned on). I'm hoping that it is pre-rooted but I haven't tested that yet.
Hi,
I will prefix this (as there are a few people around with this problem who can get into recovery mode) with the fact that holding down Vol- on boot is not getting me to the recovery / bootloader screen.
I have a rooted HTC Desire S (rooted it nearly a year ago, so info about the hboot etc is a distant memory).
Anyhoo, I decided to have a play about with one of the ICS roms but it was a bit buggy and the camera drivers still aren't working for video so I decided to go back to Endymion V3.4 - http://forum.xda-developers.com/showthread.php?t=1310845
I did a full wipe, installed base rom, installed optional addons and then upgraded to 3.4 - booted fine into the OS so set about getting my system set up the way I like it.
I noticed that endy came with a theme installer so clicked on one of them to have a look, it asked for root, said it was installed and would need to reboot to take effect...
SO
the problem is, it now won't boot and is stuck on the white HTC boot screen.
Holding vol+/- and power buttons reset it but it just ends up back hanging on the boot screen.
Have tried pulling battery and trying again.
Holding Volume Down when powering up is no longer doing anything
So, I either need a saviour to point me in the direction of a fix.. or a kindly sould to break it to me gently when they tell me my phone has gone to the USB Dock in the sky..
Any help will be greatly appreciated.
Thanks
update:
After pulling battery again, pulling out sim and sd cards, booting with vol- held down, i got into recovery. Am going to try and flash a different rom after doing a full wipe, I'll update once it's done but any insights in the meanwhile will still be appreciated
Sorted, cleared the thing out, stuck reaper CM rom on it, rebooted and everything is peachy for now.
Thanks me
Curious if anyone knows why this might have happened?
because you didnt flash the addon zip which was released alongside endymon and then tried to use the addons,it does say on the screen do not use these unless you have installed the addons
I pulled my vortex out of storage the other day to tinker. It was rooted but fully updated stock 2.2.2
When I booted it up, it stayed on the boot animation 20+ minutes, until the battery ran out. I've tried booting it up again but it keeps bootlooping.
I figured I'd just flash a new ROM onto it, but I never put a custom recovery onto it and the only Vortex Recovery I found was this;
http://androidforums.com/getitnowmarketing/330813-all-one-recovery-thread.html
However, it says I need to do on-device commands and stuff to get it working, which obviously isn't an option.
Is there any other way you guys could think to resurrect my old Vortex? My Droid Charge is my phone now, this thing doesn't get much use anymore, but I'd still like to get it back in a usable form.
EDIT: FYI, already tried everything relevant in this thread: http://forum.xda-developers.com/showthread.php?t=1031596
If you flashed stock rom. Try hard reset.
Home+vol down / vol up+ power.
thank you! that button trick did the job!
EDIT:
well, it worked once, but the phone had been uncharged for a while so the battery died, and now i can't get the trick to work again >_<
is there a way to re-flash stock without a custom recovery?
I think i might have wrecked my P5110!
I rooted it to Cyanogen mod about 6 month ago to CM10.1.1 and that was great.
I had been using the built in updater to get the latest Cyanogen firmware without any problem. Decided to try a CM 10.2 nightly but was having big problems with it draining battery, crashing and rebooting for no apparent reason.
No problems thinks I, just unwind it to an older version of CM from the built in Cyanogen Mod Updater. I selected 10.1.3 RC2, and left it be.
Came back to it some time later to find the old logo spinning there. Figured it was still running and left it some more, and some more, and some more and it just kept spinning. I guess its knackered. I DID NOT wipe the cache and data as i was doing it from within Cyanogen so naively thought it would work okay.
Okay thinks I, go into recovery, wipe the cache. No dice. Try as i may i can NOT get ClockWorkRecovery to come up, only ODIN.
Talk about fools rush in. Simple thinks I, reinstall CWM from ODIN, go back into CWM, wipe the cache, see if that works.
flashing goes smoothly, but try as i may i can no longer get into ODIN or CWM, only into a never ending circle of Cyanogen bootup.
Any suggestions for a next step. Had the worst day at work and really shouldn't have bothered touching the damn thing!
Oh, I might well have spotted the problem
I thought I was flashing the CWM for P5110, but a closer inspection of the filename
GT-P5100_ClockworkMod-Recovery_6.0.1.0.tar
Shows quite clearly what i've done.
I'm guessing there is no coming back from this?
Vannystick said:
Oh, I might well have spotted the problem
I thought I was flashing the CWM for P5110, but a closer inspection of the filename
GT-P5100_ClockworkMod-Recovery_6.0.1.0.tar
Shows quite clearly what i've done.
I'm guessing there is no coming back from this?
Click to expand...
Click to collapse
Flash stock firmware via pc odin this will solve your issues. ....
Sent from my GT-N7100 using XDA Premium 4 mobile app
Every time you flash with ANY ROM you need to wipe data or bootloop obviously will appear.
Vannystick said:
i can no longer get into ODIN or CWM, only into a never ending circle of Cyanogen bootup.
Click to expand...
Click to collapse
Even though your recovery may be screwed up, it's strange that you can't get to the download mode... So, what exactly happens if you force reboot by holding power for several seconds, and immediately after that hold power and Volume Up together while it's powering up?
When stuck in the CM boot up, pressing and holding the power button would force a shut down, but the tab would then instantly reboot.
Holding the volume up (or down, i was desperate) until the samsung logo appeared wouldn't get me to ODIN, it would go to the CM boot screen.
If i plugged it into the charger once in the CM splash, and powered down, it would take me to the charge screen. Pulling the plug would then turn it off, without it rebooting.
Initially this wouldn't work, but perhaps because i was being impatient. All the instructions i had read say that the volume button can be released once the samsung logo pops up, perhaps i've miss read. Ultimately i found (more by accident than anything), you need to keep the volume button pressed until the second time the samsung logo pops up, then it will enter ODIN.
I managed to download a a stock rom from SamMobile, and flash it in.
It still wouldn't boot though, until i went into recovery and wiped data/cache. It also then took rather a long time to boot back up, presumably unpacking various 'stuff', had me a little concerned, so i left it alone for a few hours and came back to find the first boot welcome screen.
Lesson to be learned, always wipe the cache/data before an update, even if the previous half dozen CM updates had been fine.
I think what actually screwed things up was going from a 10.2 beta BACK to a 10.1 RC ROM.
Oh well, its working happily again, and not falling over like on the 10.2 beta. And i dont need to buy a RIFF box!