HyperOS 2.0 HyperOS 2.0 STABLE RELEASE


On xiaomi.eu_ONYX_OS2.0.216.0.VOLCNXM_15 screencast does not work. after click on screencast, ist seems to somethin is open but the fokus is on the screen befor you push on screencast. No Exeption or error is shown.
mine is working just fine casting to my Android TV
 
Hello, I have a question.Is the room.eu for the Poco F7 Ultra the K80 Zorn? Is it the same as the Poco F7 Pro?
 
No. It's like this:
REDMI K80 Pro = POCO F7 Ultra = miro
REDMI K80 = POCO F7 Pro = zorn
REDMI Turbo 4 Pro = POCO F7 = onyx
 
I didnt find OS2.0.208.0.VMACNXM for ishtar on chinese ROMs websites. Anyone know something about that?
Everywhere I found only OS2.0.207.0.VMACNXM
 
Hello, my Poco F7 Ultra "Miro" shows me that the version 3.0.3.0 WOMCNXM as an update of the EU. ROM is available. When I go to download, I always get the message that I already have the current version. But I'm still on HyperOS2. However, the version is not yet offered on the download page. My phone comes about every minute with a new message new version available. Are you offering the version 3.0 now, or is that a bug? And if it's an error, how do I get the message deleted again?
 

Attachments

  • Screenshot 2025-11-06 130322.png
    Screenshot 2025-11-06 130322.png
    226.7 KB · Views: 133
 
  • Like
Reactions: dannyzamora
Hi i having an issue with the signal on a xiaomi 13 ultra the 4g is not working
And currently is on official xiaomi global rom 2.0.207.0.VMAMIXM (not xiaomi.eu) previously it was on latest xiaomi.eu
It's okay to flash the modem with the NON-HLOS.bin? From the original rom
Or is there something else that has to be done
 
There's no way to download the last rom for Garnet. The speed is abysmal.
Scratch that, now it works like a charm!
 
Last edited:
I believe the proximity sensor has an issue, on hos2 eu build for marble in, flashed the latest indian firmware before flashing hos2 eu. It works well for calling, but the screen won't turn off for apps that use the proximity sensor that don't have the calling feature
 
Not sure why my previous account got banned.

Hi team, thanks for the hard work. However, there seems to be an issue with the latest FUXI rom - xiaomi.eu_FUXI_OS2.0.215.0.VMCCNXM_15.zip.

So I tried to flash this firmware about 5 times and everytimes I was trapped in a Fastboot loop. The terminal window (Windows 11 cmd) closes automatically at the end each time, so I can't see what the final message is. However, the phone enters fastboot mode again every single time after auto reboot, and I can't exit it.

Fortunately I kept a copy of xiaomi.eu_FUXI_OS2.0.203.0.VMCCNXM_15, I clicked the same bat "windows_install_and_format_data" and the rom flashed in without any issue, the phone gets to the system as normal.

As such, I think there has been an issue with the latest miui eu rom of Xiaomi 13 (FUXI) xiaomi.eu_FUXI_OS2.0.215.0.VMCCNXM_15.zip.

Please also let me know if you need more info or if it's something wrong with my process.

Thanks again for your time. Cheers
 
Not sure why my previous account got banned.

Hi team, thanks for the hard work. However, there seems to be an issue with the latest FUXI rom - xiaomi.eu_FUXI_OS2.0.215.0.VMCCNXM_15.zip.

So I tried to flash this firmware about 5 times and everytimes I was trapped in a Fastboot loop. The terminal window (Windows 11 cmd) closes automatically at the end each time, so I can't see what the final message is. However, the phone enters fastboot mode again every single time after auto reboot, and I can't exit it.

Fortunately I kept a copy of xiaomi.eu_FUXI_OS2.0.203.0.VMCCNXM_15, I clicked the same bat "windows_install_and_format_data" and the rom flashed in without any issue, the phone gets to the system as normal.

As such, I think there has been an issue with the latest miui eu rom of Xiaomi 13 (FUXI) xiaomi.eu_FUXI_OS2.0.215.0.VMCCNXM_15.zip.

Please also let me know if you need more info or if it's something wrong with my process.

Thanks again for your time. Cheers
There's no issue with the ROM. All are built in the same way via automation. Redownload the ROM if the ZIP is corrupted.
 
There's no issue with the ROM. All are built in the same way via automation. Redownload the ROM if the ZIP is corrupted.
I understand it must be feeling very strange. But I tried 3 times on my laptop and 2 times on my desktop. Both zip files were downloaded from sourceforge directly and no copy/paste involved. I also tried installing 203 and upgrade to 215 without format but no luck - fastboot loop.
 
I understand it must be feeling very strange. But I tried 3 times on my laptop and 2 times on my desktop. Both zip files were downloaded from sourceforge directly and no copy/paste involved. I also tried installing 203 and upgrade to 215 without format but no luck - fastboot loop.

Did you do a MD5 on the zip file after downloading?
 
swear to god they are the same

I just tested to make sure what SourceForge sent me had the correct MD5 and zero issues extracting, so at least no odd corruption bit there.. You might want to do a screen recording of your interaction with terminal to discover what happens as the terminal closes.
 

Attachments

  • FUXI-215-MD5.png
    FUXI-215-MD5.png
    44.3 KB · Views: 95