[OFFICIAL] LineageOS 18.1 for the LG V20

[nostupidthing]

interesting finding i think what i got is actually us996 (just found out serial no says lgus996...., probably the seller crossflashed to h910 without me knowing)

so when i flash the us996 modem, it boots ok, then i migrate to us996 build and twrp to us996 as well, the screen become a lot of noise/static during boot, which wasn't before

in short
us996 device
h910 los18 rom 20211104 + us996 modem = ok
us996 los18 rom 20220102 + us996 modem = ok but noise/static screen during boot

also in windows explorer even with us996 rom still says LG-h910

 

[AShiningRay]

interesting finding i think what i got is actually us996 (just found out serial no says lgus996...., probably the seller crossflashed to h910 without me knowing)

so when i flash the us996 modem, it boots ok, then i migrate to us996 build and twrp to us996 as well, the screen become a lot of noise/static during boot, which wasn't before

in short
us996 device
h910 los18 rom 20211104 + us996 modem = ok
us996 los18 rom 20220102 + us996 modem = ok but noise/static screen during boot

also in windows explorer even with us996 rom still says LG-h910

That's because other models are unlocked through the engineering bootloader and the DirtySanta(DirtyCOW) exploit, while the us996 can be unlocked officially... Or at least it could a while ago. That exploit makes it necessary that the kernel provides a way around that garbled video during boot on those other models. According to @xxseva44, it's related to the proximity sensor and booting the phone with your finger blocking it "fixes" the screen noise. But since your device is a us996, simply unlocking it officially would be better. But then you can also flash an h910 kernel over that us996 rom and possibly also solve that boot issue.

At the end of the day, it depends on which kind solution you want.

 

[nostupidthing]

ahhh i didn't know that, i though it was a h910 so i unlocked/rooted using the common root method, is there anyway to revert and "officially" unlock it now?

static screen doesn't bother me that much though

wifi instability is more of a problem

ahh i just checked lg has stopped the bootloader unlock service

 

[AShiningRay]

ahhh i didn't know that, i though it was a h910 so i unlocked/rooted using the common root method, is there anyway to revert and "officially" unlock it now?

static screen doesn't bother me that much though

wifi instability is more of a problem

ahh i just checked lg has stopped the bootloader unlock service

Yep, unfortunately they seem to have closed that service, so the best approach you have is using that us996 rom with the modem that works best for you and also a h910 kernel to solve that screen glitch at boot. I don't think the h910 kernel will break things on your us996 since they're basically identical except for that unlock procedure.

 

[nostupidthing]

Yep, unfortunately they seem to have closed that service, so the best approach you have is using that us996 rom with the modem that works best for you and also a h910 kernel to solve that screen glitch at boot. I don't think the h910 kernel will break things on your us996 since they're basically identical except for that unlock procedure.

thanks! probably I'll flash h910 again for the next update... particularly no benefit in flashing us996 except the static screen anyway

 

[nostupidthing]

there is another problem.... twrp, already using latest version, cannot decrypt /data, using pin, any idea?

 

[xxseva44]

there is another problem.... twrp, already using latest version, cannot decrypt /data, using pin, any idea?

Oddly enough you need the really old versions of twrp. I forgot the exact version but it would've been bundled with your root guide. From there, format data and reboot.

 

[nostupidthing]

Oddly enough you need the really old versions of twrp. I forgot the exact version but it would've been bundled with your root guide. From there, format data and reboot.

thanks a lot! so i need to wipe again.... yikes....

