• XDA Forums have been migrated to XenForo. To discuss, report bugs and other issues, use this thread.

[GUIDE] Restore Moto E (2015) Stock Firmware

Lucas Eugene

New member
May 10, 2014
★ ★ ★ ★ ★ ★ ★ ★ ★ ★

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


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:
adb reboot-bootloader

You should see the Moto E bootloader screen with the following options:
Normal Powerup
Switch Console [NULL: null]
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:
cd c:\falcon_retgb_user_4.3_14.10.0Q3.X-76-LGG-8_54_release-keys-cid7-Retail_GB

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]
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
@lohanbarth for instructions and firmware images
Last edited:


New member
Mar 13, 2015
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.



New member
Sep 11, 2010
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?


New member
Jan 2, 2014
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:

[...] 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]
mfastboot oem fb_mode_set
mfastboot oem config carrier vzw
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.

Last edited:


New member
Jan 21, 2012
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...
Last edited: