How to Root ZTE N9180 V5 Dual SIM

Updated 6 November 2026 · Standard formula, shown below

Rooting your ZTE N9180 V5 Dual SIM gives you full administrative control over the Android operating system, allowing you to remove bloatware, install custom kernels, use root-only apps, and even flash custom ROMs. This guide walks you through the entire process using a PC, from unlocking the bootloader to verifying root access. Before you begin, back up all important data, as rooting will wipe your device.

What You’ll Need

ZTE N9180 V5 Dual SIM with at least 70% battery charge.
A Windows PC (Windows 7 or later) with a USB cable.
ZTE USB drivers installed on the PC.
ADB and Fastboot tools (download the platform-tools from the official Android developer site).
An unlocked bootloader (required before rooting).
A custom recovery like TWRP (optional but recommended for flashing zip files).
Magisk ZIP file (latest stable version) and the Magisk Manager APK.

Step-by-Step

Enable Developer Options: Go to Settings > About phone and tap Build number seven times until you see “You are now a developer!”.
Enable USB Debugging and OEM Unlock: Go to Settings > Developer options and enable both USB debugging and OEM unlocking (if available).
Backup Your Data: Since unlocking the bootloader wipes the device, copy all important files to your PC or cloud storage.
Install ADB and Fastboot: Download the platform-tools ZIP from the Android developer website, extract it to a folder like C:\adb, and add that folder to your system PATH or just use it from that directory.
Install ZTE USB Drivers: Install the official ZTE USB drivers on your PC. If the driver is not available, use the generic Google USB driver from the SDK manager.
Connect Your Phone: Plug your phone into the PC via USB. On the phone, accept the RSA fingerprint prompt for USB debugging.
Verify ADB Connection: Open a Command Prompt in the platform-tools folder and run adb devices. You should see your device listed with “device” status.
Unlock the Bootloader: In the same Command Prompt, run adb reboot bootloader to reboot into fastboot mode. Then run fastboot oem unlock (or fastboot flashing unlock on newer devices). Confirm the unlock on the phone screen when prompted. This will wipe your data.
Reboot and Re-enable USB Debugging: After the unlock, the phone reboots. Set it up again, re-enable USB debugging, and reconnect.
Flash a Custom Recovery (Optional but Recommended): Download a TWRP image for the N9180 V5. In fastboot mode, run fastboot flash recovery twrp.img. Then run fastboot reboot.
Boot into TWRP: Turn off the phone, then press and hold Volume Up + Power to boot into recovery. If TWRP asks to allow system modifications, swipe to allow.
Copy Magisk ZIP to Phone: While in TWRP, connect the phone to PC and copy the Magisk ZIP to the internal storage. Use adb push Magisk-vXX.zip /sdcard/ if MTP is not working.
Install Magisk: In TWRP, tap Install, select the Magisk ZIP, and swipe to flash. Wait for the installation to complete.
Reboot the System: Tap Reboot System. The first boot may take a few minutes.
Install Magisk Manager: After boot, install the Magisk Manager APK (now called simply “Magisk”) and open it. It should show that Magisk is installed and the device is rooted.
Verify Root: Use a root checker app from the Play Store, or open a terminal emulator and run su. If a superuser prompt appears, root is successful.

Common Mistakes

Skipping OEM Unlock: If OEM unlocking is not enabled, the bootloader unlock command may fail or not work.
Using the Wrong Drivers: Without proper USB drivers, ADB and fastboot won’t recognize your device.
Not Backing Up: Unlocking the bootloader wipes everything. Forgetting to back up leads to data loss.
Flashing Wrong Recovery: Using a TWRP image for a different device can brick your phone. Always verify the exact model.
Interrupting the Process: Pulling the USB cable or closing the command window mid-flash can corrupt the system.
Ignoring Battery Level: A low battery during flashing can cause a power failure and brick the device.

Tips

Use a high-quality USB cable and a direct USB port on your PC (avoid hubs).
Keep the platform-tools folder path simple, like C:\adb, to avoid typing errors.
After unlocking the bootloader, your phone will show a warning at boot. This is normal.
Make a nandroid backup in TWRP before flashing anything, so you can restore if needed.
Check the Magisk GitHub page for the latest version and compatibility notes.
If you prefer not to use TWRP, you can patch the boot image with Magisk directly from the Magisk app, but that requires the stock boot image and a separate method.

Troubleshooting

ADB not recognizing device: Reinstall drivers, try a different USB port, and ensure USB debugging is enabled. Also try adb kill-server then adb start-server.
Fastboot not seeing device: In fastboot mode, the device may appear as “Android” with a yellow exclamation mark in Device Manager. Update the driver manually by selecting the Google ADB interface driver.
Bootloader unlock command fails: Ensure OEM unlocking is enabled. If the command is fastboot oem unlock and it fails, try fastboot flashing unlock instead.
Phone stuck in boot loop after rooting: Boot back into TWRP (Volume Up + Power) and wipe cache and dalvik cache. If that doesn’t help, restore your nandroid backup or reflash the stock ROM.
Magisk Manager shows “Not installed”: Reflash the Magisk ZIP via TWRP, ensuring you selected the correct file. Also check that your boot image is not corrupted.
Root checker fails: Some apps need to be granted root permission in Magisk Manager. Open Magisk, go to Superuser, and allow the app.

Frequently Asked Questions

Will rooting void my warranty?

Yes, rooting typically voids the manufacturer’s warranty. You can often restore the stock firmware and unroot to regain warranty, but it’s not guaranteed.

Can I unroot later?

Yes. You can unroot by flashing the stock boot image or by using the “Uninstall Magisk” option in the Magisk Manager (if you didn’t use a custom recovery). Alternatively, reflash the stock ROM.

Will I still receive OTA updates after rooting?

Usually not, because rooting modifies the system partition. You can manually install updates or use custom ROMs that support OTA.

Is it safe to root this device?

Rooting is generally safe if you follow the steps correctly. However, there is always a risk of bricking if you flash incompatible files or interrupt the process.

What if I don’t have a PC?

Rooting without a PC is not possible for this device, as you need to unlock the bootloader and flash files via fastboot. Some devices allow root via an app, but not this one.

Can I use Magisk to hide root from banking apps?

Yes, Magisk has a feature called Magisk Hide that can hide root from specific apps. However, this is not guaranteed to work with all apps, and some banks update their detection methods.

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