• 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][addison] UNOFFICIAL LineageOS 14.1

zander21510

Senior Member
Jan 10, 2012
538
176
0
Dallas
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.
 */

Introduction
I use Lineage for my Moto Z, and was bummed out that I wasn't going to get any security updates. So, I decided to learn how to build it myself!

I'm no coder, and I have mad respect for those who actually code and make all of these ROMs possible. That being said, all I know how to do is build the thing from the Lineage repos. I CANNOT FIX BUGS. Period. I would if I could, but I simply don't know how. I can try tiny, very small things, but no guarantees.

I plan on trying to upload builds monthly as time permits, but I have a full time job and other obligations, so it may be irregular. But I like updates as much as everyone, so I'll do my best to build as often as I can.

Installation instructions
Flash using latest TWRP. Upgrades, or "dirty flashes", should be fine between builds.

If you are coming from Lineage 14.1 Official builds, you must first flash the migration zip. The installer won't work when working with different keys. Find it here

Make sure to flash Gapps BEFORE you reboot.

Changelog
2017-1-20
-Re-forked repo for easy syncing to Lineage official
-January 5 Security Patch
Not Working
-You Tell Me

Downloads
Lineage 14.1 UNOFFICIAL

FAQ
*Can you fix this bug?
-Probably not

*Can you do more frequent/daily/hourly builds?
-No

*It's not working!
-Please post your build version & information so I can check if it's a bad build, or if something broke in the code

Thanks To/Credits
* @Alberto97 , for his awesome work on our device & for providing the fixes that never went into the official build
* Lineage OS Team
Donations are appreciated, but certainly not necessary:
Litecoin: LV94DBg14pxNE4SSReKEhcCJKr5ee42o6H
Dogecoin: DCzWV2QimjpwYz73rXbc4UjEdw7yWCCES3
Additional source links:

https://github.com/zander21510/android_kernel_motorola_msm8953

https://github.com/zander21510/android_device_motorola_addison

XDA:DevDB Information
Lineage 14.1 Unofficial for Addison, ROM for the Moto Z Play

Contributors
zander21510
Source Code: https://github.com/LineageOS/android.git

ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: Lineage

Version Information
Status: Alpha

Created 2017-12-30
Last Updated 2017-01-20
 
Last edited:

zander21510

Senior Member
Jan 10, 2012
538
176
0
Dallas
News & Updates

CHANGELOG:


2017-1-20
-Re-forked repo for easy syncing to Lineage official
-January 5 Security Patch

2017-1-5
-Forked repo from Alberto97's sources
-Fixed camera issue, now using Motorola proprietary repo
-Changed fingerprint sleep to act as home button instead (my personal preference!)

2016-12-30
-Initial build
-Camera not working
 
Last edited:

WebmonkeyJMK

New member
Dec 30, 2017
1
0
0
could you please add 0xC113 bootloader support? from Alberto's AOSP fix I take it shouldn't be a hard fix to make:
-require version-bootloader=0xC105|0xC106|0xC107|0xC112
+require version-bootloader=0xC105|0xC106|0xC107|0xC112|0xC113
 

Ultramanoid

Elite Member
Apr 24, 2011
3,364
4,743
113
日本
Retried build using Alberto97's sources from 14.1-next- camera still broken. I'm guessing it has something to do with a change in the Lineage source code, but I really have no idea. Other than that, everything else seems to be working fine. If anyone wants to give me a lead on the camera problem, maybe I can do something about it.
Just to be clear, I assume by broken camera you mean camera on a system level, affecting any use of camera by any application, right ?
 
 

zander21510

Senior Member
Jan 10, 2012
538
176
0
Dallas
taking some baby steps with developing! I forked Alberto97's repos and made a couple of changes...including this one:

could you please add 0xC113 bootloader support? from Alberto's AOSP fix I take it shouldn't be a hard fix to make:
-require version-bootloader=0xC105|0xC106|0xC107|0xC112
+require version-bootloader=0xC105|0xC106|0xC107|0xC112|0xC113

I'll do some testing and upload a build later today
 
  • Like
Reactions: Ultramanoid

Mr_prfssnl

Member
Nov 5, 2017
29
23
0
Introduction



Installation instructions



Changelog


Not Working



