[ROM][UNOFFICIAL][12][Moto G6][ali]LineageOS 19.1 by FWieP

[Brunight]

Hi guys! I was using another ROM (Resurrection Remix) but suddenly it started bootlooping. I have Official LOS in my Moto G5 (Cedric) and I really liked it, so I decided to use LOS in the G6 Ali as well. I installed the newest TWRP64 (provided in some answers above), flashed this ROM with provided GApps, but after booting to system, LOS loads for aprox. 10 seconds, freezes and restarts over and over again. Don't know if this is considered a bootloop.
Tried flashing ROM without GApps, same.
Wiped literally everything, same.
The only thing that got close to work was altering `/data` filesystem from f2fs to ext4. With this, booting to system leads to a screen saying "Unsuccessful decryption".
Tried flashing Stock, it boots normally, then reinstalling TWRP and flashing your ROM, same error.
Can someone please help me? Or have I bricked my phone for good?
My Moto G6 seems to be XT1925-3.

EDIT: Forgot to mention, I also tried with your LOS 18.1 ROM with OpenGApps, same :/

 

[UserBrulate]

Hi guys! I was using another ROM (Resurrection Remix) but suddenly it started bootlooping. I have Official LOS in my Moto G5 (Cedric) and I really liked it, so I decided to use LOS in the G6 Ali as well. I installed the newest TWRP64 (provided in some answers above), flashed this ROM with provided GApps, but after booting to system, LOS loads for aprox. 10 seconds, freezes and restarts over and over again. Don't know if this is considered a bootloop.
Tried flashing ROM without GApps, same.
Wiped literally everything, same.
The only thing that got close to work was altering `/data` filesystem from f2fs to ext4. With this, booting to system leads to a screen saying "Unsuccessful decryption".
Tried flashing Stock, it boots normally, then reinstalling TWRP and flashing your ROM, same error.
Can someone please help me? Or have I bricked my phone for good?
My Moto G6 seems to be XT1925-3.

EDIT: Forgot to mention, I also tried with your LOS 18.1 ROM with OpenGApps, same :/

My answer is not the dot in cercle, but why Gapps, Aurora store market is gratefully well, only instead of chrome you follow edge from microsoft and tka, music, etc. from GitHub and aight and toast for the thread. At first u should format data with word YES for accept it. Than wipe cache,system, and data.
If you r so addictive to the owner use better PixelExperience for Moto G6 [ali]

Download DM-verity Forced Encryption Disabler for any TWRP Supported device

Dm-verity check. It prevents modifications on an Android device. In this post, we will provide you with certain encryption disablers. With the help of those, you can by-pass Dm-verity. You can download Dm-verity Forced Encryption Disabler if you want to modify your Android device without any...

www.getdroidtips.com

 

[jonshipman]

Doesn't want to run Mario Kart Tour, a 64-bit only application. Checking here to see if it's a lib error or a string sniff (build.prop.fingerprint was changed to the stock one from my Moto Z3 Play - which runs MKT fine)

 

[rotorline]

@fwiep Thanks for this update to Lineage for the G6. I use this phone as a backup and it's great that you'll take the time add the security patches for us

 

[VenkmanP]

PSA - Don't update to an android 12.x ROM on the G6 if you use Microsoft Intune.

There's a bug with Intune on android 12:

Android devices lose access to Intune-managed resources after upgrading to Android 12 (#5075) · Issues · LineageOS / issues / android · GitLab

Expected Behavior Microsoft Intune should create professional profile and connect to company intune server to be able to download specific software...

gitlab.com

Re: Known Issue: Android devices lose access to Intune-managed resources after upgrading to Android

We appreciate everyone’s patience and the feedback! Sharing a few updates below – Working with Google and OPPO/OnePlus - OPPO/OnePlus engineering believes they've identified the issue within their OS. Last we heard from them, a fix will be available within the next OTA update for S devices and...

techcommunity.microsoft.com

Which appears to be fixed on a ROM-by-ROM basis by manufacturers and the community, meaning some ROMs work and some don't.

Example:
https://www.reddit.com/r/LineageOS/comments/usrf7b
I tried all three of the 12.1 ROMs we have for the G6 and Intune is broken on all of them.

Went back to an 11-based ROM and it works fine.

 

[AshleyTheMetalhead]

can i just say, thank you for this. it installed seamlessly on my Moto G6, working really well.

 

[Wheeljack2k]

Had tried the OTA update mid December for the first time (going from Nov to Dec version). The update worked flawlessly going through TWRP without any user input needed totally user friendly and GApps was still intact afterwards.
Great job!

 

[techdad24]

Thanks for the ROM - I tried cdroid and pixelexperience but ran into wifi and GApps issues - this worked great. Only issue was Magisk - in the end I just double-clicked the apk file and was able to install it (sideload and twrp install ran but it never showed up as an app).

 

[Ampheres]

Hello,
first of all, thanks for the ROM, flashed it recently without problems. It runs really well but it doesn't track data usage on my device, neither wifi, nor mobile, always showing 0 Bytes used. Don't really know if it's a Lineage issue or a ROM specific one.
Has anyone else experienced this issue and found a solution?
Ty in advance

 

[fwiep]

... the ROM ... doesn't track data usage on my device, neither wifi, nor mobile, always showing 0 Bytes used. Don't really know if it's a Lineage issue or a ROM specific one. Has anyone else experienced this issue and found a solution?

Hi,

Thanks for pointing this out. I experience the same behavior: data measurements are always set to 0 bytes.

For now, I don't have a clue as where to look for fixing this issue. I'll put it up on the list of known bugs. If I do come across a potential solution, I'll definitely try to implement it. If anyone else can point me in the right direction, please do!

UPDATE: After consulting @brunogroa, the core developer who has made these builds possible, the problem seems to be in the kernel. There, BPF is used to take these measurements, but it is turned off and bypassed for various reasons. So, it's probably not going to be fixed soon/at all. Sorry .

Kind regards,
FWieP

 

[Ampheres]

Hi,

Thanks for pointing this out. I experience the same behavior: data measurements are always set to 0 bytes.

For now, I don't have a clue as where to look for fixing this issue. I'll put it up on the list of known bugs. If I do come across a potential solution, I'll definitely try to implement it. If anyone else can point me in the right direction, please do!

UPDATE: After consulting @brunogroa, the core developer who has made these builds possible, the problem seems to be in the kernel. There, BPF is used to take these measurements, but it is turned off and bypassed for various reasons. So, it's probably not going to be fixed soon/at all. Sorry .

Kind regards,
FWieP

Very unfortunate but thanks for the response nonetheless

 

[vernr]

Data measurement works on the Lineage 18.1 version. At least it does on my phone.

 

[fwiep]

Data measurement works on the Lineage 18.1 version. At least it does on my phone.

Indeed. Only the Android 12 kernel has BPF disabled, according to the developer who ported it.

Kind regards,
FWieP

 

[Tsumetaay]

this rom is absolutely insane, still wondering how the SoC runs Android 12 so perfectly.
for my use everything works as expected, amazing job!

if anyone is getting annoyed by some UI lag (mostly open/close animations), use SmartPack to set CPU governor to performance (if you want smooth animations and doesnt care about battery).

 

[vernr]

Yes. your Lineage 18.1 and 19.1 builds are both great roms. Thanks to @fwiep and the others for keeping Moto g6 ali current for us.

 

[old-mobile]

Hello,
first of all impressive rom - very smooth on this old phone where I have not found and glitches.

To my issue:
I tried to update via OTA an encrypted G6 but has not worked.

From Dec to Jan version it was stuck at the bootloader - I needed to flash TWRP 3.7.0_9.-0 again. At the initial Dec version installation / first startup I have chosen to update recovery during the update process.

To get a functional phone I wiped the G6 and installed Jan version.

A few days ago I started the OTA update for the Feb update and this time the installation ran through TWRP and the phone rebooted and asked me as usual to enter the password. This is accepted and then the boot animation is running infinitely without ending. After some time the phone restarts, but it is in the same loop - password accepted, infinitely start animation and restart.

During the TWRP I saw error messages that /data cannot be mounted - I guess because of encryption.

Any chance to resolve this infinitely boot without wipe/new install? I have no important data on the phone so no too sophisticated recovery required. But if it easy possible I would try it.

And:
So my question is if there is a way to use OTA with encryption enabled?
If not, how to update with encryption enabled?
Or is there no way to enable encryption if I want to update the phone regularly.

Thanks for your help

 

[fwiep]

So my question is if there is a way to use OTA with encryption enabled? If not, how to update with encryption enabled? Or is there no way to enable encryption if I want to update the phone regularly.

Hello,

My own G6 is currently not encrypted. To be honest, I have not tried updating while encryption was active. I would have to wipe the device clean and install, for example, the January build. Then enable encryption and perform the OTA update to February build. I don't want to do that just yet - it's my daily driver device.

So, in a nutshell: I don't know whether the phone can be encrypted and receive my OTA updates at the same time. Sorry.

Are there any other users out there that installed my recent (OTA-) builds and have encryption enabled? What are your experiences?

Thanks,
FWieP

 

[Skippy12359]

Hello,

My own G6 is currently not encrypted. To be honest, I have not tried updating while encryption was active. I would have to wipe the device clean and install, for example, the January build. Then enable encryption and perform the OTA update to February build. I don't want to do that just yet - it's my daily driver device.

So, in a nutshell: I don't know whether the phone can be encrypted and receive my OTA updates at the same time. Sorry.

Are there any other users out there that installed my recent (OTA-) builds and have encryption enabled? What are your experiences?

Thanks,
FWieP

I use your ROM as a daily driver and many thanks for the updates. I never update through OTAs as I found it's easy to just dl the ROM and dirty flash. Also just don't care if it's encrypted or not for my uses. I've had my G6 since they were released so flashed ROMs more times than I can count. Still a great phone and hope to keep it updated as long as possible...

 

[old-mobile]

Hello,

My own G6 is currently not encrypted. To be honest, I have not tried updating while encryption was active. I would have to wipe the device clean and install, for example, the January build. Then enable encryption and perform the OTA update to February build. I don't want to do that just yet - it's my daily driver device.

So, in a nutshell: I don't know whether the phone can be encrypted and receive my OTA updates at the same time. Sorry.

Are there any other users out there that installed my recent (OTA-) builds and have encryption enabled? What are your experiences?

Thanks,
FWieP

Hi FWieP,
Understood and clearly not so relevant that it is worth to crash/wipe your daily driver.

If you provide me the link to the January version I can try it by myself and report here.

But a short Google search gave some hits with TWRP and Android 12 encryption issues with OTA and boot loops. So it seems to be a general issue.

Best regards
old-mobile

 

[fwiep]

If you provide me the link to the January version I can try it by myself and report here.

Here you go, and thanks for digging into this.

lineage-19.1-20230112-UNOFFICIAL-ali.zip
sha256sum: f9ab1f76dae559c9dc9c6de5ec549579a5a0106a79d9e1d66ee53a121b1353ce

Kind regards,
FWieP