MIUI 13 MIUI 13 STABLE RELEASE


Status
Not open for further replies.
Hi,
I'm trying to update my Mi 11 @ 13.0.6 to 13.0.8 on my Mac. I copied the platform-tools contents into the 13.0.8 library and ran the updating script.

Code:
Waiting for device...
##################################################################
Please wait. The device will reboot when installation is finished.
##################################################################
Setting current slot to 'a'                        OKAY [  0.040s]
Finished. Total time: 0.041s
Sending 'dsp_a' (65536 KB)                         OKAY [  1.688s]
Writing 'dsp_a'                                    OKAY [  0.130s]
Finished. Total time: 1.825s
Sending 'dsp_b' (65536 KB)                         OKAY [  1.618s]
Writing 'dsp_b'                                    OKAY [  0.165s]
Finished. Total time: 1.790s
Sending 'xbl_config_a' (216 KB)                    OKAY [  0.007s]
Writing 'xbl_config_a'                             OKAY [  0.002s]
Finished. Total time: 0.019s
Sending 'xbl_config_b' (216 KB)                    OKAY [  0.007s]
Writing 'xbl_config_b'                             OKAY [  0.002s]
Finished. Total time: 0.017s
Sending 'boot_a' (196608 KB)                       OKAY [  5.063s]
Writing 'boot_a'                                   OKAY [  0.439s]
Finished. Total time: 5.513s
Sending 'boot_b' (196608 KB)                       OKAY [  4.758s]
Writing 'boot_b'                                   OKAY [  0.406s]
Finished. Total time: 5.172s
Sending 'modem_a' (249180 KB)                      OKAY [  6.575s]
Writing 'modem_a'                                  OKAY [  0.546s]
Finished. Total time: 7.129s
Sending 'modem_b' (249180 KB)                      OKAY [  6.339s]
Writing 'modem_b'                                  OKAY [  0.513s]
Finished. Total time: 6.859s
Sending 'vbmeta_system_a' (4 KB)                   OKAY [  0.002s]
Writing 'vbmeta_system_a'                          OKAY [  0.001s]
Finished. Total time: 0.011s
Sending 'vbmeta_system_b' (4 KB)                   OKAY [  0.002s]
Writing 'vbmeta_system_b'                          OKAY [  0.001s]
Finished. Total time: 0.011s
Sending 'tz_a' (3680 KB)                           OKAY [  0.097s]
Writing 'tz_a'                                     OKAY [  0.009s]
Finished. Total time: 0.113s
Sending 'tz_b' (3680 KB)                           OKAY [  0.093s]
Writing 'tz_b'                                     OKAY [  0.009s]
Finished. Total time: 0.109s
Sending 'vbmeta_a' (4 KB)                          OKAY [  0.002s]
Writing 'vbmeta_a'                                 OKAY [  0.001s]
Finished. Total time: 0.010s
Sending 'vbmeta_b' (4 KB)                          OKAY [  0.002s]
Writing 'vbmeta_b'                                 OKAY [  0.001s]
Finished. Total time: 0.010s
Sending 'bluetooth_a' (1116 KB)                    OKAY [  0.030s]
Writing 'bluetooth_a'                              OKAY [  0.004s]
Finished. Total time: 0.043s
Sending 'bluetooth_b' (1116 KB)                    OKAY [  0.029s]
Writing 'bluetooth_b'                              OKAY [  0.004s]
Finished. Total time: 0.041s
Sending 'abl_a' (204 KB)                           OKAY [  0.007s]
Writing 'abl_a'                                    OKAY [  0.003s]
Finished. Total time: 0.017s
Sending 'abl_b' (204 KB)                           OKAY [  0.007s]
Writing 'abl_b'                                    OKAY [  0.003s]
Finished. Total time: 0.016s
Sending 'cpucp_a' (104 KB)                         OKAY [  0.004s]
Writing 'cpucp_a'                                  OKAY [  0.002s]
Finished. Total time: 0.014s
Sending 'cpucp_b' (104 KB)                         OKAY [  0.004s]
Writing 'cpucp_b'                                  OKAY [  0.003s]
Finished. Total time: 0.013s
Sending 'dtbo_a' (16384 KB)                        OKAY [  0.425s]
Writing 'dtbo_a'                                   OKAY [  0.037s]
Finished. Total time: 0.469s
Sending 'dtbo_b' (16384 KB)                        OKAY [  0.397s]
Writing 'dtbo_b'                                   OKAY [  0.044s]
Finished. Total time: 0.447s
Sending 'featenabler_a' (88 KB)                    OKAY [  0.004s]
Writing 'featenabler_a'                            OKAY [  0.003s]
Finished. Total time: 0.016s
Sending 'featenabler_b' (88 KB)                    OKAY [  0.004s]
Writing 'featenabler_b'                            OKAY [  0.003s]
Finished. Total time: 0.015s
Sending 'vendor_boot_a' (5888 KB)                  OKAY [  0.154s]
Writing 'vendor_boot_a'                            OKAY [  0.016s]
Finished. Total time: 0.178s
Sending 'vendor_boot_b' (5888 KB)                  OKAY [  0.146s]
Writing 'vendor_boot_b'                            OKAY [  0.016s]
Finished. Total time: 0.170s
Sending 'keymaster_a' (276 KB)                     OKAY [  0.008s]
Writing 'keymaster_a'                              OKAY [  0.003s]
Finished. Total time: 0.020s
Sending 'keymaster_b' (276 KB)                     OKAY [  0.008s]
Writing 'keymaster_b'                              OKAY [  0.003s]
Finished. Total time: 0.019s
Sending 'uefisecapp_a' (124 KB)                    OKAY [  0.005s]
Writing 'uefisecapp_a'                             OKAY [  0.003s]
Finished. Total time: 0.017s
Sending 'uefisecapp_b' (124 KB)                    OKAY [  0.005s]
Writing 'uefisecapp_b'                             OKAY [  0.003s]
Finished. Total time: 0.016s
Sending 'qupfw_a' (56 KB)                          OKAY [  0.003s]
Writing 'qupfw_a'                                  OKAY [  0.001s]
Finished. Total time: 0.012s
Sending 'qupfw_b' (56 KB)                          OKAY [  0.003s]
Writing 'qupfw_b'                                  OKAY [  0.001s]
Finished. Total time: 0.011s
Sending 'xbl_a' (3608 KB)                          OKAY [  0.094s]
Writing 'xbl_a'                                    OKAY [  0.006s]
Finished. Total time: 0.107s
Sending 'xbl_b' (3608 KB)                          OKAY [  0.088s]
Writing 'xbl_b'                                    OKAY [  0.006s]
Finished. Total time: 0.101s
Sending 'devcfg_a' (52 KB)                         OKAY [  0.003s]
Writing 'devcfg_a'                                 OKAY [  0.001s]
Finished. Total time: 0.011s
Sending 'devcfg_b' (52 KB)                         OKAY [  0.003s]
Writing 'devcfg_b'                                 OKAY [  0.001s]
Finished. Total time: 0.011s
Sending 'hyp_a' (3616 KB)                          OKAY [  0.092s]
Writing 'hyp_a'                                    OKAY [  0.011s]
Finished. Total time: 0.110s
Sending 'hyp_b' (3616 KB)                          OKAY [  0.087s]
Writing 'hyp_b'                                    OKAY [  0.011s]
Finished. Total time: 0.105s
Sending 'imagefv_a' (2048 KB)                      OKAY [  0.056s]
Writing 'imagefv_a'                                OKAY [  0.007s]
Finished. Total time: 0.071s
Sending 'imagefv_b' (2048 KB)                      OKAY [  0.055s]
Writing 'imagefv_b'                                OKAY [  0.007s]
Finished. Total time: 0.070s
Sending 'shrm_a' (48 KB)                           OKAY [  0.003s]
Writing 'shrm_a'                                   OKAY [  0.001s]
Finished. Total time: 0.011s
Sending 'shrm_b' (48 KB)                           OKAY [  0.003s]
Writing 'shrm_b'                                   OKAY [  0.001s]
Finished. Total time: 0.011s
Sending 'aop_a' (240 KB)                           OKAY [  0.008s]
Writing 'aop_a'                                    OKAY [  0.003s]
Finished. Total time: 0.017s
Sending 'aop_b' (240 KB)                           OKAY [  0.007s]
Writing 'aop_b'                                    OKAY [  0.003s]
Finished. Total time: 0.017s
Sending 'cust' (415132 KB)                         OKAY [ 11.090s]
Writing 'cust'                                     OKAY [  0.004s]
Finished. Total time: 11.103s
Sending sparse 'super' 1/9 (738592 KB)             OKAY [ 20.136s]
Writing 'super'                                    OKAY [  0.008s]
Sending sparse 'super' 2/9 (735128 KB)             OKAY [ 19.928s]
Writing 'super'                                    OKAY [  0.010s]
Sending sparse 'super' 3/9 (754584 KB)

