Database Info

Stock XT1562 RETEU Single-SIM 5.1.1 to Stock XT1562 RETASIA Dual-SIM 6.0 (No Wipe)

Hello everyone, I just upgraded my phone to Dual SIM Marshmallow yesterday while leaving the bootloader intact and without losing any data (as far as I can tell). Yes, this is a dirty flash operation, so proceed with caution.
First a little bit of gibberish: Because I got tired of waiting around for the European 6.0 update, and also having interest in the Dual SIM function anyway, I inspected the gpt.bin of both XT1562 RETEU and XT1562 RETASIA with gpt_parser.py
Turns out: the userdata partition wouldn't suffer from misalignments by flashing a different partition table:
India gpt.bin gpt_parser.py output:
Code:
[-] Partition 42
[-] Partition type GUID: 1B81E7E6-F50D-419B-A739-2AEEF8DA3335
=> Partition type: unknown partition, UNKNOWN
[-] Unique partition GUID: 86E734CA-D096-B657-DA2D-095F241A084A
[-] First LBA: 7634944
=> Disk Offset: 0xE9000000
[-] Last LBA: 7634943
=> Disk Offset: 0xE8FFFE00
[-] Attribute flags: 1152921504606847000, UNKNOWN
[-] Partition Name: userdata
Europe gpt.bin gpt_parser.py output:
Code:
[-] Partition 42
[-] Partition type GUID: 1B81E7E6-F50D-419B-A739-2AEEF8DA3335
=> Partition type: unknown partition, UNKNOWN
[-] Unique partition GUID: 0C44D2CF-AFB9-7EEE-2FAE-03E3E1D02EB8
[-] First LBA: 7634944
=> Disk Offset: 0xE9000000
[-] Last LBA: 7634943
=> Disk Offset: 0xE8FFFE00
[-] Attribute flags: 1152921504606847000, UNKNOWN
[-] Partition Name: userdata
If you're not scared by the above feel free to proceed. The following worked for me, keep in mind that I can't know for sure if this will work out with your setup, so if you follow these instruction, you do so at your own risk:
1. I started out with LPD23.118-10 XT1562 RETEU with locked bootloader - userdata was encrypted.
2. I flashed LPD23.118-10 XT1562 RETASIA (a.k.a. Indian, and the version number is important because the OTA upgrade will only work with that - there was a faster google drive link somewhere I can't find it, sorry, will update the post if someone sends me a link) firmware like described here, but note the crucial difference:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
fastboot erase userdata is missing before the reboot because we want to keep our current settings and apps data that can't be backed up (looking at you org.thoughtcrime.securesms)
3. Boot normally, etc. it will optimise some apps because cache was erased etc. Dual SIM should be enabled now!
4. If you want to pop into the Marshmallow world without waiting till you get OTA notifications, grab the update, place it in the root directory of your SD card, and check for system updates.
5. Wait a long time while it upgrades, boots and optimises.
6. Happily check out your Android version: 6.0 and System version: 25.11.18.lux_retasia_ds.retasiaall.en.03 reteu (yes, apparently it recognises that it's a reteu phone - a little scary but everything is fine for now)
7. ???
8. PROFIT
I already switched my data/voice plan around making use of the Dual SIM ability. It works great and now I pay a couple euros less while keeping my old number! Keep in mind though, you should use two different network providers, if the same provider sees an IMSI try to log in twice poop might get shagged up. (Also, if you use an MVNO, make sure the infrastructure providers they use are also different)
Play safe and happy (dirty) flashing
Edit: fixed link

mxnd said:
...
1. I started out with LPD23.118-10 XT1562 RETEU with locked bootloader - userdata was encrypted.
2. I flashed LPD23.118-10 XT1562 RETASIA (a...
Click to expand...
Click to collapse
From where did you download that LPD23.118-10 XT1562 RETASIA ROM.
I can't find it on filefactory site.

00sand00 said:
From where did you download that LPD23.118-10 XT1562 RETASIA ROM.
I can't find it on filefactory site.
Click to expand...
Click to collapse
Here moto.shreps.fr/?dir=Moto%20X%20Play%20%28lux%29/rom/stock

What should I do if I want to make the same, but with Single-SIM and clean install?

@mxnd
Dude, you rock.
Converted uk x play single to dual sim and everything works. Data intact
Now going for marshmallow
Updated marshmallow India.
So far so good, everything seems ok.

PanOptikum said:
What should I do if I want to make the same, but with Single-SIM and clean install?
Click to expand...
Click to collapse
As far as I can tell, only dual sim phones have gotten a 6.0 update so far. No idea what takes them so long

mxnd said:
Hello everyone, I just upgraded my phone to Dual SIM Marshmallow yesterday while leaving the bootloader intact and without losing any data (as far as I can tell). Yes, this is a dirty flash operation, so proceed with caution.
Click to expand...
Click to collapse
Awesome Job Mate!!!

At the link there is a retasia marshmallow firmware too. Is it not easier to upgrade directly to marshmallow instead of the asian version of lollipop and then to marshmallow with the ota update

Jeso said:
At the link there is a retasia marshmallow firmware too. Is it not easier to upgrade directly to marshmallow instead of the asian version of lollipop and then to marshmallow with the ota update
Click to expand...
Click to collapse
Yeah, I haven't downloaded and/or inspected the gpt partitioning of that. I would assume everything would stay in the same place there too, but verifying with the python script above is probably a good idea. I thought this was the safest route and it worked If anybody experiments, I'll happily update the post.

bablu048 said:
Here moto.shreps.fr/?dir=Moto%20X%20Play%20%28lux%29/rom/stock
Click to expand...
Click to collapse
Is taht the dual sim version? in the code name does not apears "DS"

kamarilla said:
Is taht the dual sim version? in the code name does not apears "DS"
Click to expand...
Click to collapse
yes all indian versions are dual sim.
you can get it from here also https://github.com/motoxplay/stock

Superb popped my tray out and there was a blank got it out
And there's a nice picture sim 2 underneath :good:

Where can I get firmware for asiaretail_pacific?

Excellent guide
I'm following XDA since several years but I never posted.
I followed your guide and with a bit of attention I was able to reflash my Moto X Play from single sim eu to dual sim asia/eu.
I moved from XT1562_LUX_RETEU_6.0.1_MPD24.107-52 (single sim) to XT1562_LUX_RETASIA_DS_6.0.1_MPD24.107-52 (dual sim dual standby).
A check with gpt_parser.py gives same result than on original post, so I decided to try this.
This is the exact command sequence I gave (only differs in the /sparsechunk/ section because it has 9 chunks instead of 7 of the original guide. Note that EU firmware has 8 chuncks and asia has 9 chunks, so be careful and inspect zip package before flashing).
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
Now phone is working, SIM1 is correctly registered and now I have a dual sim phone. I don't have a second sim yet so I can't test, but in the settings there is the additional SIM menu.
Some questions:
* IMEI of SIM2 is zero. Is this a problem with carriers? Is there a way to have an IMEI for SIM2 too?
* Should the phone see the update to MPD24.107-70 or not? Now it is not seeing it (software up to date)
Thank you all for the guide and for the answers.
EDIT: After some hours, the phone stopped detecting SIM1. So I had no SIM working. After some readings I flashed the single sim european software back. I still need to read something to properly achieve this conversion. Every suggestion is appreciated

acehigh1971 said:
I'm following XDA since several years but I never posted.
I followed your guide and with a bit of attention I was able to reflash my Moto X Play from single sim eu to dual sim asia/eu.
I moved from XT1562_LUX_RETEU_6.0.1_MPD24.107-52 (single sim) to XT1562_LUX_RETASIA_DS_6.0.1_MPD24.107-52 (dual sim dual standby).
A check with gpt_parser.py gives same result than on original post, so I decided to try this.
This is the exact command sequence I gave (only differs in the /sparsechunk/ section because it has 9 chunks instead of 7 of the original guide. Note that EU firmware has 8 chuncks and asia has 9 chunks, so be careful and inspect zip package before flashing).
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
Now phone is working, SIM1 is correctly registered and now I have a dual sim phone. I don't have a second sim yet so I can't test, but in the settings there is the additional SIM menu.
Some questions:
* IMEI of SIM2 is zero. Is this a problem with carriers? Is there a way to have an IMEI for SIM2 too?
* Should the phone see the update to MPD24.107-70 or not? Now it is not seeing it (software up to date)
Thank you all for the guide and for the answers.
EDIT: After some hours, the phone stopped detecting SIM1. So I had no SIM working. After some readings I flashed the single sim european software back. I still need to read something to properly achieve this conversion. Every suggestion is appreciated
Click to expand...
Click to collapse
I did exactly the same a few days ago. I flashed the Asia firmware and then I flashed RR (a custom rom) and forced second SIM with the fastboot command and now it looks like this:
(I cropped the IMEI SIM1 out.)
And it's working like this. Currently I'm using only 1 SIM but I tested it with a second SIM and both works.
I got the 1562 (EU/Germany) version.
I hope that helped you!
Sent from my XT1562 using XDA-Developers mobile app

So you didn't have problems of SIM1 not detected?
Is the sim1 working ok?
My question is: probably asia firmware contains a different modem partition and it does not enable all the frequencies of my european phone.

acehigh1971 said:
So you didn't have problems of SIM1 not detected?
Is the sim1 working ok?
My question is: probably asia firmware contains a different modem partition and it does not enable all the frequencies of my european phone.
Click to expand...
Click to collapse
No, SIM1 is working with both SIM cards (congstar and O2).
Hmm, I don't think so, because it worked well for me too, but I can't confirm this 100%.
Sent from my XT1562 using XDA-Developers mobile app

Ok,
I did the procedure again from the beginning. After reboot and android optimization, I removed SIM card from slot 1 and booted again without sim.
Then shutdown, inserted SIM and then powered on. I got a notification that a new sim is present and I can configure it. From then it worked fine with one sim (I only have one at the moment).
Somewhere I read there is a bug with some custom firmware not reading both SIMs, and probably I met this bug also with an original firmware.
BUT ANYHOW, there are some serious drawbacks to this stock firmware replacements:
1) IMEI of SIM2 is 0. I don't know which operators block IMEI 0 and which don't care. Googling for info does not provide meaningful results for my country (IT). But in general this could be a problem, especially if you go abroad and you don't know the details for each operator.
2) OTA do not come if, like in my case, I have a RETASIA reteu mixed device.
There are some clever posts in this thread: http://forum.xda-developers.com/moto-x-play/help/enabling-dual-sim-single-sim-devices-t3225546 where these notes are pointed out, with practical tests.
Based on this, for the moment I decided to go back to RETEU reteu single sim sw... sigh.

He cant go back, the Asia DS one is newer as the RETEU. Only with open Bootloader he can install a older one. (there is a thread in General also.)
Got no Problems with 2 Sims (O2 and german Telekom) with the DS FW on 2 RETEU Play Devices (only with Custom FW )but there is a command to fix it.
On one Device (open Bootloader and out of Warrenty i´m back on older EU FW).
He have to wait on a newer EU FW or open the bootloader (with risks) if he would back to.
(btw.: i read on some Countrys is not legal to use a Sim with no Imei + the second Sim is not detected.)
edit: maybe it would be a good idea to wipe the whole device, and start fresh?

Already reverted to reteu
Assuming you are referring to me (... He can't go back ...), I already switched back to reteu firmware.
I did all these experiments with same build level for both versions (reteu and retasia): MPD24.107-52.
This confirms me 2 things:
* Frankenstein phones like this do not get ota updates (during the time I stayed with retasia I didn't receive upgrade notification (even checking manually). And I should, because there is a new sw for retasia already available (MPD24.107-70).
* If I stay with the same build level, the partition scheme is the same so I can go back and forth between versions, with locked bootloader and without erasing userdata. The benefit in doing this is zero for me at the moment, but this is another story. It was an interesting experiment. I learned a lot.

[Firmware] 8.1 official Moto Z3 Play [BECKHAM]

{
"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"
}
DISCLAIMER
I am not to be held responsible for any of the damage that occurs to your device during this process. You are yourself responsible for any damage done (if) to your device during this process.
REQUIREMENTS
Make sure your device is charged above 80%.
We recommend creating a backup of all your important files before beginning with this process.
HOW TO INSTALL STOCK ROM IN MOTO Z3 Play
Download Moto Z3 Play Stock Firmware from below (in download section).
Install Motorola Driver and ADB Fastboot Driver on your PC.
Now extract stock firmware in ADB Fastboot folder.
Now, turn off your device and boot into bootloader by pressing volume down button +power button simultaneously.
Now, connect your device to your PC via a USB Cable.
Open a command prompt window and type the following commands:
adb fastboot
fastboot flash partition gpt.bin ( not mandatory )
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot erase modemst1 ( not mandatory )
fastboot erase modemst2 ( not mandatory )
fastboot reboot
Click to expand...
Click to collapse
Thanks to Motorola firmwares.
Password:
MotorolaFirmwaresLB
BECKHAM_OPW28.70-22_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
-DRIVE
-AFH

Will this work on the Amazon version?

Hello, it should work

I would be VERY careful about trying to use the image provided here.
I picked up the Z3 today hoping to be able to build TWRP recovery with this image. Using the kernel from this image resulted in a permanently bricked device. It would no longer turn on. At all.
Second Z3, using the provided image's boot.img and only booting boot.img from fastboot... hung the device.
This tells me the linked image here is very likely to be incompatible with many Z3 Play devices.
The version I've tested it with is the US retus software channel version.
As far as I've been able to tell, this image is for French devices only. DO NOT use this image if you cannot confirm it will work by testing the boot image first.
Extract boot.img from the archive and put your phone into fastboot mode. Test it by typing "fastboot boot boot.img" - If your phone hangs at the motorola logo, this firmware WILL BRICK YOUR PHONE.
The Z3 Play has NO FIRMWARE candidates on https://firmware.center - So, I repeat, the firmware linked here is likely NOT compatible with your device.

twelfth said:
I would be VERY careful about trying to use the image provided here.
I picked up the Z3 today hoping to be able to build TWRP recovery with this image. Using the kernel from this image resulted in a permanently bricked device. It would no longer turn on. At all.
Second Z3, using the provided image's boot.img and only booting boot.img from fastboot... hung the device.
This tells me the linked image here is very likely to be incompatible with many Z3 Play devices.
The version I've tested it with is the US retus software channel version.
As far as I've been able to tell, this image is for French devices only. DO NOT use this image if you cannot confirm it will work by testing the boot image first.
Extract boot.img from the archive and put your phone into fastboot mode. Test it by typing "fastboot boot boot.img" - If your phone hangs at the motorola logo, this firmware WILL BRICK YOUR PHONE.
The Z3 Play has NO FIRMWARE candidates on https://firmware.center - So, I repeat, the firmware linked here is likely NOT compatible with your device.
Click to expand...
Click to collapse
This firmware is for XT1929-4 and no mention is made in the topic....

GuzXT said:
This firmware is for XT1929-4 and no mention is made in the topic....
Click to expand...
Click to collapse
The XT1929-4 is what I have and the firmware definitely did not work for me. I tried to build TWRP for the Z3 Play as I have for other devices and it definitely wasn't going to happen with these files. Even if you 'fastboot boot boot.img', it's supposed to boot like normal using the rest of the what is stored on your phone. Instead it only hangs.

there is this https://forum.xda-developers.com/moto-z/development/tool-motorola-ota-link-generator-tool-t3537039
we just have to wait for OTA i guess
also there is this if you google beckham_opw28.70-25_subsidy-default_regulatory-default_cfc.xml.zip but they ask for money
https://firmware.gem-flash.com/index.php?a=browse&b=category&id=19944
search for 1929- on https://firmware.gem-flash.com/index.php?a=browse&b=category&id=2634

Here in free access all the same))
https://mirrors.lolinet.com/firmware/moto/beckham/official/

Has anyone been able to relock the bootloader in a way that passes safetynet. I noticed that phone boots with verity set at log only which fails CTS and I want to go back to stock until Magisk works properly.

driverdis said:
Has anyone been able to relock the bootloader in a way that passes safetynet. I noticed that phone boots with verity set at log only which fails CTS and I want to go back to stock until Magisk works properly.
Click to expand...
Click to collapse
magic works quite well if you patch the boot normally, with check marks.

Willy33 said:
magic works quite well if you patch the boot normally, with check marks.
Click to expand...
Click to collapse
Thanks, this did the trick. I was able to download use the boot.img from the lollinet mirror firmware zip. It does require both force encrypt and verity enabled before patching it or it will boot loop.

---REDACTED---

Will this work on the Moto Z3 (XT1929-17)?

wanb1i said:
Will this work on the Moto Z3 (XT1929-17)?
Click to expand...
Click to collapse
You need a firmware image for your specific device. Check the websites from this thread and see if you can find one specific to your device. Other images could brick your device.
The steps should be the same for every device as far as fastboot flashing goes. But don't use an image for another device

darkdaemon32 said:
You need a firmware image for your specific device. Check the websites from this thread and see if you can find one specific to your device. Other images could brick your device.
The steps should be the same for every device as far as fastboot flashing goes. But don't use an image for another device
Click to expand...
Click to collapse
Found the original vzw firmware on Moto's site.
Thanks!

twelfth said:
The XT1929-4 is what I have and the firmware definitely did not work for me. I tried to build TWRP for the Z3 Play as I have for other devices and it definitely wasn't going to happen with these files. Even if you 'fastboot boot boot.img', it's supposed to boot like normal using the rest of the what is stored on your phone. Instead it only hangs.
Click to expand...
Click to collapse
So I have a Verizon Moto Z3 (Brand New XT1929-17, NO XDA Thread yet) I found the firmware off the Motorola site at this link https://androidfilehost.com/?w=files&flid=279604 (last file). I unzipped it, copied the boot.img to my adb folder and executed fastboot boot boot.img and this is the result:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.622s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.633s
My goal here is to modify a boot.img so I can root with Magisk without unlocking the bootloader. (Verizon devices don't allow unlocking the bootloader)
Any help would be appreciated.

wanb1i said:
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.633s
Click to expand...
Click to collapse
Your bootloader is locked. Being a Verizon device, it's likely not unlockable.
You have to have an unlocked bootloader before you can boot and flash in fastboot.
This is why people buy unlocked devices.

Xt-1929-4 opw 20.70-31
Hi, I have the Moto Z3 Play. This is the updated Firmware that I have on my device. I felt I should share it, just in case anyone else needs its. I also added a couple of simple batch files to the folder that I thought everyone might appreciate.
FlashRoot(Service) - Will automatically flash the phone with the patch_boot.img instead of boot.img. This will flash the rooted version of the boot image that was made with Magisk Manager. (Must be in Fastboot)
Flash - Stock --Will automatically flash the regular boot.img also with all the other stock files to the phone. (Must be in Fastboot)
Credit -
Magisk Manager
Google
Hi, I have the Moto Z3 Play. This is the updated Firmware that I have on my device. I felt I should share it, just in case anyone else needs its. I also added a couple of simple batch files to the folder that I thought everyone might appreciate.
FlashRoot(Service) - Will automatically flash the phone with the patch_boot.img instead of boot.img. This will flash the rooted version of the boot image that was made with Magisk Manager. (Must be in Fastboot)
Flash - Stock --Will automatically flash the regular boot.img also with all the other stock files to the phone. (Must be in Fastboot)
Credit -
Magisk Manager
Google
Android FileHost[https ://drive.google. com/open?id=1KAMijX1W2HQx69mDhZ294tp51vtAoo0E[/URL]

Can someone provide a system dump for Moto Z3 Play..
Edit: Done

Hi, my Z3 play has a Bootloop I tried with hard reset and still not working. It's XT1929-6 dual SIM, can someone help me ? Please

[FIRMWARE][GUIDE] Restoring the Moto E5 Play to Stock Factory State

Stock Android 8.0.0 Factory Firmware
Moto E5 Play (James) xt1921-5
Sprint/Virgin Mobile/Boost Mobile
WARNING: This stock Android 8.0.0 firmware package should not be used in an attempt to downgrade your device to an earlier firmware build. (While downgrading is possible, only the more advanced users should attempt it ) Use this firmware & guide only if your device has never been upgraded beyond Build No. OCP27.91-23. Attempting to downgrade your partition index (gpt.bin) or your bootloader partitions (bootloader.img) can result in a hard-bricked device -- and typically bricked beyond repair. By proceeding further, you are assuming sole responsibility for the integrity and functionality of your device, thus absolving me from any civil liability in the event your device becomes bricked, damaged, or otherwise inoperable.
SPECIFICATIONS:
Android Version: 8.0.0 Oreo
Build No. OCP27.91-23
Kernel Version: 3.18.71
Radio Version: M8920.11.54.11.41R
Security Patch Level: March 1, 2018
APPLICABILITY:
There are any number of reasons to use this restoration guide. If you are running a rooted device with system-based or systemless modifications to your Android OS, and you merely want to return to an unmodified stock configuration, this guide will accomplish that. If your device is soft bricked, stuck in a boot loop or is otherwise malfunctioning from a software standpoint, this guide will repair your phone. Or, perhaps you simply want to return to unmodified stock in order to install an OTA update. Again, this guide is for you.
RESTORATION/FLASHING INSTRUCTIONS:
This guide is written with the assumption that you have at least a rudimentary knowledge of AP Fastboot Mode and basic flashing commands. While this firmware can certainly be installed using RSD-Lite, mFastboot, etc., this guide aims at a basic fastboot installation. This procedure will erase all userdata stored on your device, enables dm-verity (device mapping), and enables default force encryption of the /userdata partition. Please make a backup of any data, files, media, etc. that you want to keep prior to proceeding. This process removes root binaries, BusyBox, root-dependent mods, and restores all OEM and carrier-specific bloatware. This guide also assumes that you have a recent version of the Minimal ADB & Fastboot utilities installed on your PC or laptop, as well as the proper USB device drivers.
1. Download the firmware package from the below link and extract the contents of the archive to your adb/fastboot directory on your PC;
2. Boot your device into AP Fastboot Mode by first powering down your device and then simultaneously holding the Power + Volume Down keys for around 8 seconds, until you see AP Fastboot Mode on your device display;
3. Connect your device to your PC using the OEM supplied or quality-equivalent micro USB to USB syncing cable;
4. Open a command window in the path of your adb/fastboot directory;
5. Enter this command:
fastboot devices
Press Enter/Return
If your device and PC are properly connected, an alpha-numeric string will appear in the command window synonomous to your device serial number;
6. After ensuring a proper connection, execute the following commands:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash dsp adspso.bin
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot erase DDR
fastboot erase cache
fastboot erase userdata
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot oem fb_mode_clear
7. Now reboot your device by entering:
fastboot reboot
Press Enter/Return
Upon reboot, your device should be fully restored to stock Android 8.0.0 firmware, Build No. OCP27.91-23, and your device will be fully capable of installing OTA update packages.
DOWNLOAD LINK:
https://drive.google.com/file/d/1v39JAH7gUjjN5-iR8qPln4WS9Hozq88s/view?usp=drivesdk

Over the next few days, I will be adding threads with firmware packages and restoration instructions for other variants of the Moto E5, including the Moto E5 Cruise & the Moto E5 Plus.

You're awesome, Because I somehow disappeared my radio again. lol. Between the rom and this you've singlehandedly rebuilt my phone

Starkiller2 said:
You're awesome, Because I somehow disappeared my radio again. lol. Between the rom and this you've singlehandedly rebuilt my phone
Click to expand...
Click to collapse
Glad it helped you. I'm in the process of updating this thread to reflect the most current firmware build of OCP27.91-23-3 with the June 1, 2018 security patch level.

MotoJunkie01 said:
Glad it helped you. I'm in the process of updating this thread to reflect the most current firmware build of OCP27.91-23-3 with the June 1, 2018 security patch level.
Click to expand...
Click to collapse
somehow I still messed up. now I'm stuck in airplane mode, with mobile radio stuck to off. I've tried everything, rerooting, different apps, programming menu. I give up. lol. even the stuff I did after I soft bricked it isn't working.

@Starkiller2, I will try to help. Who is your carrier? Your mobile service provider in other words.

MotoJunkie01 said:
@Starkiller2, I will try to help. Who is your carrier? Your mobile service provider in other words.
Click to expand...
Click to collapse
Boost mobile. Thanks for the help

Starkiller2 said:
Boost mobile. Thanks for the help
Click to expand...
Click to collapse
Ok. Try this. From the firmware package above, extract two files to your adb/fastboot directory -- NON-HLOS.bin and fsg.mbn. Boot your device into fastboot mode, connect to your PC, and open a command window in your adb/fastboot path. Execute these commands in order:
fastboot oem fb_mode_set
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot oem config fsg-id boost
fastboot oem config carrier boost
fastboot erase DDR
fastboot erase cache
fastboot oem fb_mode_clear
Reboot by entering:
fastboot reboot
This process configures your radio firmware partitions for Boost Mobile, reinstalls your radio firmware, and resets all network configurations to the factory default settings. This will typically fix problems with the cell radio, signal strength issues, domestic roaming, no cell signal, etc. Let me know. We can try some different things if need be. Whatever your issue is caused from, just remember it is fixable. Frustrating for sure, but fixable.

MotoJunkie01 said:
Ok. Try this. From the firmware package above, extract two files to your adb/fastboot directory -- NON-HLOS.bin and fsg.mbn. Boot your device into fastboot mode, connect to your PC, and open a command window in your adb/fastboot path. Execute these commands in order:
fastboot oem fb_mode_set
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot oem config fsg-id boost
fastboot oem config carrier boost
fastboot erase DDR
fastboot erase cache
fastboot oem fb_mode_clear
Reboot by entering:
fastboot reboot
This process configures your radio firmware partitions for Boost Mobile, reinstalls your radio firmware, and resets all network configurations to the factory default settings. This will typically fix problems with the cell radio, signal strength issues, domestic roaming, no cell signal, etc. Let me know. We can try some different things if need be. Whatever your issue is caused from, just remember it is fixable. Frustrating for sure, but fixable.
Click to expand...
Click to collapse
No go. Whatever it is its causing the mobile radio power switch in the programming menu to keep reverting to the off position. if I try turning it on and running a ping it switches right back off.

Starkiller2 said:
No go. Whatever it is its causing the mobile radio power switch in the programming menu to keep reverting to the off position. if I try turning it on and running a ping it switches right back off.
Click to expand...
Click to collapse
Let me research this a bit. Are you running the latest OTA update? Build OCP27.91-23-3?

yeah I flashed the stock firmware this morning and took it over wifi.

Starkiller2 said:
yeah I flashed the stock firmware this morning and took it over wifi.
Click to expand...
Click to collapse
Ok. I think I know the issue. Repeat the entire firmware restoration process again, just like you done previously, except this time skip gpt.mbn, adspso.bin and bootloader.img. Upon reboot your cell radio should work.

Still nothing. Except now it keeps trying to make me take the update again.
---------- Post added at 09:01 AM ---------- Previous post was at 08:59 AM ----------
Lol. I have a third party warranty thank God. It covers it still. Maybe it's a write off.
Still a negative. now whenever I take the update and try the firmware without the pieces you instructed, it just tries to make me update again. But recovery is working again

Starkiller2 said:
Still nothing. Except now it keeps trying to make me take the update again.
---------- Post added at 09:01 AM ---------- Previous post was at 08:59 AM ----------
Lol. I have a third party warranty thank God. It covers it still. Maybe it's a write off.
Still a negative. now whenever I take the update and try the firmware without the pieces you instructed, it just tries to make me update again. But recovery is working again
Click to expand...
Click to collapse
When it prompted you to accept the OTA, did you accept and install it? Try that and see what happens. Yours is beginning to sound like a hardware issue.

yeah I accepted it every time. lol. Im thinking I may need to just replace it. I had issues with data when I first rooted it but that was my fault and I had it working again. Thank you for all your help.

@MotoJunkie01 Do you happen to have your hands on the Retus or Unlocked firmware for this model? (Moto E5, Play)

maxmotos said:
@MotoJunkie01 Do you happen to have your hands on the Retus or Unlocked firmware for this model? (Moto E5, Play)
Click to expand...
Click to collapse
Give me the exact model number and I'll check.

The latest build is up on my Moto E5 Play Stock ROM thread -- OCPS27.91-23-3
https://forum.xda-developers.com/mo...tock-android-8-0-0-rom-moto-e5-t3806530/page2

Works with XT1944-3?
Was wondering if any of the above stock roms would work with xt1944-3 variant of Moto E5
Can you help me please? Thanks in advance

amn92 said:
Was wondering if any of the above stock roms would work with xt1944-3 variant of Moto E5
Can you help me please? Thanks in advance
Click to expand...
Click to collapse
Who is your mobile provider? I have some firmware for the xt1944-3 but I believe it's the retail. Just added xt1944-3 firmware in my thread. https://forum.xda-developers.com/moto-e5/how-to/firmware-moto-e5-xt1944-4-dual-sim-t3820901

Manually update Z3 Play to Pie

Story: I bought US version Z3 Play open market model from B&H. I could unlock the bootloader according to Motorola Developer site, but I encountered problem to root and I have struggled half day to make root done from booting TWRP to patching boot.img.
Eventually, I bit the bullet and make a step up to update to Pie bu downloading RETAIL ROM instead of RETUS. This time I patched the updated boot.img and I got success.
Prerequisite:
Full RETAIL Pie ROM
https://mirrors.lolinet.com/firmware/moto/beckham/official/RETAIL/
Bootloader unlocked
It's recommended to flash in Linux (I used Ubuntu) as I didn't have luck with Windows
Main battery should be full and supplied battery module should be at least 50% (you can charge battery module with 9V PD charger)
Some typing (all fastboot commands typed as ./fastboot)
Be aware some components will be flashed in b partition. Failure to do it will cause bootloop
./fastboot erase userdata is optional, but it is recommended to avoid unexpected trouble
Steps:
1. Download the Pie ROM and extract to somewhere you know (you can drag and drop the file into terminal window).
2. Copy the boot.img to the phone and let Magisk Manager to patch it, and copy the patched_boot.img to where you can locate.
3. Backup your personal data just in case
4. Prepare USB C cable
5. Enter bootloader. Turn the phone off, press and hold both volume down and power button together, and connect you phone to host computer. (You phone should show USB conmected)
6. Enter the following commands
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
Click to expand...
Click to collapse
7. After the phone has booted up, wait until it completed the update process. Now you have to go back to bootloader for rooting.
fastboot flash boot patched_boot.img
Click to expand...
Click to collapse
Booting process takes much longer, but it's one process until you update ROM and regain root again.
8. Run Magisk Manager to check root status
This is what I did to manually update to Pie and root it. Your milage may vary.
Good luck

Will this work on the amazon version?

CrimsonSaber5G said:
Will this work on the amazon version?
Click to expand...
Click to collapse
If the bootloader can be unlocked, it's likely

Will this still allow you to get OTAs or will it break it?

crazyjimbo said:
Will this still allow you to get OTAs or will it break it?
Click to expand...
Click to collapse
I used to flash stock on my rooted z3play, then take the OTA . For some reason that's not possible anymore. I really need the latest OTA to sideload it. I tried many different roms 8.1 and 9.0

Just installed June security patch (ALI)

Hey, I just installed June security patch on my Moto G6 and I gotta say this build is super smooth.
I’m getting more than 5-6hrs of SOT and yes DIGITAL WELLBEING IS A SYSTEM APP NOW.
I downloaded the latest firmware from here : https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/
And flashed it via RSD Lite.
Don’t forget to hit thanks

aaryan1596 said:
Hey, I just installed June security patch on my Moto G6 and I gotta say this build is super smooth.
I’m getting more than 5-6hrs of SOT and yes DIGITAL WELLBEING IS A SYSTEM APP NOW.
I downloaded the latest firmware from here : https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/
And flashed it via RSD Lite.
Don’t forget to hit thanks
Click to expand...
Click to collapse
Can I install this patch with Android 9 OTA with Root?

bradz28 said:
Can I install this patch with Android 9 OTA with Root?
Click to expand...
Click to collapse
No, unfortunately not. This is a full wipe/fresh install only. The same rooting method works, but it will have to be a fresh install.

xfrobex said:
No, unfortunately not. This is a full wipe/fresh install only. The same rooting method works, but it will have to be a fresh install.
Click to expand...
Click to collapse
Ok, thanks

Hello, I upgraded my phone through CMD commands in fastboot folder, but now I can't hear nor be heard in calls. I tried already intalling the NON-HLOS.bin from Stock ROM RETAIL OPSS27.104-92-4 and tried with the NON-HLOS.bin from the Sotck ROM from my region OPENMX OPSS27.82-87-8 too, but it didn't work.
Tried turning the phone on Secure Mode to see if it was a problem related with an app but it wasn't the case, also tried couple of times doing factory reset, but it gave the same result.
I was on the RETAIL PPSS29.55-34-1 with NON-HLOS.bin from OPENMX OPSS27.82-87-8 and the calls were fine. Could someone help me, please?
I did all of above with locked bootloader.
Edit:
Now I unlocked bootloader to downgrading to RETAIL PPSS29.55-34-1 with NON-HLOS.bin from OPENMX OPSS27.82-87-8, and it didn't work so I relock bootloader.

mariconojoda said:
Hello, I upgraded my phone through CMD commands in a fastboot folder, but now I can't hear and can't be heard in calls. I tried already intalling the NON-HLOS.bin from Stock ROM RETAIL OPSS27.104-92-4 and tried with the NON-HLOS.bin from the Sotck ROM from my region OPENMX OPSS27.82-87-8, but it didn't work.
Also tried turning the phone on Secure Mode to see if it was a problem related with an app but it wasn't the case, also tried couple of times doing factory reset, but it gave the same result.
I was on the RETAIL PPSS29.55-34-1 and the calls were fine. Could someone help me, please?
All of above with locked bootloader.
Edit:
Now I unlocked bootloader to downgrading, I donwgrade to RETAIL PPSS29.55-34-1 with NON-HLOS.bin from OPENMX OPSS27.82-87-8, it didn't work so I relock bootloader.
Click to expand...
Click to collapse
As you unlocked the bootloader your warranty is gone, plus I didn’t try with CMD commands, I used RSD Lite, so maybe try a fresh install again if problem persists.

aaryan1596 said:
As you unlocked the bootloader your warranty is gone, plus I didn’t try with CMD commands, I used RSD Lite, so maybe try a fresh install again if problem persists.
Click to expand...
Click to collapse
It don't recognize the device
Nevermind I just needed to connect the device in another port, also now the calls work thank you @aaryan1596

How do I install this without RSDLite? The program doesn't work for me at all (v5.7 on Win10), and I do not fully understand how to use fastboot/batch files to install the unpacked .zip file. Thank you for your help.
Edit: I was able to easily install this using Minimal ADB and Fastboot. Simply extract the contents of your .xml.zip file to your Minimal ADB and Fastboot installation folder. Boot your phone into fastboot mode (volume+power down) and copy and paste these commands (you can copy and paste the entire block and they will run sequentially):
Code:
fastboot erase userdata
fastboot erase cache
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase DDR
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash oem oem.img
fastboot flash logo logo.bin
fastboot flash dsp adspso.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot erase cache
fastboot reboot
Using this method I was able to easily install to latest version onto my XT1925-6, which shipped with Oreo.

Is there any different between ROM with february security patch and this one (june security patch)?

Has anyone in the UK been able to download this update via system updates yet?

um.z said:
Has anyone in the UK been able to download this update via system updates yet?
Click to expand...
Click to collapse
Just downloading via system updates, channel: retgb.

Well, I received the June 1, PPS29.55-37-4 OTA (retgb channel) at around 9:40pm (Mon 5th Aug, UK time). It took 12 minutes to download the 818.6Mb package over a 4G connection, and a further 26 minutes to install it.
Everything went without a hitch, and all seemed perfectly fine afterwards...
...however, having previously read about the problems reported here on XDA and on the Lenovo/Motorola community support forum regarding recent Pie updates, I decided to perform a factory wipe/reset immediately after the update. A tiresome chore to be sure, having to set everything up again aftwards, but it just seemed the prudent thing to do.
So now, some 19 hours later, my G6 is still working perfectly, with no obvious problems, and it does certainly feel smoother and more responsive than it's predecessor, PPS29.55-24, which I received at the end of March. And, yep, this new 'build' includes Google's Digital Wellbeing app integrated at the system level, so I guess that's something new to tinker around with.
Anyhow, just some thoughts regarding my experience of updating to this latest version of Pie.
Rgrds,
Ged.

test