Getting root rights to the Xiaomi Redmi 8 Pro opens up access to hidden Android features, but requires care. This model (codenamed olivelite) has nuances with unlocking the bootloader and compatibility of custom recoveries. In 2026, the classic method with KingRoot or SuperSU no longer works - only the official path through Magisk and TWRP.
The process consists of 4 key steps: unlocking the bootloader, installing a custom recovery, Magisk firmware and superuser rights verification. Importantly, Redmi 8 Pro with MIUI 14+ may require a rollback to MIUI 12.5 to successfully unlock. We will analyze each step in detail, including solutions to typical errors like "fastboot unauthorized" or hanging on the Mi logo.
1.Preparation of the device: what to do before unlocking
Before you start the process, make sure your Redmi 8 Pro meets the minimum requirements. First, check the MIUI version in Settings → About Phone. The best option is MIUI 12.5 (Android 10), as the newer versions make unlocking difficult. If you have a MIUI 13/14, consider rolling back through the Mi Flash Tool.
Second, make sure to back up your data. Use Settings → Additional → Backup or third-party tools like Swift Backup.
- 📱 Contact (export to) VCF)
- 📸 Photo/video (copy on PC)
- 🔑 Passwords from Wi-Fi (Settings) → Wi-Fi → Save networks)
- 🎮 Save games (use Google Play Games)
The third critical point is battery power. Make sure it's at least 70 percent charge, and when you unlock the bootloader, the device can reboot up to 10 times, and low charge will lead to a "brick."
- 🖥️ Computer on Windows 10/11 (Linux requires additional drivers)
- 🔌 Original. USB-cable (do not use extension cords!)
- 📋 Serial phone number (Settings) → The phone. → General information)
⚠️ Note: If your Redmi 8 Pro was purchased from the official Xiaomi store in Russia after 2022, check the bootloader status with the fastboot oem device-info team. OEM Unlock: False at the hardware level.
2 Unlock the bootloader: the official method through Mi Unlock
The unlock procedure on the Redmi 8 Pro differs from other Xiaomi models due to the company's policy: From 2021, you need to link your Mi Account to the device and wait 72-168 hours (3-7 days).
- Activate Developer Options: Go to Settings → About Phone and click on MIUI 7 times.
- Enable USB Debugging and OEM Unlocking in Settings → More → For Developers.
- Link your Mi Account to your phone: Settings → Xiaomi Account → Synchronization.
- Download Mi Unlock Tool (version no lower than 5.5.224.30).
Then connect your phone to your PC in fastboot mode (turn off the device, then press Volume Down + Power).
- 🔗 Sign in with the same Mi Account as you do on your phone.
- 🔓 Press Unlock and a waiting timer will appear.
- ⏳ Wait. SMS-Notifications of successful unblocking (not always coming!)
| Problem. | Reason. | Decision |
|---|---|---|
| "Couldn't unlock" error | It's been 168 hours. | Wait or use bypass methods (see spoiler) |
| "Current account is different" | Another Mi Account on PC and phone | Reconnect your account and reboot your phone |
| Device not defined | There are no Qualcomm drivers | Install Mi Phone Manager |
Waiting bypass 168 hours (unofficial method)
3. Installation of TWRP Recovery: version selection and firmware
For Redmi. 8 Pro (olivelite) is suitable only for informal TWRP from the developer wrzd (version) 3.7.0_12-0). The official builds on twrp.me don't support this model. twrp-3.7.0_12-0-olivelite.img from a reliable source (e.g, XDA Developers).
The firmware is performed via fastboot:
fastboot flash recovery twrp-3.7.0_12-0-olivelite.img
fastboot boot twrp-3.7.0_12-0-olivelite.imgAfter successfully downloading to TWRP:
DO NOT swipe to allow modifications (this will remove stock recovery)|
Backup boot, data, system| partitions
Turn off your password request (if any) via Mount → Disable MTP|
Reboot to fastboot for Magisk firmware
-->
Critical error: If the phone is stuck on the Mi logo after TWRP, it went off with an anti-rollback.
- Download stock ROM for your model.
- Sweat through the Mi Flash Tool with the clean all option.
- Re-open the loader.
💡
If TWRP You can’t see the internal memory, connect it. OTG-a flash drive with firmware files. Format it into FAT32, not NTFS exFAT.
4. Magisk firmware: obtaining root rights without risks
Magisk (version 26.4+) is the only safe way to get a root on modern Xiaomi. Download the latest version from GitHub (Magisk-v26.4.apk file).
Step 1: Patching boot image:
- Copy boot.img from your firmware (can be extracted from payload.bin via MIUI bootloader).
- In Magisk, click Install → Select and Patch a File and select boot.img.
- File received magisk_patched.img copy it to a PC.
Step 2. Firmware via fastboot:
fastboot flash boot magisk_patched.img
fastboot rebootAfter the reboot, check the root through the Root Checker app or a command in the terminal:
su⚠️ Attention: Redmi 8 Pro with MIUI 13+ Magisk can conflict with Google Pay and banking apps.To solve, install the MagiskHide Props Config module and activate MagiskHide for problem apps.
💡
Use only official Magisk builds with GitHub. Modified versions (like Magisk Alpha) can contain backdoors and lead to IMEI blocking.
5. Alternative methods: when Magisk doesn't work
If the standard method didn’t work (for example, because of anti-rollback 4 on new firmware), consider alternatives:
- 🔧 Patched Boot through ADB: Temporary root without firmware (acts until reboot). magisk_patched.img /sdcard/ adb shell su dd if=/sdcard/magisk_patched.img of=/dev/block/bootdevice/by-name/boot
- 📦 Custom firmware: LineageOS 19 or Pixel Experience already include root. minus - loss of camera features Xiaomi.
- 🔄 Downgrade MIUI: rollback MIUI 12.0.3.0 (Android 9) makes unlocking easy, but it takes away new features.
For the Redmi 8 Pro with a Snapdragon 665 processor, Havoc-OS (based on AOSP) firmware is suitable.
- Download Havoc-OS-v4.19-20230512-olivelite-Official.zip.
- Write it through TWRP (wipe → Dalvik, Cache, Data, System).
- Install NikGapps-core for Google services.
Warning: Custom firmware disables Widevine L1, which will make Netflix and Disney+ work at a resolution of no more than 480p.
6. Solving typical problems after obtaining a root
Even with a successful Magisk installation, Redmi 8 Pro users are plagued by bugs, and the most common solutions are:
| Problem. | Reason. | Decision |
|---|---|---|
| The phone's not charging. | Conflict of Magisk modules with the core | Remove Battery Charge Limit or Fast Charge modules |
| NFC's not working | The vendor section is damaged. | Sweep through the original vendor.img via TWRP |
| Random reboots | Unstable core in custom firmware | Install KernelSU or go back to stock |
| Not defined SIM-map | Damaged modemst1/st2 | Restore the modem partition backup from TWRP |
If Google Play Services stop working after receiving the root, do:
adb shell
su
pm uninstall -k --user 0 com.google.android.gms
pm install -k --user 0 com.google.android.gmsTo recover DRM L1 (for Netflix in Full HD), run the original vendor and system through the Mi Flash Tool with the clean all and lock option, then re-install Magisk.
7.Safety and Risks: What to Fear
The root rights to the Redmi 8 Pro give you full control over the system, but also open up vulnerabilities:
- 🛡️ Banking apps: SberBank Online and Tinkoff block access when routs are detected.Solution - MagiskHide + SafetyNet Fix module.
- 🔓 Encryption: After firmware TWRP The data in the internal memory may become unavailable. Always back up the external drive.
- 📡 IMEI: Incorrect Modem firmware leads to loss IMEI. You can re-establish through QCN-File (requires engineering menu ##4636##).
According to statistics from XDA Developers, 18% of Redmi 8 Pro users lose their warranty after unlocking the bootloader.
- 📄 Save the original firmware (fastboot rom) to the cloud drive.
- 🔧 Use only proven Magisk modules (Secure List: MagiskHub).
- 🔄 Regularly check the integrity of the partitions with the fsck command TWRP.
⚠️ Warning: On devices with anti-rollback 5 (firmware after 2023) an attempt to roll back on the old version MIUI Before any manipulation, check the current version of the anti-rollback via fastboot getvar anti.