Develop Bugs

[CFW][KK4.4] GomdoLight KitKat Custom Firmware Environment (System Enhancement Pack)

Hi all,
Today, I proudly present GomdoLight KitKat for KOREAN LG G / G2 / G3 / G3A / G3cat6 / Gflex / GK / Gpro / Gpro2 / LTE3 / Vu2 / Vu3 / Gpad7LTE, one of the most widely used (with 20,000+ users approximately) stock-based custom firmware in South Korea.
GomdoLight is more than 3 year old already (first version released on 19th December 2012), and is very mature.
Technically speaking GomdoLight is NOT a complete ROM, but rather a large-scale patch, which modifies official stock firmware to remove all the unnecessary components preloaded by operator/manufacturer, and reorganizes key system parts to 'basic' Android OS with manufacturer's flavor. For some devices GomdoLight's own specialized tool 'GomdoLight Sideloader' can make it possible to install GomdoLight directly over the stock firmware, even without rooting or flashing custom recovery!
GomdoLight is compatible with the following devices (BOLD indicates GomdoLight Sideloader support - no root required)
LG Optimus G: LG-F180S, LG-F180K, LG-F180L ("G")
LG G2: LG-F320S, LG-F320K, LG-F320L ("G2")
LG G3: LG-F400S, LG-F400K, LG-F400L ("G3")
LG G3A: LG-F410S ("G3A")
LG G3 Cat.6: LG-F460S, LG-F460K, LG-F460L ("G3")
LG G Flex: LG-F340S, LG-F340K, LG-F340L ("Gflex")
LG GK: LG-F220K ("GK")
LG G Pro: LG-F240S, LG-F240K, LG-F240L ("Gpro")
LG G Pro 2: LG-F350S, LG-F350K, LG-F350L ("Gpro2")
LG Gx: LG-F310L, LG-F310LR ("Gx")
LG Optimus LTE3: LG-F260S ("LTE3")
LG Optimus Vu2: LG-F200S, LG-F200K, LG-F200L ("Vu2")
LG Vu 3: LG-F300S, LG-F300K, LG-F300L ("Vu3")
LG G Pad 7.0 LTE: LG-V410 ("Gpad7LTE")
A very thorough and extensive (probably, the most extensive on entire xda) manual is provided at the download page, which contains literally everything you need to know to install GomdoLight. FAILURE TO READ THIS DOCUMENT BEFORE INSTALLING WILL ALWAYS LEAD TO VARIOUS UNEXPECTED PROBLEMS. PLEASE READ CAREFULLY. Needless to say, I WILL NOT ANSWER ANY QUESTIONS ALREADY ADDRESSED IN THIS DOCUMENT.
Due to xda forum's limits (in functionality) I am posting a link to the separate (external) DOWNLOAD PAGE. There is no way I can link to each section in the document in xda posts, since xda does not support HTML tag. However some portions of the document are also introduced here.
▶ GomdoLight Download / Manual Page
GomdoLight TUTORIALS:
Want to read the built-in user manual again?
Need help using GomdoLight Flag functions?
Installing an EasyMod package? (Sorry the tutorial is in Korean, but screenshots will help)
XDA:DevDB Information
GomdoLight KitKat, ROM for various LGE devices
Contributors
juniecho
ROM OS Version: 4.4.x KitKat
ROM Firmware Required: STOCK FIRMWARE (Firmware compatibility table available)
Based On: STOCK FIRMWARE
Version Information
Status: Stable
Current Stable Version: 4.0
Created 2015-02-26
Last Updated 2015-12-31

