The Xiaomi Mi A1 (codenamed tissot) is still a popular device among Android enthusiasts thanks to its clean Android One, robust hardware and active developer community, but the standard limitations of the system do not allow you to unlock the full potential of a smartphone: you can not remove embedded applications, change system files or use modifications like ViPER4Android without superuser rights.
Getting root rights to the Mi A1 is a multi-step process that requires unlocking the bootloader, installing a customized recover (TWRP) and Magisk firmware. Unlike devices with MIUI, there is no binding to the Xiaomi account, but there are nuances: from the firmware version to the features of working with fastboot. In this guide, we will analyze all the current ways to get a root on the Mi A1 in 2026, including bypassing typical errors like anti-rollback or data encryption problems.
Important: the procedure voids the warranty and can lead to a device blink if you do not act correctly. If you are a beginner, follow the instructions carefully and do not miss the steps of the check.
Preparation of the device: what to do before unlocking
Before you start unlocking the bootloader, you need to prepare the smartphone and the computer, and this stage is critical: missed settings can lead to failures in the next steps.
The Xiaomi Mi A1 requires:
- π Charge the battery to at least 70% (unlocking and firmware take 30-60 minutes).
- π± Enable Developer Mode: Go to Settings β About the phone and 7 times click on the Assembly Number.
- π Allow debugging by USB and Unlocking OEM in the developer menu (Settings) β System system β For developers).
- π Backup important data: unlocking the bootloader will reset the device to factory settings.
Your computer (Windows/Linux/macOS) will need:
- π» Install Android SDK Platform-Tools (or separately adb and fastboot).
- π Connect the smartphone to USB file transfer (MTP) Confirming trust in the computer.
- π‘οΈ Disable Antivirus: It Can Block Files TWRP Magisk as a potentially dangerous.
Check the firmware version: on the Mi A1, it is critical to avoid downgrade (downgrading the Android version), as this can cause anti-rollback - hardware locking of the device.
| Android version | Last stable assembly | Support for TWRP | The risk of anti-rollback |
|---|---|---|---|
| Android 7.1 Nougat | NHG47K | Yeah (tissot) | Low. |
| Android 8.0 Oreo | OPM1.171019.019 | Yeah (tissot) | Medium. |
| Android 9.0 Pie | PKQ1.180904.001 | Partially (patch required) | High-pitched |
| Android 10 | QKQ1.190910.002 | No (officially) | critical |
β οΈ Note: If your device has already been upgraded to Android 10, get back support TWRP Without the risk of a breeze, it's almost impossible, and in this case, consider alternatives like virtual root (e.g., Shizuku).
Unlock the bootloader: the official way from Xiaomi
Unlike devices with MIUI, on the Mi A1, it is easier to unlock the bootloader - no binding to the Mi Account is required. However, the process still involves waiting and confirming via fastboot.
Instructions:
- Turn off your smartphone and press Volume Down + Power to log into fastboot.
- Connect the device to the computer and execute the command: fastboot oem unlock On the screen of the smartphone will appear a warning β confirm the unlock button Volume up.
- Wait for the process to be completed (5-10 minutes) and the device will automatically reset.
After unlocking:
- π The smartphone will restart in a factory state (all data deleted).
- π The bootloader will remain unlocked even after resetting.
- π± The fastboot menu will have an inscription UNLOCKED bottom-screen.
Log in fastboot (Loudness down + Power)| Make sure UNLOCKED| Check no password request when booting |Reboot the device to the system-->
β οΈ Note: Some Android 9 firmware on some+ When unlocked, you may have a problem with data encryption (dm-verity). If the smartphone does not boot, you will need to flash Disable DM-Verity through the device. TWRP.
Installation of TWRP Recovery: version selection and firmware
TWRP (Team Win Recovery Project) is a customized recovery required to install Magisk and create backups. There are several builds available for the Mi A1, but not all work consistently with the latest firmware.
Recommended versions of TWRP for tissot:
- π Official build (3.7.0) β Suitable for Android 7-8, but may not see internal memory on Android 9.
- π οΈ Unofficial build from mauronofrio β supports Android 9 and fixes encryption errors.
TWRP firmware via fastboot:
- Download the twrp-3.x.x-x-tissot.img file and rename it to recovery.img.
- Restart your smartphone in fastboot and execute the command: fastboot flash recovery.img
- Immediately after the firmware, go to TWRP, holding Volume up + Power (otherwise, the stock firmware will overheat the Recovery).
TWRP requires:
- π Swipe to allow modifications (if requested).
- π€ Go to Wipe. β Format Data and enter yes (this will remove encryption if it interferes with partition mounting).
- πΎ Create a backup of Boot, System and Data (in case of errors).
π‘
If TWRP Can't see the internal memory, try to connect it. OTG-flash-drive ADB Sideload for transferring files.
Install Magisk: Getting root rights without SafetyNet triggers
Magisk is a universal root-rights tool that bypasses SafetyNet checks (important for banking applications and games), the latest stable version as of 2026 is Magisk 26.4.
Step-by-step:
- Download the latest version of Magisk from the official GitHub file Magisk-v26.4.zip.
- Move the archive to your smartphone or use ADB Sideload: adb sideload Magisk-v26.4.zip
- In TWRP, select Install, specify the path to the archive, and swipe for confirmation.
- After installation, reboot to the system.
Root rights check:
- π± Install the Root Checker app.
- π Run Magisk Manager (sets automatically) and check SafetyNet status under Settings β SafetyNet Check.
- π‘οΈ If SafetyNet fails, install Universal SafetyNet Fix via Magisk.
What if Magisk is not installed?
Solving Typical Problems After Getting Root Rights
Even with a successful Magisk installation, Mi A1 users often encounter bugs, and here are the most common ways to fix them:
| Problem. | Reason. | Decision |
|---|---|---|
| The smartphone does not load (bootloop) | Incompatible Magisk module or damaged boot.img | Swipe stock boot.img through fastboot, then reinstall Magisk |
| SafetyNet is not working. | Magisk is obsolete or Universal SafetyNet Fix is missing | Update Magisk and install the module with Magisk Manager |
| TWRP does not see internal memory | Data Encryption (FBE) | Format Data to TWRP or use an informal FBE-enabled build |
| Apps fly out after the root | Conflict with MagiskHide or modules | Disable MagiskHide for problem apps or remove conflicting modules |
If after the firmware Magisk stopped working banking applications (Sberbank, Tinkoff, etc.), follow the following steps:
- Open Magisk Manager and go to Settings β MagiskHide.
- Include MagiskHide and add banking apps to the list.
- Install the Universal SafetyNet Fix module and restart the device.
- Clear the data of the banking application and log in again.
β οΈ Note: Some applications (e.g. Google Pay) can block work even with MagiskHide enabled, in which case only abandoning the root or using alternative payment methods will help.
Alternative ways to obtain root rights
If the standard method with Magisk is not suitable (for example, due to anti-rollback or firmware incompatibility), consider alternatives:
- π§ Patched Boot Image: Download stock boot.img For your firmware, patch it through Magisk Manager and run it through fastboot: fastboot flash boot. magisk_patched.img
- π¦ Custom firmware: Install LineageOS or Pixel Experience with pre-sewn root. A1 Relevant builds based on Android 10/11.
- π₯οΈ Virtual Root: Use Shizuku + LSposed for getting a partial root without unlocking the bootloader (suitable for Android 9)+).
Advantages and disadvantages of alternatives:
| Method | Pluses | Cons |
|---|---|---|
| Patched Boot | Without TWRP, there are fewer risks. | Requires manual update when changing firmware |
| Custom firmware | Clean Android, regular updates | Loss of some functions (e.g., VoLTE) |
| Virtual Root | Does not require unlocking the loader | Limited capabilities (no access to /system) |
π‘
If your goal is only to remove embedded apps or block ads, consider using them. ADB-For example, disabling packets via pm uninstall -k --user 0 name-pack.
How to get everything back: root removal and bootloader lock
If you need to return your smartphone to stock (for example, for sale or warranty repair), follow the following steps:
- Download the stock firmware for your model (choose Fastboot ROM).
- Unpack the archive and launch the script flash_all.bat (Windows or flash_all.sh (Linux/macOS) firmware.
- To lock the bootloader, run the command: fastboot oem lock β οΈ This will completely reset the device and delete all data!
After returning to the stock firmware:
- π The device will be as new, without traces of the root.
- π The loader will become blocked (LOCKED fastboot).
- π± The warranty will be returned (if it has not expired).
β οΈ Note: Some Android 9 firmware on some+ locking the bootloader can lead to soft-brick (the device does not boot, but reacts to fastboot). ROM without fastboot oem lock command.