[Sort-of Treble] [H910|H918|LS997|US996|VS995|H990] UNOFFICIAL LineageOS 15.1 - LG V20 ROMs, Kernels, Recoveries, & Other Developm

[Sort-of Treble] [H910|H918|LS997|US996|VS995|H990] UNOFFICIAL LineageOS 15.1 - LG V20 ROMs, Kernels, Recoveries, & Other Developm

Updates:
9-11-21 - New builds out for all
9-7-21 - Custom TWRP is ready! Seperate Vendor Image now longer requred (vs995 only). Due to my busy schedule the vs995 variant will be my primary foucus and will recieve updates much sooner as build on system takes a while. However testing with other variants will still be posible with the older builds provided.
9-4-21 - Install method fixed. Flashing vendor image no longer require jusut party treble tool and rom. Updated builds coming soon.

cool stuff, good work

TripOG said:
cool stuff, good work
Click to expand...
Click to collapse
Thanks, did you have any luck with GSI's?

ROMSG said:
Thanks, did you have any luck with GSI's?
Click to expand...
Click to collapse
I haven't tried yet, I'll give it a shot this weekend.

ROMSG said:
View attachment 5396833
Credit goes to @x86cpu as I used much of his work.
I am not responsible for any damage done to your device.
After Hours of work I have succsesfully built a Trebleized ROM for the V20. Kinda.
I have not gotten a GSI to work YET. Why post this then? Well I'm hoping someone
with more knowledge than me can help. Reading LogCats from my VS995 I'm getting
hung up on this error:
Waited one second for [email protected]::ISensorManager/default. Waiting another...
In the meantime I have only tested 3 GSIs so if you want to try for yourself here are some builds.
But first...
Instructions this installs much differently than most ROMs
Note: If you are using a vs995 variant I have made a Treble Twrp. You can skip step 3 as the vendor image is now included in the vs995 ROM.
1. Flash this to begin, its a tool that will add the vendor partition to your device. Chose the 800mb partition size or else the partition won't be recognized by TWRP. When asked to reboot say yes.
2. Wipe System, cache, dalivk, and data. Then flash the ROM that corrosponds with your phone
3. (skip if you are using a vs995) Flash this vendor image. Make sure vendor is mounted beforehand.
4. Reboot
You may have com.android.phone has stopped keep popping up just enable developer options and it will give you the option to mute the pop up. Camera is also not working. Fixed on vs995 however likely won't work on GSI's.
VS995
H910
H990
US996
LS997 & H918 Coming Soon
Sources
Click to expand...
Click to collapse
Damnn this is exciting, well done
I'll probably give it a go on my vs995
Is it cool if i pm?

xxseva44 said:
Damnn this is exciting, well done
I'll probably give it a go on my vs995
Is it cool if i pm?
Click to expand...
Click to collapse
Sure you can pm

ROMSG said:
Updates:
9-7-21 - Custom TWRP is ready! Seperate Vendor Image now longer requred (vs995 only). Due to my busy schedule the vs995 variant will be my primary foucus and will recieve updates much sooner as build on system takes a while. However testing with other variants will still be posible with the older builds provided.
9-4-21 - Install method fixed. Flashing vendor image no longer require jusut party treble tool and rom. Updated builds coming soon.
Click to expand...
Click to collapse
so, on an h910 are we still flashing the vendor? it's not really clear which information is the most up to date.

TripOG said:
so, on an h910 are we still flashing the vendor? it's not really clear which information is the most up to date.
Click to expand...
Click to collapse
Yes h910 is still flashing the vendor image. Custom twrp and the new build are vs995 only

ROMSG said:
Yes h910 is still flashing the vendor image. Custom twrp and the new build are vs995 only
Click to expand...
Click to collapse
okay, im getting error 7 in twrp when flashing your h910 rom
did you put your vendor partition at the front or back?
also did you select system or data when creating the vendor partition?
edit: looks like my twrp was out of date, it seems to be flashing with 3.5.2_9-0
now it fails at flashing the vendor.img i get error: 255
boots to flashboot so i pushed the vendor image with that and i get the error
"Writing 'vendor' FAILED (remote: 'Unknown chunk type')"

TripOG said:
okay, im getting error 7 in twrp when flashing your h910 rom
did you put your vendor partition at the front or back?
also did you select system or data when creating the vendor partition?
edit: looks like my twrp was out of date, it seems to be flashing with 3.5.2_9-0
now it fails at flashing the vendor.img i get error: 255
boots to flashboot so i pushed the vendor image with that and i get the error
"Writing 'vendor' FAILED (remote: 'Unknown chunk type')"
Click to expand...
Click to collapse
Ya i've been having that issue with my vs995. It's fix in my newer builds for vs995. Try reinstalling party if that doesn't work newer h910 builds will be out soon.

ROMSG said:
Ya i've been having that issue with my vs995. It's fix in my newer builds for vs995. Try reinstalling party if that doesn't work newer h910 builds will be out soon.
Click to expand...
Click to collapse
I tried party a few times changing where the vendor location is and everything, seems the only place vendor can be is data after, anything else won't allow the rom to flash. I'll give it another shot when your updates are out.

TripOG said:
I tried party a few times changing where the vendor location is and everything, seems the only place vendor can be is data after, anything else won't allow the rom to flash. I'll give it another shot when your updates are out.
Click to expand...
Click to collapse
alright sorry for the issues , next build is better

TripOG said:
I tried party a few times changing where the vendor location is and everything, seems the only place vendor can be is data after, anything else won't allow the rom to flash. I'll give it another shot when your updates are out.
Click to expand...
Click to collapse
new h910 builds out

ROMSG said:
new h910 builds out
Click to expand...
Click to collapse
i set up the vendor partition again, wiped, loaded up the new 9/11 h910 rom and it boots up fine.
first thing i notice is the camera doesnt work.

TripOG said:
i set up the vendor partition again, wiped, loaded up the new 9/11 h910 rom and it boots up fine.
first thing i notice is the camera doesnt work.
Click to expand...
Click to collapse
sadly for now it may neverwork on treble

ROMSG said:
sadly for now it may neverwork on treble
Click to expand...
Click to collapse
never say never. have you tried flashing any of the google gsi? if so, were you able to boot em? where would one flash the vbmeta to?

TripOG said:
never say never. have you tried flashing any of the google gsi? if so, were you able to boot em? where would one flash the vbmeta to?
Click to expand...
Click to collapse
Google GSI’s aren’t booting. I don’t know were to flash a vbmeta. We may be able to get the cameras to work by injecting the blobs back into /system with a magisk module.

Related

[ROM][OREO][OFFICIAL] lineage-15.1 for Pixels (marlin/sailfish)

Official 15.1 nightlies have been discontinued.
Go here for the official 16.0 thread.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Wiki.
Important Info
Make sure you have the vendor, radio, & bootloader img's installed, from the stock oreo 8.1 OPM4.171019.021.P1 July 2018 factory image. More info below.
Download Links
marlin rom: https://download.lineageos.org/marlin
marlin vendor, radio, & bootloader img's: https://androidfilehost.com/?w=files&flid=278595
marlin twrp: https://twrp.me/google/googlepixelxl.html
sailfish rom: https://download.lineageos.org/sailfish
sailfish vendor, radio, & bootloader img's: https://androidfilehost.com/?w=files&flid=278596
sailfish twrp: https://twrp.me/google/googlepixel.html
google apps (Optional): https://wiki.lineageos.org/gapps.html
root su addon (Optional): https://download.lineageos.org/extras Note: Use arm64 zip. After installing the su addon, you can enable root in developer options.
Instructions
Initial Install
NOTE#1: Make sure you have the correct vendor, radio, & bootloader img's installed in BOTH slots before installing lineage. They can be extracted from the oreo 8.1 OPM4.171019.021.P1 July 2018 factory image or use the ones in the download section above that I already extracted for you. You can flash them using the following commands:
fastboot flash --slot all vendor VendorFileName.img
fastboot flash --slot all radio RadioFileName.img
fastboot flash --slot all bootloader BootloaderFileName.img
NOTE#2: The official mindthegapps build that's linked in the wiki are very minimal (like opengapps pico), so i made my own mindthegapps build that is pretty much the same as opengapps nano. download link
NOTE#3: If you're a Project Fi or Sprint customer, you need some extra gapps, so use this one instead. download link
NOTE#4: If you want to update from my unofficial 15.1 build to official without wiping, you can follow the "How to dirty flash an official weekly over an unofficial build" steps here.
1. boot into twrp and wipe data and system
2. flash rom zip
3. flash twrp zip
4. in twrp main menu, select reboot then recovery (this will reboot you into the other slot)
5. flash gapps zip (optional)
6. flash su addon zip for root (optional)
Reboot & enjoy.
Updating
If you've already done the initial install, then you can use the LineageOS Updater to install new builds. It's in settings->system->about phone->lineageos updates.
It will give you a notification when a new build is available.
Weather Provider Addons (Optional)
For those that like to use the lineage cLock widget, here are some weather provider apk's you can use that i compiled.
https://www.androidfilehost.com/?w=files&flid=243785
Changelog
https://download.lineageos.org/marlin/changes/
Bug Reporting
If a bug is discovered, confirm it with other users in this thread, then report it following our wiki here: https://wiki.lineageos.org/bugreport-howto.html
LineageOS Stats
https://stats.lineageos.org/
Credits
Many thanks to the LineageOS team and all the contributors out there in the community :good:
Source Code:
Device tree: https://github.com/LineageOS/android_device_google_marlin/tree/lineage-15.1
Kernel tree: https://github.com/LineageOS/android_kernel_google_marlin/tree/lineage-15.1
Vendor tree: https://github.com/TheMuppets/proprietary_vendor_google/tree/lineage-15.1
Android version: 8.1.0 Oreo
Kernel version: Linux 3.18.70

Omg LOS 15 ! Any Sailfish compatibility ?

Nice

Nice!!!!! Bugs?

Anyone Flash this yet?

Thanks very much for this. Op instructions were flawless and booted right up. Feel's good to be running los, everything I've tested/used works perfectly

billiepreks said:
Any Sailfish compatibility ?
Click to expand...
Click to collapse
nope, sorry. But it can be built and works fine. I know a person that uses it.
TotoBerto02 said:
Bugs?
Click to expand...
Click to collapse
Only a couple things come to mind that are worth mentioning...
Livedisplay has not been implemented yet. But Night Display is working fine.
And I cherry-picked the buttons settings changes into this rom, which is still a work-in-progress. So some of them don't work yet, but most do.
JS.zip said:
Op instructions were flawless...
Click to expand...
Click to collapse
Thanks to @kgjel for that :good:
He gave me a set of detailed instructions that I revised slightly and put in the first post.

JS.zip said:
Thanks very much for this. Op instructions were flawless and booted right up. Feel's good to be running los, everything I've tested/used works perfectly
Click to expand...
Click to collapse
No such luck here. The post says to be on 8.1 OPM1.171019.011, but the detailed instructions say to match what's in the lineage.mk, which is OPR3.170623.013. Which stock build were you on when installing this ROM? I either get boot loops or it ends up booting up, but it is still the stock OS. I have tried following the detailed instructions exactly, and all seems to go well, but no Lineage!

mrhds said:
No such luck here. The post says to be on 8.1 OPM1.171019.011, but the detailed instructions say to match what's in the lineage.mk, which is OPR3.170623.013. Which stock build were you on when installing this ROM? I either get boot loops or it ends up booting up, but it is still the stock OS. I have tried following the detailed instructions exactly, and all seems to go well, but no Lineage!
Click to expand...
Click to collapse
Same problem here, i get about 3-5 Boot Loops and then it finally stops at the G with the line under. I tried multiple times...

mrhds said:
No such luck here. The post says to be on 8.1 OPM1.171019.011, but the detailed instructions say to match what's in the lineage.mk, which is OPR3.170623.013. Which stock build were you on when installing this ROM? I either get boot loops or it ends up booting up, but it is still the stock OS. I have tried following the detailed instructions exactly, and all seems to go well, but no Lineage!
Click to expand...
Click to collapse
I saw that as well. I was on 8.1, I took the main op too be correct.

mrhds said:
The post says to be on 8.1 OPM1.171019.011, but the detailed instructions say to match what's in the lineage.mk, which is OPR3.170623.013.
Click to expand...
Click to collapse
thanks. fixed.
unfortunately, flashing stuff on a marlin is a major pain in the rear. very easy to mess up.
make sure you follow the steps EXACTLY.

AndroidDevices said:
Same problem here, i get about 3-5 Boot Loops and then it finally stops at the G with the line under. I tried multiple times...
Click to expand...
Click to collapse
mrhds said:
No such luck here. The post says to be on 8.1 OPM1.171019.011, but the detailed instructions say to match what's in the lineage.mk, which is OPR3.170623.013. Which stock build were you on when installing this ROM? I either get boot loops or it ends up booting up, but it is still the stock OS. I have tried following the detailed instructions exactly, and all seems to go well, but no Lineage!
Click to expand...
Click to collapse
The lineage MK file linked in the detailed instructions shows OPM1.171019.011. Not sure which one you're looking at? The link goes here: https://github.com/razorloves/android_device_google_marlin/blob/15.1-testing/lineage.mk#L22

hokiealumnus said:
The lineage MK file linked in the detailed instructions shows OPM1.171019.011. Not sure which one you're looking at? The link goes here: https://github.com/razorloves/android_device_google_marlin/blob/15.1-testing/lineage.mk#L22
Click to expand...
Click to collapse
I read the detailed instructions, im not looking at what he's looking at...FYI

TWRP 3.2.0-0 is unable to decrypt the factory "opm1" /data store. 3.2.1-0 is able to decrypt but fails to flash LOS. Something is not quite correct here.....

carbinefreak said:
TWRP 3.2.0-0 is unable to decrypt the factory "opm1" /data store. 3.2.1-0 is able to decrypt but fails to flash LOS. Something is not quite correct here.....
Click to expand...
Click to collapse
Do you have a pin or password on your lockscreen? If so you must remove it first

so are you the new maintainer? officially?

Zehlek said:
Do you have a pin or password on your lockscreen? If so you must remove it first
Click to expand...
Click to collapse
Good catch, Removed the password and ran through the procedure just fine. Phone just finished first boot and is in the process of updating apps now......
Thanks! Super Cool!

@razorloves is this always required when flashing any rom on Maril?
f - Go to `Mount` and select to mount `Vendor`. Go back to TWRP home
g - Go to `Advanced` - > `File Manager`. Navigate to /vendor/overlay/, then click the checkmark in the bottom right. Select `Delete`.
Click to expand...
Click to collapse

Thanks to @razorloves for making me actually read directions and stop being such a noob....

jmiller3342 said:
so are you the new maintainer? officially?
Click to expand...
Click to collapse
Yes. Intervigil is a maintainer too.
Zehlek said:
@razorloves is this always required when flashing any rom on Maril?
Click to expand...
Click to collapse
not necessarily.
Google put a couple theme apk's and frameworks apk in that folder. It will override a lot of changes we make to our custom rom. So I think it's best to remove it.
You can see my comments in this change to give you an idea of one of the problems that frameworks apk can cause. https://review.lineageos.org/198569
When you flash stock rom or flash the vendor img from the stock rom, it will replace that folder that was deleted.

[ROM][H910|H918|LS997|US996|VS995|H990*] UNOFFICIAL LineageOS-15.1 for LG V20

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING: DO NOT ENCRYPT! YOU WILL CORRUPT YOUR ENTIRE DATA INCLUDING INTERNAL SDCARD
(Please do it carefully)
Disclaimer
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Introduction
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device. More info.
These are my UNOFFICIAL builds of LineageOS-15.1 for LG V20 variants. I did NOT create this ROM. I am helping to contribute to this ROM. Thanks to all other coders who contributed to LineageOS.
IMPORTANT
BACKUP! These are UNTESTED builds. Please be ready to recover your previous ROM. If it kernel panic, boots into bootloader, etc... grab as much info as you can.
Builds are done periodically (see download below)
Do NOT be rude.
Respect all users.
Any and all users, please help each other. I have a us996 variant, so other variants might have some issues.
Known items
Lack of 2nd Screen Support
VoLTE and WiFi calling do not work yet
Other known issues (same as OFFICIAL too):
us996 static on boot: Unlock bootload from LG, using dirty santa causes static on boot, will not fix. (sorry)
WiFi or Bluetooth MAC is "00:00:00:00:00:00" - You wiped the misc partition, you'll need to fix: https://forum.xda-developers.com/showpost.php?p=70474540&postcount=12
5Ghz tether not working due to "error"
Enabling ADB Debugging in development setting can cause a kernel crash. If you are quick and press OK right away, it will take and still crash. On reboot, it will be enabled.
H918 - ARB1 .. flash the 10p version, ARB0..flash the PRE10p. (10p is where the ARB got tripped to 1)
Install
You can upgrade from 14.1 (UNOFFICIAL) to 15.1. If you are not on my UNOFFICIAL yet, flash the to-x86cpu.zip first (and reboot recover before upgrade, not reboot into system).
I would suggest the TWRP from Phoenix591 (See Thanks section below)
Flash to-x86cpu.zip if you want. (See Downloads below)
Flash UNOFFICIAL ROM
Wipe cache, and dalvik cache
Magisk if you choose
Flash GAPPS (I use nano)
Reboot and wait....
(Copied from OFFICIAL thread)
To enable Developer Options go to Settings, About Phone and repeatedly press Build Number.
If you use ADB read this: PSA by CM
If you use reboot to recovery read this: PSA by CM
Regarding new Superuser: PSA by CM
Bugs
If you encounter issues/bugs that are not known, please report. This is not the OFFICIAL ROM, but I can help to get any issues fixed. I use the us996 variant. If I can replicate your issue then I can track it down. If I cannot, please provide as much detail as possible. Logcats are great.
Please indicate what v20 variant you have (h910, h918, ls997 us996, vs995, h990/ds) and what you are running (OFFICIAL or UNOFFICIAL) and date. Any mods (no judgment) as well.
I am aware people run mods or change things. I am not against it (as I do myself). However, if needed I may ask you to data wipe (you can say no), or remove a mod that might be interfering. I will do the best I can.
Thanks
Any and all users in this thread who contributed or will contribute to making this ROM as stable as possible
LineageOS Team
@Rashed97 for continuing
@Phoenix591 for TWRP update that support OTA ( https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239 )
Downloads
ROM: UNOFFICIAL downloads (Note date)
Gapps: arm64 nano 8.1
Sources
https://github.com/LineageOS
https://github.com/LineageOS/android_kernel_lge_msm8996
https://github.com/LineageOS/android_device_lge_msm8996-common
https://github.com/LineageOS/android_device_lge_v20-common
h910
h918
ls997
us996
vs995
h990

What is not working or problematic
What is not working or still wonky:
Encryption -- Works.
USB OTG -- Should be working.
Ambient display -- Disabled now.
Livedisplay -- Should be working.
IR will work, then timeout, then work again.
Video recording -- Should be working. Works sometimes, appears to record, but playing back audio is at the beginning, video at the end, and the duration is messed up.
5g tether -- Not working still.
No FM driver.

saved

Freakin' lit. Flashing it on my VS995 now. Awesome work!

Thanks for your effort for bring LOS definitely I'II try this later tonight on my vs995 .

Thanks a lot sir, @x86cpu, your dedication should be an inspiration and I implore all users to thank and possibly donate to this dev. Make him rich. I would say this thread is XDA portal news worthy.

NotYetADev said:
Freakin' lit. Flashing it on my VS995 now. Awesome work!
Click to expand...
Click to collapse
Gabe2014 said:
Thanks for your effort for bring LOS definitely I'II try this later tonight on my vs995 .
Click to expand...
Click to collapse
hawkeye29 said:
Thanks a lot sir, @x86cpu, your dedication should be an inspiration and I implore all users to thank and possibly donate to this dev. Make him rich. I would say this thread is XDA portal news worthy.
Click to expand...
Click to collapse
There can still be bugs I haven't found. I tested what I could on a us996 using a VZW sim. Apparently LTE might be a bit weird in a vs995 device.

x86cpu said:
There can still be bugs I haven't found. I tested what I could on a us996 using a VZW sim. Apparently LTE might be a bit weird in a vs995 device.
Click to expand...
Click to collapse
Is there no fingerprint security option in 8.1? Not present

hawkeye29 said:
Is there no fingerprint security option in 8.1? Not present
Click to expand...
Click to collapse
It should be, I did test that and was working fine. Which device?

x86cpu said:
It should be, I did test that and was working fine. Which device?
Click to expand...
Click to collapse
H910

hawkeye29 said:
H910
Click to expand...
Click to collapse
I'll have to check into it.

Its great that you're able to get this up basically as soon as the april fools thread was locked and disappeared XD . Will be installing soon.
Edit: Like others are saying finger print reader is MIA (US996).

On the vs995, so far so good. Only thing I see missing is the fingerprint sensor. But maybe it's been moved

Couple more issues:
Encryption is probably broken: I let it go for an hour and the ETA was still at 0:00 like it was the whole time ( I had only a handful of apps installed and in 14.1 it only took around 5 minutes).
Enabling adb caused the whole system to crash and reboot, but it did seem to be enabled afterwards.
Still enjoying Oreo benefits like YouTube picture in picture mode

x86cpu said:
I'll have to check into it.
Click to expand...
Click to collapse
Can confirm fingerprint is missing.
@x86cpu Thanks for bringing Oreo to our devices! Very smooth experience so far except Ambient Display seems bit sluggish. Disabled it and its all good now.

Phoenix591 said:
Couple more issues:
Encryption is probably broken: I let it go for an hour and the ETA was still at 0:00 like it was the whole time ( I had only a handful of apps installed and in 14.1 it only took around 5 minutes).
Enabling adb caused the whole system to crash and reboot, but it did seem to be enabled afterwards.
Still enjoying Oreo benefits like YouTube picture in picture mode
Click to expand...
Click to collapse
I'll have to check encryption too. Did you upgrade from 14.1 encrypted? Or just try to enable the encryption? (ADB kernel panic is a known issue right now.)

x86cpu said:
I'll have to check encryption too. Did you upgrade from 14.1 encrypted? Or just try to enable the encryption? (ADB kernel panic is a known issue right now.)
Click to expand...
Click to collapse
This was enabling from unencrypted. Had handful of apps but none of my large ones restored yet so it should have been really fast.

Phoenix591 said:
Couple more issues:
Encryption is probably broken: I let it go for an hour and the ETA was still at 0:00 like it was the whole time ( I had only a handful of apps installed and in 14.1 it only took around 5 minutes).
Enabling adb caused the whole system to crash and reboot, but it did seem to be enabled afterwards.
Still enjoying Oreo benefits like YouTube picture in picture mode
Click to expand...
Click to collapse
Confirmed on the h910 as well, enabling causes a crash and reboot

I thought It was the April Fools post. I'll be waiting for the ARB1 version for my phone

So is HiFi DAC working? I thought it might not be possible...

