HyperOS 1.0 23.11.8/13/16


Status
Not open for further replies.
I installed it on my mi 13 ultra phone, but the google package installer does not work. It doesn't let me update either. The bad thing is that I can't intervene because it appears as a system application.
 
The clock on launcher is still old version, HyperOS EU 23.11.8 Xiaomi 13
 

Attachments

  • 1000000046.jpg
    1000000046.jpg
    752.8 KB · Views: 366
Last edited by a moderator:
Hi, thanks for the update!

I've managed to install HyperOS successfully on my Xiaomi 13 Ultra

There's a permanent green dot caused by Home Assistant tracking my location now, the dot persists even in full screen videos.

Is there any way to whitelist some apps from displaying this green dot, or to turn it off for location access altogether?

I've seen some posts pointing to developer settings, but the setting doesn't seem to be there in HyperOS.

Screenshot_2023-11-19-02-28-17-415_com.miui.home-edit.jpg


Screenshot_2023-11-19-02-28-30-679_com.miui.home-edit.jpg


EDIT: I've found this https://xiaomi.eu/community/threads/21-12-1.64111/page-2#post-638920, it worked to show the developer settings toggle, but neither toggle nor the shell command worked to actually hide the dot.

It would be great if there was a possibility to have a per-app whitelist, but even a solution to globally hide the annoying dot would be welcome.

I know it's a security feature, but I'm not going to check what app is getting my location if I have the dot 24/7 anyway.
 