CHANGELOG for older versions
Version History:
2015. 12. 31. - Wave 4, initial release
UPDATE LEVEL: MAJOR / IMPORTANCE: VERY HIGH
CHANGELOG:
Oh god, have I abandoned this thread this long? So many changes, sorry, I can't list them all.
A lot of things are now even better than ever. Trust me.
[#GLKITKATCOMMONUPDATE]

EMERGENCY NOTICE, etc.
Nothing for now.
* For those who have waited for a long time, sorry for being late, and thank you very much.

Still no e975 support.

PrettyJAE.swag said:
Still no e975 support.
Click to expand...
Click to collapse
choose f180k. if status bar is proved compatible everything will be good.
gomdolight kitkat is more script-oriented, so not many apks are replaced from the stock firmware. so there is a quite high possibility that it will be compatible with many variants.
however, you may need to 'debloat' the stock firmware by yourself, since i do not know what bloatwares are preloaded in non-korean stock firmware.

UPDATE - Wave 2, revision 3
UPDATE LEVEL: MEDIUM / IMPORTANCE: HIGH
UPGRADE INSTRUCTIONS:
One-touch upgrade via 'Upgrade/Repair' option
CHANGELOG:
Improved GomdoLight Engine scripts
Faster boot time, reduced processor load during boot
Improved GomdoLight operational status notifications
Slightly improved battery efficiency
'Update Center' components updated

2015. 4. 11. - Wave 2, Revision 5
UPDATE LEVEL: MEDIUM / IMPORTANCE: HIGH
UPGRADE INSTRUCTIONS:
IMPORTANT: Uninstall SuperSU app before upgrading. (However, do not perform 'full unroot') When you're done uninstalling SuperSU, do NOT reboot, and upgrade GomdoLight right away.
One-touch upgrade via 'Upgrade/Repair' option
CHANGELOG:
Improved GomdoLight Engine
Slightly faster system preparation
Update suggestion for GomdoLight Notification Provider (if available)
Bugs fixed

@juniecho thanks for your contribution, i have F300K branding is Olleh, now it is in recovery mode i have downloaded 2 file f20l.kdz and f20f.kdz but all stop at 50% or 54% when flashing, does F300K need to be flashed by its own specific branding? do you have links to these F300K Olleh firmware? (to flash before going to Gomdolight)
i would like to try using this Gomdolight ROM

touji said:
@juniecho thanks for your contribution, i have F300K branding is Olleh, now it is in recovery mode i have downloaded 2 file f20l.kdz and f20f.kdz but all stop at 50% or 54% when flashing, does F300K need to be flashed by its own specific branding? do you have links to these F300K Olleh firmware? (to flash before going to Gomdolight)
i would like to try using this Gomdolight ROM
Click to expand...
Click to collapse
sorry for late reply. by f300k you mean vu3. in the manual http://gomdolight.com/?page_id=518 you can find the 'firmware compatibility table' at 4-2.1. when you look at the table you will find download links for 20F stock kdz, which is proven safe. f300k can be flashed via lg flash tool 2014 (without specific branding or utility, etc.), and since the kdz file i provide is not a CSE-type kdz, you can just flash it with 'normal flash' mode. (by contrast, CSE-type kdzs should be flashed with 'CSE flash' option, and if you choose 'CSE flash' mode it will force a factory reset upon flashing)
sumup: 1) download the kdz file from the firmware compatibility table in the manual, 2) flash it with 'lg flash tool 2014' with normal flash mode.

did that already but stops at 40 or 50% when flashing, downloading the kdz file with IDM is not a problem? but i think when preparing the kdz file if any error occur, the LG flashtool should have notice it right?

touji said:
did that already but stops at 40 or 50% when flashing, downloading the kdz file with IDM is not a problem? but i think when preparing the kdz file if any error occur, the LG flashtool should have notice it right?
Click to expand...
Click to collapse
not sure. but for the f300k20f kdz,
CRC32: C766C041
MD5: 0D090EE1200812E11D2B87D2A5376C6B
SHA-1: 8F1CBAA6B1ACAAEB0D18E719B2240EAE5EBECE61
check before flashing.

