Database Users

[Q] [t-mobile d801 soft bricked can't use LG tool

I can get into download mode, but have a secure boot error and cant use ADB or fastboot. I've been reading every thread I can find.
I tried the LG tool, it never downloads the firmware, just hangs at 12%. Tried different drivers etc. Let it run overnight just in case it was a slow download - nada.
Tried the LG tool by entering the imei number first, but the tool reports a low battery and won't load the firmware. Phone is fully charged, i assume that battery level reporting is not working correctly.
Tried to load the kdz with the R&D tool, it errors out at 49%.
Tried to do the offline process with shttp from the unbrick any phone thread. It uses an older version of the LG tool and won't recognize that the phone is plugged in. If i install the newer tool that sees the phone, the process crashes the tool.
it all started when i tried to flash twrp and used the one for a different model g2. Dumb, I know. this is my first time soft-bricking a device.
Can anyone please point me in another direction?
UPDATE: phone was reporting that it was an 802. Downloaded and flashed an 802 kdz file and the phone booted! First time it was able to get past 49%. Nothing really works on the phone, but now i'm able to use the LG Mobile support tool to flash the correct firmware. The program is downloading the sofware now.

When you say LG tool I'm assuming you're talking about the official program you can download from their site?
I have the Verizon G2 and promptly erased everything on it the first night I got it.. Don't flash / wipe files at 4 AM when you've been up all day and night.
Anyway this thread http://forum.xda-developers.com/showthread.php?t=2432476 really saved my rear. Maybe the T-Mobile version will work to get yours back to stock.
Sent from CAMACHO, my Verizon G2 (VS980) running PAC ROM.

Vepaot said:
When you say LG tool I'm assuming you're talking about the official program you can download from their site?
I have the Verizon G2 and promptly erased everything on it the first night I got it.. Don't flash / wipe files at 4 AM when you've been up all day and night.
Anyway this thread http://forum.xda-developers.com/showthread.php?t=2432476 really saved my rear. Maybe the T-Mobile version will work to get yours back to stock.
Sent from CAMACHO, my Verizon G2 (VS980) running PAC ROM.
Click to expand...
Click to collapse
works at the start and hangs at 49%. There is one bit that needs to be switched and this would work.

okay, looks like the phone is reporting that it is a d802 from my first f'd up flash. I think this may be causing the problems with flashing the 801 kdz.
Can i flash an 802 kdz onto an 801? then possibly later go back to 801?

[Q] LG G2 Soft Bricked. Stock recovery, No download mode, No backup or data.

So here's a new one for you...
I'm working on trying to fix a friends LG G2 LS980 from Sprint, and for whatever reason. It boots into the stock recovery but has no download mode. When attempting to boot as normal it says "Security Error". (Because it has no OS to boot into, as the owner somehow deleted it) Normally in a soft brick i could just use download mode to re-install the stock firmware, but obviously that can't happen without download mode. ADB has only given errors for no apparent reason as well. I'm at a loss... "Can you help us??"- Galaxy Quest
Any tips or similar issues reported would be appreciated.
After searching for quite a while only one other person has reported this issue and no one has answered him. But I trust XDA won't have the same issue. I appreciate your time and look forward to your help.

Nothing? Tsk tsk XDA..

[Q] Help with VS980

Hello everyone, I have the Verizon LG G2 and it thinks it's a different g2. I have edited the .tot's to other device models and it still won't work. I have followed many threads and none are working for me. I also did try the .kdz method which kept getting stuck at 2%. I also do not have twrp.... My question is is there a way to install twrp right from download mode to try to flash the right software to get it working agian? Or does somebody think they can help me figure out the problem with the download mode restore?

LG V20 H910 Rom issues

For some reason I can't post when I use the model number listed in the title and the Canada variant model name. Says the post is "flagged". So that's why I'm not using the model numbers.
Hi. So last week I got a new V20....and I bricked it...within 3 hours. I'm hoping someone can help me out. So, here's what happened. I'm sure this subject has been posted 1000 times, but nothing I've read is exactly like my situation.
I bought a AT&T Model. I didn't realize how complex it was to root it. Was very easy on my D855. First I made a backup of all partitions with LGUP. Which is useless, since it's, not a kdz. I tried to unlock the bootloader with Dirtysanta. I got the static. I reflashed it with the stock Canada variant kdz. It booted just fine, but had no service. Dirtysanta also resulted in static with Canada variant rom. Reflashed Canada variant again. This time using one of the LG tools I tried merging the AT&T Model modem into a kdz file, hoping it would get a cell signal again. This failed spectacularly, because LGUP said it wasn't a valid kdz. (I'm guessing kdzs are signed and LGUP verifies them? Don't know. This stuff is clearly new to me.) Anyway, at this point I tried the dirtysanta method one more time. Got stuck with a bootloop about "corrupt device" and the red triangle. Finally managed to get download mode to work again. Flashed it with stock US996 v10f. Now it's impossible to go back to Canada variant kdz, and there is still no AT&T Model kdz. So it looks like my once AT&T Model is now stuck as a US996. Which, I guess is ok with me. Mainly I just wanted to get rid of the AT&T crapware. But, of course the FM Radio doesn't work now. Also, dirtysanta also gives static with US996 rom. Most people said if you turn the screen off and back on, the static goes away. But for me, the buttons don't. Phone doesn't show up in ADB, Windows explorer or device manager. But it's fully booting, because through the static I can see the "Welcome" screen. Now, if I'm understanding this right, the FM Radio doesn't work in the US996 version because of the kernel. And boot partiton = kernel? So using LGUP with PARTITON DL, I flashed just the boot partiton from the Canada variant kdz. Got to the second "LG" screen and doesn't boot past that. So, I flashed the correct boot partition back and it once again booted. So, fianlly to what I'm asking. Is there anyway to get:
1. TWRP recovery
2. Rooted US996 rom
3. The static to go away...and go away permanently
4. FM Radio working (there was talk about custom kernel?, but haven't gotten that far since I can't get the static to stop)
5. Red triangle error to go away
Last issue isn't that big of a deal, but just wondering if anyone has a fix for this yet. Help would greatly be appreciated. Thanks.

popit12 said:
For some reason I can't post when I use the model number listed in the title and the Canada variant model name. Says the post is "flagged". So that's why I'm not using the model numbers.
Hi. So last week I got a new V20....and I bricked it...within 3 hours. I'm hoping someone can help me out. So, here's what happened. I'm sure this subject has been posted 1000 times, but nothing I've read is exactly like my situation.
I bought a AT&T Model. I didn't realize how complex it was to root it. Was very easy on my D855. First I made a backup of all partitions with LGUP. Which is useless, since it's, not a kdz. I tried to unlock the bootloader with Dirtysanta. I got the static. I reflashed it with the stock Canada variant kdz. It booted just fine, but had no service. Dirtysanta also resulted in static with Canada variant rom. Reflashed Canada variant again. This time using one of the LG tools I tried merging the AT&T Model modem into a kdz file, hoping it would get a cell signal again. This failed spectacularly, because LGUP said it wasn't a valid kdz. (I'm guessing kdzs are signed and LGUP verifies them? Don't know. This stuff is clearly new to me.) Anyway, at this point I tried the dirtysanta method one more time. Got stuck with a bootloop about "corrupt device" and the red triangle. Finally managed to get download mode to work again. Flashed it with stock US996 v10f. Now it's impossible to go back to Canada variant kdz, and there is still no AT&T Model kdz. So it looks like my once AT&T Model is now stuck as a US996. Which, I guess is ok with me. Mainly I just wanted to get rid of the AT&T crapware. But, of course the FM Radio doesn't work now. Also, dirtysanta also gives static with US996 rom. Most people said if you turn the screen off and back on, the static goes away. But for me, the buttons don't. Phone doesn't show up in ADB, Windows explorer or device manager. But it's fully booting, because through the static I can see the "Welcome" screen. Now, if I'm understanding this right, the FM Radio doesn't work in the US996 version because of the kernel. And boot partiton = kernel? So using LGUP with PARTITON DL, I flashed just the boot partiton from the Canada variant kdz. Got to the second "LG" screen and doesn't boot past that. So, I flashed the correct boot partition back and it once again booted. So, fianlly to what I'm asking. Is there anyway to get:
1. TWRP recovery
2. Rooted US996 rom
3. The static to go away...and go away permanently
4. FM Radio working (there was talk about custom kernel?, but haven't gotten that far since I can't get the static to stop)
5. Red triangle error to go away
Last issue isn't that big of a deal, but just wondering if anyone has a fix for this yet. Help would greatly be appreciated. Thanks.
Click to expand...
Click to collapse
Static after engineering boot is fine. It boots up after a minute of wait on static screen. Also that triangle mark screen is fine too, wait for a minute which u didn't.
You should have followed brian's guide to root an H910.....
[ROOT] HOWTO: AT&T H910 up to v10v (FULLY TESTED)
https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500
Even I was able to root using this method on my Puerto Rican v20 H910PR

Thank you. I finally realized what I was doing wrong. I was skipping the step on installing H915 kdz FIRST. Guess it helps to actually follow all the instructions! Anyway, I got it working. I was even able to completely get rid of static boot with MegaRom & the mk2000 kernel. FM Radio works, too!

So how badly i bricked LG V20 LS997?

I got LS997 that was not completely unlocked (Sprint support confirms unlock status but phone did not receive unlock command, and i got no sim card and no previous owners name to re-initiate ota-unlocking process)
First thing i did - i used pathed LGUP and dirtysanta rooted my phone.
Suggested 995 kdz rom was vibrating like crazy (as described in dirtysanta guide) but i got root and started experimenting further.
Than i flashed rootable 996 kdz, rooted, had no vibration problem but got static boot issue, ok, installed mk2000 kernel, no static - all good but still not enough.
LOS16 = gsm/lte unlocked but battery was drained in 5 hours with screen turned off and no camera, got back to 996, rooted, super rom, all good but LTE not operating for some reason. Really enjoyed stock functionality (camera, seconds screen) and decided to get back to stock system.
HOWTO: Root LS997 up to ZV7, did it all, started flashing available 'stockish' roms one by one [this, and this], so there goes bad stuff.
At this moment i was still being able to boot into twrp, so i didn't really notice that phone was bricked, those stockish systems was just hanging in LG logo for hours without any progress. ok, found another one stock ls997 rom in dirtysanta root post, flashed it - and nothing, phone still stuck at lg logo.
LGUP flashing routine that was always helping me recover, now if fully completes partition_dl process but results are the same - lg logo for hours without anything happening, except vibrator motor starting to work on power up on Verizon firmware version and no vibro on 996 variant (as it sould):
996 kdz - stuck on logo
996 kdz- stuck on logo
flashing everything i got from lg-firmwares.com:
US99610g_00_1216 - stuck on logo
US99610f_00_1205 - stuck on logo
US99620f_00_1120 android 8.0 - stuck on logo
VS99512A_06_1114_ARB00 - stuck on logo
download couple more variants and still nothing, phone stucking in lg logo
so how badly i bricked it? is there any method of recovering that i am not aware of?

There is an older thread on returning the LS997 back to stock that may help.

C D said:
There is an older thread on returning the LS997 back to stock that may help.
Click to expand...
Click to collapse
Yeah, thanks, been there.
Unfortunately i'm not meeting 2 of 3 prerequisites:
- Your device needs to be able to boot into TWRP and fastboot mode
- You need access to a computer to run ADB commands to the phone
There are no more twrp presents on device because of kdz uploads from LGUP, i was thinking that it was recovery and aboot partitions that was messing up my system.
And there is no bootable system on device to turn on usb debbuging to run ADB commands as only thing i get is boot logo, fastboot are also locked to 995 or 996 (whatever version i've uploaded last from LGUP, and they are not unlockable because LG recognizes original LS997 hardware identification and refuses to give me unlock.img.
As i get it - the only thing that can tinker with my device is something that can get same hardware access as LGUP (laf is still operational or idk, maybe not, but it should be getting everything up and running but that is not the case anymore for some reason)

So you are saying that LGUP can still see the phone but ADB can't. Did you by any chance do a full system dump of the phone on LGUP before the whole DirtySanta procedure in the beginning? I wonder if those files can help getting things back on track. Not sure if they are device-specific, but I did make a dump of my own LS997, so if you think there's something useful there, let me know, and I can upload the files somewhere.

C D said:
So you are saying that LGUP can still see the phone but ADB can't. Did you by any chance do a full system dump of the phone on LGUP before the whole DirtySanta procedure in the beginning? I wonder if those files can help getting things back on track. Not sure if they are device-specific, but I did make a dump of my own LS997, so if you think there's something useful there, let me know, and I can upload the files somewhere.
Click to expand...
Click to collapse
Yes i did full LGUP backup at first system state, but nature of this backups makes them pretty useless in this system state - because they are just images of partitions.
Only software that can write directly to those partition may be able to utilize those backups, there are a lot of post on this forum describing TWRP routine for making update packages based on LGUP backups.
So unfortunately there is only LGUP, but it only can make backups but can not restore them as it uses some special file format (KDZ) that containing some dll's and data files (like glued partition images with special info of where to put what) and i didn't find a way to make my own KDZ files from backup images.
I'm now getting another idea - that this can be a blowed fuse in CPU ARB protection mechanism, if anyone has experienced ARB 1 please confirm that system should be in this state in case of ARB error