Develop Bugs

Nasty Bootloop after Flash on Sprint G2

Last night I installed geefree on my phone from the app store and used it to install TWRP. I downloaded a nightly CM11 and an appropriate gapps. Using geefree I rebooted to recovery (never figured out the button combination to boot to recovery "naturally") and installed both of the zips. This could be where I made my mistake, I installed both at the same time.
Now my phone loops, displaying the LG logo for a few seconds, then shutting off and rebooting before repeating the process. I can't seem to get it to go into download mode or the recovery menu. I've tried power+up, power+down, down+up and each of those while plugging the device in, etc. I can get the device to a hardware key control mode, though it doesn't seem too useful.
How can I save my phone? This forum has been a great resource in the past and I'm very grateful for the many tutorials I've followed rooting other devices. Hopefully you guys can save the day once again!

Volume up plus power is how to access recovery on sprint.
What stock sw version were you on before you flashed cm?
Did you wipe data before flashing?
Sent from my LG-LS970 using xda app-developers app

I was using stock 4.2.2, I believe. I didn't wipe the data (shame on me), a bad habit that I picked up from my first rooted device, the Samsung Moment. It didn't ever matter on that one, afaik. Thanks for the reply!
Edit: Volume up and power whether plugged in or not takes me to the hardware key control mode screen.
Second Edit: http://forum.xda-developers.com/showthread.php?t=2432476&page=35 I also found this thread where someone seems to be experiencing similar issues and they fix it with "LG Utility." Is that a PC application? It's a little vague to google, but I've been trying!

I have a bootloop issue every time i flash a rom i have to wipe all but sd flash roms and gapps the i do a restore from twrp and oly restore my boot image only and they boot no prob

I'm kind of starting to suspect my power button doesn't work at all for whatever reason. I have a lot of difficulty getting the phone to shut down, then it doesn't seem to easily power up. It's a strange collection of problems. Would a Sprint repair place be able to fix this?

If they have parts on hand if not either a swap out or a sendoff

Same problem here - bootloop and no download mode - CWM works! - urgently need help
I guess I have the same problem as InlineFourPower (apart from that my power-button has no problem).
I am stuck in bootloop since I tried to upgrade to Kitkat a few days ago. Now I can´t get into download mode any more, nor into fastboot or anything else. Only CWM works.
From within CWM I can successfully flash ROMs but that doesn´t help, since afterwards I am still stuck in bootloop. It is possible, however, to push files via adb-commands while I am in CWM.
Does anybody have an idea how to go from here or how to get download-mode back?

Device is recognized but can´t be mounted - bricked forever?
Parinibbana said:
I guess I have the same problem as InlineFourPower (apart from that my power-button has no problem).
I am stuck in bootloop since I tried to upgrade to Kitkat a few days ago. Now I can´t get into download mode any more, nor into fastboot or anything else. Only CWM works.
From within CWM I can successfully flash ROMs but that doesn´t help, since afterwards I am still stuck in bootloop. It is possible, however, to push files via adb-commands while I am in CWM.
Does anybody have an idea how to go from here or how to get download-mode back?
Click to expand...
Click to collapse
I tried a few things on Linux.
After terminal-command "ls /dev/sd*" when the device is unplugged from the computer I get "/dev/sda".
When the device is connected via USB, I get: "/dev/sda /dev/sdb"
So sdb is my LG G2.
So I went on to the next command: "gdisk -l /dev/sdb"
As a result I get: "Problem opening /dev/sdb for reading! Error is 123."
Does it mean that the phone isn´t mounted or what? Now I´ve connected my phone to another Linux machine with the same result. It is recognised (p.e. as sdd), but there is no sdd1. Seems as if it is recognized, but can´t be mounted. Does that mean my device is bricked for good? That´s it?