UPDATE - Wave 2, revision 9
UPDATE LEVEL: MAJOR / IMPORTANCE: CRITICAL
UPGRADE INSTRUCTIONS:
Use the clear.root flag to unroot before upgrading if you're rooted (IMPORTANT)
You can always re-root using the enable.root flag (SEE http://gomdolight.flags.usage.gomdoli.us for details)
You do not need to revert to stock, but choose the 'FRESH INSTALLATION' option at the Installer's main menu even though you're actually upgrading. (You will go through the reconfiguration process)
CHANGELOG:
Greatly improved GomdoLight Engine scripts
Added support for a new flag: reboot.recovery - reboots into recovery environment (automatically into 2nd-init recovery if installed)
Added support for a new flag: auto.install.xposed.framework - automatically schedule installation of Xposed framework when the Xposed Installer app is installed but the Xposed Framework is not.
Improved stability and battery efficiency
Automatically restores GomdoLight Engine functionality when GomdoLight Engine can't be initialized
Removed IM+ from the Update Center
Added 'LG Tag+', and 'Privilege Terminal' to the Update Center
'Update Center' components updated
(G2, Gpro, Vu3, Gflex) Now the clock/date indicator shown when the status bar is expanded will NOT do anything if you click on it, instead of taking you to the Date/Time Settings screen.
(G2, Gpro2, G3, G3A, G3cat6, Gflex) Now you can choose between stock navbar thickness and reduced (by about 25%) navbar thickness
(Gpro2, G3, G3cat6, Gflex) Better DualWindow (SplitWindow) app support
(G3, G3A, G3cat6) Improved QuickRemote (Q Remote), now you can control some air conditioners and audio systems.

juniecho said:
not sure. but for the f300k20f kdz,
CRC32: C766C041
MD5: 0D090EE1200812E11D2B87D2A5376C6B
SHA-1: 8F1CBAA6B1ACAAEB0D18E719B2240EAE5EBECE61
check before flashing.
Click to expand...
Click to collapse
i tried flash multiple time with errors but finally after about 20 times it gets to 100% and the phone was back in normal state again, thanks for your reply

The download link is dead?

allthedogs said:
The download link is dead?
Click to expand...
Click to collapse
sorry for late reply. it has moved, but i forgot here
please go to www.gomdolight.com

UPDATE - Wave 4, initial release
UPDATE LEVEL: MAJOR / IMPORTANCE: CRITICAL
UPGRADE INSTRUCTIONS:
Revert to stock firmware first, then perform a fresh install
CHANGELOG:
Too many improvements to list here.
Tons of bugfixes.

Is it support G international version ?

paul_zm said:
Is it support G international version ?
Click to expand...
Click to collapse
no, but it might be compatible with your device. To maximize the chance select 'Do not overwrite the status bar' when you're asked to select the Battery Percentage Indicator type.

Wanted to thank you for the hard work
Using a LG vu3- K and this was a savior for me - Wanted to know if possible to update the ROM and retrain the firmware? or if there are compatible rom's ? KK 4.2 is still great but newer architecture would be nice

[Recovery] TWRP 2.8.7.x for the G925T on 5.1.1 (OF6) + [Kernel]Aou's OH6 Stock Kernel

Intro:
I've put in a serious number of hours poking around my G925T that I've upgraded to the official G925TUVU2COH6 firmware, trying to get TWRP installed and working on our device. With help from @bigbiff, @_that, and several testers in this thread, we finally have something working solid for our device. Before continuing, please take a moment to read through the extremely-relevant warnings below:
WARNING: Intentionally modifying your System partition from TWRP recovery, without first flashing a custom kernel (kernel must have no "verify" mount parameter in fstab), will likely cause a soft-brick (boot-loop). Before flashing this (or any) custom recovery/kernel, it is advised that you know how to restore your phone back to OH6 stock using Odin.
Note: Flashing a custom kernel (while keeping a stock System/ROM) may cause your device to report a security threat. If you proceed without caution, the device will literally attempt to re-flash the stock OH6 kernel again. It is possible to freeze "Security Log Agent" (or uninstall it completely), and this should keep your device from reporting this problem. Other reports say that using "Smart Manager" might also report the security threat, and there are some options out there for replacing it with a patched version.
Rooted Phones: Do NOT allow "com.tmobile.pr.adapt" to obtain root permissions, EVER. This app might be something that T-Mobile uses to determine if your device has ever been rooted. I would recommend freezing/disabling this app.
Unlocked Phones: If you have unlocked your phone, you might run into problems with 5.1.1. There have been reports of phones stuck in a boot-loop when upgrading from 5.0.2 -> 5.1.1 when the phone has been unlocked or EFS/IMEI has been tampered with. Combine this with the new "FRP LOCK" (Factory Reset Protection) in 5.1.1, and you might find yourself with a complete brick with no warranty. This issue may or may not have anything to do with rooting or custom firmware.
WARNING: Flashing any custom firmware to your device will trip the KNOX Warranty Bit. At this time, this is irreversible, and might cause you problems when returning faulty devices to T-Mobile or Samsung. YMMV.
Click to expand...
Click to collapse
How-To-Install (The Short Version):
Recognize that this will trip KNOX.
Be sure you're actually already running the 5.1.1 (OH6) firmware. If you're on 5.0.2 (OCG, for example), this thread is not for you.
Turn on "OEM unlocking" in Settings -> Developer options. This is the dreaded "FRP LOCK" that prohibits custom firmware from being flashed to the G925T/G920T (and maybe others) - it's something new in 5.1.1.
Download and Odin-flash my v13 of TWRP 2.8.7.x.
Download and Odin-flash (or TWRP-flash) my v1 build of the OH6 kernel. G920T users should use the appropriate G920T kernel for their device.
(Optional): Download and TWRP-flash Chainfire's SuperSU v2.49 (.zip format).
(Advice): Use Titanium Backup or some other app to freeze/disable/uninstall "SecurityLogAgent" (remove nagging about security) and "com.tmobile.pr.adapt" (remove nagging about root, helps with sleep, and may be used by T-Mobile to determine your rooted status).
Enjoy TWRP + Root with an almost-completely-stock OH6 kernel/system!
Click to expand...
Click to collapse
Official TWRP for G925T:
It's official! Thanks to all of our hard work in this thread, plus a bunch of work getting things fine-tuned and finalized by @bigbiff, our device is now officially supported by TeamWin! Check out the official page here. Development will continue here on this thread until further notice, and I'll always be building the latest-and greatest from source and making it available in this thread (not to mention this is the go-to place to get the latest version of my kernel).
Click to expand...
Click to collapse
Downloads:
Here's the Odin-flashable OF6 kernel I've built:
Version 1 (6/25/15) - built from OF6 stock kernel source, no modifications
Version 2 (6/27/15) - built from OF6 stock kernel source, fixes boot-loop
Version 3 (6/28/15) - built from OF6 stock kernel source, fixes boot-loop and allows root
Version 4 (6/28/15) - built from OF6 stock kernel source, fixes boot-loop, allows root, and fixes Deep Sleep - also available as a TWRP-flashable .zip or Flashify .img
Here's the Odin-flashable OF8 kernel I've built:
Version 1 (8/10/15) - built from OF8 stock kernel source, fixes boot-loop, allows root, and fixes Deep Sleep - also available as a TWRP-flashable .zip or Flashify .img
Here's the Odin-flashable OH6 kernel I've built:
Version 1 (9/15/15) - built from OH6 stock kernel source, fixes boot-loop, allows root, and fixes Deep Sleep - also available as a TWRP-flashable .zip or Flashify .img
Here's the Odin-flashable TWRP recovery I've put together:
Version 13 (7/10/15) - also available as a Flashify .img
And, in case you need it, here's the stock OF8 recovery as an Odin-flashable:
OF8 Stock Recovery - No guarantees it won't trip KNOX (it shouldn't), but if you're needing this, you've probably already tripped KNOX. Sorry, I'm too lazy to package and upload a flashable OH6 stock kernel.
G920T users! I bring you a gift! I took the G920TUVU2DOH6 Samsung source, built it with the same modifications as I did the G925T kernel to allow modified System partitions (allows root w/o bootloop), and then stuck that into the G920T OH6 stock kernel provided by @icepuente (thanks!). Also, some additional thanks to @icepuente for testing it, too!
Version 1 (9/21/15) - FOR G920T - built from G920TUVU2DOH6 stock kernel source, fixes boot-loop, allows root, and fixes Deep Sleep - also available as a TWRP-flashable .zip or Flashify .img
Click to expand...
Click to collapse
Building this OH6 kernel from source:
Setup your build environment for compiling Android.
Download the latest NDK, unpack, etc., etc.
Download the OH6 source code directly from Samsung.
Update the Makefile's CROSS_COMPILE to use the NDK toolchain. Mine ended up looking like this: /home/aou/android/NDK/android-ndk-r10e/toolchains/aarch64-linux-android-4.9/prebuilt/linux-x86_64/bin/aarch64-linux-android-
make exynos7420-zerolte_tmo_defconfig
For some reason, gcc treats CONFIG_ALWAYS_ENFORCE as always defined, and therefore the kernel will, of course, always enable SELinux: Enforcing. This makes it "impossible" to root Android 5.1.1. There is a workaround:
rm -rf security/selinux
svn export https://github.com/glewarne/S6-UniKernel/trunk/security/selinux security/selinux (snags a copy of their security/linux folder...)
Go give the guys over at the UniKernel thread some "Thanks!" for making this workaround in their kernel, especially @AndreiLux - he was the one to author this change to their source that fixes this problem.
Replace drivers/scsi/sd.c with Sujit Reddy Thumma's Deep Sleep fixed version, referenced in the UniKernel's source:
curl https://raw.githubusercontent.com/glewarne/S6-UniKernel/master/drivers/scsi/sd.c > drivers/scsi/sd.c
make -j#
Go snag that juicy arch/arm64/boot/Image - This is your kernel zImage.
Go download the official OH6 Odin package and extract the boot.img (kernel) from it.
Unpack the official kernel using the mkbootimg_tools, available here, replace the kernel file in the unpacked boot.img, and then repack it into a boot.img again. This boot.img would need to be tarballed and md5summed to be Odin flashable.
You'll want to remove the ,verify from both of these files in the ramdisk: fstab.samsungexynos7420 and fstab.samsungexynos7420.fwup
At the bottom of default.prop, you'll want to add these two lines:
Code:
ro.securestorage.support=false
androidboot.selinux=0
Building TWRP from source:
Setup your build environment for compiling Android.
Download the latest NDK, unpack, etc., etc. Mine ended up in ~/android/NDK.
Git clone the TWRP zerolte kernel source somewhere useful. Mine was cloned into ~/android/kernel:
git clone https://github.com/TeamWin/android_kernel_samsung_zerolte.git -b android-5.1 ~/android/kernel
The next several steps The next several steps are performed in & relative to this path.
Update the Makefile's CROSS_COMPILE to use the NDK toolchain. Mine ended up looking like this: /home/aou/android/NDK/android-ndk-r10e/toolchains/aarch64-linux-android-4.9/prebuilt/linux-x86_64/bin/aarch64-linux-android- (to match my NDK path above - note I couldn't use the relative ~ path for /home/aou).
make exynos7420-zerolte_defconfig (ignore warnings about 'jump')
make -j# (replace # with number of CPU cores + 1)
Note the location of the output kernel - you'll need it in a little bit. In my case, it would be ~/android/kernel/arch/arm64/boot/Image.
Setup your Omnirom compile environment. Mine's in ~/android/omni. The next several steps are performed in & relative to this path.
Git clone the TWRP zeroltetmo device source into device/samsung/zeroltetmo:
rm -rf device/samsung/zeroltetmo && git clone https://github.com/TeamWin/android_device_samsung_zeroltetmo.git -b android-5.1 device/samsung/zeroltetmo
For some reason, TWRP doesn't build too well with the Omnirom's version of busybox. Replace the whole external/busybox folder with that from cm-12.1 source:
rm -rf external/busybox && git clone https://github.com/CyanogenMod/android_external_busybox.git -b cm-12.1 external/busybox
Remember that kernel we built? Rename/copy it to replace device/samsung/zeroltetmo/kernAl. In my case:
cp ~/android/kernel/arch/arm64/boot/Image device/samsung/zeroltetmo/kernAl
At this time (7/10/15), we need to cherry-pick a change by Dees Troy from the TWRP Gerrit. This is the stuff about forcing Read-Only mode on first boot, which will help with some of the boot-loop stuff (if you still have a stock kernel). You can grab the changes fairly easily using:
cd bootable/recovery && git fetch https://gerrit.omnirom.org/android_bootable_recovery refs/changes/15/14015/3 && git cherry-pick FETCH_HEAD && cd ../..
Since we're using Omnirom source and we're going to use lunch later, we need to create device/samsung/zeroltetmo/vendorsetup.sh. We can do that like this:
echo add_lunch_combo omni_zeroltetmo-eng > device/samsung/zeroltetmo/vendorsetup.sh
Do a . build/envsetup.sh (note the space between the period and "build" - was important for my environment).
lunch for omni_zeroltetmo-eng
make -j# recoveryimage (again, number of CPU cores +1)
Take that precious out/target/product/zeroltetmo/recovery.img and tarball/md5sum it to be Odin flashable.
Flash away!
Click to expand...
Click to collapse
Notes about accidentally causing a boot-loop:
The OF6/OF8/OH6 kernel, out-of-the-box, checks the hash/signature of your system partition. Modifying your system partition in any way (without flashing a custom kernel that does not perform this check) will cause your device to boot-loop.
Additionally, if you decide to use TWRP to mount your System partition read-write (despite warnings), upon exiting TWRP properly, it will make some changes to your system partition for you (namely, renames /system/recovery-from-boot.p to /system/recovery-from-boot.bak to prevent some systems from re-writing over your custom recovery). This would cause the boot-loop.
You obviously have some options to avoid causing a bootloop!
Option 1a: Flash my v4 kernel above. It does not have the hash/signature checks, plus it sets SELinux to permissive (allowing root!). You'll still need to root the device manually by flashing Chainfire's SuperSU.
Option 1b: Flash a different custom kernel that does not have these checks. The S6 UniKernel seems to work fine, for example.
Option 2: Don't modify your System partition, and don't let TWRP exit properly while you have the "read-only" checkbox unchecked (in the Mount screen).
Recovering from a boot-loop:
Something go wrong? Skip a step? No big deal. To get our device back in working order, you have a couple options:
Option 1: Flash the official OH6 firmware via Odin again. In my experience, the package DOES NOT wipe your data or sdcard partitions, so it really isn't that big of a deal to do. It just takes downloading a monster-size file, and the foreknowledge on how to flash it. But, caveat, don't blame me if something goes wrong with restoring the stock firmware!
Option 2: See Options 1a & 1b in the first list above. By flashing a custom kernel that doesn't have the hash/signature checks included, it should fix the boot-loop.
Click to expand...
Click to collapse
More Notes:
Huge thanks to @bigbiff for reading through prior versions of this post and updating the TWRP source code to work without device without the need of heavy modification. Additional thanks to @_that for his invaluable help in this project.
Click to expand...
Click to collapse

