Related
I have a very serious problem and i don't know if anyone of you here have encountered before.
My problem is, i tried to flash clockwork recovery 3.05 with unrevoked, it stopped at the stage with a message " wait for 5 second while rebooting" it went for a few minutes but i though it still running and don't want to disturb it. I left my phone at home and went out for lunch and after half of minutes i came back my phone still sitting at that screen by i noticed that my battery drained fast and by the time i want to unplug my phone from USB, it went dead!!! I tried to recharge my phone for 1 hour and still couldn't get it to turn on.
Did i bricked my phone?? Any advice to overcome this?? Need your help urgent!!
Thanks in advance.
No you did not brick it. I think your batterie is dead. Try charging it again (not true your pc and usb).
If that does not work, you will need to buy a new batterie.
I have a Gen1 Kindle Fire that will not power up. I bought it as not working so I don't know any history on it. I can usually fix these stuck in boot loop units with no problem.
On this one, I get the Orange/White Kindle Fire logo for 5 seconds and then it shuts down. I have spent a couple of days reading every post in the "5 second bootloop! aka: Don't let your battery die!" thread and have had the KF plugged into a 2 amp charger over night. Nothing seems to work including a factory cable. No drivers get a chance to load and nothing appears in device manager on a pc which loads drivers fine with a different Kindle.
I finally took the battery out and put it in another KF and it booted up no problem. When I went into Settings > Devices it said that the battery charge was 100%. I haven't been able to find any other threads with this same problem.
Now what? Can I use something like Firekit to reflash the bootloader and/or system? Any other ideas?
Any help would be greatly appreciated.
Any words of wisdom out there?
I'm having a weird problem. Yesterday I was using my phone as I normally do-- texting, playing simple puzzle games, etc.-- when I noticed the battery was at about 2%. I wasn't very concerned so I tried to send one last text before it died. Shortly afterward it died with the usual "Powering Down" alert. I thought absolutely nothing of it and once I had access to a charger, I did what I normally do: I turn on my phone, wait for it to get past the LG splash screen, and I plug it in once it gets to the boot animation. I do this so my phone will turn on instead of going into charge only mode. Also, like usual, my phone's screen dimmed seconds after the boot animation began (I assume from my automatic light sensor settings), and I could feel it vibrating a little (also something it typically does upon boot).
However this is as far as it got. I was very confused when about an hour later, the phone still hadn't completed boot. I removed the battery, inserted it again, and tried once more telling myself that I would wait as long as I could instead of just an hour. Booting the second time gave me identical results-- everything is normal (light sensor response and vibration indicating the phone is powering on) yet it gets stuck. The only difference is that this time I got to see the entire bootloop.
After the boot animation screen has run for a while, I get the usual "Android is starting.... Optimizing app ## of ##" (#= actual numbers). Once it finishes, instead of booting my phone, it begins the boot animation again. If left alone it will cycle between the boot animation and the "Android is Starting" screen indefinitely.
TL;DR:
1. ) Caught in bootloop between boot animation screen and "Android is Starting... Optimizing app ## of ##" screen.
2. ) The screen still dims and there are little vibrations that usually tell me the phone is about to turn on.
I have tried:
- a hard reset- this yields only a slightly stronger vibration and it starts the bootloop again.
- Download mode- this does the same as the hard reset
- Removing battery for a while- no results
- Full charge to completely dead to full charge again on charge only mode- no results
I am running CM13 Nightlies from late February (not completely sure which exact date). Which I flashed without issue about a month ago. I do have Xposed and run various modules, but I was using nothing at the time and hadn't for about a month. My computer recognizes my phone as an LG G3 Device, but refuses to access any files.
Any help would be greatly appreciated!!
Phone not starting.
First remove phone battery, insert it again, do not start phone. Connect your phone to original charger and charge it, while charging with the charger start your phone. Your phone should start if yes/no report me immediately. Your phone battery is failing to start your phone (Due to Low Voltage in battery). Replace with original battery.
jit1108 said:
First remove phone battery, insert it again, do not start phone. Connect your phone to original charger and charge it, while charging with the charger start your phone. Your phone should start if yes/no report me immediately. Your phone battery is failing to start your phone (Due to Low Voltage in battery). Replace with original battery.
Click to expand...
Click to collapse
Alright, I removed the battery, reinserted it (without turning the phone on) plugged it into the wall charger (seeing the charge only battery animation), and attempted to turn it on. Whenever I try to turn my phone on after plugging it in, I get the LG splash screen followed by the battery charging animation. It never reaches the boot animation. I'll let it charge for a while and try again.
Thank you for the advice!
Okay, I let the phone charge completely and attempted to turn it on whilst plugged into the wall charger again. Unfortunately I had the same issue. The phone shows the LG splash screen and then the battery charging animation again-- no boot animation.
musiceas66 said:
Okay, I let the phone charge completely and attempted to turn it on whilst plugged into the wall charger again. Unfortunately I had the same issue. The phone shows the LG splash screen and then the battery charging animation again-- no boot animation.
Click to expand...
Click to collapse
just start with a full reflash , if it doesnt boot up its simply broken
Jhinta said:
just start with a full reflash , if it doesnt boot up its simply broken
Click to expand...
Click to collapse
Yeah, I'm trying to avoid a full reflash/data wipe. Since I haven't messed around with any Xposed modules or root apps, I also haven't backed up anything for quite a while. No abnormal apps were running before the battery died, which leads me to believe this can be solved somehow without a full wipe.
Also, I tried to use my boyfriend's battery to boot up my phone. I thought it might be a bad battery-- as some people on-line have mentioned. Unfortunately, it still refused to boot and it produced the same bootloop.
You see , if and not and this and that dont help . te only way to save files is to get acces by recovery or boot, you cant boot but possible you have recovery so start saving your files you need. when you have or dont have your files . you stil need your system to boot for that to happen, it needs to work. so flashing a default rom with wipe sould work if it doesnt you flash original if that doesnt work its dead
Verstuurd vanaf mijn LG-D855 met Tapatalk
I think I forgot to mention, I cannot access recovery mode. I have the latest TWRP installed, but attempting to boot into recovery gives me the same results-- endless bootanimation/ "Android is Starting" bootloop.
So no acces at all . so what do you do ? Read above! Anyway good luck
Verstuurd vanaf mijn LG-D855 met Tapatalk
Solved
I fixed my problem. It turns out I was being an idiot and got the method of entering recovery mode on the LG G3 confused with my Samsung tablet. I should be able to fix the bootloop on my own now. Thanks everyone for your help! Cheers to idiocy.
Hey, I have the exact same issue right now. Did you solve your problem, and how? I tried removing the battery and charging with original charger to 100%. I connected it to my PC, went into Download mode and clicked "Restore Upgrade Errors" in LG PC Suite. It successfully flashed the firmware update, then it said "Android is starting.... Optimizing app ## of ##". But after that it restarted into bootlop again. Also I noticed that sometimes it vibrates, and my LED (light sensor) doesn't light up anymore.
Any advice? I haven't tried replacing the battery yet.
simon710 said:
Hey, I have the exact same issue right now. Did you solve your problem, and how? I tried removing the battery and charging with original charger to 100%. I connected it to my PC, went into Download mode and clicked "Restore Upgrade Errors" in LG PC Suite. It successfully flashed the firmware update, then it said "Android is starting.... Optimizing app ## of ##". But after that it restarted into bootlop again. Also I noticed that sometimes it vibrates, and my LED (light sensor) doesn't light up anymore.
Any advice? I haven't tried replacing the battery yet.
Click to expand...
Click to collapse
Hi i have the same problem with my lg g3 d855, after a reflash hi is start and do android optimazig after the tel is start and do this over and over. help please
Hi, the solution that worked for me was to
1. install drivers
2.install LGUP
3.flash "LGD855P_D855P10a_04" - found here https://drive.google.com/file/d/18tlmVNK_ba0jIapJy-Sz5wamxbIXh8xH/view
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.
Hello there everyone! Let me explain my problem:
Backstory
I have a Samsung Galaxy Nexus GT-i9250 maguro since 7-6 years or so. I've been flashing some roms into it and everything went well since a week ago.
I had installed from a very long time this version of CM "cm-13.0-20160921-NIGHTLY-maguro" and I have not updated it, so I basically was running that from a very long time.
Three weeks ago the phone started behaving strangely, it was closing automatically, and I thought that it was a temperature problem (being a very hot summer) so I did not worry too much.
Everything was working fine, charging and connecting via USB .
Problem
Last week the phone once again died and I tried to boot it up normally as I would normally do, but nothing happened, not even the Google logo popped up.
So I removed the battery and put it back in, the phone booted up to the Google logo, then after two or three seconds the Google logo flashed like brightness went up to 100% and black screen.
Went into fastboot, booted TWRP to see if that was working, and the recovery was working fine.
Things got worse.
At the moment
I cannot get the phone to do anything if it's not connected to a power source.
If the phone is connected via USB, or charger, I can get it to go ONLY on fastboot, and download mode. If I unplug the phone while on fastboot or download mode, the screen brightness goes up to 100% for half a second then it glitches out and goes into black screen immediatelly. I can not access bootloader nor recovery mode from fastboot, because the phone reboots, shows the Google logo and then it dies.
What I tried
Thinking that maybe the ROM went crazy, I followed this guide to flash the phone with all the original ROM and recovery (I downloaded "yakju-jwr66y-factory-4cadea65" and followed the instructions of the guide).
Nothing changed, if the phone is not connected to a power source, it is basically dead, if I put it to a power source it shows the charging logo for a second, then black screen, and I can only boot up fastboot and download mode.
I don't know if this might help but I've also tested the battery voltage and it seems to be fine.
Last thing, if I connect the phone to the PC (with the battery or without) every 2 seconds it shows up that an unidentified device is being detected.
I currently am using a laptop running windows 8.
On my desktop computer the same thing happens (the device detection) but from device manager I see a OMAP4400 (something like that) popping up but at the moment I cannot use my desktop PC since I'm traveling.
I would really like to know what happened to my phone, any answer will be appreciated.
Thanks in advance!
Update [solved]
After doing some research and trying different methods I gave up. But then I realized that maybe trying the stupidest thing could be the solution, so I went to a phone shop and asked them if they had some sort of test battery that I could plug in my phone temporarily to see if it was booting up.
Turns out, it was the battery.
I bought a new battery and now the phone runs smoothly like it's new.
I feel so dumb and I'm so sorry if I've made some of you people waste your time by reading the poem of the first post.
Hopefully this will someday help someone that will have the same problem of my GT-I9250!
(This thread can be closed now)