How to get root rights to Xiaomi Redmi Note 8 Pro without TWRP: the complete guide

Xiaomi Redmi Note 8 Pro is still a popular smartphone among Android modding enthusiasts, but getting root rights on this model is complicated by the lack of official support for TWRP for new firmware versions. If you are looking for a way to unlock full access to the system without installing a customized Recovery, this guide is for you.

Unlike the classic method with TeamWin Recovery Project, here we will look at alternative ways through unlocking the boot boot.img using Magisk and bypassing the limitations of MIUI. Importantly, the procedure requires accuracy, since improper actions can lead to locking the device or loss of warranty. We will analyze each step with the specifics of the Redmi Note 8 Pro (codename begonia) and current versions of firmware in 2026.

Why isn’t TWRP a good fit for the Redmi Note 8 Pro?

The traditional way to obtain root rights through TWRP has become less reliable for the Redmi Note 8 Pro for several reasons:

  • 🔒 bootloader lock: Xiaomi tightened security policy, and unlocking via fastboot oem unlock now requires a Mi Account binding and waiting up to 720 hours (30 days).
  • 🛡️ Anti-Rollback Protection: Starting with the MIUI 12, the device can lock when you try to roll back on the old firmware, even if you are just trying to install TWRP.
  • 🐞 Unstable assemblies TWRP: The official versions of the begonia recovery often do not support new cores and lead to bootloops (logo fixation).

Xiaomi also actively blocks downloads through uncertified recavators, making TWRP an ineffective tool for modern firmware. An alternative approach with boot.img patching through Magisk allows you to bypass these restrictions while maintaining the ability to update the system.

📊 You’ve already tried rooting on Xiaomi?
Yes, through TWRP.
Yes, through Magisk.
No, I'm afraid to block the phone.
I tried it, but it didn't work.

Preparation of the device: unlocking the loader

The first and mandatory step is to unlock the bootloader. Without that, no rooting method will work. The procedure takes at least 7 days (sometimes up to 30) due to Xiaomi's policy, so start with it in advance.

What you'll need:

  • 📱 Smartphone Redmi Note 8 Pro with battery charge >60%.
  • 💻 Windows computer (or Linux/macOS fixed ADB and Fastboot).
  • 🔌 Cable USB Type-C (original or high-quality).
  • 🔑 Mi Account linked to the device (required to have a confirmed phone number!).

Instructions:

  1. Activate Developer Mode: Go to Settings → About Phone → MIUI Version and tap 7 times on the line with the version.
  2. Return to Settings → More → For developers and enable: Debugging by USB Unlock OEM (an important item!)

Connect the phone to the PC and confirm the debugging permission.

statuary

Mi Unlock Tool

Mi

fastboot

Food + Volume Down

Unlock

☑️ Checking before unlocking

Done: 0 / 5

⚠️ Warning: Once the bootloader is unlocked, the smartphone will be completely reset to factory settings. All data (photos, contacts, messages) will be deleted).

Getting boot.img: extracting from firmware

To patch through Magisk, you'll need a boot.img file, which is an image of the boot partition of your current firmware, which can be obtained in two ways:

Method 1: Download the official firmware

If you have stock MIUI (without modifications), download the full firmware package for your model from the official website:

  1. Go to the Xiaomi downloads page.
  2. Select the Redmi Note 8 Pro (Begonia) model.
  3. Download the version corresponding to your current firmware (check in Settings → About Phone → MIUI version).
  4. Unpack the downloaded.zip archive and find the boot.img file inside.

Method 2: Remove boot.img from your phone

If you are not sure about the firmware version or want to get the latest boot.img, use ADB:

adb shell


su




dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img

This command will create a copy of boot.img in the root folder of internal memory.