[ROM][Pixel 3][UNOFFICIAL] LineageOS 16.0 [blueline]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free and open-source operating system for smartphones and tablet computers, based on the Android mobile platform.
This is an unofficial build of LineageOS for the Pixel 3 (blueline). I always liked Lineage (and its predecessor CyanogenMOD) as well as the Google line of phones. Unfortunately having a Google Pixel phone isn't certainty for a lot of custom ROMS anymore, so that's why I decided to compile my own version. It's been quite challeging, but I think I finally have a build that is good enough to share.
About
This ROM is built straight from the LineageOS sources found on https://github.com/lineageos. There are only 3 changes in order to get this build:
The device tree is just a single folder with references to the crosshatch (Pixel 3XL) tree that is already there in the sources
The binaries for this ROM come from The Muppets
The ROM is compiled with the nano version from Open Gapps, including the Pixel specific bits for unlimited photo upload for instance
I am not a developer, I only build this ROM and it reflects the the current status. If there are any things missing or not working I suggest to contact the LineageOS team, they are the real geniuses here and deserve all the credits. I will try to keep this ROM updated on a regular basis.
First Installation
Installing the ROM can be a little hard, especially the first install. Upgrades will be relatively easy though. This first setup is only needed when coming from a different ROM then this. I can't support you if you did't follow this first installation. Be warned it will wipe your user data in the process, so make sure you make a backup if needed.
Place the ROM and optionally the TWRP zip, a kernel and root on the phone and reboot to recovery by using the command line (fastboot boot twrp.img) or hold the VOL DOWN key while rebooting the phone.
In order to make the right startbase for the ROM you have to install the latest stock Pixel 3 image from Google found here to BOTH slots. You can use the script in the download folder. Instructions how to use it can be found in the script itself.
Wipe 'data' and 'Dalvik / Art Cache' from TWRP - Wipe - Advanced Wipe or use the slider in TWRP for a factory reset. Optionally you should also delete the Android folder on your internal storage through the TWRP File Manager
Flash the ROM and optionally the TWRP zip, kernel and root and reboot the phone
Upgrades to new version
After the hard initial work to get the ROM installed it's going to be easy for upgrades to new versions.
Download the new ROM on the phone and reboot or fastboot flash to the TWRP recovery
Flash the new ROM and optionally TWRP. If you want to flash another kernel or a root solution you will have to reboot you phone, so it switches slots and let it boot normally. Then go back to recovery and flash in this order: TWRP - kernel - Magisk and reboot
After a monthly update from Google and only when LineageOS also adapted to the latest monthly sources (I will tell you this) you will have to do an extra step:
Download the latest Lineage OS ROM and place it on the internal storage
Download the latest image from the Google Factory Images site, extract the bootloader, radio and vendor images and flash them in the bootloader to BOTH slots. Alternatively (and actually my prefered method) you can use the script provided in the download folder. Instructions are inside the script
From here go to TWRP recovery and flash the previously downloaded new ROM, optionally followed by TWRP.
Optionally, after a reboot you can flash Magisk and/or another kernel.
Not working
Active Edge
Now playing (on the lockscreen, it works while the screen is on, just no history))
Call recording (not enabled in sources for our device)
Accent colours Default, Forest and Cocoa display a blue colour icon theme instead of its own
Call Screen (couldn't test it myself)
The "markup" tool to edit screenshots doesn't work
Downloads
Now finally for the good part, the downloads. In this folder you will always find the latest ROM:
https://drive.google.com/open?id=1lx8dlS4ZRVVQYeQS0I7Y_6yJ5SFMg7uR
Happy flashing

Awesome! Just one question, is SELinux permissive or enforcing?

BackCheck said:
Awesome! Just one question, is SELinux permissive or enforcing?
Click to expand...
Click to collapse
Enforcing

@jorgen2009 I used to use your Pixel 2 LineageOS unofficial builds. Really excited to see that you are going to be making Pixel 3 builds now! Looking forward to trying it out tonight. Thanks!

@jorgen2009 I flashed the rom and it's working great for the most part. The only problem I've noticed is that there is no audio in phone calls. I cannot hear the other person and they cannot hear me either. This is happening regardless of whether VoLTE is enabled. Any ideas? Thanks again for your work on this.

That was happening with other February custom roms. just flashing Google's radio image in fastboot from the February Google's factory image should do the trick.

@beanaman Thanks, this fixed it for me! Flashing just the radio image wasn't enough, though. I also had to flash the vendor image.

Awesome

bdr9 said:
@beanaman Thanks, this fixed it for me! Flashing just the radio image wasn't enough, though. I also had to flash the vendor image.
Click to expand...
Click to collapse
Yup. Vendor and radio, sometimes bootloader needs to be updated

Thanks! Working great until now
Ass said before, the only thing that do not work is the active edge.
Installed today so I can't talk about battery not Google pay

Don't knot m know what's going on but after a long time charging, it's incredibly slow and laggy... A reboot solved it. Hooping to find out what's going on...

ShadowJP88 said:
Thanks! Working great until now
Ass said before, the only thing that do not work is the active edge.
Installed today so I can't talk about battery not Google pay
Click to expand...
Click to collapse
Google pay works fine (I have magisk installed), active edge is proprietary code and won't be implemented unless someone gets lucky or Google releases the source.

sonicscrewup said:
Google pay works fine (I have magisk installed), active edge is proprietary code and won't be implemented unless someone gets lucky or Google releases the source.
Click to expand...
Click to collapse
Fyi, Dirty Unicorns has a working implementation of Active Edge. I am using it right now and it works flawlessly.

sonicscrewup said:
Google pay works fine (I have magisk installed), active edge is proprietary code and won't be implemented unless someone gets lucky or Google releases the source.
Click to expand...
Click to collapse
Did you just enabled hidesu for Google pay or any special steps you performed ?
Sent from my Pixel 3 using Tapatalk

Just posted an update of the ROM, built from today's sources. Together with this release I made a Lineage OS ROM for the Pixel 3XL as well. As I don't have this phone myself I'm not sure if it's working. If anyone can confirm this I will make in announcement in the Pixel 3XL forum as well, hopefully stimulating development for our devices.
See the OP for the download link

sendhiloo7 said:
Did you just enabled hidesu for Google pay or any special steps you performed ?
Click to expand...
Click to collapse
Only enable magisk hide for them, nothing else

I'm seeing that in the OP, the instructions don't involve wiping System after making sure you start from Google's factory image as a base. Any reason I shouldn't wipe System? I did, and everything seems to be working okay. Do I lose any features or anything?

yadon said:
I'm seeing that in the OP, the instructions don't involve wiping System after making sure you start from Google's factory image as a base. Any reason I shouldn't wipe System? I did, and everything seems to be working okay. Do I lose any features or anything?
Click to expand...
Click to collapse
System will be completely overwritten by the ROM, so no need to wipe it first. Whether you wipe it or not has no effect on the features whatsoever

Hi,
To enable active edge, look at these commits: https://gerrit.dirtyunicorns.com/#/q/status:merged+topic:active_edge

jorgen2009 said:
System will be completely overwritten by the ROM, so no need to wipe it first. Whether you wipe it or not has no effect on the features whatsoever
Click to expand...
Click to collapse
Any chance thay you may add proper support so custom kernels can be used together with LineageOS?
Using a kernel like Proton together with LOS is making the phone just randomly freeze once it have fully booted non stop.

[DISCONTINUED][GSI][9][Reference] LineageOS 16.0 GSI (all archs) and how to build them

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Background:
We've been offered LOS 16 GSIs in the past (here, and here), but they haven't been updated in quite a while, so as a LineageOS lover, I decided to step up and do it myself. Turns out it wasn't so easy - there were a number of hurdles that prevented it from building properly, booting or being feature-complete. But here I am, having figured out most if not all what's needed, and verified booting on an arm64 ab device I own, I'm ready to share my findings as well as some builds with you.
Disclaimer:
This is still mostly a LineageOS team / PHH @phhusson effort, credits to them and all associated for making all this possible.
No instructions will be offered. If you're here in this forum, you should know what you're doing.
No guarantees that everything would work. This is a GSI, bugs are bound to happen.
Do not report hardware-related bugs in this thread. I am selfish and only care about getting it running on my device with whatever features I need working. Plus I'm not PHH and can't solve any either.
Download:
https://sourceforge.net/projects/andyyan-gsi/files/
Compressed as .xz archives - extract first.
Vanilla except for these changes:
Modifications needed to make it build/boot/feature-complete, see below
Disabled "vendor mismatch" warning on boot
Re-enabled lockscreen shortcuts
Default stretch-to-fullscreen (force apps to render in 18:9)
Extra tip:
If you have a relatively low-end device and experience UI stutters, try this simple build.prop trick (technically a debug property, so use at your own risk). Thanks @SnapTheRipper for bringing it up!
Modifications needed (builders-only):
Now for the juicy part. On top of PHH's already fantastic build script, you'll need these:
device/phh/treble:
Revert Update lineage.mk for LineageOS 16.0 - add back LOS sepolicy, so that LOS-specific features like Profiles, LiveDisplay, Styles, Trust would work
Revert exfat fsck/mkfs selinux label - fix a conflict in doing so
build/make:
Revert Enable dyanmic image size for GSI - fix building
external/tinycompress:
Revert tinycompress: Use generated kernel headers - remove dependency on generated kernel headers
frameworks/base:
Revert Initial support for in-display fingerprint sensors - use PHH's implementation
vendor/lineage:
Apply build/soong/Android.bp: Disable generated_kernel_* - disable generating kernel headers, since GSIs don't have a kernel
Revert lineage: Enforce privapp-permissions whitelist, or change it to log
vendor/qcom/opensource/cryptfs_hw:
Revert cryptfs_hw: Use generated kernel headers - remove dependency on generated kernel headers
Apply [TEMP]: Header hack to compile for 8974 - fix a missing header
And that's it. Doesn't look like much, but most are pretty hacky solutions, and I don't expect them to be merged anywhere. As I said, I'm only interested in getting it running, I don't care what it takes.
Stuff on GitHub (builders-only):
I've also collected necessary scripts/patches and uploaded them: treble_build_los, treble_patches (PHH's treble_patches adjusted for LOS). Not the cleanest code, but should help if you still need more clues.
Donate?
https://paypal.me/AndyCGYan
Thanks for reading - I hope this could be of use to fellow LineageOS lovers / home builders.