to get the phone into download mode you have to plug the usb cord in and hold VOL+, so to get this right as I have a case on mine, plug the usb into the phone first then hold VOL+ and plug into usb port on the computer.
it does take a loooong time to power down the phone with the button when stuck in a boot loop, just keep holding it until it shuts off, it will shut off eventually!!
plug the phone in while in download mode to install drivers and set com ports, then unplug before you begin your flash with LGFlashTool, hope this helps you out.

Cronic2009 said:
to get the phone into download mode you have to plug the usb cord in and hold VOL+, so to get this right as I have a case on mine, plug the usb in first then hold VOL+ and plug into usb port.
it does take a loooong time to power down the phone with the button when stuck in a boot loop, just keep holding it until it shuts off, hope this helps
Click to expand...
Click to collapse
Thanks Cronic2009 for your advice.
There are, however, szenarios where download-mode is not accessible any more. Neither by using the hardware-keys, nor by using the adb-command.
After four days of resarch and a lot of trial and error, I finally unbricked my F320L using the two adb-commands outlined at the beginning of that thread: http://forum.xda-developers.com/showthread.php?t=2451696
Worked like a charm.
Thanks everyone for your advice.

no problem buddy, glad you got it figured out, good luck to you from here on out!
FYI, that link doesn't work
I just wanted to ask anyone who might know, since the bootloader of the LS980 is locked, we cannot "break" this correct, so no matter what commands we decide to run through root, we cant touch the true bootloader there for LS980 fail safe? (Besides Acts of God, EMP, ect)

Cronic2009 said:
no problem buddy, glad you got it figured out, good luck to you from here on out!
Click to expand...
Click to collapse
Thanks for letting me know. I corrected the link in my previous post.

Be sure if you use a aosp based rom to flash the ZV8 modem. Your can use dr87 or furnance kernals after you flash the zva modem althought i have encountered soft brick due to this.

so i'm having this exact issue and i don't know how to get out of it. i just need to transfer the radio to my phone somehow but nothing shows up under adb devices. i'm trying to the lg mobile support tool now. its downloading the software. but if it doesn't work does any one have any fixes?
edit: i fixed it by following this http://forum.xda-developers.com/showthread.php?p=51637410&highlight=download+fail#post51637410

pitbullmommy45245 said:
so i'm having this exact issue and i don't know how to get out of it. i just need to transfer the radio to my phone somehow but nothing shows up under adb devices. i'm trying to the lg mobile support tool now. its downloading the software. but if it doesn't work does any one have any fixes?
edit: i fixed it by following this http://forum.xda-developers.com/showthread.php?p=51637410&highlight=download+fail#post51637410
Click to expand...
Click to collapse
Thank You for sharing you fixed your issue pittbullmommy but the link you posted points back to a post about a failed run on LGFlashTool, will you please fix the link and point it to the post/guide you used to fix your phone, it may help others stuck in a similar situation, glad to hear you got it fixed and working, best of luck with it from here on out!

Hi all
was just about to start a new thread but didn't want to get into trouble..anyway I am in need of some assistance please.my ls980 has been bricked for some time now been searching all over the internet for a solution to be stuck back at square one.found this video on youtube which is pretty much exactly what my phone is doing.I have used lg flash tool to revert to stock and still nothing I lost root doing that but last night,I managed to regain root access I have no idea how but it happened when i clicked ioroot batch file i went into download mode and it stated bottom left ROOTED in red so i managed that but that is it still doing what is being shown in the video its on youtube
watch?v=PjLF-pBhZSY
please if anyone has the know how I would like to fix this phone rather then bin it thank you all happy 4th everyone

After using tot and flash tool to get back to stock, did you try going into stock recovery and do a factory data reset? I know it sounds stupid especially after a tot but try it. Couldn't hurt
Sent from my LG-LS980 using Tapatalk

Borderline noob here, so please bear with me...
I have been using TWRP 2.7.0.0 to do all my work, and I was able to get the Lego ROM installed with ZVA. I got into too big of a hurry and forgot to make a backup of stock. I've also been unsuccessful in trying to install ZVC modem and firmware. Thankfully ZVA works as does the LEGO ROM, but I'd like to have stock there to access as well. The stockZVC that's on the Android Development page has been getting stuck (bootloop?) on the Sprint Spark logo. I've done TWRP's factory reset with no success. Any help would be great.
Thanks in advance!

