yashsingh1/xdaforums huggingface dataset:
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] andruyd:
Another important thing is to download the right KDZ image. This is what I used for H990N (https://lg-firmwares.com/downloads-file/4065/H990N10b_00_OPEN_HK_DS_OP_1017)
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] andruyd:
Since the video is for H910, you have to pay attention to the steps where it's talking about H910 because you're going to need to replace that with H990N specific files. The key is using the right files for your device.

If you're nervous at all and about to **** your pants while attempting this, don't do it LOL. Better to be stock than bricked.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] dilligaf56:
18.1 worked fine on my US996, except for fingerprint sensor, so I did a TWRP backup (was on the 2021-04-29 nightly), then flashed Nougat (10n) KDZ and re-rooted. All good; phone booted into stock rooted Nougat fine. Re-booted to TWRP, wiped, restored my 18.1 setup and Magisk 23.0, then dirty-flashed the 2021-05-13 update. It boots up fine, but I can't unlock the phone (PIN won't work). Is there a default PIN on Lineage? Another way to remove the PIN lock? Or do I have to start over with a clean flash of the new ROM?

Maybe wipe, restore previous setup (2021-04-29) again, remove PIN lock, then dirty flash?

TIA!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] dilligaf56:
Tried the last (wiped, restored /system, /data, and cache from my backup). PIN still doesn't work. Do I need to restore another partition to fix it?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Lithianicwashere:
Sadly, i didnt. My lcd screen burn (the flex cable damaged. Its a used phone i bought. Just got the part today. Will assemble & test first). I see u made a guide. I'll follow urs then give my feedback. I never tried gcam tho.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] bhupatib:
I don't know if this has been mentioned already, but I'll share just in case... The easiest way to downgrade to Nougat safely without locking the bootloader is by flashing this modified h918-10u (forgot the original thread, this is my personal copy) in TWRP.

H91810u.zip

drive.google.com

So wipe data+cache+system, flash this, wipe again, optional: update twrp to 3.5.2 (change from zip to img flash method) and flash lineage. For some reason you won't be able to flash magisk at this point so just reboot, install the latest magisk and rename apk to zip and try flashing again. Also, during setup, lineage will ask to update recovery, say no (TWRP is better!). Double check by going to system updater, preference and disable update recovery there as well.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] ssurell:
You may have not had a PIN previously, but it sounds like your backup /data was encrypted. A big headache. You may get access if you can restore the matching partitions, which may include /firmware but most certainly /boot...i don't know. I'd also have TWRP up to 3.5.1_9-0

See this post for a possible solution for you:

https://xdaforums.com/t/universal-dm-verity-forceencrypt-disk-quota-disabler-11-2-2020.3817389/

Attached here is a .zip I pulled from our V20 forum that may work. I've flashed both from recovery with no issues.

Bottom line:

Any new system >=Oreo with encryption by default, I flash a decryption disabler and check security settings after first boot, and if it's still encrypted: Hard Pass
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] andruyd:
I didn't know gcam needed something else to work that was originally part of gapps. You can either install gapps or this https://github.com/lukaspieper/Gcam-Services-Provider to make gcam work.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] dilligaf56:
Thanks! Much appreciated! Will take a look at it soon (long thread!).

Luckily, this is my second (backup) US996 phone (my daily driver is still running rooted stock Oreo), so it's not urgent - but I will eventually wind up using the Lineage phone as the primary if everything works well on it.

I had already tried restoring /boot from the backup - no joy.

When I clean-flashed the latest version - all looks good.

Already on TWRP 3.5.1_9-0.

Will try re-restoring my backup and try your .zip file and let you know how it works when I get a chance. WIll be busy for the next couple of days.

Again, many thanks!!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] ssurell:
So no MicroG ie signature spoofing on official 18.1 is so aggravating. Tried force system NanoDroid patcher and with Magisk. Tried Magisk MicroG module, and even fooled with smali/baksmali system framwork modding with no luck getting signature spoofing so far. Haystack looks promising, so will report back.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] dilligaf56:
@ssurell:

