Good After Noon,
Recently LG Released a new android update, (6.0.0) The phone will send you a prompt that says. "ANDRIOD UPDATE 6.0.0"
Before I get into explaining this major issue I'm going to give you guys a run through on what android updates go through before it finally reaches your device.
Lets begin. The update is developed by android, then this update has to go through several inspections before it can be sent off to the service providers.
Once the update passes all of its required inspections it is sent out to each phone brand, HTC, SAMSUNG, LG, & so on and so forth, once the phone brands receives
the update, they edit the released android update to fit there devices expectations. Once each phone brand completes editions, then they send the updates to each service provider
that sells there phone brand, that's a lot of sending.
Now the major issue!
Hopefully you have read everything mentioned above to help you understand the cause of the Bootloop.
The way you could tell if the bootloop issue was caused by the update is if the bootloop started occurring shortly after updating to 6.0.0, & if your reading this because you are experiencing bootloop issues at this moment after doing the update then try this method to see if the phone will completely boot, Just simply plug you phone into the wall charger, now once you do this if the LG G3 comes out of bootloop and boots up normally then the culprit was the update, now to be sure if the update was the culprit, just simply unplug your LG G3 from the charger, now if it goes back into a non-stop bootloop. the Update was your culprit!
The reason this bootloop happened is because the android update 6.0.0 had a major corrupted file, how did this corrupted file end up in the update, well it's pretty simple, once the update was sent to the phone brand (LG) they went in and edited the update to there likings and at some point in that process they miscoded a file or wrote over a file which in result caused the phone to bootloop, Which tells me that the file that was miscoded or wrote over could have possibly been the file that prompts the phone to boot up, the boot up process takes the most power usage then any other process a phone is able to do, which means the phone will pull power from the battery until all files have been successfully complete, if the file is corrupted then the phone will boot until it receives the corrupted file then it will shut down and keep repeating that process, then the battery gets a memory and all it know to do is boot reboot boot reboot, which is known as bootloop. the way to fix this problem is to order a replacement battery, then the phone will boot normally. just be sure before putting the new battery in, plug the phone in the wall while still using the bad battery, backup all of your, and do a factory reset, this will put the phone back to normal and it will delete the corrupted file, the phone will work perfect. I put money on it.
Related
Got the OTA Lollipop update today via the Software Centre in the phone. Downloaded and proceeded to install the update V20e-DEC-03-2014 and everything was going fine until I got to Updating Software (2/2) at 90% when the thing just stays there, then this jumbled text appears (attached image) and then it'll reboot back to this screen. And it just keeps doing so every few minutes.
Now I'm stuck in this cycle, and I can't seem to get out of it. Please help!
derrickflc said:
Got the OTA Lollipop update today via the Software Centre in the phone. Downloaded and proceeded to install the update V20e-DEC-03-2014 and everything was going fine until I got to Updating Software (2/2) at 90% when the thing just stays there, then this jumbled text appears (attached image) and then it'll reboot back to this screen. And it just keeps doing so every few minutes.
Now I'm stuck in this cycle, and I can't seem to get out of it. Please help!
Click to expand...
Click to collapse
Okay first off, were you rooted or Bump'd? That shouldn't have caused what appears to be the start of some sort of kernel panic, but it may be an underlying issue. It may also have just been a bad download that flashed incorrectly. Either way, try returning to stock and taking the OTA straight from the stock rom if you dont care about rooting or running custom roms. Otherwise, immediately root and Bump your phone after returning to stock and never ever take an OTA update as it could seriously screw you up. With all that said, here is the link to return your G3 to stock, just be sure to choose your exact model number correctly.
http://forum.xda-developers.com/showthread.php?t=2799647
If you don't know what your model number is, take off your battery cover, remove the battery, check the model from the info sticker and verify that it matches the numbers posted around the inside edge of the phone (D850, vs985, ls990, D855, F400k, something like that).
Hi all,
I've done a bit of a search on this problem but everyone I stumble across is slightly different and unique to them.
So I was on rooted stock kitkat, (v10h I believe from memory) received the lollipop OTA but held out for a while.
Decided to go ahead, backed everything up and plugged it into LG PC Suite.
Started off with a Restore Upgrade Errors to attempt to unroot and get back to stock before trying to v20f update. But I never got that far. It popped up saying update failed with an option to retry, but that also failed and then just got stuck at 0%.
So my situation now:
Turning the phone on goes straight to the Firmware Update screen. Holding down either of the volume buttons at boot makes no difference.
It is recognised by my computer, but not as an actual device. Just that something has been plugged in somewhere (it beeps). LG PC Suite no longer recognises the phone.
What are my options?
Thanks all,
Update
I left it plugged into the PC stuck in "Firmware Update" screen.
LG PC Suite did not identify and connect to the device, so the possibility of a firmware upgrade was ruled out. However there was still a manual option to "Restore Upgrade Errors"
I tried this, and had to enter the phones IMEI and what OS it was currently running (ranging from Froyo to Kitkat, so I selected Kitkat) while LG PC Suite attempted to download the correct software (presumably pulling a .kdz from its servers?).
It was taking a long time, and I was unhopeful of any recovery due to the apparent lack of communication between phone and computer. So I left it and went for lunch.
Upon returning, much to my surprise, LG PC Suite has closed itself down. But my phone was displaying the "Android is upgrading" in Lollipop-esque font. Looking promising I thought...
5 minutes later and all my apps have optimised, my D855 has booted into fully fledged Lollipop! V20f!
So after a brief scare, everything seems to be resolved for now!
I have the same problem but i cant even install the MTP device driver I'll let you know if it worked for me.
RichardW1992 said:
I left it plugged into the PC stuck in "Firmware Update" screen.
LG PC Suite did not identify and connect to the device, so the possibility of a firmware upgrade was ruled out. However there was still a manual option to "Restore Upgrade Errors"
I tried this, and had to enter the phones IMEI and what OS it was currently running (ranging from Froyo to Kitkat, so I selected Kitkat) while LG PC Suite attempted to download the correct software (presumably pulling a .kdz from its servers?).
It was taking a long time, and I was unhopeful of any recovery due to the apparent lack of communication between phone and computer. So I left it and went for lunch.
Upon returning, much to my surprise, LG PC Suite has closed itself down. But my phone was displaying the "Android is upgrading" in Lollipop-esque font. Looking promising I thought...
5 minutes later and all my apps have optimised, my D855 has booted into fully fledged Lollipop! V20f!
So after a brief scare, everything seems to be resolved for now!
Click to expand...
Click to collapse
I intended rooting my LG G3 S with STOCK Lollipop with LG Root Script v1.2.
Never did it before, so when I started the script I though it was done after first part completed and phone screen became normal. So I closed the LG Root Script v1.2 before it finished it's job. Next thing I notice my phone rebooted and it went into Firmware update.
There was no progress, buttons didn't work, my computer detected the device was unplugged/plugged back in, adb didn't detect the device anymore, so thankfully I found your post and used the LG Suite to start Restore upgrade errors which after it analyzed and downloaded fixed my phone within an hour automatically
Hoping someone can help me here.
My wife has a G3 that started acting up back in September or so. It would randomly turn off and reboot, usually while not even touching it. Did some looking around and found that the Facebook Messenger app could cause some instability. Removed the app, all was good for a couple of weeks before it started again. This time, we backed everything up, did a factory reset, all was good for about a week. Reboots started again so I did a hard reset from Recovery. Booted up, everything was good again for about a week again before the reboots started up. The wife ended up giving up on it and went back to her Galaxy S3.
I've been messing around with it today. Phone has been stuck in a boot loop at the LG logo. Battery is fully charged. I followed some guides and downloaded the V10c stock firmware TOT file, dated June 20th, 2014 and LGD851_20140611_LGFLASHv160.dll and loaded them up into LGFlashTool v1.8.1. Installed fresh LG drivers on my Win7 PC, followed the flashing instructions to the letter using a USB 2.0 port (as I read somewhere that 3.0 ports have caused issues on some devices). Everything flashes 100%, flash tool reads complete, phone shows a big 3 on the screen with a blue background. Unplug and reboot the device and it's right back to a boot loop at the LG logo.
Now at one point, during the flashing process, it would boot into LG MiniOS 3.1 and I was able to choose an option (chose Normal Boot) and it would go back into the boot loop. Also, I connected it to my Ubuntu machine just to see what would happen and I received an error "Unable to mount LGE Android Phone. Unable to open MTP device", which makes sense. However, the phone itself would get to the T-Mobile logo and briefly jump into the initial setup of the phone before jumping back to the LG logo and starting over again. Connecting back to my Win7 machine, it just boot loops unless I have the flash tool running. Not having USB connected, it just boot loops.
I'm at a loss here. I can usually muddle my way through these kind of things but this one has me completely stumped. Ordinarily, I wouldn't worry much about this but she's wanting to get a new phone through T-Mobile's JUMP program and we can't do that if the phone won't even boot.
Any help would be appreciated.
Valorendk said:
Hoping someone can help me here.
My wife has a G3 that started acting up back in September or so. It would randomly turn off and reboot, usually while not even touching it. Did some looking around and found that the Facebook Messenger app could cause some instability. Removed the app, all was good for a couple of weeks before it started again. This time, we backed everything up, did a factory reset, all was good for about a week. Reboots started again so I did a hard reset from Recovery. Booted up, everything was good again for about a week again before the reboots started up. The wife ended up giving up on it and went back to her Galaxy S3.
I've been messing around with it today. Phone has been stuck in a boot loop at the LG logo. Battery is fully charged. I followed some guides and downloaded the V10c stock firmware TOT file, dated June 20th, 2014 and LGD851_20140611_LGFLASHv160.dll and loaded them up into LGFlashTool v1.8.1. Installed fresh LG drivers on my Win7 PC, followed the flashing instructions to the letter using a USB 2.0 port (as I read somewhere that 3.0 ports have caused issues on some devices). Everything flashes 100%, flash tool reads complete, phone shows a big 3 on the screen with a blue background. Unplug and reboot the device and it's right back to a boot loop at the LG logo.
Now at one point, during the flashing process, it would boot into LG MiniOS 3.1 and I was able to choose an option (chose Normal Boot) and it would go back into the boot loop. Also, I connected it to my Ubuntu machine just to see what would happen and I received an error "Unable to mount LGE Android Phone. Unable to open MTP device", which makes sense. However, the phone itself would get to the T-Mobile logo and briefly jump into the initial setup of the phone before jumping back to the LG logo and starting over again. Connecting back to my Win7 machine, it just boot loops unless I have the flash tool running. Not having USB connected, it just boot loops.
I'm at a loss here. I can usually muddle my way through these kind of things but this one has me completely stumped. Ordinarily, I wouldn't worry much about this but she's wanting to get a new phone through T-Mobile's JUMP program and we can't do that if the phone won't even boot.
Any help would be appreciated.
Click to expand...
Click to collapse
Good afternoon, my recommendation is that flashes with lg flash tool 2015. All you need is your phone updated driver installed on your pc. Further, you need to download the KDZ (firmware of your stock rom) corresponding to your model. Look at the XDA thread as do or YouTube. If you need more help, you can consult here.
cesarandres_8911 said:
Good afternoon, my recommendation is that flashes with lg flash tool 2015. All you need is your phone updated driver installed on your pc. Further, you need to download the KDZ (firmware of your stock rom) corresponding to your model. Look at the XDA thread as do or YouTube. If you need more help, you can consult here.
Click to expand...
Click to collapse
IIRC, he's talking about going back to the latest stock firmware available from LG and flashing with with @quangnhut123's flash tool.
Thanks for both of your help on this. I actually had given up on the phone for a while. The last time I flashed, it was allowing me to get into the first time setup but wouldn't let me complete setup before rebooting. So I ordered a new battery and everything is working like it's brand new. Thanks again!
I'm stuck and confused:
Had a Nexus 4 and 5 for years. Decided to upgrade this past November to the LG G4 (T-Mobile H811)
Got it to root without touching the boot loader.
In came MM and then I had issues of repeating the process.
I came across a solution, to unlock my bootloader. So I did it and managed to get my G4 rooted while running stock LG MM (H81120i).
Everything was running well for several months, but then I started to see erratic behavior. It would heat-up in my pocket for no reason. It would not save pictures. Connections via WiFi and LTE were breaking up. All in all, I wasn't happy and I missed the stock Google interface.
So I've decided to install CM13. Had many issues of getting it to work for several days, which included persistent closings of Google Play services (and many others) and not being able to make/receive calls (it would automatically reboot) After several different attempts, I managed to get it all working. Cleared/Wiped everything off my internal drive, installed the "LG-H81120i-Flashable.COMPLETE" and "cm-13.0-201605xx-NIGHTLY-h811" and "open_gapps-arm64-6.0-nano-201605xx", all back to back. And then installed manual everything as needed Gmail, Maps, etc.
Everything worked great for about 2-days, until then next morning my screen locked up. Then the phone rebooted. After the reboot, it lasted for about 10-15 seconds in CM13 and rebooted again manually. Continued to reboot over and over, till it then stopped booting with CM13. I thought that maybe I needed to install the latest CM13 zip file, but found I couldn't get into recovery. The first reboot screen, showing "Bootloader State: Bootloader unlocked? and the LG logo would be in a loop. During that time, I could feel the phone getting hotter and hotter.
Sometimes, the phone would boot up into CM fully and last for 5 to 10 minutes. Then reboot again and stay in the first reboot screen.
I managed to get into TWRP recovery and thought that putting back the stock MRA58K image would help. During the install in recovery, the phone rebooted! I never thought it could do that. Eventually I got the stock LG back-up up and running, but it didn’t help, and same rebooting occurred.
I'm stuck and out of options. I would like to get the phone BACK TO STOCK and then perform an RMA. I’m afraid that with the BOOTLOADER UNLOCKED that my RMA will be denied and I’m stuck with what I have.
So can the H811's bootloader be re-locked?
PiCASSiMO said:
I'm stuck and confused:
Had a Nexus 4 and 5 for years. Decided to upgrade this past November to the LG G4 (T-Mobile H811)
Got it to root without touching the boot loader.
In came MM and then I had issues of repeating the process.
I came across a solution, to unlock my bootloader. So I did it and managed to get my G4 rooted while running stock LG MM (H81120i).
Everything was running well for several months, but then I started to see erratic behavior. It would heat-up in my pocket for no reason. It would not save pictures. Connections via WiFi and LTE were breaking up. All in all, I wasn't happy and I missed the stock Google interface.
So I've decided to install CM13. Had many issues of getting it to work for several days, which included persistent closings of Google Play services (and many others) and not being able to make/receive calls (it would automatically reboot) After several different attempts, I managed to get it all working. Cleared/Wiped everything off my internal drive, installed the "LG-H81120i-Flashable.COMPLETE" and "cm-13.0-201605xx-NIGHTLY-h811" and "open_gapps-arm64-6.0-nano-201605xx", all back to back. And then installed manual everything as needed Gmail, Maps, etc.
Everything worked great for about 2-days, until then next morning my screen locked up. Then the phone rebooted. After the reboot, it lasted for about 10-15 seconds in CM13 and rebooted again manually. Continued to reboot over and over, till it then stopped booting with CM13. I thought that maybe I needed to install the latest CM13 zip file, but found I couldn't get into recovery. The first reboot screen, showing "Bootloader State: Bootloader unlocked? and the LG logo would be in a loop. During that time, I could feel the phone getting hotter and hotter.
Sometimes, the phone would boot up into CM fully and last for 5 to 10 minutes. Then reboot again and stay in the first reboot screen.
I managed to get into TWRP recovery and thought that putting back the stock MRA58K image would help. During the install in recovery, the phone rebooted! I never thought it could do that. Eventually I got the stock LG back-up up and running, but it didn’t help, and same rebooting occurred.
I'm stuck and out of options. I would like to get the phone BACK TO STOCK and then perform an RMA. I’m afraid that with the BOOTLOADER UNLOCKED that my RMA will be denied and I’m stuck with what I have.
So can the H811's bootloader be re-locked?
Click to expand...
Click to collapse
Since you live in the US your only option is to apply over voltage to the battery terminal and burn the mobo so that it wont even boot up. The exact method is somewhere around here in xda so you should look it up since you have no other choice
Edit: To answer your question: No
sirsomething said:
Since you live in the US your only option is to apply over voltage to the battery terminal and burn the mobo so that it wont even boot up. The exact method is somewhere around here in xda so you should look it up since you have no other choice
Edit: To answer your question: No
Click to expand...
Click to collapse
If I can't re-lock the bootloader, has anyone had the success of returning their phones under warranty? Through T-Mobile?
Okay, So let me start from the beginning so I'm certain I'm being descriptive enough.
The other night my G3's wifi stopped working. When I went to turn it on in settings it would turn itself back off. Which I thought was strange. So, I assumed it was a software issue so I backed up any important items and factory reset my phone last night. That went over fine. Wifi worked again, all was good. Until, it said it needed an Android Software Update. I hit "update" and allowed it to do its thing. About halfway through the update the phone said "error." With an icon of the Android bot with a hazard triangle sticking out from it. I let it be for a bit and nothing happened. So in my impatience I took the battery out and put it back in and tried to restart the phone. This is where the issue occurs. The phone keeps booting to recovery mode. I'm not savvy at all with Android so I don't know if these mean anything but it says "Android System Recovery <3e> LRX21Y" The phone has had zero modifications done to it. I would really appreciate any help or any tutorials that could save the phone until my g6 preorder comes in.
Thanks!
Kyle
Your phone failed the update for some weird reasons and is now stuck. I'm afraid you'll need to restore stock Android using LG Flash tools and KDZ files to your device. It will get your phone working, but you'll lose your data in the process.
You can try mounting the phone from recovery or download mode and see if you can access your data and backup the data. You can also try the recovery option without downloading wnloaing a KDZ first.
You can fins tutorials around the forum, in the general section usually.