Yes sir I've tried that and more to no avail is there anything I can do through adb I'm on stock recovery phone doesn't stay on long enough to install anything

sarfdawg said:
Borderline noob here, so please bear with me...
I have been using TWRP 2.7.0.0 to do all my work, and I was able to get the Lego ROM installed with ZVA. I got into too big of a hurry and forgot to make a backup of stock. I've also been unsuccessful in trying to install ZVC modem and firmware. Thankfully ZVA works as does the LEGO ROM, but I'd like to have stock there to access as well. The stockZVC that's on the Android Development page has been getting stuck (bootloop?) on the Sprint Spark logo. I've done TWRP's factory reset with no success. Any help would be great.
Thanks in advance!
Click to expand...
Click to collapse
You ever get her fixed?

My Xperia S device is stuck in bootloop

Hello.
Recently I've tried to get myself a new ROM. I've decided to choose this one:
http://forum.xda-developers.com/showthread.php?t=2685822
Everything was going just fine. I unlocked bootloader, flashed device, accesed CWM menu, did all the wipes but the dalvik cache one and then my device kinda re-connected through the usb (you know, the sound windows makes when you disconnect and connect device). I had no idea what happened and from that point I can no longer acces my phone. It's stuck at Pac Rom logo. The phone only responds when i turn it on in fastboot mode (power + volume up button). Then a blue led lights up.
Have I really just bricked my phone beyond repair? Could anyone help me?

Revaey said:
Hello.
Recently I've tried to get myself a new ROM. I've decided to choose this one:
http://forum.xda-developers.com/showthread.php?t=2685822
Everything was going just fine. I unlocked bootloader, flashed device, accesed CWM menu, did all the wipes but the dalvik cache one and then my device kinda re-connected through the usb (you know, the sound windows makes when you disconnect and connect device). I had no idea what happened and from that point I can no longer acces my phone. It's stuck at Pac Rom logo. The phone only responds when i turn it on in fastboot mode (power + volume up button). Then a blue led lights up.
Have I really just bricked my phone beyond repair? Could anyone help me?
Click to expand...
Click to collapse
You didn't brick your phone, the latest version isn't working for me too.

Bornon17th said:
You didn't brick your phone, the latest version isn't working for me too.
Click to expand...
Click to collapse
What a relief. But is there any way I can, well unbootloop my phone? In case someone asks, I've already looked through the forums and all the advices were connected to people who can, in fact, acces CWM Recovery menu. My phone is not being recognized by flashtool.

Revaey said:
What a relief. But is there any way I can, well unbootloop my phone? In case someone asks, I've already looked through the forums and all the advices were connected to people who can, in fact, acces CWM Recovery menu. My phone is not being recognized by flashtool.
Click to expand...
Click to collapse
Did you have back up of your current ROM or any other ROM or its zip file ?

Bornon17th said:
Did you have back up of your current ROM or any other ROM or its zip file ?
Click to expand...
Click to collapse
I didn't have any custom ROMs before. This was my first attempt at customizing my phone. The only thing I've done is
followed instructions in this http://forum.xda-developers.com/showthread.php?t=2327473 thread after upgrading my phone to 6.2.B.1.96 Firmware. Then I unlocked bootloader and tried to flash Pac Rom. What should I do?
And one more thing, thank you for such a quick respond.

Revaey said:
I didn't have any custom ROMs before. This was my first attempt at customizing my phone. The only thing I've done is
followed instructions in this http://forum.xda-developers.com/showthread.php?t=2327473 thread after upgrading my phone to 6.2.B.1.96 Firmware. Then I unlocked bootloader and tried to flash Pac Rom. What should I do?
And one more thing, thank you for such a quick respond.
Click to expand...
Click to collapse
Flash stock ROM via flashtools.

