# Hyper ROM Firmware Library · Full corpus > Plain-text export of every guide and site document on this site, for whole-document retrieval and citation. Firmware listings are data pages: fetch them through the JSON endpoints or sitemaps listed in /llms.txt. Site: https://rom.123wen.cn/ Data source: https://github.com/HegeKen/HyperData (CC BY 4.0) Exported: 2026-11-22T08:34:44+08:00 ## Appendix: Firmware guides # How to Flash HyperOS on Xiaomi Phones with Fastboot (2026 Guide) URL: https://rom.123wen.cn/en/guide/how-to-flash/ Last updated: Oct 28, 2026 A complete walkthrough of flashing a HyperOS fastboot ROM on Xiaomi, REDMI and POCO phones: download the .tgz package, boot into fastboot, write it with MiFlash, and choose between clean all and clean all and lock. Includes fixes for the most common errors. ## When fastboot flashing is the right choice Fastboot flashing bypasses the phone's Recovery and lets a computer write images directly to the partitions. That makes it the only option when the system cannot boot, and the usual route for downgrades across major versions. - The phone will not boot, hangs on the logo, or reboots in a loop - You need to downgrade from HyperOS 3.0 to 2.0 or 1.0 - The system partition is damaged or an OTA update failed - You want to wipe every trace of user data before selling the device ## Before you start 1. Back up photos, chats and account data. Fastboot flashing wipes all user data by default. 2. Confirm the device codename on the device page (for example earth or gold). A package with a different codename must not be flashed. 3. Download the fastboot package for the correct region. The file name looks like earth_images_OS1.0.8.0.UCVCNXM_20250820.0000.00_14.0_cn_xxxx.tgz. 4. Install the Xiaomi USB driver and MiFlash on the computer, or use the official fastboot tools. 5. Keep the battery above 50% and use the original cable or a known-good one. ## Boot into Fastboot mode Power the phone off, then hold Volume Down and Power for about three seconds until the Mi Bunny robot appears. Connect the USB cable: Windows Device Manager should list an Android Bootloader Interface. ## Flash with MiFlash 1. Open MiFlash and click Select to point at the extracted package folder, which must contain flash_all.bat and the images directory. 2. Click Refresh to confirm the device is detected, then click Flash. 3. Pick clean all in the bottom right. Do not choose clean all and lock unless you specifically want to re-lock the bootloader. 4. Wait for the progress bar to finish. After success the phone reboots and the first boot can take 5 to 15 minutes. ## Package types compared | Package type | Extension | Tool | Wipes data | | --- | --- | --- | --- | | Recovery / OTA package | .zip | System updater or Recovery | Usually not | | Fastboot package | .tgz | MiFlash or fastboot | Yes | | Carrier fastboot package | .tgz | MiFlash or fastboot | Yes | ## Common errors and fixes - error: could not get flash write protect: the bootloader is still locked. Apply for unlocking in the Xiaomi Community app first. - MiFlash does not detect the phone: use a USB 2.0 port, reinstall the Xiaomi driver, or try another cable. - flash crc error: the download is incomplete. Download the package again and check the file name. - The flash succeeds but the phone still will not boot: make sure clean all was selected, and flash once more if needed. --- # Recovery Zip vs Fastboot ROM: Which Xiaomi Package Should You Use? URL: https://rom.123wen.cn/en/guide/recovery-vs-fastboot/ Last updated: Oct 28, 2026 Recovery and fastboot packages differ in file type, flashing tool, bootloader requirements, data retention and risk. This side-by-side comparison explains what each one is for, so you download the right file the first time. ## The difference at a glance | Item | Recovery package | Fastboot package | | --- | --- | --- | | File extension | .zip | .tgz | | Tool | System updater or Recovery | MiFlash or fastboot | | Bootloader unlock | Usually not required for official builds | Required | | User data | Usually kept | Wiped (clean all) | | Best for | Routine updates, minor fixes | Rescues, downgrades, damaged partitions | | Failure risk | Low; the install aborts when verification fails | Higher; an interruption can leave the phone unbootable | ## Installing a recovery package correctly 1. Copy the .zip to the root of the phone storage or to the Download folder. 2. Open Settings, go to About phone and tap the version number repeatedly to enable the manual package picker. 3. Select the matching zip and wait for verification and installation. Do not power off during the process. 4. The first boot afterwards can take longer than usual, which is expected. ## When you must use fastboot - The phone cannot boot and Recovery is unusable - You need to downgrade across major versions, for example HyperOS 3.0 to 2.0 - Recovery installs keep failing with partition verification errors - You want a full wipe to rule out software corruption ## Two common mistakes Renaming a fastboot package and installing it as a recovery zip. The archive layout does not match, so Recovery rejects it immediately. Flashing a package from another region through Recovery. The installer verifies region and version, and a mismatch normally fails verification; forcing a cross-region fastboot package can break calls, NFC and OTA updates. --- # Xiaomi Firmware Regions Explained: CNXM, MIXM, EUXM and More URL: https://rom.123wen.cn/en/guide/region-difference/ Last updated: Oct 28, 2026 The suffix at the end of a Xiaomi build number identifies the sales region. This guide maps CNXM, MIXM, EUXM, INXM, RUXM and the other codes to their markets, explains what actually differs between them, and covers the risks of cross-region flashing. ## Region code reference | Code | Region | Notes | | --- | --- | --- | | CNXM | Mainland China | Chinese-market builds, including carrier variants | | MIXM | Global | Widest coverage, no Chinese carrier customisation | | EUXM | EEA / Europe | EU compliance profile, includes Vodafone and Telefonica variants | | INXM | India | Indian bands and preinstalled services | | IDXM | Indonesia | Indonesian certification and preloads | | RUXM | Russia | Russian preloads and compliance | | TRXM | Turkey | Turkish preinstalled services | | TWXM | Taiwan | Traditional Chinese and local services | | LMXM | Latin America | Multi-country builds with Claro and Movistar variants | | MXMX | Mexico | Includes AT&T and Telcel variants | | CLXM | Chile | Mainly Entel builds | | GTXM | Guatemala | Mainly Tigo builds | | JPXM | Japan | Includes KDDI builds | | ZAXM | South Africa | Includes Vodacom and MTN builds | | THXM | Thailand | Mainly AIS builds | ## What actually differs between regions - Preinstalled apps: services, stores and compliance apps vary by market. - Network configuration: modem and carrier profiles follow local bands and VoLTE policies. - Feature switches: NFC, wallet, call recording and dual-SIM behaviour depend on local regulation. - OTA channel: updates are rolled out per region, so a cross-region flash can leave the device on the wrong channel. ## Risks of cross-region flashing Firmware for the same model usually flashes across regions at the hardware level, but afterwards you may see missing OTA updates, call or SMS problems, an unusable NFC or wallet, missing or broken Google services, and a changed warranty status. If you must cross regions, the global build (MIXM) is the usual compromise, and keep the original region package so you can roll back. ## How to choose the right region The safest method is to read the suffix of the build number currently installed, or to check the box and the sales channel for the market. Then pick the same region on the device page here. If the device is unlocked and you want one build that works in many countries, choose global. --- # How to Find Your Xiaomi Device Codename Before Flashing URL: https://rom.123wen.cn/en/guide/check-device-code/ Last updated: Oct 28, 2026 Every firmware package is matched to a device by codename. Learn how to read the codename from Settings, the Fastboot screen or an ADB command, and how it appears in recovery and fastboot file names so you never flash the wrong package. ## Method 1: Settings 1. Open Settings, then About phone, then Detailed info and specs. 2. Tap the kernel version repeatedly to open the system information screen; some models show the codename there. 3. You can also note the model number, such as 22126RN91Y, and search this site by name. ## Method 2: The Fastboot screen Power off, then hold Volume Down and Power. The Fastboot screen shows PRODUCT NAME at the bottom, for example earth. This is the most direct source, and the same codename appears in fastboot package file names. ## Method 3: An ADB command Enable developer options and USB debugging, connect the phone, then run adb shell getprop ro.product.device. The value it returns is the device codename. adb shell getprop ro.product.model returns the model number instead. ## How the codename appears in file names Fastboot packages start with the codename, for example earth_images_OS1.0.8.0.UCVCNXM_...tgz. A different codename means the package does not belong to that device, and forcing it will fail or damage the phone. - Same codename: safe to flash - Different codename but the same product family: still not interchangeable - Similar marketing names: always trust the codename, since names change by market --- # HyperOS Stable, Developer, Beta and Demo Builds Compared URL: https://rom.123wen.cn/en/guide/beta-vs-stable/ Last updated: Oct 28, 2026 Xiaomi ships several firmware branches with different release cadence and stability. Compare stable, developer, beta and demo builds, learn how to tell which branch a device is running, and what switching between them actually requires. ## Branch comparison | Branch | Flag | Characteristics | Who it suits | | --- | --- | --- | --- | | Stable | F | Reliable, released monthly or quarterly, normal OTA | Almost everyone | | Developer | X | Faster feature updates, possible bugs, requires an application | Early adopters and developers | | Beta | X | Closed testing for selected models, more issues | Test participants | | Demo | D | Retail display builds with demo restrictions | Not for daily use | | Carrier | F | Carrier preloads and network configuration | Customers of that carrier | ## How to tell which branch you are on Every build on a device page is labelled with its branch. You can also check the build number under Settings: stable builds end with a stable version number, while developer builds carry internal-test markers. ## Switching branches - Stable to developer: usually requires a fastboot flash or an accepted beta application, and wipes data. - Developer to stable: moving across branches normally needs a fastboot flash; a recovery install will not work. - Demo to stable: requires the fastboot package for the correct region, plus a check of the bootloader state. --- # How to Read HyperOS and MIUI Version Numbers (OS2.0.x.x Explained) URL: https://rom.123wen.cn/en/guide/version-naming/ Last updated: Oct 28, 2026 Take OS3.0.2.0.WOCMIXM apart piece by piece: system generation, build counter, device and Android segment, and the region suffix. Learn what each part means, which build is newer, and which market a package belongs to. ## Anatomy of a build number | Segment | Meaning | Notes | | --- | --- | --- | | OS3.0 | System generation | HyperOS 3.0; the MIUI era used forms such as V14.0 | | 2.0 | Build counter | Increments within a generation; a higher number is usually newer but does not imply downgrade support | | WO | Device and Android segment | Letters differ by model and Android version and are assigned by Xiaomi | | CM | Market segment | Commonly CN for China, MI for global, EU for Europe | | MI | Region suffix | Combined with the preceding pair it forms MIXM, CNXM, EUXM and so on | ## Common region codes - CNXM: mainland China, including carrier variants. - MIXM: global, covering most non-EU markets. - EUXM: EEA, configured for EU compliance. - INXM / IDXM / RUXM / TRXM / TWXM: India, Indonesia, Russia, Turkey and Taiwan. ## Judging age and compatibility - Compare the system generation first (OS3.0 is newer than OS2.0), then the build counter. - Cross-generation upgrades usually need a fastboot flash and may not be reversible. - Different region suffixes are different branches; whether they can be cross-flashed depends on the model and bootloader state, not on the version number alone. - Every build page here lists the actual release date and Android version, so you can compare directly instead of guessing from the number. --- # How to Verify a Downloaded Xiaomi Firmware Package URL: https://rom.123wen.cn/en/guide/verify-firmware/ Last updated: Oct 28, 2026 Confirm that a downloaded ROM is complete, unmodified and correct for your device: check the file name and version, inspect the archive structure, confirm the download came from the official CDN, and run the minimum checks before flashing. ## Step 1: check the file name A recovery package looks like miui_EARTH_OS1.0.8.0.UCVCNXM_xxxx.zip and a fastboot package looks like earth_images_OS1.0.8.0.UCVCNXM_xxxx.tgz. The codename and region code in the name must match your device and the build page you downloaded from. ## Step 2: confirm the archive is intact - Recovery package (.zip): open it with any archive tool; you should see the META-INF and firmware-update folders and no CRC errors. - Fastboot package (.tgz): after extraction you should have an images directory and scripts such as flash_all; a clean extraction means the archive is complete. - An extraction error, or a file clearly smaller than expected, means the download was interrupted and should be repeated. ## Step 3: confirm the source The download URL should be on an official host such as cdnorg.d.miui.com or bn.d.miui.com. If you obtained the file from a third-party mirror, you accept the risk yourself; compare its size and file name against the official package first. ## Why this site does not list MD5 or SHA-256 Xiaomi does not publish checksums for individual firmware packages, so any published value would lack an authoritative source. Instead of filling in guessed hashes, this site states clearly that no checksum is provided and relies on the file name, archive structure and source. --- ## Appendix: Site documents # About Hyper ROM: An Independent Xiaomi Firmware Index URL: https://rom.123wen.cn/en/about/ Last updated: Oct 28, 2026 Hyper ROM is an independent index of official Xiaomi HyperOS and MIUI firmware. It organises builds by device, country or region and version number, links only to the official Xiaomi CDN, and never hosts firmware files. ## What this site does Firmware for Xiaomi, REDMI and POCO devices is spread across regions and build numbers, and it is genuinely hard to tell which package matches a given phone. This site splits the upstream open dataset by device, region and build number, gives every build its own page, and lists the system generation, Android version, release date and security patch alongside it. ## Data source and updates - Data comes from the open-source HegeKen/HyperData project on GitHub. - A sync job checks upstream commits every 5 minutes and downloads only changed files. - The site index is rebuilt from the latest commit, and pages show the commit and sync time. - Download URLs are assembled from the build number and official file name and point to Xiaomi's CDN. ## What this site does not do - It does not host or re-upload any firmware file. - It does not offer unlocking, rooting or cracking services. - It is not affiliated with Xiaomi, and the content is provided for reference only. --- # Data Methodology: How Xiaomi Firmware Data Is Collected and Verified URL: https://rom.123wen.cn/en/methodology/ Last updated: Oct 28, 2026 How Hyper ROM collects, syncs and verifies firmware data: the upstream source, the incremental sync process, what each field means, how regions are assigned, the indexing thresholds, and the known limitations of the dataset. ## Sync process 1. Query the latest upstream commit every 5 minutes. 2. Fetch the file tree and compare blob hashes against the local snapshot. 3. Download only the device JSON and images that changed. 4. Rebuild the device catalog and site index, then refresh the sitemap cache. ## Field reference | Field | Meaning | | --- | --- | | Build number | Official firmware identifier such as OS1.0.8.0.UCVCNXM | | System | System generation derived from the build prefix, such as HyperOS 1.0 | | Android | Underlying Android version of the build | | Release date | Official release or build date supplied by upstream | | Security patch | Android security patch level supplied by upstream | | Recovery package | Recovery / OTA file name (.zip) | | Fastboot package | Fastboot file name (.tgz) | | Region | Taken from the branch region field and matching the build suffix | ## Update frequency The site updates daily: the sync job checks upstream commits every 5 minutes, and any new build or device automatically produces the corresponding pages plus refreshed sitemaps and RSS. Each page shows both "last checked" and "data updated": the first is when the sync job last looked for changes, the second is when the data actually changed. The dateModified value in structured data uses the real data update time and does not change on every request, while the release date always describes the firmware itself. The three timestamps never impersonate each other. ## How regions are assigned The region comes from the upstream branch field and matches the suffix of the build number. Separate pages are created for each region branch of a device, so cross-region builds are never mixed into one list. ## Data quality and indexing thresholds A page enters the sitemap only when it meets every hard requirement: it returns HTTP 200, the device and firmware relationship is real, the download URL is on the official CDN, the region code exists in the mapping table, the build number is complete and untruncated, and the metadata is unique. If any requirement fails, the page is not indexed. On top of that, pages are scored out of 100: complete device information 15, complete build data 20, clear device-region relationship 15, trustworthy file source 15, body text consistent with data 10, working internal links 10, correct structured data 5, unique metadata 5, accurate timestamps 5. Records scoring below 60 do not get a standalone indexed page, and records without any file name are excluded entirely. ## Known limitations - When upstream does not provide a file size, the page shows none rather than guessing. - Availability of carrier-specific packages depends on what upstream collects. - Release dates and security patches follow official and upstream data and may lag behind. --- # Disclaimer: Flashing Risk, Data Accuracy and Copyright URL: https://rom.123wen.cn/en/disclaimer/ Last updated: Oct 28, 2026 Hyper ROM is an independent firmware index that does not host firmware files. This disclaimer covers the risks of flashing and bootloader unlocking, the accuracy of the data, and copyright. ## Not affiliated with Xiaomi This website is an independent Xiaomi firmware information repository and is not affiliated with Xiaomi Inc. Xiaomi, Redmi, POCO and HyperOS are trademarks of their respective owners. Firmware compatibility depends on the exact device model, region and installation method. Always verify the firmware details before installation and back up your data. ## Flashing risk - Fastboot flashing, bootloader unlocking and cross-region installation can cause data loss or leave the device unable to boot. Back up everything first. - Firmware from another region can affect calls, NFC, payments and OTA delivery. - Whether a package can be flashed depends on the model, codename, region branch, bootloader state and installation method, not on the version number alone. - Flashing can affect warranty decisions, so assess the consequences yourself. ## Data accuracy Page data comes from Xiaomi firmware servers, indexed through a third-party open-source project. It is kept in sync as closely as possible but is not guaranteed to be complete, accurate or current. Check the build number, codename and region code before downloading. This site does not publish file sizes or checksums because Xiaomi does not disclose them. Missing fields are labelled as not provided rather than filled with guesses. ## Copyright and reuse Firmware files remain the property of Xiaomi. This site only provides an index and official download addresses. If you reuse the data, credit the source and follow the licence of the upstream open-source project. --- # Developer API: Firmware JSON Endpoints, Sitemaps and RSS URL: https://rom.123wen.cn/en/developers/ Last updated: Oct 28, 2026 Public firmware data endpoints, sitemaps and RSS feeds from Hyper ROM, including the device catalog, per-device detail, dataset metadata, field structures, caching guidance and attribution requirements. ## Public endpoints | Endpoint | Description | Cache | | --- | --- | --- | | /data/catalog.json | Device summary, system distribution and recent-update flags | 2 minutes | | /api/device.php?code={codename} | All branches and builds for one device | 5 minutes | | /data/meta.json | Data commit, sync time and statistics | 1 minute | | /api/geo-questions.json | Fixed question set used for AI citation checks | 1 hour | | /feed.xml | RSS feed of recent firmware updates | 5 minutes | | /llms.txt | Site structure and data notes for AI retrieval | 1 hour | | /sitemap.xml | Sitemap index | 1 hour | ## Device detail fields | Field | Type | Description | | --- | --- | --- | | code | string | Device codename | | name | object | Device name in Chinese and English | | branches[].region | string | Region code (cn / global / eea …) | | branches[].name | object | Branch display name | | branches[].roms[] | array | Builds in that branch | | roms[].version | string | Build number | | roms[].release | string | Release date, YYYY-MM-DD | | roms[].recovery | string | Recovery package file name | | roms[].fastboot | string | Fastboot package file name | ## Usage guidelines - The endpoints are read-only GET requests with no authentication. Do not poll aggressively; cache for at least 5 minutes. - Link to the official CDN URLs shown on the page instead of mirroring or re-uploading files. - Credit HegeKen/HyperData and this page when reusing the data. - For bulk access, start from /sitemap.xml and /data/catalog.json rather than crawling every page. --- # Firmware FAQ: HyperOS Downloads, Regions and Flashing URL: https://rom.123wen.cn/en/faq/ Last updated: Oct 28, 2026 Answers to the most common questions about Xiaomi firmware: matching a package to your device, choosing a region, recovery versus fastboot packages, whether download links are official, update frequency, OTA delivery and warranty. ---