Hope this get resolved thanks soo much @Aou !

That's some progress made
Good to hear!

Nice work @Aou

Yay! Progress has been made! Congratulations, @Aou!

http://forum.xda-developers.com/showthread.php?t= check that out looks like root via a odin able unified kernel pre rooted and twrp
Sent from my SM-G925T using XDA Free mobile app

@tylerholbrook - I'm not sure what you're linking to? (broken link?)
And, to update everyone following this post, I've just uploaded v7 and a custom OF6 kernel, and replaced my DIY instructions with what I've done this time around. MUCH simpler with 2.8.7.0!
Also:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is this proof enough for anyone that 5.1.1 does NOT lock the bootloader?

Aou said:
@tylerholbrook - I'm not sure what you're linking to? (broken link?)
And, to update everyone following this post, I've just uploaded v7 and a custom OF6 kernel, and replaced my DIY instructions with what I've done this time around. MUCH simpler with 2.8.7.0!
Also:
Is this proof enough for anyone that 5.1.1 does NOT lock the bootloader?
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...-stockmod-kernel-t3100395/page50#post61551321
try that one,, sorry, on my computer now. Its in the unified development section for the unified kernel.. They have a working TWRP for the non edge and there is a patched kernel that should give root for us when flashed in odin. If I read correctly. I'm still on 5.0.2 or I would test it, I just dont want to upgrade and it not work and be stuck having to flash the whole factory image. I need root for tethering ect..
---------- Post added at 08:34 AM ---------- Previous post was at 08:30 AM ----------
tylerholbrook said:
http://forum.xda-developers.com/gal...-stockmod-kernel-t3100395/page50#post61551321
try that one,, sorry, on my computer now. Its in the unified development section for the unified kernel.. They have a working TWRP for the non edge and there is a patched kernel that should give root for us when flashed in odin. If I read correctly. I'm still on 5.0.2 or I would test it, I just dont want to upgrade and it not work and be stuck having to flash the whole factory image. I need root for tethering ect..
Click to expand...
Click to collapse
@Aou somehow Sunderwear got another mysterious update OTA that was prerooted to my understanding... more info on that is in the TMobile galaxy s6 thread in the general section.

