Database Info

Cannot flash stock recovery.img... please help!

Is unlocking your bootloader a prequisite to flashing recovery.img? I have (from what I've gathered) a soft bricked XT 1032, and I forgot which Lollipop version it was running (I'm a loser, I know).
I vaguely remember seeing 5.0.1 . Less likely, it could have been 5.0.2 as well, but less likely. And I'm almost sure it was not 5.1 (I would have remembered).
Anyway, since I did not want to unlock the bootloader (I have still not given up on recovering my data as I did not back them up because of the loser that I am), I did not try flashing a custom recovery like TWRP, and instead tried:
- flashing the GPE recovery.img. I got the partition error (cannot erase).
- flashing gpt.bin, got Preflash vaidation failed
I repeated these steps with 5.0.2 files, and got the same results.
Could this be all because my bootloader is not unlocked? Please tell me that I don't HAVE to unlock bootloader. Of course, I have never tried rooting my phone either. I was running pure OTA stock when my phone suddenly stopped booting up, and went into a boot loop.

You have to unlock the bootloader.

n0ts0smart said:
You have to unlock the bootloader.
Click to expand...
Click to collapse
Ok, so I unlocked BL. I did not really get a clean unlocked message. But now in BL menu, it says in yellow, "Device is UNLOCKED. Status Code: 3". I checked some posts about it, and while ideally Status Code should be 1 (or 0?), a 3 is not necessarily bad. Is that true?
Anyway, I still cannot flash anything into it. I'm mostly getting the "Preflash validation failed" error, or in some cases, the "Failed to erase partition" error.
Am I doomed?

Don't worry. Code 3 is fine. Have you tried to flash custom recovery? Unlocking bootloader is the most time consuming part of getting root. No reason stopping now.
But no your not doomed. Moto pretty difficult to brick IMO. It can be done but you have to mess up pretty bad
---------- Post added at 04:29 AM ---------- Previous post was at 04:07 AM ----------
Go to the TWRP thread and download the recovery image for an XT1032. Then through fastboot flash the recovery image you got from the twrp thread. Let's see how that goes. A working recovery is the goal. You can't do much without one.
The last thing you want to do though is flash random files though so make sure the twrp you download is the one for your phone.
If you need me to be more specific just pm me.
btw long ago I was reluctant to root my device but it turned out to be the best thing I ever did. No warranty means no downside if you ask me. And at this point as I said why stop now?

n0ts0smart said:
Don't worry. Code 3 is fine. Have you tried to flash custom recovery? Unlocking bootloader is the most time consuming part of getting root. No reason stopping now.
But no your not doomed. Moto pretty difficult to brick IMO. It can be done but you have to mess up pretty bad
---------- Post added at 04:29 AM ---------- Previous post was at 04:07 AM ----------
Go to the TWRP thread and download the recovery image for an XT1032. Then through fastboot flash the recovery image you got from the twrp thread. Let's see how that goes. A working recovery is the goal. You can't do much without one.
The last thing you want to do though is flash random files though so make sure the twrp you download is the one for your phone.
If you need me to be more specific just pm me.
btw long ago I was reluctant to root my device but it turned out to be the best thing I ever did. No warranty means no downside if you ask me. And at this point as I said why stop now?
Click to expand...
Click to collapse
Thanks for the encouraging words @n0ts0smart. I have already tried flashing both stock, and now custom (TWRP) recovery images. I keep getting the "Failed to erase partition... Failed to flash partition..." error regardless of the recovery image I try to flash. I have tried flashing partition gpt.bin too, and that gave me the "Preflash vaidation failed" error.
I am at my wit's end, I don't where to go from here. Any help will be much appreciated.

Just so we don't get ahead of ourselves, when you are at the bootloader screen what version does it say? Right below the "Fastboot flash" text?
---------- Post added at 07:24 PM ---------- Previous post was at 06:54 PM ----------
Also are you using fastboot or moto fastboot (mfastboot). I will say in the past I have had a few problems when not using mfastboot. See this link and it goes into some detail. http://mark.cdmaforums.com/MotoX-mFastboot.htm

