ThisCalculator

Everyday

How to Root Motorola Moto X Force on Marshmallow

Updated · Standard formula, shown below

How to Root Motorola Moto X Force on Marshmallow

This guide walks you through rooting the Motorola Moto X Force running Android 6.0 Marshmallow. Rooting gives you superuser access, allowing you to remove bloatware, install root-only apps, and customize the system. Before starting, understand that rooting voids your warranty and carries a small risk of bricking your device. You’ll need an unlocked bootloader, which also voids your warranty and wipes all data. Proceed only if you’re comfortable with these risks.

What You’ll Need

  • A Moto X Force (XT1580) with Android 6.0 Marshmallow (build number starting with MPHS24.49).
  • A Windows PC (or a Mac/Linux with equivalent tools).
  • A USB cable that supports data transfer.
  • Motorola USB drivers installed on your PC.
  • Minimal ADB and Fastboot tools (or full Android SDK platform-tools).
  • An unlocked bootloader – follow Motorola’s official unlock process on their website (requires creating an account and accepting the warning).
  • Latest TWRP recovery image for the Moto X Force (e.g., twrp-3.x.x-kinzie.img).
  • Latest Magisk ZIP (e.g., Magisk-vXX.X.zip) – use a version compatible with Marshmallow.
  • Backup of all important data – the bootloader unlock wipes your phone.

Step-by-Step

  1. Enable Developer Options and USB Debugging: Go to Settings > About Phone and tap “Build number� 7 times. Then go to Settings > Developer Options and enable “USB debugging� and “OEM unlocking� (if available).
  2. Unlock the Bootloader: On your PC, open a command prompt in the folder with ADB/Fastboot. Connect your phone in fastboot mode (power off, then hold Volume Down + Power). Run fastboot devices to confirm it’s detected. Run fastboot oem get_unlock_data – copy the entire string shown. Go to Motorola’s unlock website, sign in, paste the string, and you’ll receive an unlock code. Run fastboot oem unlock UNIQUE_CODE (replace with your code). The phone will wipe and reboot. Re-enable USB debugging after reboot.
  3. Boot TWRP Temporarily: Download the TWRP image and place it in your ADB folder. Reboot to fastboot (Volume Down + Power). Run fastboot boot twrp.img (replace with your TWRP filename). This boots TWRP without flashing it, which is safer for testing.
  4. Flash TWRP Permanently (Optional but Recommended): Once TWRP boots, you can flash it permanently by going to Advanced > ADB Sideload or by using fastboot flash recovery twrp.img in fastboot. Then reboot to recovery to verify.
  5. Backup Your Current System: In TWRP, tap “Backup� and select Boot, System, and Data. Swipe to back up to your SD card or internal storage. This is your safety net.
  6. Install Magisk: In TWRP, tap “Install� and select the Magisk ZIP you downloaded. Swipe to confirm the flash. Magisk will install and may ask to patch the boot image – proceed.
  7. Wipe Cache/Dalvik: After flashing, go to “Wipe� > “Advanced� and select Dalvik/ART Cache and Cache. Swipe to wipe.
  8. Reboot System: Tap “Reboot� > “System�. The first boot may take several minutes – be patient.
  9. Verify Root: Once booted, install the Magisk Manager app (if not already installed) and open it. It should show “Magisk installed� and “SafetyNet� status (if supported). You can also use a root checker app from the Play Store.

Common Mistakes

  • Not Unlocking Bootloader First: Flashing TWRP or Magisk on a locked bootloader will fail or cause a bootloop.
  • Using Wrong TWRP Image: The Moto X Force has a specific TWRP build (codename “kinzieâ€�). Using another model’s image can brick your device.
  • Skipping the Backup: If something goes wrong, without a backup you may lose all data.
  • Forgetting to Enable USB Debugging: ADB commands won’t work if debugging is off.
  • Using an Incompatible Magisk Version: Newer Magisk versions may require Android 8.0+. Use a version that supports Marshmallow (Magisk v20.4 or older).

Tips

  • Keep your phone charged above 70% during the process to avoid power loss.
  • Use the original Motorola USB cable or a high-quality one to avoid connection drops.
  • If you’re not comfortable with command line, consider using a one-click root tool like SuperSU, but be aware they may not be as reliable.
  • After rooting, install a firewall app to control which apps have root access.
  • Remember that OTA updates will likely fail after rooting – you’ll need to unroot or flash stock to update.

Troubleshooting

  • Device not detected in fastboot: Install or reinstall Motorola USB drivers. Try a different USB port (preferably USB 2.0). Run fastboot devices to check.
  • Unlock code not working: Make sure you copied the entire unlock string, including the “#â€� symbols. Retry the fastboot oem get_unlock_data command.
  • Bootloop after flashing: Boot back into TWRP (hold Volume Down + Power, then select Recovery). Restore the backup you made, or reflash the stock boot image via fastboot.
  • Magisk Manager says “Magisk not installedâ€�: Reflash Magisk in TWRP, ensuring you’re using the correct version. Also, try wiping cache and Dalvik again.
  • SafetyNet fails: This is normal with root. You can enable MagiskHide (if available in your Magisk version) to hide root from some apps.
  • Wi-Fi or Bluetooth not working: This may indicate a corrupted boot image. Reflash the stock boot image or restore your backup.

Frequently Asked Questions

Q: Does rooting delete my data?
A: Unlocking the bootloader wipes all data. Rooting itself (flashing Magisk) does not, but always backup first.

Q: Can I unroot later?
A: Yes. You can flash the stock boot image or use Magisk Manager to uninstall. Unrooting restores your device to stock, but the bootloader remains unlocked.

Q: Will I still get OTA updates after rooting?
A: Usually not. OTA updates require a stock system. You can manually flash updates or revert to stock.

Q: Is it safe to root my daily driver?
A: Rooting is generally safe if you follow instructions carefully. The risk is mainly in the bootloader unlock process, which is reversible via fastboot.

Q: What is the difference between Magisk and SuperSU?
A: Magisk offers systemless root, which allows you to hide root from apps and pass SafetyNet. SuperSU is an older, more traditional root solution.

Q: My phone is stuck on the boot logo after rooting. What should I do?
A: This is a bootloop. Boot into TWRP and restore your backup. If you didn’t make one, download the stock firmware and flash it via fastboot.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.