one last question for time being, if the device is already bootloader unlocked (which I think so bcs otherwise the seller couldn't have flash h910 rom on it), is it possible to revert to stock and keep the unlocked bootloader? is flashing a stock kdz ok? or if there is anyway to check?

then with unlocked bootloader i can still install twrp and los?

thx alot guys.

 

[xxseva44]

thanks a lot! so i need to wipe again.... yikes....

one last question for time being, if the device is already bootloader unlocked (which I think so bcs otherwise the seller couldn't have flash h910 rom on it), is it possible to revert to stock and keep the unlocked bootloader? is flashing a stock kdz ok? or if there is anyway to check?

then with unlocked bootloader i can still install twrp and los?

thx alot guys.

Well if you want to be on stock, just dont flash a rom on top and flash the patched kernel which would've been with your guide. If they didn't link one, use mk2000. You should already have twrp. Do not flash a kdz, you're basically restoring the software on the phone. If you want stock, use alpha omega, weta, etc, theres a post on the v20 thread which has them linked. And you can use los with the unlocked bootloader.

 

[nostupidthing]

Well if you want to be on stock, just dont flash a rom on top and flash the patched kernel which would've been with your guide. If they didn't link one, use mk2000. You should already have twrp. Do not flash a kdz, you're basically restoring the software on the phone. If you want stock, use alpha omega, weta, etc, theres a post on the v20 thread which has them linked. And you can use los with the unlocked bootloader.

thx a lot

what im thinking is that if i have unlock bootloader then it will be nice to get rid of the red logo during boot right?

but then i just remember, usually bootloader unlock will still give you some kind of warning anyway, so that's a wash.

so probably i'm going to stick with it and just flash los h910

i prefer los to stock

thx!!!

 

[nostupidthing]

umm i just flash back to twrp-3.0.2-1-us996 and format data, then update twrp and install los, then encrypt and set pin

but still cannot decrypt in twrp....

 

[nostupidthing]

ok, i need rest and here is the outstanding issues

1. encrypted phone cannot be decrypted in twrp (tried old and new twrp)
2. wifi unstable
3. gpu driver outdated (cannot run filmic pro)

cheers.

 

[mangokm40]

umm i just flash back to twrp-3.0.2-1-us996 and format data, then update twrp and install los, then encrypt and set pin

but still cannot decrypt in twrp....

Isn't there a newer TWRP here?
https://twrp.me/lg/lgv20us996.html

 

[nostupidthing]

Isn't there a newer TWRP here?
https://twrp.me/lg/lgv20us996.html

cause it was recommended to format data just after root... so i tried again anyway

now i use twrp-3.6.0_9-0, still doesn't work, my lock code is pin, any idea?

 

[nostupidthing]

hi

Same issue with our h910 on current LOS release. I have tried several baseband versions from android 7 but no change. This issue is when WiFi is off or not connected. LTE signal from tower is 4 bars. Speed test is blazing fast. But all apps come to a halt and can't get data to work correct.

Phone calls OK. APN settings OK. I am at a loss as to why data speed test is great but apps not getting data from internet. Yes once in a while they work sporadically but its hit and miss.

Location works using GPS navigating app that has maps saved on phone.

is it ok if we get some logcats for devs to see?

my wifi is working very spordic here... i use wifi mainly, put my phone in airplane mode and enable wifi, but it keeps disconnecting and re-connecting. tried several modem, no improvement...

 

[npjohnson]

hi

is it ok if we get some logcats for devs to see?

my wifi is working very spordic here... i use wifi mainly, put my phone in airplane mode and enable wifi, but it keeps disconnecting and re-connecting. tried several modem, no improvement...

file a bug like the wiki says on gitlab

 

[nostupidthing]

sure... i'm switching back to h910-10r modem for now and see how it goes.

@AShiningRay can you do for the modem? I'll file one for decrypt and gpu driver

TWRP decrypt fail: https://gitlab.com/LineageOS/issues/android/-/issues/4335

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1621

GPU driver outdated: https://gitlab.com/LineageOS/issues/android/-/issues/4336

 

[npjohnson]

sure... i'm switching back to h910-10r modem for now and see how it goes.

@AShiningRay can you do for the modem? I'll file one for decrypt and gpu driver

TWRP decrypt fail: https://gitlab.com/LineageOS/issues/android/-/issues/4335
GPU driver outdated: https://gitlab.com/LineageOS/issues/android/-/issues/4336

TWRP isn't us, the GPU driver one is fine tho

 

[AShiningRay]

sure... i'm switching back to h910-10r modem for now and see how it goes.

@AShiningRay can you do for the modem? I'll file one for decrypt and gpu driver

TWRP decrypt fail: https://gitlab.com/LineageOS/issues/android/-/issues/4335

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1621

GPU driver outdated: https://gitlab.com/LineageOS/issues/android/-/issues/4336

Actually, the modem also isn't handled by lineage nor TWRP, that's on a different partition and relies on the firmware, and is also a proprietary blob that we can't develop directly on, so filing an issue for it doesn't make much sense unless it was for finding a way to circumvent the Wi-Fi/SIM problems, but i hardly think that's caused by lineage code. The only way of "fixing" those, if possible, is by testing lots of modem versions then making a knowledge base about them here on xda, and we also need to take into account the multiple phone variants.

Mine is a h910 and i don't face those connection problems with the modem currently on it for example, but i only tested on 2.4GHz. I'm also on LOS, but that's a custom build that we're using to test the 4.4 kernel, so it isn't exactly the same device tree that's on the official builds.

 

[nostupidthing]

Actually, the modem also isn't handled by lineage nor TWRP, that's on a different partition and relies on the firmware, and is also a proprietary blob that we can't develop directly on, so filing an issue for it doesn't make much sense unless it was for finding a way to circumvent the Wi-Fi/SIM problems, but i hardly think that's caused by lineage code. The only way of "fixing" those, if possible, is by testing lots of modem versions then making a knowledge base about them here on xda, and we also need to take into account the multiple phone variants.

Mine is a h910 and i don't face those connection problems with the modem currently on it for example, but i only tested on 2.4GHz. I'm also on LOS, but that's a custom build that we're using to test the 4.4 kernel, so it isn't exactly the same device tree that's on the official builds.

but on stock it's no problem so i think it's some interaction between kernel and firmware, we may pick one firmware and work on it?

@A.Whit what do u think?