n0ts0smart said:
Just so we don't get ahead of ourselves, when you are at the bootloader screen what version does it say? Right below the "Fastboot flash" text?
---------- Post added at 07:24 PM ---------- Previous post was at 06:54 PM ----------
Also are you using fastboot or moto fastboot (mfastboot). I will say in the past I have had a few problems when not using mfastboot. See this link and it goes into some detail.
Click to expand...
Click to collapse
Bootloader version is 41.1A. And yes, I am using mfastboot. I will admit though that in the beginning I was using fastboot. But I never got to the part where I would flash large files, so I'm not sure if that is the cause of my trouble. The results have been same with both fastboot and mfastboot for the steps that I have performed.
I really appreciate your help @n0ts0smart, you are the sane voice in my life right now.

Hi
What firmware did you have before flashing the recovery?
Gpe or stock motorola?
You can't flash a gpe recovery in a stock firmware or viceversa, is always going to show an error.
The best thing is flash the 5.0.2 or 5.1 retail firmware or gpe firmware but you have to flash all the files not just the recovery and gpt.bin
Also when you flash 5.1 it upgrades your bootloader to 41.1a so maybe you had 5.1
Hope this helps you

samuelcr93 said:
Hi
What firmware did you have before flashing the recovery?
Gpe or stock motorola?
You can't flash a gpe recovery in a stock firmware or viceversa, is always going to show an error.
The best thing is flash the 5.0.2 or 5.1 retail firmware or gpe firmware but you have to flash all the files not just the recovery and gpt.bin
Also when you flash 5.1 it upgrades your bootloader to 41.1a so maybe you had 5.1
Hope this helps you
Click to expand...
Click to collapse
Thanks @samuelcr93, it actually helps. What you say makes sense. If 41.1A is the 5.1 bootloader, then I must have had 5.1 right? I know I got on the 5 sometime early this year, then I took whatever Motorola offered OTA. I must have thaken 5.1 and I don't remember for sure.
My phone came with 4.2 from the factory, I remember taking 4.4 OTA, then 5 OTA. I have never manually upgraded to any modified version, my phone isn't even rooted. Clearly I was confused about the version, I must have the retail version all the way through.
I am going to find the retail 5.1 and see if that works.

Your welcome, we are here to help
Yes probably you updated to 5.1 and that's why you have that bootloader.
I think flashing stock will fix everything, please let me know if it worked.

I might be wrong on this but I believe taking the ota soak test would also leave you with that version of bootloader. I am reluctant to give advice on something that could potentially put you in a worse position.
With that being said I would download the factory L firmware and try to flash it. If you go that route you mightl still get errors on the motoboot and/or gpt flash command. I would flash the rest or just omit those two all together and flash everything else.

samuelcr93 said:
Your welcome, we are here to help
Yes probably you updated to 5.1 and that's why you have that bootloader.
I think flashing stock will fix everything, please let me know if it worked.
Click to expand...
Click to collapse
I'm on 5.0.2 and I have 41.1A bootloader. so this can't be right
Sent from my Moto G using Tapatalk

bublz654 said:
I'm on 5.0.2 and I have 41.1A bootloader. so this can't be right
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
Dont worry 5.0.2 is compatible with 5.1 bootloader, so it wont be a problem.
Maybe when you tried to flash gpt.bin it upgraded the bootloader.
Is your phone working know?

samuelcr93 said:
Dont worry 5.0.2 is compatible with 5.1 bootloader, so it wont be a problem.
Maybe when you tried to flash gpt.bin it upgraded the bootloader.
Is your phone working know?
Click to expand...
Click to collapse
you got the wrong person [emoji14] look at my name
Sent from my Moto G using Tapatalk