Is there any chance for A-only 64 build?

Lecterr said:
Is there any chance for A-only 64 build?
Click to expand...
Click to collapse
I hope will be for A-only too.. many people would welcome it . :silly:

Lecterr said:
Is there any chance for A-only 64 build?
Click to expand...
Click to collapse
Dejvid50 said:
I hope will be for A-only too.. many people would welcome it . :silly:
Click to expand...
Click to collapse
Done, check OP. I can't spare an A-only device to test it though, try at your own risk.
EDIT: might have to wait for SF to mirror the file...

AndyYan said:
Done, check OP. I can't spare an A-only device to test it though, try at your own risk.
EDIT: might have to wait for SF to mirror the file...
Click to expand...
Click to collapse
Thank you very much!!! Will test and give feedback....ist it build on latest Phhs V111?

Cool, which one is the a-only? ...it's not clearly writen

odysseus84 said:
Cool, which one is the a-only? ...it's not clearly writen
Click to expand...
Click to collapse
I thought it's the avN one. (Didn't boot on my phone.)

As of now I've received 1 report of A-only booting up alright. Although I don't take hardware-related bug reports, it's advised to post whether it boots on your device so as to let other users know.
Lecterr said:
Thank you very much!!! Will test and give feedback....ist it build on latest Phhs V111?
Click to expand...
Click to collapse
Not sure how I could determine that, but it's fresh synced.
odysseus84 said:
Cool, which one is the a-only? ...it's not clearly writen
Click to expand...
Click to collapse
avN, bvN - not clear enough?

