Before you flash: Flashing firmware will erase all data on your device. Back up contacts, photos, and apps before proceeding. FlashGuideHub is not responsible for any damage caused by following this guide.
About the Motorola Moto X Play / Droid Maxx 2
The Motorola Moto X Play / Droid Maxx 2 (filename codename tag: lux) is Motorola's 2015 mid-range flagship, released in July 2015 (announced; Canada/Europe/Latin America August 2015; Droid Maxx 2 for Verizon US October 2015), powered by the Qualcomm Snapdragon 615 (MSM8939) chipset. Motorola distributed it across four model numbers — XT1562 (Europe/Asia), XT1563 (Latin America/Canada, spanning many carrier subsidy branches), XT1564 (LRA), and XT1565 (Droid Maxx 2, Verizon-exclusive US, uniquely CDMA-capable) — each tied to a specific CID and, on XT1563, further scoped by carrier subsidy.
Every build in this archive is a CFC.xml service package flashed with Motorola's mfastboot binary — there is no EDL-mode package for this device in the source archive. The Prerequisites and Firmware Package sections below explain how to identify your exact variant before you begin.
Which Flash Mode Should You Use?
mfastboot (CFC.xml Package)
The standard method for every lux build in this archive. Runs the CFC.xml package's flash script with Motorola's mfastboot binary, writing system, boot, and radio images in sequence. Erases all user data.
Motorola Rescue and Smart Assistant
Motorola's official PC repair/reflash tool, confirmed for the Moto X platform generally. On the Droid Maxx 2 (XT1565), confirm the app actually detects your unit before relying on it as your only option — fall back to mfastboot if it doesn't.
Manual Fastboot (Partition-by-Partition)
An advanced alternate using the individual partition images (boot.img, system.img, and the radio/modem image) inside the same extracted CFC.xml package, flashed one at a time with standard fastboot. Useful if the mfastboot script itself won't run on your OS. Requires an unlocked bootloader and erases all user data.
EDL / QFIL (Not Applicable)
This device's Snapdragon 615 chipset is EDL-capable in principle, but no EDL-mode package exists in this archive — every known lux file is a CFC.xml mfastboot package. QFIL/EDL would only apply for recovering a hard-bricked unit with no fastboot access, which requires a Qualcomm EDL service package not currently listed here.
What You Need Before Flashing
Motorola's mfastboot binary and USB drivers are built for Windows; install the Motorola USB drivers before connecting the phone. Rescue and Smart Assistant also supports Mac.
Download the CFC.xml package that matches your exact model number, CID, and carrier subsidy tag. Confirm in Settings → About Phone → Model Number. Several XT1563 builds share an identical size but a different subsidy — check both fields, not just the size.
A data-capable USB cable is essential — charge-only cables will not be recognized by mfastboot. Use the original Motorola cable where possible, and connect directly to a USB 2.0 port rather than a hub.
The mfastboot script writes several partitions in sequence over a few minutes. This device has a non-removable battery, so a mid-flash power interruption carries more risk than on removable-battery hardware — charge to at least 30% first.
The mfastboot CFC.xml flow wipes user data. Back up photos to Google Photos, contacts to Google Contacts, and any local files to a PC before beginning.
How to Flash the Motorola Moto X Play / Droid Maxx 2 — Quick Overview
These 6 steps are tailored to the Motorola Moto X Play / Droid Maxx 2 (MSM8939). For screenshots, an interactive checklist, and troubleshooting, open the full Motorola flashfile.bat / CFC XML Script guide.
-
Identify your exact model number, CID, and carrier subsidy tag
-
Install the Motorola USB drivers and the mfastboot binary
-
Download the CFC.xml package matching your model + CID + subsidy
-
Boot to the bootloader and flash with mfastboot
-
Wait for the script to finish, then boot
-
Confirm IMEI/network on first boot
Finding the Firmware Package for
Every lux CFC.xml package extracts to a top-level CFC.xml file (some builds also ship the identical script as flashfile.xml, and the four RETCA builds ship as CFC_V2.xml) alongside a servicefile.xml and the individual partition images — boot.img, system.img, the radio/modem image, and so on — that mfastboot flashes in sequence. There is no scatter file here; that format is MediaTek-specific and does not apply to this Qualcomm Snapdragon 615 device. Fully extract the archive to its own folder on your PC before running anything — mfastboot needs to read the CFC.xml script and the partition images directly from disk, not from inside a compressed archive.
Motorola Moto X Play / Droid Maxx 2 Firmware Versions
A representative build for each confirmed model number of the Motorola Moto X Play / Droid Maxx 2. Always verify the CID and carrier subsidy match your device before flashing.
| Version | Region | Android Version | Size | MD5 | Download |
|---|---|---|---|---|---|
NPD26.48-24-1 |
XT1562 — RETEU (Europe-wide retail, CID7, subsidy-DEFAULT) | Android 7.1.1 | 1154.7 MB | — | ⬇️ Download |
NPD26.48-24-1 |
XT1563 — RETAIL, DS (CID12, subsidy-DEFAULT, generic) | Android 7.1.1 | 1204.1 MB | — | ⬇️ Download |
NCA26.48-41 |
XT1564 — LRA (CID9, subsidy-DEFAULT) | Android 7.1.1 | 1156.7 MB | — | ⬇️ Download |
MCD24.294-4-6 |
XT1565 — VERIZON (Droid Maxx 2, CID2, subsidy-DEFAULT) | Android 6.0.1 | 1506.9 MB | e55b04d248bd7ebec93e107c12403227 |
⬇️ Download |
This device has 27 known files across four confirmed model numbers. See the complete archive on AndroidFirmwareFile.com →
Common Errors on the Motorola Moto X Play / Droid Maxx 2
mfastboot: "FAILED (remote: unknown command)" or the script exits immediately
Confirm you're running Motorola's mfastboot binary from the same folder the CFC.xml package extracted into, not a stock Android SDK platform-tools fastboot.exe. Standard fastboot does not recognize several of the OEM commands Motorola's CFC.xml scripts issue.
Device not detected / mfastboot devices returns nothing
Power the phone off completely, then hold Volume Down + Power to boot straight to the bootloader/fastboot screen before connecting USB. Confirm the Motorola USB driver is installed and the phone shows up in Device Manager. Use a data-capable USB cable and a USB 2.0 port directly on the motherboard rather than a hub.
Script completes but device won't boot past the Motorola logo
An interrupted or CID/subsidy-mismatched flash can leave a partition inconsistent. Re-run the full CFC.xml script from scratch with the exact package matching your model, CID, and subsidy tag — don't assume a partial re-flash of just one partition will fix it.
No signal / wrong IMEI after flashing
Usually caused by flashing a CID- or subsidy-mismatched CFC.xml package — each branch carries its own radio provisioning, and on XT1563 several same-size builds differ only by subsidy. Re-flash using the exact package matching your model, CID, and subsidy tag from the firmware table below.
For the full mfastboot error database: mfastboot / CFC.xml Error Directory →
Frequently Asked Questions — Motorola Moto X Play / Droid Maxx 2
Not necessarily. A stall or mid-script error usually means a driver or cable issue, not a bricked device — as long as the phone still shows the bootloader/fastboot screen when powered on, it can be re-flashed. Reconnect, confirm mfastboot devices lists the phone, and re-run the same CFC.xml script from the start rather than trying to resume partway through.
This device's firmware is locked per-CID and, on several XT1563 builds, further scoped by carrier subsidy even where the CID and file size match another build exactly. A mismatch means the package's embedded CID or subsidy doesn't match what's already programmed on your device — re-check both against the fastboot screen before retrying, rather than assuming any same-size CFC.xml package for your model number will work.
No — reflashing the stock CFC.xml package over mfastboot does not itself require an unlocked bootloader on any of the four model numbers, since it writes the same signed images Motorola ships. An unlock is only needed for a custom recovery or ROM. Separately, XT1565 (Droid Maxx 2, Verizon) may have restricted official unlock eligibility through motorola.com/unlock compared to the unlocked retail model numbers — this doesn't affect the stock CFC.xml reflash covered here either way.
XT1565 is the only model number with CDMA radio provisioning for Verizon; the other three model numbers are GSM/LTE-only builds and don't carry that provisioning. Beyond the CID mismatch that should have blocked the flash in the first place, a successfully-forced cross-flash would leave the modem partition without CDMA support. Re-flash the correct XT1565/VERIZON CFC.xml package to restore it.
Ready to Flash?
Follow the full step-by-step Motorola flashfile.bat / CFC XML Script guide with interactive progress tracking, prerequisite checklist, and complete troubleshooting.