• If you are experiencing issues logging in, we moved to a new and more secure software and older account passwords were not able to be migrated. We recommend trying to reset your password, then contacting us if there are issues.
  • Nearly done! Migration cleanup is mostly done. There are a small number of issues left that we continue to work on, but all the heavy lifting is done. We still would love to hear feedback over at this thread and also check out the new XDA app! Thanks and we hope you enjoy the new forums, and thanks for your support of XDA <3

[ROM][UNOFFICIAL]LineageOS-15.1[Evert][Moto G6 Plus]

rahulsnair

Inactive Recognized Developer
May 7, 2013
1,001
2,661
0
Kottarakkara
LIneageOS is a free, community built, after-market firmware distribution of Android re-branded CyanogeMod, which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
 * 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 based on the Android Open Source Project and CyanogenMod with extra contributions from many people within the Android community. All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS please visit Gerrit Code Review.

Warning!!!
  • BackUp EFS partition before installing. .If you lose IMEI , use this backup to retrieve it in future.

Installation
  • Boot the newest TWRP .img
  • Flash copy-partitions-AB.zip from second post. (This will prevent device from getting bricked if you are coming from stock rom for the first time. It takes a backup of active slot to inactive slot)
  • In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
  • ADB sideload the newest build
  • Reboot to fastboot and do fastboot -w via terminal
  • Boot into "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
  • (Optionally) Flash GApps - Only MindTheGApps arm64 are compatible, OpenGApps are not compatible with A/B yet: MindTheGApps.
  • (Optionally) Flash SU - you'll need to turn it on from in developer settings after first boot Lineage OS SU Addon. - Magisk works fine, though is not supported.
  • Reboot
Downloads

Warning
If you are coming from stock ROM and it's your first time flashing lineage, flash copy-partition zip (See second post) unless your device will brick and I'm not responsible

- LineageOS : Unoffical Build
- TWRP : Get here

Bugs
  • bluetooth calling

Reporting bugs
  • DO NOT report bugs if you're running a custom kernel
  • DO NOT report bugs if you've modifies system files
  • DO NOT report bugs if you've installed xposed and/or other mods
  • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    Code:
    adb logcat > logcat.txt
    Code:
    adb shell dmesg > dmesg.txt
  • If it is a random reboot, grab kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    Code:
    adb shell cat /sys/fs/pstore/console-ramoops
  • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log

Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues or bugs reported in the lastest 5 pages of this thread. Any bug not reported in the bug report format below may be ignored.
Code:
Phone Informations
* LineageOS version
* Gapps version
What you did:
* Wipe data: y/n
* Upgrade from previous official cm build: y/n
* Restore with titanium backup: y/n
You're using (if yes write which one) :
* Task killer
* Phone cleaner / Battery enhancer apps
* Non-stock kernel
* Modified kernel settings
* Other mods
Bug info:
* Last version it worked on
* Repro steps
F.A.Q.
  • ROOT! ROOT! Give me root or i'll die!!! Where root is???
    First of all DO NOT flash any SuperSu/SuperUser/SuperMan zip package to get root. Go to Settings>Developement Settings>Root access and select "Apps Only"
  • Why no nightly today?
    Build failed. Check again tomorrow
  • When do I have to wipe data?
    You must wipe data only when you're switching from another rom or migrating to Snapshot branch from Nightly and vice versa. You don't need to wipe data when you update in the same release channe (this applies to 13.0 -> 14.1 upgrades too)
  • Will you add <insert awesome feature here>?
    I won't. If you write it, submit a commit to gerrit, where it will be reviewed.

The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!

Kernel Source : Here

A big thanks to @erfanoabdi to kick start the development.


XDA:DevDB Information
LineageOS, ROM for the Moto G6

Contributors
rahulsnair, erfanoabdi
Source Code: https://github.com/LineageOS

ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP
Based On: LineageOS

Version Information
Status: Beta

Created 2018-08-11
Last Updated 2018-08-11
 

Coldstream

Senior Member
May 23, 2010
120
45
0
Enschede
Already noticed this rom and the new TWRP on his androidfilehost and saw it posted on another site too, might try it soon
However, what exactly does the AB zipfile do exactly? And another question, on his AndrFilehHost he has an outdated TWRP installer Zip, is there any reason the new TWRP's are only bootable images? I'd gladly know why to stick with just booting rather then flashing TWRP?

Also thanks for the effort, i'll give the ROM a try and will report back my experiences..

