yashsingh1/xdaforums huggingface dataset:
[LG V20 Guides, News, & Discussion] Vortell:
Yes it is possible. You would have to modify the scripts. I'm surprised you can not just unlock f700 directly from lg. No one in the v20 forum is going to do the work for you though. It's a skeleton crew over here. There is better scripts in guide section fyi.
[LG V20 Guides, News, & Discussion] justcosmic:
Any guidance you can provide on this would be great. I have the F800S and have seen advice on XDA to first flash F800L ROM which Ihave done. I tried following the Dirty Santa on this video https://www.youtube.com/watch?v=aNnEe8ExhxA which I think leaves out the "fastboot flash boot bootbackup.img" (Unless that is incuded within one of the bat files too?) - but I still get static every time - and it doesn't go away on boot completion and also wouldn't goback into recovery even though I had successfully flashed TWRP and wiped data...

Ican enter download mode, so my only option has been to re-install stock with LGUP and try again... But it gets confusing because the bootloader has already been opened once....

Going to sleep on it and recharge the phone (process killed the battery very quickly)..
[LG V20 Guides, News, & Discussion] Ms0206:
Hi, after I had many problems with Magisk, fingerprint-sensor and Viper4android, I wiped my mobile in Twrp (factory reset + wiped 'system').

After this, I reinstalled LOS-15.1-20200506-X86CPU-Vs995 and LOS 16-20200505-X86CPU-Vs995, then the actual nightly of 17.1 + OpenGapps (nano).

Now I still have the problem that my fingerprint-sensor crashes and disappears when my battery is charged to 100%...(already asked here)

Any ideas what makes the fingerprint-sensor crash when battery reaches 100%? Its reproduceable. I already tried to uninstall 'digital wellbeing' through ADB before I wiped it, without success, same behaviour.
[LG V20 Guides, News, & Discussion] cnjax:
This has nothing to do with dirty santa, your best option is to consult the Los threads for your issue
[LG V20 Guides, News, & Discussion] Vortell:
That's not necessarily true. Dirtysanta can mess up the bootstack especially this version. That's why I always direct people to the other thread. Plus dirty santa works the same on all models that are vulnerable in my experience. Even when not listed for me the models were Us996 bpt, h915. Either way there are four options:

1. Go to guide section and try to install i95swervin's nougat return in twrp (more history on this and alot about these issues check out alpha omega 8.0 thread)

2.Use lgup to restore correct bootstack. Discussed in lgup/dev lgup/alpha omega 8.0, and what ever the universal lgup program(it just comes with dll files for many models, sorry I forgot the name) is called threads.

3. Use kdz writer in twrp terminal, instructions in some twrp threads.

4. Know fastboot and phone structure well enough to swap out bootstack.

I would use #1 and then lg v20 dev lgup with partial dl mode if the twrp package fails. I am actually not sure if kdzwriter is still built into twrp anymore but it worked well. More instructions in relevant threads. Older los threads should have more info on all of this though as cnjax stated.
[LG V20 Guides, News, & Discussion] Ms0206:
And this could help? I'll read a bit and try this, thx for the info.

The behaviour of my mobile is strange in my opinion as tge fingerprint-sensor always works on first bootup...until I charge it to 100%. I am really wondering whats triggered at 100% battery-level that makes the fingerprint-sensor crash....but as its reproduceable here there must be a problem somewhere...

Edit: Where exactly do I find more information about this? Every Alpha Omega-thread here is closed and shows '404 page not found' / discontinued ☹️

Google also shows nothing regarding 'lgup alpha omega'...before I try around I definately need to read a bit what I have to do.
[LG V20 Guides, News, & Discussion] Vortell:
Honestly probably bootstack curruption it causes seemingly random issues.
[LG V20 Guides, News, & Discussion] Ms0206:
I'll try, LGUP is running...but how? What do I have to do exactly to possibly fix my bootstack / bootloader (?)[MENTION=1795879]Vortell[/MENTION]?

What files are needed, what do I have to do to fix? Do I have to reflash the bootstack from my early KDZ I used in the unlock-process?

For unlocking I've used "US99610f_00_1205.kdz" (to avoid strange vibrating at startup of the 995-model). I assume this possibly could be a reason...so do I have to flash the bootstack from "US99610f_00_1205.kdz"?

Do I have to reinstall everything (Lineage) from scratch after this process? How do I get the bootstack-only at all?

So many questions...
[LG V20 Guides, News, & Discussion] Ms0206:
[MENTION=1795879]Vortell[/MENTION] I definately need more infos...there are many partitions and I've read from 'Steadfast' that the bootstack is not just one partition.

Furthermore I do not want to brick something.

My problem is that if I flash the all partions, I am stuck as a neccessary unlock afterwards for sure would brick my bootstack again.
[LG V20 Guides, News, & Discussion] Vortell:
I haven't looked at lgup in two years+, I told you where to find the info. In threads with the search feature is your best bet. I have not updated to newest los in a while maybe I will double check it. I rarely use the phone now. I would have sold it if not for screen ghosting the v20 is famous for. My Oneplus 6t and moto g7 power are way better phones unless you want video out. Lg support for open source is laughable at best. You can search for bootstack in los threads too. 14.1?
[LG V20 Guides, News, & Discussion] Ms0206:
This really drives me crazy!

Am I the only Vz995-user here having this issue?

Unbelieveable how many lifetime I've lost on this mobile....

I've now started from scratch. See my earlier posts this thread, flashed us996-kdz through LGUP, dirtysanta-unlocked it, then installed Los-x86 15, 16, LOS nightly 17.1.

Without any Gapps (!).

After every flash I checked this f... fingerprint-sensor - nothing. After the whole process and first bootup of LOS 17.1, everything is fine - fingerprint is recognized and working as it should.

Until I charge this goddamn mobile - when it reaches 100%, fingerprint crashes. And it looks as if also the QuadDAC-functionality breaks, not sure as I never used or checked it if it works at all.

@Vortell: if it is the bootstack - why does it work fine after the first bootup? If it really is the bootstack, shouldnt it be 'defect' on first startup, too? How can the bootstack cause a crash when I charge the phone to 100%?

However, I want to figure this out more precise! I am so tired of all this trial and error....can someone please tell me exactly how to catch this bug precise exactly?

I'll do a fresh install and want to get a useful log of the crash - but how exactly? What do I have to do, to see what exactly crashes when I charge the Vs995 and produce a useable bugreport for someone?

Beside the log, if its caused by my "Us996-kdz/LOS-Vs995 cross" - why does fingerprint-sensor work on first startup at all?

Strangest point of all is that everything was fine until some weeks ago the way I did it...I did exactly the same and have had a working sensor for weeks. I do not know what went wrong here, I def need to find out more precise details what is causing this...but how?

I want this terrible sh.. get fixed and a stable mobile/LOS install...who can help me and how can I help?
[LG V20 Guides, News, & Discussion] Ms0206:
Doing further tests: after the fingerprint sensor broke/was gone, I was not able to let it reappear - I did a factory reset, from OS, from Twrp, no success. I wiped Dalvik an cache, no success. I did several reboots, no success.

I started into Twrp again, wiped system, data and internal storage + dalvik, reflashed LOS x86 15,16 and Los17, no success - still no fp-sensor anymore.

I did it again - went into Twrp, wiped everything (System, data, internal and dalvik), reinstalled x86 15,16 and Los 17 - have not wiped Dalvik after this and instead of rebooting, Ive shutted mobile down and pulled the battery out.

After a reboot I am now sitting infront of 17.1 and it asks me to set fingetprint for display?!.

So I am wondering what made it reappear - that I've pulled the battery out or the miss of wiping Dalvik after installing LOS x86 15,16 and current 17.1 ....

However, it is working now until I charge it to 100% and I know how to reproduce everything.

Whats next? Neet a good dev now, telling me how to create a useful log when I charge it to wipe out the problems. Need to figure out max details now to solve the crashing things in the background when I charge to 100%.
[LG V20 Guides, News, & Discussion] Ms0206:
Update: a reboot was fine and without any problems. Charged to 98% and started system trace in dev-options with almost everything marked in hope to see anything when I charge it to 100%...but this time it did not break....mysterious, completely.

I'll watch this and try again tomorrow...it definately crashed many times at charging - I dont know why it not crashed this time after I am prepared.
[LG V20 Guides, News, & Discussion] aRandomFellow123:
Greetings, been reading around and was surprised to see this forum thread is still active since 2016; so thought I would take a shot at asking my question here

I have an LG V20 AT&T model (H910A) that I'm trying to root using the dirty santa method, but I seem to be stuck on step1.sh where "applypatch" doesn't have correct syntax:

$ applypatch /system/bin/atd /storage/emulated/0/dirtysanta

===

usage: applypatch [-b <bonus-file>] <src-file> <tgt-file> <tgt-sha1> <tgt-size> [<src-sha1>:<patch> ...]

or applypatch -c <file> [<sha1> ...]

or applypatch -s <bytes>

or applypatch -l

Filenames may be of the form

MTD:<partition>:<len_1>:<sha1_1>:<len_2>:<sha1_2>:...

to specify reading from or writing to an MTD partition.

this I"m assuming it's because my version of android would need to be downgraded to a version close to this thread's timeframe? Trying to do steps 2 and 3 ahead of time doesn't work because the patch needs to go through

Anyhow... total newbie attempting this; one of the things I'd like to try is this flashing tool: https://xdaforums.com/showthread.php?t=2797190 - haven't tried it yet due to it's age

EDIT: after all the rambling, forgot to properly state the main issues:

* applypatch doesn't work due to syntax differences in the original post on this thread

* would downgrading to a different android version help? How would this be done if I can't fastboot?

* what items are outdated or what would need to change depending on my phone model?

Thanks anyone in advance for reading this - also I'm happy to move this if there's a better spot to ask 😅

Currently on Linux to navigate this, android version is currently 7.0

EDIT:

Welp... I may have just solved my own questions. Ima try this tutorial and see who this goes https://xdaforums.com/t/root-howto-at-t-h910-up-to-v20g-fully-tested.3664500/

Roughly the same deal, but with a firmware downgrade using the tool I was nervous to try. I'll update this after the attempt
[LG V20 Guides, News, & Discussion] aRandomFellow123:
Progress:

followed the new tutorial that rolls back the lgv20 to a 2016 build. Was able to burn through all 3 steps but after the flashing of recovery and boot the lg screen launches and runs forever.

Attempted to flash boot2.img but got a secure boot and subsequent boots caused a kernel crash... something tells me I wasn't supposed to do that :p

tried to do step3 multiple times but the same results happening

Been attempting this all night and no dice. On the bright side the LGUP tool can take me back to the 2016 firmware

EDIT: more progress! made it to the lineage os boot screen, everytime it starts up however there is a kernel crash (modem)
[LG V20 Guides, News, & Discussion] aRandomFellow123:
HOLY COW ITS WORKING; I don't know what went wrong last night, but I tried re-flashing boot1.img and twrp and things are alive and well with lineage os
[LG V20 Guides, News, & Discussion] aRandomFellow123:
Well drat... not sure how to remove this message
[LG V20 Guides, News, & Discussion] Duneflower:
Hmm. I'm pretty sure I've followed the instructions properly, but I can't boot into recovery - static screen despite multiple reboots. System and fastboot are both fine, or at least usable (after covering the sensor, in system's case). RunMeFirst.bat's logcat never displays a bloody thing, forcing me to take an educated guess on the timing for running step2; that's the one thing I'm uncertain on as far as concerns having followed the instructions properly, though I'm reasonably confident I gave it sufficient time to finish everything, particularly since the terminal emulator's prompt had reappeared. When I used step3, fastboot compained "Couldn't parse partition size '0x'." when trying to flash boot, and the same thing when trying to flash either boot1 or boot2 manually; I could be wrong, but this feels like there's something wrong with my copies of those files.
[LG V20 Guides, News, & Discussion] evoblade2000:
Hello, in step 4, it says to run "applypatch /system/bin/atd /storage/emulated/0/dirtysanta"

This command fails because the file /system/bin/atd does not exist on my device. Do you have any suggestions?

I verified this by ls /system/bin and the file atd is not there. And yes, I ran the command from the device.
[LG V20 Guides, News, & Discussion] zfk110:
I flashed this rom on my vs995

https://xdaforums.com/t/vs995-oreo-...-v20-stock-oreo-rooted-flashable-zip.3845669/

it boot it up fine but when I Was trying to upgrade the MAgisk to newer build I got stuck here on this screen, I don't know what to do, and I was trying to get back into TWRP, but I couldn't. Do you know how to get back into it?
[LG V20 Guides, News, & Discussion] Duneflower:
First thing that comes to my mind is that something went wrong with the chmod. Try that command again maybe?
[LG V20 Guides, News, & Discussion] evoblade2000:
Im confused, where is a chmod? In the batch file? My issue is the directions state to patch a file that is not present.

EDIT: it seems you are referring to step1.bat. I will try to re-run the steps manually.
[LG V20 Guides, News, & Discussion] Duneflower:
Almost; I'm referring to (3.5) right after step1 finishes.

