Why TWRP on the Redmi Note 8 Pro is not as easy as it seems
Installing a custom TWRP recavator on the Xiaomi Redmi Note 8 Pro (codename begonia) is a process that requires attention to detail. Unlike most Xiaomi devices, this model is equipped with a Mediatek Helio G90T processor, which imposes specific limitations. For example, the standard method of firmware through fastboot flash recovery will not work here because of blocked kernel load. Even after unlocking the bootloader, the system can automatically overwrite the recavers on the first restart.
Another trap is the TWRP versions. Not all builds are compatible with the latest MIUI updates, and some can cause constant reboots to fastboot mode (called "bootloop") when trying to download. In this article, we will discuss current installation methods, taking into account the features of firmware from 2023-2026, and show how to circumvent typical errors, such as file Invalid sparse format at header or FAILED (remote: "Not in Lock State").
Before you start, consider that the procedure requires unlocking the bootloader, which resets the device to factory settings. If you use the Redmi Note 8 Pro as your primary phone, save data (contacts, photos, messages) to an external drive or to the cloud in advance. Also check that you have a backup method for communication during installation - the process can take anywhere from 30 minutes to several hours, including waiting for unlock.
Requirements and Preparation: What to Do Before Installation
Before you start TWRP firmware, make sure all the prerequisites are met, and ignoring them can lead to a βbrickingβ of the device (complete inoperability) or inability to complete the process.
- π± Device model: Xiaomi Redmi Note 8 Pro (begonia) only.Check Settings β The phone. β Model: Devices with in suffix (e.g. India) may require other versions TWRP.
- π Unlocked bootloader: Without this, it is impossible to flash a custom recaveri. the process takes up to 7 days (waiting) SMS More details in the next section.
- π» Computer with Windows/Linux: Drivers will be required. ADB Fastboot and firmware utilities. MacOS may have problems with Mediatek drivers.
- π Cable USB: Use the original Xiaomi cable or certified cable USB 2.0.Cables. USB 3.0 can cause data transmission errors.
- π Battery charge: At least 70%, the firmware at low charge can be interrupted, which will lead to failure.
Also download the necessary files in advance:
| File. | Reference | Notes |
|---|---|---|
| TWRP for Redmi Note 8 Pro | Official website of TWRP | Choose a version. 3.7.0_9-0 or newer |
| Platform Tools (ADB/Fastboot) | Android Developers | Unpack at the root of the C:\ disc. |
| Mediatek drivers | SP Flash Tool Drivers | Needed for Windows. |
| OrangeFox (alternative) | OrangeFox Recovery | Supports encryption |
β οΈ Note: If your device was purchased in China (the domestic version), check if it supports global firmware. TWRP.
Unlocking the bootloader: why it can not do without it
The bootloader on all Xiaomi devices is locked by default, a security measure that prevents unauthorized changes to the system partition. To install TWRP, it must be unlocked through the official Mi Unlock Tool.
The process consists of several stages:
- Linking the Mi Account to the device (in the developer settings).
- Waiting for confirmation from Xiaomi (usually 7 days, but can take up to 30 days)
- Unlocking via PC with Mi Unlock Tool.
Important: Once unlocked, the device will be reset to factory settings. Also note that Xiaomi may refuse to unlock if:
- π΅ The device was purchased less than 30 days ago.
- π Mi Account not tied to device for more than 72 hours.
- π The device is intended for another region (e.g., the Chinese version for the global market).
β οΈ Note: If you have previously blocked the bootloader (for example, after installing custom firmware), it can take up to 30 days to re-unblock. Check the lock status with the fastboot oem device-info command - Device unlocked: true means that the bootloader is already unlocked.
Once you successfully unlock, move on to the next step. If Xiaomi refuses to unlock, try:
- Use another Mi Account (preferably created more than 3 months ago)
- Connect to the Internet via a mobile network (not Wi-Fi) when you link your account.
- Try again in 24 to 48 hours.
Enable Developer Mode (7 times click on "MIUI Version")
Link Mi Account to "Settings β Additional β Developer β Mi Unlock status"
Install Mi Unlock Tool on PC
Connect your phone in Fastboot mode (Pressure Power + Vol Down)
-->
TWRP version selection: official vs unofficial builds
There are several TWRP options available for the Redmi Note 8 Pro:
- The official build from twrp.me is the most stable, but may not support the latest MIUI versions.
- Unofficial builds (e.g. from wrzd or mauronofrio) β are frequently updated, but may contain bugs.
- OrangeFox Recovery is an alternative to TWRP with advanced features (encryption support, design themes).
If it doesn't work (e.g., partitions don't mount or backup errors), try the informal builds. Notice the version of Android that the firmware is built for:
- π± For MIUI 12/13 (Android 10/11) fit TWRP 3.6.2_9-0 or 3.7.0_9-0.
- π€ For Android. 12/13 (MIUI 14+) will require 3.7.0_12-0 or newer.
Before downloading, check the hash file (MD5 or SHA1) for matching the original. Fake TWRP builds may contain malicious code. Hash can be checked using the certUtil utility on Windows:
certUtil -hashfile twrp-3.7.0_9-0-begonia.img MD5How to check the compatibility of TWRP with your firmware?
Step-by-step installation of TWRP via Fastboot
Once the bootloader is unlocked and the files are ready, you can start running the firmware. We'll look at two methods: through fastboot and using the SP Flash Tool utility (for cases where the standard method doesn't work).
Method 1: Installation via Fastboot (recommended)
- Download and unpack the platform-tools to the root of the C:\ disk.
- Place the twrp-*-begonia.img file in the same folder.
- Open the command line (Win + R β cmd) and go to the folder with platform-tools: cd C:\platform-tools
- Connect your phone in Fastboot mode (press Power + Vol Down when the device is off).
- Check the connection command: fastboot devices must display the serial number of the device.
- Please. TWRP: fastboot flash recovery twrp-3.7.0_9-0-begonia.img
- Reboot to Recovery without booting the system: fastboot boot twrp-3.7.0_9-0-begonia.img
If the system automatically overwrites TWRP after restarting, follow the following steps:
- π§ V TWRP Go to Advanced. β Flash Current TWRP (This will record the recaps in both slots).
- π΅ Turn off signature verification in settings TWRP (Settings β Disable DM-Verity).
β οΈ Note: If after the firmware TWRP The phone loads into fastboot and doesn't leave, so it's got an incompatible version installed. Try flashing another build or use it. SP Flash Tool (method 2).
π‘
If the fastboot flash recovery command gives an error FAILED (remote: 'Not allowed in Lock State'), then the bootloader is not unlocked. Repeat the unlock procedure or check the status of the command fastboot oem device-info.
Method 2: Installation with SP Flash Tool (for Mediatek)
This method is required if:
- π Standard firmware via fastboot leads to bootloop.
- π§ We need to stitch the modified boot.img sympathetically.
- π₯ The device is not defined in fastboot.
Instructions:
- Download and install the SP Flash Tool + Mediatek drivers.
- In the folder with SP Flash Tool, create a file scatter.txt (you can take from the official MIUI firmware).
- In scatter.txt, find the line with recovery and specify the path to the TWRP file.
- Launch the SP Flash Tool, download scatter.txt and press Download.
- Connect the phone to the PC (no buttons!).
After successful firmware, turn off your phone and boot into TWRP by clamping Power + Vol Up.
π‘
If the SP Flash Tool is an error, SLA Auth or DA Auth, then you need an authorization file (.auth), which can be obtained from official Xiaomi distributors or forums (for example, 4PDA).
TWRP: What to do immediately after installation
After the first download to TWRP, do some critical steps to avoid problems in the future:
- Create a backup: π Go to Backup and select the sections: Boot, System, Data, Vendor. πΎ Save a backup on a MicroSD or formatted flash drive (not in internal memory!).
- Turn off encryption (if used): π Go to Wipe. β Format Data and enter Yes. β οΈ This will delete all data on the device, but prevent partition mounting problems.
Install Magisk.
- π Download the latest version of Magisk from GitHub.
- π² Fly through Install. β Select Storage β Downloads.
If you plan to flash custom firmware (like LineageOS or Pixel Experience), first check its compatibility with your version of the Redmi Note 8 Pro. Some firmware requires additional patches to work with the Mediatek Helio G90T processor.
β οΈ Attention: If after installation TWRP the phone stops charging or turns off when connected to charging, check the kernel settings in the TWRP β Settings β Power. disable the option Fastboot after power key.
Typical errors and their solutions
Even with the correct following of the instructions, errors can occur, and let's consider the most common ways to eliminate them:
| Mistake. | Reason. | Decision |
|---|---|---|
| Invalid sparse file format | A corrupted TWRP file or incompatible version. | Download the file again, check the hash. Try another build. |
| The phone is loaded into fastboot and does not come out | Incompatible version of TWRP or damaged boot.img. | Swipe the official boot.img through fastboot flash boot, then re-install TWRP. |
| Unable to mount /data | Encryption is enabled or the file system is damaged. | Format Data into TWRP (Wipe β Format Data). |
| Touchscreen doesn't work on TWRP | The wrong build for your model. | Use the official version or build marked touch-fixed. |
If none of these methods help, try:
- π Return to stock firmware via Mi Flash Tool and repeat the process.
- π‘ Use another PC (possibly driver problem).
- π€ Contact profile forums (for example, XDA Developers or 4PDA) fault-logged.
Remember, on the Redmi Note 8 Pro, you canβt flash TWRP over a stock backup without first unlocking the bootloader. All attempts to circumvent this restriction (for example, through exploits) lead to the βbrickingβ of the device.