[LG-E977]Need help, kinda bricked, can't KDZ - LG Optimus G (International)

Hey guys, i need a little of help because i've never seen what happened to me, i will explain the entire process:
I have an E977 from Movistar Venezuela, it came with 4.2.1, after check everything was working at perfection (wifi, bluetooth, heat, etc.) i decided to root and unlock bootloaders to get into cyanogenmod 10.1 (i had a 4x HD and its very smooth with cm) so i used freegee to unlock bootloaders, installed TWRP and flashed the rom, everything perfect for a month or so, i saw the update of Paranoid Android to 4.3 and wanted to give it a shot so i downloaded it and the gapps, went into recovery, did my backup, wiped and flashed, everything working perfect but i didn't like it so i went into recovery again, did my wipes and perfomed the restore of my backup.
Now, i have a bootloop, the phone normaly showed the LG logo for about a second, turn the screen off, then on again and the OS started to load, but now i just see the logo, the screen turns of but it's not coming back -_-U i've tried to restore again and again and nothing, did wipes and tried to Paranoid Android again with no results, also tried with cm10.1, no results.
I can access the recovery and download modes, followed the guides provided here but i can't KDZ because the original firmware it's more than 1gb and the LG tool can't handle these files.
I read there's a mode to push files via adb when in TWRP, is there a way to "transform" the kdz into some file the TWRP can handle ? do i still have hope ?? I really need help, if you can help me, i will appreciate.
P.D. Also, i would like to know of there's a way to lock the bootloaders again so i can get the phone to warranty! In the worst case...

Did you try the LG Support Tool? It downloads and install the proper KDZ when entering into Emergency Mode.

A way is to restore a backup from another e977.
Another way would be if someone with an e977 would dump his rom to make a flashable zip.
Can't you try lg mobile tool?just put the phone in download mode and see if the tool detects it...
Sent from LG E975 pwd by CM 10.2

Related

Sprint LG LS980 (OptimusG2) stuck in download mode or stock recovery

Hi all. I'm not a novice when it comes to rooting and flashing but I'm stuck on this one. A friend of mine tried to install CM11 on this phone, the LS980 and somehow really jacked it up. It's stuck in a bootloop, but I can get into download mode and stock recovery. All data has been wiped. I have tried using the LGFlash tool to install the stock tot and dll but it fails. It fails because the the tool says the file is the wrong model for the phone. Here's the thing, its not. But somehow the phone now thinks its a D802 instead of an LS980. (This happened during the CM11 attempt somehow) The flash tool fails every time. I even tried the D802 files and it started to flash but failed about a 1/4 of the way through. That confirms that the phone definitely thinks its a D802, weird. When I hook it up to the LG Support tool, it tells me the phone is a testmodel!
Needless to day I've tried everything I know how. ADB sideloads, different recoveries, and I've researched for hours on end. I have hope that there's still a solution. I would be golden if I could get a recovery on it, either TWRP or CWM. Any help is appreciated.
have the same problem. simply cant recover the recovery.
My recovery for e988 g pro in lg g2. I try everything for fix the recovery but cant help it. Is there any way to re build recovery?

[Q] LG Optimus G Soft-Bricked? Please help me to recover my phone

Hey Guys,
First post and i already got a problem because i messed up very much
I used to have Cyanogenmod 11 on my Optimus G, but i got several crashes and i wasnt completely fine with it so i wanted to try something new. So i updated my bootloader from CWM to TWRP and wanted to flash Artmod 5.2 Rom. I was a bit fast with my wiping, so i accidentally wiped the whole phone, so that everything was gone: Cyanogenmod, new Artmod rom i wanted to flash just everything.
I read a bit and thought it shouldnt be a problem then to just sideload the new rom, which i tried to do. I used adb sideload to put Artmod on the phone, everything was fine, flashing went through but i got stuck at the LG boot logo at the start of the phone. I waited like 30 minutes and nothing did change, so i thought something was not right.
I then just wanted to go back to cyanogenmod, tried to flash that through the adb sideload procedure but i got an error which said "error executing updater binary in zip 'tmp/sideload.zip'".
I was kinda thinking something really messed up so i tried to revert the phone to stock rom with the correct KDZ file i searched with the tool linked in the FAQ, everything downloaded but when i tried to flash the KDZ it gave me an error like this:
"12:03:59 Launching SW update
12:03:59 Unpacking KDZ
12:05:10 KDZ file extracted
12:05:11 Extract file error
12:05:13
===FINISH===="
So i searched the forums again and noticed that it should be a problem with the KDZ updater tool because the KDZ file was too big to get flashed properly. I wanted to try the LG Flash Tool 2014 then which is provided here in the forums and should work, it extracted the KDZ file, then opened the LG Mobile Support Tool to flash the file on the phone but there i start to get errors again, it either said that i am already on the correct up to date software version or that i need to disconnect the USB cable, remove the battery, insert it again, restart and try again.
I used several tools for that, i even tried it with an offline method that i found in a german forum, but every method got me the same errors, so i couldn't even go back to stock anymore.
I once tried to flash Cyanogenmod then again when i realized that the error message also told me "This Rom is for a "E975", this is a "GEE"" which i did not completely understand because it should be the total same? I edited the Updater-Script in the Zip file of the rom then and removed the part where it checks for that (1st line actually), then the rom did flash properly, phone started to boot (Cyanogenmod Boot Logo was shown) but when the boot was over i got the message:
"Type Password to Decrypt Storage" with a keyboard to enter the password. (I did never set up any password for that).
Now i am completely confused what i can do the recover my phone, either to stock or just to another rom, every method i tried did not work and i dont have any other ideas.
I can go into Fastboot, Recovery and Downloadmode, but when i tried to wipe again in Recovery it says that it cant mount my data mount point (probably because the storage is encrypted).
Somebody told me to do a hard reset with the keys "Volume down and power" which i tired several times, but everything i get is just the Google boot logo and then happens nothing or i get the Google logo, then the LG logo but after that i get stuck again, I cant seem to go into the "Hard Reset" menu which i should get into with that keys.
Anybody can help me what I could try or got a solution for this? I would be very thankful. I don't wanna loose my phone
Astarooth said:
First post and i already got a problem because i messed up very much
Click to expand...
Click to collapse
Don't worry, that's pretty standard scenario for the first post...
I wanted to try the LG Flash Tool 2014 then which is provided here in the forums and should work, it extracted the KDZ file, then opened the LG Mobile Support Tool to flash the file on the phone but there i start to get errors again, it either said that i am already on the correct up to date software version or that i need to disconnect the USB cable, remove the battery, insert it again, restart and try again.
Click to expand...
Click to collapse
Flash Tool 2014 works great for me every time, so try it again. Make sure you disconnect from the Internet before running it (yank out your LAN cable, or disable your WiFi), so it doesn't attempt to connect to LG servers. And don't forget to put your KDZ file in the same directory with the tool. It should go through just fine. That's by far the easiest method to revert back to stock, to get you to a clean starting point.
"This Rom is for a "E975", this is a "GEE"" which i did not completely understand because it should be the total same?
Click to expand...
Click to collapse
Umm... No, they are not the same. E975 is "geehrc", and there is no such OEM ID as "gee". There are many different OG variants. For the cross-reference between the models and OEM IDs, you can look here. Generally, you should stick to the ROMs that are designed for your model, unless you know exactly what you are doing, when trying to flash a ROM from a different platform.
kt-Froggy said:
Don't worry, that's pretty standard scenario for the first post...
Flash Tool 2014 works great for me every time, so try it again. Make sure you disconnect from the Internet before running it (yank out your LAN cable, or disable your WiFi), so it doesn't attempt to connect to LG servers. And don't forget to put your KDZ file in the same directory with the tool. It should go through just fine. That's by far the easiest method to revert back to stock, to get you to a clean starting point.
Umm... No, they are not the same. E975 is "geehrc", and there is no such OEM ID as "gee". There are many different OG variants. For the cross-reference between the models and OEM IDs, you can look here. Generally, you should stick to the ROMs that are designed for your model, unless you know exactly what you are doing, when trying to flash a ROM from a different platform.
Click to expand...
Click to collapse
Well i tried Flash Tool 2014 again and seem to get the same error that wants me to disconnects as it stops at the same position like it always did, also doesn't matter if I am connected to the internet or not, everytime it doesn't run through. This time I couldn't even read the stuff that was written in the LG Mobile Support tool because it only shows "????".
Heres a Screenshot:
The settings i made should be the right ones I think, the phone does get recognized by the computer when i plug it in because of the sound that windows makes.
I clearly dont't know what I can try anymore...
And according to the roms: well i only used roms for the E975, which is exactly my phone model, thats why i was wondering about that error message i got
Artmod is for E975, the CM11 was for E975, i even tried Mokee rom but i always got same error messages...
Nobody got another idea? I really am confused because if i can enter downloadmode and recovery there should be a way to get my phone back working.
Anybody knows where i can get maybe some older KDZ Files to go to 4.1.2 Stock rom and try to flash these?
problem
Astarooth said:
Nobody got another idea? I really am confused because if i can enter downloadmode and recovery there should be a way to get my phone back working.
Anybody knows where i can get maybe some older KDZ Files to go to 4.1.2 Stock rom and try to flash these?
Click to expand...
Click to collapse
Contact me on [email protected] and ill help u over teamwiewer.
Astarooth said:
Well i tried Flash Tool 2014 again and seem to get the same error that wants me to disconnects as it stops at the same position like it always did, also doesn't matter if I am connected to the internet or not, everytime it doesn't run through. This time I couldn't even read the stuff that was written in the LG Mobile Support tool because it only shows "????".
Heres a Screenshot:
The settings i made should be the right ones I think, the phone does get recognized by the computer when i plug it in because of the sound that windows makes.
I clearly dont't know what I can try anymore...
Click to expand...
Click to collapse
I don't know why you are seeing "???", but here is a couple of things regarding the settings, based on your screenshot:
1. Type should be CDMA (yours is 3GQCT).
2. PhoneMode should be DIAG (yours is CS_EMERGENCY).
3. I would suggest using CSE Flash for a full format (you are using Normal Flash).
Remember, this is a hacked tool, so the settings might not make perfect sense, comparing to the original ones. Just try following the instructions in the OP of the Flash Tool 2014 thread. Like I said, works every time for me...
kt-Froggy said:
I don't know why you are seeing "???", but here is a couple of things regarding the settings, based on your screenshot:
1. Type should be CDMA (yours is 3GQCT).
2. PhoneMode should be DIAG (yours is CS_EMERGENCY).
3. I would suggest using CSE Flash for a full format (you are using Normal Flash).
Remember, this is a hacked tool, so the settings might not make perfect sense, comparing to the original ones. Just try following the instructions in the OP of the Flash Tool 2014 thread. Like I said, works every time for me...
Click to expand...
Click to collapse
I don't know why i see "???" also, but it didn't matter
I just tried the settings you told and used CSE Flash which worked out really well.
No i am back to 4.4.2 LG Stock rom. I think the root is gone now, but one thing i wanna ask is if my bootloader is still unlocked and custom recovery is still on it?
Anyway, thank you so so much! I appreciate your help! Thank you!
Astarooth said:
I don't know why i see "???" also, but it didn't matter
I just tried the settings you told and used CSE Flash which worked out really well.
No i am back to 4.4.2 LG Stock rom. I think the root is gone now, but one thing i wanna ask is if my bootloader is still unlocked and custom recovery is still on it?
Click to expand...
Click to collapse
Glad to hear you are back in business. After flashing KDZ, the root is definitely gone, your BL is locked, and the recovery is stock. You will need to do all the necessary steps again: root, unlock the BL and flash custom recovery.

