HyperOS 1.0 23.12.4/9


Status
Not open for further replies.
Can i go back if i don't satisfied it?
Anybody try it for Cupid? Are there any bug for it?
So far so good except the PubG game because there is jumping but I think it's mistake of android 14, if it's not optimised for this game yet.
 
Last edited:
I just opened the weather app, and it now is the default weather app available in the play store... can someone send the the hyperos weather app apk so I can install it and unlink it from the play store
 
NOT good by now...

1. Still Google Play Developer Services are crushed over and over again
2. Google Play app was failed again and again
- while Data and Clash clear. it start "Google Play" migration? that I saw first time starts but never end
3. Some apps using internet services incl. Chrome mail app etc cannot open
4. Cleared cache from Chrome but nothing has changed, it cannot be update cuz cannot use Google Play and Internet (Blowser)
- If I should update these apps with apk, please let me know, I will import these files somehow

So I cannot use Internet and G.Play, the fact of the matter is, I'm in over my heads...
Dear Developers and leaders,

Still be notified of a series of crash reports...
1) "Google Developer Services"
2) "Google Play"
3) "Xiaomi Account"
4) Chrome and web services cannot access internet (Bing can access Internet well!)

Will I have to make the decision to do a clean install...?
 
Dear Developers and leaders,

Still be notified of a series of crash reports...
1) "Google Developer Services"
2) "Google Play"
3) "Xiaomi Account"
4) Chrome and web services cannot access internet (Bing can access Internet well!)

Will I have to make the decision to do a clean install...?
Clear the app cache and data for the apps. Maybe you did the adb commands mentioned in second post?

Gesendet von meinem 2210132G mit Tapatalk
 
I can flash the ROM successfully and it runs very well, but I always get a few error codes when flashing it via Fastbooot. I have already tried different cables and USB ports. Unfortunately without success. I didn't see any errors when flashing MIUI.
Code:
Microsoft Windows [Version 10.0.22635.2850]
(c) Microsoft Corporation. Alle Rechte vorbehalten.

