HyperOS 2.0 HyperOS 2.0 STABLE RELEASE


Hello
I use a xiaomi14 pro , on xiaomi.eu 2.0.11.0
the software shows me a possible update 2.0.104 but when i try to update with twrp it opens hyper os recovery with only 2 options , erase or reboot
And i dont have a pc for fastboot
I dont t see any solution to update
Any help ?
You will definitely need a PC with fastboot.
For some reason (nobody here understands), the devs no longer include twrp in the ROM. This means, we either have to reflash twrp manually after each update, or (if you don't need twrp for other things) you just use fastboot for every update.

...or you just stick with 2.0.11..
2.0.101.0 and 2.0.104.0 mostly contain updates to HyperAI, which isn't accessible outside China anyways.
 
Last edited:
For some reason (nobody here understands), the devs no longer include twrp in the ROM. .
 
  • Like
Reactions: ntlkr
Hello!
I have the latest FUXI on my X13 phone. The phone is connected to a Huawei Watch GT3pro. It receives notifications, but very often in "confidential" form, which reduces the utility of the watch. Can anyone help me with what to set on the phone to get rid of this problem?
Thanks in advance for any help!
Hi,
Unfortunately the problem is still present in xiaomi.eu_FUXI_OS2.0.104.0.VMCCNXM_15.
Does anyone have any idea how to fix this problem?
 
Hi,
Unfortunately the problem is still present in xiaomi.eu_FUXI_OS2.0.104.0.VMCCNXM_15.
Does anyone have any idea how to fix this problem?
Did you try settings-notifications-lock screen and on Format select "Show notifications and content"?

Sent from my 2210132G using Tapatalk
 
Aurora 2.103 latest stable.

Seems like the Quick ball option is prevented from autostart after every reboot. Not sure if this is a xiaomi.eu specific bug, or a xiaomi specific bug, but have to go into settings and disable/enable it every time I reboot.
 
Interesting, thanks for the heads-up.

Anyways, I still wonder why we don't just include the A15 twrp as recovery.img then. Simply because it's slightly more work and not 100% necessary or is there another reason?
 
  • Like
Reactions: Mario1944
Interesting, thanks for the heads-up.

Anyways, I still wonder why we don't just include the A15 twrp as recovery.img then. Simply because it's slightly more work and not 100% necessary or is there another reason?
I don't know the reason, but if they had to keep up with the TWRP versions for 40+ supported devices, and now with risks for the end user... I would not call it "slightly more work".
 
Hello, I always appreciate the contribution from the developer and the community. I just installed the version 2.0.4.0 on my Redmi Note 13 Pro 5G (Garnet) device and it says "problem communicating with the servers" and I can't use Google services.

xiaomi.eu_GARNET_OS2.0.4.0.VNRCNXM_15.zip

Screenshot_20250227_004342_Brave.jpg
Screenshot_20250227_004401_Brave.jpg
Screenshot_20250227_005503_Brave.jpg
 
Last edited:
Good morning. I got the official Hyper OS 2.0 update yesterday before I got the 1.0 EU rom. Am I supposed to assume that I won't get the 2.0 EU rom until all the smartphone models that have the 1.0 EU rom get the 2.0 rom? Or is there no preference in publishing the 2.0 EU rom list? Thanks for your reply.
Greetings!
 
Hello, I'd like a clarification please, I've been watching this post since its creation in November and I see that the file dates are from January to now, are the versions kept up to date or just modified with the security or just an integration of the gpay fix modifications?

Thanks (houji)
 
Am I supposed to assume that I won't get the 2.0 EU rom until all the smartphone models that have the 1.0 EU rom get the 2.0 rom? Or is there no preference in publishing the 2.0 EU rom list?
There is no preference that I know of, but maybe if you told us what is your smartphone model, it could help understand the context of your question.
Are the versions kept up to date or just modified with the security or just an integration of the gpay fix modifications?
The versions are kept up to date
 
Interesting, thanks for the heads-up.

Anyways, I still wonder why we don't just include the A15 twrp as recovery.img then. Simply because it's slightly more work and not 100% necessary or is there another reason?
Can we change the recovery.img to the TWRP A15 by ourself, like the modem and flash it then? Any Risks? And must the TWRP installed once before flashing with changed recovery.img?
 
Can we change the recovery.img to the TWRP A15 by ourself, like the modem and flash it then? Any Risks? And must the TWRP installed once before flashing with changed recovery.img?
I don't understand the grammar in that sentence.
Copy TWRP to device, reboot to recovery, flash the ROM without rebooting, flash TWRP to recovery partition using "Install Image" button, reboot to system.
 
  • Like
Reactions: SpreeWolf
I don't understand the grammar in that sentence.
Copy TWRP to device, reboot to recovery, flash the ROM without rebooting, flash TWRP to recovery partition using "Install Image" button, reboot to system.
The question is, if we swap the stock recovery in the installer package with twrp file before installation, could this lead to any problems while/after installing?
 
Hello. I was trying to download the newest rom for houji but can't unpack it, zip is damaged. Tried to download from another mirror and same problem.
 
Xiaomi 13 (fuxi)
1. AI Pro functions (services) in gallery are gone.
2. Battery draining still fast (clean install)
 
can you please explaint it a bit?
Sourceforge allows you to download from different mirrors, in case the one assigned (usually closest by distance) is not satisfying, albeit in a very non-obvious way (you have to click "problems downloading" after initial download to select a different mirror). The policy that determines whether resume is allowed or not is in the hands of the mirror. Onboard Cloud mirror which resides in Singapore allows resume.
 
THow can I make the app full screen now? Previously it was possible in the app properties, but now there is no such item and I couldn't find it in the settings.
 

Similar threads

  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
50K
Replies
51
Views
62K
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
89K
  • Locked
HyperOS 1.0 24.7.8/12
Replies
50
Views
40K