Database Users

[Q] Impossible to flash recovery img.

Hey guys, i've owned a G2 by Amazon.fr, a f320K version, Korean version from Hong-Kong, with V10E.
Then i updated stock rom many times until V20F , OTAs by the phone.
Second step. I easily rooted my phone by the Ioroot19 method. Sucess. Root_Checker is ok for my root.
Third step. Installing TWRP with loki patch.
But, i can't flash none of all the img files i tried (f320K.img, d802.img, d802K.img). Loki patch does not match my phone. Impossibe for me to enter in recovery mode because installation failed. If i want enter in recovery mode my phone said security booting error.
So, please, what i missed ? Or is because i'm on v20F ?
I joined a picture of my adb error.

[Q] Installed F320S rom on D802, now I can't get back to D802 rom.

TL;DR: My D802 thinks it's an F320S so I can neither flash D802 kdz/tot nor get SU in adb shell.
Long story:
I tried to install Cloudyg2 version 3 without noticing, that it was for the korean model F320S.
I managed to wipe everything, ended in fastboot mode, loaded aboot etc. and was able to get to download mode.
The problem is, the phone identifies as F320S, so I haven't been able to use LG Flashtool to install a D802 tot or kdz-file.
LG Flash Tool 2014 and lgflash with "Automatic Offline Procedure-vbs" both stop at 2%.
So does the straight up LG Mobile Support upgrade recovery.
LG Flash 1.8 (for .tot files) gives the following error message:
BIN: BIN_LGD802AT-00-V10b-SEA-XX-SEP-04 (the rest is outside the window)
SWW: LGF320SAT-00-V21r-SKT-KR-APR-09- (the rest is outside the window)
SWOV: LGF320SAT-00-V21r-SKT-KR-APR-09- (the rest is outside the window)
Device Model is different!
Check Phone or DLL
I have tried with several versions of the LGUP8974.dll with LG Flash 1.8 without even getting that far. I can only get this far with LGD802_20130912_LGFLASHv160.dll.
So I've tried flashing F320S kdz-files, which I can. I've tried the following:
KoreanSKT F320S F320S11G_00.kdz (which is Jellybean)
Korea SKT KitKat F320S21R_00.kdz (which is Kitkat) and
F320S28D_00.kdz (which is Lollypop)
All of them sticks me in a boot-loop.
All three gives me access to download-mode, but I kan only change between F320S roms.
The Kitkat version gives me access to an ADB-mode by turning the phone off, then holding power and vol+ for about ten seconds. It gives me ADB-access, but the screen is black with the backlight on. In that mode, I've tried Ioroot, Vroot and Kingo root. Ioroot and Vroot doesn't work, but Kingo does to a degree.
I can also reboot into recovery and sideload either kk_root.zip or datroot.zip.
All three options make the phone show up as rooted in download-mode. The problem is, it doesn't give me superuser (su) when I use adb shell.
I've tried sideloading both Chainfire and Koush superuser-zip-files, but both fails with these error messages:
Chainfire's supersu:
E:Error in /tmp/upload.zip
(Status 255)
Installation aborted.
Koush superuser:
E:footer is wrong
E:signature verification failed
Installation aborted
As far as I can tell, there's three or four options:
Get su and install custom recovery
Get su and edit build.prop to D802 so I can flash a D802 kdz- or tot-file
Or find some flash-tool or .dll that lets me flash a D802 dkz- or tot-file
Maybe finding a way back to fastboot and using Linux to flash the right files to the right partitions.
Any help is appreciated! I've spent most of the week googling...

Bricked D801 - TOT & KDZ recoveries both failing?

