Develop Bugs

LG G4 weird bootloop

I was regularly using my G4, it was on cyanogenmod 13 nightlys for a good while now and i updated it every week or so. (haven't updated it in at least 10 days this time but it shouldn't be an issue) Suddenly the device turned itself off and went into a bootloop. I found a couple of weird things with this bootloop.
1. it wont boot into the device ever. it just shows the LG logo for a few seconds, goes black for a second then repeat.
2. I cant enter recovery mode, i used the button combination and go to the "factory reset" screen, selected 'yes' twice and i should have been sent to TWRP, which i have installed. But instead it just took a while on the yes/no screen and then blacked out, and rebooted back into the loop.
3. Sometimes it goes a bit further in the loop, and gets a little into the boot animation i have. I found that letting it run a longer time gets me a higher chance to see my little boot animation.
ive heard there was a hardware issue with LG G4's that were bought back in September of 2015 but i bought mine in June last year so i don't think that's the issue.
i didn't backup my phone for a long time so i'd love to get my files back! (otherwise I'm getting a new phone in a couple of days but i still need it until then)
Any and all help will be greatly appreciated! thanks!

What is your phone's S/N?
Sent from my LG-H815 using Tapatalk

I have the exact same problem, my phone died like this yesterday. The colder the phone is the longer it runs without rebooting so that might be a hint for you, although i have never seen it boot up completely. Maybe you can put it in the freezer or something like that. I was lucky because i just switched to cm13 and make backups of all my data the day before.

joelalmeidaptg said:
What is your phone's S/N?
Click to expand...
Click to collapse
no idea. I know it hits some within a specific range but i did check the back of the phone where the battery is and it says there H815 0506 twice H815 0430 once and H815 0508 and H815 0501 both once. Does this mean anything? how can i check the S/N if its in a loop?
helgenet said:
I have the exact same problem, my phone died like this yesterday. The colder the phone is the longer it runs without rebooting so that might be a hint for you, although i have never seen it boot up completely. Maybe you can put it in the freezer or something like that. I was lucky because i just switched to cm13 and make backups of all my data the day before.
Click to expand...
Click to collapse
heard about that, i didnt try freezer because that sounds kinda stupid and i dont feel safe doing it but i put it in front of my A/C and it cooled down but i dont think it made any special change.

SynderBlack said:
no idea. I know it hits some within a specific range but i did check the back of the phone where the battery is and it says there H815 0506 twice H815 0430 once and H815 0508 and H815 0501 both once. Does this mean anything? how can i check the S/N if its in a loop?
I saw my S/N in the box the phone came in, right above the IMEI (mine is 602).
Click to expand...
Click to collapse

I'm sorry but it seems you both have THE bootloop problem not a weird bootloop.. It does affect many more than "bought in September" devices. Actually more of the June devices..
Sorry.

joelalmeidaptg said:
I saw my S/N in the box the phone came in, right above the IMEI (mine is 602).
Click to expand...
Click to collapse
EPa said:
I'm sorry but it seems you both have THE bootloop problem not a weird bootloop.. It does affect many more than "bought in September" devices. Actually more of the June devices..
Sorry.
Click to expand...
Click to collapse
just checked the box, mines 506.
Damn that sucks! Any way confirmed to fix this issue? I dont think warranty will fix a boot loader unlocked phone.

SynderBlack said:
just checked the box, mines 506.
Damn that sucks! Any way confirmed to fix this issue? I dont think warranty will fix a boot loader unlocked phone.
Click to expand...
Click to collapse
People in the US and some European countries (ie Germany) didn't have a problem getting it fixed under warranty despite unlocked bootloader, root or even custom roms (because it's a known hardware issue unrelated to software).
Others did.
Try, you got nothing lose..
As for a fix, there is a process that involves disabling CPU cores, has worked for some. Check http://forum.xda-developers.com/showthread.php?p=67149552

