Redmi K90 (Annibale) Fastboot & Recovery Flash File (Stock ROM)

Redmi K90 Annibale Qualcomm SM8750-AB Snapdragon 8 Elite Fastboot Recovery Flash File Stock ROM Download

Redmi K90 users commonly run into issues like Region/Account Mismatch Unlock Issues, especially when dealing with Icon Pack Application Incompatibility on Default Launcher. The stock ROM below is a direct fix for this. This build is made specifically for the Qualcomm SM8750-AB Snapdragon 8 Elite chipset, so confirm your exact model number (e.g. 2510DRK44C, 2510DPC44G) before downloading.

If your Redmi K90 (codename: annibale) is stuck on the Mi logo, stuck in a bootloop, showing a dead boot screen, or you flashed a custom ROM and now want to get back to MIUI/HyperOS, you're in the right place. Below you'll find every available fastboot and recovery firmware version for this device, along with working download servers and a flashing walkthrough that doesn't skip steps.

Before you pick a file: fastboot flashing means a full reset, so use it when the phone is genuinely stuck or dead. If you're just trying to repair the system without losing data, go with the recovery ROM instead.

Device Overview

BrandXiaomi
DeviceRedmi K90
Model Number2510DRK44C, 2510DPC44G
Codenameannibale
ChipsetQualcomm SM8750-AB Snapdragon 8 Elite
OS VersionHyperOS 3 / Android 16
Storage Variants256GB / 512GB
RAM Variants12GB
Approx. Total Size13.3 GB
Recommended ToolMi Flash Tool

Fastboot vs Recovery ROM — Which One Do You Need?

People often download the wrong file the first time, so here's the short version. A fastboot ROM is a complete firmware package meant to be flashed through Mi Flash Tool on a PC — it wipes the device and reinstalls everything from scratch, which makes it the go-to fix for bootloops, dead boot, or a phone that refuses to start. A recovery ROM, on the other hand, is flashed through the phone's built-in Mi Recovery menu and is generally used to update, downgrade, or repair the system without touching your personal data (though a backup is still recommended).

🔹 Fastboot ROM

annibale_images_OS4.0.6.0.XPKCNXM_20261026.0000.00_17.0_cn
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleFastboot ROMOS4.0.6.0.XPKCNXM1712.4 GB2026-10-26
annibale_images_OS4.0.5.0.XPKCNXM_20261021.0000.00_17.0_cn
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleFastboot ROMOS4.0.5.0.XPKCNXM1713.3 GB2026-10-21
annibale_images_OS3.0.307.0.WPKCNXM_20260723.0000.00_16.0_cn
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleFastboot ROMOS3.0.307.0.WPKCNXM1612.8 GB2026-07-23
annibale_images_OS3.0.305.0.WPKCNXM_20260601.0000.00_16.0_cn
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleFastboot ROMOS3.0.305.0.WPKCNXM1612.9 GB2026-06-01
annibale_images_OS3.0.304.0.WPKCNXM_20260407.0000.00_16.0_cn
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleFastboot ROMOS3.0.304.0.WPKCNXM1612.8 GB2026-04-07
annibale_images_OS3.0.303.0.WPKCNXM_20260307.0000.00_16.0_cn
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleFastboot ROMOS3.0.303.0.WPKCNXM1612.7 GB2026-03-07
annibale_images_OS3.0.24.0.WPKCNXM_20260127.0000.00_16.0_cn
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleFastboot ROMOS3.0.24.0.WPKCNXM1612.3 GB2026-01-27
annibale_images_OS3.0.20.0.WPKCNXM_20251224.0000.00_16.0_cn
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleFastboot ROMOS3.0.20.0.WPKCNXM1612.2 GB2025-12-24
annibale_images_OS3.0.18.0.WPKCNXM_20251211.0000.00_16.0_cn
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleFastboot ROMOS3.0.18.0.WPKCNXM1612.3 GB2025-12-11
annibale_images_OS3.0.13.0.WPKCNXM_20251107.0000.00_16.0_cn
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleFastboot ROMOS3.0.13.0.WPKCNXM1612.2 GB2025-11-07
annibale_images_OS3.0.9.0.WPKCNXM_20251021.0000.00_16.0_cn
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleFastboot ROMOS3.0.9.0.WPKCNXM1612.2 GB2025-10-21

🔹 Recovery ROM

annibale-ota_full-OS4.0.6.0.XPKCNXM-user-17.0-0207c91df5
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleRecovery ROMOS4.0.6.0.XPKCNXM179.4 GB2026-11-03
annibale-ota_full-OS4.0.5.0.XPKCNXM-user-17.0-ba0c9eabdc
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleRecovery ROMOS4.0.5.0.XPKCNXM1710.1 GB2026-10-23
annibale-ota_full-OS4.0.0.22.XPKCNXM-user-17.0-5a1605b9c0
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleRecovery ROMOS4.0.0.22.XPKCNXM179.4 GB2026-08-20
annibale-ota_full-OS4.0.0.18.XPKCNXM-user-17.0-600712d62b
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleRecovery ROMOS4.0.0.18.XPKCNXM179.3 GB2026-08-14
annibale-ota_full-OS3.0.307.0.WPKCNXM-user-16.0-94dcf5f934
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleRecovery ROMOS3.0.307.0.WPKCNXM169.7 GB2026-07-30
annibale-ota_full-OS3.0.305.3.WPKCNXM-user-16.0-132048d7f5
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleRecovery ROMOS3.0.305.3.WPKCNXM169.1 GB2026-06-12
annibale-ota_full-OS3.0.305.0.WPKCNXM-user-16.0-e88370d5bc
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleRecovery ROMOS3.0.305.0.WPKCNXM169.7 GB2026-06-05
annibale-ota_full-OS3.0.304.0.WPKCNXM-user-16.0-a582a51eb5
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleRecovery ROMOS3.0.304.0.WPKCNXM169.7 GB2026-05-16
annibale-ota_full-OS3.0.303.0.WPKCNXM-user-16.0-33073f2249
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleRecovery ROMOS3.0.303.0.WPKCNXM169.7 GB2026-03-11
annibale-ota_full-OS3.0.24.0.WPKCNXM-user-16.0-f967acd36f
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleRecovery ROMOS3.0.24.0.WPKCNXM169.0 GB2026-01-31
annibale-ota_full-OS3.0.20.0.WPKCNXM-user-16.0-42b109f0f1
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleRecovery ROMOS3.0.20.0.WPKCNXM168.9 GB2025-12-28
annibale-ota_full-OS3.0.18.0.WPKCNXM-user-16.0-d8932cf81a
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleRecovery ROMOS3.0.18.0.WPKCNXM169.6 GB2025-12-16
annibale-ota_full-OS3.0.13.0.WPKCNXM-user-16.0-f28d23c6a2
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleRecovery ROMOS3.0.13.0.WPKCNXM169.4 GB2025-11-10
annibale-ota_full-OS3.0.9.0.WPKCNXM-user-16.0-e06570ff2d
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleRecovery ROMOS3.0.9.0.WPKCNXM169.4 GB2025-10-23
annibale-ota_full-OS3.0.4.0.WPKCNXM-user-16.0-eff83315c8
Device NameCodenameTypeMIUI VersionAndroid OSSizeDate
Redmi K90annibaleRecovery ROMOS3.0.4.0.WPKCNXM169.4 GB2025-10-23
Got multiple parts to download? Save them all in the same folder first. The archive will fail to extract if any single part is missing.

Tools You'll Need

Get the flashing tool and the right USB driver set up on your PC before you start — in most cases, a failed flash has more to do with a missing driver than with the firmware file.

How to Flash Redmi K90 Using Mi Flash Tool

  1. Download the fastboot ROM and extract it fully — don't skip extraction, Mi Flash Tool won't read a zipped folder.
  2. Install Mi Flash Tool from the link above and open it.
  3. Power off the phone, then hold Volume Down + Power together to boot into Fastboot mode.
  4. Connect the phone to your PC using a good-quality USB cable — cheap cables are a common cause of connection drops mid-flash.
  5. In Mi Flash Tool, click "Select" and point it to the extracted firmware folder.
  6. Once the COM port is detected, hit "Flash" and let it run — don't disconnect the phone during this step.
  7. The phone will reboot on its own once flashing finishes. First boot can take a few minutes longer than usual, so give it time.

Common Flashing Errors and How to Fix Them

"Auth file needed" — this usually shows up when the connected Mi account isn't authorized for flashing. You'll need an authorized account, or a test-point based flash for unlocked devices.

"COM port not detected" — almost always a driver issue. Install the Qualcomm/MediaTek USB driver from the link above, then put the phone back into EDL or Fastboot mode and try again.

"Flashing failed" partway through — try a different USB cable or port first; if that doesn't help, re-extract the firmware in case a file got corrupted during download.

Frequently Asked Questions

Is this firmware official?
Yes, these are unmodified stock builds pulled directly from Xiaomi's own update servers.

Will flashing delete my data?
Fastboot flashing wipes the device, so back up anything important first. Recovery flashing is less destructive but a backup is still a good idea.

My model number doesn't match exactly — can I still use this?
Make sure the codename matches annibale exactly, as listed above. Using firmware meant for a different variant or region can brick the device.

How to Unlock Bootloader on Redmi K90

Before you start: Unlocking erases all data on the phone and lowers its security. Back up first.

Steps:

  1. Log in to your Mi account on the phone.
  2. Enable Developer options: Settings → About phone → tap OS/MIUI version 7 times.
    Bind your account: Settings → Additional settings → Developer options → Mi Unlock status → Add account and device. This needs a SIM card and mobile data turned on.
  3. Download the Mi Unlock tool on your PC and sign in with the same Mi account.
  4. Enter Fastboot mode: power off the phone, then hold Power + Volume Down.
  5. Connect the phone to the PC by USB and click Unlock in the tool.

Good to know:

  • Xiaomi usually enforces a waiting period (often 72 to 168 hours). The tool will tell you how long, and the account must stay bound to the phone during that time.
  • Newer HyperOS versions have stricter unlock rules in some regions, so check Xiaomi's official unlock page for your region.
  • After unlocking, some banking or payment apps may stop working, and Widevine L1 (HD streaming) may be lost.
  • Don't flash any custom ROM or tool on a phone until you've found a confirmed guide for that exact model on XDA or the Xiaomi community.

If you hit an error like "Couldn't verify device" or a waiting-time message, let us know in the comments and we'll help.

Post a Comment

0 Comments