Neither one of the .zips was able to unlock my old backup (04-30), but using yours on the latest clean flash DID prevent it from becoming locked - I was able to back up and restore the 05-13 version, with a PIN lock, then unlock it after the restore with no issues. The prior setup (04-30) DID have a PIN in place before being backed up.

SO, it appears that the answer is installing one of the .zip files immediately after clean-flashing a ROM - this prevents the issue.

Thanks again!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] ssurell:
Since the threads are gone or links dead to the old standards, here's a link to Oreo-Nougat downgrade zip, the legendary AO Nougat ROM, and companion AO Oreo update.

LG V20 - Google Drive

drive.google.com

These zips are a bloated way to move up or down 10p or 20f firmware before installing LOS.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] npjohnson:
Means your download was bad - hence why it panicked. Redownload LineageOS/Gapps.

No, it will boot-loop.

Just format data and set it back up, all should work fine!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] dennnnnnnis:
Can anyone tell me how to get pass safetynet?

Installed magiskhide prop config & universal safetynet fix to no avail

But otherwise Running great on 990n💪
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] ugoplatamia:
Redownloaded LineageOS + Gapps and it's still giving me error 1. Tried using TWRP versions and if it installs, it kernel panics on boot.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] npjohnson:
What does "Error 1" say, nothing more than error 1?

Are you verifying the sha256 checksum on download?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] ugoplatamia:
I verified the checksum after the download is done with 7-Zip's sha256 checksum function. And yeah nothing more than error 1. I can get it to install if I use a higher TWRP version but I get a kernel panic similar to the screenshot I posted earlier.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] npjohnson:
what firmware is your device on? What stock ROM was installed before starting?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] ugoplatamia:
It was on android 7 with the Oct/Nov patch iirc.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] pavik62:
Статус 1 - этот код ошибки произошел из-за того, что были установлены неверные пути монтирования разделов.

Заходим в папку TWRP. Удалите файл twrp и перезагрузитесь в рекавери. Настроить TWRP. Также перед установкой ПЗУ смонтируйте систему, производитель.

Вы все еще можете скачать ROM
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] ugoplatamia:
EN Translation:

Status 1 - this error code occurred because the wrong partition mount paths were set.

Go to the TWRP folder. Delete the twrp file and reboot into the recovery. Set up TWRP. Also, before installing the ROM, mount the system, manufacturer.

You can still download the ROM.

How do I setup TWRP?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] aCIDsLAM:
I have question, which a developer may can answer to me.

As i mentioned, i am only able to decrypt my crypted data partition in LOS16, when using LOS 17 or 18.1 it wont decrypt and TWRP and is not mountable or i am not able to do a backup.

Now the question. When i have a LOS 18.1 with a crypted data partition and i dirty flash over the system partiton with an LOS 16 image and reboot into recovery, i can mount and decrpt the same data partiton in TWRP, which i could when having a LOS 18.1 system image on the phone.

What does this say to me. Are there files in LOS 18.1 missing, which prevents encryption or is it a TWRP issue?

This behaivor is kinda strange and i normally wouldnt expect that.

Under 18.1 i get the info, some files under system/data/vold are missing?!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Gorilla Daddy:
Hi, the last official versions of 17.1 Lineage Miracast started working. There is a Qualcomm WFD driver included with LineageOS 18 official for LG V20. Can we find whomever got wireless display working on 17.1? He'd probably be able to fix whatever isn't working with that on Lineage 18.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] npjohnson:
We would need newer msm8996 blobs, which we may never get.

Msm8998 just barely found compat blobs.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] hamid_valad:
huh. it's been a while.

I'm using the unofficial build and oh my GOOOOD it became frustrating. crashing. overheating. worst GPS ever (even worse than old Symbian phones I had when I was young!! takes half an our to get a location fix). bad camera (no wide cam, no smooth movie recording, and many more). won't auto connect to BT when screen is off. wont share screen on my TV. no IR blaster to control my devices. glitches. bugs. slow downs. ram management is non existing, it's like my smartphone became a feature phone. I literally can't do ANY multitasking. two apps at the same time? huh, no way!

