You've successfully unlocked a bootloader on a Xiaomi, Redmi or POCO smartphone -- but what now? This step opens up custom firmware, root rights, and deep system customization, but it also carries risks ranging from loss of warranty to bricking up the device. Unlike standard instructions that say "just flash TWRP," we'll take every step after unlocking, from preparing the backup to restoring IMEI if something goes wrong.
Itβs important to understand that unlocking the bootloader does not mean automatic freedom of action. For example, on new models (Xiaomi 13/14, Redmi Note 12) after unlocking, an anti-rollback can work, which will lock the device when trying to downgrade the version of MIUI. And on some devices (for example, POCO F5), you need to additionally disable the Mi Flash Lock through ADB. In this article, only current data for 2026, without outdated tips like βInstall Magisk 20.4β.
If you unlocked the bootloader for a specific purpose (e.g. installing Google Camera or removing ads in MIUI), we will show you the minimum steps necessary to avoid risking system stability. For enthusiasts, we will analyze advanced scenarios: flashing to AOSP, overclocking the processor or recovering from a soft breech.
1. Checking the unlock status and preparing the device
Before you do anything, make sure the bootloader is actually unlocked.
- π§ Turn off the phone and press the volume down. + Power to log into Fastboot Mode.
- π₯οΈ Connect the device to your PC and type in the command: fastboot oem device-info In the answer, look for the line Device unlocked: true. If there is false, unlock not passed.
- βοΈ On some models (Xiaomi) 12T, Redmi K50) status can be displayed as unlocked only after the first reboot.
Critically, if the command response has an Anti-rollback:4 (or other number), write down this value, which you will need when choosing a custom firmware. Installing software with a lower rollback will lead to hard-brick (irreparable damage).
Next, prepare the device:
- π± Make a full backup with Mi Cloud or Xiaomi Backup (settings) β Β«The phoneΒ» β Β«Backup.βDonβt rely on a Google account β it doesnβt save settings. MIUI.
- π Charge your phone to 80% β when you run through fastboot, a discharge below 30% can interrupt the process.
- π Download the official firmware for your model from the site MIUI Download (select the version of Fastboot) ROM, Not Recovery).
β οΈ Note: If you plan to install custom software (such as LineageOS), check the support for your model right away in the forum. XDA Developers. some firmware (for example, for POCO X3 NFC) Requires pre-installing of the patch disable_dm-verity.
2. Installing TWRP or OrangeFox: Which Recovery to Choose?
Xiaomi's stock recovery doesn't allow you to install unofficial firmware or modifications, so the next step is to install custom recovery.
- π οΈ TWRP β The most popular, but on new devices (Xiaomi 13, Redmi Note 12 Pro)+) It may not work due to encryption FBE (File-Based Encryption).
- π¦ OrangeFox - fork TWRP better-supported MIUI and the function of automatic partition mounting.
- π± PitchBlack β an alternative for devices with a problem TWRP (for example, POCO F4 GT).
How to install (in the example of TWRP):
- Download the recovery image for your model from the official TWRP website (file with the.img extension).
- Restart your phone to fastboot and execute the command: fastboot flash recovery twrp-3.7.0_12-0-lmi.img (Replace the file name with yours).
- Immediately after installation, reboot to recovery, holding Volume up + Power.
β οΈ Note: On devices with dynamic partitions (Xiaomi) 12, Redmi K40) before-fixing TWRP You need to disable the avb command: fastboot flash vbmeta vbmeta.img (file vbmeta.img You can get it from the official firmware).
3. firmware custom software: MIUI, AOSP or GSI?
After installing custom recovery, you can choose one of three ways:
| Type of firmware | Pluses | Cons | Suitable for |
|---|---|---|---|
| Official MIUI (Fastboot) | Stability, OTA-Update, retain the guarantee (conditionally) | Advertising, MIUI restrictions | For beginners who want to bring back the stock |
| Custom MIUI (e.g. MIUI EU) | Advertising-free, advanced settings, weekly updates | There may be bugs, no OTAs. | Users who lack the function of the drain |
| AOSP (LineageOS, Pixel Experience) | Clean Android, no Bloatware, long-term support | The camera, NFC or sensors may not work | Enthusiasts who want a βvanillaβ Android |
| GSI (Generic System Image) | Universality and Project Treble support | Low productivity, bugs | For experiments or unofficially supported models |
For installation of MIUI EU or other custom MIUI:
- Reboot to TWRP and run Wipe β Format Data (this will remove encryption).
For AOSP-Firmware (e.g. LineageOS 20):
- π Check out your model support at wiki.lineageos.org.
- π Make backup persistent and modem partitions in TWRP (They're responsible for IMEI linkage).
- π οΈ Install the firmware + NikGapps (for Google services) + Magisk (optional).
Download firmware for your model | Check anti-rollback | Make backup persist/modem | Format data in TWRP | Install NikGapps (if you need Google)
-->
4. Getting root rights: Magisk or KernelSU?
Root rights give full control of the system, but disable the ability to OTA-There are two main ways to get root in 2026, and updates can disrupt banking applications:
- π§ Magisk is a classic method that works on most devices. The latest stable version is Magisk 26.4 (check on GitHub).
- π§ KernelSU β an alternative for cores with support KPROBE. Suitable for Android 12+, but requires a custom core.
Instructions for Magisk:
- Download the latest Magisk.apk and rename it to Magisk.zip.
- V TWRP set up ZIP-file.
- Restart and check root through the Magisk app or command: su in the terminal.
For KernelSU:
- π Make sure your core supports KPROBE (check out on kernelsu.org).
- π¦ Install. KernelSU.zip through recovery or thread a custom core with KernelSU support.
- π Activate in settings: Settings β The phone. β Version of the kernel (stamp 5 times).
β οΈ Note: On devices with Dynamic Partition (Xiaomi) 11T, POCO F3) Magisk installation can result in a looped reboot, in which case a patch is required. disable_forceencrypt.
π‘
If banking applications stop working after installing Magisk, try enabling MagiskHide (in Magisk settings) and adding the application to the hidden list.
5.Recovery from Errors: From a Soft Brick to Losing an IMEI
Even with care, there are some things that can go wrong, and let's look at the typical problems and their solutions.
- π Bootloop β usually caused by incompatible firmware or incorrect Wipe Solution: Load to TWRP And do the Wipe. β Advanced Wipe β Dalvik, Cache, Data. Refresh the firmware.
Loss of network or IMEI
- Restore backup modem and persist in TWRP.
- If there is no backup, try flashing stock MIUI through the Mi Flash Tool with the clean all option.
- π« Hard-brick (device not turned on) β if the bootloader is damaged, only help EDL-Mode (emergency firmware via Qualcomm 9008). This requires an authorized Xiaomi account and boxing (for example, UFi Box).