Related
Just IN....
The nice smooth LiquidSmooth with MarshMallow 6.0 and latest android-6.0.1_r10.
Install:
First time installing LiquidSmooth to your Find5, or coming from another ROM:
- Make sure you're running a proper working Recovery (TWRP 2.8.6.0 recommended)
- Copy GApps and LS-MM-v6.0--YYYY-MM-DD-liquid_find5.zip to your internal SDCard
- Boot into Recovery
- DO A DATA WIPE / FACTORY RESET
- Flash LS-MM-v6.0--YYYY-MM-DD-liquid_find5.zip
- Flash GApps zip (I you don't need all Google feature, i recommend Opengapps, mini)
- Reboot
Works:
- Device boots
- Graphics working OK (No stress tests done)
- WiFi, bluetooth works
- Vibrator, sounds, apps, etc. works
Does not work:
- Cellular network is unavailable. I will fix this in my next update
- Minor things not tested (Please give your input or raise issues)
Cheers, Wolverine2k
XDA:DevDB Information
Unofficial LiquidSmooth MM6.0 | Oppo Find 5, ROM for the Oppo Find 5
Contributors
wolverine2k
Source Code: https://github.com/wolverine2k?tab=repositories
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Find5, OpenRecovery
Based On: CyanogenMod, LiquidSmooth
Version Information
Status: Alpha
Created 2015-12-04
Last Updated 2016-01-25
Reserved
Reserved
Sorry guys. My repo is messed up now. I need to fix certain errors in kernel and cm13 frameworks before anything is delivered. Working on it...
I will test it out for you but i am not sure how I can help you. If you release the rom I will try to flash it.
I currently already have cm13 from wux on my find 5 running.
Haas8 said:
I currently already have cm13 from wux on my find 5 running.
Click to expand...
Click to collapse
Ditto, and not sure if wuxianlin is going to release newer builds. Even with the existing bugs, I like CM13:
The big 3 problems with Oppo Find 5 CM13 builds are WiFi hotspot not working, bluetooth audio not working, video recording not working. If this is going to be an active ROM that will be maintained and I can help testing, I'll install it.
New build with Liquidsmooth this time. Help yourself...
wolverine2k said:
New build with Liquidsmooth this time. Help yourself...
Click to expand...
Click to collapse
Excellent news! Any success with getting hotspot/BT audio/video recording working in this new release?
Mateus109 said:
Excellent news! Any success with getting hotspot/BT audio/video recording working in this new release?
Click to expand...
Click to collapse
Nope. All these things will work but right now I am stuck with simcard not being detected. Am trying to debug that. And get the camera profiles up and running.
Dear All,
I am changing companies and also moving computer builds these days. So I will not be able to work on this anymore. But hopefully, I will come back with an Oreo build for our beloved Find5. I will close all the other development threads that I have since no further development will take place on the older versions.
BR; Wolverine
I'm here to question the device owner. There are few sources around about this device. They are raw and they are as common always experimental. Does anyone need them?
Furthermore, I can sum up here any sources I or other get to find about this device or its periphery.
If you are eager to Void your Warranty please Mind and Acknowledge that every modification only affects you and your contract and noone else.
custom rom
http://forum.xda-developers.com/xperia-xa/development/f3112-f3116-cyanogemod-13-project-t3488890
Silversniper said:
I'm here to question the device owner. There are few sources around about this device. They are raw and they are as common always experimental. Does anyone need them?
Furthermore, I can sum up here any sources I or other get to find about this device or its periphery.
Click to expand...
Click to collapse
Very good thing, I'm trying to build a CM13 rom from sources and I'm not sure if I have all required sources. For now I have, kernel sources with some "vendor" files from Sony and I found all build parameters like offsets/adresses and correct cmdline (no thanks to Sony because never released or mentioned them), the device tree dumped from my device, and I will dump the vendor tree too.
Now I need the defconfig for CM (very not sure if the stock one will work) , and some files like the boardconfig and some config files. I'm using the Elephone P9000 sources for sample, almost the same device (hardware side) and source files.
If I have some time I will try to upload files to git but I never tried before (sync only)...
rrvuhpg said:
Very good thing, I'm trying to build a CM13 rom from sources and I'm not sure if I have all required sources. For now I have, kernel sources with some "vendor" files from Sony and I found all build parameters like offsets/adresses and correct cmdline (no thanks to Sony because never released or mentioned them), the device tree dumped from my device, and I will dump the vendor tree too.
Now I need the defconfig for CM (very not sure if the stock one will work) , and some files like the boardconfig and some config files. I'm using the Elephone P9000 sources for sample, almost the same device (hardware side) and source files.
If I have some time I will try to upload files to git but I never tried before (sync only)...
Click to expand...
Click to collapse
Don't need to hesitate. I'll try to put the directions I've gathered here up today so it is done.
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
rrvuhpg said:
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
Click to expand...
Click to collapse
cool.. if work I would like to have it on my f3111 !!
rrvuhpg said:
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
Click to expand...
Click to collapse
Can you publish some brief preview?
Need to say the sources I had just seem to be down, so can't share them.
Through which Program are these to flash? If you're that far I can hold a look at it and may join in your development.
Verification of the Vendor Files is something I was not very good at it, not even a yolk I managed.
Silversniper said:
Can you publish some brief preview?
Need to say the sources I had just seem to be down, so can't share them.
Through which Program are these to flash? If you're that far I can hold a look at it and may join in your development.
Verification of the Vendor Files is something I was not very good at it, not even a yolk I managed.
Click to expand...
Click to collapse
For now the only preview I can publish are the CM13 boot and recovery "as is", I'm not sure if it can help but I will release them if someone want to port others MTK Roms on XA. ( Never booted any ported rom with the stock kernel, stuck at Sony logo)
Flashing is easy: the recovery with fastboot and Rom/boot in a single flashable zip on the SD.
The kernel sources are coming from 33.2.B.2.95 open source archive from Sony but built from the lastest CM13 and Google git sources.
The vendor tree from 33.2.B.2.93 dumped from my phone, only common files with the P9000 are on my git for now.
The device tree from P9000 sources (from @Deepflex git) but seem OK.
CM13 have Android 6.0.1, I don't know if the security patch is the last one but August for sure.
I'm not so far from a finished build (not mean fully bootable), for now I successfully build a full CM13 for the Elephone P9000 (the twin of the XA, I'm using it as base). It mean my "kitchen" is working Now I'm trying to identify the last proprietary files from all others stock/cm13 libs, modify make files and cross my fingers it will fully build without errors.
You can join me no problem all people are welcome because I can't do all alone
rrvuhpg said:
For now the only preview I can publish are the CM13 boot and recovery "as is", I'm not sure if it can help but I will release them if someone want to port others MTK Roms on XA. ( Never booted any ported rom with the stock kernel, stuck at Sony logo)
Flashing is easy: the recovery with fastboot and Rom/boot in a single flashable zip on the SD.
The kernel sources are coming from 33.2.B.2.95 open source archive from Sony but built from the lastest CM13 and Google git sources.
The vendor tree from 33.2.B.2.93 dumped from my phone, only common files with the P9000 are on my git for now.
The device tree from P9000 sources (from @Deepflex git) but seem OK.
CM13 have Android 6.0.1, I don't know if the security patch is the last one but August for sure.
I'm not so far from a finished build (not mean fully bootable), for now I successfully build a full CM13 for the Elephone P9000 (the twin of the XA, I'm using it as base). It mean my "kitchen" is working Now I'm trying to identify the last proprietary files from all others stock/cm13 libs, modify make files and cross my fingers it will fully build without errors.
You can join me no problem all people are welcome because I can't do all alone
Click to expand...
Click to collapse
good work , but I am noob to create rom with kitchen .. only zip edit I know
Yesterday I successfully built CM13 for XA from sources
But news are not good, the CM recovery is fully working as expected but the rom is stuck just after the Sony logo (Mediatek screen with "loading...") like on my previous attempts to port other roms. The kernel built from CM kitchen do the same... I will upload my git and my rom to see if someone have an idea on the problem. Now I will focus on the "vendor" files, but I'm not sure if it's the real problem. Can it be a locked preloader/kernel or something like that?
EDIT: I think the boot problem is related to the defconfig file from Sony kernel sources, I will try to change some settings. (the door for adding kernel features :good
rrvuhpg said:
Yesterday I successfully built CM13 for XA from sources
But news are not good, the CM recovery is fully working as expected but the rom is stuck just after the Sony logo (Mediatek screen with "loading...") like on my previous attempts to port other roms. The kernel built from CM kitchen do the same... I will upload my git and my rom to see if someone have an idea on the problem. Now I will focus on the "vendor" files, but I'm not sure if it's the real problem. Can it be a locked preloader/kernel or something like that?
EDIT: I think the boot problem is related to the defconfig file from Sony kernel sources, I will try to change some settings. (the door for adding kernel features :good
Click to expand...
Click to collapse
Love you!
I will buy this phone thanks to you :highfive:
Thank you for your work on our phone, it's very cool.
I would have helped if i could develop myself. If you need help get in touch with me i know some great devs who could maybe help you
any news @rrvuhpg ?
Yes I have some news but I want to create a dedicated thread for the CM13 project with updates, explanations and downloads to avoid off topic here. I am on holiday on next week and I will have time to work on it and give explanations. For now I'm stuck on boot because of Sony extra settings in the boot process, it's the first time I see a bootstrap and TA partition mount on a MTK device. If you know a dev for helping me passing the Sony part in the boot init it can be great :angel:
Other thing, I updated my git with parts of the update made by @Deepflex on the P9000 sources and my recent changes.
rrvuhpg said:
Yes I have some news but I want to create a dedicated thread for the CM13 project with updates, explanations and downloads to avoid off topic here. I am on holiday on next week and I will have time to work on it and give explanations. For now I'm stuck on boot because of Sony extra settings in the boot process, it's the first time I see a bootstrap and TA partition mount on a MTK device. If you know a dev for helping me passing the Sony part in the boot init it can be great :angel:
Other thing, I updated my git with parts of the update made by @Deepflex on the P9000 sources and my recent changes.
Click to expand...
Click to collapse
sorry first time I use sony ... I wish you to have nice holiday !
Hello,
this thread is only for development discussion regarding development of android for msm8974. If you have anything useful, it's the right place, however, it's not for non-dev things.
Current state of cam:
working, though, still low quality. Will be fixed on v6. (and no videocam)
if you wanna have live chat, you can join an IRC
http://webchat.freenode.net/?channels=#freexperia
placeholder
Ok. Seems I have wasted time with camera I think file which I used as a hal for nougat (camera.msm8974.so) from stock rom is not even used on stock rom, its just an aosp camera hal which is compiled by sony rom compilation! Somebody need to comfirm that please (just install stock rom 4.6.1.A.236 and remove camera.msm8974.so from system/lib/hw , try if camera working), I have no free time to install that stock rom to test that thing but I think that stock rom uses camera.qcom.so (which is not wrapper I think, its sony special camera hal), I am pretty sure that these lib is camera hal which sony uses on that rom! Somebody need to confirm!
So now i will explain all a little bit more
It is possible to get 3.4 kernel booting and working but the problem are the camera blobs for 3.4 too
All cam blobs above 4.4.4 can not used because they need drm keys but if you unlock your bootloader you will lose them
We have disscued this with all old cm maintainer and aosp devs including me as i'm one of the aosp devs
Booting 3.4 should need some hal changes in display and audio and the stock kernel need a lot of patches to get it boot on nougat
So in general 3.4 will work but we should focus on 3.10 its more efficend and if you see the progress over the last year we have done something which has no other manufacture. I fully understand all off you but we want to continue support of our devices for a long time and this is definitly easier on 3.10.
I know that sony will keep msm8974 as long as possible in the open device programm but it will end in some time because qcom discontinued the ardeno support which make it harder for all of us. I will give my best to bring msm8974 on 3.10 stable as a rock and hopefully with cam
So keep it up and help to fix the things
If you need some help or some more infos you can write me via pm or hangouts
munjeni said:
Ok. Seems I have wasted time with camera I think file which I used as a hal for nougat (camera.msm8974.so) from stock rom is not even used on stock rom! Somebody need to comfirm that please (just install stock rom 4.6.1.A.236 and remove that file from system/lib/hw , try if camera working), I have no free time to install that stock rom to test that thing but I think that stock rom uses camera.qcom.so which is not wrapper as a tomascus say, I am pretty sure that these lib is camera hal which sony uses on that rom! Somebody need to confirm
Click to expand...
Click to collapse
huh? isn't that camera.qcom.so too small to be hal? (sorry, still no device...)
munjeni said:
Ok. Seems I have wasted time with camera I think file which I used as a hal for nougat (camera.msm8974.so) from stock rom is not even used on stock rom! Somebody need to comfirm that please (just install stock rom 4.6.1.A.236 and remove that file from system/lib/hw , try if camera working), I have no free time to install that stock rom to test that thing but I think that stock rom uses camera.qcom.so which is not wrapper as a tomascus say, I am pretty sure that these lib is camera hal which sony uses on that rom! Somebody need to confirm
Click to expand...
Click to collapse
Stock uses camera. msm8974.so but it checks if drm vertity is present but we can nor rewrite the whole l drm verity on 3.4 because its closed source
SuperLamic said:
huh? isn't that camera.qcom.so too small to be hal? (sorry, still no device...)
Click to expand...
Click to collapse
I don't know but I will try in next few days when I get more free time for installing sotck rom
rcstar6696 said:
So now i will explain all a little bit more
It is possible to get 3.4 kernel booting and working but the problem are the camera blobs for 3.4 too
All cam blobs above 4.4.4 can not used because they need drm keys but if you unlock your bootloader you will lose them
We have disscued this with all old cm maintainer and aosp devs including me as i'm one of the aosp devs
Click to expand...
Click to collapse
Thats bul****! When you unlock bootloader on stock rom you still have working camera!!! WTH drm keys!
rcstar6696 said:
Booting 3.4 should need some hal changes in display and audio and the stock kernel need a lot of patches to get it boot on nougat
Click to expand...
Click to collapse
That allso is not true! Only selinux and mmap proc tunable for mmap_base ASLR is need to get it boot on nougat! For more info here you can see kernel which boots on nougat, see commits for more info! https://github.com/munjeni/android_kernel_sony_msm/commits/master
Please don't post misinformation if you are not 100% sure!
munjeni said:
Ok. Seems I have wasted time with camera I think file which I used as a hal for nougat (camera.msm8974.so) from stock rom is not even used on stock rom, its just an aosp camera hal which is compiled by sony rom compilation! Somebody need to comfirm that please (just install stock rom 4.6.1.A.236 and remove camera.msm8974.so from system/lib/hw , try if camera working), I have no free time to install that stock rom to test that thing but I think that stock rom uses camera.qcom.so (which is not wrapper I think, its sony special camera hal), I am pretty sure that these lib is camera hal which sony uses on that rom! Somebody need to confirm!
Click to expand...
Click to collapse
Camera.msm8974 is an useless lib on stock rom
Camera.qcom is Sony camera hal.
I had found out it few months ago.
munjeni said:
Thats bul****! When you unlock bootloader on stock rom you still have working camera!!! WTH drm keys!
That allso is not true! Only selinux and mmap proc tunable for mmap_base ASLR is need to get it boot on nougat! For more info here you can see kernel which boots on nougat, see commits for more info! https://github.com/munjeni/android_kernel_sony_msm/commits/master
Please don't post misinformation if you are not 100% sure!
Click to expand...
Click to collapse
If you read it again you will see that i talk about drm verity not drm keys
Test it if you want we had cm13 booting on 3.4 and it was only possible with display patches audio patches where only needed to fix some small sound issues
Chirayu desai one of the cm maintainer can confirm this.
Selinux is correct this needs to be rewritten and mmap too but i wanted to write it understandable for all guys not only for devs
The other thing about the camera hal is an info from alin but if you say he isnt correct then you will be right :good:
It could be possible that the cam will start without but not with all Features
Do what you want but i'm quite sure that you don't get a fully working cam
rcstar6696 said:
If you read it again you will see that i talk about drm verity not drm keys
Click to expand...
Click to collapse
I don't know which device you have but I speak about Honami and Amami only. On Honami and Amami unlocking bootloader have nothing to do with camera, only some small changes in picture quality can be noticed. I will definitelly go to 3.10 kernel till after camera gets working
mkdmc said:
Camera.msm8974 is an useless lib on stock rom
Camera.qcom is Sony camera hal.
I had found out it few months ago.
Click to expand...
Click to collapse
Thats what I thinking now too! Did you tested, whats happening when camera.msm8974.so gets removed, is camera working? I need confirmation on rom 4.6.1.A.236 ! Which I found camera.qcom.so uses chocobal and excal blobs, camera.msm8974.so uses nothing from that.
rcstar6696 said:
Stock uses camera. msm8974.so but it checks if drm vertity is present but we can nor rewrite the whole l drm verity on 3.4 because its closed source
Click to expand...
Click to collapse
Did you try to grep that file? For example
strings camera.msm8974.so | grep drm
You can see null results about drm
rcstar6696 said:
So now i will explain all a little bit more
It is possible to get 3.4 kernel booting and working but the problem are the camera blobs for 3.4 too
All cam blobs above 4.4.4 can not used because they need drm keys but if you unlock your bootloader you will lose them
We have disscued this with all old cm maintainer and aosp devs including me as i'm one of the aosp devs
Booting 3.4 should need some hal changes in display and audio and the stock kernel need a lot of patches to get it boot on nougat
So in general 3.4 will work but we should focus on 3.10 its more efficend and if you see the progress over the last year we have done something which has no other manufacture. I fully understand all off you but we want to continue support of our devices for a long time and this is definitly easier on 3.10.
I know that sony will keep msm8974 as long as possible in the open device programm but it will end in some time because qcom discontinued the ardeno support which make it harder for all of us. I will give my best to bring msm8974 on 3.10 stable as a rock and hopefully with cam
So keep it up and help to fix the things
If you need some help or some more infos you can write me via pm or hangouts
Click to expand...
Click to collapse
Hi
thanks for your reply. First, excuse me if i miss some point or if i'm not accurate: im new to this world. I learn cm with my z3, running my first 'mka bacon', around 1 year ago. I read a lot (xda, aosp doc, an listen the experimented devs). I agree with you that running a 3.4 kernel on aosp will be hard as it need a lot of changes but, for cm, switching to caf HAL variant need only a few variables changes. Now i am able to boot cm-13.0 and cm-14.0 on z3 without changing the build tree and this cm-13.0 is now used at daily usage.
Obliviously it doesn't change anything to camera facts.
About the 3.10 kernel, the officials cm maintainers insists a lot that i work with it but after we got a "won't fix" on the screen flickering issue it reveal the problem was a panel driver init missing, i try to fix but it is out of my knowledge, so i decide to drop the 3.10 kernel definitively as it will remain unusable for z3/z3c.
I totally get the idea of only one kernel for all devices and really agree with that. If, one day, this screen flickering issue get fixed, i will be glad to give another try and will contribute as much as i can. But for now users have an upgraded rom, almost working, with recent security patches.
About the camera, i doubt it is related to TA partition.
I just made a test with:
z3 stock .575 locked bootloader
z3 stock .200 unlocked bootloader
z3 cm-12.1
Camera on both stock z3 are working the same way.
I need to make the same test with both stock device on the same rom version now.
munjeni said:
I don't know which device you have but I speak about Honami and Amami only. On Honami and Amami unlocking bootloader have nothing to do with camera, only some small changes in picture quality
Click to expand...
Click to collapse
Drm verity are not the same as drm keys the keys are needed to get some Algorithmen to work. So this explains your lose of qualiy but drm verity is a protection to protect data and libs. On stock you have a implimenation that verfiy the loading of the carefull data and drm will be okay but these implimenation is closed source and needs to be e rewritten and this is nearly impossible because no other devices has this in a so extremly way then the sony devices
You can look into hammerhead source and you see some commits about drm verity too but hammerheads cam libs are not included in the verity
I have castor and sirius
---------- Post added at 10:00 PM ---------- Previous post was at 09:55 PM ----------
nailyk said:
Hi
thanks for your reply. First, excuse me if i miss some point or if i'm not accurate: im new to this world. I learn cm with my z3, running my first 'mka bacon', around 1 year ago. I read a lot (xda, aosp doc, an listen the experimented devs). I agree with you that running a 3.4 kernel on aosp will be hard as it need a lot of changes but, for cm, switching to caf HAL variant need only a few variables changes. Now i am able to boot cm-13.0 and cm-14.0 on z3 without changing the build tree and this cm-13.0 is now used at daily usage.
Obliviously it doesn't change anything to camera facts.
About the 3.10 kernel, the officials cm maintainers insists a lot that i work with it but after we got a "won't fix" on the screen flickering issue it reveal the problem was a panel driver init missing, i try to fix but it is out of my knowledge, so i decide to drop the 3.10 kernel definitively as it will remain unusable for z3/z3c.
I totally get the idea of only one kernel for all devices and really agree with that. If, one day, this screen flickering issue get fixed, i will be glad to give another try and will contribute as much as i can. But for now users have an upgraded rom, almost working, with recent security patches.
About the camera, i doubt it is related to TA partition.
I just made a test with:
z3 stock .575 locked bootloader
z3 stock .200 unlocked bootloader
z3 cm-12.1
Camera on both stock z3 are working the same way.
I need to make the same test with both stock device on the same rom version now.
Click to expand...
Click to collapse
Hey yes i was only talking about stock not about thr cm kernel
When did you test 3.10 the last time all display issues are normally solved if you use 1.3.3 kernel base
rcstar6696 said:
Drm verity are not the same as drm keys the keys are needed to get some Algorithmen to work. So this explains your lose of qualiy but drm verity is a protection to protect data and libs. On stock you have a implimenation that verfiy the loading of the carefull data and drm will be okay but these implimenation is closed source and needs to be e rewritten and this is nearly impossible because no other devices has this in a so extremly way then the sony devices
Click to expand...
Click to collapse
Where you found that info? Any log about it?
munjeni said:
Where you found that info? Any log about it?
Click to expand...
Click to collapse
Ask alin Jerpelea or chirayu deasi all infos i give too you are from them
For drm verity just use google :/
nailyk said:
screen flickering issue[/URL] it reveal the problem was a panel driver init missing, i try to fix but it is out of my knowledge
Click to expand...
Click to collapse
I'm oticed frezings and some strange things using that msm8994 display hal, but on my buld I have used codeaurora LA.BR.1.3.6_rb1.3 branch for display, camera and some things in media, I can confirm that display things fly, its soo smoth, video soo smooth, screen power off/on smooth... if you want to try here is it http://munjeni.myiphost.com/mynougat.tar.gz , don't forget to build kernel with script buildkernel.sh since it will install kernel headers from 1.3.3 and will build 1.3.3. kernel too. I have told jerpelea about it but no reaply about LA.BR.1.3.6
rcstar6696 said:
Hey yes i was only talking about stock not about thr cm kernel
When did you test 3.10 the last time all display issues are normally solved if you use 1.3.3 kernel base
Click to expand...
Click to collapse
Really? My last try was with the LA.BF64.1.2.2_rb4.7 branch. Great i have some waiting patches for fm and nfc! Unfortunately i half broke my original screen which make screen flickering debugging harder. I will give a try asap. Thanks for the hint!
nailyk said:
Really? My last try was with the LA.BF64.1.2.2_rb4.7 branch. Great i have some waiting patches for fm and nfc! Unfortunately i half broke my original screen which make screen flickering debugging harder. I will give a try asap. Thanks for the hint!
Click to expand...
Click to collapse
Just use nougat and everything from sonyxperiadev instruction page, its kernel 1.3.3 which is very good, extract things from mynougat.rar to android tree, build kernel with script buildkernel.sh (you will need some path modification to it), and the rest like mentioned...
[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:
As we all know the Oreo is something that is quite distant for our device.
We need testers for Oreo Builds who can report bugs with accuracy, provide the logs required and have basic experience in software testing.
Be aware that the current & later releases are unstable & cannot be used as daily drivers.
Downloads & Issue Tracker:
GDRIVE
Instructions to Boot the ROM:
1) Install Latest TWRP from twrp.me
2) Wipe All Partitions Including Internal SDCard
3) Format system & data partitions to ext4
4) Load The Zips & image onto external sdcard
5) Flash the Lineage zip
6) Reboot
BUGS
LED dead
Double tap to wake dead
Sensors dead
Camera dead
RIL dead
GPS dead (on "device only")
Sound dead
Freezes still here
Videos on Instagram still not loading
Microphone dead
Sepolicy Dead
Telegram Group for Testers & Any ROM Compilers Who Want to Help
https://t.me/Oreo_Z00A_8
Sources:
Lineage: https://github.com/LineageOS
Device ( Tree, Kernel, Deps ): https:/github.com/nutcasev15
XDA:DevDB Information
[WIP] Oreo Testing & Bug Fixing (Z00A/8), ROM for the Asus ZenFone 2
Contributors
nutcasev1.5, GiaSen, bernardobas, mauro128
Source Code: github.com/nutcasev15
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: MM BL, EXT4, Logic, Brain
Based On: Lineage
Version Information
Status: Alpha
Current Stable Version: None
Current Beta Version: None
Created 2018-06-19
Last Updated 2018-06-24
Reserved
Initial Builds <24-06-2018> (A/8)
Please build it for Z008 as well so that I will also test it
Fixed Download Links. Compiling 8.0 Now. Since the 15.1 builds are broken & old.
dnishchhal said:
Please build it for Z008 as well so that I will also test it
Click to expand...
Click to collapse
in that first moment the initial focus is on Z00a. the test results showing the evolution will be gradual for your model.
Sim card
The Sim card Doesn't work
Install instructions updated. No need to flash the boot img. It will cause a boot loop.
Thanks for working on this deserted device. I will try to help anywhere I can. Love you guyz
Is there a remote chance that this might become official in the future in case everything goes right ?
Sent from my ASUS_Z00A using XDA Labs
PedroCaseiro said:
Is there a remote chance that this might become official in the future in case everything goes right ?
Click to expand...
Click to collapse
Unlikely. Even if we get stable 8.1, they have a strict requirements to become official. Plus our repos are non mergable, so even if we go official, we can use some of the repos for compiling.
It's possible but not idea if it can really happen.
link my phone z008?
Awzil_deaf said:
link my phone z008?
Click to expand...
Click to collapse
Not available
Sent from my ASUS_Z00A using XDA Labs
Nice, very nice. This phone's hardware deserves a recent version of android.
Help fix some bugs
https://forum.xda-developers.com/an...-bug-fixing-bugs-porting-custom-roms-t2909599
Hey guys! I want to help fix some bug from this rom
Can be solved right if we try to change file from custom rom?
Sorry if I wrong... because that is only just for MTK devices.
---------- Post added at 10:35 AM ---------- Previous post was at 10:24 AM ----------
Awzil_deaf said:
link my phone ?
Click to expand...
Click to collapse
They work only for Z00A.The link of Z008 will come soon after Z00A project done.
Why you dont think if z00a and z008 have a same boot.img? '-'
Sent from my ASUS_Z00A using XDA Labs
Z008 (Z00A 20180623 build bootloops) 8.0 builds uploaded
Possible Fixes in the Source are:
Audio
Selinux Permissive
RIL
Doze
Hardware Overlays
Download links updated
Thanks for work
Pl.stable lineage rom
Tankkkks
nutcasev1.5 said:
As we all know the Oreo is something that is quite distant for our device.
We need testers for Oreo Builds who can report bugs with accuracy, provide the logs required and have basic experience in software testing.
Be aware that the current & later releases are unstable & cannot be used as daily drivers.
Downloads & Issue Tracker:
GDRIVE
Instructions to Boot the ROM:
1) Install Latest TWRP from twrp.me
2) Wipe All Partitions Including Internal SDCard
3) Format system & data partitions to ext4
4) Load The Zips & image onto external sdcard
5) Flash the Lineage zip
6) Reboot
BUGS
LED dead
Double tap to wake dead
Sensors dead
Camera dead
RIL dead
GPS dead (on "device only")
Sound dead
Freezes still here
Videos on Instagram still not loading
Microphone dead
Sepolicy Dead
Telegram Group for Testers & Any ROM Compilers Who Want to Help
https://t.me/Oreo_Z00A_8
Sources:
Lineage: https://github.com/LineageOS
Device ( Tree, Kernel, Deps ): https:/github.com/nutcasev15
XDA:DevDB Information
[WIP] Oreo Testing & Bug Fixing (Z00A/8), ROM for the Asus ZenFone 2
Contributors
nutcasev1.5, GiaSen, bernardobas, mauro128
Source Code: github.com/nutcasev15
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: MM BL, EXT4, Logic, Brain
Based On: Lineage
Version Information
Status: Alpha
Current Stable Version: None
Current Beta Version: None
Created 2018-06-19
Last Updated 2018-06-24
Click to expand...
Click to collapse
If it can help, for me LED is working…
[/COLOR]
EmilioDallaTorre said:
If it can help, for me LED is working…
Click to expand...
Click to collapse
it's good to know that...
Well, the group is on the telegram, come in and share your projects and we can develop the project better.
we stand by you
EmilioDallaTorre said:
If it can help, for me LED is working…
Click to expand...
Click to collapse
It works on the 8.0 builds. Known issue on 8.1