Database Users

[GUIDE] Restore Moto E (2015) Stock Firmware

Pre-requisites:
a) Download and install Motorola Moto EDrivers
b) Download and extract the stock Firmware of your choosing
c) If the firmware file you downloaded is a .xml.zip file then download Motorola Fastboot View attachment 2427667 (attached to this post) and extract the .exe into the same folder as the stock firmware files (the same folder as the .bin and .img files). If your firmware is a .tar.gz file then skip this step.
d) Get ADB (if you don't already have this, I suggest downloading and installing Minimal ADB and Fastboot by shimp208:
Direct Download
Disclaimer:
Follow these instructions at your own risk. If something goes wrong don't blame me!
These are the original stock signed image files from Motorola it should work on all Moto E Variants.
Steps to restore stock firmware:
1) Reboot the phone into bootloader mode. There are 2 ways to do this.
I) The 'hardware' way.
a) Unplug the USB cable and power off the phone.
b) Press and hold 'Volume down' then power on the phone.
c) Connect USB cable to your computer.​
II) The 'software' way.
a) Enable developer mode on the Moto E (Settings-> 'About Phone'. Tap 7 times on 'Build Number')
b) Enable USB debugging. (Settings -> 'Developer options' -> 'USB Debugging' -> check)
c) Connect phone to computer via USB, you should see a new ADB device detected and drivers installed.
d) Open "Minimal ADB and Fastboot". Type:
Code:
adb reboot-bootloader
You should see the Moto E bootloader screen with the following options:
Code:
Normal Powerup
Recovery
Factory
Switch Console [NULL: null]
Barcodes
BP Tools
2) Open a command prompt / terminal (Start -> cmd.exe in Win7) and browse to the folder with the extracted firmware.
In my case:
Code:
cd c:\falcon_retgb_user_4.3_14.10.0Q3.X-76-LGG-8_54_release-keys-cid7-Retail_GB
3)
Flash each of the partitions in sequence using mfastboot, you need to enter the following commands one-by-one checking that each one returns an [OKAY]
Code:
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.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 system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot oem config carrier vzw
mfastboot oem fb_mode_clear
​If you want to skip typing these commands one by one use MOTOEFLASHALL.bat. Place the .bat file inside the extracted firmware folder and run it.
4) Wait, you should now be rebooted into a fully stock Moto E firmware.
Original Thread
Creditstbon3
@lohanbarth for instructions and firmware images

FAQ
Q1: Will this work on locked bootloaders?
Ans: Yes as stock firmwares are digitally signed by Motorola.

Reserved

nice job!,
edit

iB4STiD said:
nice job!, but links aren't working
Click to expand...
Click to collapse
Are stock images even available yet?

iB4STiD said:
nice job!, but links aren't working
Click to expand...
Click to collapse
qbking77 said:
Are stock images even available yet?
Click to expand...
Click to collapse
The stock firmware aren't up yet

Lucas Eugene said:
The stock firmware aren't up yet
Click to expand...
Click to collapse
ah, thought they were thats why u made the thread.. this will come in handy tho in the future thanks :good:

good evening here Rom stock
XT1524_RETEUALL_MOTOE2 (4G-LTE) _5.0.2_LXI22.50-13_cid7_subsidy-DEFAULT_CFC.xml >>>> here <<<<

lohanbarth said:
good evening here Rom stock
XT1524_RETEUALL_MOTOE2 (4G-LTE) _5.0.2_LXI22.50-13_cid7_subsidy-DEFAULT_CFC.xml >>>> here <<<<
Click to expand...
Click to collapse
Hi thanks for the link I've created a new thread to manage Firmware

any stock firmware for the XT1527?

Stock firmware, non carrier
I tried following the steps to restore the firmware, but no luck since I got Preflash validation failed, which I take it to mean the boot.img is not the right one for the moto e2 (bought it from motorola online store). I had everything working, but decided to re-lock the phone, and forgot to check allow oem unlock. When i ran fastboot oem lock it sat there, and then on reboot it didn't start up, just stayed on fastboot screen. No matter what I do I can't get it past it and trying again to unlock it it says:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
So now I am stuck in a fastboot loop. Any suggestions for things to would be great.
Thanks.

Useful subject
https://www.youtube.com/watch?v=S1myrGuMCQg

lohanbarth said:
good evening here Rom stock
XT1524_RETEUALL_MOTOE2 (4G-LTE) _5.0.2_LXI22.50-13_cid7_subsidy-DEFAULT_CFC.xml >>>> here <<<<
Click to expand...
Click to collapse
@lohanbarth
can you provide stock rom for moto e 2015 3g variant

has moto released source or the firmware from the US lte gsm varient? what you have posted is for the EU model.

i'm wondering if the EU model is maybe the international version? which could in fact be used in the US.

Hi all
Stocks firmwares repository:
http://forum.xda-developers.com/showpost.php?p=60154569&postcount=21
Thanks if you help

With the Verizon model still having a locked bootloader, is there a possible chance that restoring the stock images from Motorola would allow you past that, or even the bootloader from the same model with a different carrier, this is my only device right now but I would like to test it but can't. Has anyone else thought of this?

Edit: Figured this out... made new post.