tylerholbrook said:
http://forum.xda-developers.com/gal...-stockmod-kernel-t3100395/page50#post61551321
try that one,, sorry, on my computer now. Its in the unified development section for the unified kernel.. They have a working TWRP for the non edge and there is a patched kernel that should give root for us when flashed in odin. If I read correctly. I'm still on 5.0.2 or I would test it, I just dont want to upgrade and it not work and be stuck having to flash the whole factory image. I need root for tethering ect..
---------- Post added at 08:34 AM ---------- Previous post was at 08:30 AM ----------
@Aou somehow Sunderwear got another mysterious update OTA that was prerooted to my understanding... more info on that is in the TMobile galaxy s6 thread in the general section.
Click to expand...
Click to collapse
I'll have to mess with those tomorrow. Thanks!
(okay, now I really need to go to bed! Work in the morning...)

Aou said:
I'll have to mess with those tomorrow. Thanks!
(okay, now I really need to go to bed! Work in the morning...)
Click to expand...
Click to collapse
Ha yeah no problem. Really hoping it works for us but they had success on the 920x versions as well as a fully working TWRP that could probably be used to branch and get yours fully working. Fingers crossed :good: Thanks for your hard work!

Bam. 5.1.1 root

Did you see bigbiff released a TWRP for the other guys where everything works. Should I test out v7? I just don't want a bootloop lol