Thanks again for A-only build...tested and works great on MiMax3 with stock PIE vendor!!!
Only thing not working is equalizer for audio, opens a empty screen but no FC or error message...but ringtone, music etc. working.

Just tested this on a Nokia 7 Plus (B2N) with the bvN images. Everything seems to work just fine, except for VoLTE/VoWiFi (which I don't care that much about anyways...).
Voice calls, Camera, MusicFX, Fingerprint, Bluetooth, LTE, all work as expected. Will come back after some usage with more info about battery life and such.
@AndyYan Awesome stuff, Andy! Thank you for this guide--will try to build it myself soon enough after I run your build for a few days to test.
By the way, do you think this will get OTA updates from LineageOS? The updater seems to work as expected, but haven't seen any new options there yet.
Thanks again!

MadalinC said:
By the way, do you think this will get OTA updates from LineageOS? The updater seems to work as expected, but haven't seen any new options there yet.
Click to expand...
Click to collapse
Nope, LOS team even stated explicitly they won't be making any official GSIs.

AndyYan said:
Nope, LOS team even stated explicitly they won't be making any official GSIs.
Click to expand...
Click to collapse
Oh, that is very unfortunate. It is running really smooth as a GSI
So that means that each security patch comes out, I will need to start from scratch and reflash the image? That would make it a bit a pain each month
Anyways, thanks for the quick reply!

On the Galaxy S9: I dirty flashed it over vanilla phh 111 to see if it boots. It did with the usual force close of course.
Then I wiped and reflashed. But stuck at the boot animation. The splash screen was there for a half century too... my guess is the ramdisk stoff from the kernel. there are some other Kernel version I will try those later.

MadalinC said:
So that means that each security patch comes out, I will need to start from scratch and reflash the image?
Click to expand...
Click to collapse
Just flash the image on top (along with whatever mods you're using), no wipe needed. It works like flashing ROMs on a regular A-only device.

AndyYan said:
Just flash the image on top (along with whatever mods you're using), no wipe needed. It works like flashing ROMs on a regular A-only device.
Click to expand...
Click to collapse
Any chance of arm-a LOS16 build?

AndyYan said:
Done, check OP. I can't spare an A-only device to test it though, try at your own risk.
EDIT: might have to wait for SF to mirror the file...
Click to expand...
Click to collapse
Now I'm busy, at night I will try to flash and will report. Thanks for your work
EDIT: Ok, so I was try to flash on Huawei P10 Lite with OpenGapps, and can't boot, no logo, just goes to recovery, that's all.. I was WIPE system, data, cache, dalvik cache

Lecterr said:
Thanks again for A-only build...tested and works great on MiMax3 with stock PIE vendor!!!
Only thing not working is equalizer for audio, opens a empty screen but no FC or error message...but ringtone, music etc. working.
Click to expand...
Click to collapse
do you mind sharing the instructions for flashing the gsi? im on the latest pie beta on my max3.

drxllxffxct said:
do you mind sharing the instructions for flashing the gsi? im on the latest pie beta on my max3.
Click to expand...
Click to collapse
Do u have TWRP recovery?

Finally there's a LOS 16 GSI! I have been looking to try to compile my own with phh build script.
Sorry which one should I use _avN or _bvN if I have an A Only Arm64 (Wayne).
I tried to flash the _avN and got stuck at the Mi logo.
Thank you very much to do the work.
Sent from my Mi MIX 2 using XDA Labs

Boots on Razer phone 1 but no wifi or data. Everything else seems to work. Thank you for the rom (no wifi or data razer phone problem).

[RECOVERY] Official TWRP 3.3.1 for Moto G7 Plus [lake]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp for short, is a custom recovery built with ease of use and customization in mind. It's a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
This device has 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
NOTE:
Decryption of data works when fastboot booting TWRP AND when permanently installing TWRP
Installation
To temporarily boot this recovery:
Code:
fastboot boot twrp-[b]build-version[/b]-lake.img
To permanently install it:
Temporarily boot twrp
Place the twrp-installer zip on your internal/external storage, or push to /sdcard or /external_sd using adb:
Code:
adb push twrp-installer-[b]build-version[/b]-lake.zip /sdcard (or /external_sd)
Tap Install -> Navigate to /sdcard or /external_sd and select the twrp-installer -> Swipe to install
Reboot recovery. NOTE: if you had Magisk installed previously, be sure to flash again before rebooting to System
NOTE: you can flash the twrp-installer zip directly in Magisk Manager as a module to install and/or update TWRP!
NOTE: Currently, there is no official twrp-installer zip, but there will be for the next official update. However, you can use the "unofficial" twrp-installer for the time being as it is built using the same sources
Downloads
• TWRP (Official) || https://twrp.me/motorola/motorolamotog7plus.html
• TWRP (Unofficial) || twrp-3.3.1-lake-Q-v1.img
• INSTALLER || twrp-installer-3.3.1-lake-Q-v1.zip
NOTE: The unofficial twrp.img and twrp-installer.zip have been updated for Stock Q and Q based custom ROM's. They may also work on all Pie ROM's (is anyone still using Pie?) as well but is untested
XDA:DevDB Information
TeamWin Recovery Project 3.3.1, Tool/Utility for the Moto G7 Plus
Contributors
Jleeblanch
Source Code: https://github.com/TeamWin/android_device_motorola_lake
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-07-23
Current Beta Version: 3.3.1
Beta Release Date: 2019-05-11
Created 2019-05-14
Last Updated 2020-04-03

Reserved

Treble support ?

Laercio_lalau said:
Treble support ?
Click to expand...
Click to collapse
Yes, of course. The device comes fully treble enabled, so it wouldn't make sense to build TWRP without supporting it. I'm sure it'll need some tweaks here and there and I gotta add in decryption support. It's not that it's broken, I just haven't implemented it yet. I wanted to get a working build up for at least flashing Magisk and GSI's.

Jleeblanch said:
Yes, of course. The device comes fully treble enabled, so it wouldn't make sense to build TWRP without supporting it. I'm sure it'll need some tweaks here and there and I gotta add in decryption support. It's not that it's broken, I just haven't implemented it yet. I wanted to get a working build up for at least flashing Magisk and GSI's.
Click to expand...
Click to collapse
so does it support GSI? It would be good news Bro

Laercio_lalau said:
so does it support GSI? It would be good news Bro
Click to expand...
Click to collapse
Yes, absolutely. I do need to update the twrp fstab a little for our device but it does support flashing system and vendor images. GSI's only contain a system.img, so you're good to go!
Again tho, until I implement decryption support, backups of /data and /sdcard (internal storage) aren't possible.

Hey guys,
I've not installed TWRP for a long time, I've been using the same phone (Nextbit Robin) almost two years.
Do I follow this guide to install this? https://www.xda-developers.com/how-to-install-twrp/
Using the instructions above?

Tomato_Jam said:
Hey guys,
I've not installed TWRP for a long time, I've been using the same phone (Nextbit Robin) almost two years.
Do I follow this guide to install this? https://www.xda-developers.com/how-to-install-twrp/
Using the instructions above?
Click to expand...
Click to collapse
The important thing NOT to follow at that link (which otherwise seems to have good info) is DON'T 'fastboot flash recovery twrp.img' but instead do 'fastboot boot twrp.img' to only boot it initially (notice the words 'flash' and 'recovery' aren't in there), after which there is a new way within TWRP to fully install it. The reason is because there is no longer a recovery partition in the newer A/B-slotted devices including G7+, so if you fastboot flash the old way it could brick your device. So just follow the instructions in OP of this thread once you get to the 'Install via ADB' section.
Edit: another thing is that touch isn't working in current version after installing twrp in latest firmware versions (but does work when booted), also as pointed out in OP decryption still isn't added so can't do full nandroid backups or work with internal storage.

Okay, thanks.
Going to give it a go shortly.

will it make its way to the 'official' download page? https://twrp.me/Devices/Motorola/

I must be doing something wrong, I have a couple of ideas but I'm afraid to try any of them in case I brick it.
I am getting FAILED (remote failure)
C:\G7Plus>adb reboot bootloader
C:\G7Plus>fastboot boot twrp-3.3.0-lake.img
downloading 'boot.img'...
OKAY [ 1.576s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 1.607s
Click to expand...
Click to collapse
Model
moto g7 plus XT1965-3
Build number
PPW29.98-28

Tomato_Jam said:
I must be doing something wrong, I have a couple of ideas but I'm afraid to try any of them in case I brick it.
I am getting FAILED (remote failure)
Model
moto g7 plus XT1965-3
Build number
PPW29.98-28
Click to expand...
Click to collapse
Did you unlock the bootloader?

washoq said:
Did you unlock the bootloader?
Click to expand...
Click to collapse
No, I did not
It has been a while since I have rooted a phone. And even then i think I have only done it 2-3 times altogether.
Thanks.

Tomato_Jam said:
No, I did not
It has been a while since I have rooted a phone. And even then i think I have only done it 2-3 times altogether.
Thanks.
Click to expand...
Click to collapse
If you need the link where to unlock bootloader on Motorola phones:
https://support.motorola.com/us/en/bootloader

Dahenjo said:
If you need the link where to unlock bootloader on Motorola phones:
https://support.motorola.com/us/en/bootloader
Click to expand...
Click to collapse
Thanks

so pointless until touch support i am guessing

supergear said:
so pointless until touch support i am guessing
Click to expand...
Click to collapse
Not pointless, and besides touch was working fine up until PPWS29.98-66-2 was released. I've since fixed touch in the latest firmware.
AFH Download -> twrp-3.3.1-v3-lake-jlb.img
md5sum = 008d4434ada4b6b68034dd19b2d199b3
I'll update the OP accordingly this evening.

Decryption is planned to get implemented in TWRP? Is it (easily) possible to run the device without encryption, while keeping the possibility to do OTA updates?
Edit: Hey, since when does Motorola stop delivering OTA updates to unlocked devices? That's not what I know from Moto G2, Moto X Play, Moto Z Play. All of them did receive and install OTA updates fine having unlocked bootloader, but the Moto G7 plus shows that it would not receive OTA updates anymore!
Edit2: Maybe they just put that warning in place but don't mean it. They wrote it would still be possible as usual:
https://support.motorola.com/us/en/products/bootloader-unlock/documents/MS91999
Unlocking your bootloader does not affect your eligibility to receive over-the-air (OTA) upgrades from Motorola. Upgrade packages to new versions of Android will be pushed to all eligible devices, regardless of their bootloader locking status.
Click to expand...
Click to collapse

Hallo ,
Have the same experiance , no April Update for Moto 7Plus over OTA reteu2 channel, nothing.... have flash self ... on my phone only open bootloader and later Magisk for root... not more...
Hope TWRP come the next time with encryption...thanks on this way for the dev's

tag68 said:
Decryption is planned to get implemented in TWRP? Is it (easily) possible to run the device without encryption, while keeping the possibility to do OTA updates?
Edit: Hey, since when does Motorola stop delivering OTA updates to unlocked devices? That's not what I know from Moto G2, Moto X Play, Moto Z Play. All of them did receive and install OTA updates fine having unlocked bootloader, but the Moto G7 plus shows that it would not receive OTA updates anymore!
Edit2: Maybe they just put that warning in place but don't mean it. They wrote it would still be possible as usual:
https://support.motorola.com/us/en/products/bootloader-unlock/documents/MS91999
Click to expand...
Click to collapse
Same here... "System integrity compromised" and I only unlocked the bootloader, nothing else

Better Mobile App

welcome