Dangerous waters ... and questions
Hi, I own a currently unlocked/rooted XT1524 (LTE/4G) which came with stock rom LXI22.50-24.1 (retde = German retail version).
At the moment I'm running @scritch007's latest rom (cm-12-20150418-UNOFFICIAL-surnia) on it and I'm thrilled to bits that someone made this happen so soon on the device. - Boundless joy, thank you so much.
But now, I'm wondering:
Lucas Eugene said:
[...] Flash each of the partitions in sequence using mfastboot, you need to enter the following commands one-by-one checking that each one returns an [OKAY]
Code:
mfastboot oem fb_mode_set
[...]
mfastboot oem config carrier vzw
[...]
Click to expand...
Click to collapse
1. Carrier VZW
What does the "... config carrier vzw" line exactly trigger/do when being applied on an European model?
Isn't VZW = Verizon Wireless?
Shouldn't this line read something like "... config carrier gsm"?
Couldn't we omit this line?
What were the consequences?
2. Risks
After unlocking/rooting I made a TWRP Backup (mfastboot boot <twrp>, didn't touch the original recovery) and also did I dd'ing all partitions living in /dev/block/platform/soc.0/by-name/ via adb root shell.
But regarding the soft-brick issues (oem re-lock) described by @Top_Quark and @squid2 here, I'm not sure (and feeling very uncomfortable with my limited knowledge) if I could re-lock the device without problems without my/any fitting original firmware (which one?). - There is only the one mentioned in the start posting (reteuall but with older LXI22.50-13, same cid 7). - So, can I re-lock my device after a TWRP restore/adb dd ... without flashing the mentioned original signed firmware (euretall)? - Or will I being "surprised" by a nice brick?
Checklist of preconditions to re-lock and go back:
Developer options: active
USB-Debugging: active
Enable OEM unlock: active
TWRP, adb, (m)fastboot set up and working
reteuall firmware: downloaded and at hand (retde firmware still has to show up somewhere yet)
_
Then processing @Lucas Eugene's flashing list
Is this right or am I missing something?
Thank you for your time reading and your replies.
Regards

Hi! I need your help... I bought a moto e xt1524 .... This phone isn't compatible with the frequencies using in Argentina... In my country works the xt1527 version... The question is if I can flash the 1527 firmware in the 1524...

[FAQ] How to prepare for and take an OTA update (All Carriers)

This is a reserection of -> http://forum.xda-developers.com/moto-x/general/faq-kit-kat-how-to-prepare-carriers-t2536735 and -> http://mark.cdmaforums.com/MotoX-OTA.html
With Verizon pushing a maintenance release for their Stock 4.4.4 (which doesn't change the Android version number), I wanted to post this sooner rather than later because questions are coming up....
Whenever a new OTA comes up, there are always questions like "what do I need to do to take the OTA?" or "I got prompted to take the OTA, but xxx is happening." This thread is intended to provide that information in once place.
This information is based on the past OTA updates for the Verizon, T-Mobile, and ATT Moto X phones, and threads on various forums. It should apply to all OTA updates.
Please note: If you have tried downgrading by flashing only parts of a rom, or have mismatched files on your phone for any reason, DO NOT TAKE AN OTA or you will likely brick your phone!! First flash your phone with a full SBF of the latest ROM for your carrier before attempting to take future OTA's. For more on Downgrading and the risks associated with it, see -> [INFO/WARNING]The Risks of Downgrading, and the impacts of GPT.BIN and MOTOBOOT.IMG
These are the most common Questions and Issues we've seen in the past...
If you could NOT get your bootloader unlock code directly from Motorola and rooted by some other process, you should *WAIT* on taking an OTA update as it may patch any vulnerability being exploited to root your phone. And you may not be able to ROOT on this new version!!
If you used Sunshine, or got your Bootloader Unlock code from the China Seller or Middleman... You should BE CAUTIOUS and *WAIT* on upgrading past 4.4.4. Please see -> [LOLLIPOP WARNING]Those Who Unlocked Via Sunshine or Purchasing a Code from China
You should expect to lose root when you take an OTA.
For the Motorola X, the OTA's are incremental updates. You must be on a specific previous ROM, and "step up." To put it another way... To take the 4.4.4 OTA, your phone needs to be on 4.4.2 (or 4.4.3 depending on your model/carrier). To take the 4.4.2 OTA, your phone needs to be on 4.4. To take the 4.4 OTA, your phone needs to be on the 4.2.2 w/camera fix version. To take the 4.2.2 w/camera fix OTA, your phone needs to be on the initial shipping ROM version.
Inside the OTA is a "Pre-flash Validation Check" to ensure your phone is on the correct version BEFORE it will flash. It includes a manifest file that contains a list of files and their check sums the OTA expects to be on your phone. If the files are missing from your phone, or the check sum for a particular file doesn't match (because you've replaced or altered the file), the OTA will fall. NOTE: The more files patched by the update, the more strict the pre-flash validation will be. So an update from 4.4.4 -> 5.1 will be more strict than the recent Verizon 4.4.4 maintenance patch.
Because of #5, you must be "stock." Any bloat you deleted, needs to be put back. Any apps you froze with Titanium Backup or the like, may need to be unfrozen. Apps disabled via the phone's Settings -> Applications -> [select app] -> [disable] can remain disabled and should not impact the update. NOTE: Back in the "early days" of the 2013 X, all apps frozen with TiBu had to be unfrozen. Later updates that hasn't been much of a problem. I don't use it, so I can't say for sure.
If you have XPosed installed on your phone, it often does make changes that will cause the Pre-Flash Validation to fail. You may be able to just disable it, rather than fully removing it, and then take the OTA. (To disable Xposed, boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip ) NOTE: There is a newer version of Xposed needed for Lollipop!!
The OTA Updates will only install via Stock Recovery. If your Root method has replaced stock recovery with something else, you will need to use mfastboot to flash stock recovery on your phone BEFORE you attempt to take the update. Not having Stock Recovery on your phone when you take the OTA can result in your phone doing a boot loop. NOTE: You can use fastboot erase cache to delete the update zip file from your phone which will stop the boot loop.
There are several options to get back to "stock" without loosing your data. (I will add them to Post #2 of this thread at a later date), some are more technical, some are more noob friendly. The one you use, depends on how much, or how little, you have modified your phone away from stock.
In some cases, using mfastboot to reflash stock Recovery.IMG and System.IMG can be enough to get you back to "Stock" and take the OTA update.
If you unlocked your bootload by getting the code from Moto, after taking the OTA you may root by following -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 Please be sure to use the latest TWRP fastboot IMG file (Alternate Link) and Installable ZIP of SuperSU
Any tethering hacks you have done will likely need to be undone in order to take the OTA (see #5 above), and may not work after the OTA is installed.
Some FAQ's...
I've tried taking the OTA, but I'm stuck in a loop. It wants to keep rebooting. - This is usually caused by having a 3rd party recovery, like TWRP/CWM, on the phone. Re-flash the stock recovery to install the OTA update, or use fastboot erase cache to delete the update zip file from your phone which will stop the boot loop. (instructions will be added to Post #2 of this thread in the future)
I've tried putting back my bloat, and taking the OTA, but it fails. - You likely missed something the Pre-flash Validation check is looking for. If you are able to capture the OTA ZIP and use the SIDE LOAD AN OTA instructions (which will be added to post #2 of this thread in the future), you can watch progress of the OTA install. It will tell you the error, and/or what file doesn't match.
In the past we've seen error codes 252 and 410. These have been related to files on the phone not matching the OTA's pre-flash validation checks.

[NOT YET SPELL CHECKED!!!]
How to return to stock & Unrooted... (Windows options only, as I don't have a Mac) Note: Some Windows 8/8.1 users have had issues, so when possible, please use Windows 7.
The following are listed in the order I originally posted them HERE and HERE
Requirements: These are the same no matter which option you use.
To repeat what I said in the OP, Do NOT attempt to downgrade your phone!! Please be aware of the risks -> [INFO/WARNING]The Risks of Downgrading, and the impacts of GPT.BIN and MOTOBOOT.IMG
Know what version ROM is on your phone before you touch anything. Normally I would suggest BEFORE you flash away from Stock, on the phone you first go App Drawer -> Settings -> About Phone... Make note of what is listed under System Version, Android Version, and build number. Then visit one (or all) of the sites that host leaked ROMS until you find the SBF that matches and down load the file to your PC for use later.. The file name will usually contain parts or all of that info listed under settings, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc).
So for example: If your phone model is XT1058 and under about phone it reports...
android version is 4.4.4
system version is 212.44.26. ghost_row.RCI.en.ca
build nunber is KXA21.12-L1.26
That tells me you have a Rogers Canada (RCI) XT1058 with 4.4.4 ROM on it. When you look at the file factory site for your SBF, you want to look for a file that contains some/all of that info, and you'll find... XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip
(notice the parts of the "about phone" info and file name which are highlighted in Bold to help illustrate the example)
IF you are already running a CUSTOM or 3Rd party rom, like CM, system version and build number will not match STOCK Moto SBF files
You must have already installed the Motorola Drivers, ADB, Android Platform Tools, and mFastboot
mFastboot (get from the previous link). NOTE: Stock fastboot that ships with the Android SDK/Platform tools can NOT flash the SYSTEM.IMG on Moto phones!!
Download ROM/SBF files for the ROM currently on your phone!!!! from one of the sites listed HERE. Failure to use the EXACT SAME ROM/SBF that is on your phone now can cause problems!!
Your battery has an 80% or greater charge!!
MicroUSB Cable.
Know how to start your phone into the Fastboot AP/Bootloader mode...
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in Fastboot AP menu on phone.
The Options...
NOTE: I most often recommend option 5.
Option 1... The "Moto X Tool Kit"
This is the most newbie friendly.. But it can be a little complex to prepare and put your SBF in the right place, etc.
See -> [TOOL] Moto X Toolkit v1.4.4 [Backup/Restore,Drivers,Return to stock,Root,Bootani]
It is an "all in one" type tool that should set things up and help you too. I've not used it, but it appears to be a complete package including ADB and the drivers. The only thing it does not appear to include would be Roms for your particular phone, so, you'll likely need to download the ROM for your phone separately. As noted in the ToolKit thread, if they are available, you can get them from here -> http://sbf.droid-developers.org/ghost/list.php your "build number" or part of it, should be in the file name you are downloading.
Again, I haven't used this tool, so for install, setup and usage, I'll have to point you to that thread to ask. Two main options you'll be interested in... UNROOT (which keeps your data and apps) or FLASH BACK TO STOCK (which will likely also completely reset your phone and wipe any/all data, settings, applications, etc).
Option 2... mFastboot flashing individual parts of your phone's firmware.
This will not erase your data and apps. It is a good option if you are stuck in a boot loop.
If you have made very few changes to your phone and already have ADB drivers and fastboot from the Android SDK installed and in your path, along with the Motorola drivers already installed and working, this is the quickest and easiest way to return to a state that is ready to accept an OTA without losing data/apps.
NOTE: you may need to disable and/or uninstall Xposed before doing this.(To disable Xposed, boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip ) Keep in mind there is a newer version of Xposed needed for Lollipop!!
After you have the requirements as listed above, the steps would be as follows...
Start the phone in Fastboot AP/Bootloader mode.
Connect phone to PC via USB cable.
open command prompt file and change to the folder you unzipped the ROM file to.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot reboot
phone should reboot and be back to stock and ready for the update.
NOTE: to combat a 410 ERROR while doing the update, some users have also had to also do the following
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
See -> http://forum.xda-developers.com/showpost.php?p=47639731&postcount=315 (thanks jimmydafish)
Option 3... Fully flash your phone using RSDLite while attempting to keep your data and settings
NOTE: this has the potential to erase your data if you don't edit the XML properly before flashing.
Follow this guide -> [GUIDE][VIDEO] Moto X - Return to 100% stock (using RSD Lite OR manual flash) using SBF of the ROM currently on your phone, or newer for your carrier and model. HOWEVER, before doing it, as part of STEP 4 while editing the XML file, also remove the line that says...
<step operation="erase" partition="userdata" />
Failure to remove this line will result in your data/apps/settings being erased from your phone!!
Option 4... Fully flash your phone using RSDLite
Note: this WILL ERASE YOUR USER DATA AND APPS, and put you back to a "fresh" phone.
Follow this guide -> [GUIDE][VIDEO] Moto X - Return to 100% stock (using RSD Lite OR manual flash) using the ROM from your carrier.
Option 5... Using mFastboot to manually flash your phone's firmware (without wiping data).
This is very similar to using option 3, but uses Moto fastboot instead of RSD, however it adds a few steps which aid in flashing when your GPT.BIN and MOTOBOOT.IMG are mismatched from the rest of your rom, and refuse to flash.
As written, these steps will NOT erase your data and apps. Because of this you may need to disable and/or uninstall Xposed before doing performing these steps.(To disable Xposed, boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip ) Keep in mind there is a newer version of Xposed needed for Lollipop!!
After you have the requirements near the top of this page, the steps would be as follows...
Start the phone in Fastboot AP mode.
Connect your phone to PC via MicroUSB cable.
open a command prompt and change to the folder you unzipped the ROM/SBF file to.
type the following, pressing enter after each command, and wait for it to finish before going onto the next... NOTE: yes, there are a few commands being repeated, but this is intentional!!!
mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash partition gpt.bin
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
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot reboot
The phone should reboot and and be ready. (it could take a little longer than a normal reboot)
NOTE: if you wish to erase your data and apps during this process, just before the final reboot command, issue... mfastboot erase userdata
Option 6... Flash only stock recovery.
This option is useful if all you did was unlock your bootloader, flash TWRP recovery, and rooted. It can be used if you've haven't installed Xposed, or modified any stock apps, and only run rooted for apps like BigTinCan's Adaway, Root Explorer, Wifi Tether for Root, etc.
Start the phone in Fastboot AP mode.
Connect your phone to PC via MicroUSB cable.
open a command prompt and change to the folder you unzipped the ROM/SBF file to.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash recovery recovery.img
mfastboot reboot-bootloader
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
The device will display the Motorola logo and then the Android in distress (logo with Exclamation mark)
Press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key
The device will start in Stock Recovery display additional menu options (Text will appear in BLUE)
While in Stock Recovery, use the VOL DOWN Key to scroll and the POWER Key to select the option you wish to use.
You may now use the option to reboot the phone.

{reserved}

KidJoe,
Thanks so much for this. Even though I manually returned all changes to stock, the ota still kept quitting with an error.
It was really annoying because after each error, I would have to redownload the entire ota, 696MB, which was downloading rather slowly.
Anyway, I followed option number 2 from the original post to flash boot, recovery and system and it was smooth sailing after that
Thanks again

KidJoe said:
[NOT YET SPELL CHECKED!!!]
Option 2... mFastboot flashing individual parts of your phone's firmware.
This will not erase your data and apps. It is a good option if you are stuck in a boot loop.
If you have made very few changes to your phone and already have ADB drivers and fastboot from the Android SDK installed and in your path, along with the Motorola drivers already installed and working, this is the quickest and easiest way to return to a state that is ready to accept an OTA without losing data/apps.
NOTE: you may need to disable and/or uninstall Xposed before doing this.(To disable Xposed, boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip ) Keep in mind there is a newer version of Xposed needed for Lollipop!!
After you have the requirements as listed above, the steps would be as follows...
Start the phone in Fastboot AP/Bootloader mode.
Connect phone to PC via USB cable.
open command prompt file and change to the folder you unzipped the ROM file to.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot reboot
phone should reboot and be back to stock and ready for the update.
NOTE: to combat a 410 ERROR while doing the update, some users have also had to also do the following
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
See -> http://forum.xda-developers.com/showpost.php?p=47639731&postcount=315 (thanks jimmydafish)
[/list]
Click to expand...
Click to collapse
KidJoe, thanks for the help. I have an XT1095. All I am pretty sure I did was root. I've never installed TWRP or even used root apps other than Greenify. In that state I was not able to accept the recent 5.1 OTA. I used the option in Supersu to full unroot (which also uninstalled Supersu). That did not fix the problem. I am now just finding your guide but other searching has led me to your conclusion that Option 2 should be all I need to do plus it won't wipe my phone.
The confusion I have now involves the system.img file. I requested the 5.0 download from Moto, but they never responded. I found the proper zip file elsewhere (TMO_XT1095_5.0_LXE22.46-11_cid9_CFC.xml.zip). When I unzip it, I see all the files. The recovery.img file is there but the system.img file is broken up into eight different files all named system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2, etc.
Do I have the right files? Do I flash all of them individually? I'm not very experienced in this and don't want to screw this up. Any information you could provide would be greatly appreciated. Thanks.
Edit: After posting this, I found this site: http://www.usoftsmartphone.com/t279221.html that showd me how to extract the system file from all the sparse files. Step one creates a system.img file from all of them. Step two seems to unzip them. I am guessing that the file created after step 1 is the file I would need to flash?
Again, thanks for your help here!

summit15 said:
KidJoe, thanks for the help. I have an XT1095. All I am pretty sure I did was root. I've never installed TWRP or even used root apps other than Greenify. In that state I was not able to accept the recent 5.1 OTA. I used the option in Supersu to full unroot (which also uninstalled Supersu). That did not fix the problem. I am now just finding your guide but other searching has led me to your conclusion that Option 2 should be all I need to do plus it won't wipe my phone.
The confusion I have now involves the system.img file. I requested the 5.0 download from Moto, but they never responded. I found the proper zip file elsewhere (TMO_XT1095_5.0_LXE22.46-11_cid9_CFC.xml.zip). When I unzip it, I see all the files. The recovery.img file is there but the system.img file is broken up into eight different files all named system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2, etc.
Do I have the right files? Do I flash all of them individually? I'm not very experienced in this and don't want to screw this up. Any information you could provide would be greatly appreciated. Thanks.
Edit: After posting this, I found this site: http://www.usoftsmartphone.com/t279221.html that showd me how to extract the system file from all the sparse files. Step one creates a system.img file from all of them. Step two seems to unzip them. I am guessing that the file created after step 1 is the file I would need to flash?
Again, thanks for your help here!
Click to expand...
Click to collapse
Keep in mind that the XT1095 is NOT a 2013 X, so its files may be different.

So I'm using a cm12 based rom and I've wanted to return to stock lately, let me see if I got this straight. Using rsd lite and erasing the line:
<step operation="erase" partition="userdata" />
Won't erase internal memory like music, photos, etc?
It's safe? I'm wondering if I'm going to have problems with the apps since they're running on ART on lollipop or if the system settings will have issues when I return to stock KitKat

OTA Accepted
For anyone who finds themselves in my same situation (all I really did to my phone was root it and install Supersu, no custom recovery or big time changes and I wanted to apply the OTA without wiping my device), I got my OTA update applied by doing the following:
Did a "Full Unroot" from within the Supersu app which then uninstalled itself.
I found the proper Moto ZIP file that contained Lollipop 5.0.
I then used mfastboot to flash the boot.img and the recovery.img
I then boot the phone up and told it to check for system updates.
It found the update, downloaded it, and then applied it.
It worked and I can move on with my life now.
NOTE: Most of my confusion in this process centered around my being told I needed to flash the system.img file. My problem was that inside the Moto ZIP file were eight different system_sparse files. I didn't know what to do with all them. I found a site in the previous link that showed me how to essentially combine all them into one system.img file. I followed those directions and it created the file. However, when I tried to flash it, I got an error that seemed to suggest that the file was corrupt.SO, this was after I had already flashed the boot and recovery files. I gave the OTA a shot just hoping it would work. Turned out it did.
Thanks again to KidJoe for this guide.

summit15 said:
For anyone who finds themselves in my same situation (all I really did to my phone was root it and install Supersu, no custom recovery or big time changes and I wanted to apply the OTA without wiping my device), I got my OTA update applied by doing the following:
Did a "Full Unroot" from within the Supersu app which then uninstalled itself.
I found the proper Moto ZIP file that contained Lollipop 5.0.
I then used mfastboot to flash the boot.img and the recovery.img
I then boot the phone up and told it to check for system updates.
It found the update, downloaded it, and then applied it.
It worked and I can move on with my life now.
NOTE: Most of my confusion in this process centered around my being told I needed to flash the system.img file. My problem was that inside the Moto ZIP file were eight different system_sparse files. I didn't know what to do with all them. I found a site in the previous link that showed me how to essentially combine all them into one system.img file. I followed those directions and it created the file. However, when I tried to flash it, I got an error that seemed to suggest that the file was corrupt.SO, this was after I had already flashed the boot and recovery files. I gave the OTA a shot just hoping it would work. Turned out it did.
Thanks again to KidJoe for this guide.
Click to expand...
Click to collapse
Again.. you have an XT1095... which is NOT a 2013 X... this guide is in the 2013 X section, so things can/will be different for a 2014 X...
But thanks for sharing.

Awsome Tutorial!!
I'm really a noob, so I still have some questions...
After that you should get the OTA update by going to setting -> about phone -> update??
because if so, I'm not.
Another thing i may done something wrong. On this step:
4. Download ROM/SBF files for the ROM currently on your phone!!!! from one of the sites listed HERE. Failure to use the EXACT SAME ROM/SBF that is on your phone now can cause problems!!
I needed to move the ROM/SBF to the phone right? At any folder? Because I didnt do that and I opened the command prompt in the pc folder that the ROM/SBF was unziped. Nothing wrong happened to my phone, apparently.
Should I remake the tutorial moving the unziped file to the sdcard folder of my phone?
sorry for so many doubts.

Malba14 said:
I'm really a noob, so I still have some questions...
After that you should get the OTA update by going to setting -> about phone -> update??
because if so, I'm not.
Click to expand...
Click to collapse
The OTA update hasn't rolled out for all phone models and carrier variants yet. So there is a VERY GOOD chance it wont be available for you yet.
Malba14 said:
Another thing i may done something wrong. On this step:
4. Download ROM/SBF files for the ROM currently on your phone!!!! from one of the sites listed HERE. Failure to use the EXACT SAME ROM/SBF that is on your phone now can cause problems!!
I needed to move the ROM/SBF to the phone right? At any folder? Because I didnt do that and I opened the command prompt in the pc folder that the ROM/SBF was unziped. Nothing wrong happened to my phone, apparently.
Should I remake the tutorial moving the unziped file to the sdcard folder of my phone?
sorry for so many doubts.
Click to expand...
Click to collapse
No, you do NOT move the SBF, or parts of it, to your phone. Leave it on your PC.
The tools to flash (RSDLite and mFastboot) are tools ON YOUR PC... they need the file to be on your pc.
In the post I talk about figuring out what file to download and use the example of the Rogers XT1058, and the correct file being XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip so sticking with that example.. you visit one of the sites (from your PC), download XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip ... and unzip it on your PC to a folder... If you are following option 2, 5 or 6 and using mFastboot, then you need to open a command prompt and change drive and directories to where you unzipped XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip to BEFORE you start entering the mfastboot commands. NOTE: you could just SHIFT-RightClick on the folder and "open command window here" as that will open a command prompt in that path/folder.

KidJoe said:
The OTA update hasn't rolled out for all phone models and carrier variants yet. So there is a VERY GOOD chance it wont be available for you yet..
Click to expand...
Click to collapse
The thing is that the update was rolled out for me before. But kept regecting it until one day that I clicked on "stop bothering me, I'll do it when I want" button and then every time I turned my phone on, after 30 seconds it rebooted to TeamWin. This kept going until I clicked on recovery or system (I dont remember - under the reboot page) and the cycle went off saying that has been some kind of problem with the update.
KidJoe said:
No, you do NOT move the SBF, or parts of it, to your phone. Leave it on your PC.
The tools to flash (RSDLite and mFastboot) are tools ON YOUR PC... they need the file to be on your pc.
In the post I talk about figuring out what file to download and use the example of the Rogers XT1058, and the correct file being XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip so sticking with that example.. you visit one of the sites (from your PC), download XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip ... and unzip it on your PC to a folder... If you are following option 2, 5 or 6 and using mFastboot, then you need to open a command prompt and change drive and directories to where you unzipped XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip to BEFORE you start entering the mfastboot commands. NOTE: you could just SHIFT-RightClick on the folder and "open command window here" as that will open a command prompt in that path/folder.
Click to expand...
Click to collapse
This part I did it right, i think. I fount the one that describe my phone better.
XT1058_VIVO-BR_4.4.4_KXA21.12-L1.26_59_cid12_CFC_1FF.xml
Actually I just reallized it is .xml. Is that ok? On my PC it opened with winrar just like any zip.

Malba14 said:
The thing is that the update was rolled out for me before. But kept regecting it until one day that I clicked on "stop bothering me, I'll do it when I want" button and then every time I turned my phone on, after 30 seconds it rebooted to TeamWin. This kept going until I clicked on recovery or system (I dont remember - under the reboot page) and the cycle went off saying that has been some kind of problem with the update.
Click to expand...
Click to collapse
Rebooted to TeamWin and said there was a problem with the update?? Yeah, because you need STOCK recovery on the phone. (as stated in the OP)
Malba14 said:
This part I did it right, i think. I fount the one that describe my phone better.
XT1058_VIVO-BR_4.4.4_KXA21.12-L1.26_59_cid12_CFC_1FF.xml
Actually I just reallized it is .xml. Is that ok? On my PC it opened with winrar just like any zip.
Click to expand...
Click to collapse
There maybe an XML inside the ZIP... you need to uncompress the entire file (extract all) BEFORE you can flash it, other wise RSDlite or mFastboot wont find the files you are trying to flash.

KidJoe said:
Rebooted to TeamWin and said there was a problem with the update?? Yeah, because you need STOCK recovery on the phone. (as stated in the OP)
There maybe an XML inside the ZIP... you need to uncompress the entire file (extract all) BEFORE you can flash it, other wise RSDlite or mFastboot wont find the files you are trying to flash.
Click to expand...
Click to collapse
Thanks for the help man. I'm sorry for the noob questions.
I actually did the hole tutorial before. I extracted this hole file and opened the command prompt in it and did the tutorial number 5.
Sorry if I wasnt clear before but the problem with the update was just a backgroud history to what I was aiming to know. That is: after I do the tutorial, what I have to do to get the OTA update now?
And how can I know that I did it right?
Your are awsome man!

Malba14 said:
The thing is that the update was rolled out for me before. But kept regecting it until one day that I clicked on "stop bothering me, I'll do it when I want" button....
Click to expand...
Click to collapse
I forgot to mention... for the models IT has started pushing for, they were sending it out in waves... IF you missed your turn (which you eventually did by not installing), you usually need to wait until the end, when the waves are done.. Because of when the BR Xt1058 push was started, I'd say that might be in the next week, or two.
Malba14 said:
Thanks for the help man. I'm sorry for the noob questions.
I actually did the hole tutorial before. I extracted this hole file and opened the command prompt in it and did the tutorial number 5.
Sorry if I wasnt clear before but the problem with the update was just a backgroud history to what I was aiming to know. That is: after I do the tutorial, what I have to do to get the OTA update now?
And how can I know that I did it right?
Your are awsome man!
Click to expand...
Click to collapse
As long as you flashed the latest 4.4.4 rom, your bootloader is consistent with the ROM you flashed, are you 100% completely stock, you just sit and wait until the OTA becomes available to your phone again. You can manually keep checking...
OR you can see if the 5.1 SBF is available for your carrier/model in this thread -> http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628 download and flash it instead, which will take you right to 5.1...
OR you can see if the official OTA zip has been posted, download the zip to the /SDCard of your phone, and follow the SIDE LOAD section of -> http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079

KidJoe said:
I forgot to mention... for the models IT has started pushing for, they were sending it out in waves... IF you missed your turn (which you eventually did by not installing), you usually need to wait until the end, when the waves are done.. Because of when the BR Xt1058 push was started, I'd say that might be in the next week, or two.
As long as you flashed the latest 4.4.4 rom, your bootloader is consistent with the ROM you flashed, are you 100% completely stock, you just sit and wait until the OTA becomes available to your phone again. You can manually keep checking...
OR you can see if the 5.1 SBF is available for your carrier/model in this thread -> http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628 download and flash it instead, which will take you right to 5.1...
OR you can see if the official OTA zip has been posted, download the zip to the /SDCard of your phone, and follow the SIDE LOAD section of -> http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079
Click to expand...
Click to collapse
Thanks a lot!!!

KidJoe said:
Option 5... Using mFastboot to manually flash your phone's firmware (without wiping data).
This is very similar to using option 3, but uses Moto fastboot instead of RSD, however it adds a few steps which aid in flashing when your GPT.BIN and MOTOBOOT.IMG are mismatched from the rest of your rom, and refuse to flash.
As written, these steps will NOT erase your data and apps. Because of this you may need to disable and/or uninstall Xposed before doing performing these steps.(To disable Xposed, boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip ) Keep in mind there is a newer version of Xposed needed for Lollipop!!
After you have the requirements near the top of this page, the steps would be as follows...
Start the phone in Fastboot AP mode.
Connect your phone to PC via MicroUSB cable.
open a command prompt and change to the folder you unzipped the ROM/SBF file to.
type the following, pressing enter after each command, and wait for it to finish before going onto the next... NOTE: yes, there are a few commands being repeated, but this is intentional!!!
mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash partition gpt.bin
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
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot reboot
The phone should reboot and and be ready. (it could take a little longer than a normal reboot)
NOTE: if you wish to erase your data and apps during this process, just before the final reboot command, issue... mfastboot erase userdata
Click to expand...
Click to collapse
Hey.
I wanted to return to stock by flashing the parts manually.
I followed your steps but when i executed the command a message popped out saying 'Variable not supported' and it continued the execution.
I did not find any change in the system when I checked after the whole process was completed.
The message I mentioned earlier was shown for every step.
Example Code:
Code:
mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.280s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
OKAY [ 0.534s]
finished. total time: 0.819s
I also flashed boot, logo, system and the others parts.
But the same message was shown every time.
And after the process was complete I restarted the phone but the 'Bootloader Unlocked Warning' screen appeared.
I hadn't removed this after I rooted the phone.
I thought it would be removed when I flashed motoboot, boot and logo.
Phone Details:
Current Android Version: 4.4.4
System Version: 212.44.26.ghost_row.AsiaRetail.en.03
Build Number: KXA21.12-L1.26
Kernel Version: 3.4.42-g50861a7
I used this image:
Drive Link:
https://docs.google.com/file/d/0B5XNxZ2OcfKtdDROTk5kb21ObU0/edit?pli=1
File Factory Link:
http://www.filefactory.com/file/3qr..._4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip
I desperately need your help.
What should I so to flash the stock image properly?
Thanks in advance.

RohanAditya said:
Hey.
I wanted to return to stock by flashing the parts manually.
I followed your steps but when i executed the command a message popped out saying 'Variable not supported' and it continued the execution.
I did not find any change in the system when I checked after the whole process was completed.
The message I mentioned earlier was shown for every step.
Example Code:
Code:
mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.280s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
OKAY [ 0.534s]
finished. total time: 0.819s
I also flashed boot, logo, system and the others parts.
But the same message was shown every time.
And after the process was complete I restarted the phone but the 'Bootloader Unlocked Warning' screen appeared.
I hadn't removed this after I rooted the phone.
I thought it would be removed when I flashed motoboot, boot and logo.
Phone Details:
Current Android Version: 4.4.4
System Version: 212.44.26.ghost_row.AsiaRetail.en.03
Build Number: KXA21.12-L1.26
Kernel Version: 3.4.42-g50861a7
I used this image:
Drive Link:
https://docs.google.com/file/d/0B5XNxZ2OcfKtdDROTk5kb21ObU0/edit?pli=1
File Factory Link:
http://www.filefactory.com/file/3qr..._4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip
I desperately need your help.
What should I so to flash the stock image properly?
Thanks in advance.
Click to expand...
Click to collapse
Based on what you posted, I'm not completely sure of your question. I mean if you think you are not stock because you still have the unlocked bootloader warning message after flashing, that is normal if you've ever unlocked your bootloader.
Out of box LOCKED bootloader shows Locked Status 0... After unlocking, it shows Unlocked Status 3. If you attempt to relock it, it will show as Locked Status 2. We don't have a way to get back to Locked Status 0. That being said... If the status is NOT 0, you'll always get the Unlocked Bootloader Warning when using the stock/standard LOGO.BIN.

KidJoe said:
Based on what you posted, I'm not completely sure of your question. I mean if you think you are not stock because you still have the unlocked bootloader warning message after flashing, that is normal if you've ever unlocked your bootloader.
Out of box LOCKED bootloader shows Locked Status 0... After unlocking, it shows Unlocked Status 3. If you attempt to relock it, it will show as Locked Status 2. We don't have a way to get back to Locked Status 0. That being said... If the status is NOT 0, you'll always get the Unlocked Bootloader Warning when using the stock/standard LOGO.BIN.
Click to expand...
Click to collapse
Okay I unlocked it. The code is 3.
Thanks
But how do I know if I'm ready to receive the OTA?
Is there a way to find out if I can receive it without it resulting in a brick?
And is the Variable not supported message normal?
Or have I done something wrong?
Thanks in advance

RohanAditya said:
Okay I unlocked it. The code is 3.
Thanks
But how do I know if I'm ready to receive the OTA?
Is there a way to find out if I can receive it without it resulting in a brick?
And is the Variable not supported message normal?
Or have I done something wrong?
Thanks in advance
Click to expand...
Click to collapse
Variable not supported is normal and nothing to worry about.
Because each OTA is different and looks at different aspects of the phone (based on what it will upgrade, or not), there is no way to tell you exactly what should be checked.
If you returned to stock by flashing the COMPLETE STOCK ROM (all parts of SBF) for your carrier/model with mFastboot, and received no errors (other than variable not supported), and your bootloader version is consistent with the ROM on your phone (i.e. you didn't attempt to downgrade), then you should be ready for the OTA...

[GUIDE][Osprey] Fastboot Flashing Factory Firmware Images

Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own.​
Based on existing tutorial by @t-bon3. This guide has been created as a hard-brick occurred using the old Moto G (1st Gen) tutorial. Please exercise extreme care with Fastboot, and only use the commands mentioned here. Experimenting with Fastboot commands can seriously damage your phone.
How to Fastboot Flash Moto G (3rd Gen) Factory Firmware Images​
Required Files:
Motorola Drivers: Download
Latest Fastboot | ADB (Windows | Linux): Download (Windows 10 users may need this pack for Drivers to work.)
Factory Firmware Images: [INDEX][Osprey] Moto G Factory Firmware Images​
WARNING: You must perform a 'Factory data reset' in Stock Recovery before flashing any Firmware Image - instructions here.​
Instructions:
1) Extracting Fastboot and Firmware Images:
Extract zip for chosen Firmware Image to a folder with a simple directory structure. For example: C:\motog_firmware\
Extract the adb-fastboot-latest_win_linux.zip into this folder.​
2) Reboot the phone into 'Bootloader mode' and preparing PC for flashing
Windows:
Entering Fastboot mode:
------------------------------------
i) The 'hardware' way.
a) Unplug the USB cable and power off the phone.
b) Press and hold 'Volume down' then power on the phone.
c) Connect USB cable to your computer.
ii) The 'software' way.
a) Enable developer mode on the Moto G (Settings-> 'About Phone'. Tap 7 times on 'Build Number')
b) Enable USB debugging. (Settings -> 'Developer options' -> 'USB Debugging' -> check)
c) Connect phone to computer via USB, you should see a new ADB device detected and drivers installed.
d) Open Command Prompt, navigate to the Firmware / ADB folder (i.e CD C:\motog_firmware ) and type:
Code:
adb reboot-bootloader
Linux:
Entering Fastboot mode:
------------------------------------
i) The 'hardware' way.
a) Unplug the USB cable and power off the phone.
b) Press and hold 'Volume down' then power on the phone.
c) Connect USB cable to your computer.
ii) The 'software' way. (Requires ADB to be already installed - see below)
a) Enable developer mode on the Moto G (Settings-> 'About Phone'. Tap 7 times on 'Build Number')
b) Enable USB debugging. (Settings -> 'Developer options' -> 'USB Debugging' -> check)
c) Connect phone to computer via USB
d) Navigate to the Firmware folder, right-click and open terminal and type:
Code:
adb reboot-bootloader
Installing ADB / Fastboot:
-------------------------------------
Flashing via Linux LiveCD: (Put factory firmware files on an external usb drive / pen)
--------------------------------
a) Download Ubuntu LiveCD
b) Burn to DVD or write to USB pen
c) Restart PC, Boot from DVD into Ubuntu
d) Open Terminal and type the following:
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot​
e) Test fastboot by typing: sudo fastboot devices
You should see:
<serial number> fastboot​f) You are now ready to flash the fastboot files
​
3) Fastboot Commands:
Do commands manually, one at a time - checking that each one returns an [OKAY].​
NOTE: Do not simply copy and paste these commands! - system.img_sparsechunks may differ in number and name.
Always check contents of folder you're working with. You must flash all of the sparsechunk files you have.​
fastboot oem fb_mode_set
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 erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot​
ALWAYS CHECK YOUR MODEL
FLASHING WRONG FIRMWARE CAN DESTROY A PHONE​

