Database Users

LG Flash tools detected wrong Model

Hey, guys Im trying to flash my my lg g2 sprint edition back to stock using the lg flash tool. I downloaded the sprint tot and dll and when it says flashing on the lg flash tools it brings up and error that says wrong dll or model, I looked at the model it detected and it says my sprint g2 was a d801.
How do i fix this?
Thanks.

Still need your help guys

Theboss1242 said:
Still need your help guys
Click to expand...
Click to collapse
same issue,
try to replace the dll file with this one:
http://forum.xda-developers.com/attachment.php?attachmentid=2553245&d=1391282521
good luck

Theboss1242 said:
Still need your help guys
Click to expand...
Click to collapse
What rom is your phone currently using right now?

Thank guys I got it to work using the dll. !!

Theboss1242 said:
Thank guys I got it to work using the dll. !!
Click to expand...
Click to collapse
do you think this dll would work for my at&t lg g2 that thinks its the d802 version??

afrojoc said:
do you think this dll would work for my at&t lg g2 that thinks its the d802 version??
Click to expand...
Click to collapse
i don't know, it worked for my ls980 with a d802 firmware

Alexandercat said:
i don't know, it worked for my ls980 with a d802 firmware
Click to expand...
Click to collapse
where did you get the dll?
OMG ITS WORKING!!!!!!

afrojoc said:
where did you get the dll?
OMG ITS WORKING!!!!!!
Click to expand...
Click to collapse
nice to know :good:

Please Help
I have the same issue. Flashtool thinks my phone is a D801. It boots normally for a few seconds and keep rebooting. Im Reading, dowloading and trying every method around since yesterday afternoon with no luck. I did replace the .dll you provided but i have a different error now, something like mismatch different files and it shows both files names. I just got this phone from a friend. it shows d801 tmo versión in flashtool so i think he was messing around with any tmo based rom (if exits). So flashtool does not let me flash the phone because of this(Think this is a 801 tmo)
I also tried lg suppor tool but it never download the firmware. It get stuck on downloading firmware or checking phone settings (something like that), I found my cell model on the back on the phone so im pretty sure is a SL980. So what comboof files i can use? Do i still can use the.dll provided? Do i have to rename something?(btw...i did and didnt work).
Any other tip? Did i miss something? I have no phone now so im kinda desperate. Thanks in advance for any help.
Sorry for any mistake, english is not my first language.

I will try ti explain you later what i did to fix this issue
Cant you go in fastboot mode?
Sent from my LG-D801 using xda app-developers app

Alexandercat said:
I will try ti explain you later what i did to fix this issue
Cant you go in fastboot mode?
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
No...how can i do it? i read pressing vol+ while connecting usb but i get to dowload. I know in fastboot i can flas img to phone but i cant get in to it

