• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[7.1.x] LineageOS 14.1 for Moto G5 [cedric][UNOFFICIAL]

Search This thread

ektus

Senior Member
Is there anyone else having issues with the fingerprint reader? As soon as I try to set it up, the app freezes. Didn't happen with an older version (Feb 2020 or so...).
I don't know as I've never used it myself. It does work as additional home button, though.

Does it work again if you flash the old version?

Did you flash OpenGAPPS in a version bigger than pico? There's been a report a couple weeks back stating that might cause trouble as it replaces LOS system system functions.
 

nift4

Senior Member
May 22, 2019
586
200
nift4.github.io
Moto G5
F(x)tec Pro1
I don't know as I've never used it myself. It does work as additional home button, though.

Does it work again if you flash the old version?

Did you flash OpenGAPPS in a version bigger than pico? There's been a report a couple weeks back stating that might cause trouble as it replaces LOS system system functions.
Nano is still OK, micro is the very first to replace. Actually pico has it's problems too. The most stable package is and ever was nano.
 

jrkb

Member
Nov 7, 2017
5
1
Hi,
thanks for this amazing rom!
I had it installed on my Moto G5, and wanted to update it with the latest build, but something went wrong.

TL;DR; issue solved itself by restarting TWRP

Somehow i get an Error 7 when trying to flash the latest zip (lineage-14.1-20201106-UNOFFICIAL-cedric.zip) from TWRP.
I checked the md5sum, the zipfile is fine. Also I wiped data/cache/etc pretty much everything except the external sdcard, where i keep the zipfile on.
I also tried to sideload the zip with adb, but it fails with the same issue.

I somehow can't figure out where the TWRP logfile is located, but I'll just try typing it out.
The log is similar, when I try to flash from TWRP directly, but anyways this is it:

Starting ADB sideload feature...
Installing zip file '/sideload/package.zip'
Verifying zip signature...
Zip signature verified successfully.
Unmounting system...
Targe: motorola/lineage_cedric/cedric:7.1.2/NJH47F/f285ef918:userdebug/test-keys
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
PAtching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 7

What could that be?

the phone is model XT1676 type M2675 (removed battery and checked the sticker)
that should be correct, or not?

[SOLVED] just restarted TWRP ( actually only because i removed the battery to check the model number, haha) and it worked!
 
Last edited:

ektus

Senior Member
Experimental new build with December 5th, 2020 patches available

Looks like the new forum is lacking support for real headlines. Links must be encapsulated to avoid being partially converted to smileys.


The November patches haven't been merged yet, but are included here together with the December patches as can be found at time of posting on the links below.

This build is to be considered alpha, albeit there having been no bug reports on
Gerrit Topic November
and
Gerrit Topic December
yet.

I haven't installed it on my device yet.

As always, these builds don't contain any patches to closed source drivers, as those would have to be supplied by Lenovo. Who have long since stopped supporting this device.

Builds prior to September 9th, 2020 have been deleted from my dropbox to mitigate space constraints.

Use at your own risk!

Regards
Ektus.
 

Attachments

  • lineage-14.1-20201215-UNOFFICIAL-cedric.zip.md5sum.txt
    78 bytes · Views: 20
Last edited:

ektus

Senior Member
Experimental new build with January 05th, 2021 security patches available


This build is to be considered alpha, albeit there having been no bug reports on Gerrit yet. I've got it installed and running on my own device, but as of now only for a couple hours.

As always, these builds don't contain any patches to closed source drivers, as those would have to be supplied by Lenovo. Who have long since stopped supporting this device.

Builds prior to September 19th, 2020 have been deleted from my dropbox to mitigate space constraints.

Use at your own risk!

Regards
Ektus.
 

Attachments

  • lineage-14.1-20210107-UNOFFICIAL-cedric.zip.md5sum.txt
    78 bytes · Views: 17

gocin

