What’s new in OrangeFox R12

• R12.0 (March 15, 2026) is the project’s “biggest visual overhaul yet”, inspired by Material You Expressive. It adds sharp SVG icons, two new themes (Fox White and Fox Dark), Inter as the default font, and swipe navigation on by default.
• R12.0_1 brought “improved support for Android 17”. On the POCO F3 it is a unified release for Android 13–17 ROMs. On the Redmi Note 13 Pro 5G the changelog mentions better Android 17 support, especially when formatting data.
• Since R11.3, OrangeFox can be controlled with the hardware buttons if the touchscreen doesn’t work (HW GUI Control, see below).
• OrangeFox R12 is for Android 13 and newer ROMs. The maintainers’ notes say not to use it with Android 12 or earlier.

OrangeFox R12 for Xiaomi, Redmi and POCO: official builds

This list comes from OrangeFox’s official download server (checked on November 14, 2026). The “Android” column shows what the maintainer’s notes for that build say. “Not stated” means the notes don’t name the Android versions, so check the download page before flashing.

The POCO F5 (marble) is listed as a supported device but has no release on the server yet. About 50 older Xiaomi phones (Redmi Note 8, Mi 9T, POCO F1, Redmi Note 10 and others) still have old R10 and R11 builds there, but they are no longer maintained. Find your phone on orangefox.download.

Your phone isn’t listed?

Many newer phones, such as the POCO X7 Pro, only have unofficial OrangeFox builds, posted by their builders in the phone’s 4PDA or XDA thread. Treat them like any community build: read the post and check which kernel or ROM it works with. For example, the unofficial R12 for the POCO X7 Pro works only with one AOSP kernel version (see our POCO X7 Pro custom ROMs post). Some ROMs also warn against OrangeFox: LineageOS Ext 24 for the Redmi Note 13 Pro 5G says flashing it through OrangeFox breaks the storage (see our Redmi Note 13 Pro 5G / POCO X6 5G ROMs post).

Download only from orangefox.download

The OrangeFox wiki has a separate impersonators warning. Since March 2025, all official builds are available only from the official download site, orangefox.download, and the team never sends builds to anyone as files. People pretending to be OrangeFox staff in private messages or Telegram chats give out commands with fastboot or erase that can hard-brick a phone. Don’t run any command you haven’t checked yourself.

How to install OrangeFox (official guide)

These steps follow the OrangeFox wiki’s installation guide. Before you start:

• Unlock the bootloader: see our HyperOS bootloader unlock guide.
• Make a full backup of your data and internal storage. The wiki answers “Should I back up?” with “Yes. Yes. YES. YES.”.
• Install ADB and Fastboot and the USB drivers on your PC.
• Read your phone’s notes on orangefox.download. The method below depends on the type of phone, and the maintainer’s instructions come first.

Already have a custom recovery? Flash the zip

Flash the OrangeFox zip with OrangeFox itself or any TWRP-compatible recovery, the same way you flash any other zip, without any wipes. Use the same method to upgrade or downgrade OrangeFox. Never flash the OrangeFox zip with fastboot.

First install from fastboot

1. Download the correct OrangeFox zip to your phone and to your PC. Extract recovery.img from the zip and copy it to your ADB folder.
2. Reboot the phone into bootloader mode, for example with adb reboot bootloader, and open a command window in the ADB folder.
3. Use the command for your type of phone:
   • A-only phone, or an A/B / Virtual A/B phone with a dedicated recovery partition: fastboot flash recovery recovery.img (or the command your maintainer gives). Then boot into OrangeFox with Power + Volume Up or fastboot reboot recovery.
   • Standard “boot-as-recovery” A/B or Virtual A/B phone (the wiki names the POCO F3 and POCO F4 as examples): boot it temporarily with fastboot boot recovery.img.
   • ROM that uses vendor_boot as recovery: none of these works, so you need instructions from your ROM’s maintainer.
4. When OrangeFox has started, check that it has mounted the data partition and that the touchscreen works.
5. Find the OrangeFox zip on the phone, tap it and swipe to install. This step is required, because OrangeFox needs files from the zip. The phone then reboots into OrangeFox.

The most dangerous mistake: never run fastboot boot on a Virtual A/B phone that has a dedicated recovery partition. The wiki says it bricks the device. Several maintainers repeat this on their device pages, for example for the Redmi Note 13 Pro 5G, the Redmi Note 12 / 13 4G and the Redmi Note 14 Pro+ 5G.

To find out whether your phone is A/B, run adb shell getprop ro.boot.slot_suffix. It prints _a or _b on an A/B phone and nothing on an A-only phone.

Device-specific notes from the maintainers

• Redmi Note 13 Pro 5G / POCO X6 5G, Redmi Note 12 / 13 4G family, Redmi Note 14 Pro+ 5G: trying fastboot boot can brick the phone. Run fastboot flash recovery recovery.img, then fastboot reboot recovery, then flash the OrangeFox zip. On the Redmi Note 14 Pro+ 5G the recovery may not boot with the non-bypass variant of WildKernel.
• POCO F5 Pro: fastboot boot doesn’t work. Use fastboot flash recovery_ab recovery.img. Some ROMs (MIUI, LineageOS) overwrite the recovery, so reflash OrangeFox right after them.
• POCO F3: install it by flashing the zip, and never flash the recovery image with fastboot flash boot. If decryption breaks after a new ROM (stuck on the OrangeFox logo), flash the OrangeFox zip again.
• Redmi Note 9S / 9 Pro family: the FBEv2 build is not for FBEv1 ROMs, MIUI or HyperOS ports, and there is a separate FBEv1 build. Redmi Note 7: the kernel-4.19 build is not for ROMs with a 4.4 kernel.
• Redmi Note 13 Pro 5G / POCO X6 5G: the maintainer says to reflash the OrangeFox zip right after every ROM install. The Flash current OrangeFox and Reflash OrangeFox after flashing a ROM options put it on the inactive slot too.

Upgrade, uninstall and a broken touchscreen

• Upgrade: first remove any OrangeFox password or PIN you set, then flash the new OrangeFox zip like any other zip.
• Uninstall: open Fox Addons → Remove OrangeFox files and swipe. Then flash another recovery (stock or custom) to replace OrangeFox.
• Touchscreen not working: from R11.3 you can use HW GUI Control. The volume buttons move between elements and the power button selects. On the POCO F4 build you turn it on by holding Volume Up and Volume Down for 3 seconds. The wiki says it’s an emergency mode, not for everyday use.

FAQ

Does OrangeFox support Android 17?

Some R12 builds do. The POCO F3 build (R12.0_1) is a unified release for Android 13–17, the Redmi Note 13 Pro 5G build mentions improved Android 17 support, and the Redmi Note 14 Pro+ 5G build supports Android 14–17 decryption. The May 2026 R12.0 builds for older phones list Android 13–16 only.

Is OrangeFox better than TWRP?

OrangeFox is built on TWRP code with its own features and interface, and the team contributes fixes back to TWRP. For a modern Xiaomi phone, what matters is which recovery has an up-to-date build for your codename and your ROM’s Android version.

Can I use OrangeFox with HyperOS or MIUI?

It depends on the build. Several maintainers say “do not use with MIUI ROMs” (POCO X3 Pro, Redmi Note 7 and 7 Pro, Redmi Note 9 Pro family), while others work with stock ROMs. Check the notes for your device. Remember that a stock HyperOS update can overwrite the recovery.

Where is the official OrangeFox download?

Only on orangefox.download. The team doesn’t send builds as files, and links in DMs or random Telegram chats are not official.

I flashed recovery.img but OrangeFox doesn’t work properly. Why?

Flashing only the image isn’t enough. The maintainers stress that you must boot OrangeFox and then flash the OrangeFox zip from it.

Sources: OrangeFox wiki (installing OrangeFox, impersonators warning, HW GUI Control); OrangeFox download server and API (device pages, release notes and changelogs, checked November 14, 2026); official OrangeFox R12.0 thread for the POCO F3 by DarthJabba9 (R12.0 announcement of March 15, 2026 and R12.0_1 release notes); 4PDA unofficial OrangeFox R12 for the POCO X7 Pro and LineageOS Ext 24 for garnet.

The post OrangeFox Recovery R12 for Xiaomi, Redmi & POCO (2026): Download, Android 17 Support & How to Install appeared first on Xiaomi Firmware.

Warning: don’t flash China (Redmi Turbo 4) firmware

Both POCO X7 Pro threads on 4PDA (the HyperOS firmware thread and the custom-ROM thread) open with the same line: installing firmware for China bricks the POCO X7 Pro. This matters right now. China’s HyperOS 4 (OS4.0.3.0.XOJCNXM, Android 17) came out on November 11, and the 4PDA post with it says it is meant only for the Redmi Turbo 4.

You don’t need it. Xiaomi’s global schedule puts the POCO X7 Pro in the mid-November 2026 HyperOS 4 wave, and our HyperOS 4 tracker shows the moment a build appears for your region. Use only Global, EEA, India, Indonesia, Russia, Taiwan or Turkey firmware, and only custom ROMs built for rodin.

Android 17 custom ROMs for the POCO X7 Pro

We checked the official builds on November 14, 2026 against each project’s own update server and download page. The unofficial builds are as posted in the 4PDA thread.