but with all these issues I can't afford to re-set up my phone, again! over and over again! loose all my apps, re installing them, singing in, settings, oh my god.

that's why I'm stock on a "once smooth rom". I have to bare all those issues, just because I don't want to re-do everything and have the same experience.

if ANYONE, can help me, guide me, tell me that this rom fixes the issues on my current rom, and wont turn my phone into a living glitch in long term, I will be glad to know

OR

if there is a way to install/test this rom, without loosing everything and starting from ground up.

that would be awesome

Is the camera working well?

GPS connectivity?

Bluetooth?

IR Blaster?

overheating?

random crashes?

ram management?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] ssurell:
Ah, a signature spoofing solution. https://lineage.microg.org/
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] mmsp15:
I had noticed when using my Bluetooth earbuds that the support for AptX doesn't seem to be there... any idea on a timeframe if/when this will be supported as well as the other codecs that have been in previous versions?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] partyman66:
Does anyone know if USB/OTG is working on this with H910?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] npjohnson:
was a platform wide bug, should work next build
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] npjohnson:
IR Blaster only works sometimes I hear -everything else works.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] dilligaf56:
Dumb question - I recently installed 18.1 on my backup LG V20 (US996 unlocked).

My daily-use phone is still running rooted Oreo. I back that phone's SD card up by simply plugging it into one of my Linux boxes and copying everything to the computer.

I can't seem to do this with the SD card in the Lineage phone. I can see the directories, but MOST files are not visible. From what I've been reading, there have been changes in file permissions since Android 8 which prevent apps from reading other apps' data.

However, why would this prevent my reading the files on the card when out of the phone and plugged into my Linux machine? I only see the directory tree and in a FEW cases, actual files; for example, my computer can't see any of the files in my Music directory - even as root - so it's not simply a file permissions problem (and the SD card is formatted as exfat, so I don't think there should actually be file-permission restrictions). Utilities such as rsync can't find the files on the SD card, either.

Is there a work-around (in Linux) for this, or a setting in Android that I can change? I've already had to go in and manually edit /system/etc/permissions/platform.xml on the phone to allow apps to use the SD card.

Thanks!

EDIT: After re-installing the card in the phone, Root Explorer and TWRP can't see files that were previously readable...same as on the Linux machine. Root Explorer can see directories and a few files (e.g. the files in my nandroid backups, and the latest nightly .zips that I previously copied to the SD card - but that's it - no music files, photos, etc.). Apps such as PlayerPro (music) and QuickPic (photos) *do* still see the files. ???
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] OldPhonesNewTricks:
I have a US996, just came over from rooted Stock. I did not have these issues with Stock.

I'm having a lot of issues with Bluetooth, and I'm not sure how to troubleshoot it. My Garmin Fenix 6 will disconnect and reconnect every five to 15 minutes. This morning I went for a run and my headphones (Powerbeats Pro) will abruptly cease playing audio about a minute after I lock the screen, but the music's progress bar in Spotify will continue to advance. Pausing and restarting does not help, I have to disable and re-enable Bluetooth on the phone, after which the same problem inevitably happens.

The Bluetooth connection also seems to be much more fragile now. Previously I could leave my phone in one room and safely travel one or two rooms away with clean audio. Now as soon as I'm out of strict line of sight the audio starts to drop out.

Most other things on the ROM seem absolutely amazing so far, and it runs much better than Stock. Please let me know if there is a solution I am unaware of, or what I can do to help contribute to solving these issues.

**Edit**: The more I play with this, at least the audio part of this seems to be an issue of reception somehow being poorer now. In my vehicle, where the phone is close to the receiver and does not change relative position, I have no issues. Connection failure when I am wearing my headphones seems to correlate strongly with having the phone pressed against my body in a waist pack. It works ok while I'm holding the phone in my hand, then within seconds of stowing the phone in my waist pack the music ceases. These patterns are also consistent with the phone losing signal when I go to a different room in the house.

