HyperOS 2.0 HyperOS 2.0 STABLE RELEASE


bomack said:
That doesn't sound right.
Have you wiped and reloaded the firmware?
You can also flash the modem again.

More details needed here. Was it an upgrade? What firmware and version did you have before?

Describe no network connection more. What is the phone doing?
Click to expand...
Previously, I had Taiwan ROM OS2.0.103.0.VMCTWXM. I reset it and installed Fuxi Eu ROM. No network. I rewrote the IMEI with the dft pro tool, but there is still no network.

Both devices are the same, but the one on the right works fine while the one on the left does not receive a network signal. The software and model are the same. Is this visual difference due to QCN?
 

Attachments

  • Screenshot_2025-08-20-03-00-07-763_com.miui.home.jpg
    Screenshot_2025-08-20-03-00-07-763_com.miui.home.jpg
    507.5 KB · Views: 139
  • Screenshot_2025-08-20-03-00-24-514_com.android.phone.jpg
    Screenshot_2025-08-20-03-00-24-514_com.android.phone.jpg
    207.6 KB · Views: 135
  • Screenshot_2025-08-20-03-00-46-509_com.android.phone.jpg
    Screenshot_2025-08-20-03-00-46-509_com.android.phone.jpg
    150.7 KB · Views: 132
  • IMG_20250820_041246_230.jpg
    IMG_20250820_041246_230.jpg
    604.4 KB · Views: 126
Last edited:
SynxOS said:
There's no charging while the 15 Ultra is off. Why isn't there? Can it be added?
Click to expand...
they changed it how it works,
first plug in your Phone and then turn it off , it will charge while its off

i read somehwere that google wanted that every phone boots up when pluged in , it should be security feature or something like that
 
  • Like
Reactions: SynxOS, 205GTX and DR.Ryniach
Does anyone know, if Xiaomi has updated the OS to work with Android Auto in Redmi Note 12 modells ?
 
Hello,

First of all thank you all for your work!
Now to my problem
I have installed xiaomi.eu_LISA_OS2.0.10.0.UKOCNXM_14.zip On
my phone, everything works fine, only goole wallet says the device doesnt meet security standards when trying to add a credit card.
On the other hand my Xiaomi Mi 13 Pro (Nuwa) with current hyperos 2 from xiaomi.eu can use google wallet.

Both devices are not rooted both devices meet only basic integrity test

Thank you for your help!

Lukas
 
LUKI508 said:
Hello,

First of all thank you all for your work!
Now to my problem
I have installed xiaomi.eu_LISA_OS2.0.10.0.UKOCNXM_14.zip On
my phone, everything works fine, only goole wallet says the device doesnt meet security standards when trying to add a credit card.
On the other hand my Xiaomi Mi 13 Pro (Nuwa) with current hyperos 2 from xiaomi.eu can use google wallet.

Both devices are not rooted both devices meet only basic integrity test

Thank you for your help!

Lukas
Click to expand...
FAQ section Play Integrity attestation doesn't pass Device Integrity
 
  • Like
Reactions: dannyzamora
zyoops said:
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
Click to expand...
Experienced this issue also in Lisa device on xiaomi.eu_LISA_OS2.0.10.0.UKOCNXM_14.zip

Best regards
 
Hi, I 've just updated on Xiaomi 12 ( Cupid) . Phone is blocked in loop in recovery mode ....I can't do anything .... :emoji_triumph:
Has someone the same issue ?
Any ideas to fix this ?
 
Hi, I just updated to SHENNONG_OS2.0.216.0.VNBCNXM_15.zip and i ran into this following Issue.

-I updated Rom via TWRP 3.7.1_16-Xiaomi_14_Pro-A15 with only the known message (not mounting) but update and reboot was okay.
-Then i rebooted into Fastboot for flashing TWRP Recovery back with reboot into TWRP
-In TWRP i flashed Magisk 29.0 stable and reboot.
-In System after reboot i finished installation of Magisk -> Direct Install (2nd option) and reboot.

Now comes the issue:
After rebooting my System i cannot start any App. Instead of that i´m getting an error message that says:
"You cannot start any app until the boot process is completed."
I also noticed that the widgets stay blank (instead of showing data after 1-2 seconds after boot)
Then I thought maybe an Issue with the Lockscreen password so i tried to deactivate it to reflash the whole thing.
Next surprise: When i enter my password then comes always "Re-Try" and i cannot deactivate my password.
So in this state my phone wasn´t usuable because no app started.

I returned to Version 2.0.215.0 and everything works fine again until i rooted my phone again -> same issue as with 2.0.216.0.

Here was my individual mistake: My Magisk is renamed to a custom name.

Here comes the solution for my mistake:
-In Magisks (of course it´s Magisk ) the apps wants to finish the Installation but at this point i canceled this.
-Instead i went back to the main screen of Magisk and reinstalled the app itself.
-After exiting and restarting Magisk i got the message to complete installation again and this time the Magisk Version and Changelog infos were given.
-So i did the reinstall with "direct patch" (2.option).
-This time after rebooting everything went fine... as far as i can see...