ToledoG28 said:
No...how can i do it? i read pressing vol+ while connecting usb but i get to dowload. I know in fastboot i can flas img to phone but i cant get in to it
Click to expand...
Click to collapse
ok this is what i did to unbrick my phone in your same conditions, in some steps maybe i made some mistakes but i went to the fastboot mode and there i replaced all kernel files of ls980 to fix the issue:
first you have to proceed to back to stock your phone with the T-Mobile USA D80110C_1.kdz :
http://forum.xda-developers.com/showthread.php?t=2432476
now your phone is a full d801, it will boot the system but will be unstable, you must be fast to go to make the developer options and debug your phone, make it on plane and and charging mode, maybe you will be able to do it after some reboots, u must insist.
download the ioroot11 program to root your device, remember always that is unstable, your device will be recognized for not long time, so you have to open the ioroot program often until it recognize your device and root it with the program.
after this step, if your phone is rooted but is still too much ustable to use the adb command (i tried to sideload and push the recovery but it always made me a sideload error), download this program:
http://forum.xda-developers.com/showthread.php?t=2633941
is a simple tool to flash the recovery, it worked in my case, you have to install the recovery of the d801, in my case the philz recovery worked, if everything will be right, you will flash the recovery.
When i was inside the recovery i tried to flash the justin sprint t mobile through the sideload command but it didn't work, same with cm11, i flashed the ls980twrp.zip and when i tried to go to recovery again i was in fastboot.
from fastboot i used the command fastboot erase to erase the partitions: aboot, boot, dbi,laf,misc, persist, recovery, rpm, sbl1, tz.
to erase you must use the command fastboot erase aboot aboot for example, to erase the boot you must repeat boot(fastboot erase boot boot) and so on.
after erased all files i flashed the partitions of ls980:
http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zv7_partitions
cmd fastboot flash aboot aboot and so on, (i didn't flashed the primaryGPT).
when i flashed all these files i pushed power volume+ and i was in upgrade firmware, so i went back to stock with zv7tot and dll..
it wasn't simple to find a way to back to stock, i guess to made some mistakes but i fixed my issue in this way, i am responsible of what i do with my phone, i cannot guarantee the same results with the others

Alexandercat said:
ok this is what i did to unbrick my phone in your same conditions, in some steps maybe i made some mistakes but i went to the fastboot mode and there i replaced all kernel files of ls980 to fix the issue:
first you have to proceed to back to stock your phone with the T-Mobile USA D80110C_1.kdz :
http://forum.xda-developers.com/showthread.php?t=2432476
now your phone is a full d801, it will boot the system but will be unstable, you must be fast to go to make the developer options and debug your phone, make it on plane and and charging mode, maybe you will be able to do it after some reboots, u must insist.
download the ioroot11 program to root your device, remember always that is unstable, your device will be recognized for not long time, so you have to open the ioroot program often until it recognize your device and root it with the program.
after this step, if your phone is rooted but is still too much ustable to use the adb command (i tried to sideload and push the recovery but it always made me a sideload error), download this program:
http://forum.xda-developers.com/showthread.php?t=2633941
is a simple tool to flash the recovery, it worked in my case, you have to install the recovery of the d801, in my case the philz recovery worked, if everything will be right, you will flash the recovery.
When i was inside the recovery i tried to flash the justin sprint t mobile through the sideload command but it didn't work, same with cm11, i flashed the ls980twrp.zip and when i tried to go to recovery again i was in fastboot.
from fastboot i used the command fastboot erase to erase the partitions: aboot, boot, dbi,laf,misc, persist, recovery, rpm, sbl1, tz.
to erase you must use the command fastboot erase aboot aboot for example, to erase the boot you must repeat boot(fastboot erase boot boot) and so on.
after erased all files i flashed the partitions of ls980:
http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zv7_partitions
cmd fastboot flash aboot aboot and so on, (i didn't flashed the primaryGPT).
when i flashed all these files i pushed power volume+ and i was in upgrade firmware, so i went back to stock with zv7tot and dll..
it wasn't simple to find a way to back to stock, i guess to made some mistakes but i fixed my issue in this way, i am responsible of what i do with my phone, i cannot guarantee the same results with the others
Click to expand...
Click to collapse
ok...i will try that...i was able to flash twrp and get to recovery

ToledoG28 said:
ok...i will try that...i was able to flash twrp and get to recovery
Click to expand...
Click to collapse
if you can go to twrp you can flash with adb, i wasn't able to go in recovery, just download with the d801 firmware, that explains why it was complicated

Thanks for all your help. I was able to erase everything via fastboot and my phone fell down and power off before flashing img and now is dead. I have a big blue pitbull inside the house who makes the disaster.,.lol. i just got one white from a friend for $160. Im sure this thread can help any people with a brick device. Thanks again.
Sent from my unknown using xda premium

Pity, dogs like smartphones :/
Inviato dal mio LG-LS980 utilizzando Tapatalk

but i get no adb?
what ToledoG28 said is exactly what I have been attempting to do to correct this issue but I am facing an additional issue. I had got to the point where I am running the d800 version on my ls980 and it is unstable as you said. I believed I had found a way out but when I connect to the computer no matter what I do I get no adb for no reason as far as I can tell.
makes no sense at all to me as I had adb before all this perfectly fine.

try this
boxorandyos said:
what ToledoG28 said is exactly what I have been attempting to do to correct this issue but I am facing an additional issue. I had got to the point where I am running the d800 version on my ls980 and it is unstable as you said. I believed I had found a way out but when I connect to the computer no matter what I do I get no adb for no reason as far as I can tell.
makes no sense at all to me as I had adb before all this perfectly fine.
Click to expand...
Click to collapse
you gotta go do device drivers and your device will show up as some unknown device so you install the adb devices for your phone and then you should get adb to show.

Alexandercat said:
same issue,
try to replace the dll file with this one:
http://forum.xda-developers.com/attachment.php?attachmentid=2553245&d=1391282521
good luck
Click to expand...
Click to collapse
The magic dll, worked for me d802 A very big thanks to you man. I spend hours trying to fix it all it needed was a magic dll from a MagicMan. Thank you again million times.

[Q]LG G2 re-flashing or rooting stock 4.4.2 bad rom

Hi all,
First off I've tried now for a two days to solve this, reading as much as I could find on here and the rest of the internet.
I decided to root my LG D802 running 4.2 and install CWM recovery no problem. Next I flashed a stock 4.4.2 vodaphone img. All went well untill i tried to use the touch screen, which shows that when i press on one point on the screen it selects multiple points basically its unusable and unable to do almost anything with it, however i have managed to turn on ADB and connect to the phone. So now i have a stock recovery and an unusable ROM.
So next up I tried to rooting it since I had ADB shell working ok, using the IOROOT25. This appears to work as when it reboots and installs the kkroot.zip in the recovery it's saying it worked. Now when I reboot and open ADB shell then type SU to get root I can't press ok when superuser pops up to asking me to give it permission, because of the touch screen problem.
If i can get root in ADB then remount the files system then i will be able to DD a new recovery img??
After getting this far and loosing, I then found this: http://forum.xda-developers.com/showthread.php?t=2432476 on flashing to stock, but the program crashes every time it's about to flash, so i tried doing a fresh install of windows 7 and then tried windows 8 however the program still crashes every time and yes I have followed the instructions and tried the manual method and checking the 127.0.0.0. lgblahblah is there
So no I am turning to you guys for help.
phone details;
Model: D802 32GB
Firmware operator: VDF
sw version: D80220a
ro.build.fingerprint: lge/g2_vdf_com/g2:4.4.2/KOT49I.D80220a/D80220a.1392133741:user/release-keys
Recovery: <3e> KOT49I.D80220a test-keys

UPADATE: I have root but getting this error when trying to flash the recovery:
+] loki_flash v2.0
[-] Loki aboot version does not match device.
any ideas?
Ok so i found a different aboot img pushed to the phone and flashed that using dd
Code:
dd if=/data/local/tmp/about.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
this solved the problem above and a allowed me to flash cwm recovery. This then broke the installed rom so it wouldn't boot. now I had a custom recovery i flashed a EUR open 16gb stock zip this all went well and now i have a working phone What i should of done is remove the stock recovery.img from the zip and the line to flash it in the update script so it didn't flash the stock recovery.
This now leaves me with the loki flash problem above when trying to flash a custom recovery i could flash a different aboot.img but i don't want to break the current rom.
Any one else found a way to solve this problem?

need help
need help please!!
i have pretty much the same as your first problem, i installed the vodafone kitkat and the touch went crazy
and the custom recovery was deleted
and the lg support tool doesnt work for me
i dont know what to do.
sorry i forgot to mention that my phone is lg g2 d802 16 GB

Mustafa1 said:
need help please!!
i have pretty much the same as your first problem, i installed the vodafone kitkat and the touch went crazy
and the custom recovery was deleted
and the lg support tool doesnt work for me
i dont know what to do.
sorry i forgot to mention that my phone is lg g2 d802 16 GB
Click to expand...
Click to collapse
Have you tried running IO root to again root on your device? Also do you know much about linux, command line and android tools like ADB? Or do I need to explain the commands step by step?

twon23 said:
Have you tried running IO root to again root on your device? Also do you know much about linux, command line and android tools like ADB? Or do I need to explain the commands step by step?
Click to expand...
Click to collapse
i downloaded ioroot25 and extracted it and ran root.bat
Looking for device...
Make sure drivers are installed. Check Windows Device Manager.
Make sure proper USB Debugging mode is enabled.
Verizon users make sure ethernet mode is selected.
Did you check phone screen for Yes/No prompt?
(select checkbox to always remember then hit yes)
...sometimes you need to unplug the USB cable then re-plug.
Determining device model...
Rebooting into stock recovery...
When recovery loads, select: *apply update from adb* with power button...
then press Enter/Return on your keyboard.
Press any key to continue . . .
(here the phone restarts and LG logo appears with (secure booting error)message in the upper left corner, and when i press any key)
Reboot back into System after flash in recovery finishes.
Press any key to continue . . .
and when pressing any key the cmd closes and the phone stays on with black screen and the back light on
in the pc i get many windows about formating drives (from H to S)
and i dont know anything about linux or command line
would you explain it to me??

Ok so your phone not longer boots, correct? Do you know what build/version plus any other details of the rom you flashed? or even a link so i can have a look at the rom you have installed. Can you get into recovery mode and is it still a stock recovery image? also what is your phone d802? 16gb 32gb?

Mustafa1 said:
i downloaded ioroot25 and extracted it and ran root.bat
Looking for device...
Make sure drivers are installed. Check Windows Device Manager.
Make sure proper USB Debugging mode is enabled.
Verizon users make sure ethernet mode is selected.
Did you check phone screen for Yes/No prompt?
(select checkbox to always remember then hit yes)
...sometimes you need to unplug the USB cable then re-plug.
Determining device model...
Rebooting into stock recovery...
When recovery loads, select: *apply update from adb* with power button...
then press Enter/Return on your keyboard.
Press any key to continue . . .
(here the phone restarts and LG logo appears with (secure booting error)message in the upper left corner, and when i press any key)
Reboot back into System after flash in recovery finishes.
Press any key to continue . . .
and when pressing any key the cmd closes and the phone stays on with black screen and the back light on
in the pc i get many windows about formating drives (from H to S)
and i dont know anything about linux or command line
would you explain it to me??
Click to expand...
Click to collapse
If you're running root.bat as an admin, try executing it without admin privileges. Dunno why, but it seemed to work for me.

Mustafa1 said:
need help please!!
i have pretty much the same as your first problem, i installed the vodafone kitkat and the touch went crazy
and the custom recovery was deleted
and the lg support tool doesnt work for me
i dont know what to do.
sorry i forgot to mention that my phone is lg g2 d802 16 GB
Click to expand...
Click to collapse
Did you try to flash CWM recovery? http://forum.xda-developers.com/showthread.php?t=2582142 This thread has What you need to do .. After then you can nandroid backup after then wipe everything except EFS on twrp after that you can stock_kitkat.zip on the xda forum. Efter that restore data via twrp.
I think that It will be correct without deleting your current rom ...
---------- Post added at 06:18 PM ---------- Previous post was at 06:12 PM ----------
makgun said:
Did you try to flash CWM recovery? http://forum.xda-developers.com/showthread.php?t=2582142 This thread has What you need to do .. After then you can nandroid backup after then wipe everything except EFS on twrp after that you can stock_kitkat.zip on the xda forum. Efter that restore data via twrp.
I think that It will be correct without deleting your current rom ...
Click to expand...
Click to collapse
NOT CWM , it is TWRP
Are you from turkey?

twon23 said:
UPADATE: I have root but getting this error when trying to flash the recovery:
+] loki_flash v2.0
[-] Loki aboot version does not match device.
any ideas?
Ok so i found a different aboot img pushed to the phone and flashed that using dd
Code:
dd if=/data/local/tmp/about.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
this solved the problem above and a allowed me to flash cwm recovery. This then broke the installed rom so it wouldn't boot. now I had a custom recovery i flashed a EUR open 16gb stock zip this all went well and now i have a working phone What i should of done is remove the stock recovery.img from the zip and the line to flash it in the update script so it didn't flash the stock recovery.
This now leaves me with the loki flash problem above when trying to flash a custom recovery i could flash a different aboot.img but i don't want to break the current rom.
Any one else found a way to solve this problem?
Click to expand...
Click to collapse
Hi! I've recently flashed an updated stock ROM and have the same Touchscreen issue as yourself! Can you tell me the steps you have done to fix it? I'm using windows 8.1 to flash etc, and using a stock ROM I can't seem to get it to work again

How to fix very bricked LG V20 from bad rooting?

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.

Please help me restore back my original LGUP dump! (H910)

I tried to use the dirtysanta method to root my H910. Here is what I did:
1. Because I have the April 2017 security patch, I used LGUP to load up an kdz that is on Dec 2016.
This step was successful. Everything worked as expected.
2. Then I followed the dirtysanta approach, and everything worked great. I got into TWRP and wiped stuff as instructed.
3. However, at the last step, when the instruction says to adb fastboot into recovery, instead of booting back into TWRP, the phone boot into strange screen with stripes, and after a while it will show me a "kernel crash!" screen with a lot of text.
Question - is there any way to get my phone back? I cannot get into TWRP, and there is no more ADB. I also tried LGUP but it lists my phone under "unknown" model and I cannot select it.
Please anyone help me. Thanks!

zhangla said:
I tried to use the dirtysanta method to root my H910. Here is what I did:
1. Because I have the April 2017 security patch, I used LGUP to load up an kdz that is on Dec 2016.
This step was successful. Everything worked as expected.
2. Then I followed the dirtysanta approach, and everything worked great. I got into TWRP and wiped stuff as instructed.
3. However, at the last step, when the instruction says to adb fastboot into recovery, instead of booting back into TWRP, the phone boot into strange screen with stripes, and after a while it will show me a "kernel crash!" screen with a lot of text.
Question - is there any way to get my phone back? I cannot get into TWRP, and there is no more ADB. I also tried LGUP but it lists my phone under "unknown" model and I cannot select it.
Please anyone help me. Thanks!
Click to expand...
Click to collapse
Obviously you did not do enough reading on the ds root process because then you'd know static on boot is normal and you would have read about the button combo to get into twrp. I suggest you do some more reading
Sent from my LG-H910 using XDA Labs