ktetreault14 said:
Did you see bigbiff released a TWRP for the other guys where everything works. Should I test out v7? I just don't want a bootloop lol
Click to expand...
Click to collapse
For the other guys? Mind linking me up?

Adizzzle said:
For the other guys? Mind linking me up?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3080940

The only missing piece of the puzzle

Thank you for having this so I didn't I'm have to reodin

Sorry a little confused here does that mean we have a new TWRP image available for the G925T/W8

Well I can't take a backup but it doesn't screw my boot up

ktetreault14 said:
Well I can't take a backup but it doesn't screw my boot up
Click to expand...
Click to collapse
Really? It didn't screw up your boot? Interesting...
In any event, the v7 I had uploaded last night was not actually v7. It was some bastardized hybrid of v6 and v7. I re-uploaded the REAL v7.
Still breaks System at this time, but I'm working on it. The TWRP for the international S6 seems to have pretty much all the same source as mine, at least what they're showing right now. I'll double check and verify some stuff.
As for root, great! I'm looking into baking the same thing into my kernel, so those who want to say closer to TMO stock can do so without fear. It's possible that the SuperSU flashable zip would work on 5.1.1 if we just set SEAndroid to "permissive" which is what I see that those guys are doing, primarily. The rest is just convenience - taking advantage of:
a) some emergency-flash feature that samsung has baked in (lets the device flash or execute something on boot, if it needs to), and
b) some modified int.rc script and injecting root and starting it with every boot.
I'm looking into this, and fixing my TWRP. Also looking into the feasibility of flashing/repairing the System partition from my existing v7 broken TWRP...

Aou said:
Really? It didn't screw up your boot? Interesting...
In any event, the v7 I had uploaded last night was not actually v7. It was some bastardized hybrid of v6 and v7. I re-uploaded the REAL v7.
Still breaks System at this time, but I'm working on it. The TWRP for the international S6 seems to have pretty much all the same source as mine, at least what they're showing right now. I'll double check and verify some stuff.
As for root, great! I'm looking into baking the same thing into my kernel, so those who want to say closer to TMO stock can do so without fear. It's possible that the SuperSU flashable zip would work on 5.1.1 if we just set SEAndroid to "permissive" which is what I see that those guys are doing, primarily. The rest is just convenience - taking advantage of:
a) some emergency-flash feature that samsung has baked in (lets the device flash or execute something on boot, if it needs to), and
b) some modified int.rc script and injecting root and starting it with every boot.
I'm looking into this, and fixing my TWRP. Also looking into the feasibility of flashing/repairing the System partition from my existing v7 broken TWRP...
Click to expand...
Click to collapse
Yeah it didn't break system. It also didn't let me backup. Though. Haven't tried other yet.

[ROM][Z00L][5.0.2] Stock Deodexed Pre-rooted ROM for ZF2 Laser [UNLOCKED BOOTLOADER]

