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.
Related
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!
So I'm not sure what happened with my girlfriend's Gnex, she updated to 4.2 a couple days ago, then her battery died. So she went to charge it and when it finished charging, she went to turn it on normally, but it went into a reboot loop? So i was talking to someone else on another thread that i saw similar, so i tried to do a flash stock + unroot, it connected i got into recovery menu and everything, went to do it, and then the screen started going staticy, and it said it failed then it said it should take 5-10 minutes or something. So i guess it froze or something, so i took the battery out and the screen was still staticy, and then i unplugged it from the USB, and now it won't turn back on. Did i brick the device? :/ Thanks in advance for future answers.
you cant get into to recovery either? or fastboot mode?
k786 said:
you cant get into to recovery either? or fastboot mode?
Click to expand...
Click to collapse
nope, when i went into recovery it went staticy again and then went back into its bootloop :/
but now it just won't turn at all, i've done a battery pull, battery swap, nothing worked.
AdmiralAqbar said:
nope, when i went into recovery it went staticy again and then went back into its bootloop :/
but now it just won't turn at all, i've done a battery pull, battery swap, nothing worked.
Click to expand...
Click to collapse
Then I am afraid you're hard bricked pal
Sent from my GNexus
AdmiralAqbar said:
nope, when i went into recovery it went staticy again and then went back into its bootloop :/
but now it just won't turn at all, i've done a battery pull, battery swap, nothing worked.
Click to expand...
Click to collapse
what about fastboot mode?
Same
AdmiralAqbar said:
So I'm not sure what happened with my girlfriend's Gnex, she updated to 4.2 a couple days ago, then her battery died. So she went to charge it and when it finished charging, she went to turn it on normally, but it went into a reboot loop? So i was talking to someone else on another thread that i saw similar, so i tried to do a flash stock + unroot, it connected i got into recovery menu and everything, went to do it, and then the screen started going staticy, and it said it failed then it said it should take 5-10 minutes or something. So i guess it froze or something, so i took the battery out and the screen was still staticy, and then i unplugged it from the USB, and now it won't turn back on. Did i brick the device? :/ Thanks in advance for future answers.
Click to expand...
Click to collapse
I'm having a similar issue. I wanted to flash the memory so i relocked the phone using the wugkit, then unlocked and rooted. For some reason, it wouldn't load a new rom. I kept getting the triangle exclamation point android graphic. I pulled the battery and that was it. Black screen. Won't turn on. A cpl of times, it was almost recognized by the computer via USB, but just kept failing. This sucks.
cyberelli said:
just a thought: are you sure it's charged up enough to boot? i know i've mistakenly thought my phone was messed up when the battery was just dead
Click to expand...
Click to collapse
Yes the battery is charged. Occassionally, when I plug it into the computer, it makes the new device notification and then fails over and over again. I keep trying to get a glimpse of a lock so i can adb it.
Phone's been slowly giving me more and more issues. Today I was using it fine, turned off the screen, a bit later, tried turning it on and nothing. This has been a common occurrence, about once a day I have to do a battery pull or plug it in to make the screen turn on, then all is normal. Battery pull got it to boot to the splash screen, but then nothing. Plugged it in, and nothing. Left it plugged it in for about an hour, tried again, still nothing. Unplugged and tried powering on, nothing. Pulled the battery again, and could only get to the splash screen. I'm running JB Sourcery, and have the one selected where the apple rots and then it spells out droid. I get through that and then it does nothing else.
Info: just tried again, had to pull the battery, then I could get the google logo to pop up, but that was it.
Info the 2nd: plugged it in for 2 hours, the graphic showed it fully charged. So I tried booting it and again, same response..gets through the boot splash screen, but goes black after. Pressing power button does nothing, doesn't even get the charge graphic to show up.
Info the 3rd: I left it be this time thinking maybe it was just really laggy or something, but after 15 minutes, still nothing. But I can feel a bit of heat as if it is on.
Info the 4th: I can get into bootloader and recovery fine. I was even able to make a backup (only thing I could think to do in there that would take some time and not risk screwing it up more) So it's not a battery issue, seems to be something with the rom.
Please help
Even though the phone is rooted and custom rom, can I take it back to Verizon? I've only had the phone since December. If I could do that, is there any way to get all the pics off of it first?
try to flash stock image from google
Cristi_10 said:
try to flash stock image from google
Click to expand...
Click to collapse
Silly question, but how would I go about getting that? And can I get it to the phone without the phone being able to boot
VooDooCC said:
Silly question, but how would I go about getting that? And can I get it to the phone without the phone being able to boot
Click to expand...
Click to collapse
deja vu.....million times.
with a little search i found this http://forum.xda-developers.com/showthread.php?t=1626895
Was able to wipe data/cache and re-flash the rom. Seems to be working for now. I think I'll go back to stock (thanks for the link samersh) and see if I'm still having issues.
Didn't find anything similar on here so I had to post. My T999 no longer boots except for a vibrate when the battery is removed and re-inserted. Occasionally it will get to the CM boot logo and then the screen goes off. If I time the button presses right, I get to the Download screen but before I can hit the Up button to confirm download mode the screen shuts off. This happened all of a sudden yesterday, the last activity being to shut off the Alarm. Tried charging but it will not get past the initial battery icon before the screen goes off. Tried replacing the battery but that didn't help. I also tried to follow the debrick instructions but it didn't help. I was running Vanir AOSP 4.4.4 with no issues until yesterday. The device does not register when connected to the PC using USB and the charger LED does not light up when plugged into charger/PC. My feeling is that something went wrong with the boot but I am unable to get into any usable screen to do anything. I had managed to brick a Samsung Vibrant before but I didn't have to struggle as much to debrick and ODIN back to stock. Any help would be greatly appreciated, I'm now without a phone .
Mine is also acting like that. It wont boot to any rom even stock ones. But i noticed that if i connect my charger it will boot to the homescreen. Sounds like a battery issue right? I also thought that but when i go to recovery, it did not shutdown after leaving it for a couple of minutes. I'm also baffled why it wont boot. I'll try to borrow other battery to test if it still the same.
maelstromm said:
Didn't find anything similar on here so I had to post. My T999 no longer boots except for a vibrate when the battery is removed and re-inserted. Occasionally it will get to the CM boot logo and then the screen goes off. If I time the button presses right, I get to the Download screen but before I can hit the Up button to confirm download mode the screen shuts off. This happened all of a sudden yesterday, the last activity being to shut off the Alarm. Tried charging but it will not get past the initial battery icon before the screen goes off. Tried replacing the battery but that didn't help. I also tried to follow the debrick instructions but it didn't help. I was running Vanir AOSP 4.4.4 with no issues until yesterday. The device does not register when connected to the PC using USB and the charger LED does not light up when plugged into charger/PC. My feeling is that something went wrong with the boot but I am unable to get into any usable screen to do anything. I had managed to brick a Samsung Vibrant before but I didn't have to struggle as much to debrick and ODIN back to stock. Any help would be greatly appreciated, I'm now without a phone .
Click to expand...
Click to collapse
Remove battery snd put back in. Does the device try to turn on by itself? If so you probably have a bad power button.
LarsonJayz said:
Mine is also acting like that. It wont boot to any rom even stock ones. But i noticed that if i connect my charger it will boot to the homescreen. Sounds like a battery issue right? I also thought that but when i go to recovery, it did not shutdown after leaving it for a couple of minutes. I'm also baffled why it wont boot. I'll try to borrow other battery to test if it still the same.
Click to expand...
Click to collapse
Boot download mode and flash stock or root66 firmware with Odin. (You may need to factory reset too)
DocHoliday77 said:
Boot download mode and flash stock or root66 firmware with Odin. (You may need to factory reset too)
Click to expand...
Click to collapse
Done this using root66 but still the same. Now my phone went to worse. It wont get past the S3 logo in the boot screen and just shuts down followed by a vibrate. But if i connect my charger, it will continue and run as normal. My suspect might be a bad battery but the thing is it doesn't auto shutdown when is download mode or in recovery mode. Will try to borrow other battery and update if this fixes the problem.
This is pretty strange. Woke up to my phone with the Galaxy s3 boot logo. And it wouldn't go past it. Tried flashing different backups I had but none of them let me go past the boot logo. Flashed CM10 since my version of TWRP recovery is so old that it can't flash anything higher up, and it goes past the boot logo finally after 2 hours then goes to the cyanogen boot logo but doesn't go past that. I'm going to try with ODIN tonight.
Seems very strange that there are others that had this happen to them to. My phone has never done this before, and it happened randomly.
What does it mean if my phone doesn't boot past the logo with an odin to root66 file?
Edit: Nevermind seems to have worked... for now.
Edit 2: Okay so now it's stuck in an infinite loop where it boots past the logo, shows the android mascot then does an android is upgrading app 1 of 169 then goes back all over again. This is fun! Can anyone help?
Edit 3: Okay so I had to do a factory reset. Got it working now. Starting to get sick of the things I have to do to get updated firmware. Samsung needs to get their crap together!
LarsonJayz said:
Done this using root66 but still the same. Now my phone went to worse. It wont get past the S3 logo in the boot screen and just shuts down followed by a vibrate. But if i connect my charger, it will continue and run as normal. My suspect might be a bad battery but the thing is it doesn't auto shutdown when is download mode or in recovery mode. Will try to borrow other battery and update if this fixes the problem.
Click to expand...
Click to collapse
Hopefully its just the battery.
Download mode may work because of how the battery reports to the os. If its going bad and reporting incorrectly that its low, it may trigger a shutdown. Whereas in download mode the os isn't running so its not reading the battery info the same way. Just a guess.
crazexr7 said:
What does it mean if my phone doesn't boot past the logo with an odin to root66 file?
Edit: Nevermind seems to have worked... for now.
Edit 2: Okay so now it's stuck in an infinite loop where it boots past the logo, shows the android mascot then does an android is upgrading app 1 of 169 then goes back all over again. This is fun! Can anyone help?
Edit 3: Okay so I had to do a factory reset. Got it working now. Starting to get sick of the things I have to do to get updated firmware. Samsung needs to get their crap together!
Click to expand...
Click to collapse
Just for future reference, factory resetting solves about 98% of boot hangs.
Still for both of you, id take this as a sign that you should make sure your backups are up to date. If something is failing you'll be glad you did!
DocHoliday77 said:
Just for future reference, factory resetting solves about 98% of boot hangs.
Still for both of you, id take this as a sign that you should make sure your backups are up to date. If something is failing you'll be glad you did!
Click to expand...
Click to collapse
Yeah factory reset unfortunately didn't work for me when I needed it before I had to ODIN to root66. But I was able to do a nandroid after I couldn't get it to boot and extract my sms from Titanium backup. What an awesome app, super thankful to that dev for making it.
DocHoliday77 said:
Hopefully its just the battery.
Download mode may work because of how the battery reports to the os. If its going bad and reporting incorrectly that its low, it may trigger a shutdown. Whereas in download mode the os isn't running so its not reading the battery info the same way. Just a guess.
Click to expand...
Click to collapse
Turns out it was the battery sir. I've tested it with another battery from 2 different phones and it worked fine. While the phone i tested with the defective battery didn't event get passed the samsung logo. I've suspected it might be having the low voltage causing the phone to shut down.
Anyways, after that i bought a new battery immediately and everything seems ok. thanks for the reply doc.
DocHoliday77 said:
Remove battery snd put back in. Does the device try to turn on by itself? If so you probably have a bad power button.
Click to expand...
Click to collapse
I can confirm that it is likely a bad power button, I have tried everything including dismantling it and seeing if I could dislodge any dirt that may be causing the problem but it didn't work. Looks like I have to find a local repair shop or ebay to get it resolved. Anyone recommend a good place to get this fixed. Funds are limited
Im not sure exactly how difficult the repair is most people seem so do it themselves and have given indications that its pretty easy. You can find the part online for a few bucks.
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