[OFFICIAL] LineageOS 18.1 for the LG V20

[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?

 

[AShiningRay]

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?

It works on stock, and that's exactly the problem. We can deal with the phone's rom and kernel sides, but the firmware is a proprietary blackbox that we have no actual access to, unlike LG with their stock rom to which the firmware was tailor-made to. We can only send things in so that it can send results out, we don't know what it does with the interface code we have on the rom and kernel any deeper than surface level, and surely we can't simply brute-force our way through by testing every possible combination of blobs/kernel configs/firmware version, etc. About using a specific firmware and working around it... that's kinda what @npjohnson is doing by recommending that people use the nougat firmwares on the first few posts. They're the ones that are known to work the best until now, and those proprietary files are also the reason we still don't (and likely will never have) VoLTE and Wi-Fi Calling on the V20's custom roms unless a genius manages to reverse-engineer the frameworks in a way that allows them to work on customs.

I mean, maybe there's a decrypted and "tweakable" firmware out there, but if there is one, i didn't find it yet and messing with those things isn't exactly legal, so the most we can do is work around the firmware with the tools we have, and that's what we're doing.

But here's the thing: Most of my knowledge is on the kernel side of things, if anyone more knowledgeable than me, especially with roms can clear some things up, i'd really appreciate it.

 

[nostupidthing]

It works on stock, and that's exactly the problem. We can deal with the phone's rom and kernel sides, but the firmware is a proprietary blackbox that we have no actual access to, unlike LG with their stock rom to which the firmware was tailor-made to. We can only send things in so that it can send results out, we don't know what it does with the interface code we have on the rom and kernel any deeper than surface level, and surely we can't simply brute-force our way through by testing every possible combination of blobs/kernel configs/firmware version, etc. About using a specific firmware and working around it... that's kinda what @npjohnson is doing by recommending that people use the nougat firmwares on the first few posts. They're the ones that are known to work the best until now, and those proprietary files are also the reason we still don't (and likely will never have) VoLTE and Wi-Fi Calling on the V20's custom roms unless a genius manages to reverse-engineer the frameworks in a way that allows them to work on customs.

I mean, maybe there's a decrypted and "tweakable" firmware out there, but if there is one, i didn't find it yet and messing with those things isn't exactly legal, so the most we can do is work around the firmware with the tools we have, and that's what we're doing.

But here's the thing: Most of my knowledge is on the kernel side of things, if anyone more knowledgeable than me, especially with roms can clear some things up, i'd really appreciate it.

thx!

1. right now h910-10r modem seems to be okish for my wifi only use. not perfect but not too bad...
2. gpu driver await dev to fix thx
3. twrp seems i'm not the only one... https://github.com/TeamWin/android_device_lge_h990/issues

 

[nostupidthing]

deleted

 

[AShiningRay]

umm.... i may have found the culprit... my 2 h910 seem to be generating the same randomized mac addresses nd so when they're both on they keep disconnecting the other from the wifi network....

their device mac are different so i have no idea why they keep generating the same randomized mac address

any idea?

right now, both devices use this randomized mac address D0:13:FD:41:AE:6C, and I cannot find anyway to disable randomization.......

Isn't there a developer option for that? I'm currently on my Redmi Note 4X (My V20 is on a barebones Lighthouse ROM for the time being), and it's LOS18.1 has a "WI-Fi-enhanced MAC randomisation" option in there.

 

[nostupidthing]

deleted