Crucial Warning: This page shows 3 representative builds out of 8 known files across three model numbers — XT1581 in particular covers two unrelated regions (China and Mexico) under one model number, illustrating how a shared model number doesn't guarantee interchangeable firmware on this device. Verify your device's own CID against the fastboot screen before running any of the flashing methods below.
Download Firmware for Motorola Moto X Force / Droid Turbo 2 (XT1580/XT1581/XT1585 kinzie)
XT1580 also ships in Mexico (RETMX, including an Iusacell-specific build) and Latin America (RETLA, single- and dual-SIM) builds sharing the same underlying build tag — see the full archive linked above for the exact one.
↓ DownloadXT1581 is also used for a separately-packaged Mexico build (CID12) — the shared model number covers two different regions, not one; see the full archive linked above for both.
↓ DownloadThe only build in this archive with a self-supplied checksum — not interchangeable with XT1580/1581 builds regardless of matching CID.
↓ DownloadCompatibility & Bootloader Notes
Stock firmware replaces the system, boot, and radio images only. Bootloader lock state is controlled separately through fastboot oem lock/unlock commands and Motorola's official unlock-token process, not by flashing firmware. Treat bootloader unlock as not guaranteed on XT1585 (Droid Turbo 2, Verizon) specifically, unlike the other two model numbers.
Preparation checklist for Motorola Moto X Force / Droid Turbo 2 (XT1580/XT1581/XT1585 kinzie)
- Confirm the model number (XT1580, XT1581, or XT1585) from the device label, Settings > About phone, or the fastboot screen.
- Record the CID shown on the fastboot screen — XT1581 units in particular can be either CID11 (China) or CID12 (Mexico).
- Install Motorola USB drivers and the mfastboot binary.
- Back up accessible user data before flashing — every method below wipes it.
How to Flash Motorola Moto X Force / Droid Turbo 2 (XT1580/XT1581/XT1585 kinzie)
Motorola Rescue and Smart Assistant
- Install Motorola Rescue and Smart Assistant on a Windows or Mac PC. This is a 2015 device, and RSA's published coverage skews toward newer Motorola phones — try it first since it's the simplest option, but have the manual method below ready in case it doesn't detect your XT1580/1581/1585 unit.
- Power off the kinzie unit, hold Volume Down + Power to enter the bootloader, then connect it via USB
- In the app, select Motorola and choose the software repair/rescue option — it should detect your exact model automatically if supported
- Confirm the repair and let the tool download and flash the matching stock firmware for your unit over fastboot without disconnecting the device
- Once it finishes and the phone reboots, confirm the Android version landed correctly under Settings > About phone and that mobile signal appears
flashfile.bat / CFC XML fastboot script
- Install the Motorola USB drivers and the mfastboot binary on your PC, then extract the kinzie package matching your exact model number and CID — XT1581 in particular covers two unrelated regions (China CID11, Mexico CID12) under one model number, so match the CID exactly, not just the model
- Boot the phone into fastboot mode (Volume Down + Power) and connect it with a reliable USB cable
- Most kinzie packages bake the CID into the filename itself in standard CFC.xml naming, so double-check it matches the fastboot screen before running flashfile.bat from a command prompt in that folder
- The Mexico XT1581 build ships under a differently formatted filename without the CFC.xml suffix — same flashing procedure once extracted, just a different-looking archive name
- Let the device reboot once the script completes
Manual fastboot flash (advanced, partition-by-partition)
- Extract the firmware zip and identify the individual images your kinzie package includes: boot.img, system.img, and the MSM8994 modem/NON-HLOS.bin radio partition
- Boot into fastboot mode and confirm the unit is detected with fastboot devices
- Flash only the partitions you need — for example fastboot flash boot boot.img, then fastboot flash system system.img — using images from the CID-matched package confirmed above
- Optionally run fastboot erase cache and fastboot erase userdata for a clean start on this device — this wipes data
- Reboot with fastboot reboot and confirm the boot loop or boot-image issue on this Moto X Force / Droid Turbo 2 unit is resolved
Frequently Asked Questions
Try Rescue and Smart Assistant first if you just want stock firmware back on a working fastboot connection — it handles detection and the correct package for you when it supports the device. Since this is a 2015 model, go straight to the manual flashfile.bat or partition-by-partition method if RSA doesn't recognize your unit, or if you need the Mexico XT1581 build, which RSA is unlikely to offer given its non-standard packaging.
Motorola's mfastboot script checks the package's embedded CID against what's already programmed on your device and refuses to proceed if they don't match — the flash fails validation rather than partially installing and leaving the phone in a bad state. The fix is downloading the package with the matching CID, not a special recovery step.
The three methods below apply to every kinzie build regardless of which of the 8 files you end up downloading — the three rows above are examples of the CID-locking pattern, not a limit on which builds these steps work for. If your exact branch isn't one of the three shown, use the archive crosslink to find it, then follow the same method here.