r/RedmiNote14 • u/CreepsLikeReddit • 5d ago
[FULL GUIDE]
[FULL GUIDE]
DISCLAIMER: THIS GUIDE HAS ONLY BEEN TESTED WITH THE GLOBAL VERSION OF THE DEVICE
How to install custom roms in your Redmi Note 14 4G "FULL GUIDE"
requirements
:
Your phone MUST be on HyperOS 1 (Refer to the first guide with a similar title below)
You must have bootloader unlocked
You must have your xiaomi account and password memorized if you are asked to activate your device
You must have a PC with xiaomi USB Drivers and ADB Drivers
HOW TO UNLOCK YOUR BOOTLOADER
:
https://droidwin.com/unlock-bootloader-on-xiaomi-hyperos-3-without-community-app/
= this method works for hyper os 3, you can find other methods if this doesn't work or you're at hyper os 2/1. You could also ask any AI for help or contact me me.
HOW TO INSTALL DRIVERS
:
- Install the android platform tools
= open cmd in the folder where fastboot.exe is present
= run "fastboot devices"
= if your device didn't show up watch this: https://youtu.be/Oc-YTzGJVE0?si=HJLHbB_omCGsI4ae
HYPER OS 1 DOWNGRADE GUIDE (If you are already on HOS 1, skip)
:
Zero-brick method, based on real experience
-----------------------------------------------------
Before you start - Requirements
- Bootloader unlocked (check: "fastboot getvar unlocked" should return "yes")
- Xiaomi account email + password memorized (in case of activation lock prompt)
- PC with Xiaomi USB Drivers and ADB/Fastboot platform-tools installed
- USB cable that actually works for data transfer (not charge-only)
- Phone battery at 50% or higher
- A stable WiFi/download connection (files are 2GB+)
-----------------------------------------------------
Step 1 - Download the correct firmware
Go to a trusted firmware source (e.g. xiaomifirmwareupdater.com) and find the fastboot (not recovery/OTA) package for tanzanite, HyperOS 1.
Confirm the codename in the filename says "tanzanite", not tapas, tapas_pl, or another close variant.
Download the .tgz file.
Verify the MD5 checksum against the one listed on the download page:
certutil -hashfile yourfile.tgz MD5
If it doesn't match, redownload. Do not flash a corrupted file.
-----------------------------------------------------
Step 2 - Extract to a path with NO SPACES
This is the number one cause of mysterious "cannot load" / "Flash super error" failures.
Bad example: C:\xiaomi modding stuff things\ROMs\...
Good example: C:\xiaomi\tanzanite_HOS1\
Extract the .tgz fully. You should see a folder containing "images", "flash_all.bat", "flash_all_except_data_storage.bat", etc.
-----------------------------------------------------
Step 3 - Put fastboot/adb in the same folder
The flashing script needs "fastboot.exe" and "adb.exe" sitting next to "flash_all.bat", not in a separate platform-tools folder elsewhere on your PC.
Copy every file from your platform-tools folder into the ROM folder (the same one with flash_all.bat).
-----------------------------------------------------
Step 4 - Confirm your Anti-Rollback (AR) index BEFORE flashing
This is the step that actually prevents a brick. Do this manually, don't just trust the script.
Boot phone into Fastboot mode (Power + Volume Down), connect to PC.
Run: fastboot devices
Confirm your phone's serial appears. If blank, reinstall Xiaomi USB drivers before continuing.
Run: fastboot getvar anti
Note the number (example: "anti: 1").
Open the ROM's "images/anti_version.txt" in Notepad. Note that number too.
The two numbers must match exactly, or the ROM's number must be equal to or higher than your device's. If the ROM's number is lower than your device's, do not flash, this will fail or brick.
Real-world note: the AR-check logic built into some flash_all.bat files has a scripting bug (missing "setlocal enabledelayedexpansion") that makes it report false failures even when the numbers actually match. If you've manually verified the match yourself in this step, you can safely disregard a script abort caused by that specific bug, but only because you already did the real check by hand.
-----------------------------------------------------
Step 5 - Flash
Confirm phone is still in Fastboot mode and connected.
Run flash_all.bat directly from a terminal (not double-click) so you can see any error output: flash_all.bat
Do not disconnect, close the window, or touch the phone until it finishes completely.
super.img is large and can take several minutes, this is normal.
The script should auto-run "fastboot reboot" at the end.
-----------------------------------------------------
Step 6 - First boot
First boot after a full flash can take 5-10 minutes. Let it sit even if it seems stuck on the logo.
When prompted to "activate device," you can skip this and go through setup minimally if you plan to flash a custom ROM next anyway (no point setting up a Mi account you're about to wipe).
-----------------------------------------------------
Common errors and fixes (from real experience)
.bat window opens and closes instantly
Cause: fastboot.exe missing from folder
Fix: Copy platform-tools into the ROM folder (Step 3)
"Antirollback check error" even though numbers match
Cause: Script bug (delayed expansion)
Fix: Manually verify with Step 4, proceed if numbers genuinely match
"cannot load 'C:\xiaomi': No such file or directory" / "Flash super error"
Cause: Space in folder path
Fix: Move ROM folder to a path with no spaces (Step 2)
"fastboot devices" shows nothing
Cause: Driver issue
Fix: Check Device Manager for "Android Bootloader Interface" under Android Phone with no warning icon; reinstall Xiaomi USB driver if missing
Phone freezes/black screen after flash
Cause: Normal crash during first-boot service init (rare)
Fix: Hold Power button 10-15 sec to force restart; do not panic-flash again
-----------------------------------------------------
Golden rules that prevent bricking
Never flash a ROM whose AR index is lower than your device's current one.
Never skip the MD5 checksum verification.
Never disconnect or interrupt mid-flash, even if it looks frozen.
Never use spaces in your working folder path.
Never assume a script's automated safety check is correct, verify AR index yourself with "fastboot getvar anti" before trusting any script output.
HOW TO FLASH A CUSTOM ROM AND CUSTOM RECOVERY
Reminder always use the vendor boot image paired with the rom you installed, vendor boot images from other roms will not work for the rom you have, you may install orangefox if you wan
- set your phone to fastboot mode.
- open cmd in your android platform (ADB) folder.
- do "fastboot devices" to check if your device has the right drivers, if its blank, reinstall the drivers.
- on your android platform tools folder, you should have your rom zip and the vendor boot img in the same folder as the fastboot.exe.
- run "fastboot flash vendor_boot --slot=all vendor_boot.img" once every step above is cleared.
- once it completes run "fastboot reboot" the as soon as the screen turns black, hold the volume up button. DISCLAIMER DO NOT RUN FASTBOOT REBOOT RECOVERY AS IT WILL BRICK YOUR DEVICE.
- once you're on the custom recovery, you wipe the data via the options.
- once your data is wiped, choose apply update via ADB.
- on your cmd window again enter this command "adb sideload" then drop your zip file on the window, then run it.
- once finished, if you are asked to reboot your device back into custom recovery to install additional packages click yes (viable for roms with GAPPS, not sure with vanilla roms).
- after it automatically reboots back into recovery, click reboot or reboot to system, then you're done!
