Stock Android 8.0.0 Oreo ROM
for Moto E5 Play (James) XT1921-5
TWRP Flashable Installer
DISCLAIMER:
By proceeding further, you are assuming full responsibility for any negative consequences which may result from flashing this ROM. While I have fully tested this ROM on my own device with no adverse issues, I will not be held liable for bricked or otherwise inoperable devices resulting from the installation of this ROM. You -- and you alone -- are solely responsible for your device. With that having been said, I will provide as much support as possible in the event of such a catastrophe. Please read this thread fully, and follow the instructions precisely, and you should incur no negative consequences.
SPECIFICATIONS:
Compatibility: XT1921-5 Moto E5 Play (James)
Android Version: 8.0.0 (Oreo)
Kernel Version: 3.18.71-perf-gb4140c9
Baseband Version: M8920_11.54.11.41R
Build No. OCPS27.91-23-3
Android Security Patch Level: June 1, 2018
Android SDK: 26
Build Date: June 7, 2018 (Original Stock Build)
Carrier Variant: Sprint, Boost Mobile, Virgin Mobile
NOTE: This ROM is mostly pure stock. I have zipaligned all APK files in /system/framework and in /system/app to optimize RAM efficiency. Also, dm-verity has been disabled in the stock kernel. It should also be noted that the ROM installer does not flash sensitive bootloader partitions, the partition index (gpt.bin), or radio firmware partitions. Hence, it is completely safe to downgrade after flashing this ROM. Likewise, if you have not updated your firmware to the latest version via OTA, this ROM should still function normally.
REQUIREMENTS:
1. Unlocked Bootloader;
2. TWRP Installed;
3. Decrypted Device Recommended (It is not yet confirmed whether this ROM will install and function on an encrypted device. In theory, and because this ROM is mostly stock, installation on an encrypted device should work so long as the /userdata partition is properly formatted. If your device is encrypted, you are flashing at your own risk. Keep in mind that by decrypting your device, you may later opt to manually encrypt your userdata by going to device SETTINGS>SECURITY & LOCATION>ENCRYPTION & CREDENTIALS and following the on-screen prompts and instructions. It is recommended to have a fully charged battery prior to encrypting your userdata. The process can take an hour or more, depending on the amount of userdata to be encrypted.
THANKS & MENTIONS:
@CodyF86 for his TWRP build, kernel patches, and /vendor fstab patches;
@SuperR. for his Windows version Kitchen;
@squid2 for his TWRP builds;
@CurbThePain for providing needed partition dumps;
@topjohnwu for his revolutionary Magisk Systemless Root Interface.
KERNEL SOURCE CODE:
Moto E5 Play (James)
MSM8920 Kernel Source Code: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-OCP27.91-23
INSTALLATION INSTRUCTIONS:
1. Download the ROM zip from the download link below and store it to external device storage. (Because the /userdata partition needs to be formatted prior to installation, saving the ROM zip to internal storage is not feasible.);
2. Boot your device into TWRP Recovery Mode;
3. MAKE A FULL NANDROID BACKUP (/system, /boot and, optionally, /data);
4. Wipe /system, /cache, and the Dalvik/ART cache;
5. Select Wipe>Format Data and follow prompts to format /data;
6. Reboot Recovery (this step is sometimes necessary to ensure proper mounting of partitions after formatting /data);
7. Select Install, navigate to the saved location of the ROM zip in external storage, select the file, and commence installation;
8. Reboot System.
Note: If you want root, flash the latest Magisk Beta version after completing Step 7 above. https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 To learn more about Magisk, visit the main Magisk stable release/announcement thread here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 Be sure to hit Thanks on @topjohnwu's threads.
BUGS:
Please let me know...
DOWNLOAD LINK:
Stock Android 8.0.0 Oreo ROM
Build No. OCPS27.91-23-3 https://drive.google.com/file/d/1j_OjzxxiqeJL4Lx7qE5tbQvj5IxbzQCd/view?usp=drivesdk
****Previous Build(s)****
Build No. OCP27.91-23
https://drive.google.com/file/d/1N69FIg-n6LOPHuXSsYZRvgyuMa67UFXl/view?usp=sharing
Can you include vendor partition in the zip or separate as img?
althafvly said:
Can you include vendor partition in the zip or separate as img?
Click to expand...
Click to collapse
Hey @althafvly, here is a dump of my vendor.img, which has force encryption disabled per the fstab file.
https://drive.google.com/file/d/1l56u4x5VHAJD8ZhnMhVo0ts7V1-NHHdI/view?usp=drivesdk
What are you thinking? Perhaps including the vendor.img in the ROM.zip to disable encryption? I am going to try implementing @CodyF86's modded fstab.qcom into the ROM for installation to /vendor/etc, to see if force encryption gets disabled after installation. Of course, I'll need to include a format command for /userdata as well.
MotoJunkie01 said:
Hey @althafvly, here is a dump of my vendor.img, which has force encryption disabled per the fstab file.
https://drive.google.com/file/d/1l56u4x5VHAJD8ZhnMhVo0ts7V1-NHHdI/view?usp=drivesdk
What are you thinking? Perhaps including the vendor.img in the ROM.zip to disable encryption? I am going to try implementing @CodyF86's modded fstab.qcom into the ROM for installation to /vendor/etc, to see if force encryption gets disabled after installation. Of course, I'll need to include a format command for /userdata as well.
Click to expand...
Click to collapse
You'll have to make the ROM install script, first mount /vendor then copy the vendor image or at least fstab to it, then install the ROM. People will still have to format /data to go unencrypted, but should still be able to use your ROM with an encrypted /data, so it's really if the person wants to do it or not, but you could write the script to push the fstab tho.
mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor
cp fstab.qcom /vendor/etc/fstab.qcom
then optionally format /data
Got it. Thanks @CodyF86 for the command lines and info. I'll try to add an Edify script into the installer. Also, because formatting /useedata will be required, I will go ahead and add a format command for the data partition into my installer as well. I will, of course, add credit to the OP for using your modded files.
Can I Flash This On My Moto E4 sprint xt1766 ? silly question but asking is free :> maybe just the system partition jejeje
ozmage said:
Can I Flash This On My Moto E4 sprint xt1766 ? silly question but asking is free :> maybe just the system partition jejeje
Click to expand...
Click to collapse
It would not be advised to do so. This stock ROM is for the Sprint variant of the Moto E5 Play only, and would certainly not be compatible on the xt1766 Sperry. This ROM would first need to be ported to the xt1766.
I'm in the process of updating the thread to reflect the recent OTA update - Android 8.0.0, Build Number OCPS27.91-23-3, Blur_Version 27.11.26.en.US.sprint. This OTA includes standard bug fixes, stability improvements, baseband radio patches for smoother data roaming handover, and Google security patches through June 1, 2018. With fingers crossed, it is looking as if this budget device will receive its fair share of OTA updates. The Motorola Mobility LLC software development manifest currently reflects that regular OTAs will be rolled out for the Moto E5 Play.
Beta release of LineageOS 15.1 is out for the James.
https://forum.xda-developers.com/moto-e5/development/rom-unofficial-lineage-os-15-1-moto-e5-t3818732
Gentlemen, ladies, and others (one must stay politically correct these days), for those of you needing factory firmware for the Moto E5 Play (James), the Development Gods have smiled upon us. Motorola Mobility has inadvertently leaked official firmware packages for ours and a few other variants. Being the watchdog that I am, I was able to capture a few packages before they were removed from the carrier manifest server. I'll be posting a stock firmware and restoration thread for the James before the weekend is up. Sure wish there was more enthusiasm for James development, but it doesn't seem so thus far. Maybe the device will catch on some more.
Question
MotoJunkie01 said:
Gentlemen, ladies, and others (one must stay politically correct these days), for those of you needing factory firmware for the Moto E5 Play (James), the Development Gods have smiled upon us. Motorola Mobility has inadvertently leaked official firmware packages for ours and a few other variants. Being the watchdog that I am, I was able to capture a few packages before they were removed from the carrier manifest server. I'll be posting a stock firmware and restoration thread for the James before the weekend is up. Sure wish there was more enthusiasm for James development, but it doesn't seem so thus far. Maybe the device will catch on some more.
Click to expand...
Click to collapse
Is the Cricket Wireless Moto e5 cruise a James variant?
adepew said:
Is the Cricket Wireless Moto e5 cruise a James variant?
Click to expand...
Click to collapse
I don't think so, but don't quote me on that. I honestly hadn't realized how many variants of the Moto E5 existed until I started researching them. Give me your model number and I'll see what I can find for you. I have packages for the xt1921-5 Sprint variant Moto E5 Play, the xt1944-1 Moto E5 LTE, a couple packages for the Moto E5 Plus, etc. But, because I'm traveling at the moment I have not had a chance to sort through everything that got leaked.
Update: my friend you do have a James. If your model number is xt1921-2 you are in luck. I have official Cricket firmware.
Thread updated to latest Build No. OCPS27.91-23-3, Security Patch Level: June 1, 2018. See Download Link in OP.
Stock Android 8.0.0 Oreo ROM
Build No. OCPS27.91-23-3
Click to expand...
Click to collapse
I am happy to report this runs on the XT 1921-1 with Freedom Mobile (Canada) branding I bought recently. Flashed with TWRP.
There is one bug. The camera app and torch function no longer work if I allow the Play Store to update "Camera Tuner for Moto E5 Play" from the version in the stock reflash.
exasperation said:
I am happy to report this runs on the XT 1921-1 with Freedom Mobile (Canada) branding I bought recently. Flashed with TWRP.
There is one bug. The camera app and torch function no longer work if I allow the Play Store to update "Camera Tuner for Moto E5 Play" from the version in the stock reflash.
Click to expand...
Click to collapse
Good info to know. I'm cooking a stock Android 8.0.0 ROM (current build) for the xt1921-1 and, since I do not own this variant, I'll need testers before I can post it to a thread. Other than disabling dm-verity in the stock kernel, I'll be leaving it untouched. Users who want root can simply flash the latest Magisk systemless root installer following the ROM installation.
Finding some helpful solution.
My aunt from US (Based in hawaii) just bought Motorola E5 Plus but I have a problem, my phone does'nt read any sim here in the Philippines. If I install your stock rom I can use any sim using this phone?
Your answer will be more appreciated. Thank you.
RandomNubGuyInPhilippine said:
My aunt from US (Based in hawaii) just bought Motorola E5 Plus but I have a problem, my phone does'nt read any sim here in the Philippines. If I install your stock rom I can use any sim using this phone?
Your answer will be more appreciated. Thank you.
Click to expand...
Click to collapse
My ROM is intended only for the Moto E5 Play (xt1921-5) variant, which is the Sprint compatible model. Nevertheless, the ROM does not enable any special carrier capabilities. In your case, go to device Settings>>System Update and select the UICC Unlock option. This should unlock your device to work with international GSM providers.
MotoJunkie01 said:
Good info to know. I'm cooking a stock Android 8.0.0 ROM (current build) for the xt1921-1 and, since I do not own this variant, I'll need testers before I can post it to a thread.
Click to expand...
Click to collapse
Will be happy to test.
exasperation said:
Will be happy to test.
Click to expand...
Click to collapse
Cool. I have a ROM ready. I'll upload and post today.
Moto E5 Play (XT1921-1)
Stock Android 8.0.0
Build No. OPP27.98
This is an untouched, pure stock ROM for the xt1921-1 Moto E5 Play. For best results it is recommended to save this ROM to external storage, boot into TWRP recovery, perform a full wipe and format /useedata prior to installing. Because I do not own the xt1921-1, I'll need testers to confirm functionality. However, I can confirm that the ROM works on my xt1921-5 Boost Mobile variant with no negative consequences or bugs.
Link: https://drive.google.com/file/d/1Ra-uOsMnaZBRc8g31bRH6W4Wtb9XPdoi/view?usp=drivesdk
Give this a try @exasperation and let me know how it goes. Thanks. Once functionality is confirmed on the xt1921-1, I'll put this ROM in its own thread.
Related
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
This firmware was developed for the p905. It doesn't apply to the p905v at this time because it's bootloader locked and a custom recovery isn't possible.
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using nano gapps.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Links
2: 20180118: remove Magisk, back su: https://drive.google.com/file/d/11V0Hmu9Jjib-oLERLXPNXbMMAie_iORq/view?usp=sharing
1: 20171231: https://drive.google.com/file/d/1m7t_7gntp9cDRRxGnJJqnwufnJxFVKUZ/view?usp=sharing
Gapps
http://opengapps.org/
Platform: ARM
Android: 7.1
Recovery
Official TWRP: http://forum.xda-developers.com/showthread.php?t=2706982
Sources
Sources: https://github.com/ResurrectionRemix/
Device: https://github.com/Valera1978/android_device_samsung_viennalte
Kernel: https://github.com/Valera1978/android_kernel_samsung_viennalte
Vendor: https://github.com/Valera1978/android_vendor_samsung_viennalte
Thanks again a lot for your work.
I wish you a happy new year!
@Valera1978
What such amazing gift for New Year!!!
Thanks for such awesome work my friend!
What is the different from this FW in compare to
https://forum.xda-developers.com/ga...-cyanogenmod-14-0-android-7-0-nougat-t3476335
? Does this thread continous the "old" one or it is a total other FW (other feature, Kernel .... ) ?
Mad07 said:
What is the different from this FW in compare to
https://forum.xda-developers.com/ga...-cyanogenmod-14-0-android-7-0-nougat-t3476335
? Does this thread continous the "old" one or it is a total other FW (other feature, Kernel .... ) ?
Click to expand...
Click to collapse
Hardware and config the same.
The idea is create another thread for custom firmwares, based on lineage\aosp.
Right now it's RR only, i'm working on OMNI rom, and later i'll build more firmwares.
please in other version don't insert the magisk.the rom to go in loop .and add in developer option the root gestion
Dagoncore93 said:
please in other version don't insert the magisk.the rom to go in loop .and add in developer option the root gestion
Click to expand...
Click to collapse
I'm taking a stab at what you are trying to express but the roms take 10 to 15 minutes to boot the first time because you are doing a full wipe. If you are not giving it at least that long magisk is not a likely cause.
Loakidog said:
I'm taking a stab at what you are trying to express but the roms take 10 to 15 minutes to boot the first time because you are doing a full wipe. If you are not giving it at least that long magisk is not a likely cause.
Click to expand...
Click to collapse
I received myself the error system ui crashed, and it got stuck on it.
Thanks Valera 1978, what a great new year gift!
I'm actually running Android 5.0.2, so is that Lollipop
Sent from my SM-G935F using XDA-Developers Legacy app
Albinoni said:
I'm actually running Android 5.0.2, so is that Lollipop
Click to expand...
Click to collapse
Yes
ralph_kl said:
I received myself the error system ui crashed, and it got stuck on it.
Click to expand...
Click to collapse
Send Valera1978 a bug report via Private Message. It is the only way developers can isolate the problem and fix it. In most Roms you can take a bug report via developer options.
help please Valera1978
i am updating from Resurrection Remix 5.8.5 version 20171231.
i wiped cache partitions
flashing rom 20180118 stuck on patching system unconditionally
theogalaxy said:
help please Valera1978
i am updating from Resurrection Remix 5.8.5 version 20171231.
i wiped cache partitions
flashing rom 20180118 stuck on patching system unconditionally
Click to expand...
Click to collapse
Try a full wipe magisk was removed with the latest version and super su added
A little help, please
Hello,
Sorry, but I need an help for understand.
How I can install this system?
I mean, can you explain to me what steps I need to do to install and which files to download?
sorry for my english, which is why I did not understand how to do it
Rosario
Valera1978 said:
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
This firmware was developed for the p905. It doesn't apply to the p905v at this time because it's bootloader locked and a custom recovery isn't possible.
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using nano gapps.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Links
2: 20180118: remove Magisk, back su: https://drive.google.com/file/d/11V0Hmu9Jjib-oLERLXPNXbMMAie_iORq/view?usp=sharing
1: 20171231: https://drive.google.com/file/d/1m7t_7gntp9cDRRxGnJJqnwufnJxFVKUZ/view?usp=sharing
Gapps
http://opengapps.org/
Platform: ARM
Android: 7.1
Recovery
Official TWRP: http://forum.xda-developers.com/showthread.php?t=2706982
Sources
Sources: https://github.com/ResurrectionRemix/
Device: https://github.com/Valera1978/android_device_samsung_viennalte
Kernel: https://github.com/Valera1978/android_kernel_samsung_viennalte
Vendor: https://github.com/Valera1978/android_vendor_samsung_viennalte
Click to expand...
Click to collapse
Compability
It is can flash for SM-P091 ?
i want the S Pen features and UI of Galaxy Tab S3 on my Galaxy Note 12.1 Pro Wifi. Am I right here and if yes how to do it please?
In terms of the little RAM I have I will use on microSD card as a RAM alternativ. is this a good idea in combination with a custom Rom?
Thx!
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.
Motorola Moto E5 Play [James]
XT1921-5 Sprint, Boost Mobile, Virgin Mobile
Stock Android 8.0.0 Oreo ROM
Build No. OCPS27.91-140-3
TWRP Flashable Installer
WARNING: Modifying your device's stock filesystem configuration (rooting, flashing, etc.) can render your warranty null & void, and carries with it the inherent risk of damaging your device (bricking) or rendering it otherwise inoperable. By proceeding further, you acknowledge these warnings and absolve me of any civil liability or responsibility in the event things go wrong. This ROM has been fully tested on my own device. Follow the below instructions carefully and things should go well. New or inexperienced members are encouraged to read and re-read the entire OP prior to performing any steps.
*********************************************
Please help keep this thread on topic. I am not a dev, so please do not request updates or post ETA-type inquiries. However, I will do my best at keeping this thread updated as future OTAs augment the incremental build or ROM version. Please be fully respectful to all members when posting. Keep in mind that language barriers can sometimes cause misinterpretations with intended meaning. Let's try to be tolerant of other members' level of experience, language, nationality, and all that good stuff. I'm here to learn and grow and I know many others are also. Thank you.
*********************************************
SPECIFICATIONS & FEATURES:
Compatible Model: xt1921-5 Only
Providers: Sprint, Boost Mobile, Virgin Mobile
Android Version: 8.0.0 Oreo
Build No. OCPS27.91-140-3
Kernel: 3.18.71-perf-g137d1ed
Radio: M8920_21.11.11.62R
Build Date: December 10, 2018
Security Patch Level: December 1, 2018
Systemless Root: Magisk v18.0-stable
SafetyNet Pass: ctsProfile & basicIntegrity
BusyBox: v1.29.3 /system/bin/busybox (static)
Init.d and su.d Support
AVB/dm-verity Disabled
Kernel Source Code: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-OCP27.91-23
CHANGELOG:
This ROM is built from a maintenance release OTA from the previous build (OCPS27.91-140-1). This update includes Motorola Mobility's standard bug fixes, stability improvements, and Android security patches through December 1, 2018. The Baseband Version (radio firmware) was not updated and remains at version M8920_21.11.11.62R. Hence, I did not include a Baseband updater in the downloads section. The bootloader partitions and partition index (GPT) were updated via the OTA. However, these were merely maintenance type updates and no substantial changes were made. For those members wishing to fully update their devices to OCPS27.91-140-3, I have included a partition updater in the downloads section.
REQUIREMENTS:
An unlocked bootloader and TWRP custom recovery are needed to install this ROM. If you do not have TWRP installed, visit XDA Senior Member @CodyF86's thread on TWRP for this device here: https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323 Also, be sure and thank @CodyF86 if you use his work.
INSTRUCTIONS:
**It is recommended that you first update your device partitions to the corresponding ROM build. Just download the partition updater below and install it with TWRP.
1. Download the ROM zip from the download link below and store it on your device's internal or external storage;
2. Boot your device into TWRP recovery mode;
3. Wipe System, Data, Cache & Dalvik/ART;
4. Select Install, navigate to the saved location of the ROM zip, select the file, and swipe the action bar to commence installation;
5. Once installation is finished, reboot system;
6. Done.
BUGS:
No known bugs. Please report any bugs in comments, with as much detail and clarity as possible. For members with knowledge on submitting bug reports, those are most helpful. Please so not post about bugs if you are using a custom kernel or if you are running ststem-based mods on this ROM (system-wide Xposed Framework, etc.). These types of modifications make it nearly impossible to properly diagnose a bug, or to determine the true source of the actual instability. Because this ROM is mostly pure stock, there should be no apparent instabilities or bugs outside of those possibly present within the factory stock build.
THANKS & MENTIONS:
I'd like to mention and give thanks to XDA Senior Member @CodyF86 for his hard work building TWRP for the James, and for his tutorials on TWRP & unlocking the bootloader. Also, thanks to the great @topjohnwu for his Magisk Universal Systemless Interface and his systemless root installer. Thanks to @osm0sis for his static BusyBox binary installer and his Magisk Modules.
DOWNLOAD LINKS:
OCPS27.91-140-3
Partition Updater: https://drive.google.com/file/d/1j1RUfGL41NsdLYtYaVQKxhMq6DD5p12V/view?usp=drivesdk
OCPS27.91-140-3 ROM: https://drive.google.com/file/d/1hivvpfy3OB5X3-njvLHQsuvcFhrfztvc/view?usp=drivesdk
Stock Recovery Image
OCPS27.91-140-3: https://drive.google.com/file/d/1dSiXl4ArnlJ9pD9gZtgvDSkjN2t-lKig/view?usp=drivesdk
Stock Boot Image
••Unmodified••
OCPS27.91-140-3: https://drive.google.com/file/d/1RoIGhfk91lDtyo3z_wzPT4S7Trc4OI8y/view?usp=drivesdk
Previous Builds:
OCPS27.91-140-1 ROM: https://drive.google.com/file/d/17steuhe7DUJEzYpbcuIqjlzQnwO3O0M3/view?usp=drivesdk
The download links require login. I want to try the rom but cannot download.
New Links?
The links above are password protected. I requested permission a few days ago for access, as Google Drive recommended, but I haven't heard anything back.
Did anyone get the files before the links went private? I would be very grateful for any help or advice.
I requested permission also, haven't heard back...
Anyone got a link for XT1921-3 Moto E5 Play (James)
again with password bad very bad
I just want to let you know that i am going to turn this into the government because
I just want to let you know that i am going to turn this into the government because you have given a link that doesnt work
lenovotech said:
motorola moto e5 play [james]
xt1921-5 sprint, boost mobile, virgin mobile
stock android 8.0.0 oreo rom
build no. Ocps27.91-140-3
twrp flashable installer
warning: Modifying your device's stock filesystem configuration (rooting, flashing, etc.) can render your warranty null & void, and carries with it the inherent risk of damaging your device (bricking) or rendering it otherwise inoperable. By proceeding further, you acknowledge these warnings and absolve me of any civil liability or responsibility in the event things go wrong. This rom has been fully tested on my own device. Follow the below instructions carefully and things should go well. New or inexperienced members are encouraged to read and re-read the entire op prior to performing any steps.
*********************************************
please help keep this thread on topic. I am not a dev, so please do not request updates or post eta-type inquiries. However, i will do my best at keeping this thread updated as future otas augment the incremental build or rom version. Please be fully respectful to all members when posting. Keep in mind that language barriers can sometimes cause misinterpretations with intended meaning. Let's try to be tolerant of other members' level of experience, language, nationality, and all that good stuff. I'm here to learn and grow and i know many others are also. Thank you.
*********************************************
specifications & features:
Compatible model: Xt1921-5 only
providers: Sprint, boost mobile, virgin mobile
android version: 8.0.0 oreo
build no. Ocps27.91-140-3
kernel: 3.18.71-perf-g137d1ed
radio: M8920_21.11.11.62r
build date: December 10, 2018
security patch level: December 1, 2018
systemless root: Magisk v18.0-stable
safetynet pass: Ctsprofile & basicintegrity
busybox: V1.29.3 /system/bin/busybox (static)
init.d and su.d support
avb/dm-verity disabled
kernel source code: https://github.com/motorolamobilityllc/kernel-msm/releases/tag/mmi-ocp27.91-23
changelog:
This rom is built from a maintenance release ota from the previous build (ocps27.91-140-1). This update includes motorola mobility's standard bug fixes, stability improvements, and android security patches through december 1, 2018. The baseband version (radio firmware) was not updated and remains at version m8920_21.11.11.62r. Hence, i did not include a baseband updater in the downloads section. The bootloader partitions and partition index (gpt) were updated via the ota. However, these were merely maintenance type updates and no substantial changes were made. For those members wishing to fully update their devices to ocps27.91-140-3, i have included a partition updater in the downloads section.
Requirements:
An unlocked bootloader and twrp custom recovery are needed to install this rom. If you do not have twrp installed, visit xda senior member @codyf86's thread on twrp for this device here: https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323 also, be sure and thank @codyf86 if you use his work.
Instructions:
**it is recommended that you first update your device partitions to the corresponding rom build. Just download the partition updater below and install it with twrp.
1. Download the rom zip from the download link below and store it on your device's internal or external storage;
2. Boot your device into twrp recovery mode;
3. Wipe system, data, cache & dalvik/art;
4. Select install, navigate to the saved location of the rom zip, select the file, and swipe the action bar to commence installation;
5. Once installation is finished, reboot system;
6. Done.
Bugs:
No known bugs. Please report any bugs in comments, with as much detail and clarity as possible. For members with knowledge on submitting bug reports, those are most helpful. Please so not post about bugs if you are using a custom kernel or if you are running ststem-based mods on this rom (system-wide xposed framework, etc.). These types of modifications make it nearly impossible to properly diagnose a bug, or to determine the true source of the actual instability. Because this rom is mostly pure stock, there should be no apparent instabilities or bugs outside of those possibly present within the factory stock build.
Thanks & mentions:
I'd like to mention and give thanks to xda senior member @codyf86 for his hard work building twrp for the james, and for his tutorials on twrp & unlocking the bootloader. Also, thanks to the great @topjohnwu for his magisk universal systemless interface and his systemless root installer. Thanks to @osm0sis for his static busybox binary installer and his magisk modules.
Download links:
Ocps27.91-140-3
partition updater: https://drive.google.com/file/d/1j1rufgl41nsdlytyavqkxhmq6dd5p12v/view?usp=drivesdk
ocps27.91-140-3 rom: https://drive.google.com/file/d/1hivvpfy3ob5x3-njvlhqsuvcfhrfztvc/view?usp=drivesdk
stock recovery image
ocps27.91-140-3: https://drive.google.com/file/d/1dsixl4arnlj9pd9gztgvdskjn2t-lkig/view?usp=drivesdk
stock boot image
••unmodified••
ocps27.91-140-3: https://drive.google.com/file/d/1roighfk91ldtyo3z_wzpt4s7trc4oi8y/view?usp=drivesdk
previous builds:
Ocps27.91-140-1 rom: https://drive.google.com/file/d/17steuhe7dujezypbcuiqjlzqnwo3o0m3/view?usp=drivesdk
Click to expand...
Click to collapse
After a month or so of testing it as a daily driver, I'll post my self built rom. It's been built just following my building guide, I didn't touch the code in any other way (and it's quite noticeable regarding the loudspeaker). It's still got a few bugs (and a few newer ones), but this is the first stable-ish rom I've managed to build since April. Tested on the US version only.
-- DISCLAIMER --
It is highly advised to backup all your phone data, as it will be PERMANENTLY LOST during the upgrade process. Keep in mind that will be needed for future updates as well, as all self built Lineage 19 roms from source needed a hard reset to work properly. This is a highly experimental build, so EVERYTHING IS AT YOUR RISK. I take to responsibility whatsoever.
Also, FOLLOW THE INSTRUCTIONS BELOW as repartitioning the device is NECESSARY for the success of the operation.
---> DOWNLOAD LINK HERE: https://androidfilehost.com/?w=files&flid=335748 <---
-- REQUIREMENTS --
- a computer with adb and fastboot installed. For further information and downloads go to https://developer.android.com/studio/releases/platform-tools
- a minimal comfort using a command line interface. For reference, a complete guide for the moto g7 play can be found here: https://wiki.lineageos.org/devices/channel/install
-- INSTRUCTIONS --
- download the regular Moto g7 partitioning file: https://androidfilehost.com/?fid=14655340768118450531 (thanks SyberHexen ). Remember this is STRICLY NECESSARY.
- connect your Moto g7 play in fastboot mode to a computer with adb and fastboot installed
- from the folder where the file has been downloaded, flash the Moto g7 partitioning file using this command:
fastboot flash boot ocean_gpt.bin
- from the moto g7 play, wipe the memory and the dalvik cache, go into recovery mode, allow sideloading and then sideload the lineage-19.1-20220721-UNOFFICIAL-channel file using the following command:
adb sideload lineage-19.1-20220721-UNOFFICIAL-channel.zip
- OPTIONAL: if you desire to install the Google apps, reboot your phone into Recovery Mode and sideload the respective package (MindTheGapps-12.1.0-arm64-20220416_174313 worked great for me)
- reboot.
-- SOURCE --
- base Lineage OS 19.1: https://github.com/LineageOS/android/tree/lineage-19.1 . This includes the standard sm6150 kernel found here: https://github.com/sm6150-motorola/android_kernel_motorola_sm6150
- SyberHexen's Motorola Channel specific settings: https://github.com/SyberHexen/android_device_motorola_channel/tree/lineage-19.1
- Proprietary blobs extracted through this guide from SyberHexen's April build (Android File Host)
-- KNOWN BUGS --
- the Lineage and the Whatsapp camera don't work well, in particular they don't always shoot photos when the button is pressed. Google Camera does work great tho.
- the backlight doesn't always turn up when calls are received (putting a finger on the fingerprint sensor with the phone ringing will turn it on)
- screen on on notifications does not work
- loudspeaker can be tinny at high volume (may be due to the loudspeaker's poor quality and to the common settings of the mixer_paths.xml file, for more info on the topic: https://forum.xda-developers.com/t/anyone-have-fix-for-low-volume-from-speaker.4054283/ )
Thank you all for this ROM, also there are LineageOS 20 builds (Android 13) on official LineageOS site, i want to ask if there is an way to fix ambient display on LineageOS 19, LineageOS 20 sadly gives me way too low RAM to use it, and SWAP memory is not working on Lineage 20
Edit: many apps do restart extremely often, but it's understandable since it's only an 2 GB RAM device running an ARM64 ROMs
@feder86co @chuy19312 Tell me please, does 4K video recording works on this particular ROM? Or is it possible at least?
kreksoverzum said:
@feder86co @chuy19312 Tell me please, does 4K video recording works on this particular ROM? Or is it possible at least?
Click to expand...
Click to collapse
Well, i didn't test that but sadly, Moto Camera doesn't even have enough permissions to save pictures to SD Card
please help..
I don't got a OS bc i was installing a ROM but it didn't work..
I was trying to install this but it says "No devices found"
newbierooter said:
please help..
I don't got a OS bc i was installing a ROM but it didn't work..
I was trying to install this but it says "No devices found"
Click to expand...
Click to collapse
Try to install Fastboot/ADB Driver
feder86co said:
After a month or so of testing it as a daily driver, I'll post my self built rom. It's been built just following my building guide, I didn't touch the code in any other way (and it's quite noticeable regarding the loudspeaker). It's still got a few bugs (and a few newer ones), but this is the first stable-ish rom I've managed to build since April. Tested on the US version only.
-- DISCLAIMER --
It is highly advised to backup all your phone data, as it will be PERMANENTLY LOST during the upgrade process. Keep in mind that will be needed for future updates as well, as all self built Lineage 19 roms from source needed a hard reset to work properly. This is a highly experimental build, so EVERYTHING IS AT YOUR RISK. I take to responsibility whatsoever.
Also, FOLLOW THE INSTRUCTIONS BELOW as repartitioning the device is NECESSARY for the success of the operation.
---> DOWNLOAD LINK HERE: https://androidfilehost.com/?w=files&flid=335748 <---
-- REQUIREMENTS --
- a computer with adb and fastboot installed. For further information and downloads go to https://developer.android.com/studio/releases/platform-tools
- a minimal comfort using a command line interface. For reference, a complete guide for the moto g7 play can be found here: https://wiki.lineageos.org/devices/channel/install
-- INSTRUCTIONS --
- download the regular Moto g7 partitioning file: https://androidfilehost.com/?fid=14655340768118450531 (thanks SyberHexen ). Remember this is STRICLY NECESSARY.
- connect your Moto g7 play in fastboot mode to a computer with adb and fastboot installed
- from the folder where the file has been downloaded, flash the Moto g7 partitioning file using this command:
fastboot flash boot ocean_gpt.bin
- from the moto g7 play, wipe the memory and the dalvik cache, go into recovery mode, allow sideloading and then sideload the lineage-19.1-20220721-UNOFFICIAL-channel file using the following command:
adb sideload lineage-19.1-20220721-UNOFFICIAL-channel.zip
- OPTIONAL: if you desire to install the Google apps, reboot your phone into Recovery Mode and sideload the respective package (MindTheGapps-12.1.0-arm64-20220416_174313 worked great for me)
- reboot.
-- SOURCE --
- base Lineage OS 19.1: https://github.com/LineageOS/android/tree/lineage-19.1 . This includes the standard sm6150 kernel found here: https://github.com/sm6150-motorola/android_kernel_motorola_sm6150
- SyberHexen's Motorola Channel specific settings: https://github.com/SyberHexen/android_device_motorola_channel/tree/lineage-19.1
- Proprietary blobs extracted through this guide from SyberHexen's April build (Android File Host)
-- KNOWN BUGS --
- the Lineage and the Whatsapp camera don't work well, in particular they don't always shoot photos when the button is pressed. Google Camera does work great tho.
- the backlight doesn't always turn up when calls are received (putting a finger on the fingerprint sensor with the phone ringing will turn it on)
- screen on on notifications does not work
- loudspeaker can be tinny at high volume (may be due to the loudspeaker's poor quality and to the common settings of the mixer_paths.xml file, for more info on the topic: https://forum.xda-developers.com/t/anyone-have-fix-for-low-volume-from-speaker.4054283/ )
Click to expand...
Click to collapse
when will we have new updates?
Androi100 said:
when will we have new updates?
Click to expand...
Click to collapse
Here, in the official site, there is an 2023-05-07 update
LineageOS Downloads
download.lineageos.org
chuy19312 said:
Here, in the official site, there is an 2023-05-07 update
LineageOS Downloads
download.lineageos.org
Click to expand...
Click to collapse
more on the site there is only one lineage 20
Androi100 said:
more on the site there is only one lineage 20
Click to expand...
Click to collapse
Well, sadly, LineageOS 19 zips were deleted, even LineageOS 18 zips some time ago, and i never understood why, there are only LineageOS 20 builds today
Androi100 said:
more on the site there is only one lineage 20
Click to expand...
Click to collapse
I just remembered, i have the last official LineageOS 19 for Moto G7 Play, i uploaded it to my Google Drive, here you have an link
lineage-19.1-20221225-nightly-channel-signed.zip
drive.google.com
The only bug it have is that ambient display doesn't work, at least, is the only one i found
Note to official developer of this ROM. if there is an problem to share this old version ROM, please tell me , but please, don't report my link in case there is an problem, i can remove the link but not the ROM since i have it because LineageOS 20 restarts almost all of the apps, multitasking on that rom doesn't exist because when switching on apps, they get restarted, even system ones
Edit: if someone have an build of LineageOS 18 or 18.1, please, give me an link for it