HyperOS 2.0 HyperOS 2.0 STABLE RELEASE
- Thread starter ingbrzy
- Start date
ekzeshka
Members
- 5 Jul 2022
- 157
- 40
Pretty annoying bug with everything going black for a second when maximizing any app. Hos2 poco f5
drive.google.com
Edit: nvm, it was caused by navtweaks module
Screenrecorder-2025-03-28-21-39-22-457.mp4
drive.google.com
Edit: nvm, it was caused by navtweaks module
dennys.sobrinho
Members
- 17 Nov 2011
- 95
- 30
Someone who has the latest version 'xiaomi.eu_ZEUS_OS2.0.6.0.VLBCNXM_15.zip' on another server, could you share the link with me (private message) ?
Today, the SourceForge.net website is extremely slow here in Brazil.
Today, the SourceForge.net website is extremely slow here in Brazil.
gogocar62
XM12 Tester
- 22 Apr 2021
- 5,258
- 322
Successfully upgraded on DITING from previous Stable HyperOS 1. So far so good, the only thing I miss from HyperOS 1 is the ability to disable the Xiaomi command center thing (The notifications\settings tab). On HyperOS 1 I it disabled.
Edit: Looked around the thread and apparently this has been a topic before. But this feature is not coming back. It's a shame, but it is what it is.
Edit: Looked around the thread and apparently this has been a topic before. But this feature is not coming back. It's a shame, but it is what it is.
Last edited:
Iain_B
Members
- 25 Mar 2013
- 1,911
- 297
For what it's worth, my experiences with the Nuwa update:
I did the normal upgrade through recovery. It seemed to go OK, but when I did a second reboot, the scale on my custom widgets (KWGT) became about 25% larger. And as I was also having 'problems' with the power button, I thought that I would revert to the 103. All widgets then became grey blocks.
So, I thought that I would go back to the 106. I could not get back through the recovery security to unlock the phone with my unlock gesture to re-install the 106. Fortunately I had done my back-up before I did the upgrade. As the hold-down power options didn't appear, I thought that things were really messed up.
I then extracted the 106 zip file on my computer and did a fastboot upgrade install. It's such a long time since I had done that that I had almost forgotten how to do it! Anyway, the upgrade went OK. I got back into the phone. I have now reduced the scale of my Kustom widgets by about 25%, and now all seems to be working fine, and I have changed the 'Power off or reboot' setting to what it was previously.
I did the normal upgrade through recovery. It seemed to go OK, but when I did a second reboot, the scale on my custom widgets (KWGT) became about 25% larger. And as I was also having 'problems' with the power button, I thought that I would revert to the 103. All widgets then became grey blocks.
So, I thought that I would go back to the 106. I could not get back through the recovery security to unlock the phone with my unlock gesture to re-install the 106. Fortunately I had done my back-up before I did the upgrade. As the hold-down power options didn't appear, I thought that things were really messed up.
I then extracted the 106 zip file on my computer and did a fastboot upgrade install. It's such a long time since I had done that that I had almost forgotten how to do it! Anyway, the upgrade went OK. I got back into the phone. I have now reduced the scale of my Kustom widgets by about 25%, and now all seems to be working fine, and I have changed the 'Power off or reboot' setting to what it was previously.
why after every reboot, i am able to see launcher and launch the apps for a bit before the lockscreen tells me to enter pin since for reboot then fp.
I suppose this is a privacy risk we are able to bypass the lockscreen.
device: marble charge 1%
I suppose this is a privacy risk we are able to bypass the lockscreen.
device: marble charge 1%
Power button on fuxi start no menu or Gemini.
Damn, my phone doesn't even support this ROM and I already know what is it and how to "fix" it. Why is it so hard for people to read or search?
Is anyone else not being able to download HyperOS 2 because of high download time (only happens with this version) (I am trying to download the Poco F5 rom).
Iain_B
Members
- 25 Mar 2013
- 1,911
- 297
In addition to the Kustom widgets noted before, NONE of the widgets are updating at all or functioning properly. This includes, for instance, Xiaomi's own widgets, eg. steps widget, as well as weather, eg Met Office.
Edit: I've just done another reboot, and they all seem to be working again.
Edit: I've just done another reboot, and they all seem to be working again.
Iain_B
Members
- 25 Mar 2013
- 1,911
- 297
As reported previously, if you go to: Settings / Additional settings / Gesture shortcuts / Power off or reboot, you have the options there. Selecting the right-hand option (Press and hold the Power button for 3s) gives the previous power menu with the power button.
Just updated my Poco F5 everything working fine. Thanks to the developers.
So I assume now when I'm on my home screen the clock on the status bar will always be shown and not be hidden like it was on HyperOS 1.
So I assume now when I'm on my home screen the clock on the status bar will always be shown and not be hidden like it was on HyperOS 1.
Hi, I have installed HyperOS 2.0 (xiaomi.eu_STAR_2.0.1.0.UKACNXM_14) on my Mi 11 Ultra. HyperOS 1.0 was installed before.
After rebooting, the phone remains in fastboot mode, which cannot be canceled despite 3 different methods.
Is there any way to recover or is the Mi 11 Ultra now unusable?
After rebooting, the phone remains in fastboot mode, which cannot be canceled despite 3 different methods.
Is there any way to recover or is the Mi 11 Ultra now unusable?
Just flash the previous version because the HOS2 Version is buggy and not bootable.
I can no longer access the Mi 11 Ultra. It remains permanently in fastboot mode.
Kameleon1987
Members
- 21 May 2023
- 2
- 15
For people who are missing the power menu, press and hold the volume up and power button for a few seconds.
These settings can be changed in Settings -> Additional settings -> Gesture shortcuts -> Power off or reboot
These settings can be changed in Settings -> Additional settings -> Gesture shortcuts -> Power off or reboot
I've been stuck for more than 30 minutes as of right now while flashing xiaomi.eu_THOR_OS2.0.10.0.VLACNXM_15. Can I cancel it and flash back the previous one without losing my data?
Code:
Waiting for device...
Your device: thor
Your device will be flashed without formatting the data partition.
You will keep your apps, settings and files on internal storage.
Continue if you are upgrading from an older Xiaomi.eu ROM.
Do you want to continue? [y/N] y
##############################################################
Please wait. The device will reboot once flashing is complete.
##############################################################
Setting current slot to 'a' OKAY [ 0.010s]
Finished. Total time: 0.016s
Warning: skip copying abl_ab image avb footer (abl_ab partition size: 0, abl_ab image size: 204800).
Sending 'abl_ab' (200 KB) OKAY [ 0.182s]
Writing 'abl_ab' (bootloader) Partition abl_a flashed successfully
(bootloader) Partition abl_b flashed successfully
OKAY [ 0.006s]
Finished. Total time: 0.309s
Warning: skip copying aop_ab image avb footer (aop_ab partition size: 0, aop_ab image size: 237568).
Sending 'aop_ab' (232 KB) OKAY [ 0.205s]
Writing 'aop_ab' (bootloader) Partition aop_a flashed successfully
(bootloader) Partition aop_b flashed successfully
OKAY [ 0.004s]
Finished. Total time: 0.276s
Warning: skip copying aop_config_ab image avb footer (aop_config_ab partition size: 0, aop_config_ab image size: 16384).
Sending 'aop_config_ab' (16 KB) OKAY [ 0.016s]
Writing 'aop_config_ab' (bootloader) Partition aop_config_a flashed successfully
(bootloader) Partition aop_config_b flashed successfully
OKAY [ 0.006s]
Finished. Total time: 0.067s
Warning: skip copying bluetooth_ab image avb footer (bluetooth_ab partition size: 0, bluetooth_ab image size: 2240512).
Sending 'bluetooth_ab' (2188 KB) OKAY [ 1.874s]
Writing 'bluetooth_ab' (bootloader) Partition bluetooth_a flashed successfully
(bootloader) Partition bluetooth_b flashed successfully
OKAY [ 0.010s]
Finished. Total time: 1.932s
Warning: skip copying cpucp_ab image avb footer (cpucp_ab partition size: 0, cpucp_ab image size: 159744).
Sending 'cpucp_ab' (156 KB) OKAY [ 0.139s]
Writing 'cpucp_ab' (bootloader) Partition cpucp_a flashed successfully
(bootloader) Partition cpucp_b flashed successfully
OKAY [ 0.006s]
Finished. Total time: 0.195s
Warning: skip copying devcfg_ab image avb footer (devcfg_ab partition size: 0, devcfg_ab image size: 57344).
Sending 'devcfg_ab' (56 KB) OKAY [ 0.051s]
Writing 'devcfg_ab' (bootloader) Partition devcfg_a flashed successfully
(bootloader) Partition devcfg_b flashed successfully
OKAY [ 0.005s]
Finished. Total time: 0.235s
Warning: skip copying dsp_ab image avb footer (dsp_ab partition size: 0, dsp_ab image size: 67108864).
Sending 'dsp_ab' (65536 KB) OKAY [ 56.332s]
Writing 'dsp_ab' (bootloader) Partition dsp_a flashed successfully
(bootloader) Partition dsp_b flashed successfully
OKAY [ 0.143s]
Finished. Total time: 56.523s
Warning: skip copying dtbo_ab image avb footer (dtbo_ab partition size: 0, dtbo_ab image size: 24117248).
Sending 'dtbo_ab' (23552 KB) OKAY [ 19.945s]
Writing 'dtbo_ab' (bootloader) Partition dtbo_a flashed successfully
(bootloader) Partition dtbo_b flashed successfully
OKAY [ 0.038s]
Finished. Total time: 20.032s
Warning: skip copying featenabler_ab image avb footer (featenabler_ab partition size: 0, featenabler_ab image size: 98304).
Sending 'featenabler_ab' (96 KB) OKAY [ 0.087s]
Writing 'featenabler_ab' (bootloader) Partition featenabler_a flashed successfully
(bootloader) Partition featenabler_b flashed successfully
OKAY [ 0.007s]
Finished. Total time: 0.153s
Warning: skip copying hyp_ab image avb footer (hyp_ab partition size: 0, hyp_ab image size: 1257472).
Sending 'hyp_ab' (1228 KB) OKAY [ 1.075s]
Writing 'hyp_ab' (bootloader) Partition hyp_a flashed successfully
(bootloader) Partition hyp_b flashed successfully
OKAY [ 0.009s]
Finished. Total time: 1.183s
Warning: skip copying imagefv_ab image avb footer (imagefv_ab partition size: 0, imagefv_ab image size: 6299648).
Sending 'imagefv_ab' (6152 KB) OKAY [ 6.127s]
Writing 'imagefv_ab' (bootloader) Partition imagefv_a flashed successfully
(bootloader) Partition imagefv_b flashed successfully
OKAY [ 0.013s]
Finished. Total time: 6.195s
Warning: skip copying keymaster_ab image avb footer (keymaster_ab partition size: 0, keymaster_ab image size: 368640).
Sending 'keymaster_ab' (360 KB) OKAY [ 0.319s]
Writing 'keymaster_ab' (bootloader) Partition keymaster_a flashed successfully
(bootloader) Partition keymaster_b flashed successfully
OKAY [ 0.006s]
Finished. Total time: 0.385s
Warning: skip copying modem_ab image avb footer (modem_ab partition size: 0, modem_ab image size: 293556224).
Sending 'modem_ab' (286676 KB) OKAY [247.592s]
Writing 'modem_ab' (bootloader) Partition modem_a flashed successfully
(bootloader) Partition modem_b flashed successfully
OKAY [ 0.386s]
Finished. Total time: 248.027s
Warning: skip copying qupfw_ab image avb footer (qupfw_ab partition size: 0, qupfw_ab image size: 53248).
Sending 'qupfw_ab' (52 KB) OKAY [ 0.049s]
Writing 'qupfw_ab' (bootloader) Partition qupfw_a flashed successfully
(bootloader) Partition qupfw_b flashed successfully
OKAY [ 0.007s]
Finished. Total time: 0.127s
Warning: skip copying shrm_ab image avb footer (shrm_ab partition size: 0, shrm_ab image size: 65536).
Sending 'shrm_ab' (64 KB) OKAY [ 0.058s]
Writing 'shrm_ab' (bootloader) Partition shrm_a flashed successfully
(bootloader) Partition shrm_b flashed successfully
OKAY [ 0.007s]
Finished. Total time: 0.111s
Warning: skip copying tz_ab image avb footer (tz_ab partition size: 0, tz_ab image size: 3911680).
Sending 'tz_ab' (3820 KB) OKAY [ 3.321s]
Writing 'tz_ab' (bootloader) Partition tz_a flashed successfully
(bootloader) Partition tz_b flashed successfully
OKAY [ 0.010s]
Finished. Total time: 3.418s
Warning: skip copying uefi_ab image avb footer (uefi_ab partition size: 0, uefi_ab image size: 2760704).
Sending 'uefi_ab' (2696 KB) OKAY [ 2.399s]
Writing 'uefi_ab' (bootloader) Partition uefi_a flashed successfully
(bootloader) Partition uefi_b flashed successfully
OKAY [ 0.007s]
Finished. Total time: 2.463s
Warning: skip copying uefisecapp_ab image avb footer (uefisecapp_ab partition size: 0, uefisecapp_ab image size: 172032).
Sending 'uefisecapp_ab' (168 KB) OKAY [ 0.148s]
Writing 'uefisecapp_ab' (bootloader) Partition uefisecapp_a flashed successfully
(bootloader) Partition uefisecapp_b flashed successfully
OKAY [ 0.005s]
Finished. Total time: 0.208s
Warning: skip copying vbmeta_ab image avb footer (vbmeta_ab partition size: 0, vbmeta_ab image size: 8192).
Sending 'vbmeta_ab' (8 KB) OKAY [ 0.010s]
Writing 'vbmeta_ab' (bootloader) Partition vbmeta_a flashed successfully
(bootloader) Partition vbmeta_b flashed successfully
OKAY [ 0.006s]
Finished. Total time: 0.063s
Warning: skip copying vbmeta_system_ab image avb footer (vbmeta_system_ab partition size: 0, vbmeta_system_ab image size: 4096).
Sending 'vbmeta_system_ab' (4 KB) OKAY [ 0.006s]
Writing 'vbmeta_system_ab' (bootloader) Partition vbmeta_system_a flashed successfully
(bootloader) Partition vbmeta_system_b flashed successfully
OKAY [ 0.005s]
Finished. Total time: 0.061s
Warning: skip copying vm-bootsys_ab image avb footer (vm-bootsys_ab partition size: 0, vm-bootsys_ab image size: 269996032).
Sending 'vm-bootsys_ab' (263668 KB) OKAY [224.806s]
Writing 'vm-bootsys_ab' (bootloader) Partition vm-bootsys_a flashed successfully
(bootloader) Partition vm-bootsys_b flashed successfully
OKAY [ 0.359s]
Finished. Total time: 225.215s
Warning: skip copying xbl_ab image avb footer (xbl_ab partition size: 0, xbl_ab image size: 1093632).
Sending 'xbl_ab' (1068 KB) OKAY [ 0.938s]
Writing 'xbl_ab' (bootloader) Partition xbl_a flashed successfully
(bootloader) Partition xbl_b flashed successfully
OKAY [ 0.010s]
Finished. Total time: 1.001s
Warning: skip copying xbl_config_ab image avb footer (xbl_config_ab partition size: 0, xbl_config_ab image size: 114688).
Sending 'xbl_config_ab' (112 KB) OKAY [ 0.098s]
Writing 'xbl_config_ab' (bootloader) Partition xbl_config_a flashed successfully
(bootloader) Partition xbl_config_b flashed successfully
OKAY [ 0.010s]
Finished. Total time: 0.162s
Warning: skip copying xbl_ramdump_ab image avb footer (xbl_ramdump_ab partition size: 0, xbl_ramdump_ab image size: 872448).
Sending 'xbl_ramdump_ab' (852 KB) OKAY [ 0.749s]
Writing 'xbl_ramdump_ab' (bootloader) Partition xbl_ramdump_a flashed successfully
(bootloader) Partition xbl_ramdump_b flashed successfully
OKAY [ 0.007s]
Finished. Total time: 0.807s
Warning: skip copying boot_ab image avb footer (boot_ab partition size: 0, boot_ab image size: 201326592).
Sending 'boot_ab' (196608 KB) OKAY [168.240s]
Writing 'boot_ab' (bootloader) Partition boot_a flashed successfully
(bootloader) Partition boot_b flashed successfully
OKAY [ 0.273s]
Finished. Total time: 168.618s
Warning: skip copying vendor_boot_ab image avb footer (vendor_boot_ab partition size: 0, vendor_boot_ab image size: 100663296).
Sending 'vendor_boot_ab' (98304 KB) OKAY [ 83.638s]
Writing 'vendor_boot_ab' (bootloader) Partition vendor_boot_a flashed successfully
(bootloader) Partition vendor_boot_b flashed successfully
OKAY [ 0.136s]
Finished. Total time: 83.825s
Warning: skip copying cust image avb footer due to sparse image.
Sending 'cust' (84 KB) OKAY [ 0.074s]
Writing 'cust' OKAY [ 0.004s]
Finished. Total time: 0.143s
Warning: skip copying super image avb footer due to sparse image.
Sending 'super' (722520 KB) OKAY [637.461s]
Writing 'super' OKAY [ 0.009s]
Finished. Total time: 637.504s
Warning: skip copying super image avb footer due to sparse image.
Sending 'super' (720896 KB) OKAY [639.015s]
Writing 'super' OKAY [ 0.004s]
Finished. Total time: 640.327s
Warning: skip copying super image avb footer due to sparse image.
Sending 'super' (720896 KB) OKAY [633.327s]
Writing 'super' OKAY [ 0.012s]@altcelalalt You can just try to start the script again and maybe try a different usb cable and or usb hub.
