First of i'd like to thank the community! I've ran in to numerous issues and have been graciously saved several times.
I'll start of by providing some context in to the issue.
original configuration:
Unlocked - T-Mobile US SIM
AT&T LG E980 factory tot 4.1.2 - flashed using LG Flashing Tool
Root - E980 Universal Root
Unlocked Bootloader - Freegee [Android Marketplace]
Installed Recovery TWRP v2.6 - Freegee [Android Marketplace]
Removed bloatware - AT&T Applications
So from this point the phone was working as expected. I spent hours configuring to my liking and decided to call it a night. Before I called it quits I decided to make a backup using TWRP. Backup took a really long time but it said successful. I left handset plugged in to charger overnight, roughly 6 hours of continuous charging. When I woke up I noticed the phone was in recovery mode. Touchscreen was also unresponsive. I held the power button to allow it to reboot and it rebooted me back to recovery. At this point I knew something was wrong. I attempted to re-install backup files made from previous night, this failed. The phone booted back to recovery. I then installing some zip files I had pre-loaded on to the external SD card, this was CM10.1 and gapps files for E980. I tried this out a few days ago and it was working fine. I decided lets try installing this and see what happens. Install was successful and rebooted. The phone boots back in to recovery. At this point I'm really frustrated. I checked the memory card by running through the TWRP menu. I noticed the file sizes were unchanged but the files were not displayed on both in/ext memory. I decided to finally restore again by using LG Flashing Tool. This by the way has saved my a$$ numerous times. So the one thing I would note, at the 85% when the phone reboots I noticed there was an error, an error I've never seen before. It was a picture of sync icon (large) and android man on top of it and text that said "error 0x123456" I didn't note the exact string. I let it go and monitored the flashing tool, somewhere around 93-95% it rebooted again in to the normal boot sequence. Viola my phone is back to where I started.
So here's some of the questions I had:
How did I end up in the TWRP Recovery boot loop?
Why could I not see the files to install once in TWRP?
Why did TWRP continuously boot back in to recovery mode after successful install of restore?
Why did TWRP continuously boot back in to recovery mode after successful install of CM10.1/gapps zip?
Has anyone seen the LG Flashing Tool error I described above and does anyone have an explanation as to what happened?
Here's my theory on what happened...
My phone was on 4.1.2 as mentioned. I noticed a few times that there was a notification stating the phone had a OTA software update available. The first time I tried to update (already rooted and unlocked) the phone failed to update. The error cited that my phone was believed to be rooted. I paid no attention to this and decided to continue using. Later in the day I noticed the notification again, I opted to try again. The phone updated, or at least tried to. It kept booting in to TWRP Recovery. Nothing I could do could restore it, except flashing using the LG Tool. After experiencing this I knew to leave the OTA alone. I don't know if this is possible but somehow I think the OTA was pushed and forced through while I was sleeping allowing the phone to charge. This is the only time I've seen that behavior. Is that even possible???
Where am I now...?
Phone is restored, I opted to upgrade using the OTA before I start tinkering again. Maybe I won't mess with it at all and leave it alone at this point.
I was on 13B rooted, then flashed the stock system to return to unroot status. Everything worked fine. Plugged into computer and Verizon Upgrade Assistant suggested upgrade to 13C, so I bit. After a 4 hour (!) download of a 2 Gb file, the upgrade install proceeded without incident, and resulted in a successful completion according to the Assistant. Phone started booting and the Upgrade Assistant re-read the phone as being on 13C, but, the phone stalls and refuses to boot past the Verizon red splash screen. I have pulled battery and tried numerous times to boot, with no luck. It just sticks at the same spot.
Any suggestions? I'm nervous about re-flashing 13 B for fear of bricking it, so perhaps flash 13C kdz?
Thanks in advance for any help.
I have now tried flashing the 13C kdz unsuccessfully a number of times. I verified the checksum on the downloaded kdz file, and attempted to flash it on three separate computers where I had successfully flashed the G4 in the past. Each time that I tried flashing the 13C it reads: "Required Information cannot be found. Contact the system administrator."
I am still stuck here. Even in the flash tool, the phone is read as having 13C on it, but it still will not boot past the Verizon splash screen. Any thoughts on whether I should dare try flashing 13B, or would I end up with even more of a brick then I have now?
Thanks again.
DO NOT FLASH 13B!
Isn't Android 6 24c?
I got stuck on the Verizon screen, but a wipe fixed it at that point.
fr4nk1yn said:
DO NOT FLASH 13B!
Isn't Android 6*?
I got stuck on the Verizon screen, but a wipe fixed it at that point.
Click to expand...
Click to collapse
Thanks, and you are correct on the number, MM is 24C.
May I ask, how were you able to wipe when stuck on the Verizon splash screen? I would love to do that if possible.
Thanks again.
Katmeat said:
Thanks, and you are correct on the number, MM is 24C.
May I ask, how were you able to wipe when stuck on the Verizon splash screen? I would love to do that if possible.
Thanks again.
Click to expand...
Click to collapse
Hold volume down and power on if I remember correctly to put the phone in recovery mode. From there you can choose to do a wipe/factory reset.
I had issues with way long boot times, the wipe fixed that, but then apps kept FC. I ended up downloading the KDZ file and used the flash tool to reflash 24C. Everything is stellar now.
Thank you so much, mikeewhite! I followed your instructions and they worked perfectly, so I am back up and running. You are the reason that I love this list so much, as there are so many people like you generous with their time and advice.
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...
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
I have used LGUP to revert back to MM (I had a Nougat build that I forgot the lock screen pattern). After going through the initial setup I got the Factory Reset Protection message so I tried the FRP removal tricks. To get one to work I had to downgrade to H815 20c firmware. After doing all that I now got a boot loop. I am back up at v29a using a .TOT file but the boot loop is still there. The screen shows the "unlocked boot loader" screen for 5s then the LG logo screen for 13s then a blank screen for 19s then it all repeats again forever.
Does anyone know what I need to do to fix it?
My when I bought the phone I was told that it had the infamous G4 boot loop fixed so I don't think it is that.
Thanks
Darren
My phone is acting really weird now. I managed to use mAid and SALT to get my userdata.img and get my pictures/videos/recordings off the phone. That seems to be the only positive, the rest is all downhill.
My PC is a Windows 10 Home x64 with 16GB RAM if that makes any difference.
I have used LGUP (upgrade and refurbish), various versions of LG Flash Tool (only 2014 did anything, all others had issues with "Failed to Load" messages), LG Bridge, numerous LG USB drivers, downgraded from my broken v29a to 20p, 20d, 20c, 10c and back up to v29a again. I am seeing weird effects such as after flashing a new KDZ and getting to the initial setup I skipped the WiFi and Google logins to get to the basic phone working with ADB and USB debugging to flash TWRP and Magisk.
The phone would reboot when I tried to change the USB settings from MTP. The phone would then loop infinitely whilst connected via USB to the PC but strangely would boot to the normal phone after a few boot loops when connected via USB to a wall charger.
The screen would go blank 2 seconds after getting to the home page of the launcher.
It would also reboot under other repeatable conditions.
I was wondering if certains paritions have been messed up and not even flashing a KDZ (10c, 20c, 20d, 20p) or TOT file (v29a) in Refurbish mode would fix it. I thought a refurbish would put ALL the partitions back to a known state (leaving things like partitions with your IMEI alone). If so, then my phone should then have started behaving itself but it doesn't. After most of these flashings I could actually go through the initial setup stage of the phone but got regular reboots.
Can it really be that I need to setup the WiFi and Google account first? I can't see why that should cause random reboots.
Has anyone got any ideas? Other than the obvious - bin the phone
I managed to update the LAF partition to one that SALT says can now flash partitions but the SALT XDA page says not to flash anything with MM and N. This means SALT is only useful for backups?
Thanks
Darren