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?
Related
I have seeARMS v0.4 running stable. When i try and install the generation x theme via Clockworkmod zip method the phone will restart and i get force close messages for 10+ apps. it then restarts and gets caught in a boot loop. (goes to load screen and vibrates twice)
I have restored back to previous stable state. Can anyone help me determine whats going on? I've trying reading as many posts as i can but not seeing anyone else getting a similar error.
Thanks
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.
Hey xda.
Recently I flashed my GS with this rom (http://forum.xda-developers.com/showthread.php?t=1449156&page=), but just in a older version(pre-alpha) and after probably a month of use I began to experienced at lot og bugs and suddenly crashes in apps and programs. I decided to do a reboot,battery pull or wipe cache to see if that clould do it, but nothing help. On the contrary, my phone would not start. The Galaxy S logo showed u, but when the miui xiaomi.com logo showed it bootlooped. Several reboots did not work, so i decided to mount usb from recovery and download the newest version of the rom and then try to flash. I did not wipe, but i worked just fine and i thought i had my phone back, but after little over a day of use the screen began to flicker and blink, and no programs nor apps worked, just crashed. I flashed again again but nothing worked, and now i'm stuck with the same problem as before. bootloop..
So have anyone experienced the same or does anyone have a solution for this problem?
Its fixed. It seems that it was stuck and just needed that extra kick with another ROM. Not really sure what the hell happened but its working fine now.
Please delete post.
Yesterday I plugged the HOS into my laptop and it started to act a little weird. It wouldn't show the SDcard but it allowed me to open it. I copied a new ROM to it and installed it. Since I did this, the phone will not work. Once it boots, it just freezes and reboots when I try and do anything. The nand allows me to boot and scroll through the home screens, but if I try and do anything else it freezes and reboots. I can't install any other ROM that's not sense base like AOKP or MIUI as they just boot loop. I can get to recovery and the boot loader no problem.
Update: I can boot a stock nand and get into the app drawer. But, once I click on an app or pull down the notification bar it freezes.
Update 2: Was able to get the cyan alpha to install after a good 5 minutes of bootloops and it runs perfect. WTF is going on here?? haha
Can anyone give me any suggestions to try? Thanks for any help that you can provide me.
Hi guys,
Really sorry to ask about this but tearing my hair out!
I have a P6200 UK model. I installed CWM v6.0.1.0 and it worked fine. The intention was to install Galaxy ROM HD (build #06), so I downloaded it, put it on my SD card, and installed from CWM recovery. The install got stuck on "Flashing boot" - so after around 15 mins I reset it.
It went into a boot loop on the initial Samsung logo. Luckily I'd previously re-flashed stock HC with Odin (to cure a dead Wifi problem caused by, I think, an errant install of Busybox) so I did this again, rebooted, and the system came up, text started scrolling up the screen, followed by a red error message (see picture) and a reboot. I was then once again stuck on the initial Samsung Tab 7.0 Plus log. I repeated the process and it didn't even get past the Samsung logo.
So I thought I'd try the newly released ICS Rom (GT-P6200_ATO_P6200XXLQ1_P6200OXALQ1) - this seemed to install OK, then half booted, did some text type installation stuff with the blue Android, then rebooted again, finally getting stuck on the Samsung logo with blue pulsating behind it. It never gets any further than that.
I tried flashing HC back - same result as earlier. I can also reflash CWM and sometimes it works, sometimes it doesn't. It seems I've run out of options.
So - question is - where (if anywhere!) can I go from here?
Help greatly appreciated, many thanks!
have you tried a system wipe in cwm? if not do a system wipe and reflash HC using odin.. same thing happen to me 2 days ago.. I think something is up with HD rom