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.
Well, as usual, I've managed to mess things up and here I am again. Somehow, I installed something or other that required rebooting. When I did, I kept getting an error that the systemui was messed up. So I decided to try to flash a custom ROM since it appeared this thing was already FUBAR and that's where the fun began. It WAS running stock 4.4.2. I wiped everything in preparation to flash the stock .tot file. Went to flash a zip from the external sdcard, and it refused telling me it couldn't mount the card! The only hopeful thing is that it powers up, I can get into download/recovery, and it's recognized by the PC through LGFT and ADB.
I can't flash anything, can't push or install through ADB, can't sideload anything. LG flash tools gets to about 38 seconds and then fails. It's like the devices permission were all changed to read only. The device is rooted and has CWM recovery. Is there a way to completely slick this thing (except for recovery - I'd do that too if need be) to reset permissions.
Any/all suggestions gladly accepted.
gjtoth said:
Well, as usual, I've managed to mess things up and here I am again. Somehow, I installed something or other that required rebooting. When I did, I kept getting an error that the systemui was messed up. So I decided to try to flash a custom ROM since it appeared this thing was already FUBAR and that's where the fun began. It WAS running stock 4.4.2. I wiped everything in preparation to flash the stock .tot file. Went to flash a zip from the external sdcard, and it refused telling me it couldn't mount the card! The only hopeful thing is that it powers up, I can get into download/recovery, and it's recognized by the PC through LGFT and ADB.
I can't flash anything, can't push or install through ADB, can't sideload anything. LG flash tools gets to about 38 seconds and then fails. It's like the devices permission were all changed to read only. The device is rooted and has CWM recovery. Is there a way to completely slick this thing (except for recovery - I'd do that too if need be) to reset permissions.
Any/all suggestions gladly accepted.
Click to expand...
Click to collapse
Surprisingly, there was nothing wrong with the phone nor the software nor the PC. After screwing around with this for a couple of days, I had a thought to try a different USB cable. So, I popped it on and, lo & behold, I'm able to flash to stock! Lesson learned: Don't use cheap cables and try changing cables when you're have weird problems like this. :good:
Hello
I tried rooting my LG H815 and it didn't go so well.
I managed to successfully unlock the bootloader following the steps on the LG developer website.
I downloaded SuperSu (UPDATE-SuperSU-v2.46.zip) and placed it in the internal storage of the phone.
Afterwards in order to root the device, I booted into TWRP with "fastboot boot twrp-3.0.2-1-h815.img".
In TWRP I flashed SuperSu. After it finished flashing I rebooted the device. After it attempted to start up again, it froze at the LG logo. I waited around 10 minutes and figured it's not successfully boot.
I removed the battery and tried to fire it up again, but it didn't get past the Logo screen again.
I managed to send "adb reboot recovery" to it, but all I get is an image of a little dead android. I guess this is because I only booted TWRP and did not flash it.
When I get it in fastboot mode, "fastboot boot twrp-3.0.2-1-h815.img" does work anymore now. I just says < waiting for any device >.
I managed to get into default recovery with power up + vol down where it prompted me to do a reset by responding Yes twice, but after it rebooted, it still got stuck on Lg logo.
If you cannot get to the recovery then follow these steps:
i) Make sure you have the LG Drivers installed from here: http://oceanhost.eu/e4h2px4e0hkd/LGMobileDriver_WHQL_Ver_4.0.4.exe.htm
ii) Download the LG Bridge software from here: http://www.lg.com/us/support/product-help/CT10000025-1438110404543-preinstall-apps
iii) Remove the battery and reinsert it so the device it is fully off.
iv) While holding the up volume button, insert your USB cable.
v) You should enter download mode. Go to the Software Update tab of the LG Bridge. It will say connecting and then should say your device is up to date. Click on the recovery text on the bottom right and then follow the instructions. The software will download the system image for you and this is roughly 1.6GB so make sure your firewall doesn't block this connection.
This shouldn't delete your data (no guarantees) but you will have to grant app permissions again and reapply any changes to system files e.g. root, viper4android, xposed ect.
If you have problems try this method instead:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
If successful and you're brave enough to try again. Then make sure you actually flash TWRP. I think you are right in that you only booted TWRP .
You can follow my TWRP/root guide here: https://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003
Good luck
Thanks a lot for answering.
LG Bridge wasn't detecting my device. I don't remember if I was in download mode when I tried this, though. I might've not been.
I didn't know how to fix it and asked a friend for help. He managed to flash the h815 stock firmware through some Taiwanese/Korean flash tool (Edit: It was LGUP and he flash a kdz file with the stock firmware).
I followed a similar guide to yours when I flashed SuperSU from TWRP, except I didn't install twrp permanently after booting it from the .img file. I thought it was not possible to install twrp if the device is not rooted first.
I still kinda want to root the device since I voided my warranty by unlocking the bootloader, but I'm afraid I'll break it again if I use the same method.
Edit: Managed to successfully flash twrp. Booted into recovery again after rebooting system. I am now creating and saving a full backup with TWRP. Will try flashing SU again afterwards.
Edit2: I flashed SU after properly installing TWRP and it worked like a charm.
My Zenfone 2 (ZE551ML 4GB) dilemma:
*•*I unlocked the bootloader with the official bootloader app
*•*I flashed the latest TWRP via adb. In the recovery screen, I saw an android showing error. That's when the panic started.
*•*I Then I rooted my phone with the one click Zenfone root application (available in XDA)
*•*I installed the official TWRP manager from the playstore and flashed with it. That also didn't solve my problem. Actually, a new problem set in. The phone started bootlooping IN RECOVERY.
*•*I rebooted the phone and then flashed an old version of TWRP for my phone. That solved the problem.
*•*Now, I wanted to flash Lineage OS in my phone. According to a YouTube tutorial, I copied my required files (the custom ROM and OpenGAPPS) to my Micro SD and then from twrp's advanced wipe, deleted everything except for Micro SD. I know that was an extremely stupid move but please bear with me.
*•*Deleting everything made things hundred times worse. It seemed impossible to get the phone into recovery mode again. But after a long time, I did.
*•*Now onto flashing the new ROM. I did a factory reset with twrp and then flashed the ROM and immediately got Error 7. By googling a bit, I found that the only way to solve this problem was by deleting the assert lines from the updater-script in meta/com/google/android inside the ROM.
*•* When I reflashed it, the process completed but it showed an error: (E:unknown command [log])
*•* Then I overlooked it again as a quick google said it didn't matter. Then I successfully flashed OpenGAPPS. I rebooted my phone and it kept bootlooping until it was back in the recovery screen. Weird right?
*•*I didn't seem to find any workaround so I decided to restore stock ROM. I downloaded it and flashed it. It succeeded. I rebooted my phone. And. .
*•*My phone now vibrates when I power on the phone and then it shows a black screen. It reboots automatically. I know it does as the phone vibrated periodically after the reboot
*•* I also can't go into the bootloader menu. My phone seems dead but I really need to revive it. I can't afford a new phone. Could you guys help me out please?
LethalHoe said:
My Zenfone 2 (ZE551ML 4GB) dilemma:
*•*I unlocked the bootloader with the official bootloader app
*•*I flashed the latest TWRP via adb. In the recovery screen, I saw an android showing error. That's when the panic started.
*•*I Then I rooted my phone with the one click Zenfone root application (available in XDA)
*•*I installed the official TWRP manager from the playstore and flashed with it. That also didn't solve my problem. Actually, a new problem set in. The phone started bootlooping IN RECOVERY.
*•*I rebooted the phone and then flashed an old version of TWRP for my phone. That solved the problem.
*•*Now, I wanted to flash Lineage OS in my phone. According to a YouTube tutorial, I copied my required files (the custom ROM and OpenGAPPS) to my Micro SD and then from twrp's advanced wipe, deleted everything except for Micro SD. I know that was an extremely stupid move but please bear with me.
*•*Deleting everything made things hundred times worse. It seemed impossible to get the phone into recovery mode again. But after a long time, I did.
*•*Now onto flashing the new ROM. I did a factory reset with twrp and then flashed the ROM and immediately got Error 7. By googling a bit, I found that the only way to solve this problem was by deleting the assert lines from the updater-script in meta/com/google/android inside the ROM.
*•* When I reflashed it, the process completed but it showed an error: (E:unknown command [log])
*•* Then I overlooked it again as a quick google said it didn't matter. Then I successfully flashed OpenGAPPS. I rebooted my phone and it kept bootlooping until it was back in the recovery screen. Weird right?
*•*I didn't seem to find any workaround so I decided to restore stock ROM. I downloaded it and flashed it. It succeeded. I rebooted my phone. And. .
*•*My phone now vibrates when I power on the phone and then it shows a black screen. It reboots automatically. I know it does as the phone vibrated periodically after the reboot
*•* I also can't go into the bootloader menu. My phone seems dead but I really need to revive it. I can't afford a new phone. Could you guys help me out please?
Click to expand...
Click to collapse
Did you flash the MM bootloader compatible TWRP mentioned in the OP for LineageOS? That solves error 7.
Ragarianok said:
Did you flash the MM bootloader compatible TWRP mentioned in the OP for LineageOS? That solves error 7.
Click to expand...
Click to collapse
I did not do that. I remembered all the steps but forgot that. That is the primary cause of my problem. Anyway to solve it?
LethalHoe said:
My Zenfone 2 (ZE551ML 4GB) dilemma:
*•*I unlocked the bootloader with the official bootloader app
*•*I flashed the latest TWRP via adb. In the recovery screen, I saw an android showing error. That's when the panic started.
*•*I Then I rooted my phone with the one click Zenfone root application (available in XDA)
*•*I installed the official TWRP manager from the playstore and flashed with it. That also didn't solve my problem. Actually, a new problem set in. The phone started bootlooping IN RECOVERY.
*•*I rebooted the phone and then flashed an old version of TWRP for my phone. That solved the problem.
*•*Now, I wanted to flash Lineage OS in my phone. According to a YouTube tutorial, I copied my required files (the custom ROM and OpenGAPPS) to my Micro SD and then from twrp's advanced wipe, deleted everything except for Micro SD. I know that was an extremely stupid move but please bear with me.
*•*Deleting everything made things hundred times worse. It seemed impossible to get the phone into recovery mode again. But after a long time, I did.
*•*Now onto flashing the new ROM. I did a factory reset with twrp and then flashed the ROM and immediately got Error 7. By googling a bit, I found that the only way to solve this problem was by deleting the assert lines from the updater-script in meta/com/google/android inside the ROM.
*•* When I reflashed it, the process completed but it showed an error: (E:unknown command [log])
*•* Then I overlooked it again as a quick google said it didn't matter. Then I successfully flashed OpenGAPPS. I rebooted my phone and it kept bootlooping until it was back in the recovery screen. Weird right?
*•*I didn't seem to find any workaround so I decided to restore stock ROM. I downloaded it and flashed it. It succeeded. I rebooted my phone. And. .
*•*My phone now vibrates when I power on the phone and then it shows a black screen. It reboots automatically. I know it does as the phone vibrated periodically after the reboot
*•* I also can't go into the bootloader menu. My phone seems dead but I really need to revive it. I can't afford a new phone. Could you guys help me out please?
Click to expand...
Click to collapse
xfstk is the only way. go to following thread and do as suggested. one advice when you get into bootloader. flash raw without AFT. that is best.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
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