run-as con
chmod 0777 /storage/emulated/0/*
[LG V20 Guides, News, & Discussion] Khiraji:
I did about the exact same thing a few hours ago. In my almost 10 years of messing with Android devices I have yet to break one in this manner up until now. Currently trying to re-flash my KDZ.
[LG V20 Guides, News, & Discussion] zfk110:
Don't flash anything, I fixed it this what I did

download TWRP img file according to your model

flash that TWRP in download mode, using adb from your PC then go back to TWRP using Chicken dance and then flash the rom again, with this kernel

here

https://xdaforums.com/t/kernel-ezv2020-kernel-all-varients-pie-oreo-stock.4090779/

dont upgrade the Magisk, also before you come out from TWRP after flashing kernel and rom flash the TWRP in recovery
[LG V20 Guides, News, & Discussion] evoblade2000:
run-as con gets the following output:

run-as: unknown package: con

and im still having the issue with the missing atd file.
[LG V20 Guides, News, & Discussion] Duneflower:
Which firmware version are you running? I was originally on...I think it was 20c and that the same issue until I downgraded to 12a or whatever the 12 one was.
[LG V20 Guides, News, & Discussion] evoblade2000:
When I look at the system update history, it says Software Version VS99520c. So I guess thats the 20c. How can I downgrade?

EDIT: Figured out how to downgrade.https://xdaforums.com/t/uppercut-add-any-lg-device-to-lgup-for-tot-kdz-flashing-g4-g5-g6-v10-v20-more.3511295/page-17#post-77713762
[LG V20 Guides, News, & Discussion] Duneflower:
Lol yep, beat me to it.
[LG V20 Guides, News, & Discussion] Jesus is God Almighty:
Sorry 200 pages just does seem a little overwhelming, does this work with H800K version?

I just got it downgraded to version 7 after getting into issues after installing A9, very very tedious. Thought no problem lets just... wait a minute, why does it now not work. So ended up using hours and hours again to just get that sorted out again.

So... Now that I am downgraded, I am now ready to fix bootloader and root... Or take it on as to say... Will take some more days I'm sure... Reading and learning and trying things out.

But if anyone can make some shortcuts, it would be nice with some info :)

Thanks.
[LG V20 Guides, News, & Discussion] Jesus is God Almighty:
Seems I'm rooted now, used the newbie version or whatever it is called version 6. F800K rooted, although still a long way to get to where I wanna be.... and I might have broken the mobile again for the second time after rooting it.

Just tried to install the newest version of SuperSU or whatever it name, but... seems to be hanging on the screen now :/

Well I guess it was unneeded to install a newer version overall... As long as it works.

I did make a backup, so hopefully I can just restore things although I do not have much experience with that.
[LG V20 Guides, News, & Discussion] Jesus is God Almighty:
How many Kernels exist for this V20 device for A8?
[LG V20 Guides, News, & Discussion] Jesus is God Almighty:
Argh, so wanted to move on, first thing to take a backup of the now rooted A8 system... But... I could not...

I was like, what now? Hmmm... Looking around I witnessed that my drive was now not accessible from TWRP again after having it rooted. Is that normal???

Like the mobile is running without any issues it seems with ROOT, yet just don't have access to my drive from TWRP. HELP!!!

I don't know so much on these things, still pretty newbie... Why would it close the drive again?

If I wanna test out the other Kernels I will then have to do it by restarting all over again, and again one by one. MK2000 beta 14 seems to do a fine job overall as far as I can see - the mobile is snappy and it is rooted. I do wonder if I should just go with that, but... knowing myself... I guess I wanna try out some of the other options.
[LG V20 Guides, News, & Discussion] Jesus is God Almighty:
Seems I have some issues with installing Magisk - seems it wanna have another Boot img to be able to install... Well....
[LG V20 Guides, News, & Discussion] Jesus is God Almighty:
What does the boot.img do? Why does it need to be flashed? Just a newbie question as Magisk seem to not like this new Boot.img that is being installed.
[LG V20 Guides, News, & Discussion] DontReuseUsernames:
No output from DirtySanta in Logcat. Only this. Why?! Can't reboot into fastboot mode either. Is there another root method? LAF? Edit the KDZ?:

01-01 14:57:46.922 7114 7117 I exploit : [*] /proc/self/mem 1367343104 1048576
01-01 14:57:46.922 7114 7114 I exploit : [*] exploited 0x7c997b7000=10102464c457f
[LG V20 Guides, News, & Discussion] DontReuseUsernames:
Jesus:

The aboot.img replaces the boot image on the phone. This is part of the rooting. It's an altered bootloader that is part of the rooting. However, it often seems to leave people with a static screen.
[LG V20 Guides, News, & Discussion] wayase8080:
For some reason the step3.sh had a miss-typed boot1.img on the 16th line and I'm a retard and didn't notice it. Now my phone has the same static screen that many have encountered in this thread already whenever I shut it down completely or restart it, I also can't use adb nor fastboot from my computer, because the phone keeps connecting and disconnecting. And I also can't copy the files manually from the phone because I don't have root privileges. "id" in the terminal emulator still shows "untrusted app". Any help would be very much appreciated.
[LG V20 Guides, News, & Discussion] DontReuseUsernames:
Try covering the light sensor and report back.

I can't get into fastboot. I think aboot.img is copied and I have a root prompt via run-as con but the new boot.img isn't actually being applied to the boot partition. It would be good to know for sure if it's being applied. No info about this in logcat. Just ....etc..exploited.

I've been trying to get this working for a year now with 3 phones. It's quite annoying.
[LG V20 Guides, News, & Discussion] wayase8080:
I'm glad this thread is still active. I managed to get that particular problem working yesterday, but ran into some more problems along the road. First, I tried to flash Magisk and then SuperSU with both running in the same error as: https://xdaforums.com/attachments/img_20210120_010234-jpg.5192927/

So I tried to flash a Rom to it without root privileges, since it should theoretically work as the boot loader is already unlocked, but that didn't work as expected... Right now I'm stuck where the phone has English warning message instead of the Korean one, but it vibrates all the time and doesn't boot anywhere, all you can see is a very dim circle that smoothly flashes on and off every 2-3 seconds. When I try to "Chicken dance" into TWRP (Vol -, then Power for 2s and Power again.) It takes me to the White screen to erase stuff, and then (I'm assuming the same) circle appears, but this time it is pulsating in and out with small colorful waves around it and a bottom text saying "Erasing", after that the same thing happens... dim circle that smoothly flashes on and off every 2-3 seconds. I tried to leave it on for at least 35-40 minutes with no change. I'll try to flash TWRP from Download mode and see if that helps anything, or is even possible and report back, I still have hope that it is fixable.
[LG V20 Guides, News, & Discussion] wayase8080:
Alright, I think I "fixed" it. I flashed TWRP in Download mode, first the old version mentioned in The guide, but that one couldn't flash Lineage with either an Error 7 or Could not find META-INF/com/google/android/update-binary when I deleted the assert lines. Then I installed the 3.3... version for US996, and "successfully" installed Lineage, but got a Kernel crash at the boot-up, I think installing a different kernel will fix it, but I'm not sure if I need root access or not to do that, I'm also not sure which one to install, but I think I'll go with the Gamma Kernel.
[LG V20 Guides, News, & Discussion] wayase8080:
Well, I tried version 15, 16, 17 of LineageOS, with either a gamma kernel, or the ezv2020 kernel, none of which solved the problem. I'll keep looking for any potential solutions, but for now I'm requesting help here, it would be very much appreciated. I'm also not sure if I unlocked the boot loader properly, but in the boot loader it says that it is "unlocked: yes", but whenever I power the device on, I get the red triangle warning, even though in the original guide in this thread it said it's normal, I heard somewhere that it should show a yellow/orange triangle instead.
[LG V20 Guides, News, & Discussion] wayase8080:
Alright, after a bunch of kernel modifying and re-compiling, I've got it solved... I think. I played with a bunch of modem.imgs and while none of them helped, flashing and re flashing different modified kernels did, right now I've settled on "gamma-kernel-SS-2018-09-13-us996" with custom band modifiers, and successfully booted into Lineage 17.1 for 996, but the phone is far from ideal right now. The camera, 5GHz wifi, flashlight, DAC, proximity sensor, fingerprint sensor, and a bunch of other things do not work, the phone isn't even able to play a HVEC encoded 720p video file. But I believe it is fixable and not relevant to this thread. So thank you, DontReuseUsernames, for the tip of covering the light sensor and temporarily fixing the Static screen, without that I might not have gotten where I am now. And thanks to everyone in this thread for putting so much work into this exploit.
[LG V20 Guides, News, & Discussion] dunawayk:
When I download the v20-root.zip file, it's identified as a trojan by my browser and Windows antivirus- https://www.androidfilehost.com/?fid=457095661767122821

Anyone know where I can find a good copy?