Related
Well, I'm at wit's end. I'm usually pretty decent at borking and consequently unborking a phone. But I think I'm stumped this time; and am hoping that the community here can help me out. Though, to be fair, I suspect that rolling back to my old phone and eventually buying a new one is my only recourse.
So I imported an H815 Open EU from Handtec UK. No real issues on that front. I eventually unlocked the bootloader, flashed TWRP, and used the KDZ method to (clean) flash my way up to Europe OPEN H81510D initially, and then around two months ago, to Europe OPEN H81510E. I've been running that software without issue since that clean flash. And all this time I've been rooted through the TWRP method.
While this is (was?) my first LG phone, it isn't my first Android experience. So I've been using TiBu to back up my apps nightly, was running Kickoff's lovely hybrid theme, and had a few Xposed modules activated to tweak my experience a bit from stock behavior. I was curious about Marshmallow, but autoprime's warning that it could be non-final test software and the fact that Xposed doesn't work on it kept me from indulging that curiosity.
Everything has been going swimmingly until today. No major issues that I couldn't solve on my own. Certainly nothing that booting into recovery and clearing caches didn't fix. I was out and about engaging in a chat via Hangouts with a friend when my phone suddenly crashed and black-screened. I wasn't plugged into the wall or my PC, and I hadn't performed any kind of major update since the 10E flash a month or two ago. I had not installed any new Xposed modules or any rogue Google Play store apps. I was just using my phone normally and it crashed.
I popped out the battery and played around with it, trying to get it to boot up. I couldn't access recovery or even get beyond the LG logo. It would just hang there and after a few seconds, black-screen. Only popping the battery out and reinserting it would allow me to try again. I eventually left it alone until I got home, at which point I figured I'd try for download mode and reinstall the 10E KDZ via a CSE flash. It's always been a last resort, but a reliable one. I successfully performed the CSE flash of the 10E KDZ.
I thought it did the trick, as I got past the static LG logo for the first time and saw the LG boot animation, but it hung towards the end of the animation and black-screened again. Tried a few more reboots. Recovery mode still not accessible. Download mode was only accessible every third or fourth attempt. Finally got back into download mode and figured I'd try to roll back to 10D (I still had the KDZ I had previously used saved, just in case). Everything seemed to start going fine. Download mode's circle arrow animation on the phone was doing its thing, and then I hear the USB connection drop out. The arrow animation hangs, and the phone black screens. LG Tool 2014 spits out an error I can't read (the software is all question marks for me at this stage). Before it black-screened, it appeared that download mode hadn't progressed beyond 0%.
Now the phone is completely unresponsive. Popping out the battery and reinserting shows no signs of life. No USB sounds from my PC. No static LG logo. No recovery mode or download mode. Not even the lonely flash of an LED.
I've never had a phone hard brick, but I imagine this is what it tastes like.
So I'm probably out of luck, right?
I apologize for the long story. Thanks in advance for sticking around.
Maybe a stupid question but still deserves to be asked, what does pluging the phone in a wall socket gives you?
Sent from my HUAWEI MT7-L09 using Tapatalk
that is strange to happen randomly. The same thing happened to one of my old devices, a 1st gen moto atrix after I dropped it. I can get it to boot up but eventually it acts like the battery is pulled and just reboots. I'm convinced some wires or chip has been damaged inside even though it was only a 2 foot drop on thick carpet... not a whole lot you can do off warranty. Good luck.
Yeah, I figured the phone was toast. Of course the only time I hard brick a phone, it'd be the one time I import one from another country. Alas.
I think I'll return to my Galaxy S4 for now and pick up a Moto X Pure in a week or two, if no other ideas or opportunities present themselves.
As for having the phone plugged in, I just mentioned it in passing in order to rule out a power surge or short or whatever. Just to be completely clear about what I was doing with my phone.
There are already a few other threads on this man. Try to read first and post. Probably it's a motherboard problem. See the date of manufacturing of your device.
I read completely through the first 5 or 6 threads I saw on bricks and was overwhelmed by Marshmallow woes. Mobo, huh? That's a damn shame. Thank you.
Hello guys,
I have a LG G4 H815 variant which shut off while talking on the phone. I did not install any new apps or anything new but got OTA update from LG 2-3 days before this happened.
I removed the battery and after I kept it back, and sometimes LG logo comes and then phone shuts off. Few times it also rebooted like 3-4 times by itself but did not pass the lg logo screen.
Now comes the most important thing, we recently had a baby (5days ago) and have all the photographs and videos of birth and delivery in this phone. I need that to be recovered, so please help with this first and then may be fix the phone next.
So hard reset of the phone is not an option I suppose. I also tried connecting to windows/Mac and system doesnt recognise the phone
I really appreciate any help from you guys.
sounds like you have the lg bootloop bug people have kept trying and eventually the phone has started
Sent from my LG-H815 using Tapatalk
nexy33 said:
sounds like you have the lg bootloop bug people have kept trying and eventually the phone has started
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
I have been trying for past 3days removing the battery and charging for whole day, nothing helped till now
Ermm, with the bootloop issue only one thing helped so far... Send it back to repair (I did it as well)
davebugyi said:
Ermm, with the bootloop issue only one thing helped so far... Send it back to repair (I did it as well)
Click to expand...
Click to collapse
So do you mean to send it to UK..... I called US LG support, they said to contact UK support.... they said, they can only send packages to Uk to send the phone for repairs. What about the data on phone? I need the very important photos of my newborn.
try the freezer method
http://forum.xda-developers.com/showpost.php?p=64905142&postcount=1
akusbharat said:
So do you mean to send it to UK..... I called US LG support, they said to contact UK support.... they said, they can only send packages to Uk to send the phone for repairs. What about the data on phone? I need the very important photos of my newborn.
Click to expand...
Click to collapse
I brought the phone back to the shop where I bought it, as I had a 2 year warranty with them. They sent it to one of their repair centers and in 8 days it was fixed for free.
I suggest to try the freezer method posted above and hopefully it will boot and you can manage to get your photos off the phone.
In case it won't boot all or just sits on the LG logo, then it is hard to recover as (probably) they have to replace the whole motherboard (like in my case) and it is unlikely they will bother with recovering data. However you may ask them very nicely, but they might just ignore it.
Hi all, ok tonight/this morning at work while on my break i went to do my usual thing of having food and watching a tv show via cartoon hd about 2mins in and my phone switched off.....now i thought it was dead so plugged in the charger but no led light, or screen on to say its charging.....i did a bit of googling and find out about the bootloop thingy buuuuut mines not looping, its swtiching on to the LG logo [i did the bootloader unlocker thingy etc so it says tha in the top corner] then it goes off.......i also get pulsing blue led lights too.....if i press, hold the power button after i get nothing, i have to take the battery out and then its rinse and repeat
Hi,
Same thing happened to me today. I was taking a shot and it switched off and same scenario.It seems that we had encountered an bootloader brick in which our device enters in some special bootloader mode in which when you connect it to the computer in the device manager it shows up as Qhsusb_bulk. I read the whole internet and there is a similar brick with G3 the guys were able to fix it. Even there is a tutorial on how to do this which I think is applicable to our device. I was able to install the required drivers and etc. but there is one big problem - I followed the guide and came into one serious problem - we need a special mbn file so we can recover our device and the sad thing is nobody on the internet doesn't have it still. There are many people like us who got selfbricked G4 and cannot fix it without this file. Please if somebody can help us please share the file so we can fix our devices. THANK YOU !
Link to the g3 unbrick guide
ive seen lots about the bootloop issue, but the thing is mine isnt doing a loop [i have to take the battery out/ pop it it back in, to switch it on then after 10-20 seconds on the LOGO it turns off
thewhisper said:
Hi,
Same thing happened to me today. I was taking a shot and it switched off and same scenario.It seems that we had encountered an bootloader brick in which our device enters in some special bootloader mode in which when you connect it to the computer in the device manager it shows up as Qhsusb_bulk. I read the whole internet and there is a similar brick with G3 the guys were able to fix it. Even there is a tutorial on how to do this which I think is applicable to our device. I was able to install the required drivers and etc. but there is one big problem - I followed the guide and came into one serious problem - we need a special mbn file so we can recover our device and the sad thing is nobody on the internet doesn't have it still. There are many people like us who got selfbricked G4 and cannot fix it without this file. Please if somebody can help us please share the file so we can fix our devices. THANK YOU !
Link to the g3 unbrick guide
Click to expand...
Click to collapse
on G2 you get security boot error phone is detected as QHUSb_BULK. on G2 the fix was to enter download mode. in G2 vol up then plug usb.
using TOT method and flash tools . flash stock firmware fixed my soft brick.
not sure about the file you mention, maybe you do need it..
jamious-daywalker said:
now i thought it was dead so plugged in the charger but no led light, or screen on to say its charging.....i did a bit of googling and find out about the bootloop thingy buuuuut mines not looping, its swtiching on to the LG logo [i did the bootloader unlocker thingy etc so it says tha in the top corner] then it goes off.......i also get pulsing blue led lights too.....if i press, hold the power button after i get nothing, i have to take the battery out and then its rinse and repeat
Click to expand...
Click to collapse
I have the issue. I don't do anything special but my phone reboot and stuck on lg logo. But now my phone doesn't want to boot. Sometimes he detect when I'm trying to charge it but often not. Yesterday I boot on download mode and recovery but today it's impossible... I think I have some hardware issue ? Or software with the bootloader...
I don't know how to fix that without access to download/recovery mode :crying:
Same here. Sometimes it boots into recovery/download but most of the times it doesn't. It's a hardware problem I think as LG officially confirmed that there were problems during the building proccess of the first G4 series. I don't want to sound bad but soon or later all phones built before october last year will get into bootloop. I was hoping it won't happen to me - I'm very light user with only light standart apps with no games and other heavy stuff, so the problem wasn't caused by overheating by heavy multitasking. Anyway it happened and I'm pretty sure it's harware related but if somebody can provide the tot and mbn files I will be more than happy to try the g2/g3 unbrick method. The main problem is that these files are not available for h815. I found on other forum tot files for other variants than h815 So if somebody have the tot filesfor h815 please share so we can try to unbrick our G4. Thanks!
same thing heppened to my g4 this week. i called lg last night and they agreed to repair it. i'd just gave them a call.
I sent mine for repair today. I hope they will agree to repare it even that it's with unlocked bootloader and with rooted custom rom !!! What you think ? Will I have problems with them because of that ?
Happened with my phone as well. It was rooted so i was hella scared if they didn't accept my phone. But soon they told me phone's motherboard has gone bad and will be replaced. Got my phone with a brand new motherboard after a couple of hours.
P.s. all your data will be gone
Sent from my LG-H818 using XDA-Developers mobile app
clotveins said:
Happened with my phone as well. It was rooted so i was hella scared if they didn't accept my phone. But soon they told me phone's motherboard has gone bad and will be replaced. Got my phone with a brand new motherboard after a couple of hours.
P.s. all your data will be gone
Sent from my LG-H818 using XDA-Developers mobile app
Click to expand...
Click to collapse
So the same problem just happened to my lg H815 with unlocked bootloader, am really f***ed without my phone, gonna call LG UK tomorrow, anything in particular I should say? also looking for solutions I saw many people are starting to have this issue now too - any official comments from LG?
P.S. if you have an LG G4 you should start backing up all your data now
This literally just happened in the last 15 minutes to me as well. Random reboot right after I woke up the phone and now stuck on the LG splash screen. Light user here, never did anything with the phone that would have heavily stressed it physically or computing-wise, so I also concur it's an inevitability for earlier runs of G4 phones.
Luckily, I backed up everything through TWRP last Thursday by chance because I was updating Xposed to the latest version and swapping to a faster 128GB microSDXC. At worst, I might have lost a handful of unimportant text messages.
Not worth the time to try to figure out any cheap fixes myself, I just got done submitting a repair request to LG.
I ordered LG G4 H815 and I hope to not see any kind of these issues
irishlad99 said:
So the same problem just happened to my lg H815 with unlocked bootloader, am really f***ed without my phone, gonna call LG UK tomorrow, anything in particular I should say? also looking for solutions I saw many people are starting to have this issue now too - any official comments from LG?
P.S. if you have an LG G4 you should start backing up all your data now
Click to expand...
Click to collapse
Guy at service center said its internally communicated all LG G4's motherboard will have to be changed at least once.
And just say you dont know what happened exactly. Slept and in the morning my phone won't work
clotveins said:
Guy at service center said its internally communicated all LG G4's motherboard will have to be changed at least once.
And just say you dont know what happened exactly. Slept and in the morning my phone won't work
Click to expand...
Click to collapse
at least once?? many had sent phone , then again having bootloop after repair..???
raptorddd said:
at least once?? many had sent phone , then again having bootloop after repair..???
Click to expand...
Click to collapse
I have got my phone repaired for like 4-5 times. 3 times motherboard change, 1 time display change and 1 time volume button pannel change.
clotveins said:
I have got my phone repaired for like 4-5 times. 3 times motherboard change, 1 time display change and 1 time volume button pannel change.
Click to expand...
Click to collapse
all under warranty?? not counting display? or did you get dead pixel?
raptorddd said:
all under warranty?? not counting display? or did you get dead pixel?
Click to expand...
Click to collapse
Yup. All under warranty and counting display replacement as well. No dead pixels as well and phone was rooted once during motherboard replacement
Sent from my LG-H818 using XDA-Developers mobile app
Got mine April 1st. Worked great until May 9th. In the morning it hung and went into a boot loop. After 7 or so reboots (at various stages of boot cycle) it came back. A few hours later it did it again. This time 4 or 5 times and went dead. I tried battery pull, SD card/SIM card pull, and even swapped to my fully charged spare battery. It will not power on.
Called Sprint and they offered to sell me a used phone or fix it for a fee. Called LG. LG said they would take care of it but I would have to send in the phone for repairs and it would be about a 2 week turn around.
It's too bad because I really do like the phone but It'll take a while to regain my confidence in it...coupled with the locked boot loader...I don't know. It has the potential to be a great phone but LG may be shooting themselves in the foot.
Yeah I've had the same issue. For some reason sometimes it would get itself stuck in a boot loop. I would wonder like what the heck is going on... My camera also stopped working functionally and I couldn't make phone calls. I tried factory resetting it and issues were still there. I had to send in my phone which was super dumb... Not only is my phone not working but I have to be without it for like two weeks.
This used to happen with G3... I went back to Samsung. But now i got G5 and i havent had any problems.
Sent from my LGLS992 using XDA-Developers mobile app
mkc90 said:
This used to happen with G3... I went back to Samsung. But now i got G5 and i havent had any problems.
Sent from my LGLS992 using XDA-Developers mobile app
Click to expand...
Click to collapse
my boot loops all happened in the same area, my wife's work. First time when I dropped her off on my way to work and again when I picked her up on the way home. I've noticed before there's a spot where I get really bad reception in the driveway of work and the phone switches to 3G or worse. Both loops started when that occurred. It may have just been a coincidence...and I've certainly been other places with various degrees of worse reception...I was at a datacenter inside a faraday cage just the week before and didn't have any problems.
Since these phones can't be rooted yet I haven't done anything that any consumer wouldn't be able to do. I DID disable some services and installed adguard, but anyone can do that and none of it requires elevated privilege or voids the phone's warranty.
The status on the LG web site is now "repair in progress".
Fortunately I use GV so I can answer my calls and texts from any phone and just went back to my G3 while thr G5 is out for repairs.
Interestingly, when I called LG they didn't even ask me for details. They immediately said "send it back and we'll fix it". Either they have really good no-hassle customer service (they might, this is my first experience with LG customer service so I have no frame of reference) or this is more common than they let on and they know about it.
phone is on the way back. the fault on the repair order is listed as "power management IC".
Let's see what others with this problem get....if you sent your phone to LG for repairs the diagnosed problem will be listed on the email from LG notifying you the phone has been fixed. Looks like the PMIC problem was present in the G4 as well.
I wonder if there was a manufacturing defect in the first batch.
blarg said:
phone is on the way back. the fault on the repair order is listed as "power management IC".
Let's see what others with this problem get....if you sent your phone to LG for repairs the diagnosed problem will be listed on the email from LG notifying you the phone has been fixed. Looks like the PMIC problem was present in the G4 as well.
I wonder if there was a manufacturing defect in the first batch.
Click to expand...
Click to collapse
How long did it take LG to fix your phone once they received it? How long was it actually at LG before they shipped it back to you?
11 days
Guys its the g4 all over again the bootloop issues on g4 have been soaring over the last few months. Lg repairs. And it does it again.
Thats the exact issue on g4 ic power managment.
Apparantly over a year and still no fix
---------- Post added at 10:24 AM ---------- Previous post was at 10:23 AM ----------
blarg said:
phone is on the way back. the fault on the repair order is listed as "power management IC".
Let's see what others with this problem get....if you sent your phone to LG for repairs the diagnosed problem will be listed on the email from LG notifying you the phone has been fixed. Looks like the PMIC problem was present in the G4 as well.
I wonder if there was a manufacturing defect in the first batch.
Click to expand...
Click to collapse
Nothin to do with first batch g4s even repair still doing it. They said any g4 aft sept 15 was good. Nope even more are looping everyday.
I haven't experienced this issue. I have had the screen ghosting issue, and my volume-down button just stopped working altogether a month ago. I've debated sending it in for repair, but I have been able to manage with the on screen controls. I really cannot go two weeks with no phone in my line of work.
Sent from my LGLS992 using Tapatalk
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.