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 just received a replacement I747M. It was running android 4.4.2 I747MVLUFNK2. I rooted and flashed recovery. Even before I installed custom rom the phone would not boot with the stock firmware unless the phone is plugged in. When plugged in the phone will boot and work fine. Whenever the cable is removed phone automatically reboots, and will start boot looping. Return the cable and the phone works fine. I tried flashing back to stock with a sammobile image of the same firmware. I also tried installing a custom rom and experience the same issue. When I flashed back to stock firmware phone took forever to load and didn't seem to get past the splash screen after waiting for over 10 min, however it was able to boot without the power cable plugged in. Any advice here would be appreciated.
Thanks
Update: I have re-flashed to stock successfully but still experiencing the boot loop problem when not connected to a USB power source. There is no reboot in recovery or download mode. Again plugging the USB cable into the phone resumes normal boot and operation. Only when the cable is removed does the phone restart.
Update #2: Turns out it was an issue with the battery. Trying another battery seems to have solved the problem.
Rooting the I747MVLUFNK2
Northerntouch said:
I just received a replacement I747M. It was running android 4.4.2 I747MVLUFNK2. I rooted and flashed recovery. Even before I installed custom rom the phone would not boot with the stock firmware unless the phone is plugged in. When plugged in the phone will boot and work fine. Whenever the cable is removed phone automatically reboots, and will start boot looping. Return the cable and the phone works fine. I tried flashing back to stock with a sammobile image of the same firmware. I also tried installing a custom rom and experience the same issue. When I flashed back to stock firmware phone took forever to load and didn't seem to get past the splash screen after waiting for over 10 min, however it was able to boot without the power cable plugged in. Any advice here would be appreciated.
Thanks
Update: I have re-flashed to stock successfully but still experiencing the boot loop problem when not connected to a USB power source. There is no reboot in recovery or download mode. Again plugging the USB cable into the phone resumes normal boot and operation. Only when the cable is removed does the phone restart.
Update #2: Turns out it was an issue with the battery. Trying another battery seems to have solved the problem.
Click to expand...
Click to collapse
Hi there,
I have the same phone as you (I747MVLUFNK2) and can't find any Xda post on how to root it... How did you did it?
Thanks
Is your phone still under warranty? If not, flash a custom recovery and install supersu from recovery.
I'm not sure how else to describe these two problems I have.
Just for reference, I am using Cyanide L RC 7.1 from here: http://forum.xda-developers.com/galaxy-s3-att/development/rom-cyanide-l-v1-android-5-0-2-t2980174,
and I am using TWRP 2.8.5.0 for d2att. I have a i747M on Rogers.
Problem #1: boot loop only when plugged into AC charging
In the past week, I found that my phone gets stuck in a boot loop only when the phone is plugged into the AC charger. It will boot up, show the Samsung logo, then the Cyanogenmod logo with Cid, then show the Cyanide L boot animation. Once the animation is over, the phone just reboots. This happens endlessly (I didn't let it go on for more than 20 minutes, I didn't have time to wait). However, if I let the phone boot while it's not plugged in, then it boots up just fine. It also boots up just fine if I am plugged in via USB as a data connection to a computer. This only happens when I am plugged in via AC.
I have tried different combinations of USB cable and USB AC adapters. Doesn't seem to make a difference. I thought maybe it's a battery thing and borrowed a colleague's battery (also i747M), no dice.
Thoughts on what's causing it to boot loop like this?
Problem #2: Cannot wipe Data in TWRP
I discovered this problem when I was trying to update to the latest version of Cyanide L RC 8. I booted into recovery (TWRP 2.8.5.0) and proceeded to dirty flash the ROM. First boot had terrible com.android.phone FCs every 5 seconds. So I booted back into recovery a couple more times to reflash, same problem. I decided to do a clean flash and do a factory wipe. That's when the problem began. Once it reads "wiping Data without erasing /data/media" (or words to that effect) TWRP would freeze (the animated progress bar at hte bottom stops moving) and the phone would just reboot. The phone then gets stuck in an endless boot loop. I tried this numerous times, same problem. Couldn't restore a NANdroid either because it wipes Data before restoring.
I had to boot up into Download mode to use Odin to flash a custom ROM back and work my way back to a NANdroid I had. Took me the better part of 2 days without a working phone to get back to my latest NANdroid backup.
Any ideas what causes this freeze + crash in TWRP? I have reflashed TWRP, but I'm too afraid to test it out, only to lose another 2 days like that.
Thanks
Maybe you'll have better luck with Philz Touch recovery for the d2lte?
No luck with Philz Touch recovery. Tried that one, and also the latest TWRP. Seems to be the exact same behaviour with trying to wipe the Data partition.
I'm currently half way through using Odin to flash a stock TW 4.3 ROM to the phone. Hoping that this might solve my problems - perhaps something went awry during a recent ROM flashing, and I'm hoping that using Odin to nuke and pave my phone will fix it.
Fingers crossed...
daver68 said:
No luck with Philz Touch recovery. Tried that one, and also the latest TWRP. Seems to be the exact same behaviour with trying to wipe the Data partition.
I'm currently half way through using Odin to flash a stock TW 4.3 ROM to the phone. Hoping that this might solve my problems - perhaps something went awry during a recent ROM flashing, and I'm hoping that using Odin to nuke and pave my phone will fix it.
Fingers crossed...
Click to expand...
Click to collapse
If Odin doesn't get it try a wipe in the stock Samsung recovery.
What bootloader is on your phone? Hopefully, it is 4.3 or newer and you are using the stock ROM from sammobile.com.
audit13 said:
What bootloader is on your phone? Hopefully, it is 4.3 or newer and you are using the stock ROM from sammobile.com.
Click to expand...
Click to collapse
I'm on NF2, so definitely not an issue with the bootloops and bricking that might happen by being on 4.2 or earlier.
Flashing with Odin worked perfectly, and yes I used a ROM from sammobile.com. After that, I flashed SuperSU and TWRP 2.8.6.0 through Odin as well, before downloading another ROM to test wiping, flashing, more wiping, and more flashing. So far no crashes in TWRP when wiping data.
I haven't been able to re-produce the boot loop when plugged into AC, it's only been a day, but we'll see if that rears its head again.
Well, it was a good 2 weeks, but now I'm back to having the same issues. This time I'm on a different ROM, but the two issues are the same.
I'm currently on S3Rx, 4.4 Touchwiz.
If plugged into AC (wall adapter), I get bootloops. If plugged into USB into a computer, it's fine.
Going into TWRP and doing anything with the /data partition causes the device to freeze up and then restart itself.
Is it possible that my storage hardware (the memory itself) might be failing?
daver68 said:
Well, it was a good 2 weeks, but now I'm back to having the same issues. This time I'm on a different ROM, but the two issues are the same.
I'm currently on S3Rx, 4.4 Touchwiz.
If plugged into AC (wall adapter), I get bootloops. If plugged into USB into a computer, it's fine.
Going into TWRP and doing anything with the /data partition causes the device to freeze up and then restart itself.
Is it possible that my storage hardware (the memory itself) might be failing?
Click to expand...
Click to collapse
The problem 1: you mentioned that the you are suffering with the problem of rebooting in the loop that occurs only when you use the AC wall outlet for charging. You must see in its rectifying circuitry detail. The problem may be there.
I eventually found a solution, though I don't know if it was a solution to the root problem.
My problem was that I was getting bootloops when plugged into AC charger. My solution, how ever random it seems, was simply to flash back to stock (via ODIN) to 4.4.2. Since then, my Problem 1 and Problem 2 were solved. This completely wiped everything on my phone (luckily I did a complete backup to my computer), but it also solved both of my problems.
It seemed the problem #1 was not caused by a bad charger or cable, as one might have thought.
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.
Hi guys
I seem to have an incredibly weird issue on my HTC. It is rooted and running DU 6.0.1.
For some reason, despite the battery being 60%+, whenever I unplug my phone from power it just switches off. If I try to reboot it/go to recovery, it starts up for a second and goes off. However, it seems to function normally when it is plugged in via usb. I can access recovery as well. I have tried to reflash as well as a full wipe, but nothing seems to work.
Im thinking something went wrong with the boot.img maybe ?
Any help would be appreciated.
xdaaccount123 said:
Hi guys
I seem to have an incredibly weird issue on my HTC. It is rooted and running DU 6.0.1.
For some reason, despite the battery being 60%+, whenever I unplug my phone from power it just switches off. If I try to reboot it/go to recovery, it starts up for a second and goes off. However, it seems to function normally when it is plugged in via usb. I can access recovery as well. I have tried to reflash as well as a full wipe, but nothing seems to work.
Im thinking something went wrong with the boot.img maybe ?
Any help would be appreciated.
Click to expand...
Click to collapse
Maybe its a stupid inquiry but does battery work as it should in stock rom? so that you can be absolutely sure its not faulty battery that's creating issues.because two things happen(in my experience when something goes wrong with boot.img) either its stuck at splash screen (hboot) with red text OR it goes blank but not off, just blank
Definitely isnt the battery. I am not experiencing any drain and it functions completely normally when plugged it. When I unplug, it works fine for a few min and then switches off. It will then not turn on, despite it showing 90%+ when I plug it in
but it happens in stock rom also? thats what i wanted to know .if you can full wipe and phone works when connected to usb,maybe you can run ruu and confirm that as well . If you can go to recovery ,make a nandroid backup.and try a ruu.
Yup, happens on stock as well.
Also, I think the recovery is messed up as well since it just crashes now when trying to flash something. It's having issues doing a nanroid backup as well
And no love for exe ruu as well?