Frequently Asked Questions:
Can I restore Factory Firmware if my Bootloader is locked?
Yes. However attempting to downgrade to an older version of Android may fail - 'Preflash validation' error. Even with an unlocked Bootloader, downgrading cannot be guaranteed. It's also important to be aware that flashing the wrong Bootloader (bootloader.img) for your model can have serious consequences. Always establish your model of Moto G before flashing.
I get a 'Preflash validation' error when flashing a Firmware Image
The Firmware Image you are trying to flash is too old. You can only flash a firmware image that matches, or is newer than the most recent system version you have had on your phone. However the former scenario can also sometimes return the error. In which case, your options are to wait for an even newer firmware image or unlock Bootloader and flash a ROM zip.
After flashing Firmware Image files phone gets stuck during boot-up | will not load Android?
Check you are naming the files correctly, and make sure you are flashing all of the 'sparsechunk' files - not just those mentioned in the tutorial. The 'sparsechunk' commands listed there are not to be copied exactly, different firmware images may have different files.
How to flash Radio Firmware only?
Use the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn​
How do I downgrade to an older Firmware?
Downgrading carries risks, and may result in constant nagging notifications to update Android. Decide carefully if this is really what you want. With earlier generations of Moto G flashing bootloader.img and gpt.bin has resulted in a hard-brick. Avoid flashing these files if you are trying to downgrade. The safer option is to find a custom Stock ROM with OTA Updates disabled.
Fastboot in Linux is not working?
In Linux, root access is required for Fastboot and/or ADB to work.
sudo fastboot devices​