Another data point: I frequently walk past either of two large mechanical rooms that used to cause a little bit of stutter when using this headphone/phone combination. Now walking past either of those rooms causes the audio to completely halt, but the progress on the audio to keep going. To restore it I must get several feet past the rooms, restart Bluetooth on the phone, and resume.

Is there some setting or configuration somewhere that would cause the phone-side receiver to either be less sensitive, or the transmitter to emit a weaker signal? Or to just be less able to recover from EMI?

Edit 2: I downloaded LightBlue to try to get some fidelity on the watch part. Forgive me for being amateurish, I'm not experienced with logging or debugging, but this is what I was able to glean.

I set up LightBlue to log then just left my phone next to my watch. When it vibrated that the connection had dropped, I unlocked my phone to check the log (entry next to top arrow). Nothing happens for nearly two minutes, then the log shows a state change to OFF. Then further down the state changes from ON to ON and my watch vibrated shortly after letting me know it had reconnected.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Cryovenom:
What files did you use for your H915?

I got the VTR 91510e KDZ applied no prob, but I'm not sure which files I can use the 910 version and which I have to change for the 915 (and where to get them).

- for the root package

- for the 91010r KDZ he moved to (do we even need this?!)

- and for the version of LineageOS (since there's no H915 version - though I haven't had a chance to try the recommended H918 one yet)
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Cryovenom:
@npjohnson

I finally got my bootloader unlocked and was able to flash recovery.

Flashing the lineage-18.1-20210527-recovery-h918.img resulted in just a screen full of static.

So I flashed a copy of TWRP, which worked.

From TWRP I tried to do an ADB Sideload of lineage-18.1-20210527-nightly-h918-signed.zip and got an error that "This package is for device: h918, elsa, h815" - Can you check if there was a typo and that 815 should be a 915?

Cheers,

Jon
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] npjohnson:
OOF - Fixed, next build will have it fixed!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] npjohnson:
Okay, so h918 builds on Thursday, so we're in luck, and you'll have a new build to test tomorrow.

May i ask though, how did you unlock your bootloader?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] marm0tte31:
Hey guys,

I'm having issue with LOS 17.1 and 18.1 on my H990N, when I start a call the 4G icon disappear then the signal icon get a cross in the top status bar and the call hang and return to dialer :(

Does someone have the same issue?

I'm located in France using SFR carrier provider.

I'm wondering if the modem is really full compatible with android 10/11 RIL.

As far as I understand the modem partition contain the LG V20 nougat baseband, does LOS flash / upgrade it when installing?

Any help would be much appreciated because without call working my phone is useless
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] xxseva44:
Lineage is a fairly heavy rom so i'm not surprised your experiencing these issues, for multi tasking, good thermal performance, overall performance and camera performance, i'd recommend going with a lighter rom from either of these threads

Lighthouse

Superior and more

But as for the issues you're experiencing, gps can be fixed with this

Ir blaster can be fixed with gamma, updated builds can be found here

Overheating, well best solution i can offer is repasting or adding shims

I too experienced random crashes on lineage and never figured out how to fix them so yea:(

Like i said, lineage is fairly ram heavy so only thing i can think of to help ram management is preventing things from running in the background

For the camera, i'd recommend open camera, although 60fps recording does not work and is believed to be a kernel issue
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] partyman66:
Newer versions of ES File Explorer can't run wit root permission using Magisk. Try using an old version from a few years ago. This only addresses a small portion of your problems but figured I'd mention it to you since I realized this act in December after switching to Lineage 17.1 and using a newer ES File Explorer version initially.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Cryovenom:
@npjohnson

I'll do a full write-up once I'm sure I've got a repeatable process, but basically it used the procedure that flashes a stock H91510e kdz, then cross-flashes the *contents* of a US99610f kdz into all the partitions using a patched copy of LGUP, then uses DirtySanta to unlock the bootloader.

At that point I had a copy of Fastboot from an engineering aboot.img and could load whatever I wanted to into recovery. It ain't pretty, but it worked. Here are my results.

