any dreaded boot loop issues with the LG G6?

Look like g6 has this again. No idea why people would buy lg after g4, v10, 5x all must have bootloop
That depends.

If it bootlooped after an OTA, then it's a software issue. A reflash will fix it.

In the case of the G4, it's a hardware issue caused by inadequate QC in how they soldered the board.
 
That depends.

If it bootlooped after an OTA, then it's a software issue. A reflash will fix it.

In the case of the G4, it's a hardware issue caused by inadequate QC in how they soldered the board.

I had the same basic thoughts about updates gone bad until today in which I case I did a bit of research on the different reasons phones go into a bootloop after update. Turns out one cause is memory going or gone bad. It is good enough to support the existing OS, however when the update tries to overwrite it fails and causes the phone to hang up and potienally bootloop or hang on startup.
 
I had a G3...had several problems with that, but none of them involved bootlooping. Two just completely died without warning and the third's screen just started acting goofy, fading out and not responding to touch. I skipped the G4 and G5 and am crossing my fingers that LG has dealt with whatever caused it, since now I'm on the G6.

My G3 never bootlooped either - I think that issue missed that iteration for the most part - but yes, hopefully LG has corrected that issue.
 
Went to Verizon store yesterday and every G6 there was hot while plugged in, every other phone in the store all plugged in were cool. Gave me more concerns.
 
Went to Verizon store yesterday and every G6 there was hot while plugged in, every other phone in the store all plugged in were cool. Gave me more concerns.

My phone has never gotten hot.
 
I've had a T-Mobile LG G6 since the week of release and have not experienced boot loop. Very satisfied with the phone.
 
Display models were playing the display video and charging, and do this all day. Was just an observation since I had 3 G4's that bootlooped. I picked up every brand of phone while in the store and all were cool to the touch, the G6's were all very noticeably warm.
 
I kinda want one but I also want something to last for 2 years, I was thinking HTC 10 vs G6 but the g6 is much newer and a better design but sense is just lighter and better.
 
I kinda want one but I also want something to last for 2 years, I was thinking HTC 10 vs G6 but the g6 is much newer and a better design but sense is just lighter and better.

I too am stuck between these two devices for my upgrade. The G6 is now ushering out a two year warranty on their devices, so there's that! It's really exciting!
 
Um, No not trolling, actually went with the Pixel and thought the G6 was a nicer phone, but I had 3 G4's in the family that bootlooped and stuck on the "life's not good screen". After that just felt I would not take the chance. Was only posting an observation when looking at phone's in the store and it made me even more concerned about going with LG again.
 
Last edited:
Mod Note: Lets keep the discussion civil please. If there is a problem with a post then please report it so the Mod team can take a look, attempting to resolve it yourself is not advisable.
Thanks.
 
Um, No not trolling, actually went with the Pixel and thought the G6 was a nicer phone, but I had 3 G4's in the family that bootlooped and stuck on the "life's not good screen". After that just felt I would not take the chance. Was only posting an observation when looking at phone's in the store and it made me even more concerned about going with LG again.

While I can't guarantee anything, I think it would be pretty foolish for LG to make the same mistake 3 times. I think the major bootloops ended with G4 and V10. The G5 has rare reports of bootloops and most reports I've seen are not bootloops or not bootloops of the systemic problem with G4/V10. The same for the V20 and the G6 though they haven't been out as long, especially the G6. The great thing is that LG is offering a two year warranty at least in the US on the G6.
 
I have a G4 and had the bootloop issue. Hardware defect. Had it fixed under warranty by LG, they put in the latest (At the time) mainboard and have has not a single issue since. I absolutely adore the G4.

I was disappointed with the G5 but the G6 i think will be its replacement, just really for the wide angle camera, waterproofing an newer software. My G4 is in immaculate condition and even as I write this I don't know if I really will move to a G6.

So I wouldn't worry at all about a boot loop issue.
 
G4 had an inherent design fault where motherboard cracked when phone got hot. LG acknowledged the fault in several press releases. However they refused to fix my bootloop/motherboard issue as it was an import even though it was a worldwide issue and they admitted to the problem.
 
Well it just happened to me also this week, got my g6 in march when it was first released. Have received a few updates over the months but 3 days ago I woke up and saw a android update available so I installed it. After phone powered down and tried to restart it's stuck in a constant reboot. Took the phone back to sprint store and of course that can't do anything with it. Contacted LG and they said to send it back and they will repair it, 2 weeks minimal. So from what I've read so far throughout this forum is that everyone who has gotten the boot loop problem all received a update prior to the loop. I must say this needs to be addressed as this is not a one time event apparently.
 
Well it just happened to me also this week, got my g6 in march when it was first released. Have received a few updates over the months but 3 days ago I woke up and saw a android update available so I installed it. After phone powered down and tried to restart it's stuck in a constant reboot. Took the phone back to sprint store and of course that can't do anything with it. Contacted LG and they said to send it back and they will repair it, 2 weeks minimal. So from what I've read so far throughout this forum is that everyone who has gotten the boot loop problem all received a update prior to the loop. I must say this needs to be addressed as this is not a one time event apparently.

Unfortunately this can happen during an update and its hard to pinpoint the actual cause.