[Q] s4 mini doesnt work

my phone dosn't turn on it just flashes the Samsung when i boot it up. i need help dont know what to do
help please

epiczsniperz said:
my phone dosn't turn on it just flashes the Samsung when i boot it up. i need help dont know what to do
help please
Click to expand...
Click to collapse
Boot it holding the volume up button. This should get you into so-called "recovery" where you can, among other things, restore it to defaults.
If recovery also doesn't work (which would be unusual), boot it holding volume DOWN button. This will get you into a "download" mode where you can use ODIN to flash new recovery (such as CWM recovery which is very nice and powerful), or even flash entire firmware from scratch.
Good luck, let us know how it goes ~
[edit] oh and do all that while having it connected to USB power, in case the battery is empty.

still doesnt work
sysKin said:
Boot it holding the volume up button. This should get you into so-called "recovery" where you can, among other things, restore it to defaults.
If recovery also doesn't work (which would be unusual), boot it holding volume DOWN button. This will get you into a "download" mode where you can use ODIN to flash new recovery (such as CWM recovery which is very nice and powerful), or even flash entire firmware from scratch.
Good luck, let us know how it goes ~
[edit] oh and do all that while having it connected to USB power, in case the battery is empty.
Click to expand...
Click to collapse
I tried both methods. Is my phone fixable. I messed it up somehow with Odin and I might have deleqted the software can I reinstall it onto my phone help please

Help!!!!
epiczsniperz said:
I tried both methods. Is my phone fixable. I messed it up somehow with Odin and I might have deleqted the software can I reinstall it onto my phone help please
Click to expand...
Click to collapse
I have the same problem , did you advance it? thx

help
cellsan said:
I have the same problem , did you advance it? thx
Click to expand...
Click to collapse
i couldnt fix it none of the steps worked. what about you?

epiczsniperz said:
I tried both methods
Click to expand...
Click to collapse
Could you clarify what happens when you do those methods exactly?
I think the download mode should basically always work...
[edit] oh wait, I think I mislead you by accident (sorry!). You should boot while holding HOME and volume up (recovery) or down (download).

stilll nothing
​
sysKin said:
Could you clarify what happens when you do those methods exactly?
I think the download mode should basically always work...
[edit] oh wait, I think I mislead you by accident (sorry!). You should boot while holding HOME and volume up (recovery) or down (download).
Click to expand...
Click to collapse
I notice no changes when I did them methods my phone still doesnt turn on

still nothing
I downloaded recovery clockwork and installed . On oden it said pasd but now I cant access recovery booting either

epiczsniperz said:
I downloaded recovery clockwork and installed . On oden it said pasd but now I cant access recovery booting either
Click to expand...
Click to collapse
Anything doesn't work , When I boot while holding HOME and volume up (recovery) appears the blue advice in the upper left corner and about 2 segs after the cellphone restart again, again and so on, When I boot with the down (download) the process on kies working good but when ends the cellphone restart again, again and so on. I'm start to think that something in the hardware is damage :crying:

looks like you messed something up there...
Anyway, if your phone is rooted, and/or you don't care about warranty you can get it in download mode (you said it works fine with kies until reset, so I suppose it means that download mode is at least accessible).
And after that use Odin to reinstall the stock rom completely.
Or, again with Odin install custom recovery, and then whatever ROM you like.
While working with odin, be sure to stick to the guides here on XDA. (for a custom recovery see: http://forum.xda-developers.com/showthread.php?t=2364980)

smartxdev said:
looks like you messed something up there...
Anyway, if your phone is rooted, and/or you don't care about warranty you can get it in download mode (you said it works fine with kies until reset, so I suppose it means that download mode is at least accessible).
And after that use Odin to reinstall the stock rom completely.
Or, again with Odin install custom recovery, and then whatever ROM you like.
While working with odin, be sure to stick to the guides here on XDA. (for a custom recovery see: http://forum.xda-developers.com/showthread.php?t=2364980)
Click to expand...
Click to collapse
I have the custom stock but it still wont boot up

epiczsniperz said:
I have the custom stock but it still wont boot up
Click to expand...
Click to collapse
If you're not entirely stock you'll have trouble using Kies.
I myself had trouble when tried to revert to stock ROM from CM.
It failed to restore NANDroid backup every time, and I also didn't succeed in flashing the stock image with Odin as well.
In the end, I succeeded with this ROM (which is modified stock TW), usin ODIN. You can try this, just read and understand the instructions in the thread before you do anything.
Ironically, after a couple of days after reverting to stock rom I was so annoyed by the speed decrease compared to CM, that I reinstalled CyanogenMod back, found TouchWiz stuff I missed via separate apps, and I'm pretty happy with it ever since.
Bottom Line: anyways, if you already on custom stuff with altered warranty, you must get custom recovery working first, then it will be simple.

LGG3 D850 stuck on firmware update screen

So my mom had an LG G3 D850 from at&t. was totally fine, then she updated whatever she had to 6.0 and it started bootlooping. Tried the LG Flash tool with a tot stock firmware. Went through the whole process got the blue screen with the red 3, it restarted, kept bootlooping. Tried it again but then it got stuck on 5% for like 4 hours, unplugged it and now no matter what i do i cant get into download mode. It shows the LG screen then goes straight to firmware update (even if i dont hold vol up) and it says 910K Bxx QEM (the xx changes) I was able to get into recovery mode, recovered it. same thing. Im losing my mind a little bit here so any advice, or pointing me to a tutorial would be greatly appreciated. Ive looked all over the internet and cant find anything helpful apparently the qualcomm thing where you short the motherboard doesnt work for this phone either?
*flips desk*

If it is under warranty .send your phone to at&t to get it fixed.

Its not
Jahanzaibawan said:
If it is under warranty .send your phone to at&t to get it fixed.
Click to expand...
Click to collapse
warranty expired 6 months ago

evangelion117 said:
warranty expired 6 months ago
Click to expand...
Click to collapse
i have same

Qualcmomm method you are describing is just to bring your phone into download mode. I have done this to my brother's g3. You have to flash using LG flashtool using different settings and then hard reset your phone. If it doesn't solve your problem.try to replace battery and then use custom rom.

tried that
Jahanzaibawan said:
Qualcmomm method you are describing is just to bring your phone into download mode. I have done this to my brother's g3. You have to flash using LG flashtool using different settings and then hard reset your phone. If it doesn't solve your problem.try to replace battery and then use custom rom.
Click to expand...
Click to collapse
no matter what settings i set LG flash tool to it doesnt recognize the phone. and no matter what i do the phone jumps to the firmware update screen, it skips the download mode screen. I have two batteries and ive repeatedly switched them back and forth :/ even after reseting the phone with factory reset it goes back go the firmware update screen

evangelion117 said:
no matter what settings i set LG flash tool to it doesnt recognize the phone. and no matter what i do the phone jumps to the firmware update screen, it skips the download mode screen. I have two batteries and ive repeatedly switched them back and forth :/ even after reseting the phone with factory reset it goes back go the firmware update screen
Click to expand...
Click to collapse
Firmware update screen is the download mode.
Just follow the guide of hyelton to flash your phone.follow steps properly.

still bootloops :/
Jahanzaibawan said:
Firmware update screen is the download mode.
Just follow the guide of hyelton to flash your phone.follow steps properly.
Click to expand...
Click to collapse
totally forgot to switch to com41, did everything exactly like that. got to the red 3, restarted it, and it still bootloops. i guess ill try a custom rom cause this stock one isnt working.

apparently cant do custom roms either, I got it to boot the the set up screen for 5seconds befores it crashed so i guess im throwing it away cause im sick of looking at it.

evangelion117 said:
apparently cant do custom roms either, I got it to boot the the set up screen for 5seconds befores it crashed so i guess im throwing it away cause im sick of looking at it.
Click to expand...
Click to collapse
Try LG PC Suite go to option update error recovery it will download the stock rom flash it dont worry it will take some time so be patient also what happened is when ur g3 wasnt fully updated meaning it got stuck or turned off when updating
.hit like if its helps

Successfuly fixed bootloop problem(?), in doing so created a new problem.. Need ideas

I decided to apply heat to the CPU using a heat gun for 15 seconds. It was extremely hot. I tapped the CPU a few times with another object to see if that would help. Once I put my phone back together, the phone finally turned on, however it would not boot.
So while I can actually fire my phone on now without putting it into the freezer and I can even get into recovery without any issue, the phone will not boot into the system. I have completely backed up all of my files, moved around many files, left the phone in recovery for an hour, and successfully flashed several roms in an attempt to boot into the system, none of this has worked. Instead my phone hangs on "life's good", it does not reboot itself, it stays on this screen for an eternity.
I would like to hear any ideas! I want to test updating the bootloader by flashing the stock rom, but I don't remember which firmware I last flashed and this could brick if flashed in the wrong order, does anyone know how to check the firmware? Another idea, is there any way to debug the boot or is there a boot log to see where it is hanging?
Thanks!

RandomUSA said:
I decided to apply heat to the CPU using a heat gun for 15 seconds. It was extremely hot. I tapped the CPU a few times with another object to see if that would help. Once I put my phone back together, the phone finally turned on, however it would not boot.
So while I can actually fire my phone on now without putting it into the freezer and I can even get into recovery without any issue, the phone will not boot into the system. I have completely backed up all of my files, moved around many files, left the phone in recovery for an hour, and successfully flashed several roms in an attempt to boot into the system, none of this has worked. Instead my phone hangs on "life's good", it does not reboot itself, it stays on this screen for an eternity.
I would like to hear any ideas! I want to test updating the bootloader by flashing the stock rom, but I don't remember which firmware I last flashed and this could brick if flashed in the wrong order, does anyone know how to check the firmware? Another idea, is there any way to debug the boot or is there a boot log to see where it is hanging?
Thanks!
Click to expand...
Click to collapse
Just flash V20p, is good to fix and to downgrade from Nougat.
Maybe you didn't heat only the CPU... the audio chip don't like to heated.
Try vol- + Power, when you see the logo release power for a second and press and keep it, maybe you're able to factory reset.
If it doesn't work, take out battery and put it back again, turn on the phone (even if is stuck on LG logo) and leave it for about 10 minutes.

RuedasLocas said:
Just flash V20p, is good to fix and to downgrade from Nougat.
Maybe you didn't heat only the CPU... the audio chip don't like to heated.
Try vol- + Power, when you see the logo release power for a second and press and keep it, maybe you're able to factory reset.
If it doesn't work, take out battery and put it back again, turn on the phone (even if is stuck on LG logo) and leave it for about 10 minutes.
Click to expand...
Click to collapse
I am certain I did not exclusively heat up the CPU, the board is very small and the output of the heatgun is relatively large. Anyway, I couldn't find anything through google that would indicate heating up the audio chip would cause boot issues, if you have any more information on this I would appreciate it.
The vol-+power allows me to get to my TWRP install, I have an unlocked bootloader and TWRP installed as my recovery. I have completely wiped the device before attempting to install various roms. I have not tried installing 20p as it seems you need to be either on 20o or 20p and I am not sure if downgrading is safe (assuming I am on a later version).
I am shooting in the dark even trying to install a new ROM, the one I had should work obviously. I would really like to check what firmware I am on before upgrading/risking permanently bricking the device. Any boot debugging would be extremely useful if possible

RandomUSA said:
I am certain I did not exclusively heat up the CPU, the board is very small and the output of the heatgun is relatively large. Anyway, I couldn't find anything through google that would indicate heating up the audio chip would cause boot issues, if you have any more information on this I would appreciate it.
The vol-+power allows me to get to my TWRP install, I have an unlocked bootloader and TWRP installed as my recovery. I have completely wiped the device before attempting to install various roms. I have not tried installing 20p as it seems you need to be either on 20o or 20p and I am not sure if downgrading is safe (assuming I am on a later version).
I am shooting in the dark even trying to install a new ROM, the one I had should work obviously. I would really like to check what firmware I am on before upgrading/risking permanently bricking the device. Any boot debugging would be extremely useful if possible
Click to expand...
Click to collapse
I got a very delayed boot up when I thought that my problem with one of the microphones was related with bad welding also. So, I heat it (Qualcomm WCD9330 Audio Codec) and it took a lot for the phone 1st boot after that.
The V20p is flashable no matter what version you have before, just need the right "8994.dll" file to be installed without problems. You can extract it from the v20p.kdz.
Good luck!

RuedasLocas said:
I got a very delayed boot up when I thought that my problem with one of the microphones was related with bad welding also. So, I heat it (Qualcomm WCD9330 Audio Codec) and it took a lot for the phone 1st boot after that.
The V20p is flashable no matter what version you have before, just need the right "8994.dll" file to be installed without problems. You can extract it from the v20p.kdz.
Good luck!
Click to expand...
Click to collapse
I might try playing with the audio chip, but there's currently no indication that the phone will progress past the boot screen. Instead of updating my phone via TWRP, I decided to get set up with LGUP following your advice. I have tried refurbish/upgrade without luck. The process seems to complete entirely and successfully, however my phone still hangs on the boot screen. Perhaps noteworthy, at the boot screen the phone is in standby mode and windows identifies the device as "LGE AndroidNet USB Serial Port (COM4)". This is the same as when it is put into download mode.
Do you know if this is normal behavior?

RandomUSA said:
I might try playing with the audio chip, but there's currently no indication that the phone will progress past the boot screen. Instead of updating my phone via TWRP, I decided to get set up with LGUP following your advice. I have tried refurbish/upgrade without luck. The process seems to complete entirely and successfully, however my phone still hangs on the boot screen. Perhaps noteworthy, at the boot screen the phone is in standby mode and windows identifies the device as "LGE AndroidNet USB Serial Port (COM4)". This is the same as when it is put into download mode.
Do you know if this is normal behavior?
Click to expand...
Click to collapse
Try to don't mess with the audio chip!
Turn ON the phone with no cable connected.
Mine have that long boot only the 1st time, after that behaves normally.
Mine when I connect to PC (USB2), option "Only Charge" on the phone and turn ON, is shown in Device manager as "Android device/ Android Sooner Single ADB Interface"
Also as "Device/G4"
After change the option "Only Charge" to "Multimidia Devica (MTP)", is shown as "Android Device/LGE Mobile ADB Interface".
Also as "Portable Device/G4", and, "Modems/LGE Mobile USB Modem".
Of course that until your phone boot completly you can't do any changes...
In "Firmware Update" mode, comes as "LGE AndroidNet USB Serial Port (COM4)" and also as "Modems/ LGE AndroidNet USB Modem".
BTW... you install "LGUSBModemDriver_Eng_WHQL_Ver_4.9.4_All" and "LGMobileDriver_WHQL_Ver_4.2.0" ? Maybe it helps to have those installed before flash.
Maybe it is the same in some devices (also depending on the phone Firmware version) to have those or others but, mine only work with those two installed.
Try this:
Re-flash with LGUP using the v20p again.
After the process is done and the long boot starts (wait 5 minutes or so), take out the battery, let the phone cool down for 10 minutes.
Insert the battery back on the phone and turn it ON.
Leave it until boot finish, go for a walk, watch some TV, forget about the phone.
Of course that if after 30 minutes stills without boot up, you can consider that you have a problem. And me out of ideas... sorry.
Wish you all the best luck on that, regarrds.

RandomUSA said:
I decided to apply heat to the CPU using a heat gun for 15 seconds. It was extremely hot. I tapped the CPU a few times with another object to see if that would help. Once I put my phone back together, the phone finally turned on, however it would not boot.
So while I can actually fire my phone on now without putting it into the freezer and I can even get into recovery without any issue, the phone will not boot into the system. I have completely backed up all of my files, moved around many files, left the phone in recovery for an hour, and successfully flashed several roms in an attempt to boot into the system, none of this has worked. Instead my phone hangs on "life's good", it does not reboot itself, it stays on this screen for an eternity.
I would like to hear any ideas! I want to test updating the bootloader by flashing the stock rom, but I don't remember which firmware I last flashed and this could brick if flashed in the wrong order, does anyone know how to check the firmware? Another idea, is there any way to debug the boot or is there a boot log to see where it is hanging?
Thanks!
Click to expand...
Click to collapse
first of all: what model? we have 11 models for the g4 and not all behave the same way.
second: use SALT. SALT shows your previously installed firmware
third: try flashing custom ROMs instead of STOCK
fourth: I guess you know about http://bit.do/ilapofixg4 ?
.

steadfasterX said:
...
third: try flashing custom ROMs instead of STOCK
...
.
Click to expand...
Click to collapse
Hi @steadfasterX!
I have a question... apart "bugs", what else have a custom ROM that can make a device with hardware issues run better?
I'm asking because I never had/saw a custom ROM working 100%, even without hardware issues, at least on LG.
There's always something that doesn't work, or, with quality/performance issues.
My doubt is, if a device have problems to boot with the firmware that was exclusively made for it, won't have the same or more issues with another one?
In case of faulty hardware, firmware (stock or not) will make any difference?
Don't think that I'm kind of messing with you. I really have those doubts.
Regards

RuedasLocas said:
Hi @steadfasterX!
I have a question... apart "bugs", what else have a custom ROM that can make a device with hardware issues run better?
I'm asking because I never had/saw a custom ROM working 100%, even without hardware issues, at least on LG.
There's always something that doesn't work, or, with quality/performance issues.
My doubt is, if a device have problems to boot with the firmware that was exclusively made for it, won't have the same or more issues with another one?
In case of faulty hardware, firmware (stock or not) will make any difference?
Don't think that I'm kind of messing with you. I really have those doubts.
Regards
Click to expand...
Click to collapse
I do not say a custom ROM is running better... but for debugging issues its easier to run custom ROMs and they do not have many of the dependencies a STOCK ROM has (like several partitions we never need on custom ROMs but on stock) which can prevent from booting.
.

steadfasterX said:
I do not say a custom ROM is running better... but for debugging issues its easier to run custom ROMs and they do not have many of the dependencies a STOCK ROM has (like several partitions we never need on custom ROMs but on stock) which can prevent from booting.
.
Click to expand...
Click to collapse
Thanks for responding! I have a t-mobile h811 variant, LGUP/SALT currently shows my firmware as 20p, I decided to try updating to 20x using lg bridge, but the firmware is still listed as 20p despite the process being completed 'successfully'.
I know that flashing the KDZ worked because it overwrote my recovery and I no longer have access to TWRP. Before flashing the KDZ I tried several ROMS (stock 20p, aokp, lineage OS).
Now the phone is bordering on being a paperweight because I have no means of installing TWRP. I have an unlocked bootloader but there is no way for me to enter the bootloader. Is it possible to repackage a KDZ with a custom boot image or custom recovery?
Before flashing the KDZ and losing access to TWRP, I tried modifying the system boot.img to limit the number of cores that could be used to 4, and even 2 cores without any luck.
Right now, I don't think the phone has any bootloop issue or heat related problem because powering on the phone has become perfectly functional, the phone does not reboot itself (just stays at "Life's Good" with the blue blinking LED), recovery worked fine and handled a lot of load for hours reaching 40C+ on the CPU and with no issue.