Develop Bugs

Phone won't pass the LG screen

my phone is rooted i'm on 13B everything was fine since i got my phone back in august till today i was listening music and was gonna skip to next song that moment is when my phone froze completely after pressing the power button the phone reboot by itself but got stuck on the lg screen i removed the battery after a few attempts it turned on. after 30 minutes or so it rebooted it self again but now even removing the battery it won't pass the lg screen. any ideas? suggestions?

probably the same problem a lot of other people are having. I also had the same symptoms as you, on rooted 13B.
you can try resetting or reflashing your phone but most likely you need a replacement.

theirs a problem with the motherboard going bad, i just had the same problem and lg sent me a replacement under warranty but i wasnt rooted

dagnisaun said:
probably the same problem a lot of other people are having. I also had the same symptoms as you, on rooted 13B.
you can try resetting or reflashing your phone but most likely you need a replacement.
Click to expand...
Click to collapse
bayniner said:
theirs a problem with the motherboard going bad, i just had the same problem and lg sent me a replacement under warranty but i wasnt rooted
Click to expand...
Click to collapse
Update!
i called verizon they sending me a replacement. just to let you know i flashed 13B KDZ but the bootloop was still there i let my phone on and finally turned on quickly i did a factory reset and booted up normal and its working again. still im gonna send it back. just sharing my experience maybe for other people might work too.

killa408shark said:
Update!
i called verizon they sending me a replacement. just to let you know i flashed 13B KDZ but the bootloop was still there i let my phone on and finally turned on quickly i did a factory reset and booted up normal and its working again. still im gonna send it back. just sharing my experience maybe for other people might work too.
Click to expand...
Click to collapse
How were you able to flash 13B if it was stuck in a bootloop, ive already recieved my replacement but id like to factory reset my old one before i send it back

bayniner said:
How were you able to flash 13B if it was stuck in a bootloop, ive already recieved my replacement but id like to factory reset my old one before i send it back
Click to expand...
Click to collapse
I put the phone in download mode and flashed 13B KDZ. But unfortunately my phone got back in the bootlop. Good thing I'm gettingmy replacement

It's a hardware issue, not software. A lot of the earlier G4s have "loose contacts" that cause the bootloop to occur. LG has acknolwedged it and are replacing any affected phones without incident. Just call verizon and they'll ship a new one.

Yup, happened to me just his week. VZW shipped another one to arrive the next day. FWIW, I strongly recommend everyone backup their phone to removable SD card using LG's on board Backup utility. If this challenge happens to you, getting back up and running quickly will be much easier if you have this backup ready to go.
...my $.02.

Happened to me as well last night. Took it back to Verizon today and they are sending me another one. I didn't have insurance and no questions were asked. Obviously they recognize the problem. Last LG phone I will own! Unless the G5 is insane. Hehe

Happened to me as well, yesterday. Interesting how this is happening to everyone at almost the same timeframe. I'll take it to Verizon to get a replacement shipped.

I had the same problem, and contacted LG support and they said it will take 9 business days to repair the phone. This seemed like an awful long time to be without a phone, I asked if there was any way to speed the process up and they said no. Thankfully I was able to borrow a phone from work for the duration of the repairs. Considering how this is a major problem with many handsets, I think LG is handling the whole situation pretty badly.

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

Need help!! LG G4(H815) not starting

Hi all,
so here is my problem.
Day before yesterday i had a perfectly working LG g4 H815 model with s/n 511 running on firmware v20h, when i decided to root it and install some mods.
so i flashed TWRP, installed xposed and xtrememusic mod. the phone booted normally after installing these. i didn't install any modules under xposed. the phone worked perfectly for two days. however today morning it hanged while taking photo with the camera app. when restarting it got stuck at LG logo for long time. My brother(who doesn't have any technical knowledge) pulled out the battery and restarted. Again it got stuck at LG logo. thinking somthing wrong he again repeated this only to find that it didn't power on at all this time. No LG logo no notofication light nothing.
Tried charging it(although battery was aroung 60-70%), pressing power button removing the battery. still nothing. the phone is not at all powering up.
However when i connect it with USB cable with laptop, laptop makes sound of getting usb connection detected. i took it to a service centre.
the technical guy there told that IC may have been faulty. he told me that motherboard needs to be replaced. however unofficially he may try heating the IC to get it booting.
What should i do now? Is the IC really fried. had the rooting and installing mod caused it?
Please help.
PS- the phone is imported and cannot be sent back for warranty purpose.

