Root ZTE Axon Mini: Full Guide
Rooting your ZTE Axon Mini gives you full administrative control over the Android operating system, letting you remove bloatware, install custom kernels, use root-only apps, and tweak system settings that are normally locked. This guide walks you through unlocking the bootloader, installing a custom recovery, and flashing Magisk to root the device. Before you begin, back up all important data, fully charge your phone, and ensure you have a Windows PC with a USB cable.
What You’ll Need
- ZTE Axon Mini (model number ZTE B2015 or B2016) with at least 70% battery
- A Windows PC (Windows 7 or later) with internet access
- USB data cable (the one that came with the phone works best)
- ZTE USB drivers installed on your PC (download from ZTE’s official support page)
- ADB and Fastboot tools – download the platform-tools zip from the Android developer site and extract it to a folder like C:\adb
- Unlocked bootloader – this is mandatory and will wipe your phone
- Magisk ZIP file (latest stable version) – download from the official Magisk GitHub releases
- TWRP recovery image for the ZTE Axon Mini (search for the correct .img file on XDA-Developers or similar trusted forums)
Step-by-Step
- Enable Developer Options and USB Debugging – Go to Settings → About phone → tap “Build number� 7 times until you see “You are now a developer!�. Then go to Settings → Developer options and turn on “USB debugging� and “OEM unlocking�.
- Install USB drivers – Connect your phone to the PC and install the ZTE USB drivers if prompted. If Windows doesn’t recognize the device, download the driver package from ZTE’s site and run the installer.
- Set up ADB and Fastboot – Extract the platform-tools zip to C:\adb. Open a command prompt in that folder (Shift+right-click → “Open command window here� or type cmd in the address bar). Verify ADB works by typing
adb devices– your phone’s serial number should appear with “device� next to it. - Back up your data – Unlocking the bootloader and flashing will erase everything. Use the built-in backup or copy files to your PC.
- Unlock the bootloader – In the command prompt, type
adb reboot bootloader. The phone will reboot into fastboot mode (you’ll see a black screen with fastboot text). Then typefastboot oem unlockorfastboot flashing unlock(the exact command depends on your model – try one, if it fails, try the other). Confirm the unlock on the phone screen using the volume keys and power button. This wipes your phone and reboots it. - Re-enable USB debugging – After the phone reboots, go through the initial setup, then re-enable Developer options and USB debugging as in step 1.
- Boot into fastboot again – Type
adb reboot bootloaderagain. - Flash TWRP recovery – In fastboot mode, type
fastboot flash recovery twrp.img(replace twrp.img with the actual filename of your TWRP image). Do not reboot yet – typefastboot rebootand immediately hold Volume Up + Power to boot into recovery. If you reboot normally, the stock recovery may overwrite TWRP. - Boot into TWRP – You should see the TWRP interface. If you don’t, repeat the flash and try the key combo again.
- Copy Magisk ZIP to your phone – While in TWRP, go to Mount → check “System� and “Data�. Then use the “Advanced� → “ADB Sideload� option, or simply push the file from PC using
adb push Magisk-vXX.zip /sdcard/(replace with the actual filename). Alternatively, you can copy the ZIP to the phone before booting into recovery. - Install Magisk – In TWRP, tap “Install�, navigate to the Magisk ZIP, select it, and swipe to confirm the flash. Wait for the process to finish.
- Wipe cache/dalvik – After flashing, go to “Wipe� → “Advanced� and check “Dalvik Cache� and “Cache�, then swipe to wipe. This prevents boot loops.
- Reboot system – Tap “Reboot� → “System�. The first boot may take several minutes – be patient.
- Verify root – After boot, install the Magisk Manager app (it may be installed automatically) and open it. You should see “Magisk installed� and a green checkmark. You can also download a root checker app from the Play Store to confirm.
Common Mistakes
- Not unlocking the bootloader first – Flashing TWRP or Magisk will fail or cause a boot loop if the bootloader is locked. Always unlock first.
- Rebooting normally after flashing TWRP – The stock recovery will replace TWRP on reboot. Always boot directly into recovery after flashing.
- Using the wrong TWRP image – The Axon Mini has several variants. Using a TWRP built for a different model can brick your phone. Double-check the model number and the source of the image.
- Skipping the cache wipe – Not wiping cache after flashing Magisk can cause boot loops or force-close errors.
- Battery dying mid-flash – A low battery can interrupt the flashing process and permanently damage the phone. Always start with at least 70%.
Tips
- Use the original USB cable and a direct USB port on your PC (not a hub) to avoid connection drops.
- If you’re unsure about a command, search for your exact model number (e.g., “ZTE B2015 unlock bootloader�) on XDA-Developers – there are often model-specific threads.
- After rooting, you can use apps like Titanium Backup to freeze bloatware, or Greenify to improve battery life.
- Keep a backup of your stock boot and recovery images – you can restore them later to unroot or take OTA updates.
- If you plan to install custom ROMs, make a full NANDroid backup in TWRP first.
Troubleshooting
Phone not detected in ADB/fastboot – Try a different USB port, reinstall drivers, or enable “USB debugging� again. In fastboot mode, Windows may show “Android� with a yellow exclamation mark – right-click and update the driver manually, pointing to the Google USB driver folder.
Boot loop after flashing Magisk – Boot back into TWRP (hold Volume Up + Power from off), go to Wipe → Advanced and wipe Dalvik Cache and Cache. If that doesn’t help, reflash the stock boot image (if you have it) or restore a backup.
Fastboot command not recognized – Make sure you’re in the correct folder (C:\adb) and that the fastboot.exe file is there. Also, check that your PATH includes that folder or run commands with “.\� prefix.
TWRP won’t boot – If you see the stock recovery instead of TWRP, the flash didn’t stick. Re-flash TWRP and immediately boot into recovery using the key combo. If it still fails, try a different TWRP version.
Magisk Manager says “Magisk not installed� – The ZIP may not have flashed correctly. Reboot into TWRP and flash it again, ensuring you select the correct file. Also, check that you have enough storage space.
OTA updates fail after rooting – Rooting modifies the system partition, so OTA updates will fail. You can unroot via Magisk Manager (uninstall) or restore the stock boot image, then take the update.
Frequently Asked Questions
Will rooting void my warranty? – Yes, in most cases rooting voids the manufacturer warranty. Some carriers may still honor it, but it’s safest to assume it’s void.
Can I unroot later? – Yes, you can unroot by opening Magisk Manager and choosing “Uninstall� → “Complete uninstall�. This restores the stock boot image and removes root.
Will I lose my data? – Unlocking the bootloader wipes all data. After that, flashing Magisk itself doesn’t wipe data, but you should still back up before any flashing.
Is rooting legal? – In most countries, rooting is legal, but it may violate the terms of service of your carrier or manufacturer. Check local laws and your contract.
What is the risk of bricking my phone? – There is always a risk, but following the steps correctly significantly reduces it. A soft brick (boot loop) can usually be fixed by flashing stock firmware. A hard brick (no response) may require specialized tools.
Can I still use banking apps after rooting? – Many banking apps detect root and refuse to run. You can use Magisk’s “MagiskHide� feature (if available) to hide root from specific apps, but it’s not guaranteed to work.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.