Last edited:
are the warnings and skips normal?
on nuwa
Code:
##################################################################
Setting current slot to 'a'                        OKAY [  0.006s]
Finished. Total time: 0.011s
Warning: skip copying abl_ab image avb footer (abl_ab partition size: 0, abl_ab image size: 233472).
Sending 'abl_ab' (228 KB)                          OKAY [  0.006s]
Writing 'abl_ab'                                   (bootloader) Partition abl_a flashed successfully
(bootloader) Partition abl_b flashed successfully
OKAY [  0.002s]
Finished. Total time: 0.046s
Warning: skip copying aop_ab image avb footer (aop_ab partition size: 0, aop_ab image size: 282624).
Sending 'aop_ab' (276 KB)                          OKAY [  0.008s]
Writing 'aop_ab'                                   (bootloader) Partition aop_a flashed successfully
(bootloader) Partition aop_b flashed successfully
OKAY [  0.003s]
Finished. Total time: 0.045s
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.000s]
Writing 'aop_config_ab'                            (bootloader) Partition aop_config_a flashed successfully
(bootloader) Partition aop_config_b flashed successfully
OKAY [  0.003s]
Finished. Total time: 0.042s
Warning: skip copying bluetooth_ab image avb footer (bluetooth_ab partition size: 0, bluetooth_ab image size: 1257472).
Sending 'bluetooth_ab' (1228 KB)                   OKAY [  0.029s]
Writing 'bluetooth_ab'                             (bootloader) Partition bluetooth_a flashed successfully
(bootloader) Partition bluetooth_b flashed successfully
OKAY [  0.003s]
Finished. Total time: 0.069s
Warning: skip copying cpucp_ab image avb footer (cpucp_ab partition size: 0, cpucp_ab image size: 192512).
Sending 'cpucp_ab' (188 KB)                        OKAY [  0.006s]
Writing 'cpucp_ab'                                 (bootloader) Partition cpucp_a flashed successfully
(bootloader) Partition cpucp_b flashed successfully
OKAY [  0.002s]
Finished. Total time: 0.042s
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.002s]
Writing 'devcfg_ab'                                (bootloader) Partition devcfg_a flashed successfully
(bootloader) Partition devcfg_b flashed successfully
OKAY [  0.003s]
Finished. Total time: 0.044s
Warning: skip copying dsp_ab image avb footer (dsp_ab partition size: 0, dsp_ab image size: 67108864).
Sending 'dsp_ab' (65536 KB)                        OKAY [  1.507s]
Writing 'dsp_ab'                                   (bootloader) Partition dsp_a flashed successfully
(bootloader) Partition dsp_b flashed successfully
OKAY [  0.047s]
Finished. Total time: 1.588s
Warning: skip copying dtbo_ab image avb footer (dtbo_ab partition size: 0, dtbo_ab image size: 16777216).
Sending 'dtbo_ab' (16384 KB)                       OKAY [  0.377s]
Writing 'dtbo_ab'                                  (bootloader) Partition dtbo_a flashed successfully
(bootloader) Partition dtbo_b flashed successfully
OKAY [  0.012s]
Finished. Total time: 0.423s
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.003s]
Writing 'featenabler_ab'                           (bootloader) Partition featenabler_a flashed successfully
(bootloader) Partition featenabler_b flashed successfully
OKAY [  0.006s]
Finished. Total time: 0.047s
Warning: skip copying hyp_ab image avb footer (hyp_ab partition size: 0, hyp_ab image size: 1454080).
Sending 'hyp_ab' (1420 KB)                         OKAY [  0.033s]
Writing 'hyp_ab'                                   (bootloader) Partition hyp_a flashed successfully
(bootloader) Partition hyp_b flashed successfully
OKAY [  0.004s]
Finished. Total time: 0.076s
Warning: skip copying imagefv_ab image avb footer (imagefv_ab partition size: 0, imagefv_ab image size: 6299648).
Sending 'imagefv_ab' (6152 KB)                     OKAY [  0.156s]
Writing 'imagefv_ab'                               (bootloader) Partition imagefv_a flashed successfully
(bootloader) Partition imagefv_b flashed successfully
OKAY [  0.009s]
Finished. Total time: 0.201s
Warning: skip copying keymaster_ab image avb footer (keymaster_ab partition size: 0, keymaster_ab image size: 409600).
Sending 'keymaster_ab' (400 KB)                    OKAY [  0.011s]
Writing 'keymaster_ab'                             (bootloader) Partition keymaster_a flashed successfully
(bootloader) Partition keymaster_b flashed successfully
OKAY [  0.005s]
Finished. Total time: 0.051s
Warning: skip copying modem_ab image avb footer (modem_ab partition size: 0, modem_ab image size: 370028544).
Sending 'modem_ab' (361356 KB)                     OKAY [  8.343s]
Writing 'modem_ab'                                 (bootloader) Partition modem_a flashed successfully
(bootloader) Partition modem_b flashed successfully
OKAY [  0.258s]
Finished. Total time: 8.638s
Warning: skip copying multiimgqti_ab image avb footer (multiimgqti_ab partition size: 0, multiimgqti_ab image size: 12288).
Sending 'multiimgqti_ab' (12 KB)                   OKAY [  0.002s]
Writing 'multiimgqti_ab'                           (bootloader) Partition multiimgqti_a flashed successfully
(bootloader) Partition multiimgqti_b flashed successfully
OKAY [  0.004s]
Finished. Total time: 0.042s
Warning: skip copying qupfw_ab image avb footer (qupfw_ab partition size: 0, qupfw_ab image size: 57344).
Sending 'qupfw_ab' (56 KB)                         OKAY [  0.002s]
Writing 'qupfw_ab'                                 (bootloader) Partition qupfw_a flashed successfully
(bootloader) Partition qupfw_b flashed successfully
OKAY [  0.004s]
Finished. Total time: 0.041s
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.003s]
Writing 'shrm_ab'                                  (bootloader) Partition shrm_a flashed successfully
(bootloader) Partition shrm_b flashed successfully
OKAY [  0.004s]
Finished. Total time: 0.041s
Warning: skip copying tz_ab image avb footer (tz_ab partition size: 0, tz_ab image size: 3948544).
Sending 'tz_ab' (3856 KB)                          OKAY [  0.089s]
Writing 'tz_ab'                                    (bootloader) Partition tz_a flashed successfully
(bootloader) Partition tz_b flashed successfully
OKAY [  0.008s]
Finished. Total time: 0.131s
Warning: skip copying uefi_ab image avb footer (uefi_ab partition size: 0, uefi_ab image size: 2945024).
Sending 'uefi_ab' (2876 KB)                        OKAY [  0.068s]
Writing 'uefi_ab'                                  (bootloader) Partition uefi_a flashed successfully
(bootloader) Partition uefi_b flashed successfully
OKAY [  0.006s]
Finished. Total time: 0.109s
Warning: skip copying uefisecapp_ab image avb footer (uefisecapp_ab partition size: 0, uefisecapp_ab image size: 180224).
Sending 'uefisecapp_ab' (176 KB)                   OKAY [  0.005s]
Writing 'uefisecapp_ab'                            (bootloader) Partition uefisecapp_a flashed successfully
(bootloader) Partition uefisecapp_b flashed successfully
OKAY [  0.004s]
Finished. Total time: 0.046s
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.002s]
Writing 'vbmeta_ab'                                (bootloader) Partition vbmeta_a flashed successfully
(bootloader) Partition vbmeta_b flashed successfully
OKAY [  0.005s]
Finished. Total time: 0.044s
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.001s]
Writing 'vbmeta_system_ab'                         (bootloader) Partition vbmeta_system_a flashed successfully
(bootloader) Partition vbmeta_system_b flashed successfully
OKAY [  0.004s]
Finished. Total time: 0.044s
Warning: skip copying xbl_ab image avb footer (xbl_ab partition size: 0, xbl_ab image size: 1200128).
Sending 'xbl_ab' (1172 KB)                         OKAY [  0.028s]
Writing 'xbl_ab'                                   (bootloader) Partition xbl_a flashed successfully
(bootloader) Partition xbl_b flashed successfully
OKAY [  0.008s]
Finished. Total time: 0.072s
Warning: skip copying xbl_config_ab image avb footer (xbl_config_ab partition size: 0, xbl_config_ab image size: 188416).
Sending 'xbl_config_ab' (184 KB)                   OKAY [  0.005s]
Writing 'xbl_config_ab'                            (bootloader) Partition xbl_config_a flashed successfully
(bootloader) Partition xbl_config_b flashed successfully
OKAY [  0.005s]
Finished. Total time: 0.047s
Warning: skip copying xbl_ramdump_ab image avb footer (xbl_ramdump_ab partition size: 0, xbl_ramdump_ab image size: 860160).
Sending 'xbl_ramdump_ab' (840 KB)                  OKAY [  0.020s]
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.065s
Warning: skip copying boot_ab image avb footer (boot_ab partition size: 0, boot_ab image size: 100663296).
Sending 'boot_ab' (98304 KB)                       OKAY [  2.266s]
Writing 'boot_ab'                                  (bootloader) Partition boot_a flashed successfully
(bootloader) Partition boot_b flashed successfully
OKAY [  0.072s]
Finished. Total time: 2.376s
Warning: skip copying init_boot_ab image avb footer (init_boot_ab partition size: 0, init_boot_ab image size: 8388608).
Sending 'init_boot_ab' (8192 KB)                   OKAY [  0.189s]
Writing 'init_boot_ab'                             (bootloader) Partition init_boot_a flashed successfully
(bootloader) Partition init_boot_b flashed successfully
OKAY [  0.016s]
Finished. Total time: 0.245s
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 [  2.260s]
Writing 'vendor_boot_ab'                           (bootloader) Partition vendor_boot_a flashed successfully
(bootloader) Partition vendor_boot_b flashed successfully
OKAY [  0.066s]
Finished. Total time: 2.362s
Sending 'cust' (4 KB)                              OKAY [  0.002s]
Writing 'cust'                                     OKAY [  0.002s]
 
