[OFFICIAL] [NIGHTLIES] LineageOS 17.1

[npjohnson]

Moto X 2014

- Your warranty is now void.
- You have been warned.
- Use at your own risk.

Introduction:
This is the Official Lineage OS 17.1 thread for the Motorola Moto X 2014, codename victara.

How to Install:
Please follow the instructions on our Official LineageOS Wiki page here.

If you don't follow these instructions, please don't expect support here. We also don't support 3rd party addons (Magisk/XPosed/Dolby/Viper/etc.), so please don't seek support if you use these.

Known Bugs:

• None.

Download:

• LineageOS Updater
• npjohnson's Personal Updater -- These are experimental, likely to break/eat your cat/destroy your data, and include GApps -- you'll find no support for these.

XDA:DevDB Information
[OFFICIAL] [NIGHTLIES] LineageOS 17.1, ROM for the Moto X 2014

Contributors
npjohnson, jeferson1979, linckandrea, tortel
Source Code: https://github.com/LineageOS

ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Newest firmware available for your variant/locality
Based On: LineageOS

Version Information
Status: Stable

Created 2020-05-15
Last Updated 2020-05-15

 

[franciscorizzo]

Hello,
this Android version don't have navigation bar?

 

[jeferson1979]

Hello,
this Android version don't have navigation bar?

If you want the old behavior, you have to set in settings/system/gestures

 

[idksomuch]

Just to confirm, we can't root our devices running this version of LOS, right?

 

[jeferson1979]

Just to confirm, we can't root our devices running this version of LOS, right?

Soon it will be available a fix for magisk, it's in test yet, if you want to try, I've build one version with the fix. You can install at recovery, and after boot install the manager. It will ask you extra setup and reboot. Available here: https://sourceforge.net/projects/victara-universe/files/Android10/Lineage-17-1/Magisk/

 

[idksomuch]

Soon it will be available a fix for magisk, it's in test yet, if you want to try, I've build one version with the fix. You can install at recovery, and after boot install the manager. It will ask you extra setup and reboot. Available here: https://sourceforge.net/projects/victara-universe/files/Android10/Lineage-17-1/Magisk/

That worked, thanks!

 

[jwhite5840]

Confused, only seeing LOS 16 builds on the official link from above?

 

[jeferson1979]

Confused, only seeing LOS 16 builds on the official link from above?

17.1 nightlies will be available soon. Hold with us a litlle :fingers-crossed:

 

[jeferson1979]

Official nightlies available :highfive:

 

[ChrisAG]