I think you are experiencing the dreaded LG G4 bootloop. I don't think rooting or modding caused a software problem. It "may" have caused a hardware problem simply because it generated enough heat to loosen the IC that little bit that initiates the problems you are describing. I rooted and installed the stock image in Nov 2015. Two weeks ago the phone froze - restarted and then could not be booted. LG sent me a Fedex label and I sent it off. Ten days later I received the same phone back. I assume they replaced the mainboard.
You should contact LG directly. I saw a class action suit that was called off because it appeared that LG will fix this particular problem (failed mainboard) out of warranty. Anyone please correct me on this if I'm wrong.

dsteinschneider said:
I think you are experiencing the dreaded LG G4 bootloop. I don't think rooting or modding caused a software problem. It "may" have caused a hardware problem simply because it generated enough heat to loosen the IC that little bit that initiates the problems you are describing. I rooted and installed the stock image in Nov 2015. Two weeks ago the phone froze - restarted and then could not be booted. LG sent me a Fedex label and I sent it off. Ten days later I received the same phone back. I assume they replaced the mainboard.
You should contact LG directly. I saw a class action suit that was called off because it appeared that LG will fix this particular problem (failed mainboard) out of warranty. Anyone please correct me on this if I'm wrong.
Click to expand...
Click to collapse
Hi thanks for the help.
But isn't the dreaded bootloop is that where the phone is stuck at the LG logo. Mine isn't booting at all. And the bootloop problem is due to big cores or such and not due to ic?

Mine wouldn't start at all - it bootlooped once for about a split second - then it was dead

Same is the problem with me. Bootlooped twice and then its completely dead. I have tried contacting Lg UK. Lets see what they say.

Ok so i got a reply from LG and they suggested me some steps to take (which are obviously not useful as it is completely dead). however they have also told me that they are willing to help me and asked me about details of purchase etc and "whether it was rooted".
so what should i reply rooted or not? will they detect it as it is dead.

dbzgoku said:
Ok so i got a reply from LG and they suggested me some steps to take (which are obviously not useful as it is completely dead). however they have also told me that they are willing to help me and asked me about details of purchase etc and "whether it was rooted".
so what should i reply rooted or not? will they detect it as it is dead.
Click to expand...
Click to collapse
Sorry to be late on reply. I advise to not answer question whether phone was rooted. Here is my reasoning:
1. This problem is widely occuring - only a tiny percentage of people root their phones therefore question is irrelevant.
2. The problem is known to be that an IC becomes loose most likely due to heat - a better question would be - do you place the phone on a hot dashboard with GPS running while you are charging?

dsteinschneider said:
Sorry to be late on reply. I advise to not answer question whether phone was rooted. Here is my reasoning:
1. This problem is widely occuring - only a tiny percentage of people root their phones therefore question is irrelevant.
2. The problem is known to be that an IC becomes loose most likely due to heat - a better question would be - do you place the phone on a hot dashboard with GPS running while you are charging?
Click to expand...
Click to collapse
thanks for the reply (although late). i have already sent the phone to LG replying as no root. Lets hope they repair it without any problems.
second i didnt do anything of anysort like placing on hot dashboard or such. one day while opening the camera app it decided to just hang and later on die on me.

I hope you didn't think I was saying you might have done something that would overheat your phone such as my second example. I was trying to come up with an example reason the IC loosens. Even if you did that the phone should survive such conditions. Let's hope the replacement motherboards somehow do better. My guess is that the soldering job is fine, the problem is probably bad design that doesn't "vent" the heat from chip.

dsteinschneider said:
I hope you didn't think I was saying you might have done something that would overheat your phone such as my second example. I was trying to come up with an example reason the IC loosens. Even if you did that the phone should survive such conditions. Let's hope the replacement motherboards somehow do better. My guess is that the soldering job is fine, the problem is probably bad design that doesn't "vent" the heat from chip.
Click to expand...
Click to collapse
so what do you suggest after repair should i keep it or sell it? Lg g4 is no doubt the best phone when considering the value for money. no phone even twice in price comes close in camera and screen quality especially. but the unreliability of this phone has made me to consider selling it as soon as i get it back.

I'd keep it if your new board is high serial

lukem99626 said:
I'd keep it if your new board is high serial
Click to expand...
Click to collapse
Well my old board was also high serial, beginning with 511

