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.
hi iam using lg optimus g pro and trying to flash stock firmware using LG flash tool but i wont flash and prompt low battery but i already charged it whole day..
the cause i wanna flash coz my phone hanged at LG logo boot up due to kernel flash error.. can any1 help me suggest aother tool that can flash
KDZ file into phone...Thank You
Im having exactly the same problem! Tried everything on 2 different computers. They both run Windows 7 x64, maybe that's the problem?
E986 - FreeGee bootloader - CM 10.2 5-11 nightly
I could enter cwm and wipe everything and then i reinstalled cm 10.2 again. Otherwise i would be crying now lol.
But now i still can't go back to stock
I'm also having the same problem, as long as the phone boots into download mode I think there is hope. I have the F240 version and I'm having the same problem as you guys, low battery problem even though the phone is fully charged. Right now I'm trying the "upgrade recovery" thing in the support tool, it is downloading the kdz file again, I hope that during flashing the low battery error won't pop up.
Well I'll post results.
SOLVED!
UPDATE:
Ok guys, I found a solution, I took a huge risk but it worked!
background info:
I have the F240 version, since a lot of apps come on Korean I decided to flash the Panama KDZ file successfully, I had no signal but all I had to no was flash through CWM the original baseband for F240. Since I live in Mexico, I wanted to try the Telcel kdz only to find out I like the Panama kdz better. This were I got into problems, I could not flash my phone anymore due to the "low battery & upgrade unavailable" error. I tried different computers, different files, nothing seem to work. I read that formatting the /data /system /cache partitions would solve the problem... BIG MISTAKE, my phone no longer booted, no recovery, nothing, just download mode. After a few hours a found the solution and so I decided to take the risk.
Solution found here... http://forum.xda-developers.com/showthread.php?p=44372777#post44372777
These were my steps:
- Download Flashtool v1.5.10
- Download DLL file for the F240 (LGUP_GKV)
- Download the TOT File for F240 (this file was impossible to download for me, so I decided to take the risk and downloaded this instead LG Optimus G Pro > ATT Value Pack Firmwar/ BIN_LGE980AT-01-V10k-310-410-JUN-07-2013-0.zip
from the XDA Server found in this thread http://forum.xda-developers.com/showthread.php?t=2438088
- Followed step by step instructions of post 9 here http://forum.xda-developers.com/showthread.php?p=44372777#post44372777
- and here http://forum.gsmhosting.com/vbb/f177/lg-flash-tool-free-no-need-b2b-user-pass-1628819/index2.html
- FINALLY MY F240 BOOTED TO THE ATT ROM.
REMEMBER YOU MUST READ ALL INSTRUCTIONS CAREFULLY, FOLLOW ALL STEPS AND BE WILLING TO TAKE THE RISK!
Hope this helps and it does hit the thanks button!
It's such a shame that the flashing tools for this device suck so horribly. They really are terrible, unstable, difficult to set up. About the worst I've ever used.
I still can't get Flash Tool to run on my device.
The main reason i wanted to go back to stock was because of the annoying delay when i make a call, or receive a call. And sometimes they don't hear me at all... It sucks that a prepaid phone of 15 euro's does the job better then a 500+ phone... In the end... it's a phone right?
I had the problem with stock rom so i flashed to cm 10.2 (i wiped everything before flash) hoping it would be gone but the problem is still there.
Now i found out there is a new .kdz file ( E98610D_00.kdz ) so i wanted to flash that but if i can't get flashtools to work..
* EDIT * i fixed it
What i had to:
Go to flashtools folder
Right-click UpTestEX
Go to compability tab
Select Windows 7
Hit the checkbox for run as administrator
Save
Just to make sure i left the phone on the charger for another hour after it said 100 pct.
Solved
I was experiencing the same problem. Easy way to get it done is
1. Uninstall the current mobile driver from your pc.
2. Download Latest Pc Suite from http://www.lg.com/in/support/pc-suite
3. Install it without inserting the USB.
4. Once installed restart your pc (safe side)
5. Now, remove the battery and insert it again after say 5 seconds and put your phone into download mode.
6. Let the PC and Phone install its drivers and once done open the LG Suite and under 'Mobile Device' tab select 'Restore Upgrade Errors'.
7. It'll download the stock 4.4.2 and you'll be back on track.
Let me know if you are stuck at anything.
Hit the thanks meter if this helped.
Cheers and good luck :good:
So I have an LG G Pro F240l
So essentially, because I flashed the wrong recovery (the F240k, as that's what I thought the phone was), this means I have no recovery.
I cannot root my phone, because basically the recovery doesn't exist.
I can use adb.
I can't do anything after booting other than use ADB, because "LG IMS has stopped working" will constantly appear and impede my ability to achieve anything (this occured after flashing the new lolipop update, which while it technically worked, I should have done a factory reset before doing it.
KDZ files are only the roms, I can flash those fine.
I have a 4.4 rom, and the new lolipop build in terms of those files.
I am unable to locate the tot or dll files I need for my F240l
First, removing LG IMS would make life easier, as that should theoretically fix the problem, making the OS at least useable.
Secondly, how would I go about getting myself a recovery that works (even the stock recover), and flashing it without already having a recovery?
Is there a way I can temporarily root the phone without going into recovery at all?
Please help, I'd rather not have a $160 paperweight..
Edit: I've gotten the ROM working, but I still have no way to root or install a recovery.
arbitrarygrill said:
So I have an LG G Pro F240l
So essentially, because I flashed the wrong recovery (the F240k, as that's what I thought the phone was), this means I have no recovery.
I cannot root my phone, because basically the recovery doesn't exist.
I can use adb.
I can't do anything after booting other than use ADB, because "LG IMS has stopped working" will constantly appear and impede my ability to achieve anything (this occured after flashing the new lolipop update, which while it technically worked, I should have done a factory reset before doing it.
KDZ files are only the roms, I can flash those fine.
I have a 4.4 rom, and the new lolipop build in terms of those files.
I am unable to locate the tot or dll files I need for my F240l
First, removing LG IMS would make life easier, as that should theoretically fix the problem, making the OS at least useable.
Secondly, how would I go about getting myself a recovery that works (even the stock recover), and flashing it without already having a recovery?
Is there a way I can temporarily root the phone without going into recovery at all?
Please help, I'd rather not have a $160 paperweight..
Edit: I've gotten the ROM working, but I still have no way to root or install a recovery.
Click to expand...
Click to collapse
Make sure you have LG Suite installed and of course all the drivers. Put the phone into download mode and engage Repair Upgrade Errors in LG Suite. You should get back to stock.
tanclo said:
Make sure you have LG Suite installed and of course all the drivers. Put the phone into download mode and engage Repair Upgrade Errors in LG Suite. You should get back to stock.
Click to expand...
Click to collapse
I just did this, all it did was re-flashed the same rom I already had (presumeably the .kdz) file. The recovery is still missing and only showing a an android with a compartment open and a red exclamation point.
arbitrarygrill said:
I just did this, all it did was re-flashed the same rom I already had (presumeably the .kdz) file. The recovery is still missing and only showing a an android with a compartment open and a red exclamation point.
Click to expand...
Click to collapse
This is a wild shot in the dark, but try holding vol down, home, power.. then wait for prompt and confirm hard reset with power button. then try the lg suite "repair upgrade" again while in download mode. Hope you can sort it out.
Please don't refer me to any more threads or forums........
I'm sure this has been done and done and talked about but I've been reading the **** out of forums and comments for a few hours now and trying to unroot my Sprint LG G2.
I had it running stock like a champ. rooted it. worked great. then I was attempting to flash lollipop and it required a recovery update (No Problem) I downloaded the correct files and bam! it says your phone is not rooted this requires a root (or something like that) I was already rooted SuperSU installed and root checker said I was fine. so what the hell I swipe to root while inside recovery and it goes to some black screen with tiny text saying fastboot: processing commands and won't leave the screen. I tried booting into recovery and same thing happens. Tried to reboot normal and I'm stuck on the LG logo with my led flashing between blue and green slowly. I CAN boot into download mode and I'm following this
http://pastebin.com/WTm1xFXz
and this
http://forum.xda-developers.com/showthread.php?t=2687929
to unbrick but having this error "Failed PreviousLoad()
Did I not get the right .dll file? I doubt it cause I only saw one...or is it the wrong .tot file? there was 3 or so
http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware
Please help!
When i'm in download mode the phone does say I am rooted. is there a way to just re-flash recovery and restore from my backups I did before all this? if I have to wipe this thing clean and start over I don't really mind I just need to get my phone back haha this is the first time this has ever happened to me and I consider myself tech savvy so idk what I did here (except re rooting in recovery like an idiot) thanks so much!
First question, is the download mode you see with a small status bar or the big one?
If you have the big one, download mode should work. The f flash software will verify the tot file. If that goes through you should be golden.
When it asked you in TWRP to root, that is a message telling you system or ROM file did not take.
If you want cm12, use zv8 tot. Root, auto-rec, update TWRP with blastgator bumped TWRP 2.5.1. Flash cm ROM or aosp, then gapps. And go
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.