It's been stuck on this line, 'super' 3/9, for 30 minutes. What to do, do I keep waiting? Will my device be bricked if I interrupt the installation? This has never happened to me before.
Don't worry, it is a common problem. Reboot phone and try again with another USB port and/or another USB cable.
 
  • Like
Reactions: Casper99
With last rom from Xiaomi 12 (cupid) Google assistant not working anymore if I clear recent apps. If I say "ok google" assistant not working, until I open the Google app or some other such Chrome. Any advice for this?
 
  • Like
Reactions: pejor
good evening I want to ask, install Rom 13.0.7 on my redmi note 10 pro, and it flows very well, the only thing that is happening to me is that in whastapp, it deletes my contacts until I update in the same app, it seems again, you would know how can i fix that? Thank you very much in advance for sharing your work. excuse my english but i'm translating it
 
good evening I want to ask, install Rom 13.0.7 on my redmi note 10 pro, and it flows very well, the only thing that is happening to me is that in whastapp, it deletes my contacts until I update in the same app, it seems again, you would know how can i fix that? Thank you very much in advance for sharing your work. excuse my english but i'm translating it
there are some workarounds…
1st change contact permissions to "Always allow" in whatsapp
- Modify and delete contacts
- Read your contacts
2nd you have to "clear data / cache" on the Permissions app
 