C:\Users\Stefan\Downloads\Xiaomi F5 Pro\xiaomi.eu_multi_MONDRIAN_OS1.0.23.12.4.DEV_os1-14>"C:\Users\Stefan\Downloads\Xiaomi F5 Pro\xiaomi.eu_multi_MONDRIAN_OS1.0.23.12.4.DEV_os1-14\windows_fastboot_update_rom.bat"
Waiting for device...
##################################################################
Please wait. The device will reboot when installation is finished.
##################################################################
Setting current slot to 'a'                        OKAY [  0.008s]
Finished. Total time: 0.019s
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.003s]
Writing 'abl_ab'                                   (bootloader) Partition abl_a flashed successfully
(bootloader) Partition abl_b flashed successfully
OKAY [  0.008s]
Finished. Total time: 0.045s
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.002s]
Writing 'aop_ab'                                   (bootloader) Partition aop_a flashed successfully
(bootloader) Partition aop_b flashed successfully
OKAY [  0.000s]
Finished. Total time: 0.061s
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.007s]
Finished. Total time: 0.056s
Warning: skip copying bluetooth_ab image avb footer (bluetooth_ab partition size: 0, bluetooth_ab image size: 2240512).
Sending 'bluetooth_ab' (2188 KB)                   OKAY [  0.045s]
Writing 'bluetooth_ab'                             (bootloader) Partition bluetooth_a flashed successfully
(bootloader) Partition bluetooth_b flashed successfully
OKAY [  0.009s]
Finished. Total time: 0.103s
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.000s]
Writing 'cpucp_ab'                                 (bootloader) Partition cpucp_a flashed successfully
(bootloader) Partition cpucp_b flashed successfully
OKAY [  0.010s]
Finished. Total time: 0.053s
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.007s]
Writing 'devcfg_ab'                                (bootloader) Partition devcfg_a flashed successfully
(bootloader) Partition devcfg_b flashed successfully
OKAY [  0.003s]
Finished. Total time: 0.046s
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.599s]
Writing 'dsp_ab'                                   (bootloader) Partition dsp_a flashed successfully
(bootloader) Partition dsp_b flashed successfully
OKAY [  0.140s]
Finished. Total time: 1.788s
Warning: skip copying dtbo_ab image avb footer (dtbo_ab partition size: 0, dtbo_ab image size: 24117248).
Sending 'dtbo_ab' (23552 KB)                       OKAY [  0.573s]
Writing 'dtbo_ab'                                  (bootloader) Partition dtbo_a flashed successfully
(bootloader) Partition dtbo_b flashed successfully
OKAY [  0.071s]
Finished. Total time: 0.698s
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.000s]
Writing 'featenabler_ab'                           (bootloader) Partition featenabler_a flashed successfully
(bootloader) Partition featenabler_b flashed successfully
OKAY [  0.013s]
Finished. Total time: 0.055s
Warning: skip copying hyp_ab image avb footer (hyp_ab partition size: 0, hyp_ab image size: 1257472).
Sending 'hyp_ab' (1228 KB)                         OKAY [  0.035s]
Writing 'hyp_ab'                                   (bootloader) Partition hyp_a flashed successfully
(bootloader) Partition hyp_b flashed successfully
OKAY [  0.013s]
Finished. Total time: 0.084s
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.174s]
Writing 'imagefv_ab'                               (bootloader) Partition imagefv_a flashed successfully
(bootloader) Partition imagefv_b flashed successfully
OKAY [  0.094s]
Finished. Total time: 0.295s
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.000s]
Writing 'keymaster_ab'                             (bootloader) Partition keymaster_a flashed successfully
(bootloader) Partition keymaster_b flashed successfully
OKAY [  0.002s]
Finished. Total time: 0.063s
Warning: skip copying modem_ab image avb footer (modem_ab partition size: 0, modem_ab image size: 289148928).
Sending 'modem_ab' (282372 KB)                     OKAY [  6.550s]
Writing 'modem_ab'                                 (bootloader) Partition modem_a flashed successfully
(bootloader) Partition modem_b flashed successfully
OKAY [  1.468s]
Finished. Total time: 8.070s
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.000s]
Writing 'qupfw_ab'                                 (bootloader) Partition qupfw_a flashed successfully
(bootloader) Partition qupfw_b flashed successfully
OKAY [  0.000s]
Finished. Total time: 0.030s
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.000s]
Writing 'shrm_ab'                                  (bootloader) Partition shrm_a flashed successfully
(bootloader) Partition shrm_b flashed successfully
OKAY [  0.017s]
Finished. Total time: 0.047s
Warning: skip copying tz_ab image avb footer (tz_ab partition size: 0, tz_ab image size: 3911680).
Sending 'tz_ab' (3820 KB)                          OKAY [  0.082s]
Writing 'tz_ab'                                    (bootloader) Partition tz_a flashed successfully
(bootloader) Partition tz_b flashed successfully
OKAY [  0.013s]
Finished. Total time: 0.135s
Warning: skip copying uefi_ab image avb footer (uefi_ab partition size: 0, uefi_ab image size: 2760704).
Sending 'uefi_ab' (2696 KB)                        OKAY [  0.066s]
Writing 'uefi_ab'                                  (bootloader) Partition uefi_a flashed successfully
(bootloader) Partition uefi_b flashed successfully
OKAY [  0.012s]
Finished. Total time: 0.108s
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.000s]
Writing 'uefisecapp_ab'                            (bootloader) Partition uefisecapp_a flashed successfully
(bootloader) Partition uefisecapp_b flashed successfully
OKAY [  0.002s]
Finished. Total time: 0.062s
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.000s]
Writing 'vbmeta_ab'                                (bootloader) Partition vbmeta_a flashed successfully
(bootloader) Partition vbmeta_b flashed successfully
OKAY [  0.000s]
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.000s]
Writing 'vbmeta_system_ab'                         (bootloader) Partition vbmeta_system_a flashed successfully
(bootloader) Partition vbmeta_system_b flashed successfully
OKAY [  0.001s]
Finished. Total time: 0.041s
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 [  5.648s]
Writing 'vm-bootsys_ab'                            (bootloader) Partition vm-bootsys_a flashed successfully
(bootloader) Partition vm-bootsys_b flashed successfully
OKAY [  1.122s]
Finished. Total time: 6.824s
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.026s]
Writing 'xbl_ab'                                   (bootloader) Partition xbl_a flashed successfully
(bootloader) Partition xbl_b flashed successfully
OKAY [  0.004s]
Finished. Total time: 0.071s
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.014s]
Writing 'xbl_config_ab'                            (bootloader) Partition xbl_config_a flashed successfully
(bootloader) Partition xbl_config_b flashed successfully
OKAY [  0.000s]
Finished. Total time: 0.045s
Warning: skip copying xbl_ramdump_ab image avb footer (xbl_ramdump_ab partition size: 0, xbl_ramdump_ab image size: 868352).
Sending 'xbl_ramdump_ab' (848 KB)                  OKAY [  0.016s]
Writing 'xbl_ramdump_ab'                           (bootloader) Partition xbl_ramdump_a flashed successfully
(bootloader) Partition xbl_ramdump_b flashed successfully
OKAY [  0.016s]
Finished. Total time: 0.079s
Warning: skip copying boot_ab image avb footer (boot_ab partition size: 0, boot_ab image size: 201326592).
Sending 'boot_ab' (196608 KB)                      OKAY [  4.448s]
Writing 'boot_ab'                                  (bootloader) Partition boot_a flashed successfully
(bootloader) Partition boot_b flashed successfully
OKAY [  0.692s]
Finished. Total time: 5.188s
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.102s]
Writing 'vendor_boot_ab'                           (bootloader) Partition vendor_boot_a flashed successfully
(bootloader) Partition vendor_boot_b flashed successfully
OKAY [  0.371s]
Finished. Total time: 2.536s
Sending 'cust' (4 KB)                              OKAY [  0.002s]
Writing 'cust'                                     OKAY [  0.001s]
Finished. Total time: 0.040s
Sending 'super' (466992 KB)                        OKAY [ 10.071s]
Writing 'super'                                    OKAY [  0.003s]
Finished. Total time: 10.998s
Sending 'super' (458752 KB)                        OKAY [  9.905s]
Writing 'super'                                    OKAY [  0.002s]
Finished. Total time: 12.522s
Sending 'super' (458752 KB)                        OKAY [ 10.216s]
Writing 'super'                                    OKAY [  0.009s]
Finished. Total time: 12.884s
Sending 'super' (458752 KB)                        OKAY [ 10.154s]
Writing 'super'                                    OKAY [  0.005s]
Finished. Total time: 13.265s
Sending 'super' (458752 KB)                        OKAY [ 10.328s]
Writing 'super'                                    OKAY [  0.006s]
Finished. Total time: 12.584s
Sending 'super' (458752 KB)                        OKAY [ 10.224s]
Writing 'super'                                    OKAY [  0.005s]
Finished. Total time: 12.527s
Sending 'super' (458752 KB)                        OKAY [ 10.216s]
Writing 'super'                                    OKAY [  0.008s]
Finished. Total time: 19.354s
Sending 'super' (521564 KB)                        OKAY [ 11.781s]
Writing 'super'                                    OKAY [  0.004s]
Finished. Total time: 14.162s
Sending 'super' (514744 KB)                        OKAY [ 11.415s]
Writing 'super'                                    OKAY [  0.003s]
Finished. Total time: 14.595s
Sending 'super' (514184 KB)                        OKAY [ 11.685s]
Writing 'super'                                    OKAY [  0.002s]
Finished. Total time: 14.379s
Sending 'super' (464068 KB)                        OKAY [ 10.727s]
Writing 'super'                                    OKAY [  0.006s]
Finished. Total time: 13.398s
Sending 'super' (458752 KB)                        OKAY [ 10.391s]
Writing 'super'                                    OKAY [  0.002s]
Finished. Total time: 18.918s
Sending 'super' (369600 KB)                        OKAY [  8.375s]
Writing 'super'                                    OKAY [  0.005s]
Finished. Total time: 10.685s
Rebooting                                          OKAY [  0.107s]
Finished. Total time: 0.114s

