Develop Bugs

LG G4 NOT stuck in bootloop but not booting past LG logo [goes off]

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

i've been blue screen'd D:

on saturday my phone suddenly shut off and shows no signs of life except the lg logo and then a blue screen sometimes. can anyone confirm the whole "putting the mainboard in the oven" thing to actually work? and if yes, how exactly should i do it?

Quote100 said:
on saturday my phone suddenly shut off and shows no signs of life except the lg logo and then a blue screen sometimes. can anyone confirm the whole "putting the mainboard in the oven" thing to actually work? and if yes, how exactly should i do it?
Click to expand...
Click to collapse
That sounds a little extreme TBH with you. I've only heard of people doing the oven trick for the flickering LCD fix, but I haven't paid too much attention lately so I could be wrong.
Please provide more info:
d850 rt? still on fulmics? can you manually boot into recovery(doubt it if you're blue screened but had to ask)? have you tried flashing a TOT or KDZ and going back to stock yet?

startswithPendswithOOH said:
That sounds a little extreme TBH with you. I've only heard of people doing the oven trick for the flickering LCD fix, but I haven't paid too much attention lately so I could be wrong.
Please provide more info:
d850 rt? still on fulmics? can you manually boot into recovery(doubt it if you're blue screened but had to ask)? have you tried flashing a TOT or KDZ and going back to stock yet?
Click to expand...
Click to collapse
yes d850 and yes i am still on fulmics but according to numerous other threads on different forums, this isn't a software issue. I can't get into download mode at all as the phone shows no signs of life when the power button is pressed or when its plugged in

Board expired
Quote100 said:
yes d850 and yes i am still on fulmics but according to numerous other threads on different forums, this isn't a software issue. I can't get into download mode at all as the phone shows no signs of life when the power button is pressed or when its plugged in
Click to expand...
Click to collapse
It's time to move on.same happened to me a week ago.and I found the reason that my charger was at fault .the charger damaged one of the ics.it causes the board to draw a lot of current and causing severe heating issue within seconds.
So,better buy a new phone.

Quote100 said:
yes d850 and yes i am still on fulmics but according to numerous other threads on different forums, this isn't a software issue. I can't get into download mode at all as the phone shows no signs of life when the power button is pressed or when its plugged in
Click to expand...
Click to collapse
Welp...that doesn't sound good. One last question(i think you already answered, but double checking)- so with power off, plugging the usb cable into a pc & holding vol up does nothing at all?
I guess if you're in "last resort mode" the oven may be the way to go, but I have not done it myself so I can't help much there. Here's a post from someone who had success using the oven... http://forum.xda-developers.com/showpost.php?p=68235296&postcount=7
I'd be nervous and would do it as the absolute last resort, but you could be at the "what do I have to lose, so why not?" point by now. You may want to PM the poster(or anyone else who has had success) for more info if you need it & to see if it is a lasting fix or not.
Good luck! :fingers-crossed:

startswithPendswithOOH said:
Welp...that doesn't sound good. One last question(i think you already answered, but double checking)- so with power off, plugging the usb cable into a pc & holding vol up does nothing at all?
I guess if you're in "last resort mode" the oven may be the way to go, but I have not done it myself so I can't help much there. Here's a post from someone who had success using the oven... http://forum.xda-developers.com/showpost.php?p=68235296&postcount=7
I'd be nervous and would do it as the absolute last resort, but you could be at the "what do I have to lose, so why not?" point by now. You may want to PM the poster(or anyone else who has had success) for more info if you need it & to see if it is a lasting fix or not.
Good luck! :fingers-crossed:
Click to expand...
Click to collapse
I also ventured for the oven.and within 2 seconds.my board was gone...oven trick is just a sarcasm.don't go for it.
You can extra life of 30 minutes by giving it a Sunbath for some time.

My bad - misquoted a poster.

I kind of forgot about this thread whoops
Well I have news for you guys, I got a used g3 from eBay and wanted my apps from my old phone back and you know what I did?
I stuck it into the oven. I **** you not, after 375 for 5 minutes it started working again and I was able to get my apps and data to an SD card. Its still working but I took the battery out of it to use with the replacement. Can't believe it worked tbh

Really...really bricked OnePlus 3

Hi guys, I would like to share my experience with a bricked OP3, I own my OP3 about 3 months ago, currently I'm running 3.5.3 CB, and zero problems with the device until now.
My younger brother has his OP3 about two months ago, and I don't know what's he thinking but he flashed a CM12 on his OP 3. Really I don't understand why a person could do that, however he really screw the phone. Never return from death.
I've tried all guides and possible solutions for the brick, there is no bootloader, no recovery, no vibration, no anything. The phone is really dead.
The device it's recognized by the pc after installing qualcomm drivers and after pressing power +volume up buttons, like qualcomm 9008, and it gets recognized by the unbrick took (msm download tool v3.0).
And when I start the tool it start to flash anything goes apparently well, green successful message. But phones continue as a expensive brick.
When I plugged the phone like it should be, pressing only volume up and connecting cable it gets correctly recognized like qualcomm 9008, and by the tool, but when I hit start, it give me that saharra communication failed message.
But when I unplugged and connect again and hit power + volume up, gets recognized again but I doesn't have that Sahara error and even its flashed with the tool, but phone continue to be dead.
I've disassembled the phone to see if I can see some simple trouble in the hardware maybe, I tested changing parts with my phone to see if the trouble is in some charging or display or anything like that, but all parts are working well.
Even I've put my motherboard on the dead phone and it works perfectly.
I can give up to leave this phone dead like that but I've tried anything possible so I'm planning selling spare parts.
In my country I don't have any SAT or any place like that to repair the phone.

dannytgt said:
Hi guys, I would like to share my experience with a bricked OP3, I own my OP3 about 3 months ago, currently I'm running 3.5.3 CB, and zero problems with the device until now.
My younger brother has his OP3 about two months ago, and I don't know what's he thinking but he flashed a CM12 on his OP 3. Really I don't understand why a person could do that, however he really screw the phone. Never return from death.
I've tried all guides and possible solutions for the brick, there is no bootloader, no recovery, no vibration, no anything. The phone is really dead.
The device it's recognized by the pc after installing qualcomm drivers and after pressing power +volume up buttons, like qualcomm 9008, and it gets recognized by the unbrick took (msm download tool v3.0).
And when I start the tool it start to flash anything goes apparently well, green successful message. But phones continue as a expensive brick.
When I plugged the phone like it should be, pressing only volume up and connecting cable it gets correctly recognized like qualcomm 9008, and by the tool, but when I hit start, it give me that saharra communication failed message.
But when I unplugged and connect again and hit power + volume up, gets recognized again but I doesn't have that Sahara error and even its flashed with the tool, but phone continue to be dead.
I've disassembled the phone to see if I can see some simple trouble in the hardware maybe, I tested changing parts with my phone to see if the trouble is in some charging or display or anything like that, but all parts are working well.
Even I've put my motherboard on the dead phone and it works perfectly.
I can give up to leave this phone dead like that but I've tried anything possible so I'm planning selling spare parts.
In my country I don't have any SAT or any place like that to repair the phone.
Click to expand...
Click to collapse
Damn that sucks. He probably flashed the wrong rom or something else. You should contact oneplus and see if they can do something about it cuz i reckon your brother's phone still has warranty.

dannytgt said:
Hi guys, I would like to share my experience with a bricked OP3, I own my OP3 about 3 months ago, currently I'm running 3.5.3 CB, and zero problems with the device until now.
My younger brother has his OP3 about two months ago, and I don't know what's he thinking but he flashed a CM12 on his OP 3. Really I don't understand why a person could do that, however he really screw the phone. Never return from death.
I've tried all guides and possible solutions for the brick, there is no bootloader, no recovery, no vibration, no anything. The phone is really dead.
The device it's recognized by the pc after installing qualcomm drivers and after pressing power +volume up buttons, like qualcomm 9008, and it gets recognized by the unbrick took (msm download tool v3.0).
And when I start the tool it start to flash anything goes apparently well, green successful message. But phones continue as a expensive brick.
When I plugged the phone like it should be, pressing only volume up and connecting cable it gets correctly recognized like qualcomm 9008, and by the tool, but when I hit start, it give me that saharra communication failed message.
But when I unplugged and connect again and hit power + volume up, gets recognized again but I doesn't have that Sahara error and even its flashed with the tool, but phone continue to be dead.
I've disassembled the phone to see if I can see some simple trouble in the hardware maybe, I tested changing parts with my phone to see if the trouble is in some charging or display or anything like that, but all parts are working well.
Even I've put my motherboard on the dead phone and it works perfectly.
I can give up to leave this phone dead like that but I've tried anything possible so I'm planning selling spare parts.
In my country I don't have any SAT or any place like that to repair the phone.
Click to expand...
Click to collapse
Really sorry To hear it?? BUT CM12 rom??? ? where he find it....?? if you hard bricked phone.. go to a expart devs shop.. he may be solved your problem

If your phone will not power on oneplus service center person are also not able to check how your phone will dead i think so you can claim the warranty.

CM 12 roms developed for One Plus 2,I don't really now why in the hell he do that, but he did it: https://forums.oneplus.net/threads/cyanogenmod-os-12-1-yog4pas1n0-update-25-08-15.349531/
What do you mean with expert dev shop?
Anyway I didn't think I will find some like that shop, I'm in Buenos Aires, Argentina, and maybe 99% of the cellphones technician didn't know anything about Oneplus 3,that's the reason why I've disassembled by miself.

dannytgt said:
CM 12 roms developed for One Plus 2,I don't really now why in the hell he do that, but he did it: https://forums.oneplus.net/threads/cyanogenmod-os-12-1-yog4pas1n0-update-25-08-15.349531/
What do you mean with expert dev shop?
Anyway I didn't think I will find some like that shop, I'm in Buenos Aires, Argentina, and maybe 99% of the cellphones technician didn't know anything about Oneplus 3,that's the reason why I've disassembled by miself.
Click to expand...
Click to collapse
No wonder why it got bricked xD. You should see if you still have the warranty for your brothers phone. Contact oneplus and see if they can replace the phone.

I contact oneplus and they say me I wanna contact my seller to review warranty, but I bought on "Mercado libre" some trading online place like ebay.
So we are in a really bad situation.

dannytgt said:
I contact oneplus and they say me I wanna contact my seller to review warranty, but I bought on "Mercado libre" some trading online place like ebay.
So we are in a really bad situation.
Click to expand...
Click to collapse
Well ****. Can't you contact the seller that you bought it from? Also your brother should be careful next time he flashes a rom. We all make mistakes, sometimes ppl have to learn it the hard way.

Yes this will be the first phone since 2005 year when I started to flash custom roms on samsung omnia i900, thats really dead, I bring from the death a lot of bricked phones. But this phone is really dead so I think I will start sparing parts, maybe we can recover some of the money invested on the device.

[HELP!] Bricked OnePlus 5T

Okay, well, hi y'all!
I have been around here, been fixing phones from your tutorials here since around 2012, so I am experienced with flashing etc.
This time though, it has got me on the point of just throwing the device away.
So, its about my mothers OnePlus 5T. It doesnt respond to anything I do to it. It won't turn on, it won't boot in to Qualcomm download mode nor in to recovery or fastboot. The device has not been tempered with before, I dont think my mother knows how to flash it
So, this is what exactly happened, according to my mother.
She woke up, got on to facebook and has been browsing a little, untill suddenly the phone turned black, gave her a warning in the left upper corner of the screen, which said something like; warning, do not share personal info. Or something like that, after that, it gave the logo of OP, and then never got a response from it ever since.
It does not react to pressing buttons, nothing, no led nothing. Charger doesnt give any response, neither did my pc with the qualcomm drivers installed.
So currently it is literally a brick, and I hope somebody can help me. I have a lot of background with flashing etc, so if the answer is really complex, no problem!
Thanks in advance,
Dane

Oneplus 5t issue
contact Oneplus.com and get a RMA to return the unit for repair or replacement. they are very friendly but not much help with trouble shooting.
daneburnes said:
Okay, well, hi y'all!
I have been around here, been fixing phones from your tutorials here since around 2012, so I am experienced with flashing etc.
This time though, it has got me on the point of just throwing the device away.
So, its about my mothers OnePlus 5T. It doesnt respond to anything I do to it. It won't turn on, it won't boot in to Qualcomm download mode nor in to recovery or fastboot. The device has not been tempered with before, I dont think my mother knows how to flash it
So, this is what exactly happened, according to my mother.
She woke up, got on to facebook and has been browsing a little, untill suddenly the phone turned black, gave her a warning in the left upper corner of the screen, which said something like; warning, do not share personal info. Or something like that, after that, it gave the logo of OP, and then never got a response from it ever since.
It does not react to pressing buttons, nothing, no led nothing. Charger doesnt give any response, neither did my pc with the qualcomm drivers installed.
So currently it is literally a brick, and I hope somebody can help me. I have a lot of background with flashing etc, so if the answer is really complex, no problem!
Thanks in advance,
Dane
Click to expand...
Click to collapse

Dead P2

Tried to calibrate battery. During the night, I think battery went down to 0%, and now I am unable do charge the phone. It's stuck at Lenovo logo. When I plug in charger, nothing happends. No LED indicating that phone is charging. When I entered fastboot and press shut down, it shuts down. Then I again, plug in charger, red LED blinks for a second and it again shows Lenovo logo. Tried also connecting it to PC, no result. Can't enter the TWRP either.
Any ideas?
Edit:
Looks like I lost TWRP and rom, I have no idea what has happend. Now I cant install TWRP, I mean it shows proper installation but when I do fastboot reboot recovery - phone doesnt respond. The same with trying to flash stock rom. It flashes all chunks of rom+recovery, but after trying to reboot - BIG NOTHING.
I have a bad feeling that internal memory of my P2 had failed. It looks like my 5 yr journey with P2 has come to an end.

what about “fastboot boot twrp*.img” command? Is it getting stuck at Lenovo logo as well?

XiaoAk said:
what about “fastboot boot twrp*.img” command? Is it getting stuck at Lenovo logo as well?
Click to expand...
Click to collapse
Yes, it tries to reset and returns to lenovo boot logo Only thing I am able to access is original fastboot.

@amdyss
Did this just happen randomly one day? What condition was the battery in?

eried1 said:
@amdyss
Did this just happen randomly one day? What condition was the battery in?
Click to expand...
Click to collapse
Yap, one day I was happily using new Android 13, everything was ok. For an almost 5yo phone - battery was ok I think. I managed one whole day, and in the evening I ususally had 20%. Next morning it died. Now I am waiting for a battery to discharge completely and I will try again to flash TWRP or stock rom. But I am not giving much hope.
Theoreticaly on adb says ok after flashing twrp. But when I try to enter twrp, vol+-, it gives me black screen, phone switches off.

amdyss said:
Yap, one day I was happily using new Android 13, everything was ok. For an almost 5yo phone - battery was ok I think. I managed one whole day, and in the evening I ususally had 20%. Next morning it died. Now I am waiting for a battery to discharge completely and I will try again to flash TWRP or stock rom. But I am not giving much hope.
Theoreticaly on adb says ok after flashing twrp. But when I try to enter twrp, vol+-, it gives me black screen, phone switches off.
Click to expand...
Click to collapse
Pretty odd. I don't think the battery went bad all of a sudden.
I have a P2 with a six year old battery that I have not replaced. I manage to get a day of use, but I should probably transfer important files right away.

eried1 said:
Pretty odd. I don't think the battery went bad all of a sudden.
I have a P2 with a six year old battery that I have not replaced. I manage to get a day of use, but I should probably transfer important files right away.
Click to expand...
Click to collapse
I'll try one more method before I annouce my P2 as a dead phone. Its really sad as I looked around and am confuse what to choose next. I have an opportunity to buy another P2 in a great condition but on the other hand it will be still a 5yo phone. I saw it. It still runs android 7 as the owner did not have the knowledge to unlock bootloader. I also have Moto z3play in my drawer, with broken screen, I have a friend to help me replace it. Any advices welcome.

amdyss said:
I'll try one more method before I annouce my P2 as a dead phone. Its really sad as I looked around and am confuse what to choose next. I have an opportunity to buy another P2 in a great condition but on the other hand it will be still a 5yo phone. I saw it. It still runs android 7 as the owner did not have the knowledge to unlock bootloader. I also have Moto z3play in my drawer, with broken screen, I have a friend to help me replace it. Any advices welcome.
Click to expand...
Click to collapse
Really old phones might have unlocking problems. So that's something to be aware of.
I think you should buy a newer phone. Go for Motorola and low-budget since they only receive one OS upgrade with only a tiny chance of ROMs in the future.

I am back . I bought p2 with faulty screen and switched my screen to p2 with good mainboard. Now I wait for OEM unlock and I am alive

Great news, man. P2 will outlive us all !