I'm going to take my chances - it's a great phone until it bootloops. I'm going to avoid scenarios best I can that could result in the phone heating up inside. That would be charging only if absolutely necessary while in my ProClip dash mount if the car is hot, using backup battery after depletion instead of charging more often etc. Thinking back I rarely put the phone into heat inducing situations - normal use results in the IC becoming loose at the 1 year mark. If mine bootloops exactly a year from now and LG fixes it again I'm an LG fan. If they blow me off no more LG.
I really regret not paying it off early and taking the $15/month deal for an S7 Edge last month

dbzgoku said:
Well my old board was also high serial, beginning with 511
Click to expand...
Click to collapse
I mean like 611 ect thats what i got from lg

dsteinschneider said:
I'm going to take my chances - it's a great phone until it bootloops. I'm going to avoid scenarios best I can that could result in the phone heating up inside. That would be charging only if absolutely necessary while in my ProClip dash mount if the car is hot, using backup battery after depletion instead of charging more often etc. Thinking back I rarely put the phone into heat inducing situations - normal use results in the IC becoming loose at the 1 year mark. If mine bootloops exactly a year from now and LG fixes it again I'm an LG fan. If they blow me off no more LG.
I really regret not paying it off early and taking the $15/month deal for an S7 Edge last month
Click to expand...
Click to collapse
Well lg did mention in my communication with them that this carries 2 year warranty.

lukem99626 said:
I mean like 611 ect thats what i got from lg
Click to expand...
Click to collapse
Didn't know that serials have gone so high

dbzgoku said:
Didn't know that serials have gone so high
Click to expand...
Click to collapse
I brought a g4 in the new year sale it has the serial of 611 i had a 601 few months back i returned it ran hot and laggy the 611 one is cool running and lag free so i think something changed

Not Booting

Hi, I was using DU, I opened an app, the device stuck I hard rebooted & it got stuck on boot animation (boot animation stopped and stuck) I flashed full stock ROM & it's on Google logo please help, wiped everything, recovery not booting either..

It seems that your 5x is mostly dead due the HW bootloop problem. The problem is in the solder connection between the cpu and the emmc memory. If your phone is still in the warranty period, ask for a refund. If not, you can try to open the phone up and reheat the emmc and cpu manually ( with a hairdryer for instance) to restore the solder connection. It can work, but it isn't a pernament fix. Some people said, that after this "fix" it worked for a while, but the problem came back after months or even weeks
Sent from my Nexus 5X using Tapatalk

dc239 said:
It seems that your 5x is mostly dead due the HW bootloop problem. The problem is in the solder connection between the cpu and the emmc memory. If your phone is still in the warranty period, ask for a refund. If not, you can try to open the phone up and reheat the emmc and cpu manually ( with a hairdryer for instance) to restore the solder connection. It can work, but it isn't a pernament fix. Some people said, that after this "fix" it worked for a while, but the problem came back after months or even weeks
Click to expand...
Click to collapse
Thanks for reply, I figured it's a hard brick as it booted once somehow (charged before a lil maybe it triggered the solder to "fix" temporarily) it went down again within an hour I gave it for service, under warranty, the service center said they'll fix it (motherboard replacement) have warranty only for 3 more months now.. Wish the replacement motherboard doesn't have the problem..

Nexus 5X hard bricked. Is there definitely no way to fix it?

I have a Nexus 5X (running Oreo 8.0 rooted) which was working fine until yesterday. The phone was responding very slowly so I decided to power it off. After that the phone will not power on at all. When I connect it to PC via USB, it shows up as "QHSUSB_BULK" in device manager. I have read online that this means the phone is hard bricked. I bought the phone in June 2016 and the warranty only lasts a year so I can't RMA it. What should I do? I really liked the 5X and nothing out there really compares to it.

@gwynlordofcinder: sad for you. But why you ask the same question as 20 others before? Try freezer and/or oven to get back the mainboard-connections. If successfull, you can save your data or go on with a kernel-profile which makes the big core sleep. Use search for details.

gwynlordofcinder said:
I have a Nexus 5X (running Oreo 8.0 rooted) which was working fine until yesterday. The phone was responding very slowly so I decided to power it off. After that the phone will not power on at all. When I connect it to PC via USB, it shows up as "QHSUSB_BULK" in device manager. I have read online that this means the phone is hard bricked. I bought the phone in June 2016 and the warranty only lasts a year so I can't RMA it. What should I do? I really liked the 5X and nothing out there really compares to it.
Click to expand...
Click to collapse
They have extended the warranty to 18 months, or someone said 24 months, since there is a hardware issue with the 5X.