EPa said:
People in the US and some European countries (ie Germany) didn't have a problem getting it fixed under warranty despite unlocked bootloader, root or even custom roms (because it's a known hardware issue unrelated to software).
Others did.
Try, you got nothing lose..
As for a fix, there is a process that involves disabling CPU cores, has worked for some. Check http://forum.xda-developers.com/showthread.php?p=67149552
Click to expand...
Click to collapse
I bought the phone as an international phone from a phone store. I dont have an LG center here and if i try to ask the store to fix it under warrently i'll probably get turned down because the bootloader is unlocked (you can clearly see that in the LG screen)
I will try talking to them but with ~20 days of warranty remaining i doubt my success chances are high

I brought mine from a phone store unlocked too (Carphone Warehouse in the UK) and it also had an unlocked bootloader running Cm13.
When it started suffering the bootloop problem they repaired it no questions asked. Worth a go.

Mine done that but wouldn't turn on after I took battery out I didn't try asking on here but no luck so I took it to insurance and I ended up with the g5 as they had no g4 repaired and ready to come back to me in 24 hours lol. Carphone warehouse ? big thanks to them now to wait for g5 to get some good stuff ... ?
Sent from my LG-H850 using Tapatalk

Request: remove 'bootloader unlocked' warning

After unlocking the bootloader, you're stuck with a message, everytime you reboot your phone, which gives you a warning that the bootloader is unlocked. Quite annoying if you ask me, especially because it takes 5 seconds before the phone continues to reboot.
Is there somebody who can remove that warning? It's already done for the motorola G4, so I guess it shouldn't be to difficult for the OP3, as long as somebody with a little bit of know how takes a look into this issue.
Somebody here who can make this happen?

wait for this mod
so annoying

Yeah will wait for this one

Shouldnt be too hard for a dev to do. i know they did it for the nexus devices. oneplus has one fugly looking fastboot and unlocked warning. also they cant spell.

fix-this! said:
Shouldnt be too hard for a dev to do. i know they did it for the nexus devices. oneplus has one fugly looking fastboot and unlocked warning. also they cant spell.
Click to expand...
Click to collapse
hahah，they can't spell

+1 for this
Gesendet von meinem OnePlus 3

Bart1981 said:
After unlocking the bootloader, you're stuck with a message, everytime you reboot your phone, which gives you a warning that the bootloader is unlocked. Quite annoying if you ask me, especially because it takes 5 seconds before the phone continues to reboot.
Is there somebody who can remove that warning? It's already done for the motorola G4, so I guess it shouldn't be to difficult for the OP3, as long as somebody with a little bit of know how takes a look into this issue.
Somebody here who can make this happen?
Click to expand...
Click to collapse
unlocking the bootloader does avoid your warranty or not?

Arrowblue said:
unlocking the bootloader does avoid your warranty or not?
Click to expand...
Click to collapse
If I remeber correctly, when you are unlocking the bootloader you get a warning that it MIGHT void warranty. But I don't think that will be the case with OnePlus.

Bart1981 said:
If I remeber correctly, when you are unlocking the bootloader you get a warning that it MIGHT void warranty. But I don't think that will be the case with OnePlus.
Click to expand...
Click to collapse
yeah other Oems like, sony samsung does avoid your warranty when you are bootloader unlocked but One plus 3 i always thought they are good to go even when your bootloader is unlocked.

It is required by Android/Alphabet as a verified device, but honestly 1+ how hard would it have been to spellcheck this screen.
I welcome a removal of this screen

Me too. The incorrect spelling drives my OCD to despair.
Sent from my ONE A3003 using XDA-Developers mobile app

+3

on the 6p. it's somewhere in the ramdisk which was risky to tinker with so nobody bothered to risk and remove it. on the other hand it's really simple with the 5x. not sure on the op3.

Arrowblue said:
unlocking the bootloader does avoid your warranty or not?
Click to expand...
Click to collapse
No

I'm waiting for this as well. Tried messing with it myself, but have very little to any experience in this particular area. I found where the LOGO file was, but when I copy and changed the format to IMG or BIN, it was unreadable with the two different programs I have to read those file types, so instead of messing things up - I gave up.

At least they fixed the spelling and the placeholder url in the latest update. I can put up with it now.

Unlocked and flashed cyanogen yesterday and didn't know the OP3 had this screen either....it's much worse that the N6P one but not as alarming lol it's still really annoying and I went back to a locked stock because of it.
Still at least it's not as annoying as the one they put on the Pixel C.....