On Android 16 you’ll find official crDroid 12.11, LunarisAOSP 3.13, AxionAOSP 2.9, LineageOS 23.2, VoltageOS, AlphaDroid and several ports (OxygenOS 16.5, NothingOS 4.1, ColorOS 16). Note that the official AxionOS listing for rodin still shows only a June 2026 Android 16 beta. The newer Axion builds in the thread are unofficial.

Which ROM should you pick?

• crDroid 13: official, monthly builds with OTA updates and the October 2026 security patch. Lots of customisation. Add GApps yourself.
• Project Infinity X 4.2: the newest official build (November 13). It comes in a GApps version, so you don’t have to flash Google apps separately. According to the 4PDA post for 4.0, it includes MIUI Camera and bypass charging.
• LineageOS 24: a clean LineageOS on Android 17 with a rebuilt Xiaomi Parts app (CPU and GPU controls, bypass charging, panel colour). Its builder calls it work in progress but stable. Official LineageOS doesn’t support this phone.
• PixelOS 17 and ASCP 6.3: Pixel-style systems with Google apps included. PixelOS ships MIUI Camera 6.4 with the Leica mod.
• Ports (ColorOS 17, One UI 9): only for experimenting. The One UI 9 port’s author lists no fingerprint, Bluetooth or NFC and warns not to set a screen password, because the phone may not accept it after a reboot and you’d have to wipe it.

Before you start

• Check your model. The 4PDA thread lists rodin as POCO X7 Pro 2412DPC0AG (Global), 2412DPC0AI (India) and Redmi Turbo 4 24129RT7CC (China). Don’t flash these ROMs on the regular POCO X7 (malachite), which is a different phone.
• Unlocked bootloader. Follow our HyperOS bootloader unlock guide. Unlocking erases the phone.
• Remove your Google accounts before a fresh install, as crDroid’s guide asks, so Factory Reset Protection doesn’t lock you out after the format.
• Back up everything and charge the phone to more than 60%, as the Infinity X guide asks. On this MediaTek phone, also back up the nvram, nvdata, nvcfg, persist, protect1 and protect2 partitions, which hold the IMEI and calibration data (see our POCO X7 Pro tips).
• Latest Global firmware and Platform Tools. crDroid asks you to be on the latest firmware for your device. Get current ADB and Fastboot. On Windows, the MediaTek drivers from the 4PDA thread header help the PC see the phone.
• Never relock the bootloader with any modifications. This is the second rule in the 4PDA thread header.

How to install a custom ROM on the POCO X7 Pro

On this phone the custom recovery lives in the vendor_boot partition, so every ROM comes with its own vendor_boot.img (some with boot.img, dtbo.img or init_boot.img too). Always download the images from the same place as your ROM build and follow that ROM’s guide.

crDroid 13 (official guide)

1. Download the latest crDroid zip, the vendor_boot.img from crDroid’s recovery folder and, if you want, GApps.
2. Power off the phone, then hold Volume Down + Power until fastboot appears. Check that the PC sees it with fastboot devices.
3. Flash the recovery to both slots:

   fastboot flash vendor_boot --slot=all vendor_boot.img

4. Reboot into recovery: with the phone off, hold Volume Up + Power until the logo appears. Don’t boot into the old system first, because that overwrites the new recovery. If you don’t see the crDroid logo, you’re in the wrong recovery, so start again.
5. For a first install, tap Factory Reset → Format data. This removes encryption and deletes everything in internal storage.
6. Go back, choose Apply update → Apply from ADB and run adb sideload crdroid.zip on the PC. Then add GApps the same way if you want them.
7. Format data, then Reboot to system.

crDroid warns that custom kernels and mods may break the sensors or camera on this ROM.

Project Infinity X 4.2 (official guide)

1. Download boot.img and vendor_boot.img from the Infinity X recovery folder for rodin (use the folder with the same date as your build) and the ROM zip.
2. Run adb reboot bootloader, then:

   fastboot flash boot boot.img
   fastboot flash vendor_boot vendor_boot.img
   fastboot reboot recovery

3. In recovery, go to Wipe → Format Data and confirm.
4. Go to Advanced → ADB Sideload and run adb sideload Project_Infinity-X-…-OFFICIAL.zip.
5. Only for the Vanilla build: if the recovery asks “Install another zip”, choose Yes and sideload your GApps. Otherwise open ADB Sideload again. Skip this step for the GApps build.
6. Optionally wipe data once more, then Reboot System.

Unofficial builds (LineageOS 24, PixelOS 17, ASCP 6.3)

The 4PDA posts use the same pattern. In fastboot, flash the images that come with the build: vendor_boot.img for PixelOS 17, plus boot.img and dtbo.img for LineageOS 24, or boot.img and init_boot.img for ASCP. Then reboot to recovery, use Apply update → Apply from ADB with adb sideload rom.zip, Format data and reboot. The PixelOS builder notes that its recovery can act strangely with sideload. His workaround: enter sideload mode, cancel, then enter it again.

Which GApps to use with a Vanilla build: see our GApps for Android 17 guide.

Updating, root and recovery

• Updates: crDroid updates through its built-in Updater (Settings → System → Update), or in recovery with the same steps but without the factory reset. You don’t need to reflash GApps unless a newer version is out.
• Root: the 4PDA posts describe patching the ROM’s init_boot.img with Magisk, KernelSU or APatch and flashing it with fastboot flash init_boot patched.img. See our Magisk root guide.
• OrangeFox: the thread lists OrangeFox 12.0, also flashed to vendor_boot (there is no official build for rodin yet: see the official OrangeFox R12 list for Xiaomi). The unofficial build by Wang Zhiyu works only with the AOSP kernel 6.6.89, not with 6.6.56.

Going back to HyperOS

This follows the 4PDA guide for flashing official firmware on an unlocked POCO X7 Pro (by Nokeew):

1. Download the Fastboot ROM for your region from our POCO X7 Pro firmware page. Never use a China build. Unpack it into the folder with ADB and Fastboot. A short path such as C:\adb works best.
2. Power off the phone, then hold Power + Volume Down until the fastboot screen appears, and connect it to the PC.
3. Run flash_all.bat. It erases all data and keeps the bootloader unlocked. flash_all_except_storage.bat keeps your data, and flash_all_lock.bat erases data and locks the bootloader.
4. Wait for the phone to reboot.

Before you flash an older build, check anti-rollback. Use flash_all_lock only with an official ROM of your phone’s own region (see ROM regions).

“Storage corrupted, your device is at risk” after custom ROMs? A 4PDA user (anomi75) traced this to the persist partition and fixed it like this: install any PixelOS build with Format data, complete the setup and power off. Then flash the HyperOS Fastboot ROM with flash_all, and lock the bootloader only after that if you want to.

FAQ

When will the POCO X7 Pro get HyperOS 4?

Xiaomi’s global schedule lists the POCO X7 Pro in the mid-November 2026 wave, with regions following over the next weeks. Track it on our HyperOS 4 tracker or firmware page. Don’t flash the China HyperOS 4 for the Redmi Turbo 4: China firmware bricks the POCO X7 Pro.

Which custom ROM is best for the POCO X7 Pro?

For Android 17 with official updates, crDroid 13 or Project Infinity X 4.2. Pick the Infinity X GApps build, or PixelOS 17 / ASCP if you want Google apps included. LineageOS 24 is the choice for a minimal system, but it’s unofficial.

Is there official LineageOS for the POCO X7 Pro?

No. LineageOS 24 and 23.2 for rodin are unofficial builds posted in the 4PDA thread.

Can I install these ROMs on the Redmi Turbo 4?

The builds are for the same codename, rodin, and the 4PDA thread covers both phones. Each ROM’s own guide is written for the POCO X7 Pro, so check the build post before flashing a China unit.

Do I lose my data?

Yes. The first install needs Format data, which erases everything, including internal storage. Later updates of the same ROM don’t.

Sources: 4PDA POCO X7 Pro / Redmi Turbo 4 custom-ROM thread (header, edited by -=©DRU987=- on 09.11.26) and ROM posts for crDroid 13, Infinity X 4.0, LineageOS 24, PixelOS 17, ASCP 6.3, One UI 9 port, OrangeFox 12.0 and the storage-corrupted fix by anomi75; 4PDA POCO X7 Pro HyperOS firmware thread (header with model numbers and the China warning, OS4.0.3.0 China post, official firmware flashing guide by Nokeew); crDroid 13 install guide for rodin; Project Infinity X rodin flash guide and download page; AxionOS official OTA server.

The post Best Custom ROMs for POCO X7 Pro (2026): Android 17 crDroid, Infinity X, LineageOS 24 & How to Install appeared first on Xiaomi Firmware.

Do you need GApps at all?

Only if your ROM comes without Google apps. Many Android 17 ROMs for Xiaomi, Redmi and POCO phones already include them: PixelOS and Evolution X have them built in, and Project Infinity X offers a separate build with Google apps (GApps). Don’t flash a GApps package on top of those. You need GApps for Vanilla builds, for official LineageOS, and for ROMs such as crDroid, which ship without them.

LineageOS also points to microG, an open-source alternative to Google services, if you’d rather not install Google’s apps.

GApps for Android 17: the options in November 2026

We checked the versions below on November 13, 2026 on each project’s own release page.

