I'm currently on slimics 4.2, though every other rom I've tried also exhibited the same behaviour...
I can get into download mode easily using 3BC. It is not as easy to get into recovery, but it does happen every other try or so.
From recovery, if I do a reboot, it starts the phone allright. If I reboot the phone from the power menu in the phone, it restarts the phone allright.
However,
If I power down the phone, it does not power down completely. It powers down, and if I have the power cable in, it shows a battery loading animation without movement, and I am not able to power up the phone, without first going to recovery mode.
If the power cable is not in, it still acts as it is and shows the battery loading animation. Then it seems like it knows that the power cable is not in, and restarts the procedure resulting in a battery icon boot loop.
This is fixed either by going into recovery and rebooting system or by flashing a new kernel in download mode and booting from there.
Has anyone experienced something similar?
This is how it looks: http://youtu.be/TvjUUL852Us
I'm inclined to think it is a hardware problem.
I got the same issue. But it only appear if I flash cm7.2 or higher.
If my phone is powered off, only the battery icon appear (without charging or movement of the status bar).
It doesn't load up the Battery. After starting the phone the battery loading up very fast.
Maybe it's a software issue because our devices never will get an official update to ics or jb.
Sent from my GT-I9000 using Tapatalk 2
These are widely known issues. Check out my post here.
http://forum.xda-developers.com/showthread.php?t=1811961
Searched but not found a similar problem that has a solution. I ran my battery dead by mistake and now all it does is restart after a few seconds on semaphore logo if unplugged, or keep looping buffering circle/battery charge symbol when plugged in. 3BC takes it to download mode but it again restarts after a few seconds...no way near enough to flash anything. Any Ideas?
I was running latest makay rom (2.8.0) and Semaphore 2,9,15s......this seems pretty fatal to me but if someone knows better ill be a very happy man.
Thanks.
Keep it plugged in for a few hours and see if this fixes it.
I have quite the same issue with my SGS i9000. Im running on slim bean 4.1.2 i think and semaphore (quessing the same as above)
So the battery got drained to zero. I charged the battery to full capacity while my phone was turned off. It did this okay and charged battery to 100%. Then i booted my phone only to find out it to start looping in boot. (Start screen to semaphore and then restarts.)
i removed the battery for about an hour, and rebooted the phone but it didn't help at all.
Can't get into recovery (vol up + home + power), though it did go into download mode.
snapper.fishes Keep it plugged in for a few hours and see if this fixes it.
Click to expand...
Click to collapse
As i plugged my phone in in to charger it shows as the battery would be empty,but it doesn't begin to charge it.
Ill be happy to answer if i forgot to mention something important according this matter.
If you can go into download mode but not recovery mode, there is only one thing that you can do - flash an odin rom.
Sent from my Nexus 4 using Tapatalk 2
snapper.fishes said:
If you can go into download mode but not recovery mode, there is only one thing that you can do - flash an odin rom.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
ill try that.
Thanks for the quick answer. Now lets see if that helps..
Tried keeping it plugged in for a few hours but with no joy, odin still recognises the device for the tiny bit of time that the phone it stays on, seen a few comments suggesting it's a battery problem. Have ordered a new one and will see what happens then. The old one was made in Sept 2010 and rarely been turned off since,so i guess its probably to be expected. Will post back when i get the new battery for other peoples future reference.
jwpil said:
Tried keeping it plugged in for a few hours but with no joy, odin still recognises the device for the tiny bit of time that the phone it stays on, seen a few comments suggesting it's a battery problem. Have ordered a new one and will see what happens then. The old one was made in Sept 2010 and rarely been turned off since,so i guess its probably to be expected. Will post back when i get the new battery for other peoples future reference.
Click to expand...
Click to collapse
Hello
I have a Samsung Galaxy S exactly with this problem.
It has cyanogen mod installed.
When i try to turn it on, it shows the default Samsung logo, and then the cyanogen mod screen, it blinks, and displays the cyanogen mod again. After that it reboots and returns do displaying the Samsung logo. ... Inifinite loop!
When i try to plug it in to charge, it shows the battery logo, and a "waiting" or "starting" to charge, blinks, reboots, starts recharging, another loop.
Both loops only stops by removing the battery.
Exactly as this thread describes.
Also, i cannot enter recovery mode: volume up + home + power, but it can enter download mode: volume down + home + power.
Is there any way of getting it to boot other than deleting everything on the phone, as i assume reflashing it would do?
banid0 said:
Hello
I have a Samsung Galaxy S exactly with this problem.
It has cyanogen mod installed.
When i try to turn it on, it shows the default Samsung logo, and then the cyanogen mod screen, it blinks, and displays the cyanogen mod again. After that it reboots and returns do displaying the Samsung logo. ... Inifinite loop!
When i try to plug it in to charge, it shows the battery logo, and a "waiting" or "starting" to charge, blinks, reboots, starts recharging, another loop.
Both loops only stops by removing the battery.
Exactly as this thread describes.
Also, i cannot enter recovery mode: volume up + home + power, but it can enter download mode: volume down + home + power.
Is there any way of getting it to boot other than deleting everything on the phone, as i assume reflashing it would do?
Click to expand...
Click to collapse
I also can't enter recovery, doesn't have time to boot that far. If it is like mine then you will be unable to stay in download mode for long enough to flash anything...if you can get to download and it not reboot again, you have some hope. You could possibly flash a different kernel via odin, semaphore possibly, and see if that helps, but if not you would have to flash back to stock and re-root etc (data will be lost). I will report back when i get a new battery and see if that is the issue (Friday Hopefully), I feel it might be battery issue because my ROM had been running perfectly for days and it started when i let battery completely discharge.
banid0 said:
Hello
I have a Samsung Galaxy S exactly with this problem.
It has cyanogen mod installed.
When i try to turn it on, it shows the default Samsung logo, and then the cyanogen mod screen, it blinks, and displays the cyanogen mod again. After that it reboots and returns do displaying the Samsung logo. ... Inifinite loop!
When i try to plug it in to charge, it shows the battery logo, and a "waiting" or "starting" to charge, blinks, reboots, starts recharging, another loop.
Both loops only stops by removing the battery.
Exactly as this thread describes.
Also, i cannot enter recovery mode: volume up + home + power, but it can enter download mode: volume down + home + power.
Is there any way of getting it to boot other than deleting everything on the phone, as i assume reflashing it would do?
Click to expand...
Click to collapse
Flashing will only delete app data. All your photos and music files will remain.
Just an update... Battery hasn't arrived yet due to snow here. But just by chance I left the phone bootlooping without charger in and it randomly decided to not bootloop. Was able to flash stock with odin root, upgrade to CM 10.1 and restore my nandroid. Oh well.
Sent from my GT-I9000 using xda premium
jwpil said:
Searched but not found a similar problem that has a solution. I ran my battery dead by mistake and now all it does is restart after a few seconds on semaphore logo if unplugged, or keep looping buffering circle/battery charge symbol when plugged in. 3BC takes it to download mode but it again restarts after a few seconds...no way near enough to flash anything. Any Ideas?
I was running latest makay rom (2.8.0) and Semaphore 2,9,15s......this seems pretty fatal to me but if someone knows better ill be a very happy man.
Thanks.
Click to expand...
Click to collapse
[SOLVED]
I recovered my Galaxy Y(s5360) by flashing another kernel from recovery mode in those few seconds for which recovery mode was starting...
I tried that but got soft brick, not enough time to flash kernel image. My power button is now broken so I feel that it may have been stuck in the on position. Think it's stuck in off now. Oh well
Sent from my GT-I9000 using xda premium
Hi I have the same problem on my Asus tf101 the battery ran out during upgrade and now it is looping on Asus title screen pls help me
Hello, I'll start with writing all the things i did:
I flashed JenaMIUI v1.29 succesfully then i waited about 30 minutes at the boot image, then I got the battery out, tried again another 10 minutes stuck at the boot image. After that I reflashed JenaMIUI v1.29 wiped data etc...same thing, stuck at boot image, I got the battery out and back in, one time just after turning on the phone ( before the boot image appear). Then I could'nt start the phone in recovery or normal or download mode. After some tries and leaving the phone for a few minutes i managed to start it normally( but still stuck at boot image) , so I wasn't able to get to recovery, one time I managed to power it up with the charger on, it showed a circle 1/4 full and then went to boot image. Now I'm not able to power up the phone at all, I tried getting the battery out and back in several times. When I connect the charger to the phone with no battery in it, it shows a black screen for a second then nothing. I am not able to start it in recovery or any other way. Is this a battery problem or sth like the mother board ? The bin counter is set to 0 (using triange away), can I take it to service ?
One more thing, when i managed to start it normally and was stuck at boot image i pressed all keys(vol up,down,home,power) and went into a black screen saying something with ARM ..idk.
Is this a battery problem or a brick ? What can I do ?
EDIT: I think the problem was caused by pulling out the battery right after powering on the phone, solution...disconnect battery from phone leave it for 10 minutes, hold power button for 30seconds then turn on the phone in download mode and flash stock...that worked for me
Are you stuck on Miui bootanimation?
Now i can't get it to turn on...i tried replacing the battery , but when i press power nothing happens
Edit: I'm pretty sure is battery problems because I pulled out and put in the battery very fast ...
no, never pull out battery while the device is on splash screen. Wait till boot animation at least. In that moment the kernel is being loaded. This is also causing the recovery bug. People get boot-loop and reset their phone by pulling out the battery. It's actually true, it's the same as if you turn off your PC by unplugging it from power cord.
So if the kernel has some problems because i pulled the battery out while it was loading...can I take it to service ? Can they see what ROM I have installed regardless of my 0 bin counter ? Will they give me a new phone or sth ? Will a lie like...I tried to change the grey case with the orange case and the battery fell out while I reseted the phone work ?
EDIT: I managed to "repair" my phone ! I used a method I found on the internet. I hold the power button for 30 seconds ( while the battery was disconnected) and then put the battery in and I managed to get it in download mode and flash stock rom, now everything works great)
Sorry for the inconvenience, i wrongly packed the rom
RageFoxtrot said:
Sorry for the inconvenience, i wrongly packed the rom
Click to expand...
Click to collapse
No problem...i knew the risks I was taking...and as long as everything turned out fine, It's all good.
I was talking on the phone on my way home. The battery lasted all the ride home, that's good, but it died on me just as I got home. So I plug it to the charger and it turns on like normal on the charging screen with the horizontal color battery animation, and the orange charging light pulses. Then it changes to the other battery animation, the all white vertical one, and the orange light stays solid, like normal. The issue is, the phone doesn't even last a second charging, the orange light turns off, and the phone reboots, only to repeat what I just wrote... So I tried to turn it on as soon as the second battery animation comes up, then the orange light goes on solid for less than a second, and it manages to turn on. It goes through the splash screen and the boot animation, no problem. But as the boot anim fades and its supposed to finish booting and start charging again, neither does it finish booting nor does it start charging... The orange light starts to pulse twice quickly, as if telling me it's not charging, and then shuts down... The phone is rooted but running stock everything, AT&T 4.4.2... Any ideas???? After some attempts, I'm able to get it as far as into recovery, but I really don't know what to try as this definitely doesn't seem like a Rom error or anything that flashing or RUU would fix????
Hi,
so I charged my Note (running some cm10 stable release) over night, using my ipad charger (5.2V, 2.4A) as I sometimes do, and the next morning the phone was stuck at the unlock pattern screen but didn't react to any inputs.
After rebooting the initial n7000 screen and the CM loading animation appeared. The phone never booted, though and reverted back to the n7000 screen and stuck there. Tried to reinsert the battery (also tried with a different one) but the phone only got to the n7000 screen the first 2 times and got stuck there. Now the phone doesn't even do that. Just black screen and no sign of life. Tried removing the SD and also getting into recovery and download mode to no luck.
Any ideas what else I could try?
Thanks!