Related
(edited some content and added a few more instructions on May 25 2015)
I initially posted this when my employer changed their policies to require device admin access to people's phones if they wanted to access company emails or calendars. Spent a few days reading the android source code and came up with a working apk.
This app removes the annoying popup saying that you need to give it admin permissions and add a numeric password. It also does not set any additional policies other than what you already have set on your device. It does not make the email app a device admin.
The app tells the server what it wants to hear - which is they have total control over the device, but it doesn't really do anything on the phone.
DISCLAIMER: I'm not responsible if:
You get fired (a very real possiblilty - companies fire people for far less than "circumventing security" even though most of us know that regular folks' emails have nothing valuable to the competition.
If you get in other sorts of trouble for using this
if this melts your device down or breaks it in any fashion or your ROM gets corrupted.
USE THIS AT YOUR OWN RISK.
How to install:
Copy the files onto your phone storage and install them using a file explorer.
NOTES (read this before you install):
This will install easily on phones that do not have email.apk and exchange2.apk. But if you have an AOSP ROM, you may already have these in your system/app directory. In that case, you'll have to uninstall the system apps email.apk and exchange or exchange2.apk using a root explorer. I use ES explorer's "App Manager" feature and it works well for me. Once the system apps are removed, you can install the files from this post.
If you update your ROM later, the system apps will come back and may conflict with these apks (installed in /data by default) so you'll have to do the removal/installation again.
You don't need Exchange.apk AND exchange2.apk on the same phone. If you use an ICS ROM (older phones), use exchange.apk. For JB or higher, Exchange2 is the one to use. If you already have exchange2.apk on your phone, you don't need to install the one from this post.
I compiled this from source, so it *should* work with all devices. There are no device-specific frameworks needed for these to run as far as I know.
I've only removed the Exchange based security. If there are any other kind of services (POP/IMAP or something else) which has similar policy enforcement, it may not work. I haven't tested it with anything other than Exchange.
UPDATE - Sep 27, 2015)
I'm sorry I disappeared - I hadn't checked back in a while and it looks like I uploaded the wrong apk. Uploading the correct one for Lpllipop.
UPDATE 4 (May 25, 2015)
Patched and compiled the Lollipop email client from CM12 sources. Google remoived exchange support from the AOSP email client, so I had to turn to CM12 for the source code.
The default Exchange2.apk from a CM or AOSP lollipop build should work so I'm not uploading it here.
UPDATE 2 (May 15, 2013)
Added Email.apk compiled from 4.2.2 sources. This gives you the nice JB style expandable notifications.
Also added higher attachment size support per a user request. The default email.apk limits the size to 5MB for atachment downloads/uploads. The attached Email-JB.apk supports 100MB download/50MB upload sizes. I'm not sure if this varies by Exchange server - I spent two whole nights because I set them too high (250M) and my exchange server threw a generic error. I spent the time troubleshooting policies where it was just the attachment size all along. Cost me 8 hours of sleep
Exchange2.apk is not needed if your phone already has Exchange.apk or Exchange2.apk. For people who have HTC phones, this may come in useful. This file was pulled from this ROM - which is compiled from sources. I couldn't get Exchange2 to compile and work properly from sources, but since there is nothing to be changed in here, any working APK (from a JB/ICS ROM) would suffice.
UPDATE 3 (Jan 11, 2014)
Added Email.apk compiled from 4.4.2 sources. This gives you the new gmail-style email view based on the contact pics or the first letter of the sender's name.
It will say that the policy was changed once you successfully connect to the exchange server, but no policy will be applied. You can check the device admins list once you connect - the newly connected exchange server will not be in the device admins list on your phone.
Notes:
I have not made any changes to the Exchange2_4_4_2.apk. I'm just pasting it here for convenience, for people who don't have it on their phones (certain HTC stock ROMS, or others that I don't know of).
If your server has other policies which prevent you from accessing it, this probably won't show an error message before bouncing you back because I've suppressed a few of these security related dialogs.
File List
May 25, 2015
Email-5_0.apk - Compiled from CM12 sources, exchange security and popup security dialogs removed, max attachment sizes changed to 100MB download/50MB upload from 5/5.
No exchange2.apk provided for lollipop - the one already on your phone should work. If you have any problems, please get it from a CM12 or AOSP ROM.
--- Old files----
Email.APK - Compiled from ICS (4.0.1) sources.
Exchange.apk - Compiled from ICS (4.0.1) sources.
May 15, 2013:
Email-JB.apk - Compiled from 4.2.2 sources, attachment sizes increased to 100MB/50MB down/up.
Exchange2.apk - pulled from a CM10.1 port (WFTN ROM)
Jan 11, 2014
Email-4_4_2.apk - Compiled from 4.4.2 (Kit Kat) sources, still retains the increased attachment size mod.
Exchange2-4_4_2.apk - Compiled from 4.4.2 sources [this apk is not needed unless you have a phone which does not already have this]
let me be the first one to say thanks !!!
worked like a charm !!
tested on HD2
I'm glad it helped
Yep thanks it's working on my rooted HTC Desire Z with andromedus
ProcessorHog said:
I'm happy to post my first actual Android dev/mod effort.
Recently my workplace introduced some draconian security policies for email syncing. I just wanted my appointments synced, so I didn't feel like encrypting my device, having zero timeout AND not even having the option of a pattern unlock (they enforce only passwords/PIN). I tried a couple of the Email.apks posted on XDA but for some reason or other, I couldn't get them to install/run. There was a GB based app which would install but when it synced, it said the device did not support some of the policies that were needed by the server. When I compared the Email app's GB source with the ICS source, I saw that there were tons more policies supported in the ICS version.
So I set upon a weekend project to modify the ICS email app, and that ended up taking 4 days part time. I learned a lot about aosp, compiling from source and all that and know that I have so much that I don't know.
Anyway, I was able to successfully modify the source code and finally managed to get the original Android Email app (which comes with AOSP) compiled running perfect, but without the ridiculous policies they wanted.
I tested it on my Evo 3D running MeanRom (4.0.3 build) and also tested it on the Android emulator of course ), and it works great. No annoying popup saying that you need to give it device admin permissions nor does it set any additional policies other than what you already have set on your device. It does not make the email app a device admin.
The app tells the server what it wants to hear - which is they have total control over my device, but it doesn't really do it on the phone. Everyone is happy
DISCLAIMER: I'm not responsible if you get fired or if you get in other sorts of trouble for using this, or if this melts your device down or breaks it in any fashion. USE THIS AT YOUR OWN RISK.
How to install:
Code:
adb install -r /path/on/your/computer/to/Email.apk
This is how I installed it. Alternatively, you can try downloading this on your phone (or copying it to the SD Card) and open it with package installer, and see if it installs.
NOTES:
I compiled this from source, so it *should* work with other devices as well. As far as I know, there are no device-specific frameworks/anything else needed for these to run. I used the android-4.0.1_r1 branch source code.
Since I was running MeanROM on my HTC (a sense-based ROM), Email.apk had some dependencies on Exchange.apk which did not exist on my device. I'm posting this as an attachment for the folks who may need it. I haven't changed any code in that project, so If you already have Exchange.apk (shows up as "Exchange Services" in your Apps) you don't need to install it.
I've only removed the Exchange based security. If there are any other kind of services (POP/IMAP or something else) which has similar policy enforcement, it may not work. I haven't tested it with anything other than Exchange.
This was compiled for the arm-v7 CPU. I'm not too sure whether this means it won't run on any other ones (but knowing that it's dalvik code and not native, it should run I guess). It ran fine on my x-86 based emulator.
[*]This is an eng build (non-optimized). I couldn't find a way to get classes.dex in the APK itself on a full "user" release build. Eng is the least optimized form, userdebug is a bit better. I couldn't find a non-device-specific "lunch" option to build this with a "userdebug" variant flag. If I do figure it out, I'll post an updated APK here.
I'm still learning how to use eclipse and such. I haven't posted the source code here, and frankly I don't know how much of it I should post (I think I changed about 3 files and commented out a bunch of stuff). If anyone is interested in knowing, I can point out the files that I changed. If I figure out how to do a proper diff that shows all the changes, I will post the code diff here.
Update:
Replaced the apks with a "release-user" build.
Click to expand...
Click to collapse
Thanks for share it, I made a CWM flasheable ZIP with your files.
ProcessorHog said:
I'm happy to post my first actual Android dev/mod effort.
Recently my workplace introduced some draconian security policies for email syncing. I just wanted my appointments synced, so I didn't feel like encrypting my device, having zero timeout AND not even having the option of a pattern unlock (they enforce only passwords/PIN). I tried a couple of the Email.apks posted on XDA but for some reason or other, I couldn't get them to install/run. There was a GB based app which would install but when it synced, it said the device did not support some of the policies that were needed by the server. When I compared the Email app's GB source with the ICS source, I saw that there were tons more policies supported in the ICS version.
So I set upon a weekend project to modify the ICS email app, and that ended up taking 4 days part time. I learned a lot about aosp, compiling from source and all that and know that I have so much that I don't know.
Anyway, I was able to successfully modify the source code and finally managed to get the original Android Email app (which comes with AOSP) compiled running perfect, but without the ridiculous policies they wanted.
I tested it on my Evo 3D running MeanRom (4.0.3 build) and also tested it on the Android emulator of course ), and it works great. No annoying popup saying that you need to give it device admin permissions nor does it set any additional policies other than what you already have set on your device. It does not make the email app a device admin.
The app tells the server what it wants to hear - which is they have total control over my device, but it doesn't really do it on the phone. Everyone is happy
DISCLAIMER: I'm not responsible if you get fired or if you get in other sorts of trouble for using this, or if this melts your device down or breaks it in any fashion. USE THIS AT YOUR OWN RISK.
How to install:
Code:
adb install -r /path/on/your/computer/to/Email.apk
This is how I installed it. Alternatively, you can try downloading this on your phone (or copying it to the SD Card) and open it with package installer, and see if it installs.
NOTES:
I compiled this from source, so it *should* work with other devices as well. As far as I know, there are no device-specific frameworks/anything else needed for these to run. I used the android-4.0.1_r1 branch source code.
Since I was running MeanROM on my HTC (a sense-based ROM), Email.apk had some dependencies on Exchange.apk which did not exist on my device. I'm posting this as an attachment for the folks who may need it. I haven't changed any code in that project, so If you already have Exchange.apk (shows up as "Exchange Services" in your Apps) you don't need to install it.
I've only removed the Exchange based security. If there are any other kind of services (POP/IMAP or something else) which has similar policy enforcement, it may not work. I haven't tested it with anything other than Exchange.
This was compiled for the arm-v7 CPU. I'm not too sure whether this means it won't run on any other ones (but knowing that it's dalvik code and not native, it should run I guess). It ran fine on my x-86 based emulator.
[*]This is an eng build (non-optimized). I couldn't find a way to get classes.dex in the APK itself on a full "user" release build. Eng is the least optimized form, userdebug is a bit better. I couldn't find a non-device-specific "lunch" option to build this with a "userdebug" variant flag. If I do figure it out, I'll post an updated APK here.
I'm still learning how to use eclipse and such. I haven't posted the source code here, and frankly I don't know how much of it I should post (I think I changed about 3 files and commented out a bunch of stuff). If anyone is interested in knowing, I can point out the files that I changed. If I figure out how to do a proper diff that shows all the changes, I will post the code diff here.
Update:
Replaced the apks with a "release-user" build.
Click to expand...
Click to collapse
what part of the smali code was modified please?
Would this work on 4.2?
I could use some help. I'm trying to run this on SOS M ver 2.6.2 (4.0.3 build) on an Evo 3d. I was under the impression that SOS M was similar enough to Mean ROM so that it would work, but all I'm getting is an immediate crash on startup. Any suggestions?
So glad that someone created this! THANK YOU SO MUCH!
The new security rules are ridiculous!
I wish that app would be maintained with the current version and be put in the google play store. How can I keep up to date with the most recent version of this app?
Recent update
Sorry I haven't been here much - life got too busy! If you post here and don't see a reply from me in a couple of days, feel free to send me a PM.
carm01 said:
what part of the smali code was modified please?
Click to expand...
Click to collapse
No smali code was modified, the apk was compiled directly from the java source code which I modified to take out a few annoying dialog boxes and the actual policies/restrictions that the server wants to set on your device.
zdravke said:
Would this work on 4.2?
Click to expand...
Click to collapse
The ICS version worked fine on 4.2 since it's just regular java code compiled from source, but I recently also added an APK compiled from 4.2.2 sources which has the expanded notifications (the ICS version didn't have it).
pbmurdoc said:
I could use some help. I'm trying to run this on SOS M ver 2.6.2 (4.0.3 build) on an Evo 3d. I was under the impression that SOS M was similar enough to Mean ROM so that it would work, but all I'm getting is an immediate crash on startup. Any suggestions?
Click to expand...
Click to collapse
Could you try the newly updated APK? Make sure your phone has exchange2.apk or exchange.apk as well. Some phones do not have these pre-installed.
sirtom1 said:
So glad that someone created this! THANK YOU SO MUCH!
The new security rules are ridiculous!
I wish that app would be maintained with the current version and be put in the google play store. How can I keep up to date with the most recent version of this app?
Click to expand...
Click to collapse
I don't think this can be put on the play store - I don't regularly maintain it (once compiled it should run without problems), and I recently updated it just because I finally got a JB ROM a few months ago and started missing the expanded notification. The next update will probably be after a long time - after the next version of android gets released.
I'm not bright enough to write something complex like the email app - there's a TON of code in it written by smart and talented people, I just dug around a little to find the policy application code and removed it. The real talented folks are the ones who actually contribute to android
luisjoseb said:
Thanks for share it, I made a CWM flasheable ZIP with your files.
Click to expand...
Click to collapse
Thanks for making this easy for others! If you have the time, could you make one for the 4.2.2 version of it? Someone could find that useful!
Just gave it a try. Works great. Thanks so much
Sent from my DROID RAZR using Tapatalk 2
thank you .. working like a charm ..
Desire with MIUI Rom (VJ - JB-4.1.2)
I had to use this mod as the latest build didnt have an Email app .. and other ROMs' Email2.apk didnt work on this one (due to mishandling the security request) .. !
anyways .. thank you ..
Thanks. I try on US T-mobile HTC One S JB 4.1.1 Sense and it works. I use Email-JB.apk and Exchange.apk
thanks for this, it's working on my galaxy s4 (android 4.2.2) now instead of that ugly samsung mail app. 1 thing i'm missing is option in the nice JB style expandable notifications to directly mark as read or delete the email in the notification panel. this option is present in cm10.1/aosp android 4.2.2 but not in this email app. Is it possible to add this?
elroy944 said:
thanks for this, it's working on my galaxy s4 (android 4.2.2) now instead of that ugly samsung mail app. 1 thing i'm missing is option in the nice JB style expandable notifications to directly mark as read or delete the email in the notification panel. this option is present in cm10.1/aosp android 4.2.2 but not in this email app. Is it possible to add this?
Click to expand...
Click to collapse
For this, I'll have to compile from CM10.1 sources. I haven't tried that - I'll give it a shot when I get some free time and will post the APK here if I manage to do that
ProcessorHog said:
For this, I'll have to compile from CM10.1 sources. I haven't tried that - I'll give it a shot when I get some free time and will post the APK here if I manage to do that
Click to expand...
Click to collapse
Okay, thanks
Getting an error on adb install... Running JDQ39 official Google version for Galaxy Nexus. Rooted/etc, obviously. Leankernel 16.something.
Is this only for AOSP ROMs?
Error I am receiving:
pkg: /data/local/tmp/Email-JB.apk
Failure [INSTALL_FAILED_CONFLICTING_PROVIDER]
No dice...
I managed to get it installed by using Titanium to uninstall Email 4.1 prior to installing yours. This gave me endless "Unfortunately, Email has stopped working" errors.
I installed a fresh AOSP 4.2.2 ROM and tried several iterations of uninstalling Email and Exchange2Google.apk and continue to get the "Unfortunately, Email has stopped working" errors.
I've tried using "apk install" and Package Installer, same results regardless of install method.
Works fine on TF101 EeePad Transformer (EOS4) and Galaxy Ace phone (CM10)
New CyanogenMod 13 snapshot build (ZNH5Y) is rolling out.
The Android ROM community isn't quite as active as it was a few years ago with Android itself becoming more feature-rich. Still, CyanogenMod is chugging along with support for a ton of devices and a reasonably fast update cycle. A new snapshot build of the Marshmallow-based CyanogenMod 13 is now official (ZNH5Y), and it will be available on the first wave of devices today.
This is a snapshot build, meaning it's the most stable build of CM you can get. Of particular note, this version of CM will include all security patches up through the August bulletin. Build ZNH5Y also includes fixes for several of the recently reported Quadrooter kernel vulnerabilities. Two of the vulnerabilities aren't accessible to the CM team, so those patches need to come from further up the chain.
If you're running the ZNH0E snapshot build, you can flash the new one on top of it. ROMs for various devices will roll out as they are ready. Today, you can expect downloads for popular devices from OEMs like OnePlus, Samsung, and Motorola, as well as most Nexus devices. The full list is available on CM's blog post, but they're all code names.
Source: http://www.androidpolice.com/2016/08/15/new-cyanogenmod-13-snapshot-build-znh5y-rolling/
CM 13.0 Release – ZNH5Y - http://www.cyanogenmod.org/blog/cm-13-0-release-znh5y
Full changelog: http://pastebin.com/ptatg6kh
cm-13.0-20160816-SNAPSHOT-ZNH5YAO0F6-bacon.zip
Link - http://download.cyanogenmod.org/get/jenkins/174518/cm-13.0-20160816-SNAPSHOT-ZNH5YAO0F6-bacon.zip
Which is better / newer ? This on ore this one cm-13.1.1-ZNH2KAS2X1-bacon-signed-704f3ea59b ?
Thanks in advance
EDIT: I discovered what is difference, this one is cyanogenmod the other one is cyanogenOs, i got wrong with the filename.
I get reboots every time I receive a phone call with clean install and the latest stock opengapps. Works fine without opengapps, now trying to get it to work without the google dialer.
Edit: ok I looked into it, I never had to do this on recent cm13 nightlies but it's necessary to set dialer as default app for phonecalls.
Spaghetti-XRY said:
Which is better / newer ? This on ore this one cm-13.1.1-ZNH2KAS2X1-bacon-signed-704f3ea59b ?
Thanks in advance
EDIT: I discovered what is difference, this one is cyanogenmod the other one is cyanogenOs, i got wrong with the filename.
Click to expand...
Click to collapse
Your are trying to compare CM with COS?
I am the proud owner of two Oneplus One devices. (TWRP 3.0.2.0)
Just dirty flashed cm-13.0-20160816-SNAPSHOT-ZNH5YAO0F6-bacon on top of the previous Snapshot version on my two devices.
DDR is wiped perfectly.
Flash process well documented (log on screen)
After Flash, do a wipe of Cache / dalvik (just to be sure)
That's all. Works well, no issues.
Again, a nice job of Cyanogen.Mod... (Some may not like them, but I (and my devices) do like them)
According to ciwrl from the LineageOS Team, "Look for [official Lineage OS] builds to start rolling out this weekend" January 21st & 22nd, 2017
If you are not familiar with the builds download page, when an official LineageOS build is available it will be listed on that page. To find the build for your device, into the left side "Devices" column, click on the appropriate horizontal tab for your device brand name. Then click on the appropriate horizontal sub-tab model name. If your device is not yet listed it means that build is not yet released, please re-visit again later.
There are no estimated time of arrival (ETA) for all builds. If you want builds to be release faster you are welcome to love back your LineageOS community by contributing a code review. Either yourself as volunteer or by paying someone to contribute on your behalf.
Two types of builds:
1. Nightly: For clean fresh install. LineageOS Team recommends that users wipe when switching to LineageOS, and reinstall their gapps.
2. Experimental: For data migration/upgrade from CyanogenMod (CM) 13.0 or 14.1 to LineageOS 14.1. That data migration may or may not work. If it does not work you can always try the Nightly build. Experimental build may wipe permissions. In that case you will have to re-allow app permissions, but should retain all user data. Experimental build is watermarked with an ugly banner to ensure that you do not permanently run that Experimental build, and upgrade to a Nightly build after. Experimental build will be available for two months after January 20th, 2017. Read more.
Bugs and feature requests
Report bugs and make feature requests in that tracker. The LineageOS team are not accepting bug or regression reports until builds are available here. If you have any questions please check the instructions in that wiki or ask in #lineageOS on freenode.
Links
• Present Builds/Downloads available
• Verifying builds authenticity
• Update & build prep
• Bug and feature request tracker
• Wiki
• Status page
• Statistics
Enjoy
Why not a link to their official blog?
And when?
We all are waiting for official lineage-14.1 builds.
Good idea
RockyTV said:
Why not a link to their official blog?
Click to expand...
Click to collapse
RockyTV Good idea. Done I just added all the official links related to the coming soon official builds at https://forum.xda-developers.com/li...january-21-t3542405/post70658000#post70658000
waiting it like a child wait xmas
I think tomorrow will be available.
EvilHowl said:
I think tomorrow will be available.
Click to expand...
Click to collapse
I hope it does.. Well all the best!!
Seems like Lineage 14.1 builds have started.
https://review.lineageos.org/#/c/155809/
First build for Nexus 5x is up!
Enviado desde mi Nexus 6P mediante Tapatalk
Nexus nightly ready ... I wait for lg d802 ?
zifnab himself said it may take an hour for builds to be available in the download portal because of the hourly update interval on the mirrors; so it could take up to an hour for device builds to show up in the portal.
There's a ROM for Galaxy J2 (J200BT...)? If not, please do one, we're stuck on 5.1.1, and it's a horrible thing.
Do we know anything about lg g2 d802? I would like to know if it will get launched on los 13 or los 14.1 and when , thank you for your great work and for your time
pananoydakis said:
Do we know anything about lg g2 d802? I would like to know if it will get launched on los 13 or los 14.1 and when , thank you for your great work and for your time
Click to expand...
Click to collapse
pananoydakis The LineageOS Team said that the builds will be release periodically starting on January 21st & 22nd, 2017. When a build is available it will be listed on that page. Into the right side "Devices" column, click on the appropriate horizontal tab for your device brand and model. If your device is not yet listed, please re-visit again later.
There are no estimated time of arrival (ETA) for all builds. If you want builds to be release faster you are welcome to love back your LineageOS community by contributing a code review. Either yourself or by paying someone to contribute on your behalf.
For S5 klte pls
Enviado desde mi SM-G900F mediante Tapatalk
Why Cynogenmod and lineageOS does not make ROMs for meizu devices?
Why Cynogenmod and lineageOS does not make ROMs for meizu devices?
tank4k said:
will LOS get substratum compatibility?
Click to expand...
Click to collapse
I hope so... It sucks to have to reapply all of your themes whenever you update.
Ouch. I tried flashing the experimental OnePlus One (bacon) over CM14.1/LineageOS unofficial 20170117. The ZIP signature failed to verify. I (probably foolishly) tried it without ZIP signature verification, and it corrupted the partitions. Back to a few months ago CM14 TWRP backup...
So I highly DON'T recommend trying to flash the 20170123 bacon build if it fails ZIP signature verification.
(Going a touch deeper, there had been problems a couple of major generations of CM ago on the OnePlus One where the ZIPs were fine but the exact signing simply didn't work, and it was appropriate at that time to skip ZIP signature verification, but... oops).
libove said:
Ouch. I tried flashing the experimental OnePlus One (bacon) over CM14.1/LineageOS unofficial 20170117. The ZIP signature failed to verify. I (probably foolishly) tried it without ZIP signature verification, and it corrupted the partitions. Back to a few months ago CM14 TWRP backup...
So I highly DON'T recommend trying to flash the 20170123 bacon build if it fails ZIP signature verification.
(Going a touch deeper, there had been problems a couple of major generations of CM ago on the OnePlus One where the ZIPs were fine but the exact signing simply didn't work, and it was appropriate at that time to skip ZIP signature verification, but... oops).
Click to expand...
Click to collapse
If you flashed the actual nightly (and did a clean install), you shouldn't have this problem. I think.
RockyTV said:
If you flashed the actual nightly (and did a clean install), you shouldn't have this problem. I think.
Click to expand...
Click to collapse
It's possible that I caused the damage myself. The not-ZIP-signature-verified Experimental flash was taking far longer than usual; after about 30 minutes I cold re-started. After the restart, the /system file system was gone.
Two concerns remain:
1. That TWRP 3.0.2.0 fails the ZIP signature verification on BOTH the Experimental and the Nightly.
2. That the flash took 30+ minutes and hadn't completed, when a normal flash on the OnePlus One (including LineageOS unofficial just a few days earlier) takes perhaps 5 minutes, or less.
[ROM][addison] Unofficial LineageOS 14.1
Moto Mods are not supported
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.2 (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 check out the Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Working
Boots
RIL (Calls, SMS, Data)
Wifi
Bluetooth
Video Playback
LED Notifications
NFC
Not Working/Bugs
–
Installation
1. Make sure you have a nougat bootloader and modem else TWRP denies the installation by throwing a message about the wrong bootloader. You can find a guide here: https://forum.xda-developers.com/showpost.php?p=74069195&postcount=91
2. Requires Unlocked Bootloader & a custom recovery
3. Place ROM & Gapps (if applicable) in your virtual SD
4. Reboot in Bootloader Mode
5. Go to "Recovery" (Vol +/Vol -) and confirm (power)
6. Wipe Data/Factory Reset
7. Wipe Dalvik cache
8. Install the ROM zip
9. Install su for root. You can get the required file from here https://mirrorbits.lineageos.org/su/addonsu-14.1-arm-signed.zip
10. Install the Gapps zip (if applicable)
11. Reboot
Note
I have not built any of these ROMs myself, I'm simply just listing them for convenience sake. All credits go their rightful creators and to @Alberto97 for laying the groundwork for Moto Z Play development.
Downloads
@fablebreton's build: https://androidfilehost.com/?fid=817906626617950356 with november's security patch, built December 2nd.
@Shreps's build: https://moto.shreps.fr/?dir=Moto Z...29/ROM/Lineage with november's security patch, built December 9th.
XDA:DevDB Information
Unofficial LineageOS 14.1, ROM for the Moto Z Play
Contributors
Mr_prfssnl, Alberto97, fablebreton, Shreps
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.1.x
Version Information
Status: Beta
Created 2017-12-12
Last Updated 2017-12-12
I have used the first rom in your list and it is November patch too
Jagadhidh said:
I have used the first rom in your list and it is November patch too
Click to expand...
Click to collapse
Oops, sorry about that, I reported the information to him and made a mistake. All have November's patch indeed and Flashqueen's includes part of December's.
Ultramanoid said:
Oops, sorry about that, I reported the information to him and made a mistake. All have November's patch indeed and Flashqueen's includes part of December's.
Click to expand...
Click to collapse
I have changed the description accordingly ?
This might be of interest for users that come searching for unofficial Lineage builds.
The Lineage with MicroG project is still building for this device, and they do every couple of days, by the way. Actually nightlies.
XDA thread : https://forum.xda-developers.com/android/software/lineageos-microg-t3700997
Build downloads : https://download.lineage.microg.org/addison/
Edit : The last build as of this post is from December 11th, and declares a December security patch.
Ultramanoid said:
This might be of interest for users that come searching for unofficial Lineage builds.
The Lineage with MicroG project is still building for this device, and they do every couple of days, by the way. Actually nightlies.
XDA thread : https://forum.xda-developers.com/android/software/lineageos-microg-t3700997
Build downloads : https://download.lineage.microg.org/addison/
Click to expand...
Click to collapse
Can this Roms be dirty flashed over existing @Alberto97 nightlies from november?
Thats my biggest fear - to have to clean everything and reinstall the whole device....?
Can you provide a little help for this circumstance... i guess there are many user with the same issue.
Thank you!
Cheers
finfin82 said:
Can this Roms be dirty flashed over existing @Alberto97 nightlies from november?
Thats my biggest fear - to have to clean everything and reinstall the whole device....?
Can you provide a little help for this circumstance... i guess there are many user with the same issue.
Thank you!
Cheers
Click to expand...
Click to collapse
It was already answered a couple of times in the official thread ( where you also asked ), so please read the posts before yours there or at least search before asking, which is expected in the forum.
You can migrate from an official build to an unofficial, and vice versa, simply using the appropriate script ( before flashing the rom ) found here :
https://forum.xda-developers.com/showpost.php?p=70452245&postcount=2
Edit : Just make a backup in TWRP before proceeding, to be safe, and you can always restore that if you have any issues.
This is listed in the wrong section... this is why XDA has a section called: Moto Z Play ROMs, Kernels, Recoveries, & Other Development
They thought ahead.
https://forum.xda-developers.com/moto-z-play/development
Mr_prfssnl said:
[ROM][addison] Unofficial LineageOS 14.1
Moto Mods are not supported
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.2 (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 check out the Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Working
Boots
RIL (Calls, SMS, Data)
Wifi
Bluetooth
Video Playback
LED Notifications
NFC
Not Working/Bugs
–
Installation
1. Make sure you have a nougat bootloader and modem else TWRP denies the installation by throwing a message about the wrong bootloader. You can find a guide here: https://forum.xda-developers.com/showpost.php?p=74069195&postcount=91
2. Requires Unlocked Bootloader & a custom recovery
3. Place ROM & Gapps (if applicable) in your virtual SD
4. Reboot in Bootloader Mode
5. Go to "Recovery" (Vol +/Vol -) and confirm (power)
6. Wipe Data/Factory Reset
7. Wipe Dalvik cache
8. Install the ROM zip
9. Install su for root. You can get the required file from here https://mirrorbits.lineageos.org/su/addonsu-14.1-arm-signed.zip
10. Install the Gapps zip (if applicable)
11. Reboot
Note
I have not built any of these ROMs myself, I'm simply just listing them for convenience sake. All credits go their rightful creators and to @Alberto97 for laying the groundwork for Moto Z Play development.
Downloads
@fablebreton's build: https://androidfilehost.com/?fid=817906626617950356 with november's security patch, built December 2nd.
@Shreps's build: https://moto.shreps.fr/?dir=Moto Z...29/ROM/Lineage with november's security patch, built December 9th.
@Flashqueen's build: https://mega.nz/#!VrwFCJxa!Fza8TlHFJ...Z9eCcRw5XZwZmA with november's security patch + part of December's security patch, built December 9th. Also has integrated root and UnifiedNlp support.
XDA:DevDB Information
Unofficial LineageOS 14.1, ROM for the Moto Z Play
Contributors
Mr_prfssnl, Alberto97, fablebreton, Shreps, Flashqueen
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.1.x
Version Information
Status: Beta
Created 2017-12-12
Last Updated 2017-12-12
Click to expand...
Click to collapse
Jimi Mack said:
This is listed in the wrong section... this is why XDA has a section called: Moto Z Play ROMs, Kernels, Recoveries, & Other Development
They thought ahead.
https://forum.xda-developers.com/moto-z-play/development
Click to expand...
Click to collapse
I tried placing the thread there but they moved it to this section, since I am not actually developing anything. I am merely listing the ROMs
Mr_prfssnl said:
I tried placing the thread there but they moved it to this section, since I am not actually developing anything. I am merely listing the ROMs
Click to expand...
Click to collapse
Odd being it is all formated as every other rom listed in that section.
---------- Post added at 07:14 PM ---------- Previous post was at 07:03 PM ----------
Ultramanoid said:
This might be of interest for users that come searching for unofficial Lineage builds.
The Lineage with MicroG project is still building for this device, and they do every couple of days, by the way. Actually nightlies.
XDA thread : https://forum.xda-developers.com/android/software/lineageos-microg-t3700997
Build downloads : https://download.lineage.microg.org/addison/
Click to expand...
Click to collapse
That looks interesting, thank you.
Mr_prfssnl said:
I tried placing the thread there but they moved it to this section, since I am not actually developing anything. I am merely listing the ROMs
Click to expand...
Click to collapse
Plenty of other people have opened threads where developers have later posted builds or applications, and those threads are naturally in development sections. I guess a listing only is a grey area and they're being strict but if developers eventually use this thread to post builds it'd be time to ask mods about moving it to development then.
Mr_prfssnl said:
[ROM][addison] Unofficial LineageOS 14.1
Downloads
@Flashqueen's build: https://mega.nz/#!VrwFCJxa!Fza8TlHFJ...Z9eCcRw5XZwZmA with november's security patch + part of December's security patch, built December 9th. Also has integrated root and UnifiedNlp support.
Click to expand...
Click to collapse
I'm sorry, but I managed to destroy my build tree due to an error
As I had no backup I've decided to move on and try AOSP 8. I hate to disappoint some of you but I can't provide builds anymore for the Z Play. So I'd suggest to move on to another of the provided builds. Thanks.
Flashqueen said:
I'm sorry, but I managed to destroy my build tree due to an error
As I had no backup I've decided to move on and try AOSP 8. I hate to disappoint some of you but I can't provide builds anymore for the Z Play. So I'd suggest to move on to another of the provided builds. Thanks.
Click to expand...
Click to collapse
Ouch. Any intention to look at Lineage 15 eventually ?
By the way, regarding the other builds, Shreps' link has changed, that build is now at :
https://moto.shreps.fr/?dir=Moto Z Play (addison)/ROM/Lineage
Ultramanoid said:
Ouch. Any intention to look at Lineage 15 eventually ?
By the way, regarding the other builds, Shreps' link has changed, that build is now at :
https://moto.shreps.fr/?dir=Moto Z Play (addison)/ROM/Lineage
Click to expand...
Click to collapse
Well, to be honest, I was so angry that I haven't yet tried to build up another source tree, which takes hours... So currently not. But if I will, I'll let you all know.
Flashqueen said:
I'm sorry, but I managed to destroy my build tree due to an error
As I had no backup I've decided to move on and try AOSP 8. I hate to disappoint some of you but I can't provide builds anymore for the Z Play. So I'd suggest to move on to another of the provided builds. Thanks.
Click to expand...
Click to collapse
I updated the thread. Thank you for your effort anyway
Is there any real difference between both releases?
Jimi Mack said:
Is there any real difference between both releases?
Click to expand...
Click to collapse
Shrep's build was done a week later, so a week's worth of Lineage commits and / or fixes over the older build.
I'm having a hard time flashing these Lineage OS ROMs. I'm running stock 7.1.1 prior to flashing 14.1, but I keep getting error 7. It says I have 0xC113 but I need 0xC105/106/107/112.
I've tried flashing just the bootloader from the latest 7.1.1 but I'm still stuck and it's driving me nuts.
What am I doing wrong?
Here's another unofficial build, but camera is now broken.
https://forum.xda-developers.com/moto-z-play/development/rom-unofficial-lineageos-14-1-t3727440
Flashqueen's build remains the best fully functional one with at least up to most of December's patches ( even if it declares a November patch ) so at this point I'd still recommend it over anything else, other than getting a different, better supported device...
Edit : Lineage with MicroG support last put out a build December 17th, but those builds seem to be broken. I guess without a maintainer fixing things for the device, there's not much point in building as-is, see camera in the linked build above, for instance.
Ultramanoid said:
Here's another unofficial build, but camera is now broken.
https://forum.xda-developers.com/moto-z-play/development/rom-unofficial-lineageos-14-1-t3727440
Flashqueen's build remains the best fully functional one with at least up to most of December's patches ( even if it declares a November patch ) so at this point I'd still recommend it over anything else, other than getting a different, better supported device...
Edit : Lineage with MicroG support last put out a build December 17th, but those builds seem to be broken. I guess without a maintainer fixing things for the device, there's not much point in building as-is, see camera in the linked build above, for instance.
Click to expand...
Click to collapse
Another good alternative to the above mentioned ROMs would be Mokee ROM. They actually support the device officially and it keeps getting updates on a daily basis. Although it is not actually Lineage it is in fact really close. It even comes with all of the Lineage features, wallpapers and apps by default. Another cool feature is that it comes with Xposed by default :victory:
Hello!
I've an older rom, that is marshmellow based. I wanted to know how to integrate security updates to it. It is a CM based AICP 11.1
Anyone know of any guides? Or Tools? I've looked through google and i dont get any answers, just what security updates do and so on.
Much appriciated, thank you.
KitsuneFoxy said:
Hello!
I've an older rom, that is marshmellow based. I wanted to know how to integrate security updates to it. It is a CM based AICP 11.1
Anyone know of any guides? Or Tools? I've looked through google and i dont get any answers, just what security updates do and so on.
Much appriciated, thank you.
Click to expand...
Click to collapse
First of all, AICP has already merged till July 2017 security patches in MM. Google has released security patches for MM till October 2017 (that was "android-6.0.1_r81") as seen here. So, afaik, for Marshmallow, you can get the security updates till r81 only.
Sync the AICP Rom repos from MM branch. I believe it is this: https://github.com/AICP/platform_manifest/tree/mm6.0
1. open the "default.xml" file and modify this line to
Code:
<default revision="refs/tags/android-6.0.1_r81"
2. you need to cd into .repo/manifests and commit the change
3. Now you can do a "repo sync --force-sync"
4. After it's done, open the AICP github page so you can see all the repos you'll upgrade.
Now you'll have to cd into each AICP repository (that's available on the AOSP page too ( https://android.googlesource.com/platform/ ).
You need to make sure you're on the default branch by running "git branch". If not, run "git checkout -b mm6.0" (replace "mm6.0" with whatever you think fit).
So, for example:
Code:
cd frameworks/base
git branch
git checkout -b mm6.0 (only if you're not on a branch, like I previously mentioned)
git remote add aosp [url]https://android.googlesource.com/platform/frameworks/base[/url]
git pull aosp android-6.0.1_r81
You'll now see the merging screen in the terminal if there aren't any conflicts. Press "Ctrl+O" then "Ctrl+X" and done.
You gotta do the same thing for all the other repositories, but with the correct aosp link for each of them.
Please note: as AICP tracks many repos from CM, Slim ROMs, DU and Omni, you'll have to make sure you are tracking appropriate branches for the repos used from those ROMs.
Hope this helps :highfive:
Nitin
Thank you, nitin! This rom is actually your edit, at least if i remember right from one of your threads. I'll have a go at getting the security patches installed on my nexus 4
Hi @nitin.chobhe
This is the rom i use. https://forum.xda-developers.com/nexus-4/development/rom-aicp-mako-t3274469
with the intergrated adaway/wakeblock/privacy and stuff.
using the OTA update doesnt give any updates, and there is no more mako listed on the AICP site.
What do i use to do the CD commands? Terminal in my android? Do i change the default xml on my phone or?
The only thing on this rom is Omni, as far as i can tell.
Unfortunately that wasnt made too clear what program i use to pull and stuff! Sorry.
KitsuneFoxy said:
Hi @nitin.chobhe
This is the rom i use. https://forum.xda-developers.com/nexus-4/development/rom-aicp-mako-t3274469
with the intergrated adaway/wakeblock/privacy and stuff.
using the OTA update doesnt give any updates, and there is no more mako listed on the AICP site.
What do i use to do the CD commands? Terminal in my android? Do i change the default xml on my phone or?
The only thing on this rom is Omni, as far as i can tell.
Unfortunately that wasnt made too clear what program i use to pull and stuff! Sorry.
Click to expand...
Click to collapse
You'll have to do a lot of reading and searching before trying to merge the security patches. It is not as easy as copy/ pasting some stuff/ files from server to your phone. Search on xda about how to build a ROM and when you build it successfully, then refer the steps I mentioned above.
Nitin
Thanks!
Since i like your specific version. I'll try my best.