[ROM][OFFICIAL][LAKE] LineageOS 17.1 for Moto G7 Plus [weeklies]

[Jleeblanch]

/*
* 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.
*/

LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device.

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

Introduction:

This is the Official LineageOS 17.1 thread for the Moto G7 Plus, codename lake.

Information:

• Official Wiki || https://wiki.lineageos.org/devices/lake

Installation

• How-to || https://wiki.lineageos.org/devices/lake/install

Downloads:

• Builds || https://download.lineageos.org/lake

XDA:DevDB Information
LineageOS 17.1, ROM for the Moto G7 Plus

Contributors
Jleeblanch
Source Code: https://github.com/LineageOS

ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Android 10 (Q) Stock Firmware

Version Information
Status: Nightly

Created 2020-04-03
Last Updated 2020-04-03

 

[Jleeblanch]

Reserved

 

[Jleeblanch]

Reserved

 

[rutger465]

many thanks! i couldnt get version 16 to work going from stock android 10 but this works like a charm

 

[Laercio_lalau]

Good job bro

 

[Jairsantana]

Really good job @Jleeblanch!!!!!

 

[bamless]

The installation instructions don't seem to work for my device. I tried the installation 2 times and both times my GPT got wrecked and I needed to reflash the stock ROM. Can someone who installed the ROM please tell me the steps they've taken so I can try to understand what I did wrong?
I'm on a Moto G7 Plus reteu BTW.

 

[chincheta0815]

The installation instructions don't seem to work for my device. I tried the installation 2 times and both times my GPT got wrecked and I needed to reflash the stock ROM. Can someone who installed the ROM please tell me the steps they've taken so I can try to understand what I did wrong?
I'm on a Moto G7 Plus reteu BTW.

I got stuck also installing lineageos 17.1 on the same device following the steps mentioned in the installation instructions. I came from stock.

The changes that helped:
1. I used copy-partiotions-AB.zip.
2. I did not flash the lineage-recovery, but TWRP for the LineageOS images.
3. I installed GApps Pico. Others would not let me login to Google Services.

For me it seems that there is an issue with the lineage recovery: I flashed lineageos 20200402 and then updated to 20200403 via the built in updater. After the reboot the device was bricked and I had to reflash. This brick was also caused using the lineage recovery in step 2 mentioned above. If there is an issue with using copy-partitions-AB.zip instead of copy-partitions.zip, I cannot tell. I peeked into Jleeblanch's Unofficial Lineage 16 thread thinking there should not be that much of a difference.

Any comments on how to make lineage OTA updates work would help me. Is there a bug in lineageos right now or am I doing something wrong?

 

[jadephyre]

Awesome, I just got this device a week ago and was hoping someone would make an official version for it :laugh:

 

[chincheta0815]

For me it seems that there is an issue with the lineage recovery: I flashed lineageos 20200402 and then updated to 20200403 via the built in updater. After the reboot the device was bricked and I had to reflash. This brick was also caused using the lineage recovery in step 2 mentioned above. If there is an issue with using copy-partitions-AB.zip instead of copy-partitions.zip, I cannot tell. I peeked into Jleeblanch's Unofficial Lineage 16 thread thinking there should not be that much of a difference.

I have to add & correct to myself:
- installing was only possible when I used twrp until lineageos was flashed.
- copy-partitions.zip as mentioned in the lake install instructions did work, but flashing GApps (not matter which) did result in a black screen while going through the wizard, using copy-partitions-AB.zip work well.

 

[rutger465]

Anyone has Android Auto working for this rom? i had it fail with all roms exept the Stock one

 

[jadephyre]

Anyone has Android Auto working for this rom? i had it fail with all roms exept the Stock one

My guess would be no, same probably goes for voice match which has never worked for me on custom Android 10 roms on other devices.

 

[gerchla]

First of all: Thanks a lot for all the effort in making this ROM!

My questions would be:
- does the ROM include some own recovery? I if flash TWRP, then do a sideload of Lineageos, I get into some Lineageos-recovery when rebooting recovery.
- how does rooting the phone work? simply flashing/sideloading latest magisk after flashing Lineageos?

 

[Jleeblanch]

The installation instructions don't seem to work for my device. I tried the installation 2 times and both times my GPT got wrecked and I needed to reflash the stock ROM. Can someone who installed the ROM please tell me the steps they've taken so I can try to understand what I did wrong?
I'm on a Moto G7 Plus reteu BTW.

Any build after the 20200405 (so 20200406+) won't have this issue. I apologize for not catching this sooner. With TWRP working as good as it does on this device, I never paid much attention to Lineage Recovery.