Hi @lost101
Need a clarification in the 3rd point (fastboot commands),
Whether it's
fastboot flash bootloader bootloader.img
OR
fastboot flash motoboot bootloader.img

==vj== said:
Hi @lost101
Need a clarification in the 3rd point (fastboot commands),
<snip>
Click to expand...
Click to collapse
From the Firmware Images I've checked; the file is called: bootloader.img and the partition: bootloader
EDIT: This information is based on the servicefile.xml included with many of these firmware images.

Hey im new here and with rooting
i recently rooted my phone but now when i try to start up the screen goes black.
im downloading the file now can someone tell my how to flash the firmware succesfully?
model: xt1541 moto g 2015
pleas reply thanks

Help to change my firmaware
Dear Lost101,
First at all, thanks for your post.
I was trying to change the firmware of my phone, because I live in Argentina and use a different band for 4G LTE Spain (where I bought the phone).
My Moto G3 is XT1541, and I need the XT1540.
When I was changing the firmare, I had problems when I wrote "fastboot flash boot boot.img"... The command shows "FAILED". Then, I change the model, put again the firmare XT1541, and everything will be right again.
Do you know why I couldn't flash with XT1540?
Best regards and thanks in advance!

Demians1 said:
I was trying to change the firmware of my phone, because I live in Argentina and use a different band for 4G LTE Spain (where I bought the phone).
My Moto G3 is XT1541, and I need the XT1540.
When I was changing the firmare, I had problems when I wrote "fastboot flash boot boot.img"... The command shows "FAILED". Then, I change the model, put again the firmare XT1541, and everything will be right again.
Do you know why I couldn't flash with XT1540?
Click to expand...
Click to collapse
Flashing a different Model Firmware will not magically unlock or change Band support. Maybe with an unlocked Bootloader you can flash another Model's Firmware, but proceed with caution as you could end up with a dead phone.

