Crucial Warning: When flashing Fastboot packages via Mi Flash Tool, always select "clean all" (flash_all.bat). Never select "clean all and lock" (flash_all_lock.bat) on imported hardware running cross-region or custom software, as relocking foreign signatures causes an irrecoverable brick. Do not confuse the 4G Redmi K30 (phoenix, Snapdragon 730G) with the 5G Redmi K30 (picasso, Snapdragon 765G), as motherboard layouts share zero compatibility.
Official Xiaomi Redmi K30 & POCO X2 Firmware & Recovery Downloads
India — POCO X2 (phoenixin) Official MIUI Stock Firmware 3 packages
phoenixin_in_global_images_V12.5.6.0.RGHINXM_20211123.0000.00_11.0_in_794e6c1d4f.tgz
Official Indian Fastboot factory package with Google Mobile Services for clean unbricking and restoration.
MD5: 794e6c1d4f748c61c74ac9ec7945e53e
miui_PHOENIXININGlobal_V12.5.6.0.RGHINXM_9ab5819b56_11.0.zip
Official Recovery OTA update package for standard system updater or stock recovery installation.
MD5: 9ab5819b56dc6c5c059174032b608c7e
miui_PHOENIXININGlobal_V12.5.7.0.RGHINXM_256a3b1761_11.0.zip
Final maintenance stable beta recovery update released for Indian POCO X2 handsets.
MD5: 256a3b17618f039bfd808a347713ccbb
China — Redmi K30 4G (phoenix) Official MIUI Stock Firmware 2 packages
phoenix_images_V13.0.6.0.SGHCNXM_20220928.0000.00_12.0_cn_edf8a2c9f6.tgz
Official Chinese Fastboot factory package marking the final stable Android 12 update for Redmi K30 4G.
MD5: edf8a2c9f63046c2a32c0028b57f0f61
miui_PHOENIX_V13.0.6.0.SGHCNXM_0b193f263c_12.0.zip
Official Chinese recovery update package for MIUI 13 based on Android 12.
MD5: 0b193f263c63db3eeb48809ba8c2d705
Community Custom ROMs & Recovery Toolkits (Xiaomi.eu, TWRP, OrangeFox) 3 packages
xiaomi.eu_multi_HMK30_V13.0.6.0.SGHCNXM_v13-12.zip
Community multilingual custom ROM with integrated Google Mobile Services, debloated system apps, and European localization.
⬇️ Download via MIUI OTAtwrp-3.7.1_12-0-phoenix.img
Official TWRP custom recovery image maintained by Himanshu Raj with support for dynamic partitions and Android 12 decryption.
⬇️ Download via Direct Link[email protected]_2.zip
Official OrangeFox recovery build for phoenix/phoenixin with built-in Magisk survival and FBE encryption management.
⬇️ Download via Direct LinkMi Flash & Fastboot Restoration Milestones
- Download and extract official Fastboot TGZ archive with 7-Zip to a root directory like C:\phoenix_fw
- Reboot device to Fastboot mode by pressing and holding Volume Down and Power together
- Connect to PC USB 2.0 port and verify connection with the command "fastboot devices"
- Open Xiaomi Mi Flash Tool, select the unzipped directory, and select "clean all" at the bottom right
- Click Flash to write partition images and allow 5 to 7 minutes for the initial MIUI first boot
Hardware Triage, Anti-Rollback & Board Verification
- 1. Verify your handset codename by booting to Fastboot mode and typing "fastboot getvar product" in Command Prompt (reports "phoenix" for Redmi K30 4G or "phoenixin" for POCO X2).
- 2. Extract your chosen Fastboot archive (such as phoenixin_in_global_images_V12.5.6.0.RGHINXM_20211123.0000.00_11.0_in_794e6c1d4f.tgz) twice using 7-Zip into a clean root directory like C:phoenix_fw to prevent command line path truncation.
- 3. Check anti-rollback status before attempting any firmware downgrade by typing "fastboot getvar anti" to confirm your board index allows the target build.
- 4. Ensure your 4500 mAh battery has at least 50% charge to prevent power failure during dynamic super partition writes.
- 5. In severe brick cases where Fastboot mode is inaccessible, Qualcomm HS-USB QDLoader 9008 EDL test points are situated beside the battery connector beneath the rear glass cover.
Qualcomm Snapdragon 730G Architecture & Sibling Demarcation
Official Fastboot flashing requires an unlocked bootloader via the official Xiaomi Mi Unlock tool. Qualcomm Emergency Download (EDL 9008) mode requires authorized Xiaomi service credentials.
Ready to Flash This Firmware?
Full step-by-step instructions for Xiaomi Redmi K30 4G / POCO X2, including prerequisites, error fixes, and screenshots, are on FlashGuideHub's Mi Flash Tool guide.
Can also be flashed via Fastboot: Open Fastboot Guide →
Technical & Archival Questions About the "phoenix" Platform
Xiaomi branched software development schedules based on regional maintenance cycles. The Chinese Redmi K30 4G (phoenix) received an upgrade to Android 12 with MIUI 13 (build V13.0.6.0.SGHCNXM) before official end-of-support in late 2022. In contrast, the Indian POCO X2 (phoenixin) concluded official public updates on Android 11 with MIUI 12.5 Enhanced (build V12.5.6.0.RGHINXM, alongside a limited V12.5.7.0 stable beta), as Xiaomi prioritized subsequent X-series hardware in the Indian market.
Flashing raw Chinese Fastboot packages onto a POCO X2 via Mi Flash Tool will fail during partition script execution because the updater script and partition tables check the hardware product identifier. While both phones share the same Qualcomm Snapdragon 730G motherboard design, forcing phoenix images onto phoenixin without modifying board assertions can cause baseband modem mismatches or bootloops. Users wanting MIUI 13 on POCO X2 generally install unified custom ROMs or Xiaomi.eu builds that account for both codenames.
The Chinese Redmi K30 4G includes an integrated NXP PN553 NFC controller and antenna array on the back housing for transit cards and mobile payments. In contrast, the Indian POCO X2 was cost-optimized for the Indian market and physically omits the NFC silicon and antenna from the motherboard PCB. No firmware or software modification can enable NFC functionality on a POCO X2 because the underlying controller is absent.
The Qualcomm Snapdragon 730G platform on the POCO X2 experienced documented thermal cycling stress, leading to solder fatigue beneath the CPU and PMIC on heavily used units. If the device is in a software bootloop, it will reliably enter Fastboot mode via physical button combinations and maintain a stable connection with "fastboot devices". In contrast, hardware solder joint failure typically causes sudden total power-off ("dead boot"), device disconnection during heavy USB write operations, or permanent rear camera freeze errors that persist even after a complete factory Fastboot reflash. Hardware solder failures cannot be resolved with firmware and require motherboard-level CPU reballing.