HyperOS 2.0 HyperOS 2.0 STABLE RELEASE


Good afternoon, everyone.
Is it possible to downgrade from HyperOS 2.0.10, which is the version I have on my Redmi Note 13 Pro 5g, to version xiaomi.eu_GARNET_OS2.0.7.0.VNRCNXM_15.zip, which is the only version hosted on SOURCEFORGE? Or should I wait for the community to upload version 2.0.10 to SOURCEFORGE?
Sometimes its possible to downgrade. Depands on changes between two versions.
 
  • Like
Reactions: Carballo
Good afternoon, everyone.
Is it possible to downgrade from HyperOS 2.0.10, which is the version I have on my Redmi Note 13 Pro 5g, to version xiaomi.eu_GARNET_OS2.0.7.0.VNRCNXM_15.zip, which is the only version hosted on SOURCEFORGE? Or should I wait for the community to upload version 2.0.10 to SOURCEFORGE?
"Downgrade" from 2.0.10 to 2.0.7? I'm not sure what version 2.0.10 is, latest version we have is 2.0.9.

I may get this wrong but Xiaomi ROMs have ARB (anti-rollback) implemented to stop you from rolling back.

The last time this affected me was on my Mi Max, so I'm not sure how it's changed now.
ARB? It was only used for 4 devices many years ago, Mi Max 3 was one of them.
 
"Downgrade" from 2.0.10 to 2.0.7? I'm not sure what version 2.0.10 is, latest version we have is 2.0.9.


ARB? It was only used for 4 devices many years ago, Mi Max 3 was one of them.
Ah see that's why I didn't say that it still existed, as I only knew of it when I had my Mi Max 3 and I thought they continued to implement it.

So basically, if I wanted to, I can downgrade from 2.0.205 to 2.0.102 for example?
 
Ah see that's why I didn't say that it still existed, as I only knew of it when I had my Mi Max 3 and I thought they continued to implement it.

So basically, if I wanted to, I can downgrade from 2.0.205 to 2.0.102 for example?
Not advised without a data format. Won't boot if security patch version is different.
Also, apps are not designed for downgrades, so some system apps may crash.
None of this has anything to do with ARB though (which hard-bricks on downgrades).
 
  • Like
Reactions: AsadP
Updated to the latest ROM, 2.0.202 on my ISHTAR, everytime charged the phone battery get heated very fast. Did not face this on previous ROM, anyone having this heating too? And is this normal?
 
I'm on Mac too.
I put my phone in fastboot mode. Then simply drag the "macos_install_upgrade.sh" file onto the terminal window and hit enter.
And that works perfect
Nah, it sort of worked, but lost many apps (thats okay) but I can NOT get any Google to work. Google App account, (please sign in, confirm on other devices, (either google, authenticator, sms, but no, bcnthen it stalls.) I empited, (dalvik) cacges, downgrade, did a reflash of both twrp, and reinstalled the rom again.
Its deffo in Google Play, perhaps in password storage?
 
Last edited:
New Peridot Update works like a charm, thank you !
Can you or perhaps any other one using a Poco F6 (peridot) tell me in short how you managed to install Xiaomi.eu HyperOS 2.0 on Poco F6 (peridot)? I followed the guide to the letter (coming from latest stock firmware via MIFlash Tool, bootloader unlocked and USB debugging enabled) and flashed using fastboot script (install_and_format_data). After flash it constantly ends up in fastboot after rebooting. Please see attached result of flash.

Or should I rollback to stock HyperOS 1.0 (coming from stock HyperOS 2.0), then flash HyperOS 1.0 Xiaomi.eu rom and then try to update to HyperOS 2.0 Xiaomi.eu rom?
 

Attachments

  • flash_peridot_hyperos2.0.txt
    15.6 KB · Views: 17
Last edited:
No idea what went wrong on your side @dudex , so after the script was successful, it should automatically reboot into the system. You did the right step. Your attached log seems correct to me, maybe try to flash it again and see what happens.
 
Can you or perhaps any other one using a Poco F6 (peridot) tell me in short how you managed to install Xiaomi.eu HyperOS 2.0 on Poco F6 (peridot)? I followed the guide to the letter (coming from latest stock firmware via MIFlash Tool, bootloader unlocked and USB debugging enabled) and flashed using fastboot script (install_and_format_data). After flash it constantly ends up in fastboot after rebooting. Please see attached result of flash.

Or should I rollback to stock HyperOS 1.0 (coming from stock HyperOS 2.0), then flash HyperOS 1.0 Xiaomi.eu rom and then try to update to HyperOS 2.0 Xiaomi.eu rom?
Do u use latest adb tools? Try another computer. Twrp yes or no. Twrp for peridot is buggy. My 2 cents
 
  • Like
Reactions: dudex
No idea what went wrong on your side @dudex , so after the script was successful, it should automatically reboot into the system. You did the right step. Your attached log seems correct to me, maybe try to flash it again and see what happens.
Thanks so much for your reply. Unfortunately retrying it failed once more.
 
Do u use latest adb tools? Try another computer. Twrp yes or no. Twrp for peridot is buggy. My 2 cents
Thank you Pakino2004 for your reply and tips. I will try another pc. Not using TWRP because it's buggy (found out from the many forums about it). And yes, had the latest ADB tools installed (downloaded them today).
 
And how about the warnings in the log file. Do they matter?
 

Attachments

  • flash_peridot_hyperos2.0 (1).txt
    15.6 KB · Views: 10
If nothing works, I would try to flash an official rom version via Miflash without relocking the BL and from there try to flash xiaomi.eu again the way you did.
Did that already. Reflashed the latest stock ROM using Miflash. And then tried to flash Xiaomi.eu ROM. Or should I be flashing an older stock ROM version with MiFlash, perhaps?
 
I was install last week last update for Vermeer, but I have a problem with Google phone app. When I receive a call, app closes and switch to Xiaomi phone. Only when I receive calls, if I call to others never closes.
Same issue on sapphiren, since last 3 versions released

Google dialer is default APP, permissions are fine. Still phone doesnt show incoming call, then popps up an error, and sometimes if Im lucky it shows Xiaomi dialer after the error popps up.
But most of the Times it ONLY starts ringing, doesnt show who is calling and i cant pick the call.
I need to wait for who ever is calling to end, then i can see who called, and call back

Totally removing Google dialer, and install it back, ONLY works as temp solution, it gets back to this strange behaviour

2.0.7.0 was the last version that this worked fine ( with february Patch level) .

Didnt tested 2.0.8.0 build.

But on builds 2.0.9.0 up to latest 2.0.11.0 this issue is present

Cheers
 
Last edited:
  • Like
Reactions: kingofdevils

Similar threads

  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
53K
Replies
51
Views
68K
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
103K
  • Locked
HyperOS 1.0 24.7.8/12
Replies
50
Views
42K