C:\Users\Stefan\Downloads\Xiaomi F5 Pro\xiaomi.eu_multi_MONDRIAN_OS1.0.23.12.4.DEV_os1-14>0
there are no errors..
 
I always flash TWRP, after flashing ROM, as it is overwritten by stock recovery.
About decryption... It just works.
when i go on windows to explorer, it shows me my phone but without data . also on my phone i did not get the information to change to data transfer
 
Clear the app cache and data for the apps. Maybe you did the adb commands mentioned in second post?

Gesendet von meinem 2210132G mit Tapatalk
Thanks for your reply,

1. Year, I did clear caches over and over again
2. As I told in my 1st report, I try adb command but adb command might not been succeed, system told "daemon started successfully / error: device not found"

Off course, Rebooted phone after cleaning app caches sometimes but nothing has changed. lol
 
Thanks for your reply,

1. Year, I did clear caches over and over again
2. As I told in my 1st report, I try adb command but adb command might not been succeed, system told "daemon started successfully / error: device not found"

Off course, Rebooted phone after cleaning app caches sometimes but nothing has changed. lol
Did you enable both, "USB debugging" and "USB debugging (security settings)"? Is your phone on?
 
Thanks for your reply,

1. Year, I did clear caches over and over again
2. As I told in my 1st report, I try adb command but adb command might not been succeed, system told "daemon started successfully / error: device not found"

