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 X4
The Motorola Moto X4 (filename codename tag: payton) is Motorola's 2017 mid-range flagship, released in October 2017, powered by the Qualcomm Snapdragon 630 (SDM630) chipset. Motorola distributed it across six model numbers represented in this archive — XT1900-1 (North America: US retail, Google Fi, Amazon Prime Exclusive), XT1900-2 (Asia-Pacific and India), XT1900-4 (Latin America open-market), XT1900-5 (Europe single-SIM), XT1900-6 (Mexico and Brazil), and XT1900-7 (Poland and Europe dual-SIM) — each tied to a specific region/subsidy tag rather than a numeric CID.
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 payton 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, generally confirmed for this device generation. On the Amazon Prime Exclusive build (XT1900-1 AMZ), confirm the app actually detects and repairs your unit before relying on it as your only option — fall back to mfastboot, and expect the community bootloader-unlock workaround if you also need an unlock.
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 630 chipset is EDL-capable in principle, but no EDL-mode package exists in this archive — every known payton 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 and region/subsidy tag. Confirm in Settings → About Phone → Model Number. Six builds share an identical size but span three different model numbers — check the model number first.
A data-capable USB-C 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 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 X4 — Quick Overview
A condensed step-by-step summary specific to the Motorola Moto X4. Follow the full Motorola flashfile.bat / CFC XML Script guide for screenshots, an interactive progress checklist, and complete troubleshooting.
-
Identify your exact model number and subsidy/regulatory tag
-
Install the Motorola USB drivers and the mfastboot binary
-
Download the CFC.xml package matching your model + region
-
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 SDM630
Every payton CFC.xml package extracts to a top-level CFC.xml file 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 630 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 X4 Firmware Versions
A representative build for each confirmed model number of the Motorola Moto X4. Always verify the model number and region tag match your device before flashing.
| Version | Region | Android Version | Size | MD5 | Download |
|---|---|---|---|---|---|
PPWS29.69-39-6-6 |
XT1900-1 — RETUS (US retail, subsidy-DEFAULT) | Android 9.0 | 1774.8 MB | — | ⬇️ Download |
PPWS29.69-26-6 |
XT1900-2 — RETAPAC (Asia-Pacific retail, subsidy-DEFAULT) | Android 9.0 | 1975.8 MB | — | ⬇️ Download |
PPWS29.69-40-3-1 |
XT1900-4 — OPENMX (Open Mexico, subsidy-DEFAULT) | Android 9.0 | 1986.5 MB | — | ⬇️ Download |
PPWS29.69-37-5 |
XT1900-5 — RETEU, single-SIM (Europe retail, subsidy-DEFAULT) | Android 9.0 | 1988 MB | — | ⬇️ Download |
PPWS29.69-26-6 |
XT1900-6 — RETBR (Brazil retail, HDTV variant, subsidy-DEFAULT) | Android 9.0 | 1975.8 MB | — | ⬇️ Download |
PPWS29.69-37-5 |
XT1900-7 — RETEU, dual-SIM (Europe retail, subsidy-DEFAULT) | Android 9.0 | 1988 MB | — | ⬇️ Download |
This device has 14 known files across six confirmed model numbers. See the complete archive on AndroidFirmwareFile.com →
Common Errors on the Motorola Moto X4
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-C. Confirm the Motorola USB driver is installed and the phone shows up in Device Manager. Use a data-capable USB-C cable and a USB 2.0/3.0 port directly on the motherboard rather than a hub.
Script completes but device won't boot past the Motorola logo
An interrupted or model-mismatched flash can leave a partition inconsistent. Re-run the full CFC.xml script from scratch with the exact package matching your model number and region — 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 model- or region-mismatched CFC.xml package — several builds share a size and build number across different model numbers. Re-flash using the exact package matching your model number and region from the firmware table below.
For the full mfastboot error database: mfastboot / CFC.xml Error Directory →
Frequently Asked Questions — Motorola Moto X4
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 model number and, in some cases, further scoped by regional radio/carrier provisioning even where the build number and file size match another build exactly. A mismatch means the package wasn't built for your exact model number — re-check it against the fastboot screen before retrying, rather than assuming any same-size CFC.xml package will work.
No — reflashing the stock CFC.xml package over mfastboot does not itself require an unlocked bootloader on any of the six model numbers, since it writes the same signed images Motorola ships. An unlock is only needed for a custom recovery or ROM. Separately, the Amazon Prime Exclusive (XT1900-1 AMZ) build has historically needed a community workaround rather than the standard motorola.com/unlock process for that specific step — this doesn't affect the stock CFC.xml reflash covered here either way.
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.