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 Nexus 6 / Moto X Pro
The Motorola Nexus 6 / Moto X Pro (filename codename tag: shamu) is Google and Motorola's 2014 flagship, released in November 2014 (global Nexus 6 launch; this China-market Moto X Pro/XT1115 variant followed the same shamu hardware), powered by the Qualcomm Snapdragon 805 (APQ8084) chipset. In China, this exact shamu hardware was retailed as the Moto X Pro rather than "Nexus 6," under its own model number, XT1115, tied to CID11 and the RETCN region tag. Globally, the same hardware shipped under different model numbers as the Nexus 6.
Every build in this archive is a CFC.xml-style mfastboot package — the China-market distribution channel for this device — rather than Google's factory-image/flash-all.sh method used for the globally-sold Nexus 6. There is no EDL-mode package for this device in the source archive. The Prerequisites and Firmware Package sections below explain how to confirm you have the right build before you begin.
Which Flash Mode Should You Use?
mfastboot (CFC.xml Package)
The method for every file in this China-market 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.
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 805 chipset is EDL-capable in principle, but no EDL-mode package exists in this archive — every known file for this build 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.
Download a build from the firmware table below matching XT1115/CID11/RETCN. Confirm in Settings → About Phone → Model Number.
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 Nexus 6 / Moto X Pro — Quick Overview
These 6 steps are tailored to the Motorola Nexus 6 / Moto X Pro (APQ8084). For screenshots, an interactive checklist, and troubleshooting, open the full Motorola flashfile.bat / CFC XML Script guide.
-
Confirm your XT1115 model number and CID11/RETCN tag
-
Install the Motorola USB drivers and the mfastboot binary
-
Download a build from the firmware table below
-
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 APQ8084
The shamu 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 805 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 Nexus 6 / Moto X Pro Firmware Versions
All 3 known files for the Motorola Nexus 6 / Moto X Pro — this is the smallest archive on the network, so nothing has been trimmed to a subset.
| Version | Region | Android Version | Size | MD5 | Download |
|---|---|---|---|---|---|
LXG22.67-7 |
XT1115 — RETCN (China, CID11) | Android 5.0.2 | 624 MB | — | ⬇️ Download |
LXG22.67-7 |
XT1115 — RETCN (China, CID11), MobileGuru4.com mirror upload | Android 5.0.2 | 625 MB | — | ⬇️ Download |
LXG22.67-7.1 |
XT1115 — RETCN (China, CID11, subsidy-DEFAULT) | Android 5.0.2 | 624.6 MB | 578c5c3c0f51b41cf4bf18d177fed407 |
⬇️ Download |
This device has 3 known files, all for one model number and region. See the complete archive on AndroidFirmwareFile.com →
Common Errors on the Motorola Nexus 6 / Moto X Pro
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 Google/Motorola logo
An interrupted flash can leave a partition inconsistent. Re-run the full CFC.xml script from scratch with the same or the alternate row above — 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-mismatched package — confirm CID11/RETCN on your fastboot screen matches before retrying, and re-flash using one of the exact builds in the firmware table below.
For the full mfastboot error database: mfastboot / CFC.xml Error Directory →
Frequently Asked Questions — Motorola Nexus 6 / Moto X Pro
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.
That script and image set are built for the globally-sold Nexus 6 model numbers (XT1100, XT1103, and other carrier variants) — they're not compatible with this China-market XT1115/CID11 build, and flash-all.sh will typically fail a device-ID or partition-table check rather than partially flash. Use the CFC.xml/mfastboot method and one of the builds in the firmware table below instead — they're packaged specifically for this model number and CID.
No — reflashing the stock CFC.xml package over mfastboot does not itself require an unlocked bootloader, since it writes the same signed images Motorola ships. An unlock is only needed for a custom recovery or ROM. Whether this China-market variant follows the same no-token fastboot oem unlock path as the globally-sold Nexus 6, or Motorola's token-based motorola.com/unlock process instead, is untested on this specific build — but it 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.