[Q] Stuck in download mode

Hey all,
I recently put the lolipop AOSP rom onto my G Pad, but wanted to revert it back to the stock software.
I plugged it into the computer and tried using the recovery tool, but it did not work, so I put the G Pad into download mode and it gets to a point where it has downloaded the software and is deploying it, but then fails every time.
I tried the offline KDZ method, but when the support tool loads it checks the connected device and always tells me to unplug it and try again.
Does anyone have anything in mind I could try or requires more information to offer a suggestion to me?
Thank you in advance.
I was in the same position a few hours ago. I downloaded the official LG Support tool (drivers and tool available HERE). Launch the LG Support tool, go to Options -> Upgrade Recovery and follow the steps. It should dowload the latest available official formware (V50020D) and flash it to your tablet. I'd recommend a factory reset, since you have CM installed on it. This procedure didn't erase /data (I've done it twice while trying to flash a custom recovery on it). Then you must use LG Flash Tool 2014.zip to flash an older firmware that has a bootloader that allows installing of a custom recovery. After flashing V20B or V20A, you must root it and flash a custom recovery (I'd recommend THIS ONE). It seems a little complicated, but this is the only way to un-brick it (it worked for me).
Get the apk from THIS thread after rooting your tablet (it should flash TWRP 2.8).

[Q] LG G Pro F240L, no recovery at all, and no root to flash one with

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.

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.

Categories

Resources