Downloads
Lineage 14.1 UNOFFICIAL

FAQ



Thanks To/Credits


Donations are appreciated, but certainly not necessary:


Additional source links:

https://github.com/zander21510/android_kernel_motorola_msm8953

https://github.com/zander21510/android_device_motorola_addison

XDA:DevDB Information
Lineage 14.1 Unofficial for Addison, ROM for the Moto Z Play

Contributors
zander21510
Source Code:https://github.com/LineageOS/android.git

ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: Lineage

Version Information
Status: Alpha

Created 2017-12-30
Last Updated 2017-01-05
Thanks for your effort man. I really appreciate it. Can you tell me what the security patch level is though?
 
  • Like
Reactions: Ultramanoid

zander21510

Senior Member
Jan 10, 2012
538
176
0
Dallas
So trying to get some things working on my daily driver...my company uses Microsoft Intune Company Portal for access to my work email, which does the standard root checking & etc. On the last official Lineage build, it worked just fine so long as root was shut off in developer tools (if the root zip was installed).

One thing it does which is a bit irritating is that it seems to assume your phone is rooted if you use a rom with test keys, which would be all unofficial builds by default, including mine. So in order to get my work email I'm making signed builds for myself along with the regular unsigned builds. If anyone is interested I can upload signed builds here in case you have some reason you need a signed build. Other than that, I'm not sure there's really any advantage to having a signed build vs an unsigned one. One big disadvantage, you can't migrate to or from any other builds, so you'd be stuck with me unless you wipe :)
 

sam00561

Elite Member
Jan 31, 2011
1,182
205
63
Is ther any way to get substratum themes working on this rom i have tried oms and lineage selection but nothing is getting themed.
 

mikehat

New member
Dec 10, 2011
2
0
0
How did you get updated proprietary blobs?

Forked Alberto97s device & kernel so I could try and fix bugs, and also started using a different repo for the proprietary blobs, that fixed the camera issue! So now it looks like everything is working, android security patch is still on Dec 5 though, but everything else is current. Let me know if there are issues
Thanks for this (and to Alberto97, if you're out there...).

Like you, I finally couldn't take it any more and began building on my own. I, too, had a fully functional phone except for the camera.

I jumped through a few hoops trying to get the proprietary blobs, and finally scraped them out of your build. I installed XT1635-02_ADDISON_7.1.1_NPNS26.118-22-2-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC and tried extract-files.sh but that didn't get everything. I didn't try a deeper look, as I was eager to get my phone working again. I unzipped your ROM and extract-files.sh worked. I rebuilt and now the camera works with my build.

How did you get those blobs? Also, do you know if Motorola publishes stock ROMs for addison, or do we always have to get them second-hand from something like lolinet?

Thanks in advance for any info. I'm probably not worthy of taking responsibility after the loss of Alberto97, but I'd be willing to lend a hand or coordinate the effort somehow.

MIke
 

zander21510

Senior Member
Jan 10, 2012
538
176
0
Dallas
Thanks for this (and to Alberto97, if you're out there...).

Like you, I finally couldn't take it any more and began building on my own. I, too, had a fully functional phone except for the camera.

I jumped through a few hoops trying to get the proprietary blobs, and finally scraped them out of your build. I installed XT1635-02_ADDISON_7.1.1_NPNS26.118-22-2-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC and tried extract-files.sh but that didn't get everything. I didn't try a deeper look, as I was eager to get my phone working again. I unzipped your ROM and extract-files.sh worked. I rebuilt and now the camera works with my build.

How did you get those blobs? Also, do you know if Motorola publishes stock ROMs for addison, or do we always have to get them second-hand from something like lolinet?

Thanks in advance for any info. I'm probably not worthy of taking responsibility after the loss of Alberto97, but I'd be willing to lend a hand or coordinate the effort somehow.

MIke
I just added this repo (https://github.com/TheMuppets/proprietary_vendor_motorola) to the manifest, you can do that in lieu of the "extract proprietary blobs" step. I noticed there was a fork of it on Alberto97's github (but it was out of date), so I poked around and found TheMuppets one was still being updated, including fixes for addison. So made a build and presto- no more camera issues.

I guess there's some gray legal area when it comes to the proprietary Motorola stuff, that's why it's not listed as an option in the official Lineage build instructions.