bublz654 said:
you got the wrong person [emoji14] look at my name
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
lol youre right sorry bro

samuelcr93 said:
Your welcome, we are here to help
Yes probably you updated to 5.1 and that's why you have that bootloader.
I think flashing stock will fix everything, please let me know if it worked.
Click to expand...
Click to collapse
n0ts0smart said:
I might be wrong on this but I believe taking the ota soak test would also leave you with that version of bootloader. I am reluctant to give advice on something that could potentially put you in a worse position.
With that being said I would download the factory L firmware and try to flash it. If you go that route you mightl still get errors on the motoboot and/or gpt flash command. I would flash the rest or just omit those two all together and flash everything else.
Click to expand...
Click to collapse
@n0ts0smart did you mean the factory Lollipop firmware? Pardon me, I'm a noob and still learning the lingo. If yes, what version of Lollipop would you suggest?
@samuelcr93 Thanks for your suggestion. I found what I think is the 5.1 factory firmware linked here. The instructions to flash assume a working phone, I think, and I'm not sure how to flash it to a phone that wouldn't boot up, or let me flash recovery.img. I thought installing a working recovery.img was the first step before I could do anything meaningful. Hence my post title.
The GPE firmwares I have found (.xml.zip format) have the files recovery.com, motoboot.img, boot.img, gpt.bin, etc. The stock firmware I found at the link above has only boot.img in the root folder. That is the only file I see that I can flash manually. I don't know if I should flash it and risk bricking my phone totally. On the other hand, I am so desperate that I am ready to try anything with even small odds of success.
If you know how to flash this firmware, can you please tell me how? The only tool I have that I can use is the mfastboot. I have ADB but I can't use it. I cannot boot into recovery or flash any kind of recovery image it seems. Are there any other tools that could be useful?

Dont worry im going to help you until your phone is 100% working :good:
If you can boot in fastboot mode then no problem
the firmware that you posted is 5.1 but you have to flash it with a custom recovery so we are not going to use it.
i found the 5.1 US retail here https://mega.nz/#!uwR2wYAI!91LHxqsBFTxZ0U7s8Pzxt5l3EUhvpABZ7jC4Cwv9DUE
Also download mfastbootv2 here https://www.dropbox.com/s/nlbrn71wfqyup4u/mfastboot-v2.zip?dl=0
now to install it follow this steps:
1. extract the 5.1 retail firmware
2. extract mfastboot into the same folder of retail
3.put the phone in fastboot mode and connect it
4. open Command prompt in the folder (shift + right click and select "open command window here" )and run the commands:
mfastboot flash partition gpt.bin
mfastboot reboot-bootloader
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
it should take 10-15 minutes to boot
if everything goes well now your phone will work normally :highfive:
please let me know if it worked

samuelcr93 said:
Dont worry im going to help you until your phone is 100% working :good:
If you can boot in fastboot mode then no problem
the firmware that you posted is 5.1 but you have to flash it with a custom recovery so we are not going to use it.
i found the 5.1 US retail here
:
:
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
it should take 10-15 minutes to boot
if everything goes well now your phone will work normally :highfive:
please let me know if it worked
Click to expand...
Click to collapse
Ok, I downloaded the 5.1 factory firmware and mfastboot from your links, :good:thanks for those. I followed your instructions, and when I started issuing commands, I got errors starting with the very first one. This is what I got...
{
"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"
}
I gotta say, this is a new one for me. While it didn't work before, whenever I tried this step before, I had invariably got the "Preflash validation failed" error. This is the first time I'm seeing this error. Progress? I'm not so sure.
The second command to reboot did not boot into to the bootloader menu, it just turned off the phone. So I started it back up in bootloader mode. Starting with flash motoboot, I started getting "failed to erase partition" error...
... until the last command, when I felt it didn't make sense to keep going. I'm not sure what to do at this point.
Can't thank you enough for all you're help.

Mmm can you send me a picture of the phone un fastboot mode?
Sent from my XT1032 using Tapatalk