+1 for this. Its really annoying. I hope it can be patched up quickly.

rustyshakelford2 said:
At least they fixed the spelling and the placeholder url in the latest update. I can put up with it now.
Click to expand...
Click to collapse
the gramma is still with mistake...
If no key pressed (if no key is pressed)
lol

How often do you guys reboot your phones for this to be an issue? I'll admit the unlocked padlock from the Nexus was a bit more classy but I can't see how this is a dealbreaker when you hardly ever reboot your phone outside flashing stuff.

Should I buy an LG G4 Today?

Hi, I was recently thinking about changing my phone so thought of buying the LG G4. A guy near my place is selling it. I have also heard about the bootloop issue. Although the phone was working fine on his shop, should I still buy the phone? Are there any special conditions under which the phone goes into the bootloop so I can test it either using a stress test tool or playing a demanding game before buying? Please, I need some help!
Thanks,
Asbaat

ShadowFiend98 said:
Hi, I was recently thinking about changing my phone so thought of buying the LG G4. A guy near my place is selling it. I have also heard about the bootloop issue. Although the phone was working fine on his shop, should I still buy the phone? Are there any special conditions under which the phone goes into the bootloop so I can test it either using a stress test tool or playing a demanding game before buying? Please, I need some help!
Thanks,
Asbaat
Click to expand...
Click to collapse
from with serial number on back starting with 601 are less likely to bootloop the higher the number the better. lower then be cautuious.
if you dont care LG not giving nougat officialy. and poor battery. go ahead but also make sure its one of the unlockable bootloaders
search for list of lg g4 that can be nootloader unlocked.
if all okey go ahead has nice camera and unofficial beta N its nice. but official would be better.

raptorddd said:
from with serial number on back starting with 601 are less likely to bootloop the higher the number the better. lower then be cautuious.
if you dont care LG not giving nougat officialy. and poor battery. go ahead but also make sure its one of the unlockable bootloaders
search for list of lg g4 that can be nootloader unlocked.
if all okey go ahead has nice camera and unofficial beta N its nice. but official would be better.
Click to expand...
Click to collapse
Thank you for your reply, can you kindly tell why buying an unlockable bootloader device is necessary? Also, if the device is 601 and it still goes into a bootloop, will there be any solution to this except repairing the motherboard stuff?
Thanks,
Asbaat

ShadowFiend98 said:
Thank you for your reply, can you kindly tell why buying an unlockable bootloader device is necessary? Also, if the device is 601 and it still goes into a bootloop, will there be any solution to this except repairing the motherboard stuff?
Thanks,
Asbaat
Click to expand...
Click to collapse
Read the bootloop fix it list in my signature.
Buying a device which can be unlocked is absolutely necessary to fully enjoy that phone plus you can do some adjustments regarding bootloop only when unlocked.
Sent from my LG-H815 using XDA Labs

ShadowFiend98 said:
Thank you for your reply, can you kindly tell why buying an unlockable bootloader device is necessary? Also, if the device is 601 and it still goes into a bootloop, will there be any solution to this except repairing the motherboard stuff?
Thanks,
Asbaat
Click to expand...
Click to collapse
unlocked bootloader you can flash other roms stock based or aosp.
you can install kernek and tune it for performance or battery.
its unknown if it will bootloop but is less likely to happen. from 601 upwards.
also see wht my friend steadfasterX says read hes the man. he knows more then i do.

as long as it is 811 or 815...and 601 or newer serial number...its still worth to buy it

No. I haven't had bootloops on my 602 but have still had problems.
No knock on to wake. (replace screen to fix)
Micro usb port worn out and can only be replaced be re-soldering.
Random notification led blinking. (restart wifi to fix)
No updates.
Still could get a bootloop.

How to determine if phone bootloader can be unlocked? thx

screen stays black?

Hey guys it's been a while since I've been active on here but I just bought the pixel 2 xl and my screen at least 2-3 times a day won't turn back on for a few minutes. After it turn on the screen is fine but sometimes I can't answer a call or turn off alarm. So I was wondering if anyone else has had this problem. Mine is stock Verizon model so I'm thinking of returning it on the 14 day hassle free return and just root and unlock it after.