Hi again,

regarding my post since Monday regarding wireless charging problem on Mi 11 Pro EU ROM, I can add some other issues:
1. The wireless charger recognizes the phone, but the phone does not charging;
2. I can not open my e-mails using Mi Mail, while the phone is on Mobile data mode. It opens mails only on WiFi mode;
3. I can't open pdf files trough "Files" app
4. No indications on locked screen about received notification by apps, nevertheless, the permission is granted by the app

MIUI has been updated to 13.0.12 Stable
 
  • Like
Reactions: Will197
Hey there, I've seen that there's an update for the Mix 4.
Does the stable version have the same notification issue as the weekly?
 
Hey everybody
i have some problems with the DKB Tan2Go app and im wondering if there is anybody else with this problem:
When i am starting the app its asking me for a new password. After i´ve set this and confirmed it the app is only showing a white screen with the blue line of the DKB Logo on the upper side of the screen. Nothing else is happening anymore.
I am on Version 13.0.12 on a MI11Pro.
On Version 12 the app has still been working.
The strange thing is that only the DKB Tan2Go App has that problem.
Postbank, ING-DIBA and Volksbank Apps are working just fine...

The Phone is not rooted. I only opened the bootloader to install Xiaomi.eu roms.

Perhaps someone already found a solution for this?

