Develop Bugs

Bootloop or something else?

So I rooted my phone by installing the rooted 13b img. And went to install xposed framework and apk. I completed all the steps found here (http://forum.xda-developers.com/g4/themes-apps/guide-installing-xposed-locked-t3181593), and now it is stuck on the android logo....suggestions on what do do from here?
A little more detail: After completing steps verbatim, it would fail to install framework. I then read somewhere else that you need to uncheck not only auto mount but the mount option, as well. I tried that and it seemed like it must have worked as it didn't immediately fail and reboot. However, it got stuck on the android logo and after an hour or so I realized there was problem. I have pulled the battery and rebooted several times. I can boot into download mode, but cannot get it to fully boot. Since I could get it into DL mode, I used LGUP to install the 24C MM update (as I didn't have the 13B on my computer). But the result is the same...stuck on the Verizon logo even after a successful install of 24C.
Is this a case of the hardware failure that others are experiencing or is this software related? I see a lot of people with bootloop issues and mine seems to be similar but different. Mine does get past the LG screen to the next screen, but even installing a stock kdz doesn't seem to help...
UPDATE:
Well I downloaded the stock 13B kdz and flashed it via LGUP and it somehow managed to boot. It looked like it was going to be stuck on the Verizon landing page but after about 10 seconds or so it completed boot up. I have now installed the rooted 13B image and made a backup img. I might try again to install xposed framework - fingers crossed it doesn't screw up this time...

Use hyleton's 'LG G4 Stock Firmware (Go Back to Stock) KDZ & TOT Method' that uses LGFlashTool2014.exe and do a CSE Flash - this will wipe all your data though

SnitchyB said:
Use hyleton's 'LG G4 Stock Firmware (Go Back to Stock) KDZ & TOT Method' that uses LGFlashTool2014.exe and do a CSE Flash - this will wipe all your data though
Click to expand...
Click to collapse
Thanks, I'll look into that. I was hoping that using LGUP to reflash to stock would do it...but I guess I have to remove whatever the flash tool put on my phone when trying to install the xposed framework...

LG G4 H811 bricked? How to recover?

So at first- i backed up all my data on my microsd (and actually- still have it using the LG Backup app included with the phone.)
I didn't even flash a new stock, already had a gsm unlocked device, so i did adb fastboot, unlocked bootloader, installed twrp properly, and pretty much recovered all data after first time booting into the cleared stock Android Marshmallow version (20i.)
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
I used the tutorial above to go through this process.
Everything had seemed fine, flashed/installed root through instructions, had root, etc. Then I went through the process of flashing and getting Xposed through multiple tutorials like this:
http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
The device was now stuck in a boot loop and I could only get into TWRP recovery. So I downloaded the stock flashable zip and flashed it and now- nothing. the screen was black upon reboot. I tried plugging it in, computer is making confirmation sound like a usb device was recognized but nothing pops up. How exactly do I unbrick and get back to stock? I have all my main data still backed up on my microsd.
(Also, I apologize for this being in the wrong forum since I am new. Please redirect me as you please.)

LG G4 H815 Euro - Troubles flashing stock ROM