adb pull /sdcard/boot.img
What if boot.img is not found in the firmware?
If the firmware archive does not have boot.img, then you have Dynamic Partitions firmware, in which case you need to use the payload.bin file and extract boot.img using the payload-dumper-go utility (instruction: https://github.com/ssut/payload-dumper-go).

Important: Make sure boot.img matches your current firmware. Using an image from another version can lead to a bootloop!

Patching boot.img via Magisk

Magisk is a universal tool for obtaining root rights without changing the systemless root. We will use it to patch boot.img.

Step-by-step:

  1. Download the latest version of Magisk from the official repository (Magisk-vXX.X.zip file).
  2. Copy boot.img to the folder with the downloaded Magisk.
  3. Rename Magisk-vXX.X.zip to magisk.zip and unpack it.
  4. Move boot.img to the folder with the unpacked Magisk.
  5. Open the terminal (Command Prompt or PowerShell) in this folder and execute the command: java -jar magiskboot.jar hexpatch boot.img If an error occurs, use the alternative command: magiskboot unpack boot.img
  6. After a successful patching, a file will appear in the folder boot_new.img-patched — That's the modified image.

Critical: If Magisk issues an error called "Unsupported/Unknown image format", your boot.img has a non-standard structure, in which case try using AIK (Android Image Kitchen) for manual patching.

💡

If you don’t have Java on your PC, download the portable version of Magisk Manager for Windows (like Magisk Manager for PC) – it includes all the dependencies you need.

Firmware patch boot.img via Fastboot

Now that you have a modified boot_new.img-patched, It needs to be flashed onto the device. It's a critical process, and it can cause an error to make it impossible to boot the system.

Instructions:

  1. Transfer the phone to fastboot mode (turn off, then press Power + Volume down).
  2. Connect the device to the PC and check its detection by the command: fastboot devices must display the serial number of the phone.
  3. The new version is called fastboot flash boot. boot_new.img-patched
  4. Reboot the device: fastboot reboot

The first download can take up to 10 minutes, which is normal. If the phone has been stuck on the Redmi logo for longer than 15 minutes, something has gone wrong (see the "Problem Solving" section).

⚠️ Note: After the patching of the patch boot.img Do not update the system through OTA! This will result in the loss of root rights and possible locking of the device, and updates can only be installed manually, before patching the new device. boot.img.

Root rights check and Magisk Manager installation

If it's successful, you'll have root rights after you boot it up. To manage it, you'll need to install Magisk Manager.

  1. Download the latest Magisk.apk from GitHub.
  2. Transfer the file to your phone and install it (allow installation from unknown sources in your security settings).
  3. Open Magisk Manager and check the status at the top of the screen. If it says Installed: XX.X, root rights are active.
  4. To test, download the Root Checker app from the Play Market and run the check.

Alternative methods of obtaining root

If boot.img patching didn’t work or seems too complicated, consider these options:

1.Use of MTK Bypass (for Helio G90T)

The Redmi Note 8 Pro is powered by a Mediatek Helio G90T processor, which allows vulnerabilities in the preloader to be exploited to unlock, a risky method that works even without officially unlocking the bootloader.

Instructions:

  1. Download MTK Bypass Tool and SP Flash Tool.
  2. Connect the phone in BROM mode (device turned off, only the Volume Up button is clamped).
  3. Download preloader and boot via SP Flash Tool.
  4. Sweep through the patch boot.img.

⚠️ Warning: This method can permanently lock the bootloader if you interrupt the process.

2. Installation of custom firmware (with pre-sewn Magisk)

Some custom firmware (like LineageOS or Pixel Experience) already include Magisk in the image, which simplifies the process, but requires:

  • Unlocked bootloader.
  • Compatible version of the firmware for begonia.
  • Preparedness for possible bugs (defunct NFC, camera problems).

3. Temporary root via ADB (no firmware)

If you need root access once (for example, for backup), you can use a temporary root through ADB:

adb shell


su -c "your_command_here"

This method only works until the device is restarted.

FAQ: Frequent questions

Can I get the root rights to the Redmi Note 8 Pro without unlocking the bootloader?
No, unlocking the bootloader is mandatory for any method of obtaining root rights on modern Xiaomi devices. Without this, the system simply will not allow you to modify the boot partition.
Will I lose my warranty after I get a root license?
Yes, unlocking the bootloader and getting root rights voids the warranty, but you can return the device to its original state by using the official firmware via the Mi Flash Tool (selecting the clean all and lock option), which will hide the traces of modifications, but does not guarantee the restoration of warranty - some service centers check the status of the bootloader through service utilities.
Can I update my MIUI after I get the root license?
Update the system through OTA You can't do it, you can lose root rights, you can lock the device, and you can get it up to date: Download the full firmware package (.zip) from the official website. Remove the new one. boot.img And patch it through Magisk. Sweat it manually through fastboot update. filename.zip. Sweep the patchy boot.img top-up.
How to remove root rights and get it back?
To completely remove root rights: Download the stock firmware for your model. Sweat it through the Mi Flash Tool, selecting the clean all option. If you want to lock the bootloader, use the command: fastboot oem lock Attention: This will lead to a complete data reset! After that, the device will return to its original state, but unlocking the bootloader will remain in the history of the Mi Account.
Will Google Pay and banking apps work after getting root rights?
Most banking applications (including Google Pay, Sberbank Online, Tinkoff) block work on root-right devices due to security policies: 🔒 Use the MagiskHide Props Config module to mask root rights. 📱 Install Universal SafetyNet Fix to pass SafetyNet. 🔄 Reboot your phone before using banking applications (some modules only work after a reboot).Please note: bypassing the security may violate the bank’s user agreement and lead to account blocking.