I've got a T-Mobile D801 and tried flashing to the stock lollipop rom D80130b_00 using TWRP and the instructions on this page, but the flash must have failed. I did a full factory reset back to stock 4.4.3 prior to attempting this flash and I'm not sure what (if anything) I did wrong for the flash to fail. I can boot in factory reset mode and select clear everything, but then I just see the android guy with gears turning for 2 seconds and the phone reboots again.
Now I'm in a bootloop where I get an "error: Boot certification verify" above the T-Mobile startup logo followed by a "Demigod Crash Handler: Critical Error!" screen that provides options for rebooting (volume down) or putting the phone into download mode (volume up). After using the volume up the screen displays "Volume Up is pressed: Jump to Dload mode" and after connecting via USB appears in device manager as "LGE AndroidNet USB Serial Port (COM41)". I can't (1) boot directly into download mode or (2) get back into TWRP.
I've tried both the KDZ and TOT methods listed in this thread and neither are working. The LG Flash Tool 2014 / KDZ option starts the LG Mobile Support Tool, but it fails every time once "S/W Upgrade is in progress" reaches 4% with a generic "Upgrade stopped due to an error" message.
The TOT method fails every time with a "Model Information Check FAIL!" message. The full text is - "PID: NULL, IMEI: NULL, Model: , DLL:801, BIN: BIN_LGD801AT-01-V10c-310-260-AUG-13-2013+0.tot , SWV: , SWOV: , Model Information Check FAIL! , 00000000"
I've also tried using srktool to repair fastboot, but it gets stuck at "waiting for device".
What do I try next?

Finally got back into 4.2.2 using tot method. LG Mobile Support Tool doesn't think updates are available though??

same situation lg g2 d802
losonn said:
Finally got back into 4.2.2 using tot method. LG Mobile Support Tool doesn't think updates are available though??
Click to expand...
Click to collapse
i am in same situation with lg g2 d802 model ..have you fixed your g2?

hunzz said:
i am in same situation with lg g2 d802 model ..have you fixed your g2?
Click to expand...
Click to collapse
Yes, I *think* what happened was that my 30b bootstack was flashed successfully via twrp, but then the actual kdz flash of D80130b_00 failed. I had a lot of trouble at this point - needed to fix qhsusb_bulk problems first, then use the more aggressive TOT flash method to reset to stock 4.2.2.
Finally the LG Mobile Tool was still reading it as having D80130b_00 / lollipop after going back to 4.2.2 via TOT (?). Last step was to do a full restore from the LG Mobile Support Tool (options -> upgrade recovery) and it actually downloaded / flashed D80130b_00 so everything is working well now :good:
If it helps anyone I used the LG backup tool to restore apps / media and have to say that for a stock solution it's pretty solid.

qhsusb_bulk?
losonn said:
Yes, I *think* what happened was that my 30b bootstack was flashed successfully via twrp, but then the actual kdz flash of D80130b_00 failed. I had a lot of trouble at this point - needed to fix qhsusb_bulk problems first, then use the more aggressive TOT flash method to reset to stock 4.2.2.
Finally the LG Mobile Tool was still reading it as having D80130b_00 / lollipop after going back to 4.2.2 via TOT (?). Last step was to do a full restore from the LG Mobile Support Tool (options -> upgrade recovery) and it actually downloaded / flashed D80130b_00 so everything is working well now :good:
If it helps anyone I used the LG backup tool to restore apps / media and have to say that for a stock solution it's pretty solid.
Click to expand...
Click to collapse
you said your g2 was detected as a lge androidnet in device manager but not as a qhsusb_bulk...then what problems have you fixed about qhususb_bulk? and what is the more aggressive tot method different from this threadhttp://forum.xda-developers.com/showthread.php?t=2432476

Were you able to find a solution? I'm in the same situation. Please help!

Problem with Boot (D802)

I was using my phone with LineageOS 14 with TWRP 3.0.0.10. I wanted to try LineageOS 17.1. That's where story started.
LOS documentation says that phone needs to be rooted and it needs to have LOS recovery. I've installed Root Checker and saw that my phone isn't rooted. I followed this guide to root my phone. It didn't succeed after many tries (After first boot, script haven't recognized my phone). After this failure I checked my root status in download mode. It said ROOTED. Then I continued with LOS documentation, I run `adb shell` then run `su`. Shell gave me `su: unknown command` response. I've searched how to root using TWRP and most of the articles mentioned that flashing SuperSU zip should solve the problem. Then I tried this method. Sadly, it didn't solve root problem.
Now, device is giving `Secure booting error` above LG logo during boot. I can't pass this screen, it is stuck at LG logo. Online articles are mentioning that I should flash regular old LG KDZ to have my phone back. I have tried 4 versions of LG Flash Tool and LG UP with no luck, they didn't work. I still have access to TWRP and download mode. How can I solve this problem?