Not for Android 17: FlameGApps was discontinued (its last builds stop at Android 12.1), and Open GApps has nothing newer than Android 11, with its last builds from 2022.

Which GApps should you pick?

• MindTheGapps: the safe default. It’s a single, simple package and the only one the LineageOS wiki lists for LineageOS 24. The wiki warns that users often run into problems when they use other packages on LineageOS.
• NikGapps: the most flexible. The ready-made packages run from core (just what the Play Store needs) to full (Pixel apps, Gmail, Chrome, Android Auto and more). A nikgapps.config file lets you skip any app. On crDroid, use the NikGapps build from crDroid’s own download page.
• BiTGApps: many sizes from Core to Full, a set of addons (Chrome, Gboard, Maps, Photos and others), and the option to install it as a Magisk or KernelSU module instead of flashing it in recovery. Its Nano, Atom, Pico, Full and Tint variants need a 64-bit phone and Android 14 or newer. See our BiTGApps download page for the build table.
• LiteGapps: small packages. It’s the second choice that LineageOS Ext 24 names after MindTheGapps.

Pick the right file: Android 17 and arm64

A GApps package depends only on two things: the Android version and the CPU architecture. LineageOS says the same.

• Android version: use the Android 17 package for an Android 17 ROM. Look for 17.0.0 in MindTheGapps, the Android-17 folder in NikGapps, and API 37 in LiteGapps. Don’t use Android 16 GApps on an Android 17 ROM, or the other way round.
• Architecture: practically every Xiaomi, Redmi and POCO phone from recent years is arm64. The LineageOS device page for your phone lists it. You can also check with ADB: adb shell getprop ro.product.cpu.abi returns arm64-v8a on a 64-bit phone.

How to install GApps on a custom ROM

These steps follow the LineageOS wiki and install guide, the official NikGapps flashing guide and crDroid’s install guide. The exact order differs a little between ROMs, so check the guide for your phone first. For the ROM part, see our posts on custom ROMs for the POCO F7, the POCO X7 Pro and the Redmi Note 13 Pro 5G / POCO X6 5G, and the LineageOS 24 device list.

1. Install the ROM in recovery as its guide says, for example with Apply update → Apply from ADB and adb -d sideload rom.zip on the PC. Don’t boot into the system yet.
2. Reboot back into recovery. After the ROM sideload, LineageOS and crDroid ask whether to reboot to recovery to install add-ons. Answer Yes. Most recent Xiaomi phones are A/B devices: the ROM goes to the other slot, and NikGapps explains that you must reboot to recovery so the GApps land on that same slot.
3. Sideload the GApps zip the same way: Apply update → Apply from ADB, then adb -d sideload MindTheGapps-17.0.0-arm64-….zip (or your NikGapps, BiTGApps or LiteGapps file).
4. If the phone shows Signature verification failed, tap Yes to continue. LineageOS says this is expected, because add-ons aren’t signed with the ROM’s key.
5. Format data if this is a clean install and you haven’t done it yet. LineageOS and crDroid do the format before the ROM. The NikGapps guide wipes data after the GApps.
6. Reboot to system. The first boot takes longer than usual.

Already booted without GApps? LineageOS warns that you then have to factory reset and install them, or expect crashes. The same applies if you want to try an older or a different GApps package.

Updating the ROM and switching packages

• ROM updates: GApps usually survive an update thanks to their addon.d scripts. crDroid still asks you to flash the GApps zip again after updating in recovery, or to reboot to recovery after an OTA update and flash it again.
• Updating GApps themselves is rarely needed: the apps update from the Play Store. NikGapps recommends a new package only when its changelog fixes a problem you actually have.
• Switching to a different package (for example from MindTheGapps to NikGapps) or downgrading needs a clean flash with a data wipe. NikGapps says it can’t be installed over another GApps package or over a stock ROM.
• Moving to a new Android version (for example from LineageOS 23.2 to 24) needs the GApps for the new version. Follow your ROM’s upgrade instructions.

Common problems

• Setup wizard gets stuck (NikGapps FAQ): connect to Wi-Fi, set that network to unmetered in the Wi-Fi settings, then finish the setup.
• Apps crash after the first boot: the system most likely started before the GApps were installed. Do a factory reset and install them again before the first boot (LineageOS).
• “Not enough space” or storage full error during installation (NikGapps FAQ): pick a smaller variant such as core, or free up system space. NikGapps also suggests setting InstallPartition in nikgapps.config.
• Contacts don’t sync (NikGapps FAQ): in Settings → Apps, show system apps, open Google Contacts Sync and allow the Contacts permission. Then check Google Play Services permissions.

FAQ

What are the best GApps for Android 17?

For most people, MindTheGapps 17.0.0 arm64: it’s the package LineageOS recommends for LineageOS 24 and works with most ROMs. Take NikGapps if you want to choose your apps, or BiTGApps if you want a module install or a specific size.

Is there NikGapps for Android 17?

Yes. The first NikGapps release for Android 17 came out on November 10, 2026, in core, basic, omni, stock, full, go and corego variants.

Is there BiTGApps for Android 17?

Yes. BiTGApps released its first Android 17 package on August 23, 2026. All variants and files are on our BiTGApps page.

Can I install GApps on HyperOS?

No, and you don’t need to: Global and EEA HyperOS already include Google services. These packages are for custom ROMs. NikGapps explicitly says it can’t be installed over a stock ROM.

Can I flash GApps after I’ve already set up the ROM?

Not without a reset. LineageOS says that if you boot the ROM before installing GApps, you have to factory reset and then install them, otherwise apps will crash.

Arm or arm64?

arm64 for practically every modern Xiaomi, Redmi and POCO phone. If in doubt, run adb shell getprop ro.product.cpu.abi: arm64-v8a means arm64.

Sources: LineageOS wiki: Google Apps and the LineageOS install guide (add-ons section); MindTheGapps 17.0.0 releases; NikGapps downloads and changelog, NikGapps flashing guide and NikGapps FAQ; BiTGApps official site; LiteGapps Android 17 builds; crDroid install guide and crDroid GApps folder; LineageOS Ext 24 post in the 4PDA garnet thread; Open GApps.

The post GApps for Android 17 (2026): MindTheGapps vs NikGapps vs BiTGApps vs LiteGapps, Download and Install appeared first on Xiaomi Firmware.

Android 17 custom ROMs for the Redmi Note 13 Pro 5G / POCO X6 5G

We checked the versions and dates below on November 13, 2026 against each project’s own download page or update server. “Official” means the ROM project lists the device itself. All builds are for the codename garnet, so the same file works on both phones.

On Android 16 the list is even longer: official LineageOS 23.2 (weekly builds, the latest from November 11, 2026, on download.lineageos.org), plus official AxionOS 2.9 (October 24, 2026, VANILLA and CORE builds; still based on Android 16), Evolution X, WitAqua, AlphaDroid, Halcyon, DerpFest, Rising Revived, a crDroid 12 build and ports of OxygenOS 16. The 4PDA thread header keeps the full list with links.

Which ROM should you pick?

• crDroid 13: lots of customisation, official monthly builds with OTA updates and a recent security patch. Add your own GApps.
• Project Infinity X 4.1: the newest official Android 17 build for garnet (October 25). It comes in a version with Google apps, so you don’t have to flash GApps separately.
• PixelOS 17: a clean Pixel-style system with Google apps built in. Its maintainer asks for the latest HyperOS 3.0 (Android 16) firmware.
• ASCP 6.3: built on the OS3.0.302.0 Global stock files. According to its changelog it unlocks the Leica camera UI and filters, adds dual video recording and updates the Adreno GPU drivers.
• LineageOS Ext 24: LineageOS on Android 17 with KernelSU-Next built in, but it’s a beta community build. If you want official LineageOS with updates, stay on 23.2 for now. Our LineageOS 24 device list shows which Xiaomi phones already have official builds.

Before you start

• Check your model. LineageOS lists these model numbers for garnet: Redmi Note 13 Pro 5G 2312DRA50G and XIG05, 2312DRA50I (India), 2312DRA50C and 2312CRAD3C (China), and POCO X6 5G 23122PCD1G and 23122PCD1I (India). Don’t flash these ROMs on the Redmi Note 13 Pro 4G or the POCO X6 Pro, which are different phones.
• Unlocked bootloader. Follow our HyperOS bootloader unlock guide. Unlocking erases the phone.
• Test the phone on stock first. The LineageOS guide asks you to check calls, SMS, Wi-Fi calling and VoLTE on HyperOS. If something doesn’t work on stock, it won’t work on a custom ROM either.
• Remove your Google accounts before you start, so Factory Reset Protection doesn’t lock you out after the format.
• Back up everything. A clean install formats the phone, including internal storage.
• A PC with current Platform Tools. Get the latest ADB and Fastboot.
• Never relock the bootloader with any modifications. This rule sits at the top of the 4PDA thread for this phone. A relocked phone running a custom ROM or modified files may not boot again.

Step 1: Get the firmware your ROM needs

Custom ROMs use the phone’s firmware (modem, bootloader and other low-level partitions) from HyperOS, so each ROM names the firmware it expects:

• Official LineageOS 23.2 requires an exact firmware version. The LineageOS wiki says to upgrade or downgrade to it if you are on a newer or older one, because the wrong firmware can cause failed installs, crashes or even permanent damage:

• PixelOS 17 and LineageOS Ext 24 ask for the latest HyperOS 3.0 (Android 16) firmware.
• Project Infinity X‘s official flash guide installs the Global firmware package in recovery right before the ROM.

If you are on stock HyperOS for your region, the phone already has that region’s firmware. The 4PDA install guide says you can skip the firmware step in that case, as long as the version matches what your ROM asks for (check Settings → About phone). Otherwise download a firmware-only package for garnet from XiaomiFirmwareUpdater and flash it in recovery with adb sideload, as in the steps below. LineageOS has a separate firmware update guide for this phone. Full stock HyperOS ROMs for every region are on our Redmi Note 13 Pro 5G / POCO X6 5G firmware page.

Step 2: Install the ROM (clean flash)

These steps follow the official LineageOS install guide for garnet. The PixelOS guide for this phone uses the same images and commands. Other ROMs differ in small details, so always read the guide that comes with your build.

1. Download boot.img, dtbo.img, vendor_boot.img and recovery.img from the same page as your ROM build (PixelOS lists them under “Additional Images”, crDroid links its recovery on the download page).
2. Power off the phone, then hold Volume Down + Power until the word FASTBOOT appears.
3. Flash the images:

   fastboot flash boot boot.img
   fastboot flash dtbo dtbo.img
   fastboot flash vendor_boot vendor_boot.img
   fastboot flash recovery recovery.img

4. Reboot into the new recovery: fastboot reboot recovery (or, with the phone off, hold Volume Up + Power until the MI logo appears).
5. If you need to update the firmware, choose Apply update → Apply from ADB, run adb sideload fw_garnet*.zip on the PC, then reboot back into recovery.
6. Choose Factory reset → Format data / factory reset and confirm. This removes encryption and deletes everything in internal storage. (PixelOS does the format right after the sideload instead. Both orders end with a formatted phone.)
7. Go back, choose Apply update → Apply from ADB and run adb -d sideload /path/to/rom.zip on the PC. Don’t reboot to the system yet.
8. Optional: to add Google apps to a Vanilla build, run Apply from ADB again and sideload the Android 17 arm64 GApps package before the first boot (which one to choose: GApps for Android 17). When the phone says Signature verification failed, tap Yes. LineageOS says this is expected, because add-ons aren’t signed with its key.
9. Choose Reboot system now. The first boot usually takes no longer than 15 minutes.

Notes from the LineageOS wiki and the 4PDA thread:

• Touch doesn’t work in Lineage recovery on this phone (4PDA guide by DuckGPTv4). Use the volume buttons to move and the power button to select.
• If the PC stops at 47% with adb: failed to read command: Success (or No error), the install still worked. The wiki calls this normal.
• Use the recovery your ROM names. LineageOS Ext 24 says to use only its own Lineage recovery, because flashing it through OrangeFox breaks the storage. Project Infinity X’s official guide, on the other hand, uses OrangeFox (firmware, then ROM, then optional GApps, then Format data).
• If signature verification fails on the ROM zip itself (official LineageOS), download it again. The file is corrupted or not an official build.

Updating and switching ROMs

• Update the same ROM: use the ROM’s built-in updater, or sideload the new zip in recovery without formatting. Project Infinity X’s guide wipes only cache and Dalvik for such a “dirty” update. If the new build asks for newer firmware, flash that first.
• Switch to a different ROM: do the full clean install above, including Format data.

Going back to HyperOS

Flash the official Fastboot ROM for your region from our firmware page with Mi Flash and Clean all. Before you flash an older build, check anti-rollback. Relock the bootloader only on an unmodified official ROM that matches your phone’s region (see ROM regions).

FAQ

Will the Redmi Note 13 Pro 5G or POCO X6 5G get HyperOS 4?

Not according to Xiaomi’s current plans. The phone isn’t on Xiaomi’s global HyperOS 4 schedule, so it stays on HyperOS 3 (Android 16). Xiaomi lists security updates until January 2028. Our news post explains what owners get instead, and the HyperOS 4 tracker will show it if that ever changes. For Android 17, a custom ROM is the only option.

Are the POCO X6 5G and Redmi Note 13 Pro 5G ROMs the same?

Yes. Both phones share the codename garnet, and every ROM in this list has one build for both. LineageOS keeps separate wiki pages per model only because the required firmware differs by region.

Is there official LineageOS 24 for garnet?

Not yet. Official LineageOS for this phone is 23.2 (Android 16), with weekly builds. The Android 17 option is LineageOS Ext 24, a community beta.

Which custom ROM is best for the Redmi Note 13 Pro 5G?

For Android 17 with regular official updates, start with crDroid 13 or Project Infinity X 4.1. Pick PixelOS 17 or the GApps build of Infinity X if you want Google apps built in. For the most stable LineageOS, use official 23.2 on Android 16.

Do I lose my data?

Yes. The first install needs Format data, which erases everything, including internal storage. Later updates of the same ROM don’t.

eSIM doesn’t work on LineageOS. Can I fix it?

A 4PDA user (qlost) got eSIM working on LineageOS 23 for garnet with OpenEUICC. After installing it, the SIM on/off switch and adding an eSIM work again. The thread header links that post.

Sources: 4PDA POCO X6 5G / Redmi Note 13 Pro 5G custom-ROM thread (header, curator ☆Alex☆, edited 27.09.26); LineageOS install guide for garnet by DuckGPTv4; ROM posts for ASCP 6.3, PixelOS 17 and LineageOS Ext 24; eSIM fix by qlost; LineageOS wiki: garnet install guide and model variants; PixelOS garnet page and instructions; crDroid for Redmi Note 13 Pro 5G; Project Infinity X garnet flash guide; ASCP garnet changelog; AxionOS official OTA server.

The post Best Custom ROMs for Redmi Note 13 Pro 5G / POCO X6 5G (2026): Android 17 Without HyperOS 4 appeared first on Xiaomi Firmware.

Android 17 custom ROMs for the POCO F7

Versions and dates below were checked on November 13, 2026 against each project’s own download page or update server. “Official” means the build is listed by the ROM project itself; unofficial builds come from independent builders.

Android 16 builds are still around too: official AxionOS 2.9 (October 10, 2026; it is still based on Android 16), crDroid 12, Matrixx 12, RisingOS Revived 8.1.1, LunarisAOSP, AfterlifeOS and many more, plus ports of OxygenOS 16 and ColorOS 16.1. For a daily driver on a phone this new, the Android 17 builds above are the ones that are actively maintained.

Which ROM should you pick?

The 4PDA POCO F7 custom-ROM thread runs a poll “Which firmware do you use?”. Of 136 votes, crDroid got 42 (31%) and Project Infinity X 40 (29%), well ahead of LineageOS-based builds (14), PixelOS (13), Evolution X and Matrixx (6 each). A quick guide from that and from the ROM pages:

• crDroid 13: the most popular choice. Lots of customisation, official monthly builds with OTA updates, and a recent security patch. Add your own GApps.
• Project Infinity X 4.2: the newest official build (November 9), offered both with and without Google apps, so you don’t have to flash GApps separately.
• PixelOS 17: a clean Pixel-style system with Google apps built in and monthly releases.
• Evolution X 12.4: Pixel features and Google apps included, but it’s an unofficial build. Its builder recommends doing a clean flash when coming from any other ROM.
• DerpFest 17: the 4PDA user who posted the build reported fast battery drain on the stock kernel and the camera crashing on every shot on the Global 47G model, so treat it as one to test rather than a safe daily driver.

Before you start

• Check your model. All of these ROMs are for onyx: POCO F7 25053PC47G (Global), 25053PC47I (India) and Redmi Turbo 4 Pro 25053RT47C (China). Don’t flash them on the POCO F7 Pro or F7 Ultra, which are different phones.
• Unlocked bootloader. Follow our HyperOS bootloader unlock guide. For the China Redmi Turbo 4 Pro, 4PDA notes that Xiaomi has completely removed bootloader unlocking for China units, so the official route doesn’t work there.
• Back up everything. A clean install formats the phone, including internal storage.
• Back up your IMEI partitions. The 4PDA thread links a backup method that needs root and Termux (below). Keep the files private.
• A PC with current Platform Tools. The 4PDA install guide stresses that an old ADB may simply fail to start the sideload. Get the latest ADB and Fastboot.

IMEI backup (from the 4PDA thread)

With root, run these in Termux. They copy the nv*, protect* and persist partitions (IMEI, SIM, Bluetooth and Wi-Fi data) to an imeibackup folder:

su
mkdir -p /sdcard/imeibackup/ && cp /dev/block/by-name/nv* /sdcard/imeibackup && cp /dev/block/by-name/protect* /sdcard/imeibackup && cp /dev/block/by-name/persist /sdcard/imeibackup

Copy the folder to your PC, then keep it secret and don’t share it with anyone. If you don’t have root yet, see our Magisk root guide.

Step 1: Flash the firmware your ROM needs

Custom ROMs use the phone’s firmware (modem, bootloader and other low-level partitions) from HyperOS, so each ROM names the firmware it expects. Check the ROM’s own post or page: for example, the Evolution X builder asks for the latest stable Global HyperOS 3 firmware, and the PixelOS post asked for the latest Android 15 / HyperOS 2 firmware when it was published. The 4PDA thread header explains how to flash a firmware package:

1. Download the firmware you need from the links in the thread header (fw-onyx or XiaomiFirmwareUpdater) and unpack it.
2. Boot the phone into Fastboot: turn it on while holding Volume Down.
3. Run the script from the package and wait until it finishes.

Current stock HyperOS builds for every region are on our POCO F7 firmware page.

Step 2: Install the ROM (clean flash)

This is the official flashing guide that Project Infinity X publishes for onyx. PixelOS, BlissROMs and Evolution X use the same image set with only small differences, so always read the guide that comes with your ROM.

1. Download the image files from the same place as your ROM build: boot.img, dtbo.img, init_boot.img, recovery.img and vendor_boot.img (PixelOS lists them under “Additional Images”).
2. Power off the phone, then hold Volume Down + Power until the word FASTBOOT appears.
3. Flash the images:

   fastboot flash boot boot.img
   fastboot flash dtbo dtbo.img
   fastboot flash init_boot init_boot.img
   fastboot flash recovery recovery.img
   fastboot flash vendor_boot vendor_boot.img

4. Reboot into recovery to check it worked: fastboot reboot recovery
5. Download the ROM .zip for onyx.
6. Sideload it, but don’t reboot to the system before finishing the next steps. On the phone choose Apply update → Apply from ADB; on the PC run adb -d sideload /path/to/rom.zip
7. Choose Factory Reset → Format data / factory reset and confirm.
8. Reboot to system. The first boot takes a while.

Notes from the 4PDA install guide (by elektrovenick, updated October 23, 2026):

• Put the ROM zip in a short path without spaces or Cyrillic letters, for example the root of drive C:, to avoid errors.
• When the sideload reaches 47% and the phone asks a question, tap No, then do the factory reset / format data. Stopping at 47% on the PC side is normal.
• If your ROM has no Google apps and you want them, reboot back into recovery, open sideload again and run adb sideload with the GApps zip (MindTheGapps or NikGapps for Android 17, see our GApps for Android 17 guide), then start the system.
• The LineageOS-style recovery that comes with these ROMs isn’t suitable for ColorOS, OxygenOS or HyperOS ports.

Updating and switching ROMs

• Update the same ROM: use the ROM’s built-in updater, or download the new zip, open recovery, choose Apply update and install it from storage or with adb sideload. A format isn’t needed (PixelOS and Evolution X describe the same “dirty flash”).
• Switch to a different ROM: same sideload steps, but do a factory reset / format data after installing.

Touch not working in recovery?

The 4PDA thread has a dedicated post for this (elektrovenick). It can happen after installing ColorOS or OxygenOS ports, after flashing vendor_boot from some guides, or after HyperOS. In order:

• Boot fully into the system once, then try recovery again.
• Use the latest OrangeFox from the thread header. In OrangeFox 12 a mouse over OTG works; you can also hold both volume buttons for 3–4 seconds to switch to button control (Hardware GUI Control).
• If you plan to stay on custom ROMs, flash the LineageOS-style recovery (for example the one from the Infinity X repository) and install ROMs with adb sideload; that recovery doesn’t break this way.

Going back to HyperOS

Flash the official Fastboot ROM for your region from our POCO F7 firmware page with Mi Flash and Clean all. Before flashing an older build, check anti-rollback, and only relock the bootloader on an unmodified official ROM that matches your phone (see ROM regions).

FAQ

Is HyperOS 4 coming to the POCO F7, or should I install a custom ROM for Android 17?

Xiaomi’s global schedule puts the POCO F7 in the mid-November 2026 HyperOS 4 wave, so the official Android 17 update is close. Our HyperOS 4 tracker shows when a build appears for your region. A custom ROM makes sense if you want a cleaner system or more customisation, not only for Android 17.

Which custom ROM is best for the POCO F7?

By popularity among 4PDA users, crDroid 13 and Project Infinity X 4.2 lead, both official Android 17 builds. PixelOS 17 is the pick if you want Google apps included and a Pixel-like system.

Can I install these ROMs on the Redmi Turbo 4 Pro?

The builds are for the same codename, onyx, but you first need an unlocked bootloader, and 4PDA reports that Xiaomi has removed official bootloader unlocking for China units.

Do I lose my data?

Yes. The first install of a custom ROM needs Format data, which erases everything including internal storage. Updating the same ROM later doesn’t.

Which GApps should I use on Android 17?

The 4PDA guide and the ROM pages point to MindTheGapps and NikGapps; crDroid links NikGapps on its download page. Use the Android 17 (arm64) version, and skip it if your ROM already includes Google apps. Our Android 17 GApps comparison covers all the options.

Sources: 4PDA POCO F7 / Redmi Turbo 4 Pro custom-ROM thread (header and poll, edited by -=©DRU987=- on 01.11.26); ADB sideload install guide by elektrovenick; recovery touch fix by elektrovenick; IMEI backup by Chiaroscuro; ROM posts for DerpFest 17 and PixelOS 17; Redmi Turbo 4 Pro unlock note by *DEMON_ODESSA13*; Project Infinity X official devices and onyx flash guide; crDroid for Poco F7; PixelOS onyx; Evolution X 17 flashing guide by fakhrads.

The post Best Custom ROMs for POCO F7 (2026): Android 17 crDroid, Infinity X, PixelOS & How to Install appeared first on Xiaomi Firmware.

Latest versions (November 2026)

Download root apps only from their GitHub releases. Re-uploads on YouTube, Telegram or “one-click root” sites are a common way to spread malware.

Comparison

Which one for your Xiaomi?

• First root, or you rely on many Magisk modules: Magisk 31.1. Note that 31.1 removed root pop-ups (grant root in advance in the Superuser tab) and the “hide Magisk app” option.
• Xiaomi 13, 14, 15, 17, Redmi Note 13–15, POCO F5–F8, X6–X8 and you want banking apps to work more often: KernelSU Next. It loads SUSFS root hiding itself on stock kernels. Hiding is never guaranteed: Google Wallet contactless and some banks still detect it.
• You want the upstream project with no extras: KernelSU 3.3.1.
• You build or flash custom kernels and want KPM: SukiSU Ultra. On a stock Xiaomi kernel it gives root and modules, but KPM needs a kernel built with KPM support.
• Older Xiaomi/Redmi phones on kernel 4.14–5.4 (Mi 11, Redmi Note 10/11, Helio phones) without a custom kernel: APatch, or Magisk. KernelSU variants need a custom kernel there.

Check your kernel first: Settings → About phone → All specs → Kernel version, or adb shell uname -r. A version like 6.12.23-android16 means GKI (KernelSU works without a custom kernel; the android16-6.12 part is your KMI). Kernel version and Android version are different things, so always check your own phone instead of guessing from the model or the Android version.

Where to get the boot image

All methods need the image from the Fastboot ROM of your exact build (same version and region, e.g. OS3.0.303.0.WOJMIXM):

1. Download the Fastboot ROM (.tgz) from your phone’s page in our firmware hub.
2. Extract it with 7-Zip. The images are in the images folder: init_boot.img (phones launched with Android 13 or later) and boot.img.
3. Keep an unpatched copy on your PC: it’s your way back if the phone bootloops.

The bootloader must be unlocked: how to unlock a Xiaomi bootloader on HyperOS. You need ADB and Fastboot on the PC.

How to install KernelSU / KernelSU Next / SukiSU (LKM)

1. Back up first: copy the unpatched init_boot.img/boot.img to your PC. Flashing it back is how you recover from a bootloop.
2. Install the manager APK from GitHub (for example KernelSU_Next_v3.4.2_33355-release.apk). If it says Not installed, your kernel is supported. Unsupported means you need a custom kernel.
3. Copy init_boot.img (or boot.img on phones without init_boot) to the phone.
4. In the manager tap Install → Select a file, choose the image and, if the manager asks for the KMI, pick the one matching your kernel version (e.g. android16-6.12). On KernelSU 3.3 and newer, choose Backup as stock image when offered: this is what Uninstall → Restore stock image uses before an OTA. The patched file is saved in Download.
5. Copy it to the PC and flash it:
   adb reboot bootloader
fastboot flash init_boot kernelsu_patched_xxxxx.img
fastboot reboot
6. Open the manager: it should show Working (LKM). Before installing modules that change system files, install a metamodule such as meta-overlayfs; without it those modules don’t mount. Add ZygiskNext if you need Zygisk or LSPosed.

How to install APatch

1. Extract boot.img (not init_boot) from the Fastboot ROM of your build and back it up to your PC. Don’t use a boot.img that was already patched by Magisk or KernelSU. APatch supports ARM64 kernels 3.18–6.12 only.
2. Install the APatch APK, tap the patch button → Select a boot image to patch, choose boot.img and set a SuperKey: 8–63 characters, letters and numbers only (no special characters); weak keys like 12345678 are rejected. Keep it private: the SuperKey grants more than root, so anyone who knows it controls the phone. Then tap Start; the patched file is saved as Download/apatch_xxxxx.img.
3. Flash the result: fastboot flash boot apatch_xxxxx.img, then fastboot reboot. Tip from the APatch docs: fastboot boot apatch_xxxxx.img test-boots the image without flashing it.
4. Open APatch, enter the SuperKey and install AndroidPatch and KernelPatch when the app asks. Use APM for modules, plus ZygiskNext if needed.

