Since not so long ago I've experienced the following:
If I leave the phone two have low battery like 10% when it dies it enters a boot loop I cannot stop and I just can only plug it in and wait while it bootloops without being able to stop it and a long time later (20/30 min) it will finally boot up, last time it had 30% battery when it finally booted up.
What could it be? It may have been the last update? Has anybody experienced this?
If you did a major firmware upgrade without a factory reset, do a factory reset now.
Otherwise clear the system cache.
It it persists, factory reset.
If it still continues it maybe hardware. It could be corrupted firmware but trying to reflash may end up causing it to brick if it acts up during the reflash. Consider your options carefully at this point especially if under warranty or insured.
I have the same thing. The phone just starts to vibrate indicating a startup, then after a few seconds it vibrates again, and continues in this loop. The screen doesn't display anything.
I'm having the same thing right now, I tried wiping the cache from bootloader and charging the phone to 100%, but it doesn't seem to be fixed
Maybe on an unlocked bootloader it doesn't work? Something related to offline charging?
IronHulk27 said:
I'm having the same thing right now, I tried wiping the cache from bootloader and charging the phone to 100%, but it doesn't seem to be fixed
Click to expand...
Click to collapse
I have not had it happen lately the other day I had 5% battery and it worked fine.
I think it might be an unsupported charger?
Related
So, last night I was out and about - just having a good time. Noticed that the battery on my GSM Galaxy Nexus was getting low. Went "Meh, wasn't the first time it's died." It got to 1% battery power and shut-off, like it normally does. Me being who I am, I turned it back on to see just how much more juice I could get out of it.
Phone booted up alright. Finished the boot animation, and then a couple seconds later turned off.. not a big deal. I get home, plug it in, and the charge screens cycle..... and then they cycle again. And again. And again. Basically just looping. I turn the phone ON, finishes the boot animation and... turns off again riight away? Goes back to the charge screen loop.
I'm not talking about the regular charge screen. After the battery gets 'filled' twice, it completely restarts. Black screen for 2 or so seconds, and then it goes through the charge animations as it would if you had just pluggied it in. I CAN get into bootloader, but that's about it. I'm just curious.. has anyone seen this before? Or know what my problem might be?
I'm unable to turn USB Debugging on in the system settings, so I'm at a loss as to how I can fix this issue WITHOUT bringing it into Bell.
Try going into recovery and wiping cache and dalvik. If that doesn't work reflash your rom
My phone is completely stock (I reflashed it to to the stock yakju? I believe it was when I found out Samsung had screwed people off the google update path.. so I can't get into recovery mode. It just shows the broken android. It's all been re-locked, and since then, my laptop has died. So I no longer have the ABD/Samsung drivers setup. Which was a pain to get going the first time..
i.vt3c.d0hc said:
My phone is completely stock (I reflashed it to to the stock yakju? I believe it was when I found out Samsung had screwed people off the google update path.. so I can't get into recovery mode. It just shows the broken android. It's all been re-locked, and since then, my laptop has died. So I no longer have the ABD/Samsung drivers setup. Which was a pain to get going the first time..
Click to expand...
Click to collapse
The "Broken android" IS stock recovery. I believe that when you push Volume Up seeing that image it takes you to the stock recovery menu. But you can always reflash Yakju or any other ROM through fastboot mode (see the tutorials here on the forum).
i.vt3c.d0hc said:
[snip]
I get home, plug it in, and the charge screens cycle..... and then they cycle again. And again. And again. Basically just looping. I turn the phone ON, finishes the boot animation and... turns off again riight away? Goes back to the charge screen loop.
Click to expand...
Click to collapse
Turn it off. Leave it charging for a few hours before turning it on.
i.vt3c.d0hc said:
[snip] I'm unable to turn USB Debugging on in the system settings, so I'm at a loss as to how I can fix this issue WITHOUT bringing it into Bell.
Click to expand...
Click to collapse
You do not need to have USB debugging enabled to use fastboot.
i.vt3c.d0hc said:
My phone is completely stock (I reflashed it to to the stock yakju? I believe it was when I found out Samsung had screwed people off the google update path.. so I can't get into recovery mode. It just shows the broken android. It's all been re-locked, and since then, my laptop has died. So I no longer have the ABD/Samsung drivers setup. Which was a pain to get going the first time..
Click to expand...
Click to collapse
It doesn't take long at all to install the drivers. Look for a thread with "universal" in the title. I think it is in GN General. Once you do install the fastboot driver, download the fastboot.exe file and reflash the stock ROM.
Diger36 said:
The "Broken android" IS stock recovery. I believe that when you push Volume Up seeing that image it takes you to the stock recovery menu. But you can always reflash Yakju or any other ROM through fastboot mode (see the tutorials here on the forum).
Click to expand...
Click to collapse
It's volume up and the power button.
Sent from my Galaxy Nexus using Tapatalk
The problem I have is that the charge animation doesn't change... i.e. It'll constantly refill the battery and all, but it always starts from the bottom (While when a phone is say... half charged, the little battery is half filled and the animation continues.
I'm not sure it's even charging at all.
Update time!
Got it into the stock recovery. Wiped the cache and all of my data. Rebooted, and.... it turns on! No longer reboots on regular startup. That's the good news. So at least it's somewhat useable now..
Now for the BAD news.
-It still does that retarded charging bootloop that doesn't seem to get me anywhere
-....When it's on. Like, running, it doesn't charge. Nadda. Zip. Zilch. Computer, wall charger, android dock, nothing. It just won't charge when it's on. However when I got it to power on, it said I had 14% remaining - which means it was likely charging inside the Bootloader, as I had it on that for quite a bit.
I think this just went from a software to a hardware issue. Thoughts?
i.vt3c.d0hc said:
Update time!
Got it into the stock recovery. Wiped the cache and all of my data. Rebooted, and.... it turns on! No longer reboots on regular startup. That's the good news. So at least it's somewhat useable now..
Now for the BAD news.
-It still does that retarded charging bootloop that doesn't seem to get me anywhere
-....When it's on. Like, running, it doesn't charge. Nadda. Zip. Zilch. Computer, wall charger, android dock, nothing. It just won't charge when it's on. However when I got it to power on, it said I had 14% remaining - which means it was likely charging inside the Bootloader, as I had it on that for quite a bit.
I think this just went from a software to a hardware issue. Thoughts?
Click to expand...
Click to collapse
Power down phone, do a long battery pull, place it inside again, let it charge for a few hours without powering it on, when it is fully charged (or after a few hours) pull battery again and then take charger out the phone. After a few minutes, place battery inside phone again and start it up without the charger.
Hope that works.
Sent from my Galaxy Nexus using xda premium
And that might fix this charging bootloop? Because the LCD doesn't even turn off..
i.vt3c.d0hc said:
And that might fix this charging bootloop? Because the LCD doesn't even turn off..
Click to expand...
Click to collapse
You could always try a new battery
Sent from my Galaxy Nexus using xda premium
+1 for the new battery thought.
Battery test
I am having a similar problem, I get the boot loop.
Difference is that I had started with a new battery so that could be your problem or unrelated. I went to a mobile shop yesterday and they let me use a new battery to see if the loop would start. It did not so there seems to be at least one other failure path. I have avoided a factory reset as I was hoping to pull some pictures but coming to the realization that I will have to try factory reset as a last resort
I posted to this thread #192
http://forum.xda-developers.com/showthread.php?t=1490815
My Galaxy Nexus phone from WIND went into a reboot loop yesterday. It had been charged to 98%, used to make a call and then put away. Wireless was enabled. Noticed vibration periodically and say it was rebooting every 6 - 7 seconds. Pulled battery to stop reboot. Saw references to fully charged battery via USB stops reboot loop so tried that. Battery voltage was 4.17V and still went into reboot loop.
Tried to boot into safe mode but still goes into a loop
I went into recovery mode and tried all options but factory reset because I am hoping to recover some pictures
reboot system now
apply update from cache (but did not have an update to install as only options were ../ lost+found/ recovery and when I selected these was in a loop as well)
wipe cache partition
Can't tell what version of Andorid I have as the phone never finishes booting.
Boot console gives the following information
Product Name – tuna
Variant – maguro
HW version – 9
Bootloader version – PRIMEKK14
Baseband version – I9250UGKL1
Have installed SMS backup because I was planning to do a backup after a trip. Also have two GPS tracker apps installed.
GNMO15 said:
[snip]
I have avoided a factory reset as I was hoping to pull some pictures but coming to the realization that I will have to try factory reset as a last resort
Click to expand...
Click to collapse
If you can boot into recovery, you may be able to get your pictures off your device.
1) Make sure you have the drivers for your device properly installed on your computer.
2) Download the attachment and unzip it to a directory on your computer.
3) Open a command prompt in the same directory.
4) Reboot your device into recovery and plug into your computer.
5) Make sure your computer sees your device by typing: adb devices
6) Pull the data off your device by typing: adb pull /data/media
Note: depending on how much data you had on /sdcard, this could take a while, so be patient.
I have a one X unlocked international version which I had rooted and set up a recovery. I then went on to try to flash over ARHD after super wiping, and did a battery stat reset since I had flashed at around 30% and figured it would reset the calibration on the battery. Anyways, from here this is where it goes bad. After restarting it goes into a boot loop and ends up getting kicked back into bootloader. After this I try to factory reset to no avail. After trying to reflash the rom a couple times using recovery, recovery just died and won't even load anymore. In addition to this I can't get the battery to hold a charge as each time I plug it in it reboots and loads then says 0 battery and dies instantly. I can get to bootloader and fastboot but can't flash anything through fastboot because it says the battery is too low.
Any suggestions on how to fix this and get it back up and running, or am I forced to send it to HTC the moment they bring in parts for it. (right now HTC says there is a wait on parts as they do not have any in stock as its a new phone and their texas facility has diddly on hand)
Any suggestions are welcome as to fixing this predicament.
phil.W said:
did a battery stat reset since I had flashed at around 30% and figured it would reset the calibration on the battery.
Click to expand...
Click to collapse
How did you wipe batterystats, from CWM? As the recoveries are new I suppose it's possible something went wrong if you did it that way, but it seems unlikely.
However, though probably not the root of your problem, there's no point in wiping batterystats.bin, as all that file holds in information on what processes have been using battery since your last unplugged your charger. This was one of those android myths (I used to do it too ) that was officially put to bed early in the year:
http://www.xda-developers.com/andro...g-battery-stats-does-not-improve-battery-life
In addition to this I can't get the battery to hold a charge as each time I plug it in it reboots and loads then says 0 battery and dies instantly. I can get to bootloader and fastboot but can't flash anything through fastboot because it says the battery is too low.
Click to expand...
Click to collapse
I'm pretty sure I've seen others with this issue, have a search around the forums. Have you tried turning the phone from the bootloader screen, and leaving it plugged in to charge for a while?
Try this:
1. Boot into bootloader
2. Select Fastboot menu
3. Select "Power off" to shut down the phone
5. Plug in charger
Leave it for a while. From what I've read, the power LED may flash at first, but should settle after a few mins to a solid red. I'd leave it till it's green and fully charged then try again.
If that works, and you can get into recovery again, try restoring your backup of the stock ROM if you have one, to check the phone boots okay. (If you didn't take a backup first, you will next time. ) Otherwise try re-flashing the ROM, or if that fails you might have to re-flash stock recovery, re-lock your bootloader and then run the relevant RUU for your device to flash the stock firmware back. You'll have to unlock and root again in that case.
Good luck, hope it works for you!
I run a rooted SG S3 on stock 4.1.1 with an old 3.0.56 kt747 kernel
Until recently, I've been running this set up for years without any problems.
I've also updated fairly recent CWM along with the latest SU.
As the title states, my phone has been turning off automatically. After weeks of troubleshooting, I noticed a pattern.
When I press the power button, there are three different scenarios that happen.
The phone goes to sleep normally
The phone goes to sleep and immediately wakes up to the lock screen
The phone displays the shut off menu
If scenario 1 occurs, everything is fine and runs perfectly for an indefinite amount of time until i attempt to put the phone to sleep again.
but, if scenario 2 or 3 occurs, the phone automatically shuts down abruptly, within 1-5 seconds.
This problem still occurs even when I boot into safe mode, and I have eliminated the SD card as a suspect. Furthermore, booting the phone up has become extremely difficult. The boot would sometimes crash after the samsung logo, after the splash screen, or during the boot animation. It takes somewhere around 3-5 tries to fully boot up the phone.
Booting into CWM recovery is still possible, but even that sometimes crashes mid-way. I've also noticed that at certain times, when I click the power button to select an action in CWM, it actually double clicks (thankfully CWM is tolerant to that) and cancels the action I was trying to do. I've done some googling and found that an over sensitive power button is a common occurrence in this model, and while that may explain why the 3 different power button scenarios occur, it still doesn't explain the crash.
Finally, I seemed to have remedied the automatic shut off problem several times by wiping cache from CWM. When I first started having these problems and began troubleshooting, wiping the cache eliminated the problem for about a week before the problem came back. When it did, I uninstalled some apps and re-wiped the cache which eliminated the problem again for several days. However, these periods become shorter and shorter, and now wiping cache does not seem to help at all. I've also tried wiping the delvik cache, but it didn't help.
I'm stumped right now. Any suggestions would be appreciated before I try some more large-scale attempts such as resetting my phone or taking it apart. Thanks everyone!
This definitely fits more in your large-scale attempts category, but it is what I'd try.
I'd grab the stock 4.1.1 firmware from sammobile.com and Odin back to stock. You're fortunate to be on the old firmware, so you can Odin back to stock. When Odin completes successfully, pull battery don't let the phone reboot normally (untick auto reboot in Odin). Boot straight into the stock recovery and do a full wipe. Then reboot your phone normally.
Doing this will correct any problems that exist with your internal storage to the extent possible. If you've still got problems after doing this, it is probably a hardware issue.
jason2678 said:
This definitely fits more in your large-scale attempts category, but it is what I'd try.
I'd grab the stock 4.1.1 firmware from sammobile.com and Odin back to stock. You're fortunate to be on the old firmware, so you can Odin back to stock. When Odin completes successfully, pull battery don't let the phone reboot normally (untick auto reboot in Odin). Boot straight into the stock recovery and do a full wipe. Then reboot your phone normally.
Doing this will correct any problems that exist with your internal storage to the extent possible. If you've still got problems after doing this, it is probably a hardware issue.
Click to expand...
Click to collapse
Yeah, that's part of the reason why i didn't want to upgrade the bootloader for the newer firmwares. I messed around with my phone this morning and its been avoiding the problem ever since. Not exactly sure what I did though lol. Thanks for the reply, I'll try it if the problem comes back over the next few days.
Your phone isn't "crashing," your power button is malfunctioning. The fix is pretty easy. You will need to open your phone up and scrape it off (the phone can be turned on without it). There are youtube videos that show how to remove it.
My unlocked phone will only work if it is plugged into the charger.
If I unplug it it will go into an endless loop of the amazon start screen.
Stock rom and I just upgraded to the new firmware.
Please help!
Please help!
Can you access recovery?
updated below
not even the stock recovery?
I can access stock recovery only when the phone is plugged into the charger
Will not work if the phone is plugged into the computer via usb
xjakerobertsx said:
I can access stock recovery only when the phone is plugged into the charger
Will not work if the phone is plugged into the computer via usb
Click to expand...
Click to collapse
then this is out of my league.
xjakerobertsx said:
I can access stock recovery only when the phone is plugged into the charger
Will not work if the phone is plugged into the computer via usb
Click to expand...
Click to collapse
I'm guessing this means you have a faulty battery. The fact that it works on the charger and not unplugged or plugged in via USB is indicative the phone believes the battery is completely drained.
I would try to following before contacting Amazon for a warranty replacement: Try to factory reset from the Amazon Stock Recovery (assuming you're certain you are on FireOS). I would then let it charge turned off for a couple hours and try to turn on. If it works, great. If not, I'm afraid working with Amazon is your only avenue.
Any update on the case? I had the same situation. My fire phone having endless bootloop. Only if I connect to charger it can work.
Manage to go to recovery, wipe all, problem still persist.
Same thing
Went into stock recovery
Wipe the phone clean and it still gives me the endless loop
Anyone got an fixes for this? How can I pull all my pics off if this if it keeps rebooting
bump for help
blazin6969 said:
Anyone got an fixes for this? How can I pull all my pics off if this if it keeps rebooting
Click to expand...
Click to collapse
Try to charge your phone and turn it on. If can, you can use WiFi file explorer from play store to pull your data. Make sure fire phone and pc or laptop connect to the same WiFi.
Mine will goes to bootloop if direct connect to pc or laptop.
I just started having this problem yesterday, same exact symptoms. Wiping cache took an incredibly long time, factory reset went smoothly, but neither fixed the issue. It went in to another boot loop immediately after the reset completed, and only came out if it when I plugged it in to a charger again.
That said, it told me a little later that it had updated its firmware, congrats yada yada... and so far (fingers crossed) it hasn't acted up again.
It's now on Fire OS 4.6.6.1 (466001420), I couldn't say what it was before. Can anyone still experiencing this report what version you are on right now?
Also, it may or may not be relevant that I allowed the phone to charge for over 12 hours before disconnecting it.
Have you tried booting into stock recovery then pushing amazon update file to the phone via adb (adb sideload)?
sirkero said:
I just started having this problem yesterday, same exact symptoms. Wiping cache took an incredibly long time, factory reset went smoothly, but neither fixed the issue. It went in to another boot loop immediately after the reset completed, and only came out if it when I plugged it in to a charger again.
That said, it told me a little later that it had updated its firmware, congrats yada yada... and so far (fingers crossed) it hasn't acted up again.
It's now on Fire OS 4.6.6.1 (466001420), I couldn't say what it was before. Can anyone still experiencing this report what version you are on right now?
Also, it may or may not be relevant that I allowed the phone to charge for over 12 hours before disconnecting it.
Click to expand...
Click to collapse
Is it possible do to update you fix your issue? I had charge my phone for more than 12 hours but no luck...
I will try to update via sideload adb. If anyone can show me the link for the how to appreciate it.
Sent from my MI 4LTE using XDA-Developers mobile app
Update on mine:
The firmware update did not fix the problem. It is still possible that it alleviated the situation for a time, but much more likely it was just coincidental timing.
My Fire Phone behaved itself for most of a day and a half, then suddenly went back to the boot loop. I left it this way overnight to try to deep cycle the battery.
After draining completely, it took several hours on the charger before it began showing a charging screen, which comes and goes in intervals just like the Amazon logo had before. It has not progressed beyond 0% charge since then. I'm assuming a faulty battery at this point, or perhaps a corrupt battery stats file (but that should have cleared with the factory reset correct?)
My sincere apologies for any false hopes I may have given anyone.
sirkero said:
Update on mine:
The firmware update did not fix the problem. It is still possible that it alleviated the situation for a time, but much more likely it was just coincidental timing.
My Fire Phone behaved itself for most of a day and a half, then suddenly went back to the boot loop. I left it this way overnight to try to deep cycle the battery.
After draining completely, it took several hours on the charger before it began showing a charging screen, which comes and goes in intervals just like the Amazon logo had before. It has not progressed beyond 0% charge since then. I'm assuming a faulty battery at this point, or perhaps a corrupt battery stats file (but that should have cleared with the factory reset correct?)
My sincere apologies for any false hopes I may have given anyone.
Click to expand...
Click to collapse
It's OK mate, we all trying to find possible solutions for our problem.
Cheers.
Sent from my MI 4LTE using XDA-Developers mobile app
Solved replacing battery
I had this problem weeks ago, solved by:
1.- Drained battery to 0% (may skip this step? idk)
2.- Replaced battery for a new one (Search for one in amazon)
3.- Fully charged the new battery.
4.- Turned on fire phone.
cramosa said:
I had this problem weeks ago, solved by:
1.- Drained battery to 0% (may skip this step? idk)
2.- Replaced battery for a new one (Search for one in amazon)
3.- Fully charged the new battery.
4.- Turned on fire phone.
Click to expand...
Click to collapse
+1 for this.
I had this problem and just replaced battery. Fire Phone worked great again !
Can't believe a. faulty battery cause many problems.
Btw, if you replace battery by yourself, please notice the attached glue between battery and case. Try to remove them all gently - can search on YouTube how to replace Fire phone battery.
D851 phone running stock lollipop
I had an issue the other day where my WiFi and Bluetooth were refusing to connect and just said "connection not allowed" so I tried a few things and then resorted to a factory reset.
Luckily the factory reset fixed the WiFi issue but now another issue has come up, an almost endless boot loop.
Occasionally the phone will actually boot but it never stays on for long even when plugged in. I've tried factory resetting again but to no avail.
Prior to this issue my phone would have the occasional random reset but nothing too frequent, my battery is relatively new but I'm not ruining out the possibility of a faulty battery and am in the process of getting a replacement.
Does anyone have any ideas what this issue could be caused by and how to fix it? The fact that it occasionally boots makes me think it IS a battery issue but I'm a complete noob to this kind of thing.