edit: also, i had no problems with opengapps on treble roms, what makes it problematic for this rom?
 
Last edited:

rahulsnair

Inactive Recognized Developer
May 7, 2013
1,001
2,661
0
Kottarakkara
Already noticed this rom and the new TWRP on his androidfilehost and saw it posted on another site too, might try it soon
However, what exactly does the AB zipfile do exactly? And another question, on his AndrFilehHost he has an outdated TWRP installer Zip, is there any reason the new TWRP's are only bootable images? I'd gladly know why to stick with just booting rather then flashing TWRP?

Also thanks for the effort, i'll give the ROM a try and will report back my experiences..

edit: also, i had no problems with opengapps on treble roms, what makes it problematic for this rom?
This device is an A/B device which means it does have two slots.One will be active (running slot) and other will be used for updating system (if any OTA is available) Opengapps doesn't support A/B devices yet.
AB zipfile makes a backup of your active slot so that your device won't get bricked after flashing lineage.
 
Last edited:

Coldstream

Senior Member
May 23, 2010
120
45
0
Enschede
I know that the G6 Plus is A/B, but i don't get what the problem is with opengapps. I flashed them just fine for the treble roms i tried. The only thing i did was flash opengapps straight after the treble rom, without rebooting. It might not be fully working with A/B devices, but they surely worked for the treble roms i tried, that's why i asked. And yes, i think i didn't read it properly the first time. Now it makes sense, though i just got a script to go back to full stock ready anyways. Anyways, again big thanks to both of you.
Maybe @erfanoabdi can say something about the TWRP files? I will probably finally have some time to flash the rom with an hour or so, and gladly report back later.

edit: oops, i totally forgot something here, you are probably talking about OTA lineage updates, while i was not even thinking on that. If that's the case, then it makes sense
 

Xplorer4x4

Elite Member
Mar 12, 2010
1,025
314
83
Hi.....after revert from this ROM tô stock....ill lose some thing? Ex....volte.....câmera...etc... Efs backup ok
You will loose volte I believe. You will loose the Los camera app but gain the moto camera app.

I know that the G6 Plus is A/B, but i don't get what the problem is with opengapps. I flashed them just fine for the treble roms i tried. The only thing i did was flash opengapps straight after the treble rom, without rebooting. It might not be fully working with A/B devices, but they surely worked for the treble roms i tried, that's why i asked. And yes, i think i didn't read it properly the first time. Now it makes sense, though i just got a script to go back to full stock ready anyways. Anyways, again big thanks to both of you.
Maybe @erfanoabdi can say something about the TWRP files? I will probably finally have some time to flash the rom with an hour or so, and gladly report back later.

edit: oops, i totally forgot something here, you are probably talking about OTA lineage updates, while i was not even thinking on that. If that's the case, then it makes sense
Opengapps will work it just won't survive an update.

As for twrp, they were buggy more or less. For example the first 3 builds weren't able to decrypt data on the internal SD card. That applies to the twrp zip as well. The 4th build supported decryption but had some lag. Go with the latest twrp build but it does lack mtp for example.

Sent from my moto g(6) plus using Tapatalk
 

Coldstream

Senior Member
May 23, 2010
120
45
0
Enschede
You will loose volte I believe. You will loose the Los camera app but gain the moto camera app.



Opengapps will work it just won't survive an update.

As for twrp, they were buggy more or less. For example the first 3 builds weren't able to decrypt data on the internal SD card. That applies to the twrp zip as well. The 4th build supported decryption but had some lag. Go with the latest twrp build but it does lack mtp for example.
Yeah i noticed that, but is there any specific reason to stick with fastbooting it rather then flashing? The flashable zip is a very old version, but the newer ones of the last few days might be better? Since there is no documentation with them on the androidfilehost, it's a bit of a gamble what is changed in each of his versions. I'd happily flash the latest version if possible, but it would be usefull to know if there would be any reason not to. Considering there is no new flashable zip i suspect there is at least one reason to stick to fastbooting it over flashing, but again without knowing its still a gamble.

Anyways, every progress done on the G6 Plus is more then welcome, so i'm more then happy so far :)
 

FAR_

Member
Jun 24, 2018
8
6
0
Do you mind upload the ROM to an alternative file hosting website?
AFH is really slow even with an gigabit internet connection and it always ends up as Failed - Network error.
 

Coldstream

Senior Member
May 23, 2010
120
45
0
Enschede
The SU addon can't be flashed, some error in path symbolic something with a sh script, will dump log later i don't have a PC around for now.
Also the LineageOS recovery can't handle the encryption.

