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.
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
Introduction
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
Requirements
Your device need to be unlocked either officially (h815 international or h811) or by UsU
Your bootloader stack should be on MM 20p (20x for H811) or higher! (see FAQ #20 for how to upgrade your bootloader stack).
.... and for your convenience I have even created TWRP flashable files for that here
in particular that means this thread is for:
F500 (UsU'd)
H810 (UsU'd)
H811
H812 (UsU'd)
H815 (official unlocked or UsU'd)
H819 (UsU'd)
LS991 (UsU'd)
US991 (UsU'd)
VS986 (UsU'd)
Latest TWRP - PREVIEW build: click
Do a full Nandroid backup before doing anything!
Installation Instructions
This single very first step is for UsU'd devices only:
If you have ever flashed the UsU baseband package: Clean flash the modem partition from your backup in TWRP.
If you do not know if you ever flashed it simply flash your modem partition again and you can be sure. This can't do any harm.
If you have no backup:
- TWRP flashable MM modems (N might not work)
Full clean install as described here (FAQ "#2") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash LOS
Optional: Flash GApps (8.1 - ARM64 for LOS 15.1, 7.1 - ARM64 for LOS 14.1) if you like
Optional (if you want root): Flash the official LOS root-addon (addonsu-15.1-arm64-signed.zip or addonsu-14.1-arm64-signed.zip) or Magisk (do not report issues if you have Magisk installed though!)
Boot (will take a bit on first boot!!!)
Enjoy
For more detailed instructions, please see my website (thepiguy0.github.io/installing)
Update Instructions
To update from a previous version of my rom:
If it is an old version of the rom, it is recommended to do a clean flash - Be aware that your data will be deleted
If it is a relatively recent version, a dirty flash should be ok - wipe cache and dalvik cache and then flash on top of your current installation - This keeps all your files
Current Issues
For a current list of all issues including possible workarounds:
Open issues
Issues with workarounds available
Summary (again check out the above linked issue tracker for a current state):
Bluetooth calling FIXED!
Flashlight icon on quick toggles FIXED!
SIM pin unlocking (Ril works, better to use an unlocked sim card for now) FIXED!
Magisk when encrypted - state UNKNOWN
Permissive SELinux FIXED!
Probably more undiscovered bugs
Downloads
Get the latest builds from steadfasterX's server
Get the legacy builds from my Google drive
Building from source
If you want to build this from source, follow the LG H815 build guide (replace H815 with H811 if needed). Immediately before the "repo sync" step, copy our local manifest (https://github.com/Suicide-Squirrel/local_manifests/blob/los-15.1/roomservice.xml) into the .repo/local_manifests/ folder. Now run repo sync.
Then miss out breakfast and proprietary files steps before continuing with Jack memory optimisations
Changelog
Go through the results here: click
older ones click here:
20/05/2018
WiFi Hotspot is now fixed
H811 audio is fixed
More audio enhancements behind the scenes
Increased performance in Titan Kernel
28/04/2018
Audio is now fully working (with the exception of bluetooth calling)
Camera and screen recorder are now both fully fixed and work
Latest Lineage and Titan updates
FAQ
Will be added as the time goes.
Credits
@kessaras, @steadfasterX and the LineageOS team
Sources
Lineage source code - https://github.com/LineageOS/
Device trees and kernel (forked from cypheros) - https://github.com/suicide-squirrel/
Proprietary files - https://github.com/CypherOS/
PREVIOUS OP (for historical reasons)
Introduction
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
Requirements
LG G4 H815/H811
Latest MM firmware for H811 and latest Nougat/MM firmware for H815
Latest official TWRP or the latest TWRP preview from steadfasterX's server - This prevents the error 7 from appearing
For UsU devices, follow @steadfasterX's instructions for TWRP
Installation Instructions
Download appropriate zip for your device along with any additional modules such as gapps (arm64 android 8.1 needed)
Recommended - Create a full nandroid backup to allow you to restore to your previous OS if needed
Wipe system, data, cache and dalvik cache - Be aware that this WILL remove your currently installed OS and wipe your apps and most data
Flash the lineage zip, followed immediately by gapps if applicable
Reboot into system and wait for boot
For more detailed instructions, please see my website (thepiguy0.github.io/installing)
Update Instructions
To update from a previous version of my rom:
If it is an old version of the rom, it is recommended to do a clean flash - Be aware that your data will be deleted
If it is a relatively recent version, a dirty flash should be ok - wipe cache and dalvik cache and then flash on top of your current installation - This keeps all your files
Current Issues
For a current list of all issues including possible workarounds:
Open issues
Issues with workarounds available
Summary (again check out the above linked issue tracker for a current state):
Bluetooth calling
Flashlight icon on quick toggles
SIM pin unlocking (Ril works, better to use an unlocked sim card for now)
Magisk when encrypted
Permissive SELinux
Probably more undiscovered bugs
Downloads
Get the latest builds from steadfasterX's server
Get the legacy builds from my Google drive
Building from source
If you want to build this from source, follow the LG H815 build guide (replace H815 with H811 if needed). Immediately before the "repo sync" step, copy our local manifest (https://github.com/Suicide-Squirrel/local_manifests/blob/los-15.1/roomservice.xml) into the .repo/local_manifests/ folder. Now run repo sync.
Then miss out breakfast and proprietary files steps before continuing with Jack memory optimisations
Changelog
20/05/2018
WiFi Hotspot is now fixed
H811 audio is fixed
More audio enhancements behind the scenes
Increased performance in Titan Kernel
28/04/2018
Audio is now fully working (with the exception of bluetooth calling)
Camera and screen recorder are now both fully fixed and work
Latest Lineage and Titan updates
FAQ
Will be added as the time goes.
Credits
@kessaras, @steadfasterX and the LineageOS team
Sources
Lineage source code - https://github.com/LineageOS/
Device trees and kernel (forked from cypheros) - https://github.com/suicide-squirrel/
Proprietary files - https://github.com/CypherOS/
XDA:DevDB Information
LineageOS 14.1/15.1 for LG G4, ROM for the LG G4
Contributors
ThePiGuy, steadfasterX, kessaras, berkantkz and LineageOS
Source Code: https://github.com/LineageOS/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: v20 (or higher for H815) bootloader and modem
Based On: Lineage OS
Version Information
Status: Stable
Current Beta Version: 20180428
Beta Release Date: 2018-04-28
Created 2018-04-26
Last Updated 2019-12-22
Reserved
Reserved
Great work!
Need more stability to have a try but following it closely!
Thanks a lot.
Good job!
I missed Lineage OS.
Is encryption working?
YOU, @ThePiGuy, built this (with help from others)? Well done man.
Good luck and Godspeed man
zeduck said:
Good job!
I missed Lineage OS.
Is encryption working?
Click to expand...
Click to collapse
Yes it is
ThePiGuy said:
Yes it is
Click to expand...
Click to collapse
Is it trimming working with encryption ( fstrim -v /data ) without the error transport endpoint not connected?
Thanks!
talk to @codeworkx.
if your commits you added are clean and crystal clear of what you did and you kept authorship, maybe you should update the official and get some logs to them to also help you.
Minor bugs of audio and maybe some props to make the camera function correctly are not hard bugs. Me i do not have the time sorry. I do not even have the time with AOSCP now that im working so much :/
Great job keeping LOS on this device. I'm holding on to it as I still find it fast and useful.
While there is a lens on the audio configuration it would be awesome to see this phone enabled for hires audio (up to 24bit / 192KHz) under LOS. I know people are skeptical of the difference but DAC is able to do this and it should simply be an edit of the relevant audio_policy_configuration.xml(?) file to enable the extra sound profiles above 16/48.
hteles said:
Is it trimming working with encryption ( fstrim -v /data ) without the error transport endpoint not connected?
Thanks!
Click to expand...
Click to collapse
I have no idea (give it a go if you want )
belrik said:
Great job keeping LOS on this device. I'm holding on to it as I still find it fast and useful.
While there is a lens on the audio configuration it would be awesome to see this phone enabled for hires audio (up to 24bit / 192KHz) under LOS. I know people are skeptical of the difference but DAC is able to do this and it should simply be an edit of the relevant audio_policy_configuration.xml(?) file to enable the extra sound profiles above 16/48.
Click to expand...
Click to collapse
First things first, got to get the audio working in the first place . And also, nobody seems to have seen the error that it kicks out in the logcat, so it might take a while to get it working - I'll try porting the cm-14.1 trees to lineage-15.1 rather than porting oreo cypheros trees to see if that makes a difference
@ThePiGuy what are the known bugs for this rom?
NummerEinsNerd said:
@ThePiGuy what are the known bugs for this rom?
Click to expand...
Click to collapse
All in the title post above (under Current Issues). Basically audio is fully broken (so this is purely testing at the moment - not suitable for a daily driver), camera is broken along with the lineage voice and screen recorder crashing.
ThePiGuy said:
All in the title post above (under Current Issues). Basically audio is fully broken (so this is purely testing at the moment - not suitable for a daily driver), camera is broken along with the lineage voice and screen recorder crashing.
Click to expand...
Click to collapse
All camera apps ? Even Google s ?
If Google's work, then it's just a prop.
Also yes that's normal since Los uses snap and maybe it needs different props , it may needs a couple different things to call for build and some overlay settings in a config.
The other Los developers should already know how to make this work since they have ported many phones.
Me I never developed in los, I don't know.
kessaras said:
All camera apps ? Even Google s ?
If Google's work, then it's just a prop.
Also yes that's normal since Los uses snap and maybe it needs different props , it may needs a couple different things to call for build and some overlay settings in a config.
The other Los developers should already know how to make this work since they have ported many phones.
Me I never developed in los, I don't know.
Click to expand...
Click to collapse
I haven't tested any others yet. I'm mainly focusing on the audio at the moment
Great job bringing LOS back to life for the G4!
Thanks for your effort! I will monitor this Thread closely and hope you soon find the audio issues
Hi,
Even though I'm not quite experienced, I'd like to join the development of this rom. Right after installing it on my device and reading the logcat, I've partially fixed the audio problem. I've also created a pull request and given enough information on GitHub repository.
Edit: Full message from GitHub
These missing files which had to be under "/system/vendor/etc" folder lead to crashes on the apps which use sound. By placing them to where they have to be, crashes on music player when trying to play any music and video recording are fixed. Although there has been no sound yet, these changes are required in order to prevent crashes.
Also, there may be another way in order to fix crashes instead of doing these changes. It is to edit the paths to "/system/etc/" as the files are already placed there.
I guess the lines for "/system/etc" can be removed as well but I am not sure if there are any system part that uses this directory. It's better to let them stay under "/system/etc" as well.
Additional message:
These changes also fixed handset and earphones. The handset is working on calls and earphones work on video/music now. However, the speaker still doesn't work. Video recording works as well as the built-in microphone does.
Additional message 2:
From now on, neither audio nor screen recorder crash. Both work well.
Click to expand...
Click to collapse
berkantkz said:
Hi,
Even though I'm not quite experienced, I'd like to join development of this rom. Right after installing it on my device and reading the logcat, I've partially fixed the audio problem. I've also created a pull request and given enough information on GitHub repository.
Click to expand...
Click to collapse
Brilliant!!! Thanks Don't worry about not being experienced - this is my first proper project at getting a rom going, so I'm learning as well
New H815 build out (20180428) with fixed audio, camera and screen/audio recorder. This has given rise to the fact that BT calling is indeed broken like it is on AOSCP
H811 build coming out soon.
Massive thanks to @berkantkz, without whom I wouldn't have been able to do it
Edit: H811 build is up as well now
The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!
Official site
Unofficial site
Code:
#include <std_disclaimer.h>
/*
*
* 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.
*
*/
This is the LineageOS ROM for the Sony Xperia XZ2 (akari), XZ2C (apollo) and XZ3 (akatsuki)
This ROM build will always mainly based on Code from Sony AOSP & LineageOS and maybe include cherry-picks.
I plan to make monthly builds, after a new security patch level, if there is no need for a critical hotfix.
FAQ:
Switch the A/B slot for every monthly release to make sure you execute the same amount of write cycles on the entire flash storage. (Extends hardware lifetime)
fastboot & adb
https://developer.sony.com/develop/open-devices/get-started/flash-tool/useful-key-combinations/
https://wiki.lineageos.org/adb_fastboot_guide.html
https://developer.android.com/studio/releases/platform-tools
Stuck at SONY logo? Maybe you need to flash the OEM binary to oem_a and oem_b, while just oem is not enough.
For a complete security patch you have to install the newest stock firmware and boot it once.
https://github.com/sonyxperiadev/bug_tracker/issues/258#issuecomment-445816826
TL;DR Flash the latest stockfirmware, boot it once, to update your baseband/mobile network drivers and then flash this ROM.
(I prefer and support only newflasher from XDA and xperifirm to download the firmware.)
Maybe this helps windows users:
https://developer.sony.com/posts/flash-tool-updated-with-new-feature/
jerpelea said:
for a complete security patch you have to
1. flash the stock firmware using https://developer.sony.com/develop/open-devices/get-started/flash-tool/
2. build and flash the ROM
* The security patch may affect or not the proprietary parts depending on HW and implementation
* After official support ends you can still get security updates for kernel and Android but loader and firmware will be stuck to the latest official release
Click to expand...
Click to collapse
Bugtracker:
SODP Bugtracker -> If you think the problem is in SODP
LineageOS Bugtracker -> If you think the problem is in LineageOS
My Bugtracker -> If you think the problem is in my implementation
Bugreport:
A bugreport needs
Code:
logcat -b all
and a way to reproduce the issue.
A crash of the system requires the content of the /sys/fs/pstore folder as bug report
Be aware that a second reboot erases this folder
A crash to the recovery partition requires additionally the content of the /dev/block/by-name/misc partition
You get the content via `cat /dev/block/by-name/misc partition > /path/to/output/file.txt`
To rescue a not responding phone:
VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.
Thank you very much for your help, code contribution & testing! (Random order):
@jerpelea, the sony employees and their volunteers (people like you and me) coding this wonderful piece of software
@dhacke for providing a download server
@Raphos for the initial installation manual without a recovery system, after I switched to OTA zips.
@kgvarunkanth for the jenkins build server
And many thanks to the few donators!
A telegram group for technical SODP stuff:
Sony [*Kim Jong*Un]official OD Chat
https://developer.sony.com/develop/open-devices OEM binaries: @SMDW_downloads Bug Tracker: https://github.com/sonyxperiadev/bug_tracker This group is only for dev stuff. For support: https://t.me/xdadevelopershub
t.me
XDA:DevDB Information
LineageOS, ROM for the Xperia XZ2
Contributors
MartinX3, SODP Team
Source Code: https://github.com/MartinX3-AndroidDevelopment-LineageOS/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Stock Firmware
Based On: LineageOS
Version Information
Status: No Longer Updated
Current Stable Version: 17.1
Created 2020-02-02
Last Updated 2020-10-23
Download & Installation
Download ROM:
Android File Host
FTP-Server from @dhacke
Download Drivers:
OEM (Tama) binaries
Please use the the OEM build which came before my last release, unless otherwise written.
GCAM Camera App:
Suggested GCams But GCAM's aren't usable at the moment until a camera hardware resource budget bug got fixed in the OEM binary blob.
Installation with a recovery:
fastboot flash oem_a oem_*.img
fastboot flash oem_b oem_*.img
Flash the ROM in a recovery
Reboot into recovery just to make sure you're on the new slot
Google Apps like Playstore
Dual Sim Patcher
(In case a modification prevents your device from booting) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Flash the ROM without a recovery:
Extract the payload.bin from the .zip file
Extract the .img files with the Playload Dumper
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot -w (Wipes your internal storage and the userdata)
Continue with the normal installation
News
24.08.2020
since we have now an official lineageos based on stock, this rom would be double work.
So i stop the los port.
(sadly unless a dev owns a xz2p or xz3 these phones won't be supported in the official stock based lineageos)
the only difference between the stock and sodp editions are:
Sodp will get gcam support later and has camera2api level 3.
Stock will never support gcam apps and has the limited stock camera2api level.
Sodp uses a 4.14 kernel and probably get mainline support later.
Stock uses the stock 4.9 kernel and will probably be there forever.
Sodp targets to use as much open source as possible.
And livedisplay doesn't work in my sodp version.
Ps: After the september exams in the new semester i look for a rom replacement for the sake of diversity.
It's good to have a choice and with the available official supported sodp based pixel experiment, we have a rom which sadly forces you to use the full gapps (google apps package).
Click to expand...
Click to collapse
13.07.2020
july security patch level
oemv9c support
and any other sodp open source changes since my last build
Click to expand...
Click to collapse
18.06.2020
june security patch level
oemv8 support
and any other sodp open source changes since my last build
fixes for charger, battery, sleep (sideeffect working bluetooth audio) and more!
Click to expand...
Click to collapse
11.05.2020
may security patch level
oemv6 support
and any other sodp open source change since my last build
ps: Camera is work in progress.
Please flash gapps and the dual sim patcher again after applying an ota update.
It seems that the ota zip replaces every partition and deletes the modifications (like gapps).
Also it enforces avb heavily which prevents modifications like gapps from getting loaded.
So i deactivated avb now.
(but since the device bootloader can't be relocked the avb is not really useful anyway)
Click to expand...
Click to collapse
14.04.2020
now android 10.0.0_r33
april security patch level
oemv5 support
and any other sodp open source change since my last build
switched to:
zip files to flash
dual sim patcher instead of dual sim rom files
removed buildin gapps, since you can flash it now via twrp
installing this rom as an update won't remove the installed gapps.
ps: Camera is work in progress.
Click to expand...
Click to collapse
09.03.2020
march 2020 security update
oemv4 -> camera & other improvements
and any other lineageos / sodp open source changes since my last build
ps: Camera is work in progress.
Ps0:
Other than the aosp release, this lineageos got the new ril by qcom enabled for mobile network access.
Please test and report bugs. (dmesg & logcat, -> and pstore if the device crashes)
it will get activated in the next aosp release as well, if it makes no trouble.
Click to expand...
Click to collapse
01.03.2020
oemv4 is needed or device won't boot.
Oemv4 is not backward compatible with older releases.
oemv4 -> camera & other improvements
and any other lineageos / sodp open source changes since my last build
ps: Camera is work in progress.
Ps0:
Other than the aosp release, this lineageos got the new ril by qcom enabled for mobile network access.
Please test and report bugs. (dmesg & logcat, -> and pstore if the device crashes)
it will activated in the next aosp release as well, if it makes no trouble.
Click to expand...
Click to collapse
29.02.2020
added support for every sodp supported xperia https://github.com/martinx3-androiddevelopment-lineageos/
(except the loire and tone platform which no one requested.)
the oemv4 rom release will delay a bit.
Was in the need to delete my build cache for aosp and lineageos.
Click to expand...
Click to collapse
25.02.2020
need to take down the builds.
Oemv4 which comes tomorrow got some additional last minute changes today which needs a new rom compilation.
Click to expand...
Click to collapse
24.02.2020
oemv4 is needed or device won't boot.
Oemv4 is not backward compatible with older releases.
oemv4 -> camera & volte & other improvements
and an other lineageos / sodp open source changes since my last build
ps: Camera is work in progress.
Oemv4 maybe comes tomorrow.
Click to expand...
Click to collapse
15.02.2020
feburary security patch level
fixed bugs, now my sony aosp release and this lineageos port should contain the same amount of bugs (aside from the stuff on the lineageos part).
Switched from alpha to beta version.
The only instability i found on my own xz2 is a crash at night in flightmode without charger.
Anything else doesn't crash it here.
Might be various reasons.
If anyone has the same bug, please provide logs in my github issue tracker.
(and please look if your logs contain more informations than my logs).
Click to expand...
Click to collapse
02.02.2020
the first lineageos 17.1 build based on the sodp device trees.
My vanilla sodp release and lineageos should share the same bugs.
Plus bugs / missing features in lineageos and bugs introduced by myself porting sodp to lineageos :silly:
sadly i can't upload it at the moment to android file host.
Their new "stackpath" ddos blocking solution banned me, because i tried to upload the rom in 6 browser tabs. :silly:
fixed
have fun!
Ps: Camera is work in progress.
Twrp 10 is not ready, so i sadly can't start develop one for the xz2, xz2c, xz3.
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
that's the reason i include opengapps pico for now.
And to use magisk, simply patch the boot.img by yourself in the magik manager app and flash it via fastboot.
Maybe you need to deactivate vbmeta, which wasn't the case at my site.
Gcam doesn't work with oemv3.
There is a library missing.
Click to expand...
Click to collapse
02.02.2020
The first LineageOS 17.1 build based on the SODP device trees.
My vanilla SODP release and LineageOS should share the same bugs.
Plus bugs / missing features in LineageOS and bugs introduced by myself porting SODP to LineageOS :silly:
Sadly I can't upload it at the moment to Android File Host.
Their new "Stackpath" DDOS blocking solution banned me, because I tried to upload the ROM in 6 browser tabs. :silly:
Fixed
Have Fun!
PS: Camera is work in progress.
TWRP 10 is not ready, so I sadly can't start develop one for the XZ2, XZ2C, XZ3.
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
That's the reason I include OpenGapps Pico for now.
And to use Magisk, simply patch the boot.img by yourself in the magik manager app and flash it via fastboot.
Maybe you need to deactivate vbmeta, which wasn't the case at my site.
GCAM doesn't work with OEMv3.
There is a library missing.
Click to expand...
Click to collapse
Nice work Martin!!!
I had looked forward to be released this rom
And i have a question to you.
Does this rom support VoLTE?
Orihamburger said:
Nice work Martin!!!
I had looked forward to be released this rom
And i have a question to you.
Does this rom support VoLTE?
Click to expand...
Click to collapse
Thank you
Yes, at least I can use VoLTE in my country with my provider.
You need to test it by yourself. [emoji14]
I need some help from testers for logs and observed behavior.
It seems that the phone crashes while sleeping in combination with the installed firmware on my XZ2.
Does this crash only happen when someone upgraded his phone to stock 10.0 first or does it also happen with a previously installed stock 9.0 rom?
https://github.com/MartinX3-AndroidDevelopment-LineageOS/bug_tracker/issues/1
MartinX3 said:
I need some help from testers for logs and observed behavior.
It seems that the phone crashes while sleeping in combination with the installed firmware on my XZ2.
Click to expand...
Click to collapse
I had the same on PE.
PE rom flashed over latest stock firmware, then latest aosp oem binary.
And always when I Iock phone for some time, impossible to wake up it. Only restart helps using volup+power.
P.S. now i'm on stock.
zhka said:
I had the same on PE.
PE rom flashed over latest stock firmware, then latest aosp oem binary.
And always when I Iock phone for some time, impossible to wake up it. Only restart helps using volup+power.
P.S. now i'm on stock.
Click to expand...
Click to collapse
Thank you
I'm curious if it is the same issue.
hi martin, thanks a lot for your work, a question, in this version the general stability of this rom is the same of your sonyaosp project? i will try today or tomorrow
nikkdib said:
hi martin, thanks a lot for your work, a question, in this version the general stability of this rom is the same of your sonyaosp project? i will try today or tomorrow
Click to expand...
Click to collapse
Thank you, you're welcome
In theory it only contains bugs from SODP and LineageOS :silly:
MartinX3 said:
Thank you, you're welcome
In theory it only contains bugs from SODP and LineageOS :silly:
Click to expand...
Click to collapse
ok i try to flash. now i have stock bugged android 10 firmware
edit: ok i flashed this rom and for now my phone seems doesn't crashed or freeze. i try to install gcam but gcam crash
nikkdib said:
ok i try to flash. now i have stock bugged android 10 firmware
edit: ok i flashed this rom and for now my phone seems doesn't crashed or freeze. i try to install gcam but gcam crash
Click to expand...
Click to collapse
Gcam should work with OEMv4
There is a library missing to run this application.
The XZ3 Dual file is corrupted. It is only 50MB in size
nickholtus said:
The XZ3 Dual file is corrupted. It is only 50MB in size
Click to expand...
Click to collapse
Thank you, but the dual sim version only contains the files different from the single sim version.
MartinX3 said:
Thank you, but the dual sim version only contains the files different from the single sim version.
Click to expand...
Click to collapse
Ahhh damnn, sorry my fault! Stupid mistake
Very promising release=) However, I need your help, Bro, cause I'm officially stuck with the stock=))) Before I used your OMNI for 6 months and it was completely fine just the camera wasn't working at all regardless of any fixes I've tried! After that, I switched my H8266 xz2 Dual to your SODP to try Android 10, which I didn't like after playing with it for a while. And now - I flashed latest 52.0.A.8.131 or newer 52.1.A.0.532 for the US device - I COULDN'T find the correct twrp as well as I CAN'T install OMNIrom. I have a simple question ==> besides the stock, which rom is stable enough here to have a working camera and TWRP. From what I see, almost each rom has some issues. Instead of Lineage 17, could you fix the links for working 16th version? FIX me if I'm wrong=)))
Mazurik said:
Very promising release=) However, I need your help, Bro, cause I'm officially stuck with the stock=))) Before I used your OMNI for 6 months and it was completely fine just the camera wasn't working at all regardless of any fixes I've tried! After that, I switched my H8266 xz2 Dual to your SODP to try Android 10, which I didn't like after playing with it for a while. And now - I flashed latest 52.0.A.8.131 or newer 52.1.A.0.532 for the US device - I COULDN'T find the correct twrp as well as I CAN'T install OMNIrom. I have a simple question ==> besides the stock, which rom is stable enough here to have a working camera and TWRP. From what I see, almost each rom has some issues. Instead of Lineage 17, could you fix the links for working 16th version? FIX me if I'm wrong=)))
Click to expand...
Click to collapse
Thank you
At the moment the source code of TWRP 10.0 is not available/usable, but is needed to create a TWRP with the 10.0 code environment.
Why you can't install omnirom?
The TWRP only work for the 9.0 ROMs at the moment and will be fixed in the future.
The LineageOS 16.0 release wasn't made by me and I can't do anything (except creating my own LineageOS 16.0 but my time/ressources are sadly limited :silly
does anyone know how well gcam works compared to stock camera on locked device?
tb_ said:
does anyone know how well gcam works compared to stock camera on locked device?
Click to expand...
Click to collapse
The camera driver is work in progress
The gcam workarounded missing features on 9.0.
Now on 10.0 we need to wait for OEMv4 for a working gcam.
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
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS Modded is a free, community built, aftermarket firmware distribution of Android 11 (R), which is designed to increase performance and reliability over stock Android for your device.
LineageOS Modded is based on the Android Open Source Project and LineageOS with extra contributions from many people within the Android community.
All the source code for LineageOS Modded is available in the LineageOS Modded Github repo.
What's working?
Stuff
What's not working?
Enforcing
Other stuff
Installation
1. Boot into twrp
2. Advanced -> ADB Sideload -> Swipe
5. adb sideload lineage.zip
6. Wipe Data
7. Profit?
Downloads: https://1pwn.ixmoe.com/android/surfna/Lineage18.1-Mod/
Notes
This ROM comes with Google Apps!
This ROM comes with Customizations that are not apart of LineageOS
Source: https://github.com/electimon/VoidKramel/tree/Void-moto-4.9-redo
Credits: @electimon, @erfanoabdi, @SyberHexen
Updated: 06/20/2021
June Patch and userdebug
I have the T-Mobile version of this phone, with the a ramdisk-enabled Magisk-patched boot image, and working touch recovery.
I tried this lineage 18 rom, and ended up in a boot loop. I noticed that your lineage 18 treble version includes new vendor and boot images. This was not clear in the instructions.
Recently, I successfully installed a phh-aosp 11 gsi system image only on this phone with no issues. I had to disable superuser after booting up the first time, because magisk is installed in the boot image, but otherwise no problems. No need for new vendor or boot images. Hope this info helps. Thanks for all of your work on the Moto E6.
There is a need for the new boot and vendor images because this is a 64BIT ROM not a 32BIT ROM like stock and the GSIs, and why do you tell me this without providing any kinds of logs. Also this is NOT A GSI, it is a source built ROM, thanks.
Thanks for clarifying. I wll try again and have some logs.
Update: I tried to install both roms. Rom v2 boot looped. Rom v1 stayed on G symbol. I waited 20 minutes on that one, but no change. I did install magisk.zip both times. Perhaps that is the problem. I don't know how to save logs prior to actually booting the rom. Thanks.
Update 2: No difference with or without magisk installed into boot image.
Just for the record, I installed this and I've booted into the OS. Now I want to see if I can get microG on here.
@Electimon I'm pretty sure I can't install microG because Gapps leaves no space for microG to be installed, and the OrangeFox recovery isn't mounting system so I can't resize it. Can you make a LineageOS version without gapps installed, or can uninstalling Gapps suffice?
Another update: While I could never get LineageOS and microG to work, one stunning thing that I discovered is that if you install this ROM, you can now use arm64 A/B GSI ROMs. This opens up the possibilities immensely as I reckon arm64 a/b GSIs will be around way longer than anything else.
Absence of com.android.documentsui means that when you are trying to choose folders for an application, there is no application available to do so. This results in crashes when you are trying to do something such as giving external SD card support to an application.
Had to go back to 32 bit because using power button seems to force restart on my phone. I'm sure I'm the only one with this issue
@Electimon will it work on E6 Play too?
do u plan to rls it without gapps (I can install some of my choosing later, right)?
@koyo @scottyrick2 managed to run it?
if not what other solution did u come up with/rom (maybe stock+micro?)
Also do i need those too & why? https://forum.xda-developers.com/t/recovery-unofficial-orangefox-r11-x-64bit-f2fs.4293397/ & https://forum.xda-developers.com/t/e6-aio-toolkit-mod-release.4122643/ & https://forum.xda-developers.com/t/experimental-twrp-dirty-port-for-moto-e6.3976715/
The post says moto e6 only.
Electimon said:
The post says moto e6 only.
Click to expand...
Click to collapse
Could You fix one for Play too?
My country only sell those ;( Thanks
kamolinkaaa said:
@Electimon will it work on E6 Play too?
do u plan to rls it without gapps (I can install some of my choosing later, right)?
@koyo @scottyrick2 managed to run it?
if not what other solution did u come up with/rom (maybe stock+micro?)
Also do i need those too & why? https://forum.xda-developers.com/t/recovery-unofficial-orangefox-r11-x-64bit-f2fs.4293397/ & https://forum.xda-developers.com/t/e6-aio-toolkit-mod-release.4122643/ & https://forum.xda-developers.com/t/experimental-twrp-dirty-port-for-moto-e6.3976715/
Click to expand...
Click to collapse
No I didn't. I'm in the process of selling the phone because it wouldn't work. Got a Moto G Fast instead for the same price
kamolinkaaa said:
Could You fix one for Play too?
My country only sell those ;( Thanks
Click to expand...
Click to collapse
I don't have the device
koyo said:
No I didn't. I'm in the process of selling the phone because it wouldn't work. Got a Moto G Fast instead for the same price
Click to expand...
Click to collapse
Oh u so lucky, can't get Moto G Fast here...so am gonna buy E5 Plus
Electimon said:
I don't have the device
Click to expand...
Click to collapse
Is there an option to buy E6 in Your area and send to me (& hm root it w Your rom), please?
Or maybe I can warp E6 Play to You and u could create a rom for it too hmm
Discontinued, los-modded 12 is coming soon
No one wants this phone so I'm stuck with it. Hopefully LOS 12 will fix the problems with LOS 11
thank you @Electimon for building this ROM! i have successfully flashed it to a Visible Moto E6 and works just fine for my needs. I used OrangeFox recovery to get to this stage. Flashed Magisk v23.0 afterwards and that works just fine as well.
just wondering, was there a specific reason you went with Google GO apps instead?
keep up the good work and look forward to Android 12 LOS ROM. reset my XDA password and logged on just to express my appericiation and grattidue for your work. thanks again.
desidude2000 said:
thank you @Electimon for building this ROM! i have successfully flashed it to a Visible Moto E6 and works just fine for my needs. I used OrangeFox recovery to get to this stage. Flashed Magisk v23.0 afterwards and that works just fine as well.
just wondering, was there a specific reason you went with Google GO apps instead?
keep up the good work and look forward to Android 12 LOS ROM. reset my XDA password and logged on just to express my appericiation and grattidue for your work. thanks again.
Click to expand...
Click to collapse
I went with GO GApps because surfna is limited in RAM, it would not be good with full gapps, no RAM left for system. Thank you for using my work!!