t2noob said:
Hey guys it's been a while since I've been active on here but I just bought the pixel 2 xl and my screen at least 2-3 times a day won't turn back on for a few minutes. After it turn on the screen is fine but sometimes I can't answer a call or turn off alarm. So I was wondering if anyone else has had this problem. Mine is stock Verizon model so I'm thinking of returning it on the 14 day hassle free return and just root and unlock it after.
Click to expand...
Click to collapse
If definitely return that puppy if it still persists after a factory reset or running it in safe mode for a while. Be advised, you'll need the Google version if you want to unlock and root that puppy ?

Badger50 said:
If definitely return that puppy if it still persists after a factory reset or running it in safe mode for a while. Be advised, you'll need the Google version if you want to unlock and root that puppy ?
Click to expand...
Click to collapse
I thought as long as I don't update it past the January security update I could still do it? I plan to taking off Sim and not connecting to internet until I do the critical unlock.

t2noob said:
I thought as long as I don't update it past the January security update I could still do it? I plan to taking off Sim and not connecting to internet until I do the critical unlock.
Click to expand...
Click to collapse
If it's a true Verizon variant phone, then you can't unlock the bootloader or root it! :crying:

Badger50 said:
If it's a true Verizon variant phone, then you can't unlock the bootloader or root it! :crying:
Click to expand...
Click to collapse
Oh ok I thought I had read somewhere that before the January update you could still go the critical unlock fastboot command and unlock it that way. And that after the January update they fixed that work around.

t2noob said:
Oh ok I thought I had read somewhere that before the January update you could still go the critical unlock fastboot command and unlock it that way. And that after the January update they fixed that work around.
Click to expand...
Click to collapse
You may have been reading about the smaller pixel 2 and not the 2xl. Which was indeed true for a while.

Phone went to bootloop

so I woke up this morning and the phone was off, i tried to turn it on with no luck. Plug in the original OEM charger and been getting stuck in bootloop.
tried to follow recovery mode but everytime i get to the "fastboot" screen and try to toogle the menu, the phone reset back to the "Google" logo....so now i can't even enter recovery mode to side load. have anyone run into this issue before? and what is the solution?
thanks

So after i let the phone run out of the battery, i noticed the no battery icon keep flashing. plus when i was only holding down the Volume down button, i can go to fastboot mood. it seems like the power button is stuck causing the phone to reset all the time. I think this is a hardware issue.

lpiratel said:
So after i let the phone run out of the battery, i noticed the no battery icon keep flashing. plus when i was only holding down the Volume down button, i can go to fastboot mood. it seems like the power button is stuck causing the phone to reset all the time. I think this is a hardware issue.
Click to expand...
Click to collapse
Are you BL locked or unlocked? If unlocked, you can at least try installing the factory image (with or without the -w) and see what it does.

sliding_billy said:
Are you BL locked or unlocked? If unlocked, you can at least try installing the factory image (with or without the -w) and see what it does.
Click to expand...
Click to collapse
unfortunately, BL is locked and I can't do anything that I know of on my end. Time to go back to my back up oneplus 3T

lpiratel said:
unfortunately, BL is locked and I can't do anything that I know of on my end. Time to go back to my back up oneplus 3T
Click to expand...
Click to collapse
Can you see the device in Fastboot with fastboot devices from a command prompt? Are you locked and not unlockable (Verizon) or just not unlocked? If just not unlocked you could try unlocking the BL (assuming you had at least toggled OEM Unlocking in developer settings)? I don't know if the command works on a locked BL (I suspect it doesn't, but it is worth a try), but fastboot reboot fastboot would get you to fastbootd where you can do ADB sideload.

sliding_billy said:
Can you see the device in Fastboot with fastboot devices from a command prompt? Are you locked and not unlockable (Verizon) or just not unlocked? If just not unlocked you could try unlocking the BL (assuming you had at least toggled OEM Unlocking in developer settings)? I don't know if the command works on a locked BL (I suspect it doesn't, but it is worth a try), but fastboot reboot fastboot would get you to fastbootd where you can do ADB sideload.
Click to expand...
Click to collapse
my phone is not Version version, bought it directly from google. oem is unlocked for sure. I tried the command, but it keep restarting after 3 seconds in fastboot mode. I think the power button board is messed up.