samuelcr93 said:
Mmm can you send me a picture of the phone un fastboot mode?
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Well, I didn't take any pictures of the phone when I tried your instructions. Let me do it again, and I'll get pictures of the phone.

A Noob's Guide to upgrade Moto X Play to Marshmallow ;)

Before i begin, i would like to state that none of the files belong to me, they have been uploaded or provided by someone or other over the internet and i have given credit wherever it is due. If i forget somewhere and please lemme know, I'll fix it.
Note: This is tested only on Moto X Play XT1562 Indian version only. Others use this guide at their own risk. Currently Calls/Data do not work in X1562 as you loose the modem files on upgrade and flashing them back has no effect
First, Lets download the stuff we need at hand:
1) Stock Brasilian Firmware drive.google.com/open?id=0Bx1aljTBgTbATE9ISmNYZ3h2UGs From Yuri Martins @ androidpit.com
2) The Marshmallow update. https://drive.google.com/open?id=0B-MLCAZmmekxb2hOa3ppWTBFRjQ from estanenmi @ XDA
Steps:
1)Now Reboot in fastboot mode by turning off phone and turning it on by holding volume down and power button. Connect to PC, open the command prompt in ADM folder by using shift+right click on ADB folder and selecting open command prompt option.
2)Copy past all the line below as it is in the command prompt. Sit back and relax. It will take around 5 minutes.
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
3) Restart the phone, it will have Brasilian firmware. Go through the initial set up and connect to PC to copy the marshmallow update file in phone directory.
4) Again restart the bootloader of phone by turning it off and turning on by holding the volume down and power button. Here select the recovery option. It will show a dead android pic, press power button and quickly tap volume up. You will be in the stock recovery. There select the install update from SD card option. Select the update file and install. Beware it will take a lot of time and it would appear stuck at patching or verifying files (can't remember which one ) but dont worry, its normal. Once it is done, restart the phone and enjoy the yummy marshmallow.
P.S: Sorry if i missed any instructions, i know the community here will help out others. I was in a bit of hurry, getting very late for bed, will add more instructions and pics tomorrow.
Adios

Mods, please edit the title to : A Noob's to upgrade Moto X Play to Marshmallow

antisocialbratt said:
Mods, please edit the title to : A Noob's to upgrade Moto X Play to Marshmallow
Click to expand...
Click to collapse
Plz upload TWRP backup if possible

Will do that once i have a stable build running. Having trouble with getting sim card detected. I think i need to get the correct modem files for Indian version. Trying to find out correct files for the Dual Sim.

antisocialbratt said:
Will do that once i have a stable build running. Having trouble with getting sim card detected. I think i need to get the correct modem files for Indian version. Trying to find out correct files for the Dual Sim.
Click to expand...
Click to collapse
Yes you have to flash indian modem files... Just flash modem files of retail india firmware

Dont have them and cant find them. Can anyone share the files or upload them to their google drive. They are hardly 40mb, dont wanna download whole indian firmware of 1.2 gb for that :/

antisocialbratt said:
Dont have them and cant find them. Can anyone share the files or upload them to their google drive. They are hardly 40mb, dont wanna download whole indian firmware of 1.2 gb for that :/
Click to expand...
Click to collapse
Here you go

droider007 said:
Plz upload TWRP backup if possible
Click to expand...
Click to collapse
pls upload twrp backup please

Please upload twrp backup by any indian for indian version ... Thnks in advance

Is it multilingual?
Envoyé de mon XT1562 en utilisant Tapatalk

Has anyone tested this procedure on a Canadian xt1563?

I managed to save the modems upto brasilian rom upgrade. Lets see if i can manage to get them all the way through the end till marshmallow.

Hii
---------- Post added at 12:53 PM ---------- Previous post was at 12:49 PM ----------
Hey I am using moto x play Indian Version. Can it upgraded to 6.0? What about warranty?

flash original brazilian firmware with rsd lite then update via stock recovery to marshmallow.
you doesnt need unlocked bootloader

Unable to get the sim to work in Marshmallow for Indian Moto X Play. Here are my findings. Could be useful for the tinkerers .
1) Install Indian ROM>Brasil ROM(no Sim)> Marshmallow (No Sim.)>Flash Indian modem = No Sim
2) Install Indian ROM> Brasil ROM without Brasil Modems (Sim works)> Marshmallow (No Sim)> Flash Indian modem = No Sim
3) Install Indian ROM>Brasil ROM> Flash Indian modem = No Sim