I admit I did not read the thread fully, because it has about 2000+ posts on several hundreds of pages...
I did read the OP's instructions very carefully, and followed it word by word.
Right now, I could get into fastboot and flash TWRP again. That can get me into TWRP but any ROM I flash (either stock based, or custom ROMs), the phone will simply just get back into the static stripes and eventually crash on kernel or modem.
Is this because I should not use H910 ROMs anymore, because the DS uses other models kernels? 996?

zhangla said:
I admit I did not read the thread fully, because it has about 2000+ posts on several hundreds of pages...
I did read the OP's instructions very carefully, and followed it word by word.
Right now, I could get into fastboot and flash TWRP again. That can get me into TWRP but any ROM I flash (either stock based, or custom ROMs), the phone will simply just get back into the static stripes and eventually crash on kernel or modem.
Is this because I should not use H910 ROMs anymore, because the DS uses other models kernels? 996?
Click to expand...
Click to collapse
Flash whatever rom you want/can and then after flash preferably the mk2000 kernel (your varient) right after initial flash of rom-then reboot. Static will vanish like tacos on fat Tuesday. You can then do whatever.

Mysticblaze347 said:
Flash whatever rom you want/can and then after flash preferably the mk2000 kernel (your varient) right after initial flash of rom-then reboot. Static will vanish like tacos on fat Tuesday. You can then do whatever.
Click to expand...
Click to collapse
My problem now is that I can no longer boot into TWRP anymore.... I had recovery-twrp-h910-2018-10-18.img flashed and worked fine, but after I flashed the H910 Oreo stock rom, vol- and power then power, yes and yes to factory reset, the phone just boots into statics then LG then statics then the initial setup wizard. No more TWRP.
Trying to use fastboot to flash TWRP again, but now my phone can only be seen by adb under MTP mode, not when it's in fastboot mode.
Any way to flash TWRP when I am in regular MTP mode (e.g. regular adb)?

