HyperOS 2.0 HyperOS 2.0 STABLE RELEASE


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.
 
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:
I recommend you to use KernelSU Next instead of Magisk. Magisk is problematic, I'm more than happy with KernelSU Next
 
  • Like
Reactions: Sithlord512589

Similar threads

  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
56K
Replies
51
Views
75K
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
117K
  • Locked
HyperOS 1.0 24.7.8/12
Replies
50
Views
45K