HyperOS 2.0 HyperOS 2.0 STABLE RELEASE


Yes, with the last version (101) for vermeer the errors stop with mi-connect. All good now and the safety date is 1-1-25. Will check the battery life now for some days.
 
be able to log in to the part where it asks you to block by pin and just skip the option
I don't even see this option, I confirm the phone number and I get the message that the app isn't official.
 

Attachments

  • Screenshot_2025-01-08-13-25-40-111_com.whatsapp.jpg
    Screenshot_2025-01-08-13-25-40-111_com.whatsapp.jpg
    323.6 KB · Views: 71
  • Like
Reactions: Pakino2004
Yes, with the last version (101) for vermeer the errors stop with mi-connect. All good now and the safety date is 1-1-25. Will check the battery life now for some days.
Yes, but mi connect is still searching for devices in background even when turned off, and it is draining battery
 
Last edited:
I'm having the same problem with Whatsapp
Are you rooted. maybe changes in the builtprop like the name of the phone itself gonna help. I'm not rooted because of a failure with twrp. Mine is not touchresponsive. Never worked with my phone. Doesn't matter which kind of twrp. I don't no why...
 
Are you rooted. maybe changes in the builtprop like the name of the phone itself gonna help. I'm not rooted because of a failure with twrp. Mine is not touchresponsive. Never worked with my phone. Doesn't matter which kind of twrp. I don't no why...
I'm not rooted, I did a clean installation without root
 
Ok, didn't know this..
Can you tell me how to stop mi-connect or even delete it?
Remove with exa system app remover

Disable with ice box or hail



I choose to disable it, because you never know with system apps

There is also problem with Interconectivity system app
You can check in settings>notifications>history
 
  • Like
Reactions: groxFR
Just upgraded Peridot to 2.0.6, everything ok. Just have one problem that has been around for years: the games are at 60hz. Searched a lot online, and the only solution is to wipe data of "battery and performance". Is there any other workaround to make it permantly stick to 120hz? Didn't have this problem on global ROM btw. Thank you for the constant updates!
Does anybody know anything about this? Thanks
 
I updated my TWRP to A15 and flashed the HyperOS 2.0 rom 12S Pro (unicorn).
I got a lot of "skip copying super image avb footer due to sparse image" errors and my phone only shows Xiaomi HyperOS. I tried to flash the rom via windows and over TWRP.
Anyone an idea how to fix it ?

Thank you
 
I updated my TWRP to A15 and flashed the HyperOS 2.0 rom 12S Pro (unicorn).
I got a lot of "skip copying super image avb footer due to sparse image" errors and my phone only shows Xiaomi HyperOS. I tried to flash the rom via windows and over TWRP.
Anyone an idea how to fix it ?

Thank you
After booting, wait for a while, then have someone call your phone. This might help in completing the boot process.
Although the phone has likely already finished booting, the screen might be stuck due to some bugs. If you connect your phone to a computer and run ADB commands, it works, indicating that the booting is complete.
Some overlay actions like an alarm or phone call might help getting out of the infinite boot screen as I tested.
 
I updated my TWRP to A15 and flashed the HyperOS 2.0 rom 12S Pro (unicorn).
I got a lot of "skip copying super image avb footer due to sparse image" errors and my phone only shows Xiaomi HyperOS. I tried to flash the rom via windows and over TWRP.
Anyone an idea how to fix it ?

Thank you
After booting, wait for a while, then have someone call your phone. This might help in completing the boot process.
Although the phone has likely already finished booting, the screen might be stuck due to some bugs. If you connect your phone to a computer and run ADB commands, it works, indicating that the booting is complete.
Some overlay actions like an alarm or phone call might help getting out of the infinite boot screen as I tested.
Make a log guys.
 
Make a log guys.
I flashed back to HO1 enabled adb and flashed HO2 over TWRP.
Here is the log
I waited 10 minutes with the boot logo.
 

Similar threads

  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
45K
Replies
51
Views
48K
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
60K
  • Locked
HyperOS 1.0 24.7.8/12
Replies
50
Views
35K