Thanks Lost101.
Really I dont looking for change my firmware, but I suppuose that this could be a way to change the cell band....
Do you know or you heard about some way to change band support?

Demians1 said:
Really I dont looking for change my firmware, but I suppuose that this could be a way to change the cell band....
Do you know or you heard about some way to change band support?
Click to expand...
Click to collapse
There is this guide for Moto G (1st Gen) and this universal guide - however I don't know if either will work for you or what damage trying them might cause.

Thnak you very much Lost101!

just a small tip you can copy all text and flash then paste it in CMD it will flash all the partitions no need to enter manually one by one

Dear all,
I have a XT1541, and flash my Moto G3 with a XT1540 and XT1543 firmwares without problems. However I had to unblock the phone before flash it.
Lost101 I can confirm you that replace the model firmware DO NOT change the band frequencies... Thanks again for your warnings!

Very useful guide. Everything is working fine.

lost101 i have an error wit xt1544
see:
Code:
c:\celular>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing ´partition´...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.432s

douglaswfranciscon said:
lost101 i have an error wit xt1544
see:
Code:
c:\celular>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing ´partition´...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.432s
Click to expand...
Click to collapse
This usually occurs when attempting to Flash a Firmware Image older than the one currently installed. Unlocking Bootloader will often remove this error.
You can normally skip this command and still successfully flash Android.