APatch 11282 adds support for the newest HyperOS 4 kernels, but its own notes call it an early release, warn that upgrading is risky, and ask you to uninstall embedded KPMs first. If you don’t have a brand-new HyperOS 4 kernel, you don’t need it.

Updating HyperOS on a rooted phone

An update replaces the patched image, so root is gone afterwards. The safest order on Xiaomi:

1. Before an incremental OTA, restore the stock image (manager → Uninstall → Restore stock image), or use the full Recovery ROM of the new build. Install the update and boot normally without root once.
2. Download the Fastboot ROM of the new build, extract its init_boot.img or boot.img, patch it again and flash it.

KernelSU and Magisk also offer Install to inactive slot after an OTA. It is the official method, but it is mainly tested on Pixel phones, and users have reported bootloops with it on a Xiaomi 15 (KernelSU) and a Xiaomi 15 Pro (SukiSU). The order above works on every Xiaomi. If a bootloop happens, flash the stock image of the new build from Fastboot, boot once, then flash the patched one. For the big jump to HyperOS 4, read how to install HyperOS 4 manually first.

Problems and fixes

Don’t mix root methods. Before switching (for example from Magisk to KernelSU Next), uninstall the old one and flash the stock image first.

FAQ

Is KernelSU better than Magisk on Xiaomi?

Not in general. Magisk is easier and has more modules. KernelSU Next is better at hiding root on recent GKI phones, which matters for banking apps. Both are actively maintained.

Does APatch use init_boot.img?

No. APatch always patches boot.img, because it modifies the kernel, not the ramdisk.

Do I need a custom kernel for KernelSU on my Xiaomi?

Not if your kernel is 5.10 or newer with a GKI version string (Xiaomi 12 series and newer, most 2022+ Redmi and POCO). Older kernels need a custom kernel, or use APatch/Magisk.

Does root work on HyperOS 4?

Yes. Owners report Magisk, KernelSU Next and SukiSU working on HyperOS 4 phones such as the Xiaomi 17 series. Re-patch the boot image after every update; if you use the inactive-slot OTA shortcut, keep the new build’s stock image ready.

Can I root without unlocking the bootloader?

No. All these methods flash a modified boot image, which a locked bootloader refuses.

Sources: KernelSU docs (installation, rescue from bootloop, FAQ); APatch installation docs; GitHub release notes of Magisk, KernelSU, KernelSU Next, SukiSU Ultra, APatch and ZygiskNext; 4PDA headers of the KernelSU, KernelSU Next and APatch threads (iMiKED); POCO X7 Pro firmware thread (KernelSU Next GKI guide by -=Saint=-).

The post KernelSU vs KernelSU Next vs SukiSU vs APatch vs Magisk: Best Root for Xiaomi on HyperOS 3 and 4 (2026) appeared first on Xiaomi Firmware.

HyperOS 4: no new global stable build, but test builds for the next waves

No new HyperOS 4 stable build for global, EEA or India phones arrived between November 10 and 12. The only public global builds are still the POCO F8 Pro (Global) and POCO F8 Ultra (Europe); see where the rollout stands.

What did change: on November 12 internal HyperOS 4 test builds showed up on Xiaomi’s servers for many phones of the next two waves, according to XiaomiTime’s firmware feed:

• Mid-November wave: POCO F7 Pro (Indonesia, Russia, Taiwan), Redmi Note 17 5G / POCO M8 Power, Redmi Pad 2 Pro 5G (Global); plus the early-wave POCO X8 Pro Max and Redmi Note 15 5G / POCO M8 5G that are still waiting.
• December wave: Xiaomi 14 Ultra (Global), MIX Flip (Global, EEA), Xiaomi 14T Pro (Turkey), Redmi Note 14 Pro 4G, Redmi Note 14 4G, POCO X7 / Redmi Note 14 Pro 5G (EEA) and Xiaomi Pad 6S Pro 12.4.

Test builds (version numbers like OS4.0.0.5) can’t be installed by owners; they’re a sign that the schedule is on track. In China, the Xiaomi 15 series still has no stable HyperOS 4 build, although Xiaomi’s China plan promises it by November 15. When it lands, the global mid-November wave usually isn’t far behind. Track every device in our HyperOS 4 tracker, which now picks up new global builds automatically.

China builds got security updates on November 10–11: Xiaomi 18 Pro / Pro Max OS4.0.29.0, Xiaomi 17 Pro / Pro Max OS4.0.6.0, Redmi K100 Pro Max OS4.0.7.0, Redmi K90 Pro Max OS4.0.6.0 and Xiaomi Pad 8 OS4.0.12.0.

November security patch: 1 of 74 Xiaomi phones so far

Google’s November Android bulletin fixes 216 vulnerabilities, 23 of them critical, including a zero-click remote code execution flaw; full protection needs patch level 2026-11-05. On Xiaomi’s side, the first build with the November patch is the Redmi A5 / A7 / POCO C71 EEA build A15.0.19.0.VGWEUXM from November 10. That’s 1 of 74 supported devices in our security patch tracker; 26 are on October and the rest are older. Phones that won’t get HyperOS 4, such as the Redmi Note 13 Pro+, still receive HyperOS 3 patch updates (EEA OS3.0.304.0.WNOEUXM, October patch).

Tip: even without a new HyperOS build, install the latest Google Play system update (Settings → About phone → Android version). It carries some of the fixes, including for the “SMS of Death” telephony bug disclosed at the end of October.

November 17 in Paris: more than the Xiaomi 18 Pro

Confirmed. Xiaomi’s global launch on November 17 (14:00 CET) will also bring the Xiaomi Watch S5 41mm, the Smart Band 11, the Xiaomi Clip clip-on open-ear earbuds and new Mijia smart home products, alongside the Xiaomi 18 Pro and 18 Pro Max. No prices yet. The Clip earbuds launched in China in May, so this is their global debut. More on the phones: Xiaomi 18 series codenames and global launch.

Rumor. A tipster says the Xiaomi 18 Pro reaches India in December, while the 18 Pro Max won’t launch there at all. Leaked European prices from October (around €1,449 for the 18 Pro, €1,849 for the Pro Max) are still unconfirmed.

Leaks: Xiaomi 18, Xiaomi 18T and a 10,000 mAh Redmi flagship

• Xiaomi 18 (standard), rumor: retailers in China are taking refundable deposits, and a new leak lists up to 16 GB RAM and 1 TB storage, a 200 MP main camera, 100 W charging and about 200 g. The standard model isn’t part of the Paris event; its China launch is expected in December.
• Xiaomi 18T, rumor: Dimensity 8600, a flat 1.5K OLED at 165 or 185 Hz, IP69, 200 MP main + 50 MP ultrawide + 50 MP periscope, HyperOS 4 out of the box. No date; the 17T launched in May.
• Redmi “K100 Ultra”, rumor: an engineering sample with a 2 nm chip, a battery of about 10,000 mAh, 100 W wired and 50 W wireless charging, bypass charging, a 50 MP 3× periscope and IP68/69. Redmi K Ultra phones usually come to the rest of the world as POCO F Ultra models, usually with a smaller battery.
• Redmi is also said to be testing a 185 Hz refresh rate across the whole interface, not just in games (single source).
• A new Redmi phone for India (model 26119RA82I) passed BIS certification. Its name is unknown; Redmi phones usually launch in India two to six weeks after BIS.

Also this week

• Xiaomi Q3 2026 results come on November 24.
• Xiaomi was 4th in China’s tablet market in Q3, a market that shrank 22.3% year on year.
• New HyperOS 3 updates for the POCO X8 Pro (Russia, India), Redmi Note 14 5G / POCO M7 Pro 5G (Turkey, Russia, Indonesia), Xiaomi 14T Pro (Indonesia) and Redmi 13C (India). Download them on our firmware pages.

New on xiaomifirmware.com

• Xiaomi security patch status: which phones have the latest Android patch, by region.
• LineageOS 24 (Android 17) for 24 Xiaomi, Redmi and POCO phones.
• Magisk 31.1: how to root HyperOS 3 and 4.
• SP Flash Tool v6.2404 and MTK_AllInOne_DA.bin explained.
• Xiaomi ADB/Fastboot Tools 7.0.3 and the best HyperOS alternatives.

FAQ

Did any new phone get global HyperOS 4 this week?

No. Between November 10 and 12 no new global, EEA or India stable build appeared. Test builds exist for the mid-November and December waves.

When does the Xiaomi 15 get HyperOS 4?

Xiaomi’s China plan promises the Xiaomi 15 series by November 15; the global schedule lists it for mid-November. The China build hadn’t appeared by November 12.

Which Xiaomi phones have the November 2026 security patch?

So far only the Redmi A5 / A7 / POCO C71 (EEA build of November 10). Check your model in the security patch tracker.

What will Xiaomi launch on November 17?

The Xiaomi 18 Pro and 18 Pro Max, plus the Watch S5 41mm, Smart Band 11, the Xiaomi Clip earbuds and Mijia products, at a global event in Paris.

Sources: Xiaomi on X; XiaomiTime firmware feed (t.me/miui_download); 91mobiles; Gizmochina; XimiTime; GSMArena; Gadgets360; Android Security Bulletin.

The post Xiaomi News This Week (Nov 8–12): Paris Launch Lineup, HyperOS 4 Test Builds, November Patch and Redmi Leaks appeared first on Xiaomi Firmware.