lpiratel said:
my phone is not Version version, bought it directly from google. oem is unlocked for sure. I tried the command, but it keep restarting after 3 seconds in fastboot mode. I think the power button board is messed up.
Click to expand...
Click to collapse
Suggestion: Call Google support

lpiratel said:
my phone is not Version version, bought it directly from google. oem is unlocked for sure. I tried the command, but it keep restarting after 3 seconds in fastboot mode. I think the power button board is messed up.
Click to expand...
Click to collapse
Homeboy76 said:
Suggestion: Call Google support
Click to expand...
Click to collapse
Same suggestion as Homeboy at this point. Sorry.

lpiratel said:
so I woke up this morning and the phone was off, i tried to turn it on with no luck. Plug in the original OEM charger and been getting stuck in bootloop.
tried to follow recovery mode but everytime i get to the "fastboot" screen and try to toogle the menu, the phone reset back to the "Google" logo....so now i can't even enter recovery mode to side load. have anyone run into this issue before? and what is the solution?
thanks
Click to expand...
Click to collapse
They will rma it, I had a similar issue on my pixel 2 (slot unbootable load error) and they shipped me once right away.

lpiratel said:
So after i let the phone run out of the battery, i noticed the no battery icon keep flashing. plus when i was only holding down the Volume down button, i can go to fastboot mood. it seems like the power button is stuck causing the phone to reset all the time. I think this is a hardware issue.
Click to expand...
Click to collapse
This just happened to me yesterday. Plugged my Pixel 3 XL in to the wall charger and it immediately went into a bootloop. Nothing would stop it as if it were a hardware issue. Tried to boot into recovery and fastboot but it would immediately bootloop again. Eventually after the battery died I was able to start it up and get it working again. My issue now is that I'm worried it will happen in the future. Didn't plan on upgrading but might have to move to the 4 XL as I use this phone for work.

holy crap - this happened to my wife's phone last week. We ended up getting a Pixel 3A XL for her.
She plugged in her 3XL at around 10% and it started boot looping. I couldnt' do anything with it. The only way I could try and keep it on is blasting it with a flipped can of CO2. I tried everything from factory reset to reflashing. Finally I gave up, and let it sit for a week. Started the phone, and it stayed on for 3 days and let the battery drain again to 10% - plugged the phone it and it started bootlooping again. I'm wondering if the battery just gave out. I wonder if we can see if there is some manufacturing correlation here, maybe all of our phones came from the same batch. I ended up buying in Nov 2018 for Black Friday sale.

Hey i'm currently going through this exact issue right now with my Pixel 3 XL. However my phone is out of warranty, it expired back in november, anyone has had experience with Google over the handling of this issue once the phone is out of warranty?
Would be great for your feedback! literally cried when this happened. I experienced the bootloop issue with the 6P. couldn't believe it was happening again with a phone of lifespan still less than 2 years.
Thanks!

hazeem96 said:
Hey i'm currently going through this exact issue right now with my Pixel 3 XL. However my phone is out of warranty, it expired back in november, anyone has had experience with Google over the handling of this issue once the phone is out of warranty?
Would be great for your feedback! literally cried when this happened. I experienced the bootloop issue with the 6P. couldn't believe it was happening again with a phone of lifespan still less than 2 years.
Thanks!
Click to expand...
Click to collapse
I'd simply try to get support for this, it looks like the next big flaw and is likely class action lawsuit material, assuming hardware failure can be proven - to which I have not a single doubt in my mind, from reading alone the reports a few red flags can be seen instantly!
From not being able to reach fastboot or get past Google logo it appears to be the UFS storage chip that went bad! However it also seems that there's a relation to the charging mechanism, potentially involving the battery itself..
I think we'll start to see more an more reports about this flaw the next month, I hope not but after all Google released to the public on hardware level alone I wouldn't be surprised either - don't get me wrong, I love their devices and most Nexus and Pixel in daily use, I wouldn't even consider switching to another brand as love those devices to much but after all the years I also know that Google doesn't always execute their plans well on hardware level! Their 'lemon count' is statistically higher than elsewhere!
Good luck everyone, I'm definitely keeping an eye on this thread and issue!
Sent from my Google Pixel 3 XL using XDA Labs