lost101 said:
This usually occurs when attempting to Flash a Firmware Image older than the one currently installed. Unlocking Bootloader will often remove this error.
You can normally skip this command and still successfully flash Android.
Click to expand...
Click to collapse
Hello Lost101. I was download de Rom in other Site. The site is a clone for your site, but the rom is diferente.
Today I was downloades the rom in your site and have success...
Thanks!!!
My motoG are live again!

is it possible to just upgrade my phone without wiping everything? if so, what commands are required just to upgrade it?

krsmit0 said:
is it possible to just upgrade my phone without wiping everything? if so, what commands are required just to upgrade it?
Click to expand...
Click to collapse
Skip the following command: fastboot erase userdata

can i skip bootloader and recovery so they dont overright my custom recovery?

krsmit0 said:
can i skip bootloader and recovery so they dont overright my custom recovery?
Click to expand...
Click to collapse
Yes.

[GUIDE] Return to stock and "Official status" - Moto X 2014

Return to stock - Moto X 2014​
What you need:
Minimal ADB and Fastboot
Stock ROM Alternative 1 (Faster option)
Stock ROM Alternative 2 (Downloads speed are super slow if you are not premium)
Moto fastboot (mfastboot.exe) (This one is only needed if the file system.img is too big to flash (More than 500MB))
Steps:
Connect your phone to your computer and make sure to have "USB Debugging" enabled (About phone > Tap several times "Build number" > Go back > Developer options > Enable USB debugging)
Make sure your phone is at least 50% charged
Open ADB cmd (MAF32.exe)
Run this command to make sure it recognizes your phone.
Code:
adb devices
After it recognizes it, run the command (It should reboot into bootloader)
Code:
adb reboot bootloader
Unzip the downloaded STOCK ROM into the same folder as where you installed minimal ADB (C:\Program Files (x86)\Minimal ADB and Fastboot)
Open the "flashfile.xml" file with any text editor
The file tells you how to flash the files into your phone
Mine said:
Code:
fastboot oem fb_mode_set oem
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.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 erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
The sistem.img part was a big file divided into 9 files about 250MB each. If your system.img is bigger than 500MB you'll need to use mfastboot.
Do the commands one by one.
After you are done with everything, reboot and it should say in the Status: Official
EDIT 24/04/2016:
- Added faster alternative download to stock ROMS.

