Related
Hello!
A few months back I rooted my Verizon LG G3 without any issue. Worked great, went smoothly.
Last night I was watching Netflix when the phone suddenly shut off without warning. I haven't recently installed anything out of the ordinary. When I tried to reboot, I got the green screen with a HW reset warning. Pressing Vol down to reboot gave me a blue screen. I'm able to reboot using Power + Vol down, but if I try any of the options [including factory reset] it suddenly goes to the blue screen.
I also tried getting into download mode without any luck - you guessed it: Blue screen. If I connect the phone to a PC, it doesn't recognize it. I've tried downloading and running the LG PC Suite, but it can't connect to the phone.
Any thoughts on what's going on and how I might be able to repair it? I've looked through various threads here and anything similar seems to revolve around flashing gone awry...and I'm not flashing anything (nor do I really have the know-how to do so).
Thanks, in advance, for any assistance.
Andrew
rewkim said:
Hello!
A few months back I rooted my Verizon LG G3 without any issue. Worked great, went smoothly.
Last night I was watching Netflix when the phone suddenly shut off without warning. I haven't recently installed anything out of the ordinary. When I tried to reboot, I got the green screen with a HW reset warning. Pressing Vol down to reboot gave me a blue screen. I'm able to reboot using Power + Vol down, but if I try any of the options [including factory reset] it suddenly goes to the blue screen.
I also tried getting into download mode without any luck - you guessed it: Blue screen. If I connect the phone to a PC, it doesn't recognize it. I've tried downloading and running the LG PC Suite, but it can't connect to the phone.
Any thoughts on what's going on and how I might be able to repair it? I've looked through various threads here and anything similar seems to revolve around flashing gone awry...and I'm not flashing anything (nor do I really have the know-how to do so).
Thanks, in advance, for any assistance.
Andrew
Click to expand...
Click to collapse
Do you get the blue screen when attempting both recovery and download mode?
Blue screen no matter what I do - recovery, download or normal mode. As a matter of fact, now the phone won't attempt to boot at all.
Really strange.
rewkim said:
Blue screen no matter what I do - recovery, download or normal mode. As a matter of fact, now the phone won't attempt to boot at all.
Really strange.
Click to expand...
Click to collapse
I feel you. I started a thread about my issue but sadly no one helped...
Seems like you got a "bricked" phone though Qualcomm phones are theoretically unbrickable.
I was in a worse situation than you, I think my board fried haha, but i'll try my best to help you here
Do you have a custom recovery?
IS there anything else showing on the blue screen? (example: Factory Reset Status)
also does your led flashes?
If you can't boot, or flash through download mode (KDZ and TOT method) I think either your bootloader got messed up (for no apparent reasons apparently) or it's simply a physical defect.
Are you sure your PC doesn't detect your phone's USB after installing the appropriate drivers?
Or does it detect the a device as "QDLoader 9008"?
Bastienhere said:
I feel you. I started a thread about my issue but sadly no one helped...
Seems like you got a "bricked" phone though Qualcomm phones are theoretically unbrickable.
I was in a worse situation than you, I think my board fried haha, but i'll try my best to help you here
Do you have a custom recovery?
IS there anything else showing on the blue screen? (example: Factory Reset Status)
also does your led flashes?
If you can't boot, or flash through download mode (KDZ and TOT method) I think either your bootloader got messed up (for no apparent reasons apparently) or it's simply a physical defect.
Are you sure your PC doesn't detect your phone's USB after installing the appropriate drivers?
Or does it detect the a device as "QDLoader 9008"?
Click to expand...
Click to collapse
I appreciate your help - thank you. For what it's worth, no - there was never any text on my blue screen, and I couldn't ever get it to get into Download Mode. Plugging it in to a computer did nothing except give me a blue screen, and the computer never recognized it as a device.
I ended up getting a replacement G3, so [for now] my troubles are over. Thanks, again, for your help.
(I guess this thread can be closed now.)
Bastienhere said:
I feel you. I started a thread about my issue but sadly no one helped...
Seems like you got a "bricked" phone though Qualcomm phones are theoretically unbrickable.
I was in a worse situation than you, I think my board fried haha, but i'll try my best to help you here
Do you have a custom recovery?
IS there anything else showing on the blue screen? (example: Factory Reset Status)
also does your led flashes?
If you can't boot, or flash through download mode (KDZ and TOT method) I think either your bootloader got messed up (for no apparent reasons apparently) or it's simply a physical defect.
Are you sure your PC doesn't detect your phone's USB after installing the appropriate drivers?
Or does it detect the a device as "QDLoader 9008"?
Click to expand...
Click to collapse
Quick update: I just learned today that a co-worker who also has a G3 (T-Mobile) also got a blue screen last week. He was told that this was a "known issue" with this phone...but they wouldn't provide him with a replacement, which also seemed strange.
rewkim said:
Quick update: I just learned today that a co-worker who also has a G3 (T-Mobile) also got a blue screen last week. He was told that this was a "known issue" with this phone...but they wouldn't provide him with a replacement, which also seemed strange.
Click to expand...
Click to collapse
Glad you got it replaced!!
And a shame for your friend :/
In my case, it was practically hopeless, nothing seemed to work, eventually i had to have the motherboard replaced. It was clearly a damaged bootloader, yet, they repaired it under warranty! funny
I doubt you can damage a bootloader without root or stuff.
I wonder what would suddenly mess with the bootloader after months of no issues?
I'm having the same issue. Or rather I had the same issue but I was able to get it back to stock through all the various .tot methods and using download mode and everything. I had no issues so I rooted it again, installed the 35B firmware from xdabbeb, as well as his 46A so everything is still stock, and running the latest android update, but the phone is still rooted. In any case it has been working fine for almost a week. Today it shut itself off again and now only blue screen when I turn it on. It barely gets past the LG logo before it blue screens again. I can't enter download mode because while installing the device on the PC it blue screens and crashes in download mode.
So I'm not sure what the deal is. I have the extended insurance and warranty but if you pull the battery for a couple hours and put it back in it will boot past the LG screen and start the OS, but the boot loading screen shows "Android" instead of "Verizon" so they'll know it's a custom firmware and do nothing for me. If anyone has any ideas I'm open to them! I would love to revert back to stock but with it crashing in download mode I can't even do that.
try these things but g3 is crap phone
you can try these things: use stock charger and try to boot then, i think its a 2amp charger. if it boots then swapping out battery with good one will likely cure it. its hard to find good new oem batteries though. usually that only works if you see a blue screen with a number on it. if its just a flat blue screen and connected to stock charger wont improve anything then its likely corrupted bootloader (hard brick). i currently am trying to resurrect one that is acting the same, it will only randomly turn on to blue screen, sometimes after days left with battery in while turned off. all the tricks like taking battery out, connecting to charger or computer without battery or holding power button to drain capacitors with batt out dont seem to help really. i am trying to get it to turn on into download mode at which point i will flash stock kitkat but seems like it wont happen. seems like lollipop 5.0 has something to do with this issue. there is an outfit on ebay that fixes it for 29bucks in texas. you will find them on youtube. g3 is crap. g2 was excellent except for touch screen issues.
can you explain what outfit in you are talking about? i am facing the same problem,
Simaramis said:
you can try these things: use stock charger and try to boot then, i think its a 2amp charger. if it boots then swapping out battery with good one will likely cure it. its hard to find good new oem batteries though. usually that only works if you see a blue screen with a number on it. if its just a flat blue screen and connected to stock charger wont improve anything then its likely corrupted bootloader (hard brick). i currently am trying to resurrect one that is acting the same, it will only randomly turn on to blue screen, sometimes after days left with battery in while turned off. all the tricks like taking battery out, connecting to charger or computer without battery or holding power button to drain capacitors with batt out dont seem to help really. i am trying to get it to turn on into download mode at which point i will flash stock kitkat but seems like it wont happen. seems like lollipop 5.0 has something to do with this issue. there is an outfit on ebay that fixes it for 29bucks in texas. you will find them on youtube. g3 is crap. g2 was excellent except for touch screen issues.
Click to expand...
Click to collapse
..
ARYA3 said:
..
Click to expand...
Click to collapse
Sorry "outfit on ebay" means seller on ebay. Don't remember what their name was. With the g3 it's like this: bootloop is usually fixable with a new battery. If it loads with charger connected, then definitely try new battery. If blue screen without a number, it's likely faulty motherboard. It may still boot occasionally, after leaving batt out or putting in freezer (yes freezer). If it does boot then do a backup immediately but phone is likely in need of new motherboard.
http://forum.xda-developers.com/showpost.php?p=70264535&postcount=9
BSOD is not so BSOD as you might think. This is actually the default view of the screen controller. It just means.... well... basicly... you're ****ed....
Something in the hardware doesn't fire up as it should and it's usually the SoC.... or the so called processor. Heating and baking might help if the problem is with low temperature welding but again it might not. And even if it does... it will be totally temporary (most cases weeks) because of the rapid increase/decrease of the processor temperature and thus welding joints... I'm basically in the same situation right now with the same phone... he fought well as it is 2014 phone after all but in the end it died heroically.... ;(
Having a bit of a nightmare day! I have a 855 G3 and have had it around 18 months. Its rooted, and has been running ok.
Today, I was using the phone, then had to do something. When I went back to it, it was off and wont come back on.
I have tried lots of things - removing battery and plugging in, leaving battery out for a while, trying to plug in without battery, holding down various buttons in various sequences, pluging into the PC - and nothing at all.
One time I took the battery off and plugged it in, I did get a display that indicated there was no battery installed. I then put the battery one and a charging screen came up for a few moments, then it went dead again.
Anything else I can try, or has it got to go off for repair?
I saw this http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 but I don't want to do that if I can still get a repair under warranty.
Its bought from Amazon Germany and I have to send it back to them, they are happy to repair it. Is it going to be a problem that its been rooted?
One last question. I need to buy a cheap, but reasonable phone to keep me going in the meantime. Any suggestions? Saw a Moto G 2nd gen.
same thing happened with me as well Mine is US Cellular G3
the diff is
I was trying to boot in recovery ( TWRP , mine was rooted ) but it looked as if TWRP was gone to i pulled battery and restarted and used the native AUTOREC app to reinstall TWRP once done when i tried to boot in recovery
my phone never woke up
and its still in same state
( you were lucky to see charging screen for a few seconds , but i instead just see that empty battery screen when i plug it in without battery , that too goes away once i plug the battery inside
guyz plz help
lord dredd said:
same thing happened with me as well Mine is US Cellular G3
the diff is
I was trying to boot in recovery ( TWRP , mine was rooted ) but it looked as if TWRP was gone to i pulled battery and restarted and used the native AUTOREC app to reinstall TWRP once done when i tried to boot in recovery
my phone never woke up
and its still in same state
( you were lucky to see charging screen for a few seconds , but i instead just see that empty battery screen when i plug it in without battery , that too goes away once i plug the battery inside
guyz plz help
Click to expand...
Click to collapse
I think I have tried everything now. Ordered a new battery to try, which should arrive in the next few hours but I am not holding my breath. So, looks like its got to go back to Germany and hopefully they will repair or replace it!
superdon said:
I think I have tried everything now. Ordered a new battery to try, which should arrive in the next few hours but I am not holding my breath. So, looks like its got to go back to Germany and hopefully they will repair or replace it!
Click to expand...
Click to collapse
Too bad , and yes believe me new battery might not solve it , but then keep your fingers crossed.
all the best
New battery just arrived. So, I put it in and it started to boot! The LG logo came up, I got excited and then....bang turned off! Very strange.
Sort of the same happened to me today. Let's hope is battery.
My G3 shut down suddenly although battery was at apologize 75%, blue screen and splash logo and flickering and then black screen.
After some time I managed to boot up and then 2-3 minutes later...off again. Repeating procedure, booting up and then immediately booting twrp. I thought something is wrong with my setup: fulmics 3.7 and xceed kernel latest nightly; managed to restore a backup (stock rooted MM) and everything was fine.
Phone boot up normally, apps beginning to update, made a few calls...and then...boom...shut down with the same flickering to blue screen. I hope is battery issue related. My phone is from August of 2014 and a bit abused since December (MM update).
superdon said:
Having a bit of a nightmare day! I have a 855 G3 and have had it around 18 months. Its rooted, and has been running ok.
Today, I was using the phone, then had to do something. When I went back to it, it was off and wont come back on.
I have tried lots of things - removing battery and plugging in, leaving battery out for a while, trying to plug in without battery, holding down various buttons in various sequences, pluging into the PC - and nothing at all.
One time I took the battery off and plugged it in, I did get a display that indicated there was no battery installed. I then put the battery one and a charging screen came up for a few moments, then it went dead again.
Anything else I can try, or has it got to go off for repair?
I saw this http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 but I don't want to do that if I can still get a repair under warranty.
Its bought from Amazon Germany and I have to send it back to them, they are happy to repair it. Is it going to be a problem that its been rooted?
One last question. I need to buy a cheap, but reasonable phone to keep me going in the meantime. Any suggestions? Saw a Moto G 2nd gen.
Click to expand...
Click to collapse
Same here, no recovery, no download mode, nothing... I've tried shorting the pins and using boardiag (tests are all PASS except for SDRAM which I've been told it needs a power source to boot the device a.k.a battery ) so i highly suspect it's a battery thing
Sent mine back today. Got a Moto G to keep me going in the meantime.
Mine is now on the way back to me after a quick turnaround. Not sure what they have done to repair as can't log on to the repair tracking website for some reason, but will find out next week when it arrives.
Still waiting, but I now have the repair report. The phone they are sending back has a different serial number, so I presume they are sending a new/refurb phone?
I've sent my phone(with the same symptoms) last week in service under warranty although it was rooted and from service center I have a tracking information that it was repaired (probably mobo replaced). So, I will know for sure in a couple of days
Try connecting it to PC without battery, you notatras that it decteta pc , if so you are lucky , you step tutorial, the files are only for d855
https://mega.nz/#!6Zt0iDCC!dh5K-THYZp0nk-cIjgQ-zX1rBJ6Lhu_c0cv30mpT7Gs
instructions in Spanish , a question shout
So yesterday I was trying to make a phone call and the phone went dead. I tried turning it back on but to no avail. When connected to a charger, it just shows the battery for a while and then it disappears and reboots to showing it again only to reboot itself again. Needless to say, I am stuck with a bricked phone. I managed to get it up and running by flashing the stock rom but after update to Android 7.0 the problem came back after like 10 hours. Now I can't even get into bootloader without the phone being connected to a charger, which is a problem because I can't flash anything through charger obviously. Connecting the phone through USB does not work, the phone stays dead like it is out of juice. With that being said I think it might be a faulty bootloader. The power button is fine, so I think we can count this option out. Any other ideas? I am considering taking the phone to the shop where I bought it as it is still under warranty but because it is not Google they might refuse to replace it with a new one or repair it. Is there anything I can do?
EDIT: I sent it to LG.
kubatbg said:
So yesterday I was trying to make a phone call and the phone went dead. I tried turning it back on but to no avail. When connected to a charger, it just shows the battery for a while and then it disappears and reboots to showing it again only to reboot itself again. Needless to say, I am stuck with a bricked phone. I managed to get it up and running by flashing the stock rom but after update to Android 7.0 the problem came back after like 10 hours. Now I can't even get into bootloader without the phone being connected to a charger, which is a problem because I can't flash anything through charger obviously. Connecting the phone through USB does not work, the phone stays dead like it is out of juice. With that being said I think it might be a faulty bootloader. The power button is fine, so I think we can count this option out. Any other ideas? I am considering taking the phone to the shop where I bought it as it is still under warranty but because it is not Google they might refuse to replace it with a new one or repair it. Is there anything I can do?
EDIT: I sent it to LG.
Click to expand...
Click to collapse
I had the same issue just a few weeks ago, did you ever get it back? How long did it take? Was covered under warranty?
Thanks - Ed
I just unlocked my phone and swiped down to check notifications. It immediately froze and the screen stayed on for awhile. Then the screen went black and I can't get the phone to start up. Tried holding power for a real long time and also volume down + power but still can't get it to start up. After messing with it for awhile I got it to briefly show the boot screen once and then once more I had it in the bootloader and I was able to scroll through the boot options but when I tried booting to recovery it died again. Connected to my computer the device manager sometimes shows it as "Qualcomm HS-USB QDLoader 9008". Any ideas if there's anything else I can try, or am I totally screwed?
I'm sorry to hear this, but is the known bootloop problem with hardware. It's caused by loosing solder balls on CPU. The best option tries to RMA, if you have a warranty.
That's what mine did. I was able to put it in the freezer and get a little life out of it, but never booted all the way. I used the hair dryer (following youtube videos on using a heat gun) heating of the CPU and motherboard and got some life out of it, but not a full boot.
So I bought a heat gun and got it to boot and for me to take most of the data off of it. Then it had issues, so I did a longer heating and it booted and acted normally. I thought it was actually fixed. But after 9 hours of acting like is was normal, it rebooted itself. It lasted for a while, then rebooted and lasted less time, and the cycle reduced really quickly to just bootlooping. I gave the heat gun one more try and pressed the CPU down with a wooden spoon to see if that made a difference, but it started the reboot cycle maybe 30 minutes into trying to set it back up. Google replaced mine though it was a few months past the end of the 12 month warranty since I bought it from them.
LG is extending the warranty on the 5X on a case by case basis. So you should give them a try.
Thanks guys. I did get it to boot into the bootloader a couple more times last night, but I wasn't able to get it to do anything meaningful. Whenver I tried booting to system or recovery it just hung up on the Google screen. I have it boxed up now and looks like it's going back to LG again.
UPDATE: Got an update from LG that my phone is undergoing repair. When I started the RMA and gave my IMEI they warned me the phone may not be under warranty. But according to the update they sent me they're indicating that it is covered under warranty - so apparently it's true that they're extending warranties to cover the hardware boot loop issues from faulty solder connections. Hopefully they'll even send my phone back with the SIM tray this time...
My G4 was plugged in overnight to charge, and on the following day, I woke up to notice it was completely dead. Strange I thought because it wouldn't respond to anything (recovery/download mode, normal boot, etc.). I assumed it was just the battery's time to die so I ordered a new one off Amazon (PowerBear). I put it in the phone, and it started turning on. Whew, it's back... Right? Suddenly, the screen shuts off during the LG boot logo (before the animation). WTF? Now I'm back at square one. Phone doesn't respond to anything. A couple battery tricks where I take it out and hold the power button for 30 seconds can sometimes get it to show the empty battery screen when connected to my computer, but even that's very rare. If I try putting the battery in at this part, it shows a battery loading animation and then the phone freezes indefinitely.
I've tried multiple USB cables, computers, and A/C adapters. No matter what, I can't get the phone into recovery or download mode. My computers can detect the correct driver as the phone is dead but it still won't work in LGUP. I've also returned the PowerBear battery, arguably prematurely.
If it's of any relevance, I had my G4 screen replaced by a third-party repair store a month prior to this incident, and I find it hard to believe it's just a coincidence my phone dies not too long after. Based off what I know, this isn't a bootloop issue. My friend who works at another repair shop insists it's the motherboard but can't fix it since they no longer have an LG technician. However, before all this, my Android OS was acting super funky - "Android is upgrading 300 apps..." for 20mins upon each reboot, despite it being the latest software, and my data limits had a glitched out schedule where it thought the phone was in the year 2023 despite date/time being set correctly. I had plans to reset the software but not being able to boot the phone anymore has prevented it, obviously.
According to the serial number, the phone was manufactured in November 2015, which I believe is past the date of when the faulty G4s were distributed. So what gives!?
The freakiest part of this is that my iPhone 7 Plus - which was at 100% battery (unplugged) before I fell asleep, was completely drained when I woke up on the same day. I also have no idea what that's about.
Any and all replies are appreciated. Thanks for reading!
SuperGlueG4 said:
My G4 was plugged in overnight to charge, and on the following day, I woke up to notice it was completely dead. Strange I thought because it wouldn't respond to anything (recovery/download mode, normal boot, etc.). I assumed it was just the battery's time to die so I ordered a new one off Amazon (PowerBear). I put it in the phone, and it started turning on. Whew, it's back... Right? Suddenly, the screen shuts off during the LG boot logo (before the animation). WTF? Now I'm back at square one. Phone doesn't respond to anything. A couple battery tricks where I take it out and hold the power button for 30 seconds can sometimes get it to show the empty battery screen when connected to my computer, but even that's very rare. If I try putting the battery in at this part, it shows a battery loading animation and then the phone freezes indefinitely.
I've tried multiple USB cables, computers, and A/C adapters. No matter what, I can't get the phone into recovery or download mode. My computers can detect the correct driver as the phone is dead but it still won't work in LGUP. I've also returned the PowerBear battery, arguably prematurely.
If it's of any relevance, I had my G4 screen replaced by a third-party repair store a month prior to this incident, and I find it hard to believe it's just a coincidence my phone dies not too long after. Based off what I know, this isn't a bootloop issue. My friend who works at another repair shop insists it's the motherboard but can't fix it since they no longer have an LG technician. However, before all this, my Android OS was acting super funky - "Android is upgrading 300 apps..." for 20mins upon each reboot, despite it being the latest software, and my data limits had a glitched out schedule where it thought the phone was in the year 2023 despite date/time being set correctly. I had plans to reset the software but not being able to boot the phone anymore has prevented it, obviously.
According to the serial number, the phone was manufactured in November 2015, which I believe is past the date of when the faulty G4s were distributed. So what gives!?
The freakiest part of this is that my iPhone 7 Plus - which was at 100% battery (unplugged) before I fell asleep, was completely drained when I woke up on the same day. I also have no idea what that's about.
Any and all replies are appreciated. Thanks for reading!
Click to expand...
Click to collapse
All devices up to March 2016 (so 603) are affected by the ilapo. Your story above sounds exactly like the ilapo. Read my signature for the ilapo fix list which may bring up some hours/days/months life back.
Sent from my LG-H815 using XDA Labs
SuperGlueG4 said:
My G4 was plugged in overnight to charge, and on the following day, I woke up to notice it was completely dead. Strange I thought because it wouldn't respond to anything (recovery/download mode, normal boot, etc.). I assumed it was just the battery's time to die so I ordered a new one off Amazon (PowerBear). I put it in the phone, and it started turning on. Whew, it's back... Right? Suddenly, the screen shuts off during the LG boot logo (before the animation). WTF? Now I'm back at square one. Phone doesn't respond to anything. A couple battery tricks where I take it out and hold the power button for 30 seconds can sometimes get it to show the empty battery screen when connected to my computer, but even that's very rare. If I try putting the battery in at this part, it shows a battery loading animation and then the phone freezes indefinitely.
I've tried multiple USB cables, computers, and A/C adapters. No matter what, I can't get the phone into recovery or download mode. My computers can detect the correct driver as the phone is dead but it still won't work in LGUP. I've also returned the PowerBear battery, arguably prematurely.
If it's of any relevance, I had my G4 screen replaced by a third-party repair store a month prior to this incident, and I find it hard to believe it's just a coincidence my phone dies not too long after. Based off what I know, this isn't a bootloop issue. My friend who works at another repair shop insists it's the motherboard but can't fix it since they no longer have an LG technician. However, before all this, my Android OS was acting super funky - "Android is upgrading 300 apps..." for 20mins upon each reboot, despite it being the latest software, and my data limits had a glitched out schedule where it thought the phone was in the year 2023 despite date/time being set correctly. I had plans to reset the software but not being able to boot the phone anymore has prevented it, obviously.
According to the serial number, the phone was manufactured in November 2015, which I believe is past the date of when the faulty G4s were distributed. So what gives!?
The freakiest part of this is that my iPhone 7 Plus - which was at 100% battery (unplugged) before I fell asleep, was completely drained when I woke up on the same day. I also have no idea what that's about.
Any and all replies are appreciated. Thanks for reading!
Click to expand...
Click to collapse
You need a new battery
deltadiesel said:
You need a new battery
Click to expand...
Click to collapse
Lol
Sent from my LG-H815 using XDA Labs
I had something similar happen, except it is a 2016 model, I believe, to sum it up:
The battery seemed to be starting to die, so I bought a battery of eBay, but it also was having pretty bad battery life, so I drained the battery, to calibrate it, but now my G4 (H812) refuses to show any sign of life when I plug it in, or try to turn it on, is it also the Ilapo/Bootloop issue, or something else?