I´ve searched already in the Forums but most people experience these kind of problems with root and magisk which doesn´t really fit for me.

Thanks in advance for any help :)
 
I have Poco F3, and just upgraded from 12.5 to 13.0.5. When connected to my home wifi, it says that the network "Can't connect to the internet" which is wrong since if I open up a browser I can browse the internet. Apps that check with android first don't work since it thinks there is no access, but for apps that dont do that check everything is fine.

I have tried the "Reset wifi/mobile /bluetooth" and it didn't help .

Anything else I can do ? I really want to avoid a factory reset if at all possible. I am rooted if that helps.

thanks
 
I recently upgraded from a Mi 9 Lite to a 11 Lite 5G NE. On my Mi 9 Lite (CC9) I was running MIUI 12.5 weekly (xiaomi.eu_multi_MI9LiteMICC9_21.9.8_v12-11.zip or thereabouts) but my Google Chat features were not working with a "chat features unavailable for this device" message. I decided to move to MIUI 12.5 stable (xiaomi.eu_multi_MI9LiteMICC9_V12.5.5.0.RFCCNXM_v12-11.zip) and was immediately able to enable chat features in Google Messages!

On my 11 Lite 5G NE I was running MIUI 13 (OEM) (miui_LISAGlobal_V13.0.4.0.SKOMIXM_0508eaacfa_12.0.zip) and Google Messages chat features worked fine. Last night I unlocked the bootloader and flashed MIUI 13 stable (xiaomi.eu_multi_MI11LE_XM11Lite5GNE_V13.0.1.0.SKOCNXM_v13-12-fastboot.zip) using Fastboot and I am back to the same "chat features unavailable for this device" error.

I tried all the usual google "fixes" (erase app data, etc.) but no luck. Is it possible something is "broken" in the MIUI 13 Stable release preventing chat features from working? I don't want to revert to the OEM build if I can avoid it!

FYI: I am in Canada with Public Mobile (Telus) and can connect to 3G, 4G, and 5G networks but no difference and have been using the same SIM/service across both devices and all ROMs mentioned above.
 
I don't get notifications either ... i tried multiple xiaomi.eu ROMS and multiple China ROMS. I found some succes with China 13.0.4, but it's far from perfect. I get like 90% of notifications on time, while the other 10% don't come at all, come hours later or just when I open the app. I don't even have the energy to complain anymore

Gmail just refuses to push any notification.
My livescores apps show me notifications completely random, some yes, mostly not, there is just no logic.

Fun fact, my father's Mi 10T Pro works perfect with Global ROM.
My MIX 4 is driving me crazy. Multiple ROMS, EU & China ... And no one can handle notifications right ... I don't understand.
I also did realize that once in awhile my Whatsapp doesn't push notifications unless I open it manually. I did however remove the battery saver for Whatsapp, hoping it doesn't happen again. Poco F3 13.0.5, Been rocking this for a few weeks. Thank you devs for making this.
 
Wiped data
Installed ROMS
Cleared cache
Cleared data
Fresh install of applications
Autostart on
No battery restrictions
Gave all permissions
I even navigated some deeper settings to set no data restrictions for all google apps and all apps that bother me with notifications delay
Nothing can make it work.
This is an €800 Xiaomi MIX 4.
I have said it in the past and I will say it again, for the flawless way an iphone works, it should cost €3000. I had multiple iphones, from 2G to 11 and I had no issues with any of them. For a short period of time, I also had a Huawei, notifications problem there also. It's unacceptable.
Apps shouldn't even need all that autostart on, no battery restrictions and giving all permissions. What's the point of having all these skins running over OS, allowing all these customizations, if they can't find a way to work as intended.
Everything in Android is hit or miss.
I know the problem:
.Motorola G4 - Android 7 & 8 - Stock Rom.
.Motorola G4 - Android 9 - Custom Rom.
.Mi 10 T Lite Global Android 11/12 EEA Rom.
.Mi 10 T Lite xiaomi.eu Android 12 Stable Rom.
In all cases I have only observed this problem with Gmail and no matter how the settings are set.
No other app, including WhatsApp, needs auto-start or special settings to display notifications properly.
 
