Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 7.x (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod 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. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 14.1 on your device, or coming from another ROM?
Unlock Bootloader!
Download the zip(s).
Install Appropriate FW base (STOCK MM 4.21.40.xx base is required) simple FW update package is available at my download link
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package. Open Gapps x86 7.1
Broken Features / Known Issues
VIDEO ENCODER/DECODER ISSUES: This results in green lines on videos/pictures taken using the Intel HW encoder/decoder and other playback issues dependent on video formats. See the list below:
Snapchat: thin greeen line tends to appear on recorded videos for snapchat
Asus Pixelmaster Camera App: Super resolution mode does not work. Turning off "Optimizations" from settings clears up any green line issues.
Some video formats do not play as expected
FM Radio is unsupported.
audio is a little weird in Real Racing 3.
sim 2 cannot be disabled (this is true for all CM builds on non qualcomm hardware)
Other than Fugu (Nexus Player TV box) there are no Vendor released M x86/x86_64 builds in existance. You may experience some issues with GAPPS and some known apps not loading or working correctly. Below is a list of KNOWN apps that do not currently run on CM13 based x86 Zenfone 2 builds :
Polaris Office, Chase Mobile, Showbox...
DRM content is currently broken
Live Display (color calibration) not working yet
Screen recording not working
Chromecast screen mirroring not working, native casting works though.
factory reset from setting menu has been reported to cause recovery boot loops.
Battery life is horrible, numerous display wakelock issues
CM14 (not device specific issues)
No CMTE yet
Status bar icon changing broken
CM file manager has trouble accessing external sdcard
Battery profile is non functional/string errors
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking or ask the same question over and over again.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
As the Zenfone2 has multiple models from multiple countries please include the following information in your report:
model #
CPU Speed / RAM Size
device state when errors occur (BT/wifi/nfc on ? On a call ? sitting idle on shelf ? )
method to reproduce if you've found something consistent
Download Links
CyanogenMod for Z00A/ ze551ml: ROM
CyanogenMod for Z008/ ze550ml: ROM
Recovery Links
Z00A
MM BL compatible TWRP: TWRP
Z008
MM BL compatible TWRP: TWRP
Google apps addon:
Recommend GAPPS for now as the updated x86 gapps.
Flashable Modem updates:
FOR INFO ON MM BOOTLOADER BASED BUILDS SEE THIS POST
XDA:DevDB Information
CyanogenMod 14.1 Nightly Bulids (Z00A/Z008), ROM for the Asus ZenFone 2
Contributors
jrior001, crpalmer, say99
Source Code: https://github.com/CyanogenMod/android_kernel_asus_moorefield
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 4.21.40.xxx stock base
Version Information
Status: Beta
Beta Release Date: 2016-11-09
Created 2016-11-09
Last Updated 2016-11-22
Reserved
Official CM-13.0 -> CM14.1 Upgrade Guide
As seen with my previous unofficial CM-13.0 builds based on the MM Stock roms, An upgrade to the MM Firmware and bootloader is required going forward.
This guide is here to assist.
1) Download ROM and 7.1 GAPPS
2) Download my Firmware Update package for Z00A or Z008 . FASTBOOT AND ADB ARE REQUIRED!
3) Follow the included instructions to update Firmware and flash the new compatible TWRP. If for some reason the new TWRP is not flashed automatically flash it manually via fastboot. "fastboot flash recovery recoverimagename.img
4) Reboot to recovery and flash CM 14 and Gapps, reboot and enjoy. Data Wipe on upgrade is not required
CM 14.1 from Stock MM
1) Unlock Bootloader
2) Flash compatible TWRP
3) Perform desired backups
4) From recovery, factory reset & install ROM & 7.1 GAPPS
5) Enjoy!
CM 14.1 from CM13 Mm based beta builds
1) Reboot to TWRP( should already have good version)
2) Flash CM14.1 and 7.1 GAPPS
3) Reboot and enjoy!!
Yes!!!
yes u made it sir.. most awaited build of the year.. we really appreciate your time and efforts given to the project.. May God bless you.. behalf of all the zf2 a big thanks to @jrior001 and @say99
Sent from my ASUS_Z008 using XDA-Developers mobile app
just a question. Do i need to be on MM Bloobs or can I upgrade straight from LP bloobs? Also has the Brazilian sensors bug been fixed on CM14.1?
leoarten said:
just a question. Do i need to be on MM Bloobs or can I upgrade straight from LP bloobs? Also has the Brazilian sensors bug been fixed on CM14.1?
Click to expand...
Click to collapse
Has this been resolved in stock? I've heard mixed reports. I've included the updated sensor firmware from the .144 stock update so if it's in there we got it.
See post 2 as I update it, gonna try trying o cover all possible situations in guide there.
Sent from my ASUS_Z00A using Tapatalk
Awesome!
Downloading...
Downloading now.
Is the camera bug still present on N? Shouldn't the MM BLOBS fix that?
Thanks for your effort, @jrior001 !!!!
Thanks.. but just to clarify.. I need to update bootloader to MM Blobbs before I install CM14 right? or just flash new TWRP and flash rom as per usual (from LP Bloobs)? Im a bit confused.. Yes I saw theres a MM Bloobs session.. but couldnt find the answer to this.
Awesome work btw
jrior001 said:
Has this been resolved in stock? I've heard mixed reports. I've included the updated sensor firmware from the .144 stock update so if it's in there we got it.
See post 2 as I update it, gonna try trying o cover all possible situations in guide there.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
leoarten said:
Thanks.. but just to clarify.. I need to update bootloader to MM Blobbs before I install CM14 right? or just flash new TWRP and flash rom as per usual (from LP Bloobs)? Im a bit confused.. Yes I saw theres a MM Bloobs session.. but couldnt find the answer to this.
Awesome work btw
Click to expand...
Click to collapse
Direct from post #2:
Official CM-13.0 -> CM14.1 Upgrade Guide
As seen with my previous unofficial CM-13.0 builds based on the MM Stock roms, An upgrade to the MM Firmware and bootloader is required going forward.
This guide is here to assist.
1) Download ROM and 7.1 GAPPS
2) Download my Firmware Update package for Z00A or Z008 . FASTBOOT AND ADB ARE REQUIRED!
3) Follow the included instructions to update Firmware and flash the new compatible TWRP. If for some reason the new TWRP is not flashed automatically flash it manually via fastboot. "fastboot flash recovery recoverimagename.img
4) Reboot to recovery and flash CM 14 and Gapps, reboot and enjoy. Data Wipe on upgrade is not required
Sent from my ASUS_Z00A using Tapatalk
Thank you very much..
jrior001 said:
Direct from post #2:
Official CM-13.0 -> CM14.1 Upgrade Guide
As seen with my previous unofficial CM-13.0 builds based on the MM Stock roms, An upgrade to the MM Firmware and bootloader is required going forward.
This guide is here to assist.
1) Download ROM and 7.1 GAPPS
2) Download my Firmware Update package for Z00A or Z008 . FASTBOOT AND ADB ARE REQUIRED!
3) Follow the included instructions to update Firmware and flash the new compatible TWRP. If for some reason the new TWRP is not flashed automatically flash it manually via fastboot. "fastboot flash recovery recoverimagename.img
4) Reboot to recovery and flash CM 14 and Gapps, reboot and enjoy. Data Wipe on upgrade is not required
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Thanks for your job, but no sensors found in brazilians devices...
ysllan said:
Thanks for your job, but no sensors found in brazilians devices...
Click to expand...
Click to collapse
Not that I can do anything about Asus's fail here but I'd like to see a logcat & dmesg captured from boot on this issue.
Sent from my ASUS_Z00A using Tapatalk
Is there Xposed for CM 14?
yumms said:
Is there Xposed for CM 14?
Click to expand...
Click to collapse
Nope right now. Just stay tuned for updates from rovo's thread.
Sent from my ASUS_Z00A using XDA Labs
jrior001 said:
Not that I can do anything about Asus's fail here but I'd like to see a logcat & dmesg captured from boot on this issue.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Did you use the 144 blobs? Asus solved problems with this version.
Enviado de meu ASUS_Z00A usando Tapatalk
I'm sorry to be a pain in the ars*. But you've mentioned you're basing on .144 stock update right? Having said that the link you posted with the zip to update bootloader Ive found files mentioning 4_21_40_134.bin (.134) wouldnt this be the reason sensors arent still working for brazilians devices? I had a look at Asus website and this is fix has been implemented on .144 update. So is this update on script and files updating bootloader or are they on the ROM itself..
Now I know the rules on XDA and I wouldnt dare to ask for ETA, however if this is the case, I would ask very politely if you could update the scripts files to .144 whenever's convenient for you and whenever you have time. That would be much appreciate. I will be coming back to this post and will be waiting anxiously for this.. Take you time and Thank you again.
jrior001 said:
Has this been resolved in stock? I've heard mixed reports. I've included the updated sensor firmware from the .144 stock update so if it's in there we got it.
See post 2 as I update it, gonna try trying o cover all possible situations in guide there.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
jrior001, crpalmer, say99 are best!)) Makes backup and installed
see, told you guys that it will be soon please take use of logcat whenever you guys are reporting some issue, we won't be able to do anything without logcat if we can't produce it on our device. Enjoy people
jrior001 said:
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 7.x (Nougat), which is designed to increase performance and reliability over stock Android for your device.
CyanogenMod 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. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 14.1 on your device, or coming from another ROM?
Unlock Bootloader!
Download the zip(s).
Install Appropriate FW base (STOCK MM 4.21.40.xx base is required) simple FW update package is available at my download link
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package. Open Gapps x86 7.1
Broken Features / Known Issues
VIDEO ENCODER/DECODER ISSUES: This results in green lines on videos/pictures taken using the Intel HW encoder/decoder and other playback issues dependent on video formats. See the list below:
Snapchat: thin greeen line tends to appear on recorded videos for snapchat
Asus Pixelmaster Camera App: Super resolution mode does not work. Turning off "Optimizations" from settings clears up any green line issues.
Some video formats do not play as expected
FM Radio is unsupported.
audio is a little weird in Real Racing 3.
sim 2 cannot be disabled (this is true for all CM builds on non qualcomm hardware)
Other than Fugu (Nexus Player TV box) there are no Vendor released M x86/x86_64 builds in existance. You may experience some issues with GAPPS and some known apps not loading or working correctly. Below is a list of KNOWN apps that do not currently run on CM13 based x86 Zenfone 2 builds :
Ingress, Polaris Office, Chase Mobile, Showbox...
DRM content is currently broken
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking or ask the same question over and over again.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
As the Zenfone2 has multiple models from multiple countries please include the following information in your report:
model #
CPU Speed / RAM Size
device state when errors occur (BT/wifi/nfc on ? On a call ? sitting idle on shelf ? )
method to reproduce if you've found something consistent
Download Links
CyanogenMod for Z00A/ ze551ml:ROM
CyanogenMod for Z008/ ze550ml:ROM
Recovery Links
Z00A
MM BL compatible TWRP: TWRP
Z008
MM BL compatible TWRP: TWRP
Google apps addon:
Recommend GAPPS for now as the updated x86 gapps.
Flashable Modem updates:
FOR INFO ON MM BOOTLOADER BASED BUILDS SEE THIS POST
XDA:DevDB Information
CyanogenMod 14.1 Nightly Bulids (Z00A/Z008), ROM for the Asus ZenFone 2
Contributors
jrior001, crpalmer, say99
Source Code:https://github.com/CyanogenMod/android_kernel_asus_moorefield
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 4.21.40.xxx stock base
Version Information
Status: Beta
Beta Release Date: 2016-11-09
Created 2016-11-09
Last Updated 2016-11-09
Click to expand...
Click to collapse
haha thx so much bt wechat isnt working too haha
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
What's new in 3.2.2-0:
</> CHANGELOG : ? </>
Code:
Code:
* adb backup fixes
* OTA style update zips will now install automatically without prompting for decrypt
* minor tweaks to handling date/time on Qualcomm devices
* updates to some language translations
</> DOWNLOAD ? </>
https://twrp.me
$ TIP $
You can update it from previous TWRP recovery if you already have it installed, else install it as fresh by using adb or Official TWRP Installer app from google play store or similar
To flash with Fastboot/Adb:
Code:
Code:
make sure OEM-Unlocking is ON
$ adb reboot bootloader
$ fastboot flash recovery twrp-3.2.2-0-woods.img
To contribute:
TWRP Code Review
TeamWin
XDAevDB Information
Moto E4 ROMs, Kernels, Recoveries, & Other Development
Contributors
iykeDROID™ {dumbDevpr*}
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created: 2018-07-12
Last Updated: 2018-07-13
Great news. Now I'm waiting for stable and fully working Oreo ROM and start flashing.
ka4o_pi4a said:
Great news. Now I'm waiting for stable and fully working Oreo ROM and start flashing.
Click to expand...
Click to collapse
from the looks of things on my side, i don't think that will happen in anytime too soon.
let's just hope for a God sent dev to take over the Moto E4(woods) development .
if any bug with the TWRP, create/open an issue regarding such bug on GitHub :
https://github.com/omnirom/android_bootable_recovery
( make sure to see how other issues were created and follow such trend )
thanks
I am getting a wrong architecture error (error 64 in twrp) when trying to flash ARM gapps.
EstebanxZ said:
I am getting a wrong architecture error (error 64 in twrp) when trying to flash ARM gapps.
Click to expand...
Click to collapse
wait for next update or use this at your own risk
https://t.me/motoe4woods/12179
Same here. Wrong architecture. Even the backup was corrupted and I wasn't able to flash back my stock ROM. This is my last Motorola device.
ka4o_pi4a said:
Same here. Wrong architecture. Even the backup was corrupted and I wasn't able to flash back my stock ROM. This is my last Motorola device.
Click to expand...
Click to collapse
i used it to install Both XOSP & Gapps Pico today.
Few days ago I was spent my day on trying to flash some ROM, but didn't manage to flash any (Pico,nano, micro, etc) gapps... All finished with the same error 64. Then I install last beta of twrp and successfuly install gapps, but can't boot into system (boot into recovery every time).
ka4o_pi4a said:
Few days ago I was spent my day on trying to flash some ROM, but didn't manage to flash any (Pico,nano, micro, etc) gapps... All finished with the same error 64. Then I install last beta of twrp and successfuly install gapps, but can't boot into system (boot into recovery every time).
Click to expand...
Click to collapse
please your issues on that specific ROM's thread.
As far as i know, the TWRP recovery works fine even before the unofficial beta... woods has come to it's best so far.
thanks.
Already do that. Also try with two or three different ROMs and get the same error. Doesn't matter, I'LL wait for some more stable version of twrp and some ROM.
Tks
Thanks man!
Laruzzo said:
Hi, this TWRP version to Moto E4 woods is not good.
It does not install GAPPS, and do not install SUPER SU.
With GAPPS the error is about 64 bits version. And with supersu it says that "Bad recovery no Unzip."
I tried with a unnoficial version and worked everything.
Please update in TWRP site to a new version with bug fix.
Look a this thread with the version that worked with Moto E4 woods.
https://forum.xda-developers.com/mo...rp-3-1-1-r1-port-xt1760-t3772249/post76177524
Click to expand...
Click to collapse
Dude,
learn how to read a full post with instructions & proper way of reporting an issue anywhere you find yourself.
Know you device SoC, Architecture, etc ... don't just talk any how.
also, commits has not been merged
see on gerrit.twrp.me :=> https://gerrit.twrp.me/#/c/android_device_motorola_woods/+/63/
Finally, always check to see if no one has report similar issue and been solved before you start writing sh*t into the air
https://postimages.org/
https://forum.xda-developers.com/showpost.php?p=77250466&postcount=6
NOTE : MOTO E4 SERIES IS ARM(32bit) Architecture Device, stop trying to flash/install ARM64 Gapps as you stop being dumb.
OK
Ok, I´m sorry you are the developer and I should thanks for your great work. May you please share here the alternative file that works with gapps? Because I cannot access telegram at the momment. Thank you very much and sorry again if my words was not good. I respect and admire your work.
Laruzzo said:
Ok, I´m sorry you are the developer and I should thanks for your great work. May you please share here the alternative file that works with gapps? Because I cannot access telegram at the momment. Thank you very much and sorry again if my words was not good. I respect and admire your work.
Click to expand...
Click to collapse
Download ⍖ ?
TWRP-323.0-Unofficial-woods.img
iykeDROID™ said:
TWRP is an open source, community project.
..
..iykeDROID™[/URL] {dumbDevpr*}
Source Code: https://github.com/TeamWin
[/SIZE][...his other way cause I doubt about official ¿‽
Click to expand...
Click to collapse
Abish4 said:
Format Data Partition with F2FS format is not available which is usually available with every Moto Device Kernel
Click to expand...
Click to collapse
please deal with the kernel source here : https://github.com/MotorolaMobilityLLC/kernel-mtk/tree/nougat-7.1.1-release-woods
Abish4 said:
Can you help with this other way cause I doubt about official ¿‽
Click to expand...
Click to collapse
due to negligence, you couldn't check the source code here : https://github.com/TeamWin/android_device_motorola_woods
also check the twrp site : https://twrp.me/motorola/motorolamotoe4.html
I cannot flash gapps arm 7.1.x
Hi. I have one MotoE4 XT1763 Mediatek MT6735 with unlocked bootload.
would you recommend flashing the
twrp-3.2.3-0-woods.img 15.1M
Or the
TWRP-323.0-Unofficial-woods.img 15.5M
for the Lenovo Moto E4(XT1762)
?
Thank you peoples. TWRP unofficial working fine
Hey peoples. Accidentally i wiped my system. I have a backup in pc. I dont have sd card right now. How can i put the backup wich is in pc back to TWRP backup folder in order to restore ?
LineageOS 15.1 (Beta v1.01)
for Moto E5 Play (james)
Boost Mobile/Virgin Mobile/Sprint Variants
LineageOS 15.1 is a free, community-built, aftermarket firmware distribution of Android 8.1.0 Oreo, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project (AOSP) with extra contributions from a myriad of developers and enthusiasts within the Android community. LineageOS can be used without need of having any Google application installed. LineageOS does still include various hardware-specific code, which is slowly being open sourced.
LineageOS Source Code: https://github.com/LineageOS
LineageOS Changelog: https://www.cmxlog.com/15.1
LineageOS Gerrit Code Review: https://review.lineageos.org/#/q/status:open
Kernel Source Code MSM8920: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-OCP27.91-23
This is a LineageOS 15.1 build based on Project Treble. More specifically, it is based on XDA Recognized Developer @phhusson's Phh-Treble and his ARM32 Vanilla GSI. Because the Moto E5 Play is officially supported by Project Treble, I have taken the vanilla GSI and made it bootable for our device. Along with a modified kernel from the stock Android 8.0.0 OS, I've compiled a TWRP flashable Lineage 15.1 custom ROM for the james. This vanilla ROM is very much bare-bones -- no GApps, no SU addon, etc. -- and is likely chocked full of bugs at this time. So, without further ado.....
DISCLAIMER: Your warranty is hereby null, void, and held for naught. By proceeding further, you are assuming full responsibility for any good or bad consequences which may result from flashing this ROM. While I have installed and tested this ROM on my own device, and can confirm boot up and basic functionality, I cannot yet elaborate on bugs and other types of instabilities. This is truly a work in progress at this point. So, to sum it up, FLASH THIS AT YOUR OWN RISK. I am hereby absolved of any liability from bricked, damaged, or otherwise inoperable devices.
SPECIFICATIONS:
Android Version: 8.1.0
Build: OPM2.171026.006
Kernel Version: 3.18.71
Security Patch Level: June 5, 2018
Build Date: June 26, 2018
LineageOS API: llama (9)
STATUS: Beta
Created: Thu, July 29, 2018 15:00:00
REQUIREMENTS/INSTRUCTIONS:
1. First and foremost, an unlocked bootloader is necessary;
2. TWRP custom recovery installed and force encryption disabled. Please visit @CodyF86's thread on how to do this, and please be sure and hit the THANKS button if you used his work;
3. Download the ROM zip from the below download link and store it on external device storage;
4. Boot your device into TWRP recovery;
5. Select Wipe, and swipe to perform a factory data reset. Now, select Wipe and then Format Data, and follow all prompts to commence formatting;
6. Reboot Recovery (often necessary to ensure proper mounting of /userdata after formatting the partition;
7. Select Install, navigate to the location of the ROM zip, and swipe to commence installation;
8. Reboot System (1st boot up can take around 3 minutes or more);
NOTE: This vanilla ROM does not include GApps so, if you want GApps, visit https://opengapps.org/ and download a package of your preference. If installing GApps, simply flash the package during the above installation process after Step 7, then Reboot System.
BUGS:
Working:
RIL
Bluetooth
WiFi
Not Working:
Camera
Please properly report bugs, with submission of a bug report if you know how. If not, please give a clear and concise explanation of the bug. NOTE: Please DO NOT report bugs if you are running modifications such as Magisk Modules, Xposed Framework, etc. This makes it nearly impossible to pinpoint, troubleshoot and fix bugs and instabilities. Also, please know that I am not a ROM maintainer for Project Treble or LineageOS. So, while I will do my best to resolve bugs and provide some bug fixes and updates, please do not ask for ETAs. I work 55+ hours a week at Motorola Mobility, LLC., so I don't always get a lot of free time.
THANKS & MENTIONS:
Thanks to @SuperR. for his awesome Windows Kitchen;
Thanks to @CodyF86 for breaking ground and building TWRP for the james;
Thanks and credits to @phhusson for his Phh-Treble Vanilla GSIs;
Thanks to the entire LineageOS team;
DOWNLOAD LINK:
LineageOS 15.1 (Beta v1.01): https://drive.google.com/open?id=1TPl879IQvVH2ajYG6ZJ2kobp_rMgRfE5
Guys please provide feedback and feel free to contribute on this. I have more custom ROMs on the way such as ResurrectionRemix, PixelExperience, and AOSP-Extended. But I don't have a lot of free time to maintain ROMs, so I'm going to need help ironing out bugs and compiling patches.
Hum that's weird, wifi works for me on Moto E5
For camera, I have the fix pending for two months, I just haven't committed it yet -_-'
Thanks so much for commenting. After wiping the Dalvik/ART & /cache, WiFi is now working. I'll keep my eyes open for your pending camera commit.
Update: WiFi,, Bluetooth and RIL appear to be functional. Over the next few days I'm in hopes that user feedback will provide me with more insight as to bugs & instabilities.
this boots fine on e5 plus after flashing e5plus-noverity kernel and magisk as for ril data and all i cant tell you until i fix my sprint e5plus modem files messed them up by accidently flashing a differnt e5plus rom will report back more when i manage to completly fix my phone
allenjthomsen said:
this boots fine on e5 plus after flashing e5plus-noverity kernel and magisk as for ril data and all i cant tell you until i fix my sprint e5plus modem files messed them up by accidently flashing a differnt e5plus rom will report back more when i manage to completly fix my phone
Click to expand...
Click to collapse
Ok thanks @allenjthomsen. Yeah there seems to be many of us in the same boat -- patiently waiting for Motorola Mobility to either release or "leak" some factory images for the Moto E5 series devices. I'm actually drafting a baseband radio thread now for the James, compiling a TWRP flashable installer to restore radio/modem firmware and reset the network config to factory default. I know of a couple of devs over at Android Central that may can dump baseband partitions for your device. Also, please provide me with your Baseband Version. Thanks...
I have a bootable Android 9.0-DP3 ROM for the James. Lots of stuff broken, so I'm going to get it more stable, implement a working GApps package, etc. before posting it. Going to try and get our camera app working on this ROM also, maybe see if I can talk @phhusson into sharing his fix. Hint hint
i can dump files if needed and btw i tried your lineage os and i couldnt get data but got signal and camera crash other than that it ran great on my replacement E5 Plus Sprint model
allenjthomsen said:
i can dump files if needed and btw i tried your lineage os and i couldnt get data but got signal and camera crash other than that it ran great on my replacement E5 Plus Sprint model
Click to expand...
Click to collapse
Thank you for your feedback. I have a camera fix underway. As far as data connectivity I've had some issues myself, so I'm dissecting that issue too.
I have the same problem with the camera with GSI roms on a motorola e5 plus (rhannah). I get the impression that Motorola has something not standard in its handling of cameras of this family of devices
What DPI is this device? 320dpi right?
nachoxda79 said:
What DPI is this device? 320dpi right?
Click to expand...
Click to collapse
Yes. 320dpi (xhdpi); 1280 x 720 resolution
MotoJunkie01 said:
Yes. 320dpi (xhdpi); 1280 x 720 resolution
Click to expand...
Click to collapse
Thanks dude.
@MotoJunkie01 Hey, if you get a second pm me. I got your rom to boot on the g6 play by switching kernels, so I decided to compile a treble rom myself and I can compile it successfully, but the rom won't boot...clang seg faults like 30 times trying to compile it, so I think that is the actual issue, but wanted to bounce a few things off of you. No worries, thanks.
CodyF86 said:
@MotoJunkie01 Hey, if you get a second pm me. I got your rom to boot on the g6 play by switching kernels, so I decided to compile a treble rom myself and I can compile it successfully, but the rom won't boot...clang seg faults like 30 times trying to compile it, so I think that is the actual issue, but wanted to bounce a few things off of you. No worries, thanks.
Click to expand...
Click to collapse
I tried to PM you but sending failed. I'll get on my PC and login through the browser. I think my messaging settings are preventing the PM from sending.
Thanks for your work. Would this Lineage ROM work for the T-Mobile variant of the E5 Play (XT1921-3)?
konradsa said:
Thanks for your work. Would this Lineage ROM work for the T-Mobile variant of the E5 Play (XT1921-3)?
Click to expand...
Click to collapse
Not likely. There's no real danger in trying it because my installer does not flash sensitive partitions, but only /system & /boot. While I don't perceive any chance of bricking your device, it would be at your own risk. You would be better off flashing your device with a Treble GSI. While this ROM is technically based on a Project Treble GSI, I done some mods to the stock boot image and compiled the installer from porting. Hence, the ROM should not be characterized as a GSI itself. By the way I do have firmware for the xt1921-3, which I will be posting in my Moto E5 firmware thread over the next couple days.
my model is moto e5 play (XT1920-15)
my model is moto e5 play (XT1920-15) , will it work also my codename is not james. also how we can backup stock rom. before trying dont we need stock rom for this phone , so we can be secure.
rehannasim said:
my model is moto e5 play (XT1920-15) , will it work also my codename is not james. also how we can backup stock rom. before trying dont we need stock rom for this phone , so we can be secure.
Click to expand...
Click to collapse
I can only confirm compatibility with the xt1921-5. But before trying it, as you have correctly noted, it is crucial to have a suitable backup of your /system and /boot partition, just in case anything goes wrong. Most times, backups are made using a custom recovery such as TWRP. However I'm not familiar with your variant and therefore do not know of a working TWRP for your device. I will check my firmware archive and see if I can find a package for your model.
Update; unfortunately, at this time I cannot find firmware or custom recovery for your variant. I would urge you to post under the Q&A thread and ask if any members have your model.
LePro 3 : How to install GSI Roms, and where to find them
The point of this discussion is to alleviate the confusion of installing and configuring GSI Roms.
Although many of us would prefer to use fully native Android Pie Roms that are specifically designed for our phones, we do not yet have Official Pie Rom options, and there isn't alot of Beta options to choose from. Consequently, we get bored easily and are always searching something new.
Thankfully, GSI provides a wide range of alternative options and there's nothing wrong with experimentation and quelling our curiosities. In the end, lets just make sure that we continue to support our XDA Le Pro 3 developers, and if you can afford to do something nice for them...Please do so!
This thread is a work in progress and and intended to be a group effort, your participation is very welcome and highly appreciated
The OP will change often to add further information, or to correct inaccuracies, dead links, etc. So remember to check the OP occasionally, for updated information and links for useful add-ons or fixes.
The goal is that participants/you; share experiences, reviews, and suggestions.
In example, which GSI Roms you've tried, what was the experience like, was it worth it the time, did you use add-ons, etc.
If your installation required plugins, add-ons, fixes and what specifically did you use, PLEASE provide the link...etc.
Please don't say that you used a zip file to fix something and then not mention the name of that item.
Again, this a teamwork thread, be descriptive, it helps us understand what works and what doesn't. Be kind, share, discuss, and answer questions with patience and humility. If this is all new to you, feel feel to ask for help. [/I]
For now, I am providing the steps that I personally took to install and try several GSI Roms, See the steps below to get started and try this new GSI option for yourself.
Step 1 - Gather all needed Files
Latest Twrp : https://twrp.me/leeco/leecolepro3.html
Base Rom Currently base rom options are : Lineage 15.1 Treble, AICP 13.1 and Bootleggers ( Trebled Version)
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Gapps 9.0 : https://opengapps.org/ (I personally use Nano, or Pico > Best to choose something small )
Lineage 15.1 Treble Build : https://forum.xda-developers.com/le-pro3/development/rom-lineageos-15-0-leeco-le-pro3-t3683720
Lineage Boot: https://mega.nz/#!uuoBiaDK!_6JlNChLg...7ZKRzCcwNI3_p0 (Can also be extracted from 15.1 or any trebled rom)
AICP 13.1 Treble version: https://forum.xda-developers.com/le-pro3/development/rom-aicp-13-0-pro3-aka-zl1-x727-x720-t3698058
Bootleggers https://forum.xda-developers.com/le-pro3/development/bootleggers-rom-x727-x720-t3838454
Preferred GSI Rom: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
BlackScreen Kernel for Oreo Base : https://androidfilehost.com/?fid=11410932744536996059
BlackScreen Kernels for Pie Base Rom : https://androidfilehost.com/?w=files&flid=285063
___________________________________________________________________________________________
Step 2 - Installation Part 1 - Automated Vendor Option - See Bottom of OP for more Manual vendor flash method
Longterm and recommended - Quick Recovery Method
******Boot to Recovery> Flash Preferred Base Rom > Flash Gapps, Flash Magisk******
1. Choose advanced wipe : Select system, Data, Cache and Dalvik Cache
2. Reboot Recovery
3. Flash Trebled Lineage or Trebled AICP ( from Links above)
4. Reboot Recovery - Flash Rom a second time.
5. Flash Gapps 8.1
6. Flash Magisk 17.1
7. Reboot to recovery, reboot to OS > Must do Basic Setup.
8. After setup - Reboot to Recovery Create full backup> Check Everything.
9. Optional save copy of Backup to PC, this will help you quickly restore the phone should you encounter any issues.
Once you have a full Backup of a your trebelized installation, you are now ready to install GSI Rom.
Some GSI Roms have Gapps included while others do not.
If you chosen GSI rom ( seems ideal) that does not have Gapps, you will need to flash Gapps 9.0
Step 3 - Installation Part 2
GSI Installation Steps
1. Reboot Recovery
2. Do a factory reset
3. Install GSI to system
4. Flash Gapps 9.0 ( if needed)
5. Flash Magisk
6. Reboot to recovery, reboot to OS > Setup GSI > Enjoy!
___________________________________________________________________________________________________________________
ADDONS and ISSUE FIXES ( Only if needed- some GSI's will not have these issues)
Safety Net Fix: https://forum.xda-developers.com/oneplus-5t/how-to/guid-bypassing-safetynet-august-t3837809
Adaptive Brightness Fix : [url]https://forum.xda-developers.com/attachment.php?attachmentid=4581000&d=1535255905
NFC Fix https://mega.nz/#F!kgdGiI6L Key: !_Gr9otePqXOX7yVLtjUxfQ ( Thanks to @ enigmatic92 and @ ademir.dias for providing a working accessible link)
Option 2 NFC Fix : Pie-NFCFix-Universal_v1.zip
Substratum Dark Mode : The Fix is simple join Substratum Beta then use a compatible Pie them
See more information here: https://forum.xda-developers.com/showpost.php?p=77651573&postcount=36
Disable Rounded Corners: https://goo.gl/CcEMzi ( Substratum add-on)
Substratum Beta through Google https://play.google.com/apps/testing/projekt.substratum
Android P dark themes : Pi Dark [substratum]
Here is a free dark overlay to get you started Pie compatible, Open Source, Signed-off-by: Harsh Shandilya
OverLay : https://mega.nz/#F!kAw1WK6I Key: !wtX2GAY2676wjGFiwNwpVg
___________________________________________________________________________________________________________________
Installation Option 2 -
Quicker install Method - You can choose to have no backup at all or save a partial recovery ( System,Root) which is very helpful to have available, if you break your installation
Step 1 - Installation Part 1
Gather your Preferred Base Rom , Gapps, Magisk
Boot to Recovery
Choose advanced wipe : Select system, Data, Cache and Dalvik Cache
Reboot Recovery
Flash Trebled Lineage or Trebled AICP ( see Links above)
Reboot Recovery - Flash Rom a second time.
No Gapps needed ( save alot of time by skipping setup)
Flash Magisk 17.1
Reboot to Recovery Create full backup> Check Everything.
( Note that you are not booting to system, this method install base and provides a recovery, to will help save time when starting over or returning to a standard Rom.)
Optional save copy of Backup to PC, this will help you quickly restore the phone should you encounter any issues.
Once you have your gappless backup of a your trebelized installation, you are now ready to install GSI Rom.
Some roms have Gapps included while others do not.
If you chosen GSI rom that does not have Gapps, you will need to flash Gapps 9.0
Step 2 - Installation Part 2
1. Reboot Recovery
2. Do a factory reset
3. Install GSI to system
4. Flash Gapps 9.0 ( if needed)
5. Flash Magisk
6. Reboot to recovery, reboot to OS > Setup GSI > Enjoy!
The steps listed above assumes that you know the fundamentals of fastboot, using TWRP recovery, etc.
Using GSI’s roms is essentially testing GSI roms, there is no guarantee, although quite a few run extremely well on many devices.
The instructions above are just guidelines, of course as per XDA policy, anything that you choose to flash is done at your own risk
Generic System Image (GSI) list
LePro 3 use type A
Here's a collection of available GSI ROMs, in order to keep it easy to choose what you want.
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Treble-Enabled Device Development
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Project Treble
https://forum.xda-developers.com/project-treble
With any GSI Rom, if it doesn't list our phone specifically ( Zl1 or Zl0) then you use the versions Label type A or : arm64 A only
I am personally using Havoc: https://sourceforge.net/projects/hav...0.zip/download
Installing updates - Steps Needed
The Base Rom method is easier a superior to using Trembled TWRP ( for me the using regular Twrp and Base cause the system to have better stability.
To update GSI Rom
You do not need to wipe any vendor partitions.
Place the update in your downloads folder, and unpack it.
Boot to recovery,
Clear simple cache,
Flash GSI rom to system,
Clear caches
Reboot to system > finished.
If you have a bootloop [email protected] reflash lineage boot.
Troubleshooting Tips
Trouble booting/stuck in bootloop ? : Resolution here: https://forum.xda-developers.com/showpost.php?p=77668925&postcount=71
UPDATE - September 20- 2018 - Manual Vendor Method - Using Codeworks New Treble TWRP
Download : twrp-3.2.3-0-20180919-codeworkx-zl1
Install Trebled TWRP
Choose Longterm or Quick method from Above, (regarding creating a backup)
After you have your Recovery, placed unpacked GSI Rom and vendor files on your Storage Drive,
Flash GSI to System
Flash 3 Vendor files
Flash Gapps if needed
Flash Magisk 17.1
Reboot to Recovery, clear cache
Reboot to system
If you have a good suggestion, I will add it to the OP and in will give your full deserved credit
Thanks to following members for their feedback and offer to help keep this thread accurate by providing reviews and their support @rob_z11, @Ramg77, @enigmatic92, @willngg @ademir.dias @4K2K
@*.*.*.* Please do not copy this OP into another thread without providing credit a link to this OP.
So far we we know that the following Roms work on the Leeco pro 3
Benzo, version 9/1
Havoc, most recent version. : Gapps is installed separately - I have experienced no issues at all with this rom. Currently using BlackScreen 5.3. r3
AOSP Extended 9.0 v6' Per @willngg : https://forum.xda-developers.com/showpost.php?p=77652380&postcount=37
If I left anyone out of this post let me know.
If anyone tries a GSI Rom not listed above, and it boot and runs, with success, please let me know so I can update this comment.
Today I installed the latest build of [9.0] [GSI] Pixel Experience P - UNOFFICIAL.
Very good and stable rom, with the same issues of the other GSI (Nfc, mobile network setup, stock camera)
It brings less personalization than Benzo but does not have as many problems with the Gapps that it comes pre-installed.
It's PR2 and it brings September security patch.
I'm noticing that all the GSIs that I've tried so far have a sharpness and screen definition that I did not see in Oreo, it's what I think.
Link: https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294
Ramg77 said:
Today I installed the latest build of [9.0] [GSI] Pixel Experience P - UNOFFICIAL.
Very good and stable rom, with the same issues of the other GSI (Nfc, mobile network setup, stock camera)
It brings less personalization than Benzo but does not have as many problems with the Gapps that it comes pre-installed.
It's PR2 and it brings September security patch.
I'm noticing that all the GSIs that I've tried so far have a sharpness and screen definition that I did not see in Oreo, it's what I think.
Link: https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294
Click to expand...
Click to collapse
I fully agree!
tsongming said:
So far we we know that the following Roms work on the Leeco pro 3
Benzo, version 9/1
Havoc, most recent version. : Gapps is installed separately - I have experienced no issues at all with this rom. Currently using BlackScreen 5.3. r3
If I left anyone out of this post let me know.
Click to expand...
Click to collapse
First things first, excellent work with the guide step by step, very complete.
I add to the information that there is a new version of Benzo (0912) but it was very difficult to install because the Gapps that are preinstalled have a conflict with the Google Play Store, once all the steps are finished and before starting the first boot of the system , the protection of Google (factory reset protection or FRP) must be removed by means of a PC program, otherwise the initial setting will not go beyond "Searching for Updates". How I said the installation of this Rom is complicated.
Finally in XDA as in the Russian forum 4PDA I read that is about to come out a patch to run the NFC in the GSI Android Pie Roms, hopefully so.
Informative post! Aosip has been treblized too, have not tried it as a base however.
Ace42 said:
Informative post! Aosip has been treblized too, have not tried it as a base however.
Click to expand...
Click to collapse
Thanks,
I am using AICP as a base for Havoc with the boot.img from lineage and Blackscreen 5.3.r3 .
Its a flawless installation, Gapps is installation separately the gapps issue that some GSI Roms bring is avoided completely.
Sound quality, Call Quality, Battery life all excellent. Plus, I have installed all of my usual Magisk mods (alot!) without breaking the install.
Ramg77 said:
First things first, excellent work with the guide step by step, very complete.
I add to the information that there is a new version of Benzo (0912) but it was very difficult to install because the Gapps that are preinstalled have a conflict with the Google Play Store, once all the steps are finished and before starting the first boot of the system , the protection of Google (factory reset protection or FRP) must be removed by means of a PC program, otherwise the initial setting will not go beyond "Searching for Updates". How I said the installation of this Rom is complicated.
Finally in XDA as in the Russian forum 4PDA I read that is about to come out a patch to run the NFC in the GSI Android Pie Roms, hopefully so.
Click to expand...
Click to collapse
Yes, its the 0901 version that has no issues, right?
I only tried the 09/12 version, after seeing your post. and prior to that I was on two separate versions of miui GSI. and 2 versions of P beta
The Miui 10 Oreo version will be excellent once its display bugs are worked out.
tsongming said:
Yes, its the 0901 version that has no issues, right?
I only tried the 09/12 version, after seeing your post. and prior to that I was on two separate versions of miui GSI. and 2 versions of P beta
The Miui 10 Oreo version will be excellent once its display bugs are worked out.
Click to expand...
Click to collapse
That's right, the 0109 is the stable version of Benzo.
Against my principles I passed Antutu to the Pixel Experience 9 that I am testing and it gave me a very good score although I still seem that Android 9 offers the best user experience on this phone and Antutu does not reflect that.
Edit: The phone did not raise temperature while running the Antutu tests.
Incredible work @tsongming!! You are a fine machine....
tsongming said:
Thanks,
I am using AICP as a base for Havoc with the boot.img from lineage and Blackscreen 5.3.r3 .
Click to expand...
Click to collapse
Do you still need the lineageOS boot.img if you're using blackscreen?
Plan on flashing GSI soon. Really appreciate your instructions as they will help me and many others.
tsongming said:
LePro 3 : How to install GSI Roms, and where to find them
The point of this discussion is to alleviate the confusion of installing and configuring GSI Roms.
Although many of us would prefer to use a fully native Android P Rom that is specifically designed for our phones, we do not currently have alot of native options.. In consequence, we get bored easily and are often ready to try something new.
Thankfully, we have options, and there's nothing wrong with experimentation and quelling our curiosities. Lets just make sure that we continue to support our own Le Pro 3 developers, and if you can afford it, do something nice for them
This thread is a work in progress and a group effort, your participation is very welcome and highly appreciated
The OP will change to add or change to add further information or correct inaccuracies. So check the OP occasionally.
The goal here is that all participants/ you to share experiences, reviews, and suggestions. I.E : which GSI Roms have you tried , what was your experience, was it worth it, did you use addons, if so what, can you provide the link...etc. or add ons that they have tried. This should be fun!
For now, I am providing the steps that I personally took to install and try several GSI Roms, See the steps below to try it for yourself..
Step 1 - Gather all needed Files
Latest Twrp : https://twrp.me/leeco/leecolepro3.html
Base Rom Currently two options Lineage 15.1 Treble and AICP Treble version
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Gapps 9.0 : https://opengapps.org/ (I personally use Nano, choose something small )
Lineage 15.1 Treble Build : https://sourceforge.net/projects/lin...1.zip/download
Lineage Boot: https://forum.xda-developers.com/att...9&d=1536591029 Can be used with AICP as well.
AICP Treble version: https://forum.xda-developers.com/showpost.php?p=77596157&postcount=4898
Preferred GSI Rom: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
BlackScreen 5.3.r3 : https://forum.xda-developers.com/showpost.php?p=77596092&postcount=540
ISSUE Resolutions Files
Safety Net Fix: https://forum.xda-developers.com/oneplus-5t/how-to/guid-bypassing-safetynet-august-t3837809
Step 2 - Installation Part 1
Longterm ( recommended - Quick Recovery Method)
******Boot to Recovery> Flash Preferred Base Rom > Flash Gapps, Flash Magisk******
1. Choose advanced wipe : Select system, Data, Cache and Dalvik Cache
2. Reboot Recovery
3. Flash Trebled Lineage or Trebled AICP ( from Links above)
4. Reboot Recovery - Flash Rom a second time.
5. Flash Gapps 8.0
6. Flash Magisk 17.1
7. Reboot to recovery, reboot to OS > Must do Basic Setup.
8. After setup - Reboot to Recovery Create full backup> Check Everything.
9. Optional save copy of Backup to PC, this will help you quickly restore the phone should you encounter any issues.
Once you have a full Backup of a your trebelized installation, you are now ready to install GSI Rom.
Some GSI Roms have Gapps included while others do not.
If you chosen GSI rom ( seems ideal) that does not have Gapps, you will need to flash Gapps 9.0
Step 3
GSI Installation Steps
1. Reboot Recovery
2. Do a factory reset
3. Install GSI to system
4. Flash Gapps 9.0 ( if needed)
5. Flash Magisk
6. Reboot to recovery, reboot to OS > Setup GSI > Enjoy!
___________________________________________________________________________________________________________________
Option 2 - Step 1
Quicker install Method - You can choose to have no backup at all or save a partial recovery ( System,Root) which is very helpful to have available, if you break your installation
Step 1
Gather your Preferred Base Rom , Gapps, Magisk
Boot to Recovery
Choose advanced wipe : Select system, Data, Cache and Dalvik Cache
Reboot Recovery
Flash Trebled Lineage or Trebled AICP ( see Links above)
Reboot Recovery - Flash Rom a second time.
No Gapps needed ( save alot of time by skipping setup)
Flash Magisk 17.1
Reboot to Recovery Create full backup> Check Everything. ( Note that you are not booting to system, this method install base and provides a recovery, to will help save time when starting over or returning to a standard Rom.)
Optional save copy of Backup to PC, this will help you quickly restore the phone should you encounter any issues.
Once you have your gappless backup of a your trebelized installation, you are now ready to install GSI Rom.
Some roms have Gapps included while others do not.
If you chosen GSI rom that does not have Gapps, you will need to flash Gapps 9.0
Step 2
1. Reboot Recovery
2. Do a factory reset
3. Install GSI to system
4. Flash Gapps 9.0 ( if needed)
5. Flash Magisk
6. Reboot to recovery, reboot to OS > Setup GSI > Enjoy!
The steps listed above assumes that you know the fundamentals of fastboot, using TWRP recovery, etc.
Using GSI’s roms is essentially testing GSI roms, there is no guarantee, although quite a few run extremely well on many devices.
The instructions above are just guidelines, of course as per XDA policy, anything that you choose to flash is done at your own risk
Generic System Image (GSI) list
LePro 3 use type A GSI
Here's a collection of available GSI ROMs, in order to keep it easy to choose what you want.
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Treble-Enabled Device Development
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Project Treble
https://forum.xda-developers.com/project-treble
Thanks to following members for their feedback and offer to help keep this thread accurate by providing reviews and their support
@rob_z11, @ Ramg77, @DrMyrkurs
Click to expand...
Click to collapse
Excellent job.
Thanks for your contribution and dedication for the our device.
Enviado de meu LEX720 usando o Tapatalk
Hi
Ramg77 said:
First things first, excellent work with the guide step by step, very complete.
I add to the information that there is a new version of Benzo (0912) but it was very difficult to install because the Gapps that are preinstalled have a conflict with the Google Play Store, once all the steps are finished and before starting the first boot of the system , the protection of Google (factory reset protection or FRP) must be removed by means of a PC program, otherwise the initial setting will not go beyond "Searching for Updates". How I said the installation of this Rom is complicated.
Finally in XDA as in the Russian forum 4PDA I read that is about to come out a patch to run the NFC in the GSI Android Pie Roms, hopefully so.
Click to expand...
Click to collapse
I've been running benzo without major problems for days.i updated to 9/12 with no problems.only new prob I found in the update is the mobile network is inaccessible from settings but 3rd party app can access it.no prob with gapps running.no play store issues either.great rom so far.cant wait to try havoc and a few others. Cool thread,thanks.
https://forum.xda-developers.com/le...ject-treble-lepro3-x72x-t3820844/post77636757
This is to fix adaptive brightness
Ascertion said:
Do you still need the lineageOS boot.img if you're using blackscreen?
Plan on flashing GSI soon. Really appreciate your instructions as they will help me and many others.
Click to expand...
Click to collapse
Probably not since Blackscreen overwrites the boot. When I first tried installing GSI's, I was only successful after using the Lineage boot, and the treble Black Screen had not been released yet.
rob_z11 said:
https://forum.xda-developers.com/le...ject-treble-lepro3-x72x-t3820844/post77636757
This is to fix adaptive brightness
Click to expand...
Click to collapse
Thanks, I added it to the OP
Good work with the guide mate
Thank you for this in-depth summary.
Here is my Antutu for the Havoc GSI
Sent from my LEX727 using XDA Labs
I flashed latest aex pie yesterday.just ran it for few hours.everything worked good and fast minus the usual nfc,and few settings arent complete but runs smooth and stable.moved back to latest benzo just cause it's more complete.but aex is still a great option.love options.lol
Resurrection Remix Oreo
If you're not familiar with Resurrection Remix (RR), it's a very customizable and feature rich ROM. It's packed with some many great features like a notification ticker (like in the good ol' Kitkat days), styling changes, custom gestures, and more! RR is based on LineageOS. This is a build originally developed on by (russel5), but abandoned in favor of AospEx and Pie projects of his. Personally, I'm not a fan of the direction taken in Pie and will be sticking with Oreo. I'll be developing the rom further with features, bug fixes and enhancements. Any suggestions or bugs should be opened as an issue on the Github.
Please report any issues you have on the Github. The issue tracker helps me keep organized and on top of stuff.
Downloads
GitHub
Installation
1. Download firmware zip
2. Download OpenGapps/MicroG/Whatever
3. Push to phone
4. Reboot to recovery (recommend TWRP) and do a full wipe
5. Flash RR then whatever else after (Gapps, ect)
6. Reboot
7. ???
8. Profit
General Info:
If you have issues with the camera being green, make sure you update your firmware to the most recent Oreo one via newflasher. I will update this with information regarding this. It's been months since I did it so I need to remember and hunt the files down I used (which is hard since my last computer died and I switched to Linux). I'd backup your Drm keys before doing anything if you do.
Exclude when flashing:
* fotakernel.sin
* kernel.sin
* simlock.ta (if you have it)
* system.sin
* userdata.sin
* vendor.sin
Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Special thanks to:
@modpunk
@russel5
Anyone else I'm forgetting
Source:
Repo
XDA:DevDB Information
[G8441, XZ1c] [8.1] Resurrection Remix v6.2.1 (Oreo), ROM for the Sony Xperia XZ1 Compact
Contributors
hockeymikey
Source Code: https://github.com/hockeymikey/android_device_sony_lilac
ROM OS Version: 8.x Oreo
Based On: LOS
Version Information
Status: Stable
Current Stable Version: 6.2.1
Created 4/19/2020
Last Updated 5/13/2021
Additional info
Changelog:
May 13th, 2021 - 6.2.1-2020.10.11
* Signature spoofing, tweaked building fixing issues
September 4th, 2020 - 6.2.1-2020.09.04
* First build, updated libraries, security update
April 20th, 2020 - 6.2.1-2018.11.08
* Last release from russel5
Has anyone tried it yet?
DerSteppo said:
Has anyone tried it yet?
Click to expand...
Click to collapse
Yes, very good rom but i find out on androidfilehost about half year, so old.
USB tethering doesnt work.
Plenty of functions.
Stable, fast, no lags, pretty battery acceptable, more than 1 day of battery life.
Display options from stock, stock camera works very good.
I think, we need upgrade RR to 7 or 8.
I am using it now for about week and its very good as daily.
And at this moment its way better than Q roms.
jurko217 said:
Yes, very good rom but i find out on androidfilehost about half year, so old.
USB tethering doesnt work.
Plenty of functions.
Stable, fast, no lags, pretty battery acceptable, more than 1 day of battery life.
Display options from stock, stock camera works very good.
I think, we need upgrade RR to 7 or 8.
I am using it now for about week and its very good as daily.
And at this moment its way better than Q roms.
Click to expand...
Click to collapse
You can't find the most recent version of the rom on AFH, I had to hunt it down from some random forum and the most recent one before that was unstable so wanted to get it out there for people to have. I really like RR. I'll test tethering, I thought it was fine but haven't really used it. Maybe I'll mess with 7 or 8 someday after I have this one developed alittle. I personally don't have any interest in Pie+.
Edit: USB tethering works fine for me. Must be an issue with your computer. I'm using Kubuntu 18.04 and works perfectly.
hockeymikey said:
You can't find the most recent version of the rom on AFH, I had to hunt it down from some random forum and the most recent one before that was unstable so wanted to get it out there for people to have. I really like RR. I'll test tethering, I thought it was fine but haven't really used it. Maybe I'll mess with 7 or 8 someday after I have this one developed alittle. I personally don't have any interest in Pie+.
Edit: USB tethering works fine for me. Must be an issue with your computer. I'm using Kubuntu 18.04 and works perfectly.
Click to expand...
Click to collapse
I am using Windows 8.1, but in other roms like stock or PE 10 USB tethering works. I push that on and no reaction in computer - networking.
If will be Havoc OS 2.x or BaikalOS, ill start interest in pie, because i had these roms in Mi Mix 2 and they was best. Havoc in general, can be compared with most functions with RR, Baikal from russia brats in battery life, performance and simplicity.
Idk if they dont arrive to XZ1c, but pie i liked was stock, Oxygen, Miui (with some bugs, but with future).
Still, oreo and nougat roms are older, but better in most things except mentioned roms.
jurko217 said:
I am using Windows 8.1, but in other roms like stock or PE 10 USB tethering works. I push that on and no reaction in computer - networking.
If will be Havoc OS 2.x or BaikalOS, ill start interest in pie, because i had these roms in Mi Mix 2 and they was best. Havoc in general, can be compared with most functions with RR, Baikal from russia brats in battery life, performance and simplicity.
Idk if they dont arrive to XZ1c, but pie i liked was stock, Oxygen, Miui (with some bugs, but with future).
Still, oreo and nougat roms are older, but better in most things except mentioned roms.
Click to expand...
Click to collapse
No idea, it has to be your computer I'm guessing. Make sure you're running the most recent version since that other versions found on the other thread is very buggy. Noted on them.
> Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Where's the boot.img?
asdf2345 said:
> Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Where's the boot.img?
Click to expand...
Click to collapse
It's in the zip file.
Got a new update out https://github.com/hockeymikey/android_device_sony_lilac/releases/tag/6.2.1-2020.09.04
Check it out and let us know how it works. Seems stable on my end from testing.
How does Resurrection Remix compare to CrDroid?
asdf2345 said:
How does Resurrection Remix compare to CrDroid?
Click to expand...
Click to collapse
No idea, can't remember testing out the Pie CrDRoid on here. I'm not a fan of Pie+ so it didn't interest me. Should test and report in, looks like they are similar being LOS based with decent amount of customization. CrDroid has signature spoofing, but I'm making a build with that added in for RR as I type. But yeah, let me know and what other features that CrDroid has that looks cool.
hockeymikey said:
Resurrection Remix Oreo
If you're not familiar with Resurrection Remix (RR), it's a very customizable and feature rich ROM. It's packed with some many great features like a notification ticker (like in the good ol' Kitkat days), styling changes, custom gestures, and more! RR is based on LineageOS. This is a build originally developed on by (russel5), but abandoned in favor of AospEx and Pie projects of his. Personally, I'm not a fan of the direction taken in Pie and will be sticking with Oreo. I'll be developing the rom further with features, bug fixes and enhancements. Any suggestions should be opened as an issue on the Github.
Downloads
GitHub
Installation
1. Download firmware zip
2. Download OpenGapps/MicroG/Whatever
3. Push to phone
4. Reboot to recovery (recommend TWRP) and do a full wipe
5. Flash RR then whatever else after (Gapps, ect)
6. Reboot
7. ???
8. Profit
General Info:
If you have issues with the camera being green, make sure you update your fireware to the most recent Oreo one via newflasher. I will update this with information regarding this.. It's been months since I did it so I need to remember and hunt the files down I used (which is hard since my last computer died and I switched to Linux). I'd backup your Drm keys before doing anything if you do.
Exclude when flashing:
* fotakernel.sin
* kernel.sin
* simlock.ta (if you have it)
* system.sin
* userdata.sin
* vendor.sin
Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Special thanks to:
@modpunk
@russel5
Anyone else I'm forgetting
Source:
Repo
XDA:DevDB Information
[G8441, XZ1c] [8.1] Resurrection Remix v6.2.1 (Oreo), ROM for the Sony Xperia XZ1 Compact
Contributors
hockeymikey
Source Code: https://github.com/hockeymikey/android_device_sony_lilac
ROM OS Version: 8.x Oreo
Based On: LOS
Version Information
Status: Stable
Current Stable Version: 6.2.1
Created 2020-04-19
Last Updated 2020-04-20
Click to expand...
Click to collapse
Hi, i have tested update of this rom and found out 2 system bugs.
First thing - bootloop. I flashed it like usually with newest BitGapps arm64 8.1.0 v15 and magisk. BitGapps caused bootloop. Clean install with only magisk booted, but magisk app not installed, so i had to install Magisk Manager manually, root installed.
Second boot into recovery and flash BitGapps caused no google store app, like before, so i flashed MindGapps and it works.
It is mine problem, i using alternative gapps but good to notice.
Sometimes not smooth, torn animations. More often than older build.
Red blinkings: Right after successful boot, after some clicks i see weird red blinkings on display. Something similar like in developer options turn on display blinkings after stress GPU/CPU but this happen in random time and is not turned on. Is little bit enyoying, its not happened in older 2018 build.
So my decide will be flash again .228 firmware and stay with Havoc OS, now i used version 3.8 for month and i can say, now is android 10 in lilac flawlessly done. I like more older Oreo UI but fix issue with blinking and i will be your satisfied user.
Thank you and best regards.
jurko217 said:
Hi, i have tested update of this rom and found out 2 system bugs.
First thing - bootloop. I flashed it like usually with newest BitGapps arm64 8.1.0 v15 and magisk. BitGapps caused bootloop. Clean install with only magisk booted, but magisk app not installed, so i had to install Magisk Manager manually, root installed.
Second boot into recovery and flash BitGapps caused no google store app, like before, so i flashed MindGapps and it works.
It is mine problem, i using alternative gapps but good to notice.
Sometimes not smooth, torn animations. More often than older build.
Red blinkings: Right after successful boot, after some clicks i see weird red blinkings on display. Something similar like in developer options turn on display blinkings after stress GPU/CPU but this happen in random time and is not turned on. Is little bit enyoying, its not happened in older 2018 build.
So my decide will be flash again .228 firmware and stay with Havoc OS, now i used version 3.8 for month and i can say, now is android 10 in lilac flawlessly done. I like more older Oreo UI but fix issue with blinking and i will be your satisfied user.
Thank you and best regards.
Click to expand...
Click to collapse
What's special about Bitgapps? That's really strange, can you grab a log on boot using adb? If not, go to https://github.com/hockeymikey/android_device_sony_lilac/issues and make an issue and help me track it and I'll get around to testing it. It'll help keep in touch with you and solve it especially if for some reason I can't recreate it for some reason. I got that red outline too and I thought it was just me. It went away for me so might be temporary on the initial install. If you could create an issue for that too on the previous link so I can keep you updated for that too.
jurko217 said:
Hi, i have tested update of this rom and found out 2 system bugs.
First thing - bootloop. I flashed it like usually with newest BitGapps arm64 8.1.0 v15 and magisk. BitGapps caused bootloop. Clean install with only magisk booted,......
Click to expand...
Click to collapse
So I did some testing. The red blinking is gone, that fix will be included in the next release (which includes signature spoofing and updates so a few system libraries like base, native and lineage-sdk). BitGapps doesn't cause a bootloop for me. It was kinda buggy, which is odd and crashes. I'll see what I can find for it. Magisk works fine for me. Make sure it's the most recent version but I was using old versions too as well as new so I don't know.
Hm, with usb-debugging enabled, it dont ask for permission and dont save the adb-key, so u arent able to adb into twrp. But ADB to the booted device works. Anybody else got this?
muebbel said:
Hm, with usb-debugging enabled, it dont ask for permission and dont save the adb-key, so u arent able to adb into twrp. But ADB to the booted device works. Anybody else got this?
Click to expand...
Click to collapse
That's a TWRP reason. Whoever built it disabled adb in it. I repackaged twrp to allow adb for myself, I can share it if you want.
This will be nice
And... i get this red-frame too if some higher cpu-usage happens. What did u do against it?
Encrypting the device ends in a infinity-loop at the "Encrypting... time remaining 00:00.."-Screen.
Maybe i missed something (tried with and without the boot.img for force-encryption)?
muebbel said:
This will be nice
And... i get this red-frame too if some higher cpu-usage happens. What did u do against it?
Encrypting the device ends in a infinity-loop at the "Encrypting... time remaining 00:00.."-Screen.
Maybe i missed something (tried with and without the boot.img for force-encryption)?
Click to expand...
Click to collapse
I think this is the correct one, let me know if not. Red frame is an issue I caused with how I built it, building it as a dev build not production. It's fixed on my device. I'll eventually get a new build out, I've been waiting to get OpenDelta done for OTA updates first to streamline the updating process. Maybe I should push one out sooner since the build on here I don't think is really that usable while my phone one I'm using daily. I haven't tested encryption honestly. I'll have to look into. If you could make an issue on github with every little detail to help me track and fix, that'd be cool.
Hmm, same problem -> adb devices -> unauthorized
And there is no dialog for accept/store the ADB-Key if u plugin the PC for the first time.
So.. i was using newflasher to flash the stock oreo rom and guess what... the stock rom does the same... so if u flash the stock rom (47.1.A.16.20) without remove any files from the stock-rom-directory and the adb_key still exists... where can it be?
BTW: i can access the stock-rom with adb add the first start at the "Welcome"-Screen... but twrp cant find/use the key which is stored $somewhere