New member
Mar 24, 2020
2
1
I'm using the October release without issue. Fingerprint works just fine. Did you try re-flashing stock Nougat and then flashing the latest build?

Hi,
after re-flashing Stock Oreo and flashing latest build it didn't work. Then I re-flashed Stock Nougat and after the October release, which worked fine. After I flashed the latest build and everything including the fingerprint reader works now. Thanks!
 
  • Like
Reactions: rahimali

rtd4

Senior Member
Jan 31, 2021
86
17
excelente trabajo pero tiene algunos detalles

acciones de moto no responden hasta pasar 3 segundos

radio fm se entrecorta señal muy debil

dpi confuso 440dpi el g5 tiene 480dpi

bateria se agota mas rapido que android 8.1 oreo

el launcher de lineageos apesta en mi opinion parece agenda de contactos es mejor usar Pixel Launcher 7.1.1-3862848

bootanimation lineage horrible es mejor bootanimation stock motorola

lo demas esta bello sigo en stock 8.1 porque no se acaba tan rapido la bateria en nougat duraba aun mas creo yo

MOD EDIT for Google Translate to English:
excellent work but has some details

motorcycle actions do not respond for 3 seconds

fm radio stutters very weak signal

confusing dpi 440dpi the g5 has 480dpi

battery drains faster than android 8.1 oreo

The lineageos launcher sucks in my opinion, it seems that the contact book is better to use Pixel Launcher 7.1.1-3862848

horrible bootanimation lineage is better motorola stock bootanimation

The rest is beautiful I'm still in stock 8.1 because it doesn't run out so fast, the nougat battery lasted even longer I think
 
Last edited by a moderator:

ektus

Senior Member
Experimental new build with February 05th, 2021 security patches available


This build is to be considered alpha, albeit there having been no bug reports on Gerrit yet. The patches from January haven't been merged yet, but are of course also included. I've got it installed and running on my own device, but as of time of posting only for a couple minutes.

As always, these builds don't contain any patches to closed source drivers, as those would have to be supplied by Lenovo. Who have long since stopped supporting this device.

Builds prior to October 7th, 2020 have been deleted from my dropbox to mitigate space constraints.

Use at your own risk!

Regards
Ektus.
 

Attachments

  • lineage-14.1-20210206-UNOFFICIAL-cedric.zip.md5sum.txt
    78 bytes · Views: 11

rtd4

Senior Member
Jan 31, 2021
86
17
Experimental new build with February 05th, 2021 security patches available


This build is to be considered alpha, albeit there having been no bug reports on Gerrit yet. The patches from January haven't been merged yet, but are of course also included. I've got it installed and running on my own device, but as of time of posting only for a couple minutes.

As always, these builds don't contain any patches to closed source drivers, as those would have to be supplied by Lenovo. Who have long since stopped supporting this device.

Builds prior to October 7th, 2020 have been deleted from my dropbox to mitigate space constraints.

Use at your own risk!

Regards
Ektus.
If Android 7.0 / 7.1 no longer receives security patches as of 10/2019, how are the current patches integrated? Is there any benefit to doing this?
 

ektus

Senior Member
Those patches are being backported to LOs 14 (and maybe even lower) in order to support devices where newer versions of Android are not supported (neither sufficently current closed source drivers nor workable open source drivers for the hardware, mostly). This doesn't apply for the G5, as newer versions of Android are available (8.1 stock and even more recent LOS variants), but those are not necessarily better. I'm still on this version as I don't want to do a fresh install or risk bricking my device. I can get one week or more of standby on one charge, too, so no need to update for endurance reasons. My configuration: Bluetooth off, Wifi off, two SIM cards, one with data always on, no apps with background activity. Very low usage.
 

rtd4