Hello ingbrzy,
the ROM works very well and very fluid on Xiaomi 14 Pro (Shennong). But I see that you have not included a very useful function to protect the battery, and that it does have the original Chinese ROM.
I was in Settings/battery/Battery protection/
It was a button to prevent it from charging to more than 80%, designed to protect the battery when connected to a vehicle on a long trip. Or simply to prevent it from charging more than 80%, significantly extending the life of the battery. It was under the "Nighttime protection" button that you included.
If possible, it would be interesting if you included this button in future updates.
I am very grateful to the entire team for your excellent work.
 
  • Like
Reactions: ingbrzy
POCO F5 Pro
My English is not very good
Is it because I didn’t format the phone?



QQ图片20231119125818.jpg
QQ图片20231119130233.jpg


Still prompts that there is a system update



QQ图片20231119130332.jpg



Abnormality in AOD setting interface
QQ图片20231119130337.jpg
QQ图片20231119130342.jpg



The weather is not displayed
 
You need to read first and second post.
Thanks I figured it out. I was just confused that the android and operating system were new, and I thought that I needed to erase the data. and everything works fine. The only thing in the settings that says update is the firmware version. thank you so much for your work.
 
Thank you for your reply. The problem has been solved, but I forgot to mention one thing. The notification bar icon is also abnormal.
 