This *just* happened to me, too! Happened at 330pm EDT right before I had a meeting, so I had to quickly swap the sim into another phone. I'm also out of warranty, and the fact that there are a number of us reporting this same issue in a quick span of time leads me to think this is something on Google's end

Sam Nakamura said:
I'd simply try to get support for this, it looks like the next big flaw and is likely class action lawsuit material, assuming hardware failure can be proven - to which I have not a single doubt in my mind, from reading alone the reports a few red flags can be seen instantly!
From not being able to reach fastboot or get past Google logo it appears to be the UFS storage chip that went bad! However it also seems that there's a relation to the charging mechanism, potentially involving the battery itself..
I think we'll start to see more an more reports about this flaw the next month, I hope not but after all Google released to the public on hardware level alone I wouldn't be surprised either - don't get me wrong, I love their devices and most Nexus and Pixel in daily use, I wouldn't even consider switching to another brand as love those devices to much but after all the years I also know that Google doesn't always execute their plans well on hardware level! Their 'lemon count' is statistically higher than elsewhere!
Good luck everyone, I'm definitely keeping an eye on this thread and issue!
Sent from my Google Pixel 3 XL using XDA Labs
Click to expand...
Click to collapse
Since my original reply to this post, it has happened a couple of more times on my phone. Both times I've noticed the phone gets extremely hot but as soon as the battery dies and the temperature cools for a while, the phone will power back on. My uneducated guess is that something in the processor or battery connection is causing the phone to overheat. Excuse the layman's terms lol.
I too have been a big fan of the Nexus and PIxel lineups over the years but my reason for upgrading to the newer model was always because my old phone had some sort of hardware defect. Galaxy Nexus microphone died, Nexus 6P wouldn't power on, OG PIxel bootlooped. Pixel 2 XL had screen issues. Pixel 3 XL, here we are now lol. Each one lasted me at least over a year and the software is unmatched in my opinion. I'm proud of how far they've come with software, hardware and camera. I just wish they'd put a little "oomph" in their quality control department.

Google doesn't help with bootloop
hazeem96 said:
Hey i'm currently going through this exact issue right now with my Pixel 3 XL. However my phone is out of warranty, it expired back in november, anyone has had experience with Google over the handling of this issue once the phone is out of warranty?
Would be great for your feedback! literally cried when this happened. I experienced the bootloop issue with the 6P. couldn't believe it was happening again with a phone of lifespan still less than 2 years.
Thanks!
Click to expand...
Click to collapse
----------------------------------------
I bought my Pixel 3 XL November 2018 from the Google Store.
The phone has been great, but the bootloop started happening with me 4-5 days ago. I had to buy a new phone (yes, I'm stuck in the modern world, unfortunately. i need a phone)
Recovery buttons get to a menu...and then back to the bootloop within 2 seconds, There was little time to press volume buttons etc and no response when I do so on this screen, other than the dead Android with it's hatch open.
But no matter what I do - it goes back to the bootloop within a few seconds.
I spoke w rep from Google for 40 minutes or so, I was polite. No help; he said he could not send me a new or renewed device. he suggested repair shops. Which....the shop told me they do not deal with bootloops, "probably a hardware issue", he said.
So...idea....use my credit card extended warranty! But....for this purchase, strangely...I used PayPal. ughhhh!
Disapointing. Not quite 2 years out of my Pixel, and I was hoping to capitalize on the resale / trade-in value. Not possible now, even a trade in requires a factory wipe.
I did think of using ADB / fastboot, but I do not have time to futz around right now.
You could try Google, but...if you are out of warranty, it is unlikely they will help. Did you buy it with a credit card w extended warranty?
good luck

this just happened to me google is saying that because the phone is out of warranty (by 8 months)
there is nothing they can do about it
at least I have the extended care