Hello to all of you,
Thanks in advance for any help you can provide.
I bought second hand a LG G4 H815 with CyanogenMod 14 already installed on it.
Everything was fine until I installed my Ebanking apps, that would not function with an unlocked bootloader. I needed to return to a clean factory safe state...
It was the second time I flashed a rom in my whole life, the first one was a Galaxy S plus years ago.
I followed all the instructions for the KDZ flash in this tutorial but I stumbled upon a "Upgrade stopped due to error" in LG flash tool.
I retried 3 or 4 times but with no luck. I verified that the ROM was correct for my model and it was. European and all...
I tried LGUP but my phone is unknown ( at least it's detected)...
I read some posts and told myself "I probably have messed up something, let's try it again with a fresh thing"... I clicked on the factory reset button and carried on.
There the phone booted on TWRP (That i didn't know existed before this). As I explored the menus with a TWRP google search on the computer, I began to realize that the factory reset was maybe a bad thing to do with a custom rom. I tried to reboot but I always end up booting on TWRP.
I re-tried to flash in download mode, but with always the "Upgrade stopped due to error".
I also tried to flash directly from TWRP a stock rom. Didn't work.
I was beginning to lose it and tried to flash the CM14 version I had before, juste to have a working phone again, but even this didn't work... I'm stuck with a TWRP phone
I need some help there...

FamousCarpet said:
Hello to all of you,
Thanks in advance for any help you can provide.
I bought second hand a LG G4 H815 with CyanogenMod 14 already installed on it.
Everything was fine until I installed my Ebanking apps, that would not function with an unlocked bootloader. I needed to return to a clean factory safe state...
It was the second time I flashed a rom in my whole life, the first one was a Galaxy S plus years ago.
I followed all the instructions for the KDZ flash in this tutorial but I stumbled upon a "Upgrade stopped due to error" in LG flash tool.
I retried 3 or 4 times but with no luck. I verified that the ROM was correct for my model and it was. European and all...
I tried LGUP but my phone is unknown ( at least it's detected)...
I read some posts and told myself "I probably have messed up something, let's try it again with a fresh thing"... I clicked on the factory reset button and carried on.
There the phone booted on TWRP (That i didn't know existed before this). As I explored the menus with a TWRP google search on the computer, I began to realize that the factory reset was maybe a bad thing to do with a custom rom. I tried to reboot but I always end up booting on TWRP.
I re-tried to flash in download mode, but with always the "Upgrade stopped due to error".
I also tried to flash directly from TWRP a stock rom. Didn't work.
I was beginning to lose it and tried to flash the CM14 version I had before, juste to have a working phone again, but even this didn't work... I'm stuck with a TWRP phone
I need some help there...
Click to expand...
Click to collapse
uninstall any drive for g4 from pc and reinstall again and lgup. now reboot phone to download mode when lgup is open first check upgrade opsion and when open kdz check refurbish opsion and start. good luck

Thank you for your answer
Still no luck
Uninstalled drivers
Rebooted PC
Reinstalled the drivers
Still unknown device

The best way to flash stock image is to use official LG Bridge app. Download it, turn off your phone, connect it to PC while holding volume up button - phone will go into download mode. Then there is option for software restore in LG Bridge but i won't tell u where exactly. If it won't work i would try on another PC. If it won't work maybe you would be able to flash stock image trough send_command but i won't help you with it.

FamousCarpet said:
Thank you for your answer
Still no luck
Uninstalled drivers
Rebooted PC
Reinstalled the drivers
Still unknown device
Click to expand...
Click to collapse
open lgup torn off the phone press volume up insert usb cable wait to see download mode on phone release up button and see if everything go fine

Thank you a lot Avantu, the LG Bridge did the trick! I now have a factory rom!

LG G4 boot loop into TWRP

Hello everyone,
yesterday I flashed a new Cyanogenmod 14 nightly (12062016) for my G4 from earlier nightly in TWRP. After reboot the phone keeps going back to TWRP and I can't seem to get it to boot to system..
I tried factory reset, reflashing back to old nightly, flashing stock.. but nothing seems to work.
Also tried doing this in the TWRP terminal:
dd[space]if=/dev/zero[space]of=/dev/block/platform/f9824900.sdhci/by-name/fota
Didn't fix the loop, I guess because it wasn't the OTA update that caused the problem in the first place.
If anyone has an idea, I would greatly appreciate the help!
Thanks.

If you can reach download mode you could try reflashing back to stock then starting again.....Hope you get yours fixed - Sorry to say this but mine did a very similar thing only 24 hours before you posted!!! Only mine was on stock FW and was in use at the time - I've now had to swap it as valuebasket who sold me the phone have ceased trading. If yours is a UK model you may be able to get it replaced under warranty - believe that LG guarantee their phones for 2 years and a ruling by the European court said that flashing a custom rom doesn't invalidate any warranties.

I have the same exact issue, I also flashed the latest CM14 nightly and cannot get the device to boot any rom.
I have even tried flashing stock rom but I get the same problem.
From what I have read, the bootloop issue happens once the device boots but I don't seem to be getting that far.
Any ideas?

Ran into the same problem 3 days ago. This is the first time I have encountered a non-revertible issue in 3 years as a cyanogenmod user. This changes my opinion on how safe it is to make use of a custom ROM. I tried to wipe everything, reinstall TWRP, change TWRP with another recovery, reinstall a safe NAND backup of mine.....nothing.....it went into boot loop. Before I read this post, I was convinced my phone encountered the infamous G4 bootloop problem.....now I see there are other examples, so it shouldn't be the case. Long story short, I had to check my device in at the LG assistance, with 25 days as time forecast.
The guilty nightly was 20161205.
I have never seen anything like this...

This has solved it for me - I installed LG Bridge and flashed the factory firmware using the tool. Now it seems I'm back on stock but at least it's working.

got mine working. I had to install LGUP and flash stock ROM. Once flashed I installed CM14 and I am back up and running again.

I tried LGUP but it could not recognize the device while this was looping.....a bad experience......

I have the same issue. My phone was updated to 20i via the original stock firmware, then I put twrp 3.0.2-0 and cyanogenmod on. I did a cyanogenmod update from within cyanogenmod, which just booted into twrp, then I manually installed the update zip that cyanogenmod had downloaded, then it always boots into twrp. I wonder if initiating the update from within cyanogenmod was the cause. The phone is not detected by LGUP or LG Bridge. I've tried this on a win10 machine, and a win7 vm from linux. I have access to twrp, and download mode by doing the reboot into bootloader from within twrp.
If those people who have fixed this could give more details about how they did it, that would be good. What exact steps did you take? What stock firmware version did you have before installing a custom rom? What OS version were you using? What twrp version?

Well. Mine got stuck in bootloop for the second time today. What is going on? In between the two bootloops I had one good update with CM. Using TWRP 3.0.2.1. Steps to reproduce failure: updating CM from within CM, it autoreboots into TWRP and after that nothing happends, no autoinstall. Then after a manual install of the new CM the bootloop starts.
Resolve the problem:
* Install LGUP 8994 DLL Ver 0 0 3 23, Install LGUP Install Ver 1 14, get the latest KDZ
* Get the phone into download mode with usb cable and after that in firmware update mode
* Startup LGUP and choose refurbish and select the kdz file.
* After that you can boot into your stock LG firmware again, reinstall TWRP an CM. If you want so.

Read that it is advised to manual update cm from within TWRP. TWRP will get an update in the future to solve this bootloop problem.

iankelling said:
I have the same issue. My phone was updated to 20i via the original stock firmware, then I put twrp 3.0.2-0 and cyanogenmod on. After a cyanogenmod update, it always boots into twrp. The phone is not detected by LGUP or LG Bridge. I've tried this on a win10 machine, and a win7 vm from linux. I have access to twrp, and download mode by doing the reboot into bootloader from within twrp.
If those people who have fixed this could give more details about how they did it, that would be good. What exact steps did you take? What stock firmware version did you have before installing a custom rom? What OS version were you using? What twrp version?
Click to expand...
Click to collapse
I second that. Same issue and neither LG Up nor LG Bridge will recognize my device. Looking in device manager there are no serial interfaces. Do I need a special driver that provides a com port for a phone in recovery or fastboot mode?
---Edith 2016-12-12: Found a solution for my issue:
The phone has to be in _download_ mode, not in recovery or fastboot. After realizing that I have to boot the phone in a different manner, it will be recognized by LG UP.
Here is how to boot the pone in download-mode:
- Power off your LG device.
- Press and hold Volume Up button.
- Connect your device to PC with a USB cable while holding the Volume Up button.
- You’ll boot into download mode with “Firmware Update” written on top of the screen.
Now everything is fine again.

croclacrimae said:
Hello everyone,
yesterday I flashed a new Cyanogenmod 14 nightly (12062016) for my G4 from earlier nightly in TWRP. After reboot the phone keeps going back to TWRP and I can't seem to get it to boot to system..
I tried factory reset, reflashing back to old nightly, flashing stock.. but nothing seems to work.
Also tried doing this in the TWRP terminal:
dd[space]if=/dev/zero[space]of=/dev/block/platform/f9824900.sdhci/by-name/fota
Didn't fix the loop, I guess because it wasn't the OTA update that caused the problem in the first place.
If anyone has an idea, I would greatly appreciate the help!
Thanks.
Click to expand...
Click to collapse
I was able to get out of that by also wiping by-name/misc. Don't do that, though, because then your wifi mac address will get messed up and you'll spend all day looking for a permanent fix for that.
I suggest reflashing a stock KDZ using LGUP, as others have said. You can get the usb drivers from LG Bridge.

I will release a fix for that soon. Check the twrp thread for updates on this.

Hi
I also have this problem
I installed cm-14.1-20161201-NIGHTLY-h815 successfully and was running it for almost 2 weeks without issues, today I updated to cm-14.1-20161213-NIGHTLY-h815 from cmupdater and I have been ending up in recovery every time I rebooted.
I tried flashing the latest cm recovery and reflashing the rom, with full wipes but no luck.
Full steps of recovering would be appreciated (for example, there are comments about flashing the latest stock rom, but a link to this rom would be helpful)
Thanks

Good news regarding this:
http://forum.xda-developers.com/showpost.php?p=70082901&postcount=213
The above will fix TWRP bootloop issues as well and I also released a first h811 version which should allow installing CM etc as it should.
Keep in mind that this is a BETA and not an official TWRP release.
Please report back in the above thread!
.

Does your twrp beta really fix the boot loop even it is already happening. What do I have to wipe? I have not managed to get out of the boot loop despite intalling it.
Is using using LG Up to flash to the stock rom really the only option?
Edited 2017-01-25 2:45 pm:
Well, sometimes you just have to be patient. Powered down the phone and when th H815 restarted CM did boot. Great. :good:

Hey, I just want to share a small detail, possibly a fluke that helped me overcome the bootloop.
So...I started with a fresh, stock H815, I don't quite remember the firmware version..it was something like version "20g"..
OK, I looked up several guides and tried to get the newest stable versions of each tool. I went through with the official bootloader unlock, then moved on to rooting: Kingroot didn't work for me so I went on installing twrp in fastboot mode so I could afterwards install supersu and root.
I got there eventually but first I was stuck in bootloop - kept ending up in twrp interface. I found the 2 dd commands but those didn't work for me as the msm_sdcc folder did not exist, but instead there was a "f9824900.sdhci". Tried to overwrite this one ...but as others have stated as well, it didn't work.
At that point, I had nothing to lose, I was starting to accept that I had soft-bricked my precious G4 so..I went on installing the DU 10.6 7.1.1 rom and the stock gapps, wiped dalvik, rebooted and held my breath...not literally
About 12 minutes later, after an endless red, spinning logo, my shiny ping pong paddle showed me a different screen, a fresh start welcome screen .
Almost 24h / 10-12 reboots (twrp included) / 70+ apps installed and removed later, the new OS holds around 2G ram average, a bit better battery life, smoother transitions, flawless navigation, flush streaming over both 3G/LTE & 2.4/5 G wifi.
FYI the reboots were intended, wanted to see consistency in boots - we're in the green . Now testing long term stability with moderate/high usage.
There is 1 aspect I noticed, there are a couple of contexts when the interface burps (several menus, various situations, never in apps) and resets back to homescreen...but I think that's more of a launcher topic than an OS one.
Other than that, so far I'm happy with the mod.
Hope my experience helps others that might be in the same spot I was or at lest boosts their confidence to try out a decent idea they might be pondering.

2017 LG G4 Stuck in Boot Loop?

I unlocked an H812 (2017 version... serial starts with 702) several months ago and successfully flashed a stock Nougat ROM. Everything was working great until now. This past week, it randomly started shutting down. Yesterday, it got to the point where I could no longer boot into the OS. I think I got to the unlock screen once, and then it shut off. Now it simply boot loops. There is no SD card in the phone. I couldn't figure out how to get into Safe Mode from TWRP, so I did a factory reset. Still boot loop. I then did a factory reset + wiped the internal drive, and then reinstalled Stock N ROM. Still boot looped. Tried reinstalling the ROM again. Still in a boot loop. I know LG G4 has hardware issues. However, I can boot into TWRP just fine, the temperature doesn't look crazy at all, and it can stay in TWRP indefinitely without shutting down.
Something I noticed after wiping the internal drive is that when I'm finished installing N stock, it says it's successful, but when I checked the File Manager to look in the internal SD card, it still shows it as blank (with the exception of a TWRP folder). Is this normal? Isn't the operating system supposed to be installed on this? Why is it telling me that it's finished installing, and yet nothing is there. For fun, I tried booting up, and I'm still in a boot loop. But I assume it's because I have no OS? Or does the internal sd populate with files upon bootup?
I also used used fastboot and flashed the 4 core image (H811 because GPT compatibility said H811). And I also flashed the 4 core TWRP. I tried installing the stock N again, and file manager still shows no files or folders on internal sd except for TWRP folder. Phone still stuck in boot loop (no OS)?
Please, someone help!
I spoke with LG in case it is a motherboard issue, and they said they only replace the 2015 and 2016 model motherboards for free.

threehappypenguins said:
I unlocked an H812 (2017 version... serial starts with 702) several months ago and successfully flashed a stock Nougat ROM. Everything was working great until now. This past week, it randomly started shutting down. Yesterday, it got to the point where I could no longer boot into the OS. I think I got to the unlock screen once, and then it shut off. Now it simply boot loops. There is no SD card in the phone. I couldn't figure out how to get into Safe Mode from TWRP, so I did a factory reset. Still boot loop. I then did a factory reset + wiped the internal drive, and then reinstalled Stock N ROM. Still boot looped. Tried reinstalling the ROM again. Still in a boot loop. I know LG G4 has hardware issues. However, I can boot into TWRP just fine, the temperature doesn't look crazy at all, and it can stay in TWRP indefinitely without shutting down.
Something I noticed after wiping the internal drive is that when I'm finished installing N stock, it says it's successful, but when I checked the File Manager to look in the internal SD card, it still shows it as blank (with the exception of a TWRP folder). Is this normal? Isn't the operating system supposed to be installed on this? Why is it telling me that it's finished installing, and yet nothing is there. For fun, I tried booting up, and I'm still in a boot loop. But I assume it's because I have no OS? Or does the internal sd populate with files upon bootup?
I also used used fastboot and flashed the 4 core image (H811 because GPT compatibility said H811). And I also flashed the 4 core TWRP. I tried installing the stock N again, and file manager still shows no files or folders on internal sd except for TWRP folder. Phone still stuck in boot loop (no OS)?
Please, someone help!
I spoke with LG in case it is a motherboard issue, and they said they only replace the 2015 and 2016 model motherboards for free.
Click to expand...
Click to collapse
Refer to FAQ # 5a in the UsU unlock thread.
Did you do a clean flash of the rom? If not, wipe cache, dalvik cache, system and most important, format data, before installing the rom again.
I note you did not mention flashing the appropriate gapps for the rom version you're trying to boot up. Maybe an idea if you didn't.
If all else fails, go to IRC (Support / IRC Channel paragraph in the UsU unlock thread OP) and get help directly from steadfasterX.

sdembiske said:
Refer to FAQ # 5a in the UsU unlock thread.
Did you do a clean flash of the rom? If not, wipe cache, dalvik cache, system and most important, format data, before installing the rom again.
I note you did not mention flashing the appropriate gapps for the rom version you're trying to boot up. Maybe an idea if you didn't.
If all else fails, go to IRC (Support / IRC Channel paragraph in the UsU unlock thread OP) and get help directly from steadfasterX.
Click to expand...
Click to collapse
Yes, I did a clean flash. wiped cache, dalvik cache, system, and also formatted data (yes, formatted, not just wipe). I did not flash gapps because I flashed a stock Nougat ROM (the same one that has been working for months).
I'm really hoping to know whether it's normal for file manager to be blank and not show the Android, data, folders and all that. I want to know if those folders populate upon a successful bootup, or if they're supposed to be there right after the ROM says it's successfully flashed. That way I can tell if there is an issue with the ROM not installing (which if that is the case, of course I can't boot up).
I have been posting on the UsU thread, but steadfasterX said to flash 4 core boot rom and 4 core TWRP. I did that, but still no boot up. And I *think* there is no boot up because I have no operating system? Again, what is supposed to be in file manager after a ROM flash? I asked steadfasterX but have not gotten an answer.

threehappypenguins said:
Yes, I did a clean flash. wiped cache, dalvik cache, system, and also formatted data (yes, formatted, not just wipe). I did not flash gapps because I flashed a stock Nougat ROM (the same one that has been working for months).
I'm really hoping to know whether it's normal for file manager to be blank and not show the Android, data, folders and all that. I want to know if those folders populate upon a successful bootup, or if they're supposed to be there right after the ROM says it's successfully flashed. That way I can tell if there is an issue with the ROM not installing (which if that is the case, of course I can't boot up).
I have been posting on the UsU thread, but steadfasterX said to flash 4 core boot rom and 4 core TWRP. I did that, but still no boot up. And I *think* there is no boot up because I have no operating system? Again, what is supposed to be in file manager after a ROM flash? I asked steadfasterX but have not gotten an answer.
Click to expand...
Click to collapse
I know when I've clean flashed a rom in TWRP, I show no files in Internal in the USB connection screen. If you didn't get an error indicating no OS installed, I wouldn't worry about that for now.
Again, refer to FAQ #5a. Did you immediately flash the baseband file after the rom flash? Did you re-install the N modem? etc, etc. You may have to re-install the bootloader stack etc. Go through all the steps.
And again, go to IRC if all else fails.
Note: Please learn to use the Thanks button (bottom right of post), when members answer your questions or provide useful information when trying to help. It's an XDA courtesy - please learn to use it.

sdembiske said:
I know when I've clean flashed a rom in TWRP, I show no files in Internal in the USB connection screen. If you didn't get an error indicating no OS installed, I wouldn't worry about that for now.
Again, refer to FAQ #5a. Did you immediately flash the baseband file after the rom flash? Did you re-install the N modem? etc, etc. You may have to re-install the bootloader stack etc. Go through all the steps.
And again, go to IRC if all else fails.
Note: Please learn to use the Thanks button (bottom right of post), when members answer your questions or provide useful information when trying to help. It's an XDA courtesy - please learn to use it.
Click to expand...
Click to collapse
Here's what I've done now at this point. I tried creating and flashing a 2 core boot image via fastboot, and then flashing the 2 core TWRP. Still bootloop.
I flashed the v29a N modem and UsU kernel for my device (H812), then went to TWRP and flashed stock N ROM again. Still bootloop.
I flashed N stock modem again, then baseband package for my model. Still bootloop.
I'm about to extract my MM modem and flash that.
Beyond that, I don't know what to do. I had zero issues with the UsU method originally and everything went fine and has been fine for the last couple of months since I did it.

Well, roadblock again. I attempted to extract modem from the kdz with SALT in FWUL, and after a while, I get a popup window that says: "This KDZ has an ARB of: arb-detect-error" and then it says "Select partition(s) to EXTRACT:"
Except there are no partitions to select. And my only options are "Deselect All" "Extract" and "Abort." If I try "Extract," I get the error, "No partition selected or abortioned by user."
I did make sure I had the latest version of SALT.

Gave up on salt to extract the kdz and turned to Windows. I didn't know what else to do. I was able to extract the .dz, and then extract the modem_32768.bin file. Transferred it to FWUL, renamed it modem_32768.img, and then typed
Code:
fastboot flash modem modem_32768.img
Rebooted, and still have boot loop.
I'm going to investigate this bootloader stack thing (I don't even know what that is). But again, I really don't understand why this all worked fine for a couple of months.

threehappypenguins said:
Gave up on salt to extract the kdz and turned to Windows. I didn't know what else to do. I was able to extract the .dz, and then extract the modem_32768.bin file. Transferred it to FWUL, renamed it modem_32768.img, and then typed
Rebooted, and still have boot loop.
I'm going to investigate this bootloader stack thing (I don't even know what that is). But again, I really don't understand why this all worked fine for a couple of months.
Click to expand...
Click to collapse
Read about the ilapo it can't be fixed by software it may just help to enlenghten life.
Sent from my OnePlus 6T using XDA Labs