OK, so from everything I have read, this does NOT work correctly with the XT1562, in that modems do not work with this method, and thus no data or calls/sms. Should this not be given a big massive warning in the first post?
S

TheBishopOfSoho said:
OK, so from everything I have read, this does NOT work correctly with the XT1562, in that modems do not work with this method, and thus no data or calls/sms. Should this not be given a big massive warning in the first post?
S
Click to expand...
Click to collapse
Done that. Thanks for pointing it out. Actually when i created the thread, I did not put my sim card in the phone thus had no idea about it. Its a shame though that everything else works flawlessly.

antisocialbratt said:
Unable to get the sim to work in Marshmallow for Indian Moto X Play. Here are my findings. Could be useful for the tinkerers .
1) Install Indian ROM>Brasil ROM(no Sim)> Marshmallow (No Sim.)>Flash Indian modem = No Sim
2) Install Indian ROM> Brasil ROM without Brasil Modems (Sim works)> Marshmallow (No Sim)> Flash Indian modem = No Sim
3) Install Indian ROM>Brasil ROM> Flash Indian modem = No Sim
Click to expand...
Click to collapse
Did you used the method with four steps to change the modem?
Like:
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
Anyway think twice before upgrading with this method because usually on motorola phones you can't simply downgrade the firmware, many users in other forum sections faced some soft or even hard bricks trying to downgrade ( mainly bootloader and/or gpt )

Great, thanks. Ive been burned before a few times and left with expensive paperweights for phones from not reading all the comments and blindly updating. I make sure I know what Im heading into before flashing!

So... is anybody able to use his/her sim in europe (germany etc.) with this (brazilian) firmware with or without flashing the modem ?

AUSTRALIAN XT1572 guide to restore stock to get offical OTA 6.0 update

DISCLAIMER - if you have never rooted or flashed a phone in the past, please stop reading now. Don't even try this, you will probably brick your phone. This process complete replaces all OS components on your phone which can be hard to reverse if you don't know what you are doing. Proceed at your own risk! Backup and have a few roms handy to flash in case you mess up if the guide does not work for you. Make sure you have plenty of battery life before beginning.
This is a guide to restore to stock a Retail Asia (Australian Vodafone) Moto X Style XT1572 single sim phone.
I rooted and then flashed the EU single sim version rom of 6.0 a while ago, but now I wanted to go back to stock. Here is guide how. You will need your bootloader unlocked and developer mode on for USB debugging.
I believe the original Stock OS for the Retail Asia single sim Moto X style was 'X_Style_XT1572_CLARK_RETASIA_5.1.1_LPH23.116-18.1'. That is version 23.116-18.1. Retail Asia, NOT dual sim. The only reason to do this is you have an Australia/ Retail Asia handset and you flashed another rom on to it and want to go back to the Retail Asia single sim OTA update (Australian vodafone). If you have not messed with your phone you should not need to do this. But you could download the OS image as a future backup in case you ever want to back original stock rom the phone shipped with.
Google drive link - 'X_Style_XT1572_CLARK_RETASIA_5.1.1_LPH23.116-18.1 (1.4gb)
Once you have downloaded the zip, decompress it to a folder. Then using Command prompt or Terminal navigate to the folder. Make sure you have fastboot or mfastboot running properly (not sure why you need to use mfastboot but some do), boot in to the bootloader and beginning flashing the individual components of the zip file.
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 flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
Once you reboot the phone you should be running the completely stock rom the phone come with. It will remove root and any custom recovery you might have installed. It will not relock the bootloader.
To get the OTA you need to be on the stock rom and NOT rooted. Once you reboot within seconds you should get an update notification to download the new 24.11.20 Android M 6.0 update. It is about 640mb.
I hope this helps.

