Over the years I've always been good at solving these things, but this is the first time I've every had to request help/guidance.
LG
1. Came from from 4.4.2, ioroot rooted, installed twrp via freegee, but not the kernel patch. This prevented me from booting back into Android.
2. Factory reset everything, wiped everything from twrp.
3. Ran adb commands here:http://forum.xda-developers.com/showthread.php?t=2451696 Got me into fastboot.
4. Flashed all .img files for LG D800 from prime's D800 img stash. Fastboot rebooted.
5. Installed Mahndi ROM via adb. Reboot
6. Stuck. Phone hangs on LG logo, loading modem and com drivers in windows. Recovery is now stock, so no flashing. Download mode works but always get a "Device Model is different" error at 0% when flashing from LG Flash Tools. Correct .tot and correct .dll for D800.
Any help or ideas to get my G2 up and running again would be amazing. I'm still trying to figure out if I can modify the .tot to match my device's current model or just ignore it and overwrite (best hope). Even if i can get ubuntu to detect the phone that would lit my spirits.
Thanks.
Progress
So I have actually figured out the problem completely, yet I do not yet have a solution.
-I after flashing the correct .img over to my device, I was all set to go, but read somewhere about flashing over mahdi ROM.
-I successfully flashed Mahdi, but DID NOT FLASH THE DEVICE VERSION PATCH (literally hit my head on the desk when I realized).
-I panicked after it did not work and reflashed all the .img so I was stuck with stock recovery, no adb, no sideload, no fastboot.
Is there ANY WAY to flash back to stock with the LG Flash Tool for the ATT D800 that ignores the model number inconsistency. This type of phone only supports the .TOT method of flashing. There is no other way (KDZ = NO). Currently my device's build.prop says that the model is "g2" (this is what the patch was supposed to fix) and my flashing file/.dll is for "D800".
My device can not be seen in Ubuntu.
Any suggestions?
datdude_tc said:
So I have actually figured out the problem completely, yet I do not yet have a solution.
-I after flashing the correct .img over to my device, I was all set to go, but read somewhere about flashing over mahdi ROM.
-I successfully flashed Mahdi, but DID NOT FLASH THE DEVICE VERSION PATCH (literally hit my head on the desk when I realized).
-I panicked after it did not work and reflashed all the .img so I was stuck with stock recovery, no adb, no sideload, no fastboot.
Is there ANY WAY to flash back to stock with the LG Flash Tool for the ATT D800 that ignores the model number inconsistency. This type of phone only supports the .TOT method of flashing. There is no other way (KDZ = NO). Currently my device's build.prop says that the model is "g2" (this is what the patch was supposed to fix) and my flashing file/.dll is for "D800".
My device can not be seen in Ubuntu.
Any suggestions?
Click to expand...
Click to collapse
over here http://androtransfer.com/AndroidUser00110001/ROM/G2/KK/D80220a/ there is a dll named lgup_8974.dll which is for d800 and is supposed to skip the model check
datdude_tc said:
Over the years I've always been good at solving these things, but this is the first time I've every had to request help/guidance.
LG
1. Came from from 4.4.2, ioroot rooted, installed twrp via freegee, but not the kernel patch. This prevented me from booting back into Android.
2. Factory reset everything, wiped everything from twrp.
3. Ran adb commands here:http://forum.xda-developers.com/showthread.php?t=2451696 Got me into fastboot.
4. Flashed all .img files for LG D800 from prime's D800 img stash. Fastboot rebooted.
5. Installed Mahndi ROM via adb. Reboot
6. Stuck. Phone hangs on LG logo, loading modem and com drivers in windows. Recovery is now stock, so no flashing. Download mode works but always get a "Device Model is different" error at 0% when flashing from LG Flash Tools. Correct .tot and correct .dll for D800.
Any help or ideas to get my G2 up and running again would be amazing. I'm still trying to figure out if I can modify the .tot to match my device's current model or just ignore it and overwrite (best hope). Even if i can get ubuntu to detect the phone that would lit my spirits.
Thanks.
Click to expand...
Click to collapse
I have almost the exact same problem will keep an eye on thread, hope we git it sorted soon!
I'll Take a look
XxZombiePikachu said:
over here http://androtransfer.com/AndroidUser00110001/ROM/G2/KK/D80220a/ there is a dll named lgup_8974.dll which is for d800 and is supposed to skip the model check
Click to expand...
Click to collapse
Thanks!
I have seen and downloaded that one before, and if I recall correctly, I didn't get a model error, but rather something else. I believe it was a bin file error??, but I do not recall. I actually just sent my G2 in on a warranty claim (*please oh please don't notice I replaced the screen") and hopefully that will take care of it. I was just posting so that maybe someone doesn't have to dig through 350 pages of replies to find out what happened. I'll keep the post going when I find anything out though.
Working together!
MRobbo80 said:
I have almost the exact same problem will keep an eye on thread, hope we git it sorted soon!
Click to expand...
Click to collapse
I won't have my phone available for a few days. Any chance you could go ahead and give that lgup_8974.dll a test run and report back? I'd be more than willing to help do any research if it gives a different error besides the model.
Sorry to dig up this thread, but I have the exact same problem, except I flashed mahdi on my D802 and somehow the version patch didnt flash correctly. Is there anything like a lgup_8974.dll for D802s?
I'm really desperate here.
i have the exact same problem!!
Any solution found yet??
jeanclaudevandamme said:
Right, I've figured out where things have went wrong but still can't find a fix
1) So after Step 14 after running the BAT files all cmd windows closed. I then clicked step3.bat while in fastboot mode. because he did not explain clearly where you were supposed to get CMD window for commands in Step 16.
I had used CMD / ADB / Fastboot years ago, but I had forgotten how they worked exactly, as the instructions for the previous phones I have rooted were so much better written.
later i discovered how to see what was inside a BAT file (use notepad to open it) so step3.BAT contained instructions to flash "boot1.img" which came with the Dirty Santa v20 files. I don't know what model that boot image was taken from. it also contained instructions to flash a twrp file name that didn't exist (so I guess nothing would have gotten flashed).
2) later I was able to launch into fastboot mode and manually flash the correct twrp file onto the phone. then led me being able to get into twrp recovery to flash kernel + SU.
However phone still didn't boot, presumably of the mistake was previously by clicking Step3.BAT, which flashed a "boot1.img" from dirty santa files
Also when going into download mode, the phone would crash with static 1 second after connection.
3) At the time, I didn't know the difference between aboot and boot files. So I went into fastboot and flashed abootbackup.img
I still don't know fully what aboot does. But the effect it has is it locked the bootloader, so i am no longer able to flash anything with fastboot. writing the old aboot.img has caused my device to go into a corrupt bootloop, cannot launch into recovery.
I think that if I flashed bootbackup.img then things might have worked out ok. i had 2 choices and I picked the wrong one, but that's gone now.
flashing the abootbackup.img also had another effect, download mode no longer crashed with static after 1 second, however a new error code came up when download mode is launched <633A B50>, the phone acts like a firmware is currently trying to be flashed but stuck at 0% even just by launching download mode.
I'm guessing there may be some sort of variant mismatch between the boot1.img and the abootbackup.img as the boot1.img wouldn't have originally come from my phone? As well as the other stuff pushed onto device in Step2.BAT
eithe way, LG Bridge / LGUP do not recognise model even with Uppercut.. LG Flash 2014 has the error messge of "connection to server failed", I tried letting it run in the background without closing error message as suggested in that thread, but I guess because of my 633A B50 error message, flashing did not occur in the background like other people.
----------------
I don't know where to go from here exactly. because
1) boot1.img, that came with dirtysanta files, which model / variant did it come from?
2) what LGUP_common.dll will recognise my device now? I know someone patched their DLL, but how do you patch a DLL using hex editor and how to make the DLL recognise my presumably mismatched device?
3) i don't know what the <633A B50> error message means exactly
------
https://forum.xda-developers.com/v20/help/help-h990ds-t3650303
looks like someone did something similar to what I did. he didn't get answers to his questions and he hasn't been logged in since August..
Click to expand...
Click to collapse
It's more bricked than usual..
Have a go at this?
I like using the LGUP Patched DLL for H91810J. It seems to recognize all variants.
as a last resort use LG Bridge, refurbish. it will repair all sorts of half installs and messed up partitions. the only thing is : IT WILL BRING YOUR BUILD UP TO 10q=================WHICH IS NOT ROOTABLE!!======================
Just in case this issue has not been resolved. I did the same thing 10 minutes ago. I flashed the wrong abootbackup.img (10c) instead of 10d.
All you have to do is open LGUP and if the device won't be recognise, just run the Uppercut tool and the device will show up. Flash your .kdz file and the phone should be running once again.
Hello to all of you taking your time reading this. I have got into some problems with my LG G2 D802 recently. More precisely: I have bricked it and installed a broken recovery. HELP!
It all started with me wanting to upgrade my LG G2 to android Pie 9.0 with a custom rom. So I found an all in one tool to root and install TWRP on the phone (I probably never should have done that). I quickly realized that inside TWRP only the upper half of the screen was working somewhat close to normal, and the lower part was completely messed up. That made me unable to install the custom rom I had downloaded.
- - -
ADB and Fastboot
I tried to get rid of TWRP by using ADB and Fastboot to install the stock recovery back on my device. I wanted to use the command: “fastboot flash recovery recovery.img”. Though, before I even came that far, I had troubles getting my phone into fastboot mode. Whenever I executed the command: “adb reboot bootloader”, the phone just restarted and went back into TWRP. How can I enter fastboot?
This had been tried on multiple systems including Linux, Windows 7 and 10, with different USB drivers all removed completely between testing.
- - -
LG FlashTool (v. 1.8.6.527)
Then I went to try install a stock rom on my phone (which I had done once before with LG FlashTool). So I started the tool and put my phone into download mode. It got detected on COM41 and the flashing could start. I used the following files: LGD802_20130912_LGFLASHv160.dll and BIN_LGD802AT-00-V10b-SEA-XX-SEP-04-2013-32G+0.tot.
When LG FlashTool then reports: “CUST”, “Skip BackupGPT Partition.” and then “Waiting for reset 120 sec”, the phone reboots. . . - into TWRP. . . Sighs*. . .
I tried to shut it back down and enter download mode again while LG FlashTool was running. But after a while LG FlashTool just says: “FBOOT Check….“, then “FBOOT FAIL!!” and “Fail to get BOOT Complete Status. 00000064”
So is FBOOT = fastboot? If so, have I then messed something up with my fastboot then?
- - -
LG Flash Tool 2014
I also tried flashing with the kdz file called: Europe Open D80230b.kdz. But here my device didn’t even got detected by the tool. So I started searched for something else on the web, found nothing, and here I am.
I honestly don’t know what to do next. I know that one quick solution is to go and get a new phone. But that solution is expensive and what I really want, is to get my LG functioning again.
As I see it, the options for getting the phone back, is to fix either fastboot, TWRP(screen not working), LG Flash Tool 2014(if it not uses fastboot) or use this tool; SRK Tool 2.1. I just don't know how to proceed with any of this.
Any kind of help is highly appreciated. Thank you.
Hi,
I’ve got an older Verizon LG V20 that’s been bricked. I hid it in a drawer for the past year or so, and stumbled across it again. If I can get this fixed, I’d love to update it and give it as a gift to an older friend who has a 6 yr old crap android phone. But first, some history…
-bought used in great shape and rooted with Dirty Santa to run on TMobile. I don't recall which ROM I used, but it was very stock minus the carrier apps. My wife had a chance to go to Italy, so we bought a 3rd party european SIM with 30 days of data and voice from Three UK. Short story is that the phone never recognized the SIM, but she used it to take some great pics during her stay.
-once back in the US, I decided to try a different ROM and I think I flashed the wrong files or something… it’s my fault but I honestly can’t recall if I loaded a Samsung image instead, or what exactly happened.
Currently, the phone boots ONLY into fastboot mode. ADB does not recognize the device, and I’m thinking that I’ve lost TWRP Recovery since I can’t enter Recovery Mode at all.
If I do hold Vol Down + Power, I get a Hard Reset menu, but nothing in there helps.
I tried using LGUP, but the device is "not recognized."
I’m at a loss as to what to do at this point. If there IS a way to un-brick this, I think it would make a great phone for a good friend.
If anyone has any suggestions, I’d love any ideas that you may have. I tried looking to see if any other threads cover this, but I’m not seeing anything with specifics or pointers to How-Tos. If I missed the relevant links, I’d appreciate being pointed to them.
Also…
-if I can return to Stock condition, I can then unlock the bootloader and flash a more current ROM again. Would I need to pick a new radio so it better matches TMobile vs the Verizon setup it originally came with?
thanks for reading!
motionmonk
Since you can get to fastboot why not flash a twrp to see if you will get recovery
0x0null said:
Since you can get to fastboot why not flash a twrp to see if you will get recovery
Click to expand...
Click to collapse
When I run fastboot in Terminal, I get a blank response-- that is, a simple carraige return with no info listed.
This is on a fresh Win10 install with the latest Platform Tools package (Justt adb & fastboot) from the Android Studio website.
Are there other drivers that I need? When I installed LGUP, I did install the LGMobileDriver_WHQL_Ver_4.1.1.exe installer as well.
-motionmonk
motionmonk said:
When I run fastboot in Terminal, I get a blank response-- that is, a simple carraige return with no info listed.
This is on a fresh Win10 install with the latest Platform Tools package (Justt adb & fastboot) from the Android Studio website.
Are there other drivers that I need? When I installed LGUP, I did install the LGMobileDriver_WHQL_Ver_4.1.1.exe installer as well.
-motionmonk
Click to expand...
Click to collapse
That is bad, can you try it ona windows 7 PC?
0x0null said:
That is bad, can you try it ona windows 7 PC?
Click to expand...
Click to collapse
I could... I need to find my Win7 install disks for an old laptop.
I'll report back by tomorrow.
I don't do this often... what makes WIndows 7 a better method than Win 10?
-motionmonk
motionmonk said:
I could... I need to find my Win7 install disks for an old laptop.
I'll report back by tomorrow.
I don't do this often... what makes WIndows 7 a better method than Win 10?
-motionmonk
Click to expand...
Click to collapse
issues with drivers
It took longer than I thought to find my Win7 installers... I'm in the middle of the reinstall now.
I plan to load the Android Platform Tools, LG Mobile Drivers, LGUP framework... is there anything else I should install?
thanks for any suggestions; I don't root often at all and am rusty at this
-motionmonk
Win 7 update
Ok, I've installed WIN7, Android Platform Tools (just ADB & Fastboot), LG drivers and LGUP.
Now when I do the fastboot command, I get a true response:
fastboot devices
VS995aa11a111 fastboot (where a=letters, 1=numbers)
YAY!
So at this point, if I load a TWRP.zip, would I be able to boot into Recovery, instead of fastboot mode?
I checked the official TWRP website, and the latest is TWRP 3.2.3-0.
EDIT: I looked in the LG Section, and it appears that there is not an official TWRP for the LG V20. Is that right?
Having gotten to the point where the laptop recognizes the phone, I really don't want to make a dumb mistake :silly:
thanks for getting me this far!
-motionmonk
motionmonk said:
Win 7 update
Ok, I've installed WIN7, Android Platform Tools (just ADB & Fastboot), LG drivers and LGUP.
Now when I do the fastboot command, I get a true response:
fastboot devices
VS995aa11a111 fastboot (where a=letters, 1=numbers)
YAY!
So at this point, if I load a TWRP.zip, would I be able to boot into Recovery, instead of fastboot mode?
I checked the official TWRP website, and the latest is TWRP 3.2.3-0.
EDIT: I looked in the LG Section, and it appears that there is not an official TWRP for the LG V20. Is that right?
Having gotten to the point where the laptop recognizes the phone, I really don't want to make a dumb mistake :silly:
thanks for getting me this far!
-motionmonk
Click to expand...
Click to collapse
There is no official twrp build for the V20, search for Phoenix's unofficial twrp thread
Sent from my LG-H910 using XDA Labs
cnjax said:
There is no official twrp build for the V20, search for Phoenix's unofficial twrp thread
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Thank you cnjax... I think I got it now:
recovery-twrp-vs995-2018-10-18
Now that I have the TWRP Installer, I connect the phone (in perma-fastboot mode), and verify that it is connected by using fastboot devices. I get a recognition string in reply. So now I move on...
-rename recovery-twrp-vs995-2018-10-18.img as TWRP.img
-move TWRP.img to my platform-tools folder
-issue flashing command fastboot flash recovery TWRP.img
Here's what I get:
Sending 'recovery' (25984 KB)
OKAY [ 0.889s]
Writing 'recovery'
FAILED (REMOTE: 'unknown command'}
Finished. Total time: 1.092s
I'm pretty sure I have the syntax correct, and the TWRP.img file is being recognized, but -something- isn't working.
Have I missed something here?
thanks for any suggestions,
motionmonk
fastboot help pages
motionmonk said:
Now that I have the TWRP Installer, I connect the phone (in perma-fastboot mode), and verify that it is connected by using fastboot devices. I get a recognition string in reply. So now I move on...
-rename recovery-twrp-vs995-2018-10-18.img as TWRP.img
-move TWRP.img to my platform-tools folder
-issue flashing command fastboot flash recovery TWRP.img
Here's what I get:
Sending 'recovery' (25984 KB)
OKAY [ 0.889s]
Writing 'recovery'
FAILED (REMOTE: 'unknown command'}
Finished. Total time: 1.092s
I'm pretty sure I have the syntax correct, and the TWRP.img file is being recognized, but -something- isn't working.
Have I missed something here?
thanks for any suggestions,
motionmonk
Click to expand...
Click to collapse
Hi
I'm just a noob but I am interested in the problem you are having and am following it to see what comes up with it.
There is a good fastboot thread here:
https://forum.xda-developers.com/showthread.php?t=2277112
On the first page you have options to wipe before flashing - i.e. system, boot, data, RECOVERY etc,
Maybe give those pages a read while waiting for someone more knowledgeable to fix your phone...
Since you are not sure what happened maybe the modem was affected which I think is bad...
I think doing a "fastboot getvar all" might give you a status of what you are dealing with .... since it gives you versions
of things...
Anyhow, good luck reviving the phone - "rooting" for you haha!
---------- Post added at 10:33 PM ---------- Previous post was at 10:05 PM ----------
This link might also be a good read
https://forum.xda-developers.com/v20/how-to/guide-lg-v20-to-life-t3827732
secondhand2 said:
There is a good fastboot thread here:
https://forum.xda-developers.com/showthread.php?t=2277112
. . .
I think doing a "fastboot getvar all" might give you a status of what you are dealing with .... since it gives you versions
of things...[/url]
Click to expand...
Click to collapse
secondhand2,
THX for the links! Those were very helpful!
No need to call yourself a noob... I think I outrank you in that department at this point!
I did try your suggestion of fastboot getvar all, and found something interesting...
when I did the command it returned (bootloader) unlocked:no
which I thought was WEIRD, since the phone -was- unlocked with a custom ROM before I messed things up.
I have attached a screenshot to this msg with the full info report.
So now I'm wondering if that's why my previous attempt at flashing TWRP failed?
Does this mean I have a soft-brick or a hard-bricked phone at this point?
I"m learning more through everyone's help and input, but I'm still lost as to where to go from here.
Hi,
I have a US996 and I unlocked it using the lg web site - they send a bin file that you can use to unlock the phone.
There are different exploits on different versions of V20 phones. THere are also versions of Nougat that have an anti rollback that stop you from going from a recent OTA update back to an older one that can be exploited to get root. For example, on the US996 I have., if I had bought it and it had been patched with 10p (not 100% sure which version was the cutoff point) even if the phone was unlocked, I might not be able to get root. So the versions of the ROMs/firmware are imnportant. As it happened I had the 10f version so rooting was possible - but I followed the threads on this site for my specific phone and stuck to STOCK rom's.
So I'm not sure about what ROM you have - i..e which version of the vs995 is rootable after you unlock the phone. And the unlocking method to use - I'm not familiar with dirty santa or lafsploit (might not have spelled that correctly). There is a tool called LGUP and a good thread on that below that I was reading but it is long read which is good for learning.
I can only point you to some threads - but unlocking is the next hurdle.
You might also want to use the latest TWRP and Magisk if you do get to root the phone. I used PHOENIX591's TWRP
- there is a good thread on that. https://forum.xda-developers.com/v2...-t3720239/post78529520?nocache=1#post78529520
Sorry I can't help you more with this - you do need to get the phone unlocked first. Some of these things are very device specific
I'm still keeping an interested eye on this...
Here is the other thread
https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
Good Luck!
secondhand2 said:
Hi,
I have a US996 and I unlocked it using the lg web site - they send a bin file that you can use to unlock the phone.
There are different exploits on different versions of V20 phones. THere are also versions of Nougat that have an anti rollback that stop you from going from a recent OTA update back to an older one that can be exploited to get root. For example, on the US996 I have., if I had bought it and it had been patched with 10p (not 100% sure which version was the cutoff point) even if the phone was unlocked, I might not be able to get root. So the versions of the ROMs/firmware are imnportant. As it happened I had the 10f version so rooting was possible - but I followed the threads on this site for my specific phone and stuck to STOCK rom's.
So I'm not sure about what ROM you have - i..e which version of the vs995 is rootable after you unlock the phone. And the unlocking method to use - I'm not familiar with dirty santa or lafsploit (might not have spelled that correctly). There is a tool called LGUP and a good thread on that below that I was reading but it is long read which is good for learning.
I can only point you to some threads - but unlocking is the next hurdle.
You might also want to use the latest TWRP and Magisk if you do get to root the phone. I used PHOENIX591's TWRP
- there is a good thread on that. https://forum.xda-developers.com/v2...-t3720239/post78529520?nocache=1#post78529520
Sorry I can't help you more with this - you do need to get the phone unlocked first. Some of these things are very device specific
I'm still keeping an interested eye on this...
Here is the other thread
https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
Good Luck!
Click to expand...
Click to collapse
You're incorrect arb hasn't been incremented on the 996
Sent from my LG-H910 using XDA Labs
Hi cnjax
The thread I used discussed arb but from what I remember it was never clear how to know which arb ( 0 or 1 ) a particular update was at. Are you saying there is never an increment for the us996?
Thank you for clarifying
secondhand2 said:
Hi cnjax
The thread I used discussed arb but from what I remember it was never clear how to know which arb ( 0 or 1 ) a particular update was at. Are you saying there is never an increment for the us996?
Thank you for clarifying
Click to expand...
Click to collapse
Was just pointing out that through the 996 oreo release lg hasn't incremented arb on the 996
Sent from my LG-H910 using XDA Labs
Hi cnjax
It is a bit difficult to read everything n get a clear picture sometimes. I'm hoping you would clarify something
If TWRP is not installed and the phone is unlocked but not rooted which method could be used to install oreo 20f?
Would you be forced to install 10f (nougat) to root and install twrp first before moving on to oreo?
In this scenario I assumed nougat was on the phone originally and it seems the phone is locked from the fastboot info given...but let's say it gets unlocked
Is there a method to install oreo first instead of starting with nougat and version 10f? If there is that would be awesome
Thank you!
secondhand2 said:
Hi cnjax
It is a bit difficult to read everything n get a clear picture sometimes. I'm hoping you would clarify something
If TWRP is not installed and the phone is unlocked but not rooted which method could be used to install oreo 20f?
Would you be forced to install 10f (nougat) to root and install twrp first before moving on to oreo?
In this scenario I assumed nougat was on the phone originally and it seems the phone is locked from the fastboot info given...but let's say it gets unlocked
Is there a method to install oreo first instead of starting with nougat and version 10f? If there is that would be awesome
Thank you!
Click to expand...
Click to collapse
If his bootloader is locked he'll need to downgrade, root and unlock the bootloader with dirty santa, flash updated twrp, flash a rom and magisk
Sent from my LG-H910 using XDA Labs
Post #71 about dumping contents/partitions with lgup seems a good idea -
Then I would try fastboot oem unlock to see what happens but not sure if that can break the bootloader or not. I think you would be in a deeper hole if it went south on you. I'm not sure if doing fastboot oem unlock can be risky at this point
OS - Windows 10 Enterprise N LTSC 64-bit
How I got here:
Rolled back to 2016 build using LGUP (store, patched).
Used dirtysanta to unlock bootloader and install TWRP.
On first boot, I got static and a constant buzz from the haptic feedback motor.
Not knowing that Verizon users sometimes need to wait over 20 minutes, after 10 or so I assumed I was toast.
Tried to flash NotYetADev's Oreo build with the same result. (https://forum.xda-developers.com/v20/development/vs995-verizon-lg-v20-stock-oreo-rooted-t3845669)
Attempted repairs:
Tried LG Flashtool using dksoni411's method (https://forum.xda-developers.com/v20/how-to/guide-lg-v20-to-life-t3827732) and it failed to work.
Now LGUP is not working. Changes between "not recognized" and "wrong DLL" depending upon LHUP_common.dll version.
Uppercut ran after disabling A/V but didn't work and required a system restore to get Windows back to a normal state.
Flashing several alternate kernels doesn't fix.
Flashing LineageOS, same thing.
What's still working:
Download Mode
Fastboot Mode
TWRP
Notes:
I have the original files from the first LGUP dump.
Looking at the build.prop from the TWRP terminal, each flash appears to be successful but still hangs at the LG "Life's good" screen.
I am kind of at a loss as to how to proceed. I have some reservations pushing aboot or any other files via fastboot as I don't want to risk a hardbrick condition. Any assistance would be greatly appreciated. I can spinup a VM if needed to run Uppercut. I am not going down that road again...
Update:
Installed all software, drivers, etc. in a Windows VM. Same results. Uppercut still fails to work with LGUP...
Out of desperation, I flashed bootbackup.img to the device. No change.
Anyone? Anyone? Bueller?
It appears that TWRP is not flashing the system partition even though it is mounted.
Anyone?
You don't need uppercut. Remove it. You need lgup patched working. Do that first. Trial and error I recall with dll file. Just keep trying. Forget virtual machine. If you don't need Verizon firmware you can use US996 and then dirtysanta. Vibrator issue is with verizon firmware only.
Sent from my LGE LG-US996 using XDA Labs
Posting an updated request in another thread as no help is forthcoming here.
if i remember correctly it has to do with dirty santa step 3 where you install twrp and need to type
"adb reboot recovery"? this step almost screwed me over... you actually dont need to wait for vibrate to stop to boot in twrp, wait 5mins then type the adb command, and it will reboot in recovery...
Thanks for the reply.
I got LGUP (patched) working again on a clean virtual machine. My work PC is very loaded with software and I wanted to avoid driver conflicts. Sadly, the original KDZ dated December 2016 that I first flashed won't work now. It throws a "wrong model" error likely caused by my using the LG flash tool and it failing to complete the flash.
It turns out that my file system was hosed but I managed to fix that in TWRP. Rather than try and use fastboot to flash the files individually from the original LGUP dump, I am making a TWRP flashable zip. Hopefully, that will work.
If I can get it back to stock, I am confident that I can get it going. My main screwup was not waiting long enough on the first rooted boot (static screen, and vibrate). I now have a kernel to flash that is supposed to fix that. I have a bad feeling that I will need to revisit the LG Flashtool and correct those errors before anything will be resolved.
More information in an updated thread here:
https://forum.xda-developers.com/v2...anta-bootloader-t3519410/page400#post81065413