Xiaomi, Redmi and POCO phones with LineageOS 24

All devices below have official LineageOS 24 builds (moved from LineageOS 23.2); the POCO X4 GT joined after launch. Download links go to the official LineageOS wiki; the last column links our stock firmware page for the same phone, which you’ll need to go back to HyperOS or to update the firmware before installing.

Moved to LineageOS 23.2 (Android 16) instead: Mi 11 Pro (mars) and Mi 11i / Redmi K40 Pro / K40 Pro+ / Mi 11X Pro (haydn). More devices are added as maintainers finish them, so check the LineageOS device list for the current status of your phone.

Not on the list: no current Xiaomi flagship (Xiaomi 14, 15 or 17 series) and no Redmi Note 13–15 or regular Redmi Note 12 (only the Redmi Note 12 Turbo, i.e. POCO F5) has an official LineageOS 24 build yet. For those, unofficial builds exist on XDA and 4PDA (for example for the POCO X7 Pro), and crDroid 13 (also Android 17) is official for some of them.

What’s new in LineageOS 24

• Android 17 base with security patches up to October 2026. It’s out months ahead of HyperOS 4 for many of these phones, several of which (Xiaomi 12 series, Redmi Note 8/9, Redmi 9) will never get Android 17 from Xiaomi.
• Browser flashing: a new flash.lineageos.org tool installs via Fastboot or ADB directly from Chrome/Edge over WebUSB, without installing Platform Tools. The wiki instructions remain the supported way.
• Updater: redesigned, and updates are now streamed on A/B devices, so they install much faster.
• Apps: new image editor Canvas, Material 3 Expressive in many built-in apps, faster Twelve music player, PWA shortcuts in the Jelly browser.
• Older devices on Linux kernels 4.4 and 4.9 stay on LineageOS 22.2, which is why some older Xiaomi phones didn’t move up.

How to install LineageOS 24 on a Xiaomi phone

The steps below summarize the official LineageOS wiki. Your device’s own install page is the reference: follow every section of it exactly, and don’t continue after something fails.

1. Check the basics. Your exact model number must be listed on the device’s wiki page (for example 23049PCD8G for the POCO F5 Global). Boot stock once and test calls, SMS and VoLTE/VoWiFi: if they don’t work on stock, they won’t on LineageOS.
2. Unlock the bootloader (this erases the phone): Xiaomi bootloader unlock on HyperOS.
3. Install the exact stock firmware the wiki lists for your device. It is often older than what you run now (for example, the POCO F5 page requires Android 15 firmware), and the wiki warns that the wrong firmware can cause permanent damage. Going back to an older build is a downgrade with a full wipe: check anti-rollback first. Check the Android version, not the HyperOS version; if there are several updates of the required version, use the latest. Some pages (for example the POCO F3) list an exact HyperOS build per region instead. Remove all Google accounts (the wiki requires this to avoid Factory Reset Protection); signing out of your Mi account and turning off Find Device is also a good idea.
4. Install ADB and Fastboot (or use flash.lineageos.org in Chrome).
5. Download the LineageOS 24 build, the recovery image and every file listed under “Flashing additional partitions” on your device’s install page (often boot.img, dtbo.img and vendor_boot.img; some devices, such as the Redmi Note 8, need none), and flash them exactly in the order shown before the recovery. Missing one gives a recovery that won’t boot or a bootloop.
6. Flash Lineage Recovery with the command on your device’s page. The partition differs per device: on the POCO F5 and Redmi Note 8 it is fastboot flash recovery recovery.img, but on the POCO F3 (alioth) the recovery file is vendor_boot.img and goes to fastboot flash vendor_boot vendor_boot.img. Then boot into recovery. On devices without A/B, such as the Redmi Note 8, don’t boot into HyperOS/MIUI after flashing the recovery: it overwrites Lineage Recovery. Boot straight to recovery with Volume Up + Power.
7. If your device page has an “Ensuring all firmware partitions are consistent” section (for example the POCO F3), sideload the copy-partitions zip from recovery and reboot to recovery before going on. The wiki warns that skipping it can hard-brick the phone if the other slot holds old firmware.
8. In recovery: Factory reset → Format data / factory reset, go back, then Apply update → Apply from ADB and adb -d sideload lineage-24.0-…-nightly-codename-signed.zip. Don’t reboot to system yet. A signature failure means a corrupted or unofficial file; “failed to read command: Success” at 47% is normal.
9. Google apps: LineageOS ships without Google Play. After the ROM sideload, recovery asks whether to reboot to recovery to install add-ons: tap Yes. Then Apply update → Apply from ADB and adb -d sideload MindTheGapps-17…-arm64.zip. When it says “Signature verification failed”, tap Yes (normal for add-ons). Only then choose Reboot system now; the first boot can take up to 15 minutes. If you boot LineageOS before installing GApps, you have to factory reset to add them later. Alternatives are compared in our GApps guide.

Already on official LineageOS 23.2? You don’t need to wipe: use the wiki’s Upgrade to a higher version of LineageOS guide for your device.

Things to know before switching from HyperOS

• Camera: LineageOS uses its own camera app (Aperture); photos are usually weaker than Xiaomi’s camera, especially at night. A GCam port helps on many models.
• Banking apps and Google Wallet may not work because the bootloader stays unlocked.
• Missing Xiaomi features: no HyperOS AI features, Xiaomi cloud, Mi Share or Game Turbo.
• Going back: flash the stock Fastboot ROM for your region with Mi Flash (Clean all). Check anti-rollback before flashing an older stock build.

FAQ

Which Xiaomi phones support LineageOS 24?

24 phones at launch, 25 now: Xiaomi 12, 12 Pro, 12S, 12S Pro, 12S Ultra, 12T Pro, 13, 13 Pro, MIX Fold 2, Mi 10 Pro, Mi 10 Ultra, Mi 10T / 10T Pro, Mi 10T Lite 5G, Mi A3, POCO F3, POCO F5, POCO F5 Pro, POCO F6 Pro, Redmi K60 Pro, POCO X4 GT / Redmi Note 11T Pro (added after launch), Redmi Note 8 / 8T, Redmi Note 9, Redmi Note 10S, Redmi 9 and Redmi 12C.

Is LineageOS 24 Android 17?

Yes. LineageOS 24.0 is based on Android 17 and was released on October 11, 2026.

Does LineageOS 24 include Google Play?

No. Install MindTheGapps for Android 17 right after flashing the ROM, before the first boot. If you boot first, you’ll need a factory reset to add it. Other options are compared in our GApps for Android 17 guide.

Can I install LineageOS without unlocking the bootloader?

No. An unlocked bootloader is required, and unlocking erases all data on Xiaomi phones.

My Xiaomi phone isn’t on the list. Will it get LineageOS 24?

Only if a maintainer brings it to the official build roster. Check the LineageOS wiki from time to time, or look for unofficial builds and crDroid on XDA and 4PDA.

Sources: LineageOS Changelog 32 (Nolen Johnson); LineageOS wiki install pages for the POCO F5 (marble), POCO F3 (alioth) and Redmi Note 8 (ginkgo), the Google Apps page and the device list, maintained by the device maintainers named there.

The post LineageOS 24 (Android 17) for Xiaomi: All 25 Supported Xiaomi, Redmi and POCO Phones appeared first on Xiaomi Firmware.

Magisk 31.1 download

What’s new in Magisk 31.0 and 31.1

• New app (31.0): the whole interface was rebuilt with Jetpack Compose and Material 3. It has a built-in terminal for module scripts and can patch boot images straight from an OTA download link.
• No more root prompts (31.1): apps no longer show a “Grant / Deny” pop-up when they ask for root. Open Magisk → Superuser and allow the apps you trust before using them. Command-line root for adb shell is set there too.
• App hiding removed (31.1): the “Hide the Magisk app” (repackaging) feature and the stub app are gone, and Magisk no longer reinstalls its app if it’s missing. The developer’s advice: after setting up root permissions and modules, simply uninstall the Magisk app if you want it out of sight. Root keeps working.
• One patching pipeline: raw images, OTA ZIPs and factory images are all patched the same way, with progress and speed shown.
• Android 6 dropped: Android 7.0 is the minimum.

Before you start

• Unlocked bootloader. Rooting is impossible without it, and unlocking erases the phone: how to unlock the bootloader on HyperOS.
• Back up photos and chats. A wrong image means a bootloop (fixable, see below), but a factory reset may be needed.
• Banking and payment apps: with an unlocked bootloader, many of them and Google Wallet fail the Play Integrity check, root or not. Plan for that.
• PC with Fastboot: ADB, Fastboot and Xiaomi USB drivers.

How to root HyperOS with Magisk 31.1

