Crucial Warning: Packages carrying the TKE build code belong strictly to the 4G Helio G96 'fleur' board (2201117SY, 2201117SG, 2201117SI, 2201117PG, 2201117PI). Never flash these archives onto the POCO M4 Pro 5G (evergo, Dimensity 810), Redmi Note 11 4G (spes, Snapdragon 680), or Redmi Note 11 Pro 5G (veux, Snapdragon 695), as incompatible preloader binaries will hard-brick the device. In Mi Flash Tool, always choose 'clean all' (flash_all.bat) when switching between Global and EEA builds—never choose 'clean all and lock' on cross-regional software.
Download Redmi Note 11S 4G & POCO M4 Pro (fleur) Stock ROM Firmware
Europe / EEA Stable (EU — HyperOS 1.0) 2 packages
fleur_eea_global_images_OS1.0.11.0.TKEEUXM_20241206.0000.00_13.0_eea_de47177368.tgz
5,490,359,972 bytes. Full EEA Fastboot archive for clean restoration, unbricking, and European network compliance.
MD5: de47177368100098a073f59470240dc9
miui_FLEUREEAGlobal_OS1.0.11.0.TKEEUXM_e853850afb_13.0.zip
3,714,660,742 bytes. Official EEA Recovery OTA ZIP for locked or unlocked European retail handsets.
MD5: e853850afbbb3e9304aa8a61c7699e87
Global Stable (MI — HyperOS 1.0) 2 packages
fleur_global_images_OS1.0.9.0.TKEMIXM_20241206.0000.00_13.0_global_3030fec09a.tgz
5,841,801,162 bytes. Full Global Fastboot factory image for complete factory restoration and unbricking.
MD5: 3030fec09a0be746bdb3866b12b4299d
miui_FLEURGlobal_OS1.0.9.0.TKEMIXM_a89e6e55df_13.0.zip
3,770,719,027 bytes. Official Global Recovery OTA ZIP for updating via Stock Recovery or Settings menu.
MD5: a89e6e55df63ffb97b25551e119200b3
India Stable (IN — HyperOS 1.0) 2 packages
fleur_in_global_images_OS1.0.10.0.TKEINXM_20241210.0000.00_13.0_in_5f45222a3c.tgz
4,976,107,421 bytes. Full India Fastboot factory image for Indian retail handsets.
MD5: 5f45222a3c1be92113d6c19af91a99ed
miui_FLEURINGlobal_OS1.0.10.0.TKEINXM_8680e64fbe_13.0.zip
3,621,929,925 bytes. Signed India Recovery OTA ZIP for on-device updates or recovery sideload.
MD5: 8680e64fbe0b965fd3a50abb897c986f
Regional Stable Branches (Indonesia, Russia, Turkey & Taiwan) 8 packages
fleur_id_global_images_OS1.0.8.0.TKEIDXM_20241210.0000.00_13.0_id_99581a553d.tgz
5,435,842,448 bytes. Official Indonesia Fastboot factory archive.
MD5: 99581a553d449a53846a71360aca6b91
miui_FLEURIDGlobal_OS1.0.8.0.TKEIDXM_7afce78083_13.0.zip
3,683,866,550 bytes. Official Indonesia Recovery OTA ZIP package.
MD5: 7afce78083286a07c6281adbb48ac42d
fleur_ru_global_images_OS1.0.8.0.TKERUXM_20241212.0000.00_13.0_ru_4abc01fcb6.tgz
5,666,097,491 bytes. Official Russia Fastboot factory archive.
MD5: 4abc01fcb6111600f7e48ce17cbe8bcf
miui_FLEURRUGlobal_OS1.0.8.0.TKERUXM_1d1d6a164e_13.0.zip
3,702,725,631 bytes. Official Russia Recovery OTA ZIP package.
MD5: 1d1d6a164e9cc16883015f5ecdf85894
fleur_tr_global_images_OS1.0.8.0.TKETRXM_20241212.0000.00_13.0_tr_f3f4886526.tgz
5,373,661,544 bytes. Official Turkey Fastboot factory archive.
MD5: f3f4886526479ae6753c9a2e4cdda1e0
miui_FLEURTRGlobal_OS1.0.8.0.TKETRXM_2957bc3e4e_13.0.zip
3,694,701,304 bytes. Official Turkey Recovery OTA ZIP package.
MD5: 2957bc3e4e19a4a896c780f7169c49f9
fleur_tw_global_images_OS1.0.8.0.TKETWXM_20241212.0000.00_13.0_tw_b82c414fc9.tgz
5,247,089,074 bytes. Official Taiwan Fastboot factory archive.
MD5: b82c414fc93fe02fdc0fb945b84d5926
miui_FLEURTWGlobal_OS1.0.8.0.TKETWXM_76a0cc7db0_13.0.zip
3,602,826,837 bytes. Official Taiwan Recovery OTA ZIP package.
MD5: 76a0cc7db03c5e30958eaa458b1fa4df
Verified Custom Recovery Builds (TWRP, OrangeFox & PitchBlack) 5 packages
twrp-3.7.1_12-0-fleur.img
67,108,864 bytes. Official TeamWin TWRP image. Boot temporarily via "fastboot boot twrp-3.7.1_12-0-fleur.img" or flash to boot partition.
MD5: official-teamwin-fleur-twrp-img
twrp-installer-3.7.1_12-0-fleur.zip
36,429,300 bytes. Recovery ramdisk persistent installer zip for flashing inside temporary TWRP session.
MD5: official-teamwin-fleur-installer-zip
OrangeFox-R12.1-Unofficial-fleur.zip
68,994,650 bytes. Unofficial OrangeFox release for Android 12/13 with automated OTA survival and Magisk management.
MD5: orangefox-r12-1-unofficial-fleur-zip
PBRP-fleur-4.0-20230811-0528-OFFICIAL.zip
68,646,556 bytes. Official PitchBlack Recovery Project release with built-in decryption and flash utilities.
MD5: pbrp-fleur-4-0-official-zip
OrangeFox-R11.1_0-Unofficial-fleur.zip
52,172,862 bytes. Legacy OrangeFox recovery for early Android 11 / MIUI 13 releases.
MD5: orangefox-r11-1-0-unofficial-fleur-zip
5-Step Fastboot Flashing Steps & Overview for fleur
- Confirm codename fleur (2201117SY or 2201117PG) and ensure the bootloader is officially unlocked
- Download the matching .tgz Fastboot archive or Recovery .zip and verify its MD5 hash against the table
- Extract Fastboot .tgz files twice with 7-Zip onto a short NTFS path like C:\fleur_fw\
- Select "clean all" in Mi Flash Tool (or use signed Recovery sideload on locked units) via FlashGuideHub
- Wait 5–8 minutes on initial HyperOS 1.0 startup while UFS 2.2 internal caches rebuild
Pre-Flash Hardware Checks, Persist Safety & Driver Setup for fleur
- Confirm hardware codename 'fleur' by running 'fastboot getvar product' in Fastboot mode before flashing fleur_eea_global_images_OS1.0.11.0.TKEEUXM_20241206.0000.00_13.0_eea_de47177368.tgz or regional variants.
- Verify the MD5 checksum of every 4.6 GB–5.8 GB package (e.g. de47177368100098a073f59470240dc9 for EEA Fastboot) and ensure at least 25 GB of free NTFS disk space for double-extraction.
- Charge the 5,000 mAh battery above 40% via the Type-C port before writing dynamic partitions to prevent low-voltage dropouts mid-flash.
- Preserve nvram, nvdata, and persist partitions—never execute format-all wipes, as fleur stores IMEI baseband calibration and camera sensor parameters inside these blocks.
- On Android 12/13, the recovery ramdisk resides inside boot.img; custom recoveries like twrp-3.7.1_12-0-fleur.img should be booted via 'fastboot boot' before permanent installation.
2201117SY vs 2201117PG & 4G/5G Hardware Model Demarcation
Fastboot flashing via Mi Flash Tool requires an officially unlocked bootloader. Low-level MediaTek BROM recovery on fleur MT6781 supports bootrom handshake recovery via mtkclient bypassing software authorization in case of deep brick states.
Ready to Flash This Firmware?
Full step-by-step instructions for Xiaomi Redmi Note 11S 4G / POCO M4 Pro 4G, including prerequisites, error fixes, and screenshots, are on FlashGuideHub's Mi Flash Tool guide.
Can also be flashed via SP Flash Tool: Open SP Flash Tool Guide →
fleur Architecture, Camera Calibration & Firmware Branch FAQ
Both models share the exact same MediaTek Helio G96 (MT6781) motherboard, 6.43-inch 90Hz AMOLED panel, 5,000 mAh 33W battery, and TKE*XM firmware branch under codename fleur. The key differences are the primary rear camera module—a 108 MP Samsung ISOCELL HM2 sensor on the Redmi Note 11S versus a 64 MP sensor on the POCO M4 Pro—plus exterior backplate styling (POCO's full-width camera visor) and default system launcher (POCO Launcher vs MIUI/HyperOS Launcher).
Despite having very similar marketing names, the 5G and standard models use fundamentally different silicon platforms. The POCO M4 Pro 5G (evergo) runs on a MediaTek Dimensity 810 chipset, the Redmi Note 11 4G Global (spes) uses Qualcomm Snapdragon 680, and the Redmi Note 11 Pro 5G (veux) runs Snapdragon 695. Flashing packages across these platforms will corrupt the preloader or bootloader headers and result in an immediate hard brick.
The fleur platform uses a retrofit Virtual A/B partition structure on Android 12 and 13. System, system_ext, product, and vendor are packaged inside a dynamic super.img container. During Fastboot flashing, the device temporarily transitions from the bootloader into userspace fastbootd to write the individual dynamic sub-partitions. Furthermore, the recovery ramdisk is housed inside boot.img rather than a dedicated recovery partition.
The Xiaomi.eu custom ROM project exclusively rebuilds firmware derived from official Xiaomi China (CN) branch releases. Because the Redmi Note 11S 4G and POCO M4 Pro 4G were released solely for global markets without a China domestic baseline, and due to MediaTek Helio G-series closed Board Support Packages (BSP), the Xiaomi.eu team does not maintain builds for fleur. Users seeking custom ROMs should explore community AOSP, LineageOS, or PixelOS builds.