Installed without a hitch! Thanks guys!
(Dirty install using TWRP & factory reset, I'll see how it behaves).

 

[lantsem]

Installed latest lineage-17.1-20200530 build today. Found the following bugs:
1. In commit by @npjohnson CID 0x0 moved to XT0197's guard. So my XT1095 with 0x0 detected now as 1097. Purely cosmetic, but maybe it needs a correction.
2. No MCC and MNC codes or operator names visible on the roaming network. This bug was present also in 16.0. Last time it worked with 14.1.
3. rild crashes when I try to manually select a network (Network & internet -> Mobile network -> unselect Automatically select network) and I get 'Couldn't find networks. Try again.' in GUI. logcat attached.

 

[ywlke]

Amazing work! That my XT1095 which shipped with Android 4.4.4 can now run 10 is remarkable. The 5/30 build is working great so far, using the beta Magisk from a few posts back.

Prior to LOS 17.1, I was running LOS 15.1 (unofficial). I noticed that neither official LOS 17.1 nor LOS 16 (which I used for 1 day, and then 17.1 came out!) can drop the screen brightness as low as 15.1 could. Is it possible to bring back the lower-than-OEM brightness feature?

 

[jeferson1979]

Installed latest lineage-17.1-20200530 build today. Found the following bugs:
1. In commit by @npjohnson CID 0x0 moved to XT0197's guard. So my XT1095 with 0x0 detected now as 1097. Purely cosmetic, but maybe it needs a correction.
2. No MCC and MNC codes or operator names visible on the roaming network. This bug was present also in 16.0. Last time it worked with 14.1.
3. rild crashes when I try to manually select a network (Network & internet -> Mobile network -> unselect Automatically select network) and I get 'Couldn't find networks. Try again.' in GUI. logcat attached.

I'm aware of this and now a potential fix wich I will test tomorrow. (Rild on searching). Thanks for the log

---------- Post added at 12:49 AM ---------- Previous post was at 12:48 AM ----------

Amazing work! That my XT1095 which shipped with Android 4.4.4 can now run 10 is remarkable. The 5/30 build is working great so far, using the beta Magisk from a few posts back.

Prior to LOS 17.1, I was running LOS 15.1 (unofficial). I noticed that neither official LOS 17.1 nor LOS 16 (which I used for 1 day, and then 17.1 came out!) can drop the screen brightness as low as 15.1 could. Is it possible to bring back the lower-than-OEM brightness feature?

We will look for it ASAP

 

[jwhite5840]

Just attempted to install LOS 17.1 official nightly 20200601 using TWRP 3.2.1-0 today.

Clean flash completed without error but on reboot got "Encryption Failed" splash screen indicating a factory reset was needed.

Went ahead with that - it booted to TWRP and did a wipe, then rebooted again to the same splash.

Detailed steps were:

(1) Successfully boot OS to LOS 16 20200419
(2) Mount internal storage and copy lineage-17.1-20200601-nightly-victara-signed.zip and open_gapps-arm-10.0-stock-20200530.zip
(3) Boot to recovery TWRP 3.2.1-0
(4) Standard wipe (factory reset)
(5) Install lineage-17.1-20200601-nightly-victara-signed.zip
(6) Wipe cache/dalvik
(7) Install open_gapps-arm-10.0-stock-20200530.zip
(8) Wipe cache/dalvik a second time
(9) Attempt to boot OS to LOS 17.1 20200601 - got LOS boot animation followed by "Encryption Failed" splash indicating factory reset needed
(10) Accepted factory reset "Erase Everything" button
(11) Boot to recovery automatically
(12) Automatically perform factory reset wipe
(13) Attempt to boot OS to LOS 17.1 20200601 - got LOS boot animation followed by "Encryption Failed" splash indicating factory reset needed

... loop ...

Was able to restore from TWRP LOS 16 20200419 backup without issue.

Any suggestions?

 

[Jaytn]

Just attempted to install LOS 17.1 official nightly 20200601 using TWRP 3.2.1-0 today.

Clean flash completed without error but on reboot got "Encryption Failed" splash screen indicating a factory reset was needed.

Went ahead with that - it booted to TWRP and did a wipe, then rebooted again to the same splash.
[...]
Was able to restore from TWRP LOS 16 20200419 backup without issue.

Any suggestions?

Interesting, I got the same screen dirty flashing over 16.0 and just thought it was due to my dirty rom (I messed something up before, regular 16.0 updates wouldn't boot) or me screwing up the update process. But since you got it on a clean flash, maybe it's something different?
For completeness, I followed the guide from the updater (see here), namely:
- LOS 16.0 2019-12-27 installed (with opengapps)
- (make a backup in TWRP)
- (not wiping anything)
- reboot to sideload
- reboot to TWRP and use sideload there (regular wasnt working for some reason)
- sideload 17.1 2020-06-01
- flash new opengapps (as per instructions) from TWRP (not sideload, because that wouldn't apply my gapps.config)
- reboot "Encryption failed"
- (restore to backup and give up for the moment)
Also not to mention, I didn't have my phone encrypted on 16.0

 

[jeferson1979]

Answer to all points: you need to be full ext4 at your filesystem for lineage-17.1. As well dirty flash Android version to another never delivered good results.

 

[jwhite5840]

Answer to all points: you need to be full ext4 at your filesystem for lineage-17.1.

DATA was f2fs - switched to ext4 and repeated previous steps, worked like a charm. Thanks!

 

[MauricioJorge]

magisk does not work
Any solution? already installed beta version and it doesn't work

 

[esjarc]

Does anyone else experience bootloops if you try to boot the device with Secure Startup enabled?

 

[jeferson1979]

Does anyone else experience bootloops if you try to boot the device with Secure Startup enabled?

As you commented on issue, connected you are able to boot?