Most likely fixable, but with the need of special files.
Search up on QD Loader 9008 on this subforum and read through it.
i'm on the hunt to find a fix for it, hopefully i'll make it. gonna share my findings asap!

Voicebox said:
They have extended the warranty to 18 months, or someone said 24 months, since there is a hardware issue with the 5X.
Click to expand...
Click to collapse
There is no extended warranty in the UK, which is where I purchased the phone.

gwynlordofcinder said:
There is no extended warranty in the UK, which is where I purchased the phone.
Click to expand...
Click to collapse
Since this happened from normal usage and not from you installing a custom ROM or updating the bootloader, or something like that, I think you have the bootloop problem. I normally think of a hard brick being the result of flashing say the incorrect bootloader, or a corrupt file, etc. which can then hopefully be undone by software means to get the right software back on there.
If you have the bootloop, it is a hardware problem. The fact that the phone doesn't bootloop does not mean you don't have the hardware problem. Boot looping was just the most common way to identify it, but many, like mine would just either never even start booting, or would start, then go black.
If you don't figure out any software way to do anything, then try to look for bootloop fixes. Searching for that might get you further. But with a hardware problem, everything except the fix for disabling the big cores (in XDA threads), is temporary unless you are lucky.
Assuming you have a hardware issue, here's some steps to maybe try. I was able to get the rescue fix installed on my phone after using a hair dryer on the motherboard. But that didn't fix anything since my problem was hardware. But if your OTA update was maybe slightly corrupted, maybe it'll help.
https://productforums.google.com/forum/#!topic/nexus/G_0s70PzK_s
To jump right to trying a rescue OTA, go here:
https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!topic/nexus/hdrNONCCoNE
If it doesn't react enough to do anything from a computer, you may have to resort to putting it in the freezer for a while first. Which may give a short period where it'll boot and you can maybe adjust the settings so you can try one of the XDA fixes that disable the big cores.
One fix that disables the big cores:
https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
Example video of heat gunning the motherboard. He did hair dryer, but then did it again with a heat gun. That's in a separate video of his. By using a heat gun, I was able to get it to where I could pull my data off and it even acted normal for 9 hours. Then rebooted and then eventually ended up bootlooping. The fix to disable the big cores was not around back then, so I never have tried it, and ended up getting the 5X replaced by Google.
https://www.youtube.com/watch?v=SD25mdrgAys
Different walk through:
https://www.youtube.com/watch?v=6HlqfB7VD1E

Voicebox said:
which can then hopefully be undone by software means to get the right software back on there.
Example video of heat gunning the motherboard. He did hair dryer, but then did it again with a heat gun. That's in a separate video of his. By using a heat gun, I was able to get it to where I could pull my data off and it even acted normal for 9 hours. Then rebooted and then eventually ended up bootlooping. The fix to disable the big cores was not around back then, so I never have tried it, and ended up getting the 5X replaced by Google.
https://www.youtube.com/watch?v=SD25mdrgAys
Different walk through:
https://www.youtube.com/watch?v=6HlqfB7VD1E
Click to expand...
Click to collapse
except that the files needed for unbricking corrupt bootloaders/eMMCs' are so hard to find it's incredible.
bought a used 5X that "suddenly died in a pocket", now that you mention all of this, i might try doing the hardware fixes and then apply the big core disabling and hopefully get my phone to work.
the phone did get serviced though, so they might've installed bad firmware since the phone is in QDLoader & in EDL mode (PC recognizes the phone, while fastboot/adb/LGUP doesn't)

gwynlordofcinder said:
I have a Nexus 5X (running Oreo 8.0 rooted) which was working fine until yesterday. The phone was responding very slowly so I decided to power it off. After that the phone will not power on at all. When I connect it to PC via USB, it shows up as "QHSUSB_BULK" in device manager. I have read online that this means the phone is hard bricked. I bought the phone in June 2016 and the warranty only lasts a year so I can't RMA it. What should I do? I really liked the 5X and nothing out there really compares to it.
Click to expand...
Click to collapse
Can you update driver "QHSUSB_BULK" in device manager by choose driver manually . I have problem like this in Inew V3 (Chaina Phone) and can fix by choose driver manually.