So i´m now in 2.0.216.0 and my problem wasn´t a rom issue at all... Just a Magisk users issue
Like the old joke in the IT says: "99,9% of all computer errors are sitting on the keyboard"
So maybe my experience is helpful for some Magisk Users.

So i don´t know if this post wouldn´t better belong to the Root Section instead of here.
So Mods feel free to move this post. Or let me know if i need to rewrite it into the root topic.

Anyways i don´t want to miss the chance to thank all you great and crazy guys who keep this project alive for so many years.
I really appreciate your great work.... Thank you very much :emoji_pray:
 
Last edited:
  • Like
Reactions: Ahaba
I just installed xiaomi.eu_FUXI_OS2.0.207.0.VMCCNXM_15.zip after installing, the phone information shows that version 2.0.203.0 is stable and the unlock password can still be opened, but TWRP has the wrong password so I can't install another ROM. Please help me.
 
Hello. This morning I installed the latest version 2.0.215 on xiaomi 15 from 2.0.214 version. Everything works fine except that my watch with wearOS has stopped being recognized (OnePlus watch 2). I've tried factory resetting the clock, reinstalling the OnePlus app and clearing the cache of the Bluetooth app but nothing works. When it comes to pairing it with the mobile phone, it gives an error. I have tried pairing it with another smartphone and it works without problems.
 
Sithlord512589 said:
Hi, I just updated to SHENNONG_OS2.0.216.0.VNBCNXM_15.zip and i ran into this following Issue.

-I updated Rom via TWRP 3.7.1_16-Xiaomi_14_Pro-A15 with only the known message (not mounting) but update and reboot was okay.
-Then i rebooted into Fastboot for flashing TWRP Recovery back with reboot into TWRP
-In TWRP i flashed Magisks 29.0 stable and reboot.
-In System after reboot i finished installation of Magisk -> Direct Install (2nd option) and reboot.

Now comes the issue:
After rebooting my System i cannot start any App. Instead of that i´m getting an error message that says:
"You cannot start any app until the boot process is completed."
I also noticed that the widgets stay blank (instead of showing data after 1-2 seconds after boot)
Then I thought maybe an Issue with the Lockscreen password so i tried to deactivate it to reflash the whole thing.
Next surprise: When i enter my password then comes always "Re-Try" and i cannot deactivate my password.
So in this state my phone wasn´t usuable because no app started.

I returned to Version 2.0.215.0 and everything works fine again until i rooted my phone again -> same issue as with 2.0.216.0.

Here was my individual mistake: My Magisks is renamed to a custom name.

Here comes the solution for my mistake:
-In Magisks the apps wants to finish the Installation but at this point i canceled this.
-Instead i went back to the main screen of Magisks and reinstalled the app itself.
-After exiting and restarting Magisks i got the message to complete installation again and this time the Magisks Version and Changelog infos were given.
-So i did the reinstall with "direct patch" (2.option).
-This time after rebooting everything went fine... as far as i can see...


So i´m now in 2.0.216.0 and my problem wasn´t a rom issue at all... Just a Magisks users issue
Like the old joke in the IT says: "99,9% of all computer errors are sitting on the keyboard"
So maybe my experience is helpful for some Magisks Users.

So i don´t know if this post wouldn´t better belong to the Root Section instead of here.
So Mods feel free to move this post. Or let me know if i need to rewrite it into the root topic.

Anyways i don´t want to miss the chance to thank all you great and crazy guys who keep this project alive for so many years.
I really appreciate your great work.... Thank you very much :emoji_pray:
Click to expand...
I recommend you to use KernelSU Next instead of Magisk. Magisk is problematic, I'm more than happy with KernelSU Next
 
  • Like
Reactions: Sithlord512589
topaloglu321 said:
I recommend you to use KernelSU Next instead of Magisk. Magisk is problematic, I'm more than happy with KernelSU Next
Click to expand...
I would give it a try..Is there any good step by step manual for the first time setting everything up?
And especially the warnings to avoid a factory reset
 
You must log in or register to reply here.

Similar threads

ingbrzy
  • Locked
HyperOS 1.0 24.7.28 (Final)
Replies
292
Views
889K
HyperOS
Igor Eisberg
Igor Eisberg
ingbrzy
  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
103K
HyperOS
Mistery88
M
ingbrzy
  • Locked
HyperOS 1.0 24.7.22/25/26
Replies
51
Views
124K
HyperOS
Ahaba
A
ingbrzy
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
186K
HyperOS
KGVER
KGVER
ingbrzy
  • Locked
HyperOS 1.0 24.7.8/12
Replies
50
Views
68K
HyperOS
emre_66
E
Top Bottom
Back