Stock Deodexed, Debloated, pre-rooted ROM for Zenfone Laser 2 is here.
I have removed most of the unwanted bloatware but kept few useful apps like Playstore, AsusBackup, PClink, Remotelink, Filemanager, etc.
List of removed apps (from 1.17.40.1234 ) From 1.17.40.1531
System/App:
Asus Browser
Asus DrawRes
Asus fmradio (Added back in .1531)
Asus Fmservice (added back in .1531)
Asus mirror
AWS
Bbbleractor
BRapps
CleanMaster
Data transfer
DrEye
Drive
Drive Activator
eMusic (added back)
Gameloft
Hangouts
Kindle
KKbox
Maps
MyAsus
Music2 (google)
Omlet-stub
Photos (google)
Puffin Browser
Trip advisor
Videos (Google)
What's next
Yahoo auction
YahooECShopping
YahooMall
Zenflash
ZenTalk
ZenUI help
Zenio
Zenioservice
Viso
System/priv-app:
Applocker
Asus Calculator
Asus fresh green theme
Asus lovely pink theme
Asus quick search (Google)
Asus task (do it later)
Game center
Laser Ruler
Microfilm (mini movie)
ShareRimBinary (share link)
Supernote
ZenCircle
/system/etc
Amazon.kindle.pro
Ezding
Features
➪Pre-rooted
➪Deodexed
➪Debloated
➪Both TWRP and Fastboot flashable
1.17.40.1531 is Zipaligned too.
DOWNLOADS
1.17.40.1234 1.17.40.1531
Flashable zip :
Z00L_1.17.40.1531_deodexed [Google Drive link]
1.15.40.871
Fastboot .img : [Google Drive link] | [AndroidfileHost Link]
Instructions
Method 1: Via Custom recovery- [Get TWRP]
1. Download Flashable zip
[file name: Z00L_deodexed_10may2016_fixed2.zip]
2. Put it in your External sd-card.
3. Boot you phone in recovery mode.
4. Wipe System, Data, Cache, Dalvik Cache.
5. Install/Flash the ROM zip!
6. Reboot
Method 2: via fastboot-
1. Download Fastboot .imgs
2. Install Asus drivers.
3. Download adb_fastboot.zip and extract its contents to the same folder where you have system-deodexed.img and boot.img files.
4. Reboot your phone to 'bootloader mode'. To do this turn of your phone completely. Hold volume down button and then press and hold power button. Release power button after Asus logo appears and then release volume down button. Your phone is now in bootloader mode.
5. Connect your phone to pc via a reliable usb cable. Look at your phone screen. It should display "Fastboot mode!"
6. Now go to the folder where you have extracted all the files. Holding down shift key, Right click on any point on white screen. Then click on 'open command window here' from the menu that appears. Command Prompt will open now
7. On command prompt type
Code:
fastboot devices
and check if it is detecting your device.
8. Now run the following commands in the given sequence
Code:
fastboot flash boot boot.img
fastboot.exe flash system system.img
fastboot erase userdata
fastboot erase cache
fastboot reboot
"fastboot flash system system.img" will take 10-20 mins to start flashing, so be patient.
Flashable Zip of Removed apps
Use this if you want any of the removed apps.
Download Link: [Google Drive] | [Android File Host]
All apps are deodexed
Bugs
1. Calculator FC - Fixed in 24 May update
​
Credits:
@xpirt - Guide for handling system.new.dat
@SuperR. - kitchen for deodexing
@Chainfire - for superSU
@luca020400 - for twrp
Go thank all these awesome developers!!!
XDA:DevDB Information
Optimized Z00L Stock ROM, ROM for the Zenfone 2 Laser
Contributors
sziraqui
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Unlocked Bootloader
Based On: Stock build-v1.17.40.1234
Version Information
Status: Beta
Current Stable Version: NA
Created 2016-05-04
Last Updated 2016-06-15

#Reserved
Future tasks: All tasks completed
-Rebuild from 1.17 WW firmware :good: Done
-Flashable zips for flashing removed apps :good: Done
-Deodex /system/vendor/app :good: Not found in 1.17.40.1234 firmware
-Remove more bloatware. :good: 437mb of bloat removed
CHANGELOG-
24 May 2016
1. Fixed Calculator FC
2. Fixed missing root
3. Added busybox
Click to expand...
Click to collapse
15 June 2016
1. Rebuilt from 1.17.40.1531
2. supersu within system.new.dat
3. Retained FMservice, FMRadio, eMusic as these were potentially causing headphone issue
Click to expand...
Click to collapse

Really loving the upsurge in development for the ZF2L. Awesome work mate!
Sent from my ASUS_Z00TD using Tapatalk

Can you do this for the WW1.16.40.763 version? I think they removed the 1.15.40.871 version for some unknown reason(security compromise may be?)

OMIT

souravipc53 said:
Can you do this for the WW1.16.40.763 version? I think they removed the 1.15.40.871 version for some unknown reason(security compromise may be?)
Click to expand...
Click to collapse
Yeah, I can, but I was thinking to rebuild from 1.17 stock version. By the way, have you tried it? I would like to have your reviews

sziraqui said:
Yeah, I can, but I was thinking to rebuild from 1.17 stock version. By the way, have you tried it? I would like to have your reviews
Click to expand...
Click to collapse
So far its smooth. I was using CM version due to the bloated Asus rom but it has returned my faith in stock ROM again. Thanks OP

souravipc53 said:
So far its smooth. I was using CM version due to the bloated Asus rom but it has returned my faith in stock ROM again. Thanks OP
Click to expand...
Click to collapse
Please don't compare ROMs. CM is built from source. I have just modified a ROM.
I am not even a nail dust of the developers of CM. They are the real developers!!!

sziraqui said:
Please don't compare ROMs. CM is built from source. I have just modified a ROM.
I am not even a nail dust of the developers of CM. They are the real developers!!!
Click to expand...
Click to collapse
Agreed, however, your work is much appreciated! My other DD is a Moto E 2015 4G LTE, and this phone seems to be taking off with mad developer love as the Moto E did at the end of last year. Much respect!
On a side note,, other than the big LITTLE issue, would this work on Z00TD?

lenigma1too said:
Agreed, however, your work is much appreciated! My other DD is a Moto E 2015 4G LTE, and this phone seems to be taking off with mad developer love as the Moto E did at the end of last year. Much respect!
On a side note,, other than the big LITTLE issue, would this work on Z00TD?
Click to expand...
Click to collapse
Nope, this won't work on Z00TD, don't even try.
Z00T runs 615 snapdragon while this rom is for Z00L running 410 Snapdragon. Many more hardware differences

sziraqui said:
Nope, this won't work on Z00TD, don't even try.
Z00T runs 615 snapdragon while this rom is for Z00L running 410 Snapdragon. Many more hardware differences
Click to expand...
Click to collapse
Fair enough! The irony here is as I mentioned before my other DD is a Moto E 2015 4G LTE, which also runs the Snapdragon 410, LOL ... same bored too I believe the msm8916

lenigma1too said:
Fair enough! The irony here is as I mentioned before my other DD is a Moto E 2015 4G LTE, which also runs the Snapdragon 410, LOL ... same bored too I believe the msm8916
Click to expand...
Click to collapse
I really doubt if it will even boot on surnia, the ROM depends on 64 bit libs which surnia doesnt support (correct me if i am wrong)

sziraqui said:
I really doubt if it will even boot on surnia, the ROM depends on 64 bit libs which surnia doesnt support (correct me if i am wrong)
Click to expand...
Click to collapse
That's one of the odd Snippets about the Moto E 2015 4G LTE. Although all of the hardware is 64-bit capable, it has been, for lack of a better word, restricted to 32bit. Squid2, a
kernel developer and ROM maintainer for several Moto devices, had a couple of solid xtheories as to why, but the fact that it only has 1 gig of RAM makes it proof positive that 64-bit would be a waste of time on that unit. And I was never even thinking about trying to flash this ROM on a Motorola! LOL
If you do decide to work your magic on the z00 TD, PM me and I will jump at the chance, first in line!

New version is out . Rebuilded from 1.17.40.1234.
457mb of bloatware removed.
Download it from my Gdrive

Error while flashing
Thank you so much for your hard work sir. I appreciate your contribution to this device. Sadly i would like to say that while i was trying to flash your May6 update i encountered an error. It was not ready to flash and got aborted. I would really be thankful if you see to the problem and solve it ASAP. thank you.

Santanuhbk30 said:
Thank you so much for your hard work sir. I appreciate your contribution to this device. Sadly i would like to say that while i was trying to flash your May6 update i encountered an error. It was not ready to flash and got aborted. I would really be thankful if you see to the problem and solve it ASAP. thank you.
Click to expand...
Click to collapse
Can you provide more info-
What error message you got?
Which phone model you were flashing?
Do you unlocked bootloader?
What is your SKU? (Found in build.prop)
IF your phone model is ZE550KL (ASUS Z00LD) download updater-script.zip attached. extract the file from it.
Replace updater-script from downloaded rom with this new updater-script.
Detailed instructions-
In your ROM zip, goto META-INF/com/google/android
You will see two files, "update.binary" and updater-script"
Rename the original updater-script to "updater-script.bak"
Now copy the EXTRACTED "updater-script" to the same folder where update-binary exists.

ZE601KL
Does this work for ZE601KL?

Alucarde said:
Does this work for ZE601KL?
Click to expand...
Click to collapse
No. But if there are enough users of of this variant, I will make a deodexed ROM for it. I will need testers. So tell me if you are in for testing. Mostly, there won't be any issues in even the first build but I need someone to confirm.

final version released (Z00L_deodexed_10may2016.zip)
Download link updated in original post

sziraqui said:
final version released (Z00L_deodexed_10may2016.zip)
Download link updated in original post
Click to expand...
Click to collapse
Hi thanks! it seems there's a new update for ze550kl

[ROM][8.0.0][STOCK] Stock Android 8.0.0 ROM for Moto E5 Play (James) XT1921-5

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.

Delete

Mod: Delete thread and delete my account. Thanks.

bob24260 said:
This is the Stock Boot Image & Magisk Patched Stock Image OOS 11.0.5.1.HD65AA for OnePlus 7T Global and OnePlus 7T T-Mobile variant that's been converted to International (Global) variant. I won't include a tutorial on how to flash because if you don't already know how to do this you shouldn't be messing with it anyway. I pulled the boot image from the OTA 11.0.5.1.HD65AA and extracted it with payload dumper go by ssssut , original thread here:
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this can extract img files from (full) OTA payload.bin really quickly. See how fast this is: https://i.imgur.com/adpijqf Source Code: https://github.com/ssut/payload-dumper-go Prebuilt binaries...
forum.xda-developers.com
Thanks to ssssut for what I'm sure was countless hours creating this handy little tool. Make sure you thank him for making all of our lives easier with this tool. Also thanks to topjohnwu for his revolutionary Magisk. We couldn't enjoy root without you.
I take no responsibility for anything you flash to your devices. You do it freely and voluntarily and if you yell at me for ending up with a doorstop I will laugh and point right back at you. Having said that, I hope this helps someone. Yes I know other people have posted these but it doesn't hurt to have several sources for these files. I highly recommend that you patch the stock boot image yourself with magisk from the intended device but I'm including it as well anyways.
Click to expand...
Click to collapse
thanks bro for the files
i already tested and it works