How to root Xiaomi, Redmi and POCO phones with Magisk
Rooting a Xiaomi, Redmi or POCO phone is easy once the bootloader is unlocked. Unlocking is the hard part: Xiaomi requires an approved application, a linked account and a waiting period, and it has changed those rules several times since HyperOS launched. China-region phones cannot be unlocked officially at all.
Last updated 10 sourcesHow we check pages
Xiaomi's unlock rules are changing: check before you start
Reports from December 2025 said Xiaomi removed the unlock application from the Xiaomi Community app, at least in China; other sources say global users can still apply after 30 days, and some 2026 guides say unlocking works again. Xiaomi's own policy pages could not be checked for this update. Treat the steps below as the most recent known process, and trust what the Xiaomi Community app and Mi Unlock tool tell you on your phone.
- Bootloader unlockApplication + Mi UnlockGlobal phones only
- Waiting period72 hours to 30 daysPlus a 30-day-old account
- China-region phonesNot officially unlockable
- Data wipeYes, when unlocking
- Image to patchinit_boot.img (check)boot.img on phones from before Android 13
- DowngradingBlocked by anti-rollback
Rooting a Xiaomi: the whole job
- Step 1 · Minutes, then days of waitingApply for unlocking and bind your account
- Step 2 · 5 minutes, after a 72-hour to 30-day waitUnlock with Mi Unlock
- Step 3 · 20 minutesGet the fastboot ROM and find the image
- Step 4 · 2 minutesPatch the image in the Magisk app
- Step 5 · 2 minutesFlash the patched image
- Step 6 · 2 minutesFinish setup and check root
Find your model
Every row below was checked against the model's official update on Xiaomi's servers in October 2026 (how). Most Xiaomi phones that launched with Android 13 or later use init_boot.img, but not all: the POCO F5, several Redmi Note 13 and 14 models and the Redmi 14C 5G have no init_boot, so find your exact model. Phones that launched before Android 13 use boot.img.
-
Xiaomi 17, 17 Pro, 17 Pro Max, 17 Ultra
pudding, pandora, popsicle, nezhaThe 17 Pro and Pro Max are China-only, which cannot be unlocked officially.Checked in official firmware: all four, Android 17 builds (how)Launched withAndroid 16Patchinit_boot.img -
Xiaomi 15T, 15T Pro
goya, klimtChecked in official firmware: both (how)Launched withAndroid 15Patchinit_boot.img -
Xiaomi 15, 15 Pro, 15 Ultra
dada, haotian, xuanyuanChecked in official firmware: all three (how)Launched withAndroid 15Patchinit_boot.img -
Xiaomi 14, 14 Pro, 14 Ultra, 14T, 14T Pro
houji, shennong, aurora, degas, rothkoChecked in official firmware: all five (how)Launched withAndroid 14Patchinit_boot.img -
Launched withAndroid 15Patchinit_boot.img
-
Redmi K70 (POCO F6 Pro)
vermeerChecked in official firmware: Redmi K70 and POCO F6 Pro (how)Launched withAndroid 14Patchinit_boot.img -
POCO F7, F7 Pro, F7 Ultra
onyx, zorn, miroChecked in official firmware: all three (how)Launched withAndroid 15Patchinit_boot.img -
POCO F6, F6 Pro
peridot, vermeerChecked in official firmware: both (how)Launched withAndroid 14Patchinit_boot.img -
POCO F5, F5 Pro
marble, mondrianNoinit_bootpartition, although it launched with Android 13 or later. Itsboot.imgholds the ramdisk.Checked in official firmware: both (how)Launched withAndroid 13Patchboot.img -
POCO X7, X7 Pro
malachite, rodinChecked in official firmware: both (how)Launched withAndroid 14 / 15Patchinit_boot.img -
POCO X6 Pro
duchampChecked in official firmware: yes (how)Launched withAndroid 14Patchinit_boot.img -
Redmi Note 14 5G, 14 Pro 5G, 14 Pro+ 5G
beryl, malachite, amethystThe 4G models are different: see the next row.Checked in official firmware: all three (how)Launched withAndroid 14Patchinit_boot.img -
Redmi Note 14 4G, 14 Pro 4G
tanzanite, obsidianItsboot.imghas no ramdisk (we checked); the phone's ramdisk is invendor_boot. Magisk patchesboot.imganyway and adds a ramdisk of its own, as on the Pixel 6, and that is what the app picks. If Magisk doesn't start after flashing it, patchvendor_boot.imginstead (Magisk v30.3 or later) and flash it withfastboot flash vendor_boot. We haven't seen a confirmed install on this model.Checked in official firmware: both (how)Launched withAndroid 14Patchboot.img -
Redmi Note 13 (4G), 13 Pro+, Note 12 4G
sapphire, zircon, topazThe Note 13 5G, 13 Pro 5G and 13 Pro 4G are different: see the next rows.Checked in official firmware: all three (how)Launched withAndroid 13Patchinit_boot.img -
Redmi Note 13 Pro 5G (POCO X6 5G)
garnetNoinit_bootpartition, although it launched with Android 13 or later. Itsboot.imgholds the ramdisk.Checked in official firmware: yes (how)Launched withAndroid 13Patchboot.img -
Redmi Note 13 5G, 13 Pro 4G (POCO X6 Neo, M6 Pro)
gold, emeraldItsboot.imghas no ramdisk (we checked); the phone's ramdisk is invendor_boot. Magisk patchesboot.imganyway and adds a ramdisk of its own, as on the Pixel 6, and that is what the app picks. If Magisk doesn't start after flashing it, patchvendor_boot.imginstead (Magisk v30.3 or later) and flash it withfastboot flash vendor_boot. We haven't seen a confirmed install on this model.Checked in official firmware: both (how)Launched withAndroid 13Patchboot.img -
Redmi 15C, 15C 5G, 14C (4G)
dew, tornado, lakeThe Redmi 14C 5G is different: see the next row.Checked in official firmware: all three (how)Launched withAndroid 14 / 15Patchinit_boot.img -
Redmi 14C 5G (POCO M7 5G)
flameItsboot.imghas no ramdisk (we checked); the phone's ramdisk is invendor_boot. Magisk patchesboot.imganyway and adds a ramdisk of its own, as on the Pixel 6, and that is what the app picks. If Magisk doesn't start after flashing it, patchvendor_boot.imginstead (Magisk v30.3 or later) and flash it withfastboot flash vendor_boot. We haven't seen a confirmed install on this model.Checked in official firmware: yes (how)Launched withAndroid 14Patchboot.img -
Redmi Note 12 5GSnapdragon 4 Gen 1Launched withAndroid 12Patchboot.img
-
POCO X3 Pro, X3 NFC, F3Snapdragon 860 / 732G / 870Launched withAndroid 10 / 11Patchboot.img
-
Redmi 9C, Redmi 10, Redmi Note 10, 9, 8Launched withAndroid 9 to 11Patchboot.img
No match. Open your fastboot ROM's images folder: patch init_boot.img if it exists, otherwise boot.img.
Launch Android versions and chips are from GSMArena and Wikipedia specification pages. Magisk's guide notes that some Xiaomi phones report Ramdisk: No but still accept a patched boot image, so trying the boot method is reasonable there.
What we found in the official firmware
We read the partition list of every model's newest official update package on Xiaomi's own download servers, without downloading the whole package, and checked the device name each package reports. Where a phone has no init_boot, we also extracted its boot.img, checked it against the hash in the update's manifest, and opened it with Magisk's own tool to see whether it holds a ramdisk. Package links come from the Xiaomi Firmware Updater tracker. Checked October 27, 2026.
| Model | Official package | init_boot partition | Ramdisk in boot.img | Patch |
|---|---|---|---|---|
| Xiaomi 17 Global (pudding) | OS3.0.337.0.XPCMIXM Android 17 | Yes | — | init_boot.img |
| Xiaomi 17 Pro China (pandora) | OS4.0.5.0.XBLCNXM Android 17 | Yes | — | init_boot.img |
| Xiaomi 17 Pro Max China (popsicle) | OS4.0.5.0.XPBCNXM Android 17 | Yes | — | init_boot.img |
| Xiaomi 17 Ultra Global (nezha) | OS3.0.337.0.XPAMIXM Android 17 | Yes | — | init_boot.img |
| Xiaomi 15T Global (goya) | OS3.0.303.0.WOEMIXM Android 16 | Yes | — | init_boot.img |
| Xiaomi 15T Pro Global (klimt) | OS3.0.335.0.XOSMIXM Android 17 | Yes | — | init_boot.img |
| Xiaomi 15 Global (dada) | OS3.0.303.0.WOCMIXM Android 16 | Yes | — | init_boot.img |
| Xiaomi 15 Pro China (haotian) | OS3.0.309.0.WOBCNXM Android 16 | Yes | — | init_boot.img |
| Xiaomi 15 Ultra Global (xuanyuan) | OS3.0.303.0.WOAMIXM Android 16 | Yes | — | init_boot.img |
| Xiaomi 14 Global (houji) | OS3.0.304.0.WNCMIXM Android 16 | Yes | — | init_boot.img |
| Xiaomi 14 Pro / Ti China (shennong) | OS3.0.309.0.WNBCNXM Android 16 | Yes | — | init_boot.img |
| Xiaomi 14 Ultra Global (aurora) | OS3.0.304.0.WNAMIXM Android 16 | Yes | — | init_boot.img |
| Xiaomi 14T Global (degas) | OS3.0.305.0.WNEMIXM Android 16 | Yes | — | init_boot.img |
| Xiaomi 14T Pro Global (rothko) | OS3.0.303.0.WNNMIXM Android 16 | Yes | — | init_boot.img |
| Redmi K80 China (zorn) | OS3.0.309.0.WOKCNXM Android 16 | Yes | — | init_boot.img |
| Redmi K80 Pro / POCO F7 Ultra Global (miro) | OS3.0.302.0.WOMMIXM Android 16 | Yes | — | init_boot.img |
| Redmi K70 China (vermeer) | OS2.0.218.0.VNKCNXM Android 15 | Yes | — | init_boot.img |
| POCO F6 Pro Global (vermeer) | OS3.0.304.0.WNKMIXM Android 16 | Yes | — | init_boot.img |
| POCO F7 Global (onyx) | OS3.0.303.0.WOLMIXM Android 16 | Yes | — | init_boot.img |
| POCO F7 Pro Global (zorn) | OS3.0.303.0.WOKMIXM Android 16 | Yes | — | init_boot.img |
| POCO F6 Global (peridot) | OS3.0.303.0.WNPMIXM Android 16 | Yes | — | init_boot.img |
| POCO F5 Global (marble) | OS3.0.4.0.VMRMIXM Android 15 | No | Yes | boot.img |
| POCO F5 Pro Global (mondrian) | OS3.0.5.0.VMNMIXM Android 15 | No | Yes | boot.img |
| Redmi Note 14 Pro 5G / POCO X7 Global (malachite) | OS3.0.305.0.WOOMIXM Android 16 | Yes | — | init_boot.img |
| POCO X7 Pro Global (rodin) | OS3.0.303.0.WOJMIXM Android 16 | Yes | — | init_boot.img |
| POCO X6 Pro 5G Global (duchamp) | OS3.0.10.0.WNLMIXM Android 16 | Yes | — | init_boot.img |
| Redmi Note 14 4G Global (tanzanite) | OS3.0.305.0.WOGMIXM Android 16 | No | No | boot.img |
| Redmi Note 14 5G / POCO M7 Pro 5G Global (beryl) | OS3.0.303.0.WOQMIXM Android 16 | Yes | — | init_boot.img |
| Redmi Note 14 Pro 4G Global (obsidian) | OS3.0.305.0.WOFMIXM Android 16 | No | No | boot.img |
| Redmi Note 14 Pro+ 5G Global (amethyst) | OS3.0.307.0.WOPMIXM Android 16 | Yes | — | init_boot.img |
| Redmi Note 13 Global (sapphire) | OS2.0.213.0.VNGMIXM Android 15 | Yes | — | init_boot.img |
| Redmi Note 13 5G / POCO X6 Neo 5G Global (gold) | OS3.0.5.0.VNQMIXM Android 15 | No | No | boot.img |
| Redmi Note 13 Pro 4G / POCO M6 Pro Global (emerald) | OS3.0.307.0.WNFMIXM Android 16 | No | No | boot.img |
| Redmi Note 13 Pro 5G / POCO X6 5G Global (garnet) | OS3.0.302.0.WNRMIXM Android 16 | No | Yes | boot.img |
| Redmi Note 13 Pro+ 5G Global (zircon) | OS3.0.303.0.WNOMIXM Android 16 | Yes | — | init_boot.img |
| Redmi Note 12 4G NFC Global (topaz) | OS2.0.210.0.VMGMIXM Android 15 | Yes | — | init_boot.img |
| Redmi 15C / POCO C85 Global (dew) | OS3.0.307.0.WBNMIXM Android 16 | Yes | — | init_boot.img |
| Redmi 15C 5G / 15R 5G / 17C 5G Global (tornado) | OS3.0.305.0.WPOMIXM Android 16 | Yes | — | init_boot.img |
| Redmi 14C/17C/A3 Pro/POCO C75 Global (lake) | OS3.0.307.0.WGTMIXM Android 16 | Yes | — | init_boot.img |
| Redmi 14C 5G / POCO M7 5G India (flame) | OS3.0.302.0.WGUINXM Android 16 | No | No | boot.img |
What this changed: most Xiaomi phones that launched with Android 13 or later do have init_boot, but the POCO F5 and F5 Pro, the Redmi Note 13 5G, 13 Pro 4G and 13 Pro 5G, the Note 14 4G and 14 Pro 4G, and the Redmi 14C 5G don't, so the launch-version rule would have sent their owners to the wrong image. Five of them also have no ramdisk in boot.img; their rows above explain what that means. The full output, the extraction checks and the tool: evidence files. Here is the Redmi Note 13 5G, one of the phones without init_boot:
Lines 85 to 99 of the unedited output. Full log · how it was made
Before you start
You will need
- A global-region phone (Global, EEA, India and so on). China-region phones cannot be unlocked officially, and a China phone cannot be unlocked from a global account or the other way round.
- A Xiaomi account at least 30 days old, signed in on the phone, and the Xiaomi Community app.
- A Windows PC for Xiaomi's Mi Unlock tool, plus Google's Platform-Tools.
- The fastboot ROM for your exact model, region and HyperOS version.
- A backup. Unlocking erases the phone.
What you give up
- Possibly HyperOS updates. When it launched HyperOS, Xiaomi said phones left unlocked would no longer receive HyperOS updates. We found no newer statement either way.
- Downgrades. Xiaomi's anti-rollback protection rejects or bricks on older firmware, and unlocking does not disable it.
- Strong Play Integrity. An unlocked bootloader fails the device verdict on Android 13 and later. See Play Integrity and root.
Root your Xiaomi step by step
Each step has a Done box so you can keep your place, which helps across the unlock wait. Your progress is saved in this browser only.
-
Apply for unlocking and bind your account
Minutes, then days of waiting- In the Xiaomi Community app, set the region to Global and find Apply for unlocking. Community guides report a small daily quota that fills right after it opens at midnight Beijing time (00:00 GMT+8); “Application quota limit reached” means try again the next day. Reports say each account can unlock one device per year.
- Once approved, open Settings → Additional settings → Developer options → Mi Unlock status and tap Add account and device. Guides recommend doing this on mobile data with Wi-Fi off.
-
Unlock with Mi Unlock
5 minutes, after a 72-hour to 30-day wait- Turn the phone off, hold Power + Volume Down to enter fastboot, and connect it to the PC.
- Run Mi Unlock and sign in with the same account. The first attempt usually shows a waiting time; HyperOS phones are most often told 72 hours. Do not sign out of the account on the phone during the wait, as users report it resets the timer.
- After the wait, run Mi Unlock again and unlock. This erases all data.
-
Get the fastboot ROM and find the image
20 minutesDownload the fastboot ROM (a
.tgz, not the recovery ROM zip) for your exact model, region (Global, EEA, India and so on) and HyperOS version. Extract it and open theimagesfolder. Ifinit_boot.imgis there, use it; otherwise useboot.img. Copyinit_boot.imgto the phone.Never flash an older ROMXiaomi's anti-rollback check compares the phone's index (
fastboot getvar anti) with the ROM's. Flashing a ROM with a lower index is rejected or bricks the phone. Only take the image from the build you are running now. -
Patch the image in the Magisk app
2 minutesInstall the Magisk app, tap Install → Select and Patch a File and pick
init_boot.img. Copy the patched file back with adb.Copy the patched image to the computer$adb pull /sdcard/Download/magisk_patched-XXXXX_YYYYY.img -
Flash the patched image
2 minutesBoot to fastboot (Power + Volume Down) and flash the patched file to
init_boot.Flash$fastboot flash init_boot magisk_patched-XXXXX_YYYYY.img $fastboot reboot -
Finish setup and check root
2 minutesOpen the Magisk app and accept the additional setup. A version number on the Magisk card, for example
31.1 (31100), means root works. Don't go by the App card: its Installed line shows the app's own version even when Magisk isn't running.
Keeping root after updates
The dependable update route
- 1Download the new firmwareFastboot ROM for your model
- 2Patch its image againIn the Magisk app
- 3Flash itKeeping your data
- 4Boot and checkMagisk shows its version
Most recent Xiaomi phones have A/B slots, so Magisk's method can keep root: Uninstall → Restore Images, install the update without restarting, then Install to Inactive Slot (After OTA). Magisk's documentation only vouches for this method on Pixels, and Xiaomi has said unlocked phones may not be offered HyperOS updates at all. The dependable route is to download the new fastboot ROM, flash it with Mi Flash using save user data, then patch and flash its init_boot.img again. Full steps: keeping root after an update.
Mi Flash's default option relocks the bootloader. On a phone with any modified image that can leave it unable to boot. Choose save user data or clean all.
If the phone does not boot
Boot to fastboot with Power + Volume Down and flash the untouched image from the same fastboot ROM: fastboot flash init_boot init_boot.img. If that is not enough, flash the whole fastboot ROM for the same build with Mi Flash using clean all (wipes data), never clean all and lock. Module bootloops: see fixing a Magisk bootloop.
Errors and fixes
The messages people most often hit on this brand, and what they mean.
“Application quota limit reached” in the Community app
The daily unlock quota is already used up. Community guides report it fills right after midnight Beijing time (00:00 GMT+8); try again at that time the next day.
“Account Error” when applying
Community guides report this as a temporary refusal and advise waiting about ten days before applying again.
“Couldn't unlock” with a waiting time
Normal on the first attempt. Keep the account signed in on the phone and try again when the timer ends; signing out or resetting the phone is reported to restart the countdown.
“Couldn't verify, wait a minute or two and try again” when binding
Users report success after switching to mobile data with Wi-Fi off, signing out and back in, and checking that the phone's ROM region matches the phone.
“anti-rollback check failed” or Mi Flash refuses the ROM
The ROM is older than the phone's anti-rollback index. Do not force it: use a ROM with the same or newer index.
The Magisk app shows Ramdisk: No
Magisk's guide notes that some Xiaomi phones accept a boot ramdisk even though they report none. Trying the normal boot-image method is the only way to know; if it fails, flash the stock image back.
Questions people ask
Can I still unlock a Xiaomi bootloader in 2026?
For global-region phones, most recent reports say yes, through an approved application in the Xiaomi Community app and then Mi Unlock. The rules have changed repeatedly, so check the app on your phone before planning a root. China-region phones cannot be unlocked officially.
How long is the Mi Unlock wait?
Usually 72 hours on HyperOS, but users report waits of 7, 14 or 30 days. The account also has to be at least 30 days old.
Can I unlock a China ROM phone with a global account?
No. China and global devices and accounts cannot be mixed, and China-region phones have no official unlock route.
Do I patch boot.img or init_boot.img?
Look up your exact model in the finder above: we checked each one in its official firmware. If your fastboot ROM's images folder has init_boot.img, patch that; if not, patch boot.img. Don't go by launch Android version alone: the POCO F5, Redmi Note 13 5G, 13 Pro 4G and 5G, Note 14 4G and 14 Pro 4G and the Redmi 14C 5G launched with Android 13 or 14 and have no init_boot.
Will I still get HyperOS updates?
Xiaomi said in 2023 that phones left unlocked would stop receiving HyperOS updates. Plan on updating by flashing new fastboot ROMs yourself.
Is it safe to relock later?
Only on completely stock firmware. Flash the full ROM with clean all, confirm it boots, and only then lock.
Sources
This page is written from the sources below. If anything here disagrees with them, the upstream source is correct.
- Magisk installation guide, including the Xiaomi ramdisk note (topjohnwu)
- Mi Unlock tool (Xiaomi)
- Xiaomi removes the bootloader unlock option (XimiTime, Dec 2025)
- Xiaomi global unlock policy: one device per year (XimiTime)
- Xiaomi's 180-day unlock rule for China (XimiTime)
- HyperOS and unlocked bootloaders: no updates (9to5Google)
- Xiaomi anti-rollback protection explained (XDA)
- Bootloader unlock status by brand: Xiaomi (community tracker)
- Xiaomi unlocking and rooting guide for HyperOS 3 (community)
- Generic boot partition and init_boot (Android Open Source Project)
Found a mistake or something out of date? Tell us and we will check it against the source and fix the page. Confirmed corrections are listed in the corrections log.
Report a problem with this page