1. Find your exact build. Settings → About phone → HyperOS version, for example OS3.0.303.0.WOJMIXM. The image you patch must come from this exact build, region included.
2. Download the matching Fastboot ROM (.tgz) from your phone’s page in our firmware hub. If your build isn’t there yet, check the version decoder to make sure you pick the right region.
3. Extract the image. Open the .tgz with 7-Zip and go to the images folder. If you see init_boot.img, use that one: most phones that launched with Android 13 or later (Xiaomi 13 series and newer) keep the ramdisk there, but not all of them, so go by what’s in the folder. If there is no init_boot.img, use boot.img. After installing Magisk, also check the Ramdisk line on its home screen: if it says Yes, patch the image that holds the ramdisk (a few devices keep it in vendor_boot.img); if it says No, see “Magisk in Recovery” in the official docs. The docs note that some Xiaomi phones report No but still boot a patched boot image. Shortcut: Magisk 31 can also patch a Recovery ROM .zip or its payload.bin directly, without extracting the image first.
4. Patch it. Install Magisk-v31.1.apk on the phone, copy the image to the phone, then in Magisk tap Install → Patch firmware / image → Select from storage and pick the image. The result is saved as Download/magisk_patched-31100_xxxxx.img. Patch the image yourself, on this phone: never flash a patched image someone else shared, and never patch an image that was already patched. Always start from the untouched image of the build you run, and keep that stock image on your PC.
5. Copy the patched file to the PC (for example adb pull /sdcard/Download/magisk_patched-31100_xxxxx.img) and reboot the phone to Fastboot (power off, then hold Power + Volume Down).
6. Flash it:
   fastboot flash init_boot magisk_patched-31100_xxxxx.img
   (or fastboot flash boot magisk_patched-31100_xxxxx.img if you patched boot.img), then fastboot reboot.
7. Finish in the app. If the Magisk app is missing after the reboot, install the APK again first. Open Magisk; if it asks for additional setup, let it reboot once. Then open the Superuser tab and allow root for the apps that need it.

Many Xiaomi phones have A/B slots. fastboot flash init_boot … writes the active slot, as in the Magisk docs. Some 4PDA guides (for example for the POCO X7 Pro) use fastboot flash init_boot_ab …, which writes both slots. Both work; keep the stock init_boot.img on your PC for recovery.

Updating HyperOS on a rooted phone

A system update replaces your patched image, so root is lost after every update unless you re-patch:

• Simple way (works on all models): an incremental OTA usually fails on a rooted phone, so first open Magisk → Uninstall → Restore images (this restores the backup Magisk made when it was installed; don’t reboot), or install the full Recovery ROM of the new build instead. Then install the update, download the Fastboot ROM of the new build, extract its init_boot.img or boot.img, patch it again in Magisk and flash it as above.
• Magisk’s official A/B method: turn off Automatic system updates in Developer options. When an update arrives, open Magisk → Uninstall → Restore Images (don’t reboot), install the update and don’t tap Restart, then Magisk → Install → Install to Inactive Slot (After OTA), and restart. The 4PDA Magisk FAQ recommends the same. The Magisk docs say this is only tested on Pixel phones, and KernelSU-based root users have reported bootloops with the same shortcut on a Xiaomi 15 and a Xiaomi 15 Pro. If it fails on your phone, use the simple way above, and keep the new build’s stock init_boot.img ready: flashing it from Fastboot fixes the bootloop.
• Major updates such as HyperOS 3 → HyperOS 4 (Android 17): read how to install HyperOS 4 manually first, and keep the Fastboot ROM of your current build at hand to go back.

Problems and fixes

How to unroot

In Magisk tap Uninstall → Complete Uninstall, or flash the stock init_boot.img/boot.img of your build with Fastboot. To return to a completely stock phone, flash the full Fastboot ROM with Mi Flash using Clean all (not “Clean all and lock” unless the ROM matches your region and nothing is modified).

Magisk alternatives

KernelSU, KernelSU Next and APatch root the phone at kernel level (full comparison: KernelSU vs APatch vs Magisk on Xiaomi) and are popular on newer Xiaomi devices; APatch added support for the HyperOS 4 kernel in October 2026. They work differently from Magisk and need their own patched images, so pick one method and don’t mix them.

FAQ

Can I root a Xiaomi phone without unlocking the bootloader?

No. Every working root method for HyperOS needs an unlocked bootloader. Apps that promise one-click root without unlocking don’t work on modern Xiaomi phones.

Should I patch init_boot.img or boot.img?

Use init_boot.img if the images folder of your Fastboot ROM has it (phones launched with Android 13 or later). Otherwise use boot.img. If unsure, check the Ramdisk line in the Magisk app.

Why don’t I get a root pop-up anymore?

Magisk 31.1 removed interactive root prompts. Grant root to each app in advance in the Superuser tab of the Magisk app.

Can I uninstall the Magisk app and keep root?

Yes, since 31.1. Root and modules keep working; reinstall the app when you need to change settings or update Magisk.

Where do I get init_boot.img for my Xiaomi phone?

From the official Fastboot ROM of your exact build: open your phone on our firmware page, download the Fastboot ROM and extract images/init_boot.img.

Sources: Magisk documentation by topjohnwu (Installation, OTA upgrade guide) and v31.1 release notes; 4PDA Magisk FAQ (install and remove, Kokaino2033, keeping root after OTA, Displax); POCO X7 Pro firmware thread (init_boot root guide by IZZY_RU87 and toreton, payload.bin patching by Dead master).

The post Magisk 31.1 for Xiaomi: How to Root HyperOS 3 and HyperOS 4 (init_boot, 2026) appeared first on Xiaomi Firmware.

Xiaomi ADB/Fastboot Tools 7.0.3 download

Download: XiaomiADBFastbootTools.jar 7.0.3 (GitHub mirror) · second GitHub mirror. The official repository no longer exists, so these are community re-uploads. We compared the copies from three different mirrors: they are byte-identical, report version 7.0.3 and have the original build date. Check the SHA-256 above after downloading (Windows: certutil -hashfile XiaomiADBFastbootTools.jar SHA256).

Avoid sites that offer an “.exe” or “installer” for version 7: the real tool is only a .jar. The old Windows .exe builds were version 2.x from 2018.

What the tool does

• App Manager: uninstall, reinstall, disable or enable preinstalled Xiaomi and Google apps (debloater).
• Screen density and resolution changer, device properties viewer and a simple file explorer.
• Fastboot tools: flash a partition image, boot image or a full Fastboot ROM, wipe partitions, reboot to recovery, fastboot or EDL.
• Camera2 / EIS enabler (needs TWRP, not needed on modern phones) and a ROM downloader for old MIUI.

The App Manager and the screen tools work with a locked bootloader. Flashing, wiping and Camera2 need an unlocked bootloader.

How to run it

1. Install Java 11 or newer, for example Eclipse Temurin 21.
2. On the phone: Settings → About phone, tap OS version 7 times, then turn on USB debugging in Additional settings → Developer options. Also turn on USB debugging (Security settings); Xiaomi needs it for changing system settings and some app actions.
3. Connect the phone and allow the computer. On Windows, install the ADB and Xiaomi USB drivers if it isn’t detected.
4. Double-click the .jar. If nothing happens, open a terminal in the folder and run java -jar XiaomiADBFastbootTools.jar. On first start the tool downloads Google’s ADB and Fastboot by itself.

Does it work on HyperOS?

Partly. Owners report that on HyperOS 1 and 2 the tool still connects, reads the device and can uninstall many apps. Three things don’t work well anymore:

• Old app list. The tool used to download its list of removable apps from the developer’s GitHub. That page is gone, so it falls back to the built-in list from 2020 (131 apps). Most HyperOS-era apps aren’t on it; you have to add package names by hand.
• Disabling fails. On HyperOS, disabling some system apps from the computer is blocked. You’ll see Failure [ADB error], Shell cannot change component state or Cannot disable system packages. Uninstalling the same app (for your user only) often works.
• No updates. The tool was never updated for HyperOS 3 or 4, and we found no reports of it working on those versions.

Common errors and fixes

Better alternatives for HyperOS 3 and 4

Shizuku on HyperOS 4: the official Shizuku app (13.6.0) doesn’t work properly on Android 17, which HyperOS 4 is based on: apps don’t get access. Until RikkaApps updates it, owners use the community build Shizuku 13.7.0 by thedjchi, which adds Android 17 support.

Which apps are safe to remove on HyperOS, with commands: debloat HyperOS without root via ADB.

For the other modules you don’t need a separate tool: change screen density with adb shell wm density, read device info with adb shell getprop, and flash or wipe with Google’s Fastboot (platform-tools) or Mi Flash. Bootloader unlocking is done with Mi Unlock.

There is also a small 2026 community rebuild, xiaomi-adb-tools, that lists all installed apps and bundles its own Java, including for Apple Silicon. It’s a hobby project with few users, so test it carefully.

Version history

The project was archived in 2022 with a note that it was outdated and that some functions no longer worked on recent devices. The repository was deleted in spring 2023.

FAQ

Is Xiaomi ADB/Fastboot Tools safe?

The tool itself is open source (MIT) and only sends standard ADB and Fastboot commands. The risk is in what you remove: uninstalling core apps such as Security or the launcher can cause a bootloop. Download only the .jar and check its SHA-256.

Is there a newer version than 7.0.3?

No. 7.0.3 is the final release by Szaki. Anything labelled 7.1 or 8.0 is not from the original developer.

Does it need root or an unlocked bootloader?

No for the debloater and screen tools; they use ADB with USB debugging. Yes for flashing partitions, wiping and the Camera2 enabler.

What should I use instead on HyperOS 4?

UAD-ng 1.3.1 on a computer, or Canta with the Android 17-compatible Shizuku build on the phone.

The post Xiaomi ADB/Fastboot Tools 7.0.3 Download (Discontinued): HyperOS Status and Best Alternatives appeared first on Xiaomi Firmware.