Tovagulet said:
Return to stock - Moto X 2014​
What you need:
Minimal ADB and Fastboot
Stock ROM (That's the only download page with like all the stock ROMs, downloads speed are super slow if you are not premium)
Moto fastboot (mfastboot.exe) (This one is only needed if the file system.img is too big to flash (More than 500MB))
Steps:
Connect your phone to your computer and make sure to have "USB Debugging" enabled (About phone > Tap several times "Build number" > Go back > Developer options > Enable USB debugging)
Make sure your phone is at least 50% charged
Open ADB cmd (MAF32.exe)
Run this command to make sure it recognizes your phone.
Code:
adb devices
After it recognizes it, run the command (It should reboot into bootloader)
Code:
adb reboot bootloader
Unzip the downloaded STOCK ROM into the same folder as where you installed minimal ADB (C:\Program Files (x86)\Minimal ADB and Fastboot)
Open the "flashfile.xml" file with any text editor
The file tells you how to flash the files into your phone
Mine said:
Code:
fastboot oem fb_mode_set oem
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.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 erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
The sistem.img part was a big file divided into 9 files about 250MB each. If your system.img is bigger than 500MB you'll need to use mfastboot.
Do the commands one by one.
After you are done with everything, reboot and it should say in the Status: Official
Click to expand...
Click to collapse
the easiest way is using RSDlite and chose flashfile.xml to flash. Done !

md07 said:
the easiest way is using RSDlite and chose flashfile.xml to flash. Done !
Click to expand...
Click to collapse
Not everybody uses windows. I am a linux user, so no RSDLite is available. Also not available for mac. This guide is great for people who can't use RSDLite or need to do specific steps only instead of blindly trusting RSDLite.
Sent from my XT1095 using Tapatalk

Thanks, I'm also not fond of flashing ROM images via program scripts, I prefer the old step by step method. :thumbup:

Any word on XT1095 or XT1097_retca-retca? How freaken hard is it to capture an OTA or factory image these days?

I still get "Software status: Modified"

md07 said:
the easiest way is using RSDlite and chose flashfile.xml to flash. Done !
Click to expand...
Click to collapse
AGISCI said:
Not everybody uses windows. I am a linux user, so no RSDLite is available. Also not available for mac. This guide is great for people who can't use RSDLite or need to do specific steps only instead of blindly trusting RSDLite.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Also, RSDLite does not work in Windows 10.
Thanks for tutorial.

Is this for Stock 6.0 Firmware : VICTARA_RETEU_XT1092_6.0_MPE24.49-18_cid7_CFC.xml.zip

thomstrack said:
Also, RSDLite does not work in Windows 10.
Click to expand...
Click to collapse
it works with Windows 10... try to upgrate RSD to the latest version

nikky2u20 said:
Is this for Stock 6.0 Firmware : VICTARA_RETEU_XT1092_6.0_MPE24.49-18_cid7_CFC.xml.zip
Click to expand...
Click to collapse
well, it's got all the right words and numbers (although the one I'm running from the TWRP method thread is MPE24.11-18, and this appears to be MPE24.49-18). I'm downloading it now - has anybody else tried it?

niciolaux said:
it works with Windows 10... try to upgrate RSD to the latest version
Click to expand...
Click to collapse
The latest version that I see is the 6.2.4, and does not work in Windows 10.
There is another version?

unfnknblvbl said:
I still get "Software status: Modified"
Click to expand...
Click to collapse
I think "Modified" means you unlocked the bootloader, right?
I used to successfully update my xt1095 to 5.1 by these steps:
unroot by using the uninstalling root function in the SEusers, and flash the stock recovery.img back.
download the OTA update, and let it flash my phone automatically.
got a stock 5.1. then you may do whatever you want.

unfnknblvbl said:
I still get "Software status: Modified"
Click to expand...
Click to collapse
+1
This method don't change to Status Official.
thomstrack said:
Also, RSDLite does not work in Windows 10.
Thanks for tutorial.
Click to expand...
Click to collapse
RSD Lite works perfectly in Windows 10.

I followed these steps, and reflashed to 5.1-21.3, then update to 21.6 (security patch).
Now I'm running 6.0! The OTA works!

We def need to get this stock image re-upped, because I could get gray hairs waiting for this to download... Anyone have any other links? Thanks

help!!! I downloaded the recovery image from the official motorola site, i have system image of 2 Gb and have no idea about how to flash the system image. I have a folder called windows(which was included in the recovery image zip that i downloaded) that folder contains a fastboot.exe file so is that the mfastoot file?If yes then how do i use it?
EDIT- Solved!

nikky2u20 said:
Is this for Stock 6.0 Firmware : VICTARA_RETEU_XT1092_6.0_MPE24.49-18_cid7_CFC.xml.zip
Click to expand...
Click to collapse
unfnknblvbl said:
well, it's got all the right words and numbers (although the one I'm running from the TWRP method thread is MPE24.11-18, and this appears to be MPE24.49-18). I'm downloading it now - has anybody else tried it?
Click to expand...
Click to collapse
Can confirm, this is the real deal. Works a treat, and none of those RPC errors that plagued me on the TWRP backup image.

I am on Brazilian frimware with 6.0 now on my device, but my actual model of the device is xt 1092 Indian version.
I want to go back to Indian frimware. Have anyone tried downgrading from 6.0 Brazilian frimware to 5.1 Indian frimware, is it possible? Is full image of 6.0 out for xt 1092, if so please share the link.
Sent from my XT1097 using Tapatalk

unfnknblvbl said:
Can confirm, this is the real deal. Works a treat, and none of those RPC errors that plagued me on the TWRP backup image.
Click to expand...
Click to collapse
Thnx for the info m8.
Could you upload it to something that is faster then filefactory perhaps? Cause this **** is SLOW
Thnx in advance
Cheers
Edit: it is also available here: https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!IkEVHRxS
With thnx to @salaesp for finding the MU folder

Used this firmware on my MotoX
VICTARA_RETEU_XT1092_6.0_MPE24.49-18_cid7_CFC.xml.zip
And was able to get back to the stock state. The Bootloader is still unlocked but that I guess I can lock via OEM lock way?
Since this is the latest one couldn't verify if the OTA works or not.