CGuys, I don't want to be the bad guy, but identify your problems and post it in the right place. the last 20 posts are things from the official room, that the EU team has no business. generate unnecessary spam
 
CGuys, I don't want to be the bad guy, but identify your problems and post it in the right place. the last 20 posts are things from the official room, that the EU team has no business. generate unnecessary spam
Hi Luis,

Sorry to bother you, but which is the right place? Talking about my problems, all of them appeared after MIUI has been updated to 13.0.12 version and my phone has EU ROM. I will highly appreciate your support to direct me to the right place to post my problems, as I really would like to find a solution for them.

Thanks in advance.
 
Wiped data
Installed ROMS
Cleared cache
Cleared data
Fresh install of applications
Autostart on
No battery restrictions
Gave all permissions
I even navigated some deeper settings to set no data restrictions for all google apps and all apps that bother me with notifications delay

Nothing can make it work.
This is an €800 Xiaomi MIX 4.

I have said it in the past and I will say it again, for the flawless way an iphone works, it should cost €3000. I had multiple iphones, from 2G to 11 and I had no issues with any of them. For a short period of time, I also had a Huawei, notifications problem there also. It's unacceptable.

Apps shouldn't even need all that autostart on, no battery restrictions and giving all permissions. What's the point of having all these skins running over OS, allowing all these customizations, if they can't find a way to work as intended.

Everything in Android is hit or miss.
you should keep using iphones so don't suffer with Android
 
  • Like
Reactions: byterain77
Hi. I have Mi 11 Pro and CN Rom 13.0.9. Because of poor notification, Whatsapp contact list and missing my native language I am thinking to switch to xiaomi.eu Rom 13.12. Is it good idea? Thanks!
 
CGuys, I don't want to be the bad guy, but identify your problems and post it in the right place. the last 20 posts are things from the official room, that the EU team has no business. generate unnecessary spam
I share your opinion but notification problems are very common and frustrating. Not always the user's fault.
In my case, only Gmail was failing and I have already uninstalled it.
I have installed Spark and my email notifications now works fine.

However, I agree that this is not xiaomi.eu's problem and I don't think they can solve anything about it.
 
  • Like
Reactions: biscoot
Hi,
I did the last update 13.0.6.0 on my Mix 4, and bugs are still here.
Mirror cast impossible, sound go down when I connect headphones and impossible to use remote control on my headphones.
 
Hi, will the ROM base for the 11 Lite 5G NE (lisa) get changed from China to Global any time soon? Mi 11 LE's lastest update is becoming incredibly outdated, it's still on February patch and it's almost June while global is on April.
 
Thanks to those working on Xiaomi.eu!

Quick bug report about the latest stable on Mi 11 Ultra (V13.0.12.0.SKACNXM).

Google Voice app can not connect to Google in latest stable. App starts, but no calls, messages, or contacts are visible. Instead app displays error message that network is unavailable / can't connect to Google.

Connects fine in previous stable release V13.0.10.0.SKACNXM
Connects fine in most recent weekly 22.5.11_v13-12 (is this most recent anymore? there may be one more since that I didn't test)

Have also tried stable from scratch (installed V13.0.12.0.SKACNXM with format/new install script for bare phone, then installed Google Voice as 1st installed app), Google Voice could not connect even on fresh install. For the moment reverted to V13.0.10.0.SKACNXM.

Regular Google Voice user so hoping it's fixed in a future stable. ;-)
 
Status
Not open for further replies.

Similar threads

  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
40K
Replies
51
Views
35K
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
37K
  • Locked
HyperOS 1.0 24.7.8/12
Replies
50
Views
32K