I got stuck also installing lineageos 17.1 on the same device following the steps mentioned in the installation instructions. I came from stock.

The changes that helped:
1. I used copy-partiotions-AB.zip.
2. I did not flash the lineage-recovery, but TWRP for the LineageOS images.
3. I installed GApps Pico. Others would not let me login to Google Services.

For me it seems that there is an issue with the lineage recovery: I flashed lineageos 20200402 and then updated to 20200403 via the built in updater. After the reboot the device was bricked and I had to reflash. This brick was also caused using the lineage recovery in step 2 mentioned above. If there is an issue with using copy-partitions-AB.zip instead of copy-partitions.zip, I cannot tell. I peeked into Jleeblanch's Unofficial Lineage 16 thread thinking there should not be that much of a difference.

Any comments on how to make lineage OTA updates work would help me. Is there a bug in lineageos right now or am I doing something wrong?

Nope, you weren't doing anything wrong. Read my reply above. Any build from April 6th on shouldn't have any issues. I spent the last couple days figuring this out lol

My guess would be no, same probably goes for voice match which has never worked for me on custom Android 10 roms on other devices.

Voice match should work as long as GApps is installed. However, if you're referring to hotword detection when the screen is off, then no. It's currently not fully implemented but I have had it working on Lake during our initial Lineage 17.1 bring up but unfortunately it didn't work on all sdm660 devices at the time. I'll work on decommonizing sound trigger in the near future, so stay tuned.

First of all: Thanks a lot for all the effort in making this ROM!

My questions would be:
- does the ROM include some own recovery? I if flash TWRP, then do a sideload of Lineageos, I get into some Lineageos-recovery when rebooting recovery.
- how does rooting the phone work? simply flashing/sideloading latest magisk after flashing Lineageos?

Yes, Lineage Recovery is included by default (as well as on the official downloads page). The reason you're seeing it after you've flashed twrp to boot and then flashed the lineageos zip is because this device doesn't have an actual recovery partition. The recovery is part of the boot.img, so once you flash lineage, you're essentially overwriting twrp. To keep twrp permanently, you would also need to sideload the twrp-intaller zip from the Official twrp (I recently updated the official thread with newer unofficial version until new official versions are built) AFTER you've installed LineageOS.

If you also want to install GApps and root (Magisk), then reboot recovery and sideload them before rebooting to Lineage.

 

[SirR]

The new Roms works very well, thank you A LOT for that!

Tried an automatic update yesterday (from system setup menu) and had a short moment of panic: device did not boot anymore. I could save the situation by rewriting GPT and bootloader from the Stock image (10.0), but it was a close call!

The GPT delivered had quite different partition names / tables.

Why replacing bootloader and gpt? afaik if you start installation from scratch using twrp the partition names etc. do not change.

Will keep using twrp (sideloading it) for updates in the future.

 

[chincheta0815]

Nope, you weren't doing anything wrong. Read my reply above. Any build from April 6th on shouldn't have any issues. I spent the last couple days figuring this out lol

Well, for me it did not took days, but turned me mad the same way I think ;o)

Just a quick quick question:
Will I just have to reflash the respective build you mention or will a simple OTA update do the same?
And very important: Will an OTA update run through and not hang in the bootloader, which was an issue also. (Stucked in a scrambled bootloader causing a stock reflash...)

Thanks a lot!

 

[mmxthorn]

Moto Gestures?

 

[jadephyre]

Moto Gestures?

Moto Gestures are not part of AOSP, so no.

 

[Jleeblanch]

Well, for me it did not took days, but turned me mad the same way I think ;o)

Just a quick quick question:
Will I just have to reflash the respective build you mention or will a simple OTA update do the same?
And very important: Will an OTA update run through and not hang in the bootloader, which was an issue also. (Stucked in a scrambled bootloader causing a stock reflash...)

Thanks a lot!

Starting with the next nightly (20200406) you'll be able to OTA update without any issues. Just flash the next build that gets released in twrp and after that you'll be fine. The builds don't flash the bootloader, but bootctrl and gpt-utils do as they are past of what makes the magic of "seamless updates" work, which is why previous builds were wrecking the gpt table.

Moto Gestures?

Check > Settings > System > Advanced > Moto Gestures

Also, fingerprint swipe for notifications is include (disabled by default) and also found in the same place as stock (> Settings > System > Gestures)

 

[infected36]

Can I flash this over an older build of 17.1? I have the March 14th one installed and it can't find the OTA update, so I'm wondering if I can just flash this new one over it, then flash twrp and magisk without losing anything.