[GUIDE][addison] FACTORY STOCK IMAGES (ZIPs)

These have just about everything:
This is what you would use - using my guides - to flash your phone :
"firmware center"
https://firmware.center/firmware/Motorola/Moto Z Play/Stock/
"lolinet"
https://mirrors.lolinet.com/firmware/moto/addison/official/
- - - - - - - - - - - - - - - -
The rest of this is an old guide - use my or others later guides
- - - -
NEVER try to downgrade => permanently bricked phone.
ie if you're on nougat, DON'T try to go back to MM.
While I have not tested going from anything back to MM, I have certainly bounced back and forth many times between 7.x and 8.x bootloaders/ROMs - see my other guides.
windows: Remember if you are going to use RSD lite, use the latest one 6.2.4 from here http://rsdlite.en.lo4d.com/ , and start it in admin mode. Earlier versions won't recognize your phone. (boot phone to fastboot screen and usb plug to PC)( do lots of googling if you're using win10.)
Using RSD lite: [GUIDE][addison]RSD lite and adb - writing firmware to phone
OR
Using adb: This one is for India phone on 7.x . Remember never try to downgrade to MM or you will brick your phone. This was 7.x to 7.x .
How to go from Lineage OS 14.1 to stock? (Updated with the process & latest links)
Credit @kkube - see post 5 of above link.
Process to go from custom rom back to stock (August update)
There are several guides on going back from custom rom to full stock, but still I made this guide with latest links. I just went from LOS 14.1 back to full stock. Below is the step I took:
1) Download and install minimal ADB AND FASTBOOT
I used version 1.4.2 which is the latest version https://www.androidfilehost.com/?fid=745425885120698566
2) Download and install motorola drivers
https://motorola-global-portal.custh...ail/a_id/88481
3) Download the latest firmware
I used ADDISON_NPNS26.118-22-1 which has august security updates https://www.androidfilehost.com/?fid=673368273298986785
4) Extract the zip file (firmware) and move all its contents to the folder where you have installed minimal adb and fastboot
5) Create a text file, add the following text to it and save it as "launch.bat" in the same folder.
Quote:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
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 system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
6) Switch off your phone and open it in fastboot mode (press power and volume down button for few seconds after phone as switched off)
7) Connect your mobile to your computer
8) Click on the launch.bat file that you saved and it will install stock firmware on to your mobile. It will take a couple of minutes. (It will wipe everything on your mobile so take a backup of your important data)
9) Once the process is complete, it will ask you to enter any key, after which it will reboot itself.
Once rebooted, you will have full stock, non rooted, and latest firmware with august patches.
Click to expand...
Click to collapse

KrisM22 said:
These have just about everything:
You would likely only use these in a bricked situation and under guidance from someone experienced.
"firmware center"
https://firmware.center/firmware/Motorola/Moto Z Play/Stock/
"lolinet"
https://mirrors.lolinet.com/firmware/moto/addison/official/
NEVER try to downgrade => permanently bricked phone.
windows: Remember if you are going to use RSD lite, use the latest one 6.2.4 from here http://rsdlite.en.lo4d.com/ , and start it in admin mode. Earlier versions won't recognize your phone. (boot phone to fastboot screen and usb plug to PC)( do lots of googling if you're using win10.)
Click to expand...
Click to collapse
And make sure you use Motorola data cable - RSD is super sensitive to it! I nearly got grey before I actually found the reason RSD didn't recognize my phone - I used a random Chinese cable I found in the office.

okaban said:
And make sure you use Motorola data cable - RSD is super sensitive to it! I nearly got grey before I actually found the reason RSD didn't recognize my phone - I used a random Chinese cable I found in the office.
Click to expand...
Click to collapse
Yep, gotta try different cables!!!
Just used it because I forgot Alberto's "verity" patch. So 5 minutes later I'm looking at 7.1.1 Nov 1 which was where I was at before I unlocked BL. Easy!!!

KrisM22 said:
Yep, gotta try different cables!!!
Just used it because I forgot Alberto's "verity" patch. So 5 minutes later I'm looking at 7.1.1 Nov 1 which was where I was at before I unlocked BL. Easy!!!
Click to expand...
Click to collapse
hi friend this firmware also serves for moto z play mexico before installing Lineage OS I had NPNS26.118-22-2-12?

rubencho21 said:
hi friend this firmware also serves for moto z play mexico before installing Lineage OS I had NPNS26.118-22-2-12?
Click to expand...
Click to collapse
I would have no idea.
Do you know what channel you were on? I would guess retla but I only see 6.0.1 for that and you were on 7.1.1 so you certainly don't want to use that! @ TeamMex would probably have a much better idea. Or anyone in Mexico... Let us know if you find out!
EDIT also found this Nougat Moto Z on at&t mexico (this may be compatible with more models) but can't vouch for i since that's for Griffin - different phone.

If you follow my guide, you dont need a software channel..

SupahCookie said:
If you follow my guide, you dont need a software channel..
Click to expand...
Click to collapse
That guide is here [Guide] relock bootloader, and be back to lasted stock rom
You need to be in a custom (not stock) ROM
and need to have settings/developer options/"OEM unlocking" ON (and I assume android debugging (usb debugging) ON. both of those should always be on anyway... :|
I have not personally tried it but lots of folks there say it works.
Remember to give tons of thanks there if it works for you!!! _

KrisM22 said:
That guide is here https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190
Start from back of thread to find latest fix zip link.
latest was at https://forum.xda-developers.com/showpost.php?p=75099150&postcount=126
You need to be in a custom (not stock) ROM
and need to have settings/developer options/"OEM unlocking" ON (and I assume android debugging (usb debugging) ON. both of those should always be on anyway... :|
I have not personally tried it but lots of folks there say it works.
Click to expand...
Click to collapse
Or just use the normal download, its the same link

edit

KrisM22 said:
edit
Click to expand...
Click to collapse
I have stock with unlocked bootloader and rooted with magisk. I have updated to security Feb 2018 then my device just keeps booting to TWRP..
Will this work with unlocked bootoader?
Will this procedure relocked my bootloader?

jeprox said:
I have stock with unlocked bootloader and rooted with magisk. I have updated to security Feb 2018 then my device just keeps booting to TWRP..
Will this work with unlocked bootoader?
Will this procedure relocked my bootloader?
Click to expand...
Click to collapse
Depending on your channel I would use RSD Lite or SupahCookie's thread

bump but only for ROM links at top

KrisM22 said:
These have just about everything:
This is what you would use - using my guides - to flash your phone :
"firmware center"
https://firmware.center/firmware/Motorola/Moto Z Play/Stock/
"lolinet"
https://mirrors.lolinet.com/firmware/moto/addison/official/
- - - - - - - - - - - - - - - -
The rest of this is an old guide - use my or others later guides
- - - -
NEVER try to downgrade => permanently bricked phone.
ie if you're on nougat, DON'T try to go back to MM.
While I have not tested going from anything back to MM, I have certainly bounced back and forth many times between 7.x and 8.x bootloaders/ROMs - see my other guides.
windows: Remember if you are going to use RSD lite, use the latest one 6.2.4 from here http://rsdlite.en.lo4d.com/ , and start it in admin mode. Earlier versions won't recognize your phone. (boot phone to fastboot screen and usb plug to PC)( do lots of googling if you're using win10.)
Using RSD lite: [GUIDE][addison]RSD lite and adb - writing firmware to phone
OR
Using adb: This one is for India phone on 7.x . Remember never try to downgrade to MM or you will brick your phone. This was 7.x to 7.x .
How to go from Lineage OS 14.1 to stock? (Updated with the process & latest links)
Credit @kkube - see post 5 of above link.
Click to expand...
Click to collapse
Hi, Kris. IDK if you're still around but I'm wondering if I can use the RSDLite method and that Android 8 ADDISON_NPNS26.118-22-1 to flash Oreo onto my XT1635-02 software channel attmx which currently has Android 6.0.1 and baseband M8953_10203.02.04.42R ADDISON_ROW_CUST and build number of MPN24.104-25 ?
Can anyone give me some insight on this, please?