MIUI 14 MIUI 14 STABLE RELEASE


body-mg

Members
Feb 21, 2017
18
15
Hi,

i have already istalled XIAOMI.EU 13.0.41 stable on my MI 12. I have already installed TWRP 3.6.2. i can get into fastboot in twrp and also to original fastboot. But the device is not recognized from my win11 pc. And the driver installation doenst work. i have a failire in device manager. what can i do?
 

Ewanuna

Members
Nov 11, 2018
7
13
Help! My phone entered into a soft brick after trying to install the A13 TWRP, when I try to reboot the phone it just keeps on the Fastboot screen. HELP PLEASE (I have a Xiaomi 12)
EDIT: I reinstalled the ROM with the 'windows_fastboot_update_rom.bat' archive and the phone just installed it and rebooted perfectly, and I didn't have any data lose. Thanks god.
EDIT 2: The trouble that soft bricked the phone was an error during the installation of the TWRP, on the 2nd step, the 'fastboot boot twrp.img' step. The first one went perfectly, but when I typed the second command line, the 'Failed to load/authenticate boot image: Load Error' appeared and all was gone. Boys of xiaomi.eu, try to see what was the problem and try to fix it, please. P.D. I downloaded the TWRP from the link that YOU uploaded, this one exactly 'https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/cupid/' (the Xiaomi 'cupid' 12 one, and exactly, the file named 'twrp-3.7.0_12-v6.5_A13-cupid-skkk.img', because my phone actually has Android 13 with the MIUI 14 update). Thank you for your help.
 
Last edited:

Igor Eisberg

Lead Developer
Staff member
Oct 6, 2016
8,809
322
Help! My phone entered into a soft brick after trying to install the A13 TWRP, when I try to reboot the phone it just keeps on the Fastboot screen. HELP PLEASE (I have a Xiaomi 12)
EDIT: I reinstalled the ROM with the 'windows_fastboot_update_rom.bat' archive and the phone just installed it and rebooted perfectly, and I didn't have any data lose. Thanks god.
EDIT 2: The trouble that soft bricked the phone was an error during the installation of the TWRP, on the 2nd step, the 'fastboot boot twrp.img' step. The first one went perfectly, but when I typed the second command line, the 'Failed to load/authenticate boot image: Load Error' appeared and all was gone. Boys of xiaomi.eu, try to see what was the problem and try to fix it, please. P.D. I downloaded the TWRP from the link that YOU uploaded, this one exactly 'https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/cupid/' (the Xiaomi 'cupid' 12 one, and exactly, the file named 'twrp-3.7.0_12-v6.5_A13-cupid-skkk.img', because my phone actually has Android 13 with the MIUI 14 update). Thank you for your help.
I'm using that same TWRP on my Xiaomi 12, so no idea what your issue is.
As for "I downloaded the TWRP from the link that YOU uploaded", I would change that tone if I were in your place.
 

night_whisper

Members
Sep 10, 2011
45
40
Help! My phone entered into a soft brick after trying to install the A13 TWRP, when I try to reboot the phone it just keeps on the Fastboot screen. HELP PLEASE (I have a Xiaomi 12)
EDIT: I reinstalled the ROM with the 'windows_fastboot_update_rom.bat' archive and the phone just installed it and rebooted perfectly, and I didn't have any data lose. Thanks god.
EDIT 2: The trouble that soft bricked the phone was an error during the installation of the TWRP, on the 2nd step, the 'fastboot boot twrp.img' step. The first one went perfectly, but when I typed the second command line, the 'Failed to load/authenticate boot image: Load Error' appeared and all was gone. Boys of xiaomi.eu, try to see what was the problem and try to fix it, please. P.D. I downloaded the TWRP from the link that YOU uploaded, this one exactly 'https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/cupid/' (the Xiaomi 'cupid' 12 one, and exactly, the file named 'twrp-3.7.0_12-v6.5_A13-cupid-skkk.img', because my phone actually has Android 13 with the MIUI 14 update). Thank you for your help.
Well did you flash blank vbmeta before trying to boot TWRP?
Find blank vbmeta on google for your device.

Sent from my 2112123AC using Tapatalk
 

ryshd

Members
Aug 12, 2022
5
15
message app error

java.lang.ExceptionInInitializerError
at k.a.a.a.e.b.<clinit>(Unknown Source:5)
at k.a.a.a.e.b.b(Unknown Source:0)
at t.b.c.h.d.b.K(Unknown Source:24)
at t.b.c.h.d.b.<init>(Unknown Source:23)
at t.b.c.h.d.b.N(Unknown Source:13)
at d.a.a.b.d._A_.F(Unknown Source:3)
at j.o.q.f.e.e(Unknown Source:17)
at j.o.q.f.e$a$a.run(Unknown Source:4)
at java.lang.Thread.run(Thread.java:1012)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'java.io.File android.content.Context.getFilesDir()' on a null object reference
at k.a.a.a.h.h.a.<clinit>(Unknown Source:4)
... 9 more
 
  • Like
Reactions: Kakarotvn

whereismymind33

Members
Dec 28, 2022
2
3
message app error

java.lang.ExceptionInInitializerError
at k.a.a.a.e.b.<clinit>(Unknown Source:5)
at k.a.a.a.e.b.b(Unknown Source:0)
at t.b.c.h.d.b.K(Unknown Source:24)
at t.b.c.h.d.b.<init>(Unknown Source:23)
at t.b.c.h.d.b.N(Unknown Source:13)
at d.a.a.b.d._A_.F(Unknown Source:3)
at j.o.q.f.e.e(Unknown Source:17)
at j.o.q.f.e$a$a.run(Unknown Source:4)
at java.lang.Thread.run(Thread.java:1012)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'java.io.File android.content.Context.getFilesDir()' on a null object reference
at k.a.a.a.h.h.a.<clinit>(Unknown Source:4)
... 9 more
I have the same
 