Thanks
Was wondering when they would release the official update for retasia
Have reverted back to stock to download the OTA and also captured the OTA for single sim retasia. The version number on this is slightly newer than the Europe and US versions I have been using
edit: Link to retasia MM
https://drive.google.com/file/d/0B4G7mEPBaNoHckxCWWxnY0dzaVU/view?usp=sharing

Awesome! Thank you @Sensation_NZ. I tried to capture the OTA but for some reason my adb would flash but not rewrite anything from the device back. I have grabbed a copy for future use.

wondering if all Australian X Style handsets are Asian? or EU?

Thanks for the post... Just wondering if you could help me, where could I find the modem for the Australian version? Thank you

swifteagle said:
Thanks for the post... Just wondering if you could help me, where could I find the modem for the Australian version? Thank you
Click to expand...
Click to collapse
Never mind, it is included. "fastboot flash modem NON-HLOS.bin" . Thank you very much for this post, life saver!

How did you capture the OTA?

Will this work for dual sim??

Great .. My 1st BootLoop ..
I followed this to the T .. And now it doesn't boot ...
Anyone know how to fix this so it works again, like back to Stock that works.?

I think you flashed Lolipop.
The same way as here:
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
Don't copy&paste; read, think & retype, download newest 6.x.x for your model, check how many sparsechunks it has(9,10,12?). @Lethal_1