Senior Member
Jan 31, 2021
86
17
Those patches are being backported to LOs 14 (and maybe even lower) in order to support devices where newer versions of Android are not supported (neither sufficently current closed source drivers nor workable open source drivers for the hardware, mostly). This doesn't apply for the G5, as newer versions of Android are available (8.1 stock and even more recent LOS variants), but those are not necessarily better. I'm still on this version as I don't want to do a fresh install or risk bricking my device. I can get one week or more of standby on one charge, too, so no need to update for endurance reasons. My configuration: Bluetooth off, Wifi off, two SIM cards, one with data always on, no apps with background activity. Very low usage.
If there were 32bits roms it would be different it would work almot all android 8.1 stock is the best rom you can find even better than LOs 14.1 I find it ridiculous that motorola will not send more patches since 2/2019 neither android 9 g6 play if they updated it to android 9 having the same SD430 a j6 with SD425 gets android 10 a nokia 1 with mt6737m gets android 10
 

b.zill

Member
Oct 30, 2016
44
13
Thanks, Ektus, for keeping us updated. Though, since using TWRP 3.4.0.1 and recent builds (November?), there are major issues:


1. When installing a new (or old) build, TWRP reports:

Unmounting system...
Target: ...
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
unmount of /system failed (-1): Device or resource busy

[after some seconds of delay, the log continues:]
Patching system image unconditionally...
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
mount of /system failed (-1): Device or resource busy
unmount of /system failed (-1): Device or resource busy
script succeeded: result was [1.000000]


The system partition does not show up as mounted in the mounting option screen. Why would TWRP mount the system partition? What would keep it busy?

On some rare occasions, on booting into recovery, after entering the encryption password, a TWRP welcome screen appears: „Unmodified System Partition: Keep System Read only?

On repeated attempts to reinstall, at some point, it was not possibly any more to install any zip file, no specific error given.

Wiping Cache/Dalvik in the installation process reports a different sequence than when wiping separately: first, the cache is reformatted, then wiped, not vice versa. IMHO, this would render wiping (not: deleting) useless, since after formatting, there are no structures to wipe any more.

Downgrading to TWRP 3.2.1.0 seemed to resolve most of this (except the wiping order). The mount/unmount attempt of /system does not show in the logs any more.


2. Root seems to not work any more, the usual reinstallation of addon-su does not change anything. In settings, root access only shows (unmarked) options „deactivated“ and „ADB only“, which indicated that root access for apps is still set, but not available. After disabling and re-enabling developer’s options, „deactivated“ is correctly marked. Apps requiring root access do not work any more.

End of last year, this happened first and could only be resolved with numerous reinstallations of TWRP and older Lineage builds. After upgrading to the current build, the trouble starts again.

This time, after downgrading to the 2020-12-15 build, the developer options menu had been lost and needed to be reactivated. Still no root access for apps. Only after repeating the re-installation of addon-su several times, the root access reappeared.


3. When booting Lineage, the first password dialog (encryption / white keyboard) updates/reappears after a short time with a flicker while the Lineage user password dialog is omitted. When having started to type in the password, the first characters are lost in the second screen, so the dialog is reset, not just a redrawing of the screen.


4. Charging issues: Sometimes, Lineage says, it’s charging via USB, but the charging flash in the battery icon is not present and the battery effectively drains.


TWRP issues? Lineage changes that break compatibility with root? Compromised device? Lineage adopting the Redmond rule to better stick with old releases? All of the above?

Thanks for comments.
 

TheFixItMan

Senior Member
Jul 8, 2012
7,833
4,027
London
Thanks, Ektus, for keeping us updated. Though, since using TWRP 3.4.0.1 and recent builds (November?), there are major issues:


1. When installing a new (or old) build, TWRP reports:

Unmounting system...
Target: ...
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
unmount of /system failed (-1): Device or resource busy

[after some seconds of delay, the log continues:]
Patching system image unconditionally...
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
mount of /system failed (-1): Device or resource busy
unmount of /system failed (-1): Device or resource busy
script succeeded: result was [1.000000]


The system partition does not show up as mounted in the mounting option screen. Why would TWRP mount the system partition? What would keep it busy?