Igor Eisberg

Lead Developer
Staff member
Oct 6, 2016
8,809
322
message app error

java.lang.ExceptionInInitializerError
at k.a.a.a.e.b.<clinit>(Unknown Source:5)
at k.a.a.a.e.b.b(Unknown Source:0)
at t.b.c.h.d.b.K(Unknown Source:24)
at t.b.c.h.d.b.<init>(Unknown Source:23)
at t.b.c.h.d.b.N(Unknown Source:13)
at d.a.a.b.d._A_.F(Unknown Source:3)
at j.o.q.f.e.e(Unknown Source:17)
at j.o.q.f.e$a$a.run(Unknown Source:4)
at java.lang.Thread.run(Thread.java:1012)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'java.io.File android.content.Context.getFilesDir()' on a null object reference
at k.a.a.a.h.h.a.<clinit>(Unknown Source:4)
... 9 more
I have the same
Unable to reproduce. Clear app data for Messaging app.
 

cseryz

Members
Dec 22, 2022
15
15
Help! My phone entered into a soft brick after trying to install the A13 TWRP, when I try to reboot the phone it just keeps on the Fastboot screen. HELP PLEASE (I have a Xiaomi 12)
EDIT: I reinstalled the ROM with the 'windows_fastboot_update_rom.bat' archive and the phone just installed it and rebooted perfectly, and I didn't have any data lose. Thanks god.
EDIT 2: The trouble that soft bricked the phone was an error during the installation of the TWRP, on the 2nd step, the 'fastboot boot twrp.img' step. The first one went perfectly, but when I typed the second command line, the 'Failed to load/authenticate boot image: Load Error' appeared and all was gone. Boys of xiaomi.eu, try to see what was the problem and try to fix it, please. P.D. I downloaded the TWRP from the link that YOU uploaded, this one exactly 'https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/cupid/' (the Xiaomi 'cupid' 12 one, and exactly, the file named 'twrp-3.7.0_12-v6.5_A13-cupid-skkk.img', because my phone actually has Android 13 with the MIUI 14 update). Thank you for your help.
Hello,
After flashing twrp, just restart your phone to recovery, do not execute this command "fastboot boot twrp.img"
Cheers
 
Last edited:
  • Like
Reactions: katerpanne

kreso75

Members
May 19, 2021
12
15
I'm one more with Messaging app closing with latest MIUI 14.0.3.0.TLACNXM on 12S Ultra.
Bug report is exactly the same as @ryshd wrote.

Backed up the SMS (that worked) and cleared data for Messaging app, unfortunately without improvement.
 

Orjon

Xiaomi 12 tester, Polish translator
Staff member
Mar 18, 2017
546
182
Can you try to get a bit longer logcat from the crash? We're unable to reproduce it, maybe it could give a clue what is happening there.
 

ryshd

Members
Aug 12, 2022
5
15
Can you try to get a bit longer logcat from the crash? We're unable to reproduce it, maybe it could give a clue what is happening there.

OK?
 

katerpanne

Members
Apr 19, 2014
3,458
332
Hi,

i have already istalled XIAOMI.EU 13.0.41 stable on my MI 12. I have already installed TWRP 3.6.2. i can get into fastboot in twrp and also to original fastboot. But the device is not recognized from my win11 pc. And the driver installation doenst work. i have a failire in device manager. what can i do?
install correct driver
 

tezukaryoma

Members
Nov 2, 2018
29
15
Rubens K50 same message forced closed issue as above reported, on latest 14.0.4.0 ROM, work fine on previous 14.0.3 rom
 

Kakarotvn

Members
Jun 19, 2016
23
15
Same, Unicorn on 14.0.3 Message app force close. Try to install google message but can't send new message also.
 

Attachments

  • Screenshot_2022-12-29-09-08-22-190_com.google.android.apps.messaging.jpg
    Screenshot_2022-12-29-09-08-22-190_com.google.android.apps.messaging.jpg
    397.1 KB · Views: 165

wongwengtim

Members
Aug 16, 2022
7
15
It doesn't work for my 12s Ultra. Dou have any other sugestion?
Tks.
This is the only solution I've heard from Xiaomi CN Official DEV. You can try that code on MIUI 13 CN build. If it still doesn't work then you may extract the modem.img from MIUI 14 and flash it over MIUI 13.
 

mesabogii

Members
Oct 5, 2022
6
15
12s Ultra here.
Having same xiaomi messaging error log as @ryshd
- Updated to xiaomi.eu_multi_THOR_V14.0.3.0.TLACNXM_v14-13-fastboot.zip
- Xiaomi Messaging App version 14.0.0.21

Tried
1. Clear Data Cache, Clear All data, Clear Cache. Error persist
2. Re-flash fastboot_update_rom.sh. Error persist

Thanks
Update

I've revert back to 14.0.2.0 with macos_fastboot_update_rom.sh from xiaomi.eu_multi_THOR_V14.0.2.0.TLACNXM_v14-13-fastboot.
The messaging app is back to normal with same messaging app version 14.0.0.21.

* Before upgrading to V14.0.3.0, I had clean install from xiaomi.eu_multi_THOR_V14.0.2.0.TLACNXM_v14-13-fastboot.
Try at your own risk...
 
Last edited:
  • Like
Reactions: Evgenums