zhangla said:
My problem now is that I can no longer boot into TWRP anymore.... I had recovery-twrp-h910-2018-10-18.img flashed and worked fine, but after I flashed the H910 Oreo stock rom, vol- and power then power, yes and yes to factory reset, the phone just boots into statics then LG then statics then the initial setup wizard. No more TWRP.
Trying to use fastboot to flash TWRP again, but now my phone can only be seen by adb under MTP mode, not when it's in fastboot mode.
Any way to flash TWRP when I am in regular MTP mode (e.g. regular adb)?
Click to expand...
Click to collapse
I believe that via adb you can type "push" then type your directed file area of located file (twrp). Double check with google search on how push files via adb
Yeah for some odd reason adb reads via mtp (or photo transfer) only for some reason.

Mysticblaze347 said:
I believe that via adb you can type "push" then type your directed file area of located file (twrp). Double check with google search on how push files via adb
Yeah for some odd reason adb reads via mtp (or photo transfer) only for some reason.
Click to expand...
Click to collapse
The push command is to send files to external SD card while in recovery mode. I did that once. I don't think it actually flashes anything...

zhangla said:
The push command is to send files to external SD card while in recovery mode. I did that once. I don't think it actually flashes anything...
Click to expand...
Click to collapse
Might just have to redo Dirty Santa again...I really dont know what else other than researching ADB commands.
Im assuming that you already tried manual boot in twrp as Cnjax stated. Look into those as well. Different models sometimes have different button combos.

@zhangla
You best slow down and do more reading
You made another mistake
I had recovery-twrp-h910-2018-10-18.img flashed and worked fine, but after I flashed the H910 Oreo stock rom
Click to expand...
Click to collapse
The Oreo stock rom is Stock and flashes Stock recovery and removed TWRP.
Their are two v20 rooted Oreo h910 roms
you needed to use those.
You now need to start over by flashing the h915 nougat kdz and following the root guide
https://r.tapatalk.com/shareLink?ur...share_tid=3664500&share_fid=3793&share_type=t
[ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED)
Sent from my PH-1 using Tapatalk

LG VS995 Only boots to LG screen and vibrates -- Help needed please

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