Redmi Note 13 4G NFC Sapphiren Can't update to OS1.0.8.0.UNHMIXM


Migsse

Members
8 Nov 2023
5
15
Hello

I have the Redmi Note 13 4G NFC Sapphiren.
Bootloader is unlocked, no TWRP/Orangefox(Both don't have this phone listed, only the Sapphire).

When I download the update, then it goes to recovery (Xiaomi HyperOS Recovery), my only options are Reboot - Wipe Data - Connect with MiAssistant.
Not able to select the zip file to to the update.

Also sadly I can't even load a stable official rom either due to not finding a recent version of MiFlash that recognizes this phone and is stable in Windows 10/11 (only found MiFlash20220507 and nothing newer so far).

So even if I screw things up, get into a boot loop etc, the only way I can recover the phone in a working state, is to use the rom and batch files provided by Xiaomi.EU.

Any assistance would be helpful.

Thanks in advance
 
Installation guide is given in the very first post of the recent STABLE ROMS thread.
There are also additional guides in the forum from the valued member @gogocar62:
Just make sure to download the correct ROM for your device.
 
Installation guide is given in the very first post of the recent STABLE ROMS thread.
There are also additional guides in the forum from the valued member @gogocar62:
Just make sure to download the correct ROM for your device.
The problem comes in with the step regarding recovery
Installing recovery method (TWRP)

On the websites of TWRP and OrangeFox, Sapphiren is not listed. Only Sapphire.
 
MiFlash is futile as long as your phone isn't bricked.

To update the ROM, you can just run the "windows_fastboot_update_rom.bat" file from the xiaomi.eu package while your phone is in fastboot (or the corresponding other file format if you're not on windows). No need for a custom recovery.

If you want to reflash the stock ROM, just run the "flash_all.bat" file from the stock package while your phone is connected in fastboot. No need for MiFlash.
(DO NOT run the "flash_all_lock.bat", it will cause a soft brick)
 
  • Like
Reactions: Migsse
@ntlkr
To update the ROM, you can just run the "windows_fastboot_update_rom.bat" file from the xiaomi.eu package while your phone is in fastboot (or the corresponding other file format if you're not on windows). No need for a custom recovery.
Thank you, this allowed me to upgrade to the newest firmware without losing any data on the phone.
One slight change though, using Windows anyway, the file to run was windows_install_upgrade.bat instead of windows_fastboot_update_rom.bat

I'll might look into stock roms in future, but for now, I'll try out the Xiaomi.EU Flavour.

Thanks again for the help, its really appreciated.

Now I can upgrade to the new phone.
 
  • Like
Reactions: ntlkr
Follow this page:
 
MiFlash is futile as long as your phone isn't bricked.

To update the ROM, you can just run the "windows_fastboot_update_rom.bat" file from the xiaomi.eu package while your phone is in fastboot (or the corresponding other file format if you're not on windows). No need for a custom recovery.

If you want to reflash the stock ROM, just run the "flash_all.bat" file from the stock package while your phone is connected in fastboot. No need for MiFlash.
(DO NOT run the "flash_all_lock.bat", it will cause a soft brick)
The advantage of Miflash is that it provides a detailed and very useful log in case of a problem.
 
The advantage of Miflash is that it provides a detailed and very useful log in case of a problem.
I do know that MiFlash has a log function, never had any problems while flashing with MiFlash though...
Do you have an example for what kind of problems could occur and what the log would state in that case?
 
I do know that MiFlash has a log function, never had any problems while flashing with MiFlash though...
Do you have an example for what kind of problems could occur and what the log would state in that case?
There are many, the most common error is the bootloader lock which is selected by default or flash timeout/crclist error which is often due to the usb cable/port or on certain versions of windows, the folder must be at the root of the disk or the super img which blocks, cable/port.