Hi all,
Let me try to walk you through everything that I've done to try and get some help here.
I have an lg g2 sprint (lg-ls980)
1. When I got it I first upgraded to android 4.4.2
2. Then I rooted using stump root
3. I installed xposed and a few xposed modules....I then decided Id rather have a different rom, so
4. I used autorec (which to my understanding changed my kernel in order to workaround boot loader and install twrp? is that accurate?)
5. Booted to twrp, wiped data and installed cyanogenmod and gapps
After this I get stuck and can't boot past the lg logo, so I booted back to recovery and restored my backup. So I did the same and tried pacrom this time with the same results.
I then decided that if I'm going to be stuck with stock rom I at least want my knock on back, so I flashed the patched kernel and same thing- stuck at lg logo....
I know I downloaded the correct zip files and placed them on the root, and always wiped before flashing.
Then I went into download mode on the lg support tool to try to get back to factory, but it says my firmware and recovery is up to date. The odd thing is that the lg support tool shows my phone as ls740 rather than ls980... is this because of something that autorec changed? Do I need to download zip files for ls740 instead? So confused..
About phone in my g2s settings shows android version 4.4.2 and kernel version 3.4.0
Anyways, if anyone could help me to successfully get one of these roms to flash and get back to the kernel that supports the knock code I would really appreciate it.
Thanks in advance!
Hi guys,
I attempted to restore my G2 (D802 international 32GB) back to the stock kitkat firmware from Cyanogen Mod 12. While attempting the restore, the lg support tool gave me an error saying it had failed, however when I disconnected the device it was apparently still doing something.
I now am at a stage where I get no recovery, download, or fastboot mode, etc, however my device is connecting to my PC as qhsusb_bulk in device manager. I followed this thread: http://forum.xda-developers.com/showthread.php?t=2582142 in order to help remedy the issue, however it didn't work. I'm guessing it could have something to do with the fact that I had CM12 rather than the stock firmware of which I extracted the necessary files for my device (I extracted the files from an IMEI number provided KDZ) in place of the files provided on the thread.
Could someone help point me in the right direction? Do I need the image files from CM12, or the stock images despite the device running CM12 before hand? am I following the right process?
Thank you very much in advance for any help anyone can provide, I really appreciate it!
PS. Sorry if this has been covered before, I just haven't been able to find anything else.
Were you able to find out what the problem was? I am on CM12 myself on my G2 D802. Got some problems with TWRP. It wouldnt restore backups, and had problems with flashing ROMs ang gapps so I flashed CWM with flashify and now when I try to reboot to recovery I just get the LG logo and boot verification issue... Would really appreciate if you could share your solution if you were able to find one
I tried updating the bootstack on my LG G2 since it was having WiFi disconnect issues. After updating it with the Lollipop bootstack on a Lollipop ROM (Dirty Unicorns 5.1.1) I couldn't use the camera and flash light.
I then decided to just flash the stock LG G2 Lollipop KDZ and start afresh.
However, my phone became bricked into fastboot mode but I got out of it by flashing all the img files through fastboot. Now it is getting stuck at the LG logo and I can't enter fastboot or recovery now... I can access download mode but it says it's still rooted and when I go to flash a new KDZ (tried multiple versions) it says phone disconnected, or force closes the support tool.
I've been in this situation before but I can't remember how I got out of it...
I'm running Windows 8.1 and have read that you can't flash KDZ through the support tool on Windows 8/8.1 so I'm in the process of installing a Windows 7 virtual machine.
reeper250 said:
I tried updating the bootstack on my LG G2 since it was having WiFi disconnect issues. After updating it with the Lollipop bootstack on a Lollipop ROM (Dirty Unicorns 5.1.1) I couldn't use the camera and flash light.
I then decided to just flash the stock LG G2 Lollipop KDZ and start afresh.
However, my phone became bricked into fastboot mode but I got out of it by flashing all the img files through fastboot. Now it is getting stuck at the LG logo and I can't enter fastboot or recovery now... I can access download mode but it says it's still rooted and when I go to flash a new KDZ (tried multiple versions) it says phone disconnected, or force closes the support tool.
I've been in this situation before but I can't remember how I got out of it...
I'm running Windows 8.1 and have read that you can't flash KDZ through the support tool on Windows 8/8.1 so I'm in the process of installing a Windows 7 virtual machine.
Click to expand...
Click to collapse
Oh my god.. What happend to you g2 ?
First, don't give up, sooner or later you are gonna unbrick your G2 in the end. I have been there too.
If you can get into download mode, you are very lucky.
Just Ignore root thing, it has nothing to do with flashing KDZ/TOT.
You got to learn how to use LG flashtool first.
http://forum.xda-developers.com/showthread.php?t=2432476
My suggestion is that just stick to TOT tool instead of KDZ tool. Sometimes KDZ tool fails during flashing without proper reason.
And that problem often happens when you are going back to stock rom from CM12.1 roms like DU, BlissPop...
But one thing to remember, TOT tool would wipe out your internal memory.
Unplugging you external SD memory is recommended while doing KDZ/TOT flashing.
If you still fail with TOT tool.... It's no good. You may have to try short-circuit method.
Good luck.
ailing said:
Oh my god.. What happend to you g2 ?
First, don't give up, sooner or later you are gonna unbrick your G2 in the end. I have been there too.
If you can get into download mode, you are very lucky.
Just Ignore root thing, it has nothing to do with flashing KDZ/TOT.
You got to learn how to use LG flashtool first.
http://forum.xda-developers.com/showthread.php?t=2432476
My suggestion is that just stick to TOT tool instead of KDZ tool. Sometimes KDZ tool fails during flashing without proper reason.
And that problem often happens when you are going back to stock rom from CM12.1 roms like DU, BlissPop...
But one thing to remember, TOT tool would wipe out your internal memory.
Unplugging you external SD memory is recommended while doing KDZ/TOT flashing.
If you still fail with TOT tool.... It's no good. You may have to try short-circuit method.
Good luck.
Click to expand...
Click to collapse
Failed everything except TOT. The TOT took about 6-8 hours to download...
Flashed TOT and it booted fine, then updated to stock Lollipop with KDZ. It's currently working EXCEPT....
Camera doesn't work still, can't send a text because the "Messaging" app force closes, don't have the flash light, and I can't seem to start ABD to root it.
SD Card is working fine though. Using a 64GB formatted to FAT32 and restored all my pictures, music, etc.
The main thing is the camera and messaging app, plus the flash light is really handy when working on my car.
At least I have a working phone
Managed to get it recognised in device manager and ADB but when rooting it stops at 45%...
reeper250 said:
Managed to get it recognised in device manager and ADB but when rooting it stops at 45%...
Click to expand...
Click to collapse
Oh... I think there's possibility your camera hardware has gone out of order.
When you are in LG stock rom, and still experience problem... well I guess it's not software problem.
Because TOT flashing is complete software factory reset. It revert everything to out of factory state.
And for rooting, sometimes it just get stuck. but suddenly it just get rooted. I can't explain the reason.
But you should remember one thing in mind, don't initialize V3. It's anti virus program, and it blocks rooting.
When you boot for the first time, you maybe was asked if you agree with V3 software, just choose don't agree and skip it.
If you still fail rooting, just flash KDZ/TOT again to go back to KitKat. When you're done with flashing KDZ/TOT, just stay there and don't update KK version because KK update could block rooting.
Of course you should not agree with V3 software install.
Use towel root, it's the most easiest way. go to towelroot.com and download apk. (click logo)
Root your G2 and use KitKat version of autorec to install TWRP.
ailing said:
Oh... I think there's possibility your camera hardware has gone out of order.
When you are in LG stock rom, and still experience problem... well I guess it's not software problem.
Because TOT flashing is complete software factory reset. It revert everything to out of factory state.
And for rooting, sometimes it just get stuck. but suddenly it just get rooted. I can't explain the reason.
But you should remember one thing in mind, don't initialize V3. It's anti virus program, and it blocks rooting.
When you boot for the first time, you maybe was asked if you agree with V3 software, just choose don't agree and skip it.
If you still fail rooting, just flash KDZ/TOT again to go back to KitKat. When you're done with flashing KDZ/TOT, just stay there and don't update KK version because KK update could block rooting.
Of course you should not agree with V3 software install.
Use towel root, it's the most easiest way. go to towelroot.com and download apk. (click logo)
Root your G2 and use KitKat version of autorec to install TWRP.
Click to expand...
Click to collapse
Got root eventually. Not sure why but it worked after like the 6th time...
Is it the bootstack or something that's causing the camera and flash to stop working?
It only started having those issues when I installed the new bootstack.
I'm about to throw this stupid phone against the wall...
I cleared Cache and Dalvik Cache after successfully installing TWRP and it came up with "Security Error" and I can't boot
reeper250 said:
I'm about to throw this stupid phone against the wall...
I cleared Cache and Dalvik Cache after successfully installing TWRP and it came up with "Security Error" and I can't boot
Click to expand...
Click to collapse
I can guarantee TOT flashing would revert everything to factory default state. So Even if bootstack has caused problem, after flashing TOT, everything should be back to normal. Because TOT flashing includes bootstack.
Tot flashing completely wipe out your G2 and rewrite EVERYTHING.
I am 100 percent sure that camera's malfunction has nothing to do with bootstack.
BTW, which version of autorec did you use ? There are two versions of autorec. You should not be mistaken.
Because KitKat autorec would destroy Lollipop's kernel and cause security error.
To my knowledge, XDA forum has only KK version which made by cloudyfa.
Even if you had security error, It's too early to give up.
First, Power off, and holding vol.up and connect USB. If you are lucky again, you would see download mode.
Or try to get into recovery by pressing vol.up and power.
At worst case, you can't get into recovery nor download mode, either.
But That doesn't mean you should throw out g2. You can still revive G2.
Recently I made how to revive bricked G2 (only F320 specific) in Korean. It's already known method.
You have to open back cover and disassemble to try short-circuit.
If you really want to try short-circuit method, I would make short translated version for you.
G2 is really hard to brick. So don't throw up until G2 is real dead.
Good luck
ailing said:
I can guarantee TOT flashing would revert everything to factory default state. So Even if bootstack has caused problem, after flashing TOT, everything should be back to normal. Because TOT flashing includes bootstack.
Tot flashing completely wipe out your G2 and rewrite EVERYTHING.
I am 100 percent sure that camera's malfunction has nothing to do with bootstack.
BTW, which version of autorec did you use ? There are two versions of autorec. You should not be mistaken.
Because KitKat autorec would destroy Lollipop's kernel and cause security error.
To my knowledge, XDA forum has only KK version which made by cloudyfa.
Even if you had security error, It's too early to give up.
First, Power off, and holding vol.up and connect USB. If you are lucky again, you would see download mode.
Or try to get into recovery by pressing vol.up and power.
At worst case, you can't get into recovery nor download mode, either.
But That doesn't mean you should throw out g2. You can still revive G2.
Recently I made how to revive bricked G2 (only F320 specific) in Korean. It's already known method.
You have to open back cover and disassemble to try short-circuit.
If you really want to try short-circuit method, I would make short translated version for you.
G2 is really hard to brick. So don't throw up until G2 is real dead.
Good luck
Click to expand...
Click to collapse
I probably installed the wrong AutoRec then...
Flashed the KDZ again and booted but it's saying "System UI has stopped", com.android.phone has stopped", etc.
I guess I have to TOT flash again and start over... again...
reeper250 said:
I probably installed the wrong AutoRec then...
Flashed the KDZ again and booted but it's saying "System UI has stopped", com.android.phone has stopped", etc.
I guess I have to TOT flash again and start over... again...
Click to expand...
Click to collapse
In normal case, after flashing TOT, there should not be any problem at all. Because It's in factory default condition. I mean, it's like the first time you open up the package right after you buy.
As for your case, I think something is seriously wrong.
Make sure you flashed right TOT matched to your F320. As you already know, there are 3 variants, F320S, F320K, F320L.
Ah.. I almost forgot. If you want to try aosp roms other than LG stock rom, you can try when you are in KitKat, too. While you are in KK, don't update KK version. Because updated KK version blocks rooting.
Right after flashing KK tot/kdz, try towel root. It's the easiest rooting tool.
You can download it at towelroot.com
After rooting, install supersu and use KK autorec (which made by cloudyfa) to install TWRP.
But In my opinion you should figure out why stock rom has system UI crash.
In authorized LG service center, engineer uses the same TOT tool. In theory you can't have any problem after flashing TOT. unless there are some damaged hardware.
This is all I can help. Hope you solve the problem.
ailing said:
In normal case, after flashing TOT, there should not be any problem at all. Because It's in factory default condition. I mean, it's like the first time you open up the package right after you buy.
As for your case, I think something is seriously wrong.
Make sure you flashed right TOT matched to your F320. As you already know, there are 3 variants, F320S, F320K, F320L.
Ah.. I almost forgot. If you want to try aosp roms other than LG stock rom, you can try when you are in KitKat, too. While you are in KK, don't update KK version. Because updated KK version blocks rooting.
Right after flashing KK tot/kdz, try towel root. It's the easiest rooting tool.
You can download it at towelroot.com
After rooting, install supersu and use KK autorec (which made by cloudyfa) to install TWRP.
But In my opinion you should figure out why stock rom has system UI crash.
In authorized LG service center, engineer uses the same TOT tool. In theory you can't have any problem after flashing TOT. unless there are some damaged hardware.
This is all I can help. Hope you solve the problem.
Click to expand...
Click to collapse
TOT is for my F320S, just flashed it again and it worked.
Installed AutoRec LP and it worked. Ended up installing Dirty Unicorns 5.1.1 which worked.
Camera and flash still don't work.
I remember this happened to me ages ago but I can't remember how I fixed it
ailing said:
In normal case, after flashing TOT, there should not be any problem at all. Because It's in factory default condition. I mean, it's like the first time you open up the package right after you buy.
As for your case, I think something is seriously wrong.
Make sure you flashed right TOT matched to your F320. As you already know, there are 3 variants, F320S, F320K, F320L.
Ah.. I almost forgot. If you want to try aosp roms other than LG stock rom, you can try when you are in KitKat, too. While you are in KK, don't update KK version. Because updated KK version blocks rooting.
Right after flashing KK tot/kdz, try towel root. It's the easiest rooting tool.
You can download it at towelroot.com
After rooting, install supersu and use KK autorec (which made by cloudyfa) to install TWRP.
But In my opinion you should figure out why stock rom has system UI crash.
In authorized LG service center, engineer uses the same TOT tool. In theory you can't have any problem after flashing TOT. unless there are some damaged hardware.
This is all I can help. Hope you solve the problem.
Click to expand...
Click to collapse
Hello it is easy to provide me links to f320s .tot and .dll ?
LG g2 d802 not accepting fastboot commands
reeper250 said:
I tried updating the bootstack on my LG G2 since it was having WiFi disconnect issues. After updating it with the Lollipop bootstack on a Lollipop ROM (Dirty Unicorns 5.1.1) I couldn't use the camera and flash light.
I then decided to just flash the stock LG G2 Lollipop KDZ and start afresh.
However, my phone became bricked into fastboot mode but I got out of it by flashing all the img files through fastboot. Now it is getting stuck at the LG logo and I can't enter fastboot or recovery now... I can access download mode but it says it's still rooted and when I go to flash a new KDZ (tried multiple versions) it says phone disconnected, or force closes the support tool.
I've been in this situation before but I can't remember how I got out of it...
I'm running Windows 8.1 and have read that you can't flash KDZ through the support tool on Windows 8/8.1 so I'm in the process of installing a Windows 7 virtual machine.
Click to expand...
Click to collapse
if anyone can help me. I dont know if it'is a hard brick or not, but i can go to the fastboot mode only. when i try to erase some partitions tho i get this error FAILED (remote: failed to erase partition) and my phone says Failure sending erase group start command to the card(RD;2).
I've tried to flash files too but nothing seems to work since everything leads me to an error and the phone says this when i try to flash it :Failure sending write group start command to the card(RD;2).
if anyone is able to help me, i would very much appriciate
So I just recently wiped all the data on my phone in a rush except TWRP and I want to revert back to stock ROM. But LGUP doesn't recognize my phone when I do use TWRP or fastboot mode. From my research done I need to get stock firmware update back in order to get LG UP to work again? I'm not entirely sure what I'm doing since I'm new to this. Help im noob. no backups too.
I tried this thread:
https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903
But... LGUP doesn't see my device as said and KDZ files don't flash on TWRP. I tried doing some random .ZIP files of stock roms which I'm not entirely sure I did correctly.
You dont use TWRP or fastboot with LGUP you use Download mode
me2151 said:
You dont use TWRP or fastboot with LGUP you use Download mode
Click to expand...
Click to collapse
Yes I know that. But TWRP replaced my download mode because whenever I plug in my device and press the UP volume key TWRP showed up instead.
Anyway I fixed it myself so thread close pls. Not sure how to do this.
Whenever you fix your own problems, it's still considered good forum etiquette (to many people including myself) to still offer the solution you came up with so that anyone else reading the thread because they might be having the same issue that you're having would love to get a working solution too.
Anyway, the issue is that the lafsploit method using the USB Linux distro overwrites the laf partition to get TWRP installed on the device. Most people never bother to fix that problem but the solution is to flash the laf_restore.zip file (I got it from another thread but can't find that thread at this moment so I'm just going to host the file on Drive for safekeeping):
https://drive.google.com/open?id=1WkR-6--OpOaRw-W5Wt9BzljIBVvG_kMF
MD5: 976bf936548c6fab4fe04dec43f53fb4
SHA-1: 1c6d509f4f29b65d7e0d3d406e6978caeb43d6a9
After you flash TWRP temporarily on the H918, then update TWRP (flashing the newest version), reboot back into recovery/TWRP and then flash the laf_restore.zip which will restore the laf partition(s) to their proper state - AFTER all this then you should be able to get to Download Mode again normally if you must.
Oh yeah I was sorta thinking about posting my solution last night. Anyway the solution I found was to find a .ZIP file of an older stock ROM like the H91810u using what I used which was TWRP since I didn't know what else to flash it with.
I found the file on this thread IIRC. A lot of the links are dead but the 10u version wasn't for me.
https://forum.xda-developers.com/v20/development/rom-h91810q-stock-rom-twrp-flashable-zip-t3681312
My main concern was to just get stock ROM back. I only wanted stock recovery because that was the only way I knew to flash .KDZ files using LGUP. Although I guess bootloader is still unlocked on my phone. But stock download mode still comes back.
I didn't do anything after that but it seems good enough for me now since I don't turn turn off and on my phone a lot. Till another day.