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 G (1st Gen)
The Motorola Moto G (1st Gen) family encompasses both the original 3G release (codename: falcon) and the subsequent 4G LTE refresh (codename: peregrine), built on the Qualcomm Snapdragon 400 processor architecture.
Official stock firmware for these models is distributed as CFC.xml / flashfile.xml service packages flashed via Motorola's mfastboot binary. The sections below provide instructions for identifying your platform, setting up required drivers, and executing a complete software restore.
Which Flash Mode Should You Use?
mfastboot (CFC.xml / flashfile Package)
The standard factory restore method for all Moto G 1st Gen models. Runs the official XML script via Motorola's mfastboot tool to write partition table, bootloader, kernel, system sparsechunks, and modem images. Erases all userdata.
Manual Fastboot (Partition-by-Partition)
Advanced alternate method where individual image files (gpt.bin, motoboot.img, boot.img, recovery.img, system sparsechunks, NON-HLOS.bin, fsg.mbn) are flashed manually in command prompt.
EDL / QFIL (Not Applicable)
Qualcomm Snapdragon 400 hardware supports Emergency Download (EDL 9008) mode at the silicon level, but Motorola factory packages are distributed as fastboot CFC.xml archives. QFIL recovery requires specialized signed Firehose programmers not provided in standard stock archives.
What You Need Before Flashing
Motorola mfastboot and driver installers are configured for Windows environments. Use native USB 2.0 ports for optimal fastboot stability.
Download the specific firmware build matching your model (XT1028-XT1045) and carrier CID branch tag. Never mix 3G falcon and 4G peregrine files.
A dependable data cable is essential. Avoid charge-only cords or unpowered hubs that can drop connection during sparsechunk transfers.
The Moto G 1st Gen has a non-removable 2070mAh battery. Ensure sufficient charge to prevent mid-flash shutdown while writing critical bootloader or modem partitions.
A complete stock reflash formats cache and userdata. Back up photos, contacts, and personal files before beginning the procedure.
How to Flash the Motorola Moto G (1st Gen) — Quick Overview
A condensed step-by-step summary specific to the Motorola Moto G (1st Gen). Follow the full Motorola flashfile.bat / CFC XML Script guide for screenshots, an interactive progress checklist, and complete troubleshooting.
-
Identify your hardware platform and exact XT model number
-
Install Motorola USB Drivers and obtain the mfastboot tool
-
Download and extract the matched CFC.xml firmware package
-
Connect in bootloader mode and execute the flash script
-
Allow partition writing to finish without interruption
-
Reboot and verify baseband and IMEI status
Finding the Firmware Package for
Motorola Moto G firmware archives contain XML service definitions (CFC.xml or flashfile.xml) along with partition binaries (gpt.bin, motoboot.img, boot.img, recovery.img, NON-HLOS.bin, fsg.mbn, and chunked system files such as system.img_sparsechunk.0 through .3). These Qualcomm packages do not use MediaTek scatter files. Always extract the ZIP archive into a dedicated folder on your computer before executing flashing tools.
Motorola Moto G (1st Gen) Firmware Versions
A representative build for each confirmed model number of the Motorola Moto G (1st Gen) (spanning 3G falcon and 4G LTE peregrine lines). Always verify the platform and branch match your device before flashing.
| Version | Region | Android Version | Size | MD5 | Download |
|---|---|---|---|---|---|
LPBS23.13-33.7-2 |
XT1028 — VERIZON (Verizon Wireless USA, 3G CDMA) | Android 5.1 | 589 MB | e4f9765c7c745a17bf23a9bdf76ac7a9 |
⬇️ Download |
LPBS23.13-33.6-2 |
XT1031 — USC (U.S. Cellular, 3G CDMA) | Android 5.1 | 559.5 MB | — | ⬇️ Download |
LPBS23.13-56-2 |
XT1032 — RETEU (Retail Europe, 3G Single-SIM) | Android 5.1 | 553 MB | 93c2ea622304dab2ecf1f8a3dd2e1fd7 |
⬇️ Download |
LPBS23.13-56-2 |
XT1033 — ASIA (Retail Asia / India, 3G Dual-SIM) | Android 5.1 | 552.2 MB | — | ⬇️ Download |
LPBS23.13-57-2 |
XT1034 — RETCA (Retail Canada, 3G AWS) | Android 5.1 | 567 MB | — | ⬇️ Download |
LPB23.13-17 |
XT1039 — RETEU (Retail Europe, 4G LTE) | Android 5.1 | 587 MB | — | ⬇️ Download |
LPBS23.13-35.5-1 |
XT1040 — RETBR (Retail Brazil, 4G LTE) | Android 5.1 | 583 MB | — | ⬇️ Download |
LPBS23.13-60-1 |
XT1042 — USC (U.S. Cellular, 4G LTE CDMA) | Android 5.1 | 584 MB | ebb2b163c115e01a9c18d9d06d48ee22 |
⬇️ Download |
LPBS23.13-61-1 |
XT1045 — RETUS (Retail USA, 4G LTE) | Android 5.1 | 585 MB | 5a2b8df6428117d9316098c3f64c5afb |
⬇️ Download |
This device family has 63 known files across nine confirmed XT model numbers. See the complete archive on AndroidFirmwareFile.com →
Common Errors on the Motorola Moto G (1st Gen)
mfastboot: "FAILED (remote: unknown command)" or immediate script termination
Motorola CFC.xml scripts contain proprietary bootloader commands (such as motoboot flashing and getvar verification). Ensure you are using Motorola's mfastboot executable located in the same directory as the firmware files, not stock fastboot from Android platform-tools.
Device not detected / "fastboot devices" returns an empty line
Power down completely and enter bootloader mode with Volume Down + Power before plugging in. Verify that Motorola USB drivers are installed and the device appears under Windows Device Manager as "Motorola Fastboot Interface". Avoid USB 3.0 ports and hubs.
Device stuck in a bootloop at the Motorola logo after flashing
Often caused by residual cache or leftover data partition mismatches between Android versions (e.g., upgrading from KitKat to Lollipop). Boot back into fastboot mode and execute "fastboot erase cache" followed by "fastboot erase userdata".
Baseband Unknown / No Service after flash
Occurs when the modem partition is skipped or when cross-flashing regional branch variants with incompatible radio calibrations. Re-flash NON-HLOS.bin and fsg.mbn using the exact firmware package intended for your carrier/region.
For the full mfastboot error database: mfastboot / CFC.xml Error Directory →
Frequently Asked Questions — Motorola Moto G (1st Gen)
This usually occurs when using a standard fastboot binary rather than Motorola's mfastboot, or when flashing over a USB 3.0/hub connection. Use a direct motherboard USB 2.0 port, verify you are running mfastboot.exe, and ensure the system sparsechunks are flashed in strict numerical order (system.img_sparsechunk.0, .1, .2, .3).
No. Falcon (Snapdragon 400 MSM8226/MSM8626) and peregrine (Snapdragon 400 MSM8926 LTE) have fundamentally different modem architectures, partition partition tables, and radio hardware. Cross-flashing between falcon and peregrine risks hard-bricking the modem partition or rendering cellular connectivity permanently inoperable.
No. Flashing stock firmware overwrites the software partitions (boot, recovery, system, radio) but leaves the bootloader state untouched. To relock the bootloader, you must run "fastboot oem lock begin", flash the matching stock package completely, and finalize with "fastboot oem lock".
This typically indicates a carrier/CID branch mismatch or cross-flashing single-SIM (XT1032) firmware onto a dual-SIM (XT1033) device. Dual-SIM models require specific modem configuration files (NON-HLOS.bin and fsg.mbn) built for dual-baseband operation. Re-flash the exact package matching your model number and regional CID.
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.