[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

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

I know I'm not the only one who has been having trouble finding the stock firmware for the Moto e5 play xt1921-3 MetroPCS/TMobile variant, code named James, that wasn't posted by @MotoJunkie01 and therefore blocked and undownloadable.
So thanks to @HPLazerJetPrinter1012 who was kind enough to find it on XDA in another section and thanks to @timjames474 for posting it in that thread....
VERY IMPORTANT IMHO THAT YOU BACKUP YOUR IMEI INFORMATION AS SOON AS YOU ROOT YOUR DEVICE, PREFERABLY BEFORE FLASHING A CUSTOM ROM. GOING FROM CUSTOM OREO BACK TO STOCK CAN EASILY ERASE ALL YOUR PHONES IMEI INFO MAKING VOLTE AND 4G AND PHONE INOPERABLE. HAPPENED TO ME AND IT WAS A HUGE P.I.T.A. TO FIX.
Download Links
JAMES_T_OCP27.91-51-4_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip / MIRROR
This is the newest (at least at the time of post) update, dated Oct 1, 2018
Instructions to revert back to stock firmware and make it so that you can get OTA updates again:
To install, extract the zip file in your adb/fastboot directory and then make sure you are properly connected to your computer by running the command
Code:
fastboot devices
Then, once you confirm you are properly connected, just run the following fastboot commands one line at a time, making sure spelling is correct (or copying and pasting to ensure proper spelling):
Code:
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 flash system system.img_sparsechunk.4
fastboot erase DDR
fastboot erase cache
fastboot erase userdata
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot oem fb_mode_clear
After this is complete, simply reboot your device, and as long as you did everything right, you should be back on stock firmware with the ability to receive OTA updates.
Flashing a stock recovery,unencrypting your phone, or rooting will make OTA fail, so i recommend waiting to do those things until you are fully updated (unless you don't care about the latest build).
Just to cover my ass, i had nothing to do with the making of these files and I am simply posting well known information for newer users to help them get back to stock.
Therefore, i claim no responsibility for any damage or bricking of your device.
Have a good day friends and if I helped you out, a 'thanks' would be appreciated :good:

Thanks for posting this. I was actually going to upload it myself. You save me from having to do the work

weakNPCdotCom said:
Thanks for posting this. I was actually going to upload it myself. You save me from having to do the work
Click to expand...
Click to collapse
Not a problem.... I actually found most of the firmwares that MotoJunkie01 had posted, I might repost his firmware post (copy and paste) and replace the links after i upload them to my own Gdrive, when I have time....

AesopRock127 said:
Not a problem.... I actually found most of the firmwares that MotoJunkie01 had posted, I might repost his firmware post (copy and paste) and replace the links after i upload them to my own Gdrive, when I have time....
Click to expand...
Click to collapse
sweet. sounds great man. thank you

NM connection working now

https://mirrors.lolinet.com/firmware/moto/ look here for firmware and make sure its correct one and up to date before flashing it.

AesopRock127 said:
I know I'm not the only one who has been having trouble finding the stock firmware for the Moto e5 play xt1921-3 MetroPCS/TMobile variant, code named James, that wasn't posted by @MotoJunkie01 and therefore blocked and undownloadable.
So thanks to @HPLazerJetPrinter1012 who was kind enough to find it on XDA in another section and thanks to @timjames474 for posting it in that thread....
VERY IMPORTANT IMHO THAT YOU BACKUP YOUR IMEI INFORMATION AS SOON AS YOU ROOT YOUR DEVICE, PREFERABLY BEFORE FLASHING A CUSTOM ROM. GOING FROM CUSTOM OREO BACK TO STOCK CAN EASILY ERASE ALL YOUR PHONES IMEI INFO MAKING VOLTE AND 4G AND PHONE INOPERABLE. HAPPENED TO ME AND IT WAS A HUGE P.I.T.A. TO FIX.
Download Links
JAMES_T_OCP27.91-51-4_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip / MIRROR
This is the newest (at least at the time of post) update, dated Oct 1, 2018
Instructions to revert back to stock firmware and make it so that you can get OTA updates again:
To install, extract the zip file in your adb/fastboot directory and then make sure you are properly connected to your computer by running the command
Then, once you confirm you are properly connected, just run the following fastboot commands one line at a time, making sure spelling is correct (or copying and pasting to ensure proper spelling):
After this is complete, simply reboot your device, and as long as you did everything right, you should be back on stock firmware with the ability to receive OTA updates.
Flashing a stock recovery,unencrypting your phone, or rooting will make OTA fail, so i recommend waiting to do those things until you are fully updated (unless you don't care about the latest build).
Just to cover my ass, i had nothing to do with the making of these files and I am simply posting well known information for newer users to help them get back to stock.
Therefore, i claim no responsibility for any damage or bricking of your device.
Have a good day friends and if I helped you out, a 'thanks' would be appreciated :good:
Click to expand...
Click to collapse
How did you get your phone to work meaning when I call some one they can't hear me but I can hear them .I re-flashed so many ROMs already that I'm staying on GSI Rom 8.1.0 Hanna metro PC's also I did flash stock Rom and still the see problem maybe it's time for replacement. It's been 3 days searching and asking for help. Maybe device to new idk ..

skullkid383 said:
https://mirrors.lolinet.com/firmware/moto/ look here for firmware and make sure its correct one and up to date before flashing it.
Click to expand...
Click to collapse
dude this link is worth money. amazing. thank you so much.

weakNPCdotCom said:
dude this link is worth money. amazing. thank you so much.
Click to expand...
Click to collapse
Yeah I used it on my Perry before I got hannah so it was first place looked when I needed Hannah fw

Googleme35 said:
How did you get your phone to work meaning when I call some one they can't hear me but I can hear them .I re-flashed so many ROMs already that I'm staying on GSI Rom 8.1.0 Hanna metro PC's also I did flash stock Rom and still the see problem maybe it's time for replacement. It's been 3 days searching and asking for help. Maybe device to new idk ..
Click to expand...
Click to collapse
I got mine to work because I have a James device.... You mention Hannah device so guessing you flashed the wrong firmware and that's the issue. I have the James xt1921-3

AesopRock127 said:
I got mine to work because I have a James device.... You mention Hannah device so guessing you flashed the wrong firmware and that's the issue. I have the James xt1921-3
Click to expand...
Click to collapse
Ok Thanks

I'm glad i could be of assistance,i was actually hunting down root methods for my GFs samsung and saw a video that linked to the user who uploaded it to AFH, rootjunkie was the channel if i recall,so i can't take all of that sweet credit. Yall have fun,but not too much fun

AesopRock127 said:
I know I'm not the only one who has been having trouble finding the stock firmware for the Moto e5 play xt1921-3 MetroPCS/TMobile variant, code named James, that wasn't posted by @MotoJunkie01 and therefore blocked and undownloadable.
So thanks to @HPLazerJetPrinter1012 who was kind enough to find it on XDA in another section and thanks to @timjames474 for posting it in that thread....
VERY IMPORTANT IMHO THAT YOU BACKUP YOUR IMEI INFORMATION AS SOON AS YOU ROOT YOUR DEVICE, PREFERABLY BEFORE FLASHING A CUSTOM ROM. GOING FROM CUSTOM OREO BACK TO STOCK CAN EASILY ERASE ALL YOUR PHONES IMEI INFO MAKING VOLTE AND 4G AND PHONE INOPERABLE. HAPPENED TO ME AND IT WAS A HUGE P.I.T.A. TO FIX.
Download Links
JAMES_T_OCP27.91-51-4_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip / MIRROR
This is the newest (at least at the time of post) update, dated Oct 1, 2018
Instructions to revert back to stock firmware and make it so that you can get OTA updates again:
To install, extract the zip file in your adb/fastboot directory and then make sure you are properly connected to your computer by running the command
Code:
fastboot devices
Then, once you confirm you are properly connected, just run the following fastboot commands one line at a time, making sure spelling is correct (or copying and pasting to ensure proper spelling):
Code:
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 flash system system.img_sparsechunk.4
fastboot erase DDR
fastboot erase cache
fastboot erase userdata
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot oem fb_mode_clear
After this is complete, simply reboot your device, and as long as you did everything right, you should be back on stock firmware with the ability to receive OTA updates.
Flashing a stock recovery,unencrypting your phone, or rooting will make OTA fail, so i recommend waiting to do those things until you are fully updated (unless you don't care about the latest build).
Just to cover my ass, i had nothing to do with the making of these files and I am simply posting well known information for newer users to help them get back to stock.
Therefore, i claim no responsibility for any damage or bricking of your device.
Have a good day friends and if I helped you out, a 'thanks' would be appreciated :good:
Click to expand...
Click to collapse
PLEASE tell me how you fixed the IMEI/SIM not recognized issue. I can't figure this out at all. Thanks!

OMG!!!! This was a god send. Thank you guys for putting this together for us. I thought all hope was lost. My phone is back and running. YaY!!!!!!

weakNPCdotCom said:
dude this link is worth money. amazing. thank you so much.
Click to expand...
Click to collapse
I keep getting unsecured network... Is this an issue from my end?

How do you backup IMEI in TWRP?
EFS?
Mine won't mount data for backup and cache in red
Or should I do it another way?

I have XT1924-2 AND I TOO HAVE IMEI=0 ANY FIXES?

Thank you!
This was very helpful, thanks!

TheLastAlphaUK said:
I have XT1924-2 AND I TOO HAVE IMEI=0 ANY FIXES?
Click to expand...
Click to collapse
Flash most up-to-date software

skullkid383 said:
Flash most up-to-date software
Click to expand...
Click to collapse
That's a weird Necro-Response. Also updating doesn't fix IMEI, (even though this was over a year ago, they would need an IMEI flasher and the box/numbers found somewhere else)