Problem fixed, just uninstall the google pay app and go to setting-google-leftbottom coner there will be a function said add payment card. Just link your card and setup google pay there
Thanks. That's a strange behaviour. I uninstalled Google wallet and as you said I can still access it from Google settings. Added my cards successfully, so I need to test it today if payments are working this way. Strange thing is I have 1 specific card that I cannot add with the message that it cannot be used for contactless payments. This card used to work on miui 14 A13. Oh well

Sent from my 2210132G using Tapatalk
 
Notification center is much better now, and every time I use it is superb.

Also new guy here, I willing to share my experience using EU rom.
and Thank you for delivering to us this milestone.

Device: Poco F5 Pro
Place: Somewhere in Sound East Asia
 

Attachments

  • Screenshot_2023-11-19-14-05-50-829_com.miui.home.jpg
    Screenshot_2023-11-19-14-05-50-829_com.miui.home.jpg
    765.1 KB · Views: 247
Just got my Xiaomi14 unlocked (paid service is the only way for now) and flashed the Xiaomi EU ROM. Currently in the process of restoring a backup. :)

Thank you devs for your fast work!
 
  • Like
Reactions: 4fun20
Installed on 13 Pro (nuwa). Works legit so far.
I only cant get rid of that "Update available" text on the settings screen. After clicking on it, it says you already have the newest version.

Is that cause I installed this weekly through TWRP and not Fastboot?
Should I Install it again through Fastboot?

Thx devs for your work
 

Attachments

  • Screenshot_2023-11-19-08-14-35-479_com.android.settings.jpg
    Screenshot_2023-11-19-08-14-35-479_com.android.settings.jpg
    263.7 KB · Views: 187
  • Screenshot_2023-11-19-08-14-43-728_com.android.updater.jpg
    Screenshot_2023-11-19-08-14-43-728_com.android.updater.jpg
    218.2 KB · Views: 234
I installed HyperOS with fastboot as update over the weekly Rom on my 13 Ultra. Works fantastic! Very fluid. So far I did not find any problem. Geekbench is almost 10% faster. Google wallet works again. Battery life seems better than before. Congratulations developers! Good job! Enjoy a beer transactioncode 27D14668VP441531R.
 
  • Like
Reactions: NXTwoThou and rasne
Hello everyone
installation ok on Xiaomi 13.
On the other hand, no change to the calendar apk and no change to the icons either as expected!
Small problem also in the notification bar, the icons all remain grayed out
 
Last edited:
Tradingshenzhen is a China Shop
Hello, I placed an order a week ago for a 13 Ultra on tradingsgenzen with firmware xiaomi.eu unlocked, does this mean that it comes with unlocked bootloader too? Will upgrading to HyperOS be possible with nothing else to do from my part?

I used iPhones my entire life so if I sound like a complete idiot, is because I am. In preparing for my Xiaomi adventure, I’m trying to understand at least the basics but so far everything is overwhelming and quite confusing. Also, I apologise in advance if asking here breaks the rules. Regards.
 
So to whoever have tried hyperOS, is there any significant pros over miui 14 or just a 'face lift' ? (Fuxi device)
 
Status
Not open for further replies.

Similar threads

Replies
51
Views
36K
  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
41K
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
38K
  • Locked
HyperOS 1.0 24.7.8/12
Replies
50
Views
32K