For future reference, this is how i solved my problem
I have flashed the phone with TOT using this guide
Installed attached LG drivers
Installed attached LG Flash Tool 1.8 for TOT
Copy&pasted attached Megalock.dll file into LG Flash Tool
Downloaded TOT files from here and followed the guide
after this process, phone booted correctly into Android 4. in order to upgrade to Lollipop
I have used attached LG FlashTool 2.0
Then specified regular KDZ file for lollipop found here. I've used Normal flash method as CSE Flash method didn't work at all.
After this process, phone rebooted into Android 5. Then I followed this guide to root the phone. While rooting in download mode, i've replug the device in order for OneClickRoot program to recognize my device.
Phone rebooted itself. I've checked root status and it was successful. Then I followed steps in LOS documentation.
These steps solved my problem and I'm using Android 10 on my 7.5 year old Android phone!!

LG G6 - TWRP loop

Hello! Sorry for my bad language, but English is not my native language.
I have a LG G6 H870 EU. A year ago I unlocked the bootloader, installed TWRP and a custom rom.
Everything worked, but I bought a newer phone. Now I need LG G6 with original firmware (and stock camera app). I found the stock software on XDA for TWRP. I installed them. The phone booted up properly, Android requested data formatting. When I agreed, my phone got stuck in the TWRP loop.
Now I install various software, custom and stock - only TWRP starts every time. I tried LG UP but at 9% it shows "USB Connection established" error. I've tried various DLLs, but on others the program doesn't start at all. Maybe I have the wrong DLL? I've tried UPPERCUT too.
Please help, thank you.

Hi. I have a similar problem on my LG G6. After selecting reboot from TWRP, the message "No OS Installed!" shows. After reboot I get into TWRP again.

Using LGUP CMD (command line) I was finally able to flash the phone and get it working.
See:
How to use LGUP (Command Line) to flash LG phones
This guide will explain how to use LGUP (Command Line version) to flash firmware (in .kdz or .tot format) to an LG Android device. RequirementsDownload and install LG drivers Download the firmware for
www.hovatek.com
LGUP CMD / Dev / Lab / Store Tool Versions
Below is a collection of different versions of LGUP CMD / Dev / Lab / Store tools. They are Windows tools for flashing .kdz & .tot files / firmware to an LG Android device Download LGUP CMD / Dev / La
www.hovatek.com
LGUP_common dll versions
Below is a collection of different versions of LGUP_common.dll. They are files necessary for getting LGUP to properly detect an LG phone in download mode. Download LGUP common dll LGUP common dllLGUP_
www.hovatek.com
It might work for you. It is worth a try. Good luck.

worldoflimak said:
Hello! Sorry for my bad language, but English is not my native language.
I have a LG G6 H870 EU. A year ago I unlocked the bootloader, installed TWRP and a custom rom.
Everything worked, but I bought a newer phone. Now I need LG G6 with original firmware (and stock camera app). I found the stock software on XDA for TWRP. I installed them. The phone booted up properly, Android requested data formatting. When I agreed, my phone got stuck in the TWRP loop.
Now I install various software, custom and stock - only TWRP starts every time. I tried LG UP but at 9% it shows "USB Connection established" error. I've tried various DLLs, but on others the program doesn't start at all. Maybe I have the wrong DLL? I've tried UPPERCUT too.
Please help, thank you.
Click to expand...
Click to collapse
Sorry for the post hijack, just curious. How did you manage to unlock your bootloader a year ago. I thought LG stopped providing the unlock.bin's like, 5 years ago?