Moto app (with gestures and Moto screen) will works with custom roms? I never had Motorola phone before. Good to see that development of g6 plus starts.
The Moto app itself won't work but the actions are intergrated.

Editie: noticed the SU addon is removed from the OP, i'd suggest keeping us updated here aswell because i'm sure others reported it, but if others report it on another place then it would be much more usefull to at least keep us updated here to prevent people running in the same issues, and dumping the same logs but just on different locations? Also as it is now, obviously only ADB root can be chosen in dev settings.
 
Last edited:
  • Like
Reactions: weazie

WYPIERDAALAAC

Senior Member
Sep 3, 2012
985
682
0
Warszawa
The SU addon can't be flashed, some error in path symbolic something with a sh script, will dump log later i don't have a PC around for now.
Also the LineageOS recovery can't handle the encryption.


The Moto app itself won't work but the actions are intergrated.

Editie: noticed the SU addon is removed from the OP, i'd suggest keeping us updated here aswell because i'm sure others reported it, but if others report it on another place then it would be much more usefull to at least keep us updated here to prevent people running in the same issues, and dumping the same logs but just on different locations? Also as it is now, obviously only ADB root can be chosen in dev settings.
If I do understand right moto gestures are intergrated in system settings of lineageOS? What about face recognition ?
 

smitharro

Elite Member
Jan 2, 2012
2,629
1,711
113
Blokker
Finally! Some development going on for Evert! I'll still wait a while before unlocking the bootloader, because I'm afraid that the A/B system bricks my device. Furthermore bluetooth calling is important to me, so I hope this will be solved soon. Is everything else working so far?
 
Last edited:

Coldstream

Senior Member
May 23, 2010
120
45
0
Enschede
Finally! Some development going on for Evert! I'll still wait a while before unlocking the bootloader, because I'm afraid that the A/B system bricks my device. Is everything working so far?
If there's anything i've learned so far from the A/B system, it's a good improvement. Nothing i'd be affraid of. What makes u scared? I've ran a lot of the treble roms with different outcomes but going back to full stock is fairly easy so far and right now i'm running this rom.
Obviously i'm not going to say that you can't brick it or should take things too easy, but with just simply understanding the actions your taking it's nothing to be affraid of. Besides, when you flash stock running on A straight to B, and run into troubles with something flashed on A u can switch rather easy is my experience.
 

Xplorer4x4

Elite Member
Mar 12, 2010
1,025
314
83
Yeah i noticed that, but is there any specific reason to stick with fastbooting it rather then flashing? The flashable zip is a very old version, but the newer ones of the last few days might be better? Since there is no documentation with them on the androidfilehost, it's a bit of a gamble what is changed in each of his versions. I'd happily flash the latest version if possible, but it would be usefull to know if there would be any reason not to. Considering there is no new flashable zip i suspect there is at least one reason to stick to fastbooting it over flashing, but again without knowing its still a gamble.

Anyways, every progress done on the G6 Plus is more then welcome, so i'm more then happy so far :)
At this time the dev has had issues building an updated zip installation for twrp but it will probably be resolved soon.



The SU addon can't be flashed, some error in path symbolic something with a sh script, will dump log later i don't have a PC around for now.
Also the LineageOS recovery can't handle the encryption.


The Moto app itself won't work but the actions are intergrated.

Editie: noticed the SU addon is removed from the OP, i'd suggest keeping us updated here aswell because i'm sure others reported it, but if others report it on another place then it would be much more usefull to at least keep us updated here to prevent people running in the same issues, and dumping the same logs but just on different locations? Also as it is now, obviously only ADB root can be chosen in dev settings.
You can flash magisk 16.7 beta and root will work fine.


Finally! Some development going on for Evert! I'll still wait a while before unlocking the bootloader, because I'm afraid that the A/B system bricks my device. Furthermore bluetooth calling is important to me, so I hope this will be solved soon. Is everything else working so far?
Nothing to worry about with AB. It's a good thing.

Bluetooth calling is being worked on.



Sent from my moto g(6) plus using Tapatalk
 

martiengrandia

Senior Member
Aug 29, 2012
78
8
0
Updated process ended with ERROR: 1

When I try to flash this rom to my moto g6 plus, I get this error: error applying update: 7 (errorcode:: kInstallDeviceOpenError) Updated process ended with ERROR: 1

What's wrong here?