Bootloader Notes:

- Lineage H918 Recovery (lineage-18.1-20210603-recovery-h918.img) results in screen full of static

- Lineage US996 Recovery (lineage-18.1-20210506-recovery-us996.img) also static

- TWRP 3.0.2 loads but won't let you sideload lineage because it can't identify the phone

- TWRP 3.5.2 had some other problem I forgot to document

- But the Lineage H910 recovery (lineage-18.1-20210506-recovery-h910.img) works fine!!

So then I used the Lineage H910 Recovery to try different OS builds

OS Build Notes:

- Lineage H918 nightly (lineage-18.1-20210603-nightly-h918-signed.zip) results in screen full of static

- Lineage US996 nightly (lineage-18.1-20210506-nightly-us996-signed.zip) also static (I got it displaying at some point but it crashed out on OS load with a modem error. Can't re-create that though)

- Lineage H910 nightly (lineage-18.1-20210506-nightly-h910-signed.zip) seems to work

I say "seems" because it's past midnight here and I just got the OS booted. I was able to put my Telus SIM in and make a phone call to a number and hear the company's IVR recording.

I'll test in more detail tomorrow, but it's starting to look like the H910 image may be the one to take as the base OS instead of the H918. I have no idea what the actual hardware differences are between the different models, so let me know if that makes any sense to you.

Cheers,

Jon
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] hibby50:
Anyone able to test android auto? I cam from 17.1 with a diry flash. Before I do a factory reset I just want to see if it's working for others
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Cryovenom:
Okay so here are the results of my testing of the H910 LineageOS build on my H915:

Testing:

- Boots into OS without Errors PASS

- Able to make phone calls PASS

- Able to take pictures:

- Forward cam (normal) PASS

- Forward cam (wide angle) ????

- Selfie cam PASS

- Can surf on WiFi PASS

- Speedtest 239/164

- Can surf on Mobile Data FAIL

- Speedtest N/A

- GPS finds location quickly PASS

- Bluetooth PASS

* I don't know how to switch front-facing cameras in LineatsOS' camera app

So the big issue is I don't have mobile data. I can make phone calls no problem, and the APNs look good, but it just won't connect to mobile data.

According to this thread here (post #3), it's the engineering aboot.img that we used to unlock the bootloader that's somehow causing the problem. I tried to just flash the stock aboot.img back onto the phone without changing anything else, but that resulted in a boot loop so I'll have to re-flash the stock KDZ and start from scratch.

More experimentation required. If anyone has any ideas at this point I'd love to hear them!
[Nexus 7 (2013) Original Android Development] npjohnson:
Nexus 7 2013 (Wi-Fi & LTE)

- Your warranty is now void.
- You have been warned.
- Use at your own risk.

Introduction:

This is the Official Lineage OS 18.1 thread for the Nexus 7 (2013, Wi-Fi & LTE).

Downloads:

Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.

Official Builds:

flox - 2013 (Wi-Fi)

debx - 2013 (LTE)

Unofficial - built once a month by me, includes GApps and Pixel goodies:

flox - 2013 (Wi-Fi)

debx - 2013 (LTE)

If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

Known Bugs:

None.

Find any? Report them according to this guide.

Notes:

The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.

This device _must_ be repartitioned before installation, the only supported repartition package is the one listed in the Wiki linked above - please make sure you followed it before attempting to install!

Kernel Source: https://github.com/LineageOS/android_kernel_google_msm
[Nexus 7 (2013) Original Android Development] jb-:
Thanks for an official version!

Can we possibly get the same for deb? (LTE)

I suppose I mean debx (deb repartitioned)

Edit: oh i see your note about debx, hopefully someone with experience will jump on it.
[Nexus 7 (2013) Original Android Development] npjohnson:
See the last bullet in the "Notes" section ;p
[Nexus 7 (2013) Original Android Development] jb-:
I see followmsi has 18.1 unofficial for flo/deb, maybe he'd be interested in working on official, although don't believe there was much interest in the past.