Off course, Rebooted phone after cleaning app caches sometimes but nothing has changed. lol
Did you tried with the original cable? I have problems with other cables. USB Port 2.0 did you tried?

Gesendet von meinem 2210132G mit Tapatalk
 
Ishtar here, all good (via fastboot, I'm used to that method now I don't bother with twrp unless I have to).
I had to redo the adb trick for Gallery crashing, but that takes like 5 seconds so I'm fine with it.
No other issues, well except the detecting layers while setting a magazine wallpaper but they (Xiaomi itself) will figure it out eventually.

For guys having issues with Aliexpress, here's what I've done to bypass the "accepting cookies" hang: just tap the third option, it goes to a browser, save preferences, then close the app (even from recent) and reopen it, it should solve the issue. Random crashes/weird behaviour happen in that app, but as I said on the previous release, I assume it's an Android 14 related issue so they'll eventually figure it out as well.
 
Did you enable both, "USB debugging" and "USB debugging (security settings)"? Is your phone on?
Thank you, I didn't enable USB (Security Setting), after enabling the toggle, rebooted the phone but nothing has changed.

BTW, the Xiaomi account service crush report seems web service issue. Here is the report attached.
 

Attachments

  • Screenshot_2023-12-11-05-27-44-326_com.miui.bugreport.jpg
    Screenshot_2023-12-11-05-27-44-326_com.miui.bugreport.jpg
    169.3 KB · Views: 101
On my K60 Pro(Socrates), LSPosed worked with KSU and ZygiskNext very well, both with the inject app by the EU team.
Nothing seems bad in this build, Singpass works well but some bank APP not work[Halifax, Lloyds] (The problem of this build is not the EU team).
If your app crash just second dex then reboot, everything runs super smooth and good.
 
Thank you, I didn't enable USB (Security Setting), after enabling the toggle, rebooted the phone but nothing has changed.

BTW, the Xiaomi account service crush report seems web service issue. Here is the report attached.
So you enabled both toggles and ran the adb commands while your phone is on and then you rebooted?
 
I have this error, but only in dark mode. The YouTube videos and those from the security cameras have this line as shown in the attached image. My phone is Mi 13 ultra (isthar).
 

Attachments

  • Imagen de WhatsApp 2023-12-10 a las 16.38.40_eeb2ad0c.jpg
    Imagen de WhatsApp 2023-12-10 a las 16.38.40_eeb2ad0c.jpg
    60.3 KB · Views: 148
I have this error, but only in dark mode. The YouTube videos and those from the security cameras have this line as shown in the attached image. My phone is Mi 13 ultra (isthar).
 
  • Like
Reactions: Condizioninatore
I have this error, but only in dark mode. The YouTube videos and those from the security cameras have this line as shown in the attached image. My phone is Mi 13 ultra (isthar).
 
I have this error, but only in dark mode. The YouTube videos and those from the security cameras have this line as shown in the attached image. My phone is Mi 13 ultra (isthar).
Read some posts above, there is the solution

Gesendet von meinem 2210132G mit Tapatalk
 
So you enabled both toggles and ran the adb commands while your phone is on and then you rebooted?
Thanks again, but result has not changed.

PS C:\> adb kill-server
PS C:\> adb shell pm compile -a -f -r
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found

I'm not sure we should add last word (cmdline) but both results are the same...
 
Dear Developers and leaders,

Still be notified of a series of crash reports...
1) "Google Developer Services"
2) "Google Play"
3) "Xiaomi Account"
4) Chrome and web services cannot access internet (Bing can access Internet well!)

Will I have to make the decision to do a clean install...?
If you don't run these commands successfully, these apps will crash indefinitely. Have you authorized computer on device? (Dialog should appear after entering the first command; reboot device if you don't have it + make sure you are connected to PC...).
 
Thanks again, but result has not changed.

PS C:\> adb kill-server
PS C:\> adb shell pm compile -a -f -r
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found

I'm not sure we should add last word (cmdline) but both results are the same...
Use CMD, not PowerShell..
 
Status
Not open for further replies.

Similar threads