On some rare occasions, on booting into recovery, after entering the encryption password, a TWRP welcome screen appears: „Unmodified System Partition: Keep System Read only?

On repeated attempts to reinstall, at some point, it was not possibly any more to install any zip file, no specific error given.

Wiping Cache/Dalvik in the installation process reports a different sequence than when wiping separately: first, the cache is reformatted, then wiped, not vice versa. IMHO, this would render wiping (not: deleting) useless, since after formatting, there are no structures to wipe any more.

Downgrading to TWRP 3.2.1.0 seemed to resolve most of this (except the wiping order). The mount/unmount attempt of /system does not show in the logs any more.


2. Root seems to not work any more, the usual reinstallation of addon-su does not change anything. In settings, root access only shows (unmarked) options „deactivated“ and „ADB only“, which indicated that root access for apps is still set, but not available. After disabling and re-enabling developer’s options, „deactivated“ is correctly marked. Apps requiring root access do not work any more.

End of last year, this happened first and could only be resolved with numerous reinstallations of TWRP and older Lineage builds. After upgrading to the current build, the trouble starts again.

This time, after downgrading to the 2020-12-15 build, the developer options menu had been lost and needed to be reactivated. Still no root access for apps. Only after repeating the re-installation of addon-su several times, the root access reappeared.


3. When booting Lineage, the first password dialog (encryption / white keyboard) updates/reappears after a short time with a flicker while the Lineage user password dialog is omitted. When having started to type in the password, the first characters are lost in the second screen, so the dialog is reset, not just a redrawing of the screen.


4. Charging issues: Sometimes, Lineage says, it’s charging via USB, but the charging flash in the battery icon is not present and the battery effectively drains.


TWRP issues? Lineage changes that break compatibility with root? Compromised device? Lineage adopting the Redmond rule to better stick with old releases? All of the above?

Thanks for comments.

Use magisk to root your device - su-addon is not really maintained by lineage and isn't really the way to root your device
 

ektus

Senior Member
Might be encryption-related, which I don't use. I've had no trouble at all installing any of my builds, so can't really help there. Sorry.
My device is rooted with the su-addon, which I haven't touched since before I started building myself. I do install the new ROM and Open GApps only.
My device is installed with TWRP 3.1.1-0, as it works for everything I need.
 

ektus

Senior Member
Experimental new build with March 05th, 2021 security patches available


This build is to be considered alpha, albeit there having been no bug reports on Gerrit yet. I've got it installed and running on my own device for almost one day now.

As always, these builds don't contain any patches to closed source drivers, as those would have to be supplied by Lenovo. Who have long since stopped supporting this device.

Builds prior to November 6th, 2020 have been deleted from my dropbox to mitigate space constraints.

Use at your own risk!

Regards
Ektus.
 

Attachments

  • lineage-14.1-20210302-UNOFFICIAL-cedric.zip.md5sum.txt
    78 bytes · Views: 9

ektus

Senior Member
New build with March 05th, 2021 security patches available


There have been two more tiny patches applied, and the changes have been merged already. Therefore I've done an updated build.

As always, these builds don't contain any patches to closed source drivers, as those would have to be supplied by Lenovo. Who have long since stopped supporting this device.

Builds prior to December 15th, 2020 have been deleted from my dropbox to mitigate space constraints.

Use at your own risk!

Regards
Ektus.
 

Attachments

  • lineage-14.1-20210307-UNOFFICIAL-cedric.zip.md5sum.txt
    78 bytes · Views: 6

Top Liked Posts

  • 2
    Experimental new build with January 05th, 2021 security patches available

    The build from January 7th has been deleted from Dropbox, this one includes a couple more patches from Gerrit:


    This build is to be considered alpha as it is lacking two patches from July as can be read on Gerrit. The patches from August have been merged, September through January have also been included, but no updated patch level. It still reports June 5th, 2021, as it is lacking the two patches from July from the "not implemented" section. There seems to be no progress in backporting these patches :-(

    I've got it installed and running on my own device for one day now.

    As always, these builds don't contain any patches to closed source drivers, as those would have to be supplied by Lenovo. Who have long since stopped supporting this device.

    Builds prior to October 8th, 2021 have been deleted from my dropbox to mitigate space constraints.

    Use at your own risk!

    Regards
    Ektus.
  • 5
    Experimental new build with January 05th, 2022 security patch available

    (URL deleted, no longer valid per 2022-01-22)

    Same as above, but with one additional patch from https://review.lineageos.org/q/topic:%22n-asb-2022-01%22+(status:eek:pen+OR+status:merged)

    There has been only one patch yet, I've been waiting with publishing in order to see if there would arrive some more. Doesn't seem like it. Supporting Nougat further is becoming difficult :-(

    Builds prior to October 8th, 2021 have been deleted from my dropbox to mitigate space constraints.

    Use at your own risk!

    Regards
    Ektus.
    2
    Experimental new build with January 05th, 2021 security patches available

    The build from January 7th has been deleted from Dropbox, this one includes a couple more patches from Gerrit:


    This build is to be considered alpha as it is lacking two patches from July as can be read on Gerrit. The patches from August have been merged, September through January have also been included, but no updated patch level. It still reports June 5th, 2021, as it is lacking the two patches from July from the "not implemented" section. There seems to be no progress in backporting these patches :-(

    I've got it installed and running on my own device for one day now.

    As always, these builds don't contain any patches to closed source drivers, as those would have to be supplied by Lenovo. Who have long since stopped supporting this device.

    Builds prior to October 8th, 2021 have been deleted from my dropbox to mitigate space constraints.

    Use at your own risk!

    Regards
    Ektus.
  • 102

    mwRBiAz.jpeg


    Code:
    /*
    * I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
    * Please do some research if you have any concerns about features included in the products you find here 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.
    * Your warranty will be void if you tamper with any part of your device / software.
    * Same statement for XDA.
    */

    LineageOS is a free, community built, aftermarket firmware distribution of Android 7 (nougat), 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.



    What's working :

    • Boots
    • Touch
    • RIL [Calls, Mobile Data, Dual SIM]
    • Wifi
    • Wifi Tethering
    • Bluetooth
    • Camera
    • Camcorder
    • Audio
    • Sensors
    • Flash
    • GPS
    • Notification LED
    • Fingerprint
    • OTG
    • VoLTE
    • FM Radio

    Known issues:
    • Fingerprint(Fixed in the build 25.05.2017)
    • OTG(Fixed in the build 29.05.2017)
    • Camcorder(Fixed in the build 01.06.2017)
    • VoLTE(Fixed in the build 27.06.2017)
    • Wi-Fi Obtaining IP problem in some variants.(Fixed in the build 27.06.2017)
    • Video player stutters.(Fixed in the build 28.06.2017)
    • FM Radio(Fixed in the build 28.06.2017)
    • Rear Camera in 3rd party apps does not work on some users.(Fixed in the build 30.06.2017)
    • USB tethering function does not work.A Third party app such as pdanet might be a solutiıon.(Fixed in the build 30.06.2019)

    Instructions :

    Downloads :

    Source Code:

    XDA:Rom Information
    LineageOS 14.1,cedric, ROM for the Moto G5

    Contributors
    wzedlare, vache, CodeZero, ektus
    ROM OS Version: 7.1.x Nougat

    Version Information
    Status:
    Stable

    Created 2017-05-25
    Last Updated 2021-08-29
    18
    The build with january security patch is now on the thread.
    16
    New build(18/10/17) is now available to fix "Krack" vulnerability.
    16
    just got Oreo booted on our beloved Moto G5
    15
    New Build 12-11-2017.Big thanks to vache and jobinrjohnson for their helps.Changelog:
    Code:
    - Root obtaining problems(a.k.a segmentation faults) are fixed.
    - Governor of the little clusters is interactive now.
    - Some other optimizations.