MIUI 14 23.1.3


Status
Not open for further replies.
Error happened. Did as told to reboot TWRP and try reinstalling again. Did it multiple times but same results on Thor. Any other 12s ultra people facing the same issue?
 

Attachments

  • Screenshot_2023-01-06-19-44-55.png
    Screenshot_2023-01-06-19-44-55.png
    475.2 KB · Views: 267
Followed this to install twrp to mi11 (venus).

You do not need to Format Data.

Rename the downloaded TWRP to twrp.img
1. run TWRP using the fastboot command:
Code:
fastboot boot twrp.img
2. Insert the downloaded TWRP into the phone.
3. Install
4. Install the image
5. Install Recovery Ramdisk
6. reboot to recovery
7. reboot to systém

best regards
 
Error happened. Did as told to reboot TWRP and try reinstalling again. Did it multiple times but same results on Thor. Any other 12s ultra people facing the same issue?
still not enough.. sometime it takes more than 10x try to pass this TWRP error.. so reboot to TWRP again and try again..
 
  • Like
Reactions: Abbashady
Hello, I am on miui 13.0.3 stock , can I go with eu recovery rom or need to flash fastboot rom first then update with recovery
No, it's not necessary. After unlocking the bootloader, install twrp skk on the phone. Then flash the recovery rom. And at the end, format data from the wipe options
 
  • Like
Reactions: NasrS
I believe the status bar icons in control center have been pushed down on the latest build
Poco F3
 

Attachments

  • Screenshot_2023-01-07-12-53-43-543_com.miui.home-edit[1].jpg
    Screenshot_2023-01-07-12-53-43-543_com.miui.home-edit[1].jpg
    464.6 KB · Views: 358
I have POCO F3. When trying to install twrp-3.7.0_12-v6.6_A13-alioth-skkk.img I get this error:
Sending 'recovery' (196608 KB) OKAY [ 4.281s]
Writing 'recovery' FAILED (remote: '(recovery_a) No such partition')
fastboot: error: Command failed


Am I doing something wrong? What should I do?
 
K50 Ultra update from nearest dev ver (V14.0.22.12.26.DEV).
Go to update > Pick update package > ok
Phone reboot to twrp a13 and auto update > reboot to system
Finally got bootloop many times at miui screen and now automatically enter fastboot mode. Can't enter recovery mode.
Anyone help :(
=================================
Update: Re install "xiaomi.eu_multi_DITING_V14.0.22.12.26.DEV_v14-13-fastboot" and K50 Ultra was working normally.
How to update the "xiaomi.eu_multi_DITING_V14.0.23.1.3.DEV_v14-13" to work properly?
 
Last edited:
I believe the status bar icons in control center have been pushed down on the latest build
Poco F3
This is so that all icons can be displayed when the camera prevents it.
I have POCO F3. When trying to install twrp-3.7.0_12-v6.6_A13-alioth-skkk.img I get this error:
Sending 'recovery' (196608 KB) OKAY [ 4.281s]
Writing 'recovery' FAILED (remote: '(recovery_a) No such partition')
fastboot: error: Command failed


Am I doing something wrong? What should I do?
You need to use fastboot boot twrp.img command on Poco F3
 

Attachments

  • Screenshot_2023-01-07-10-33-03-818_com.android.settings.jpg
    Screenshot_2023-01-07-10-33-03-818_com.android.settings.jpg
    23.2 KB · Views: 236
Ingress
All went good, new rom seem fast and smoth.
However fastboot boot recovery command don't worked 4 me making a soft brick.
Fastboot flash recovery command worked after install last fastboot rom again.
Recovery started at First boot decrypting SSD and asking PIN .
Thanks
 
Update done on mi 11 without problem!
On the other hand I have the impression that it is the installations via twrp which drains the battery!
Because with the first 2 versions released miui 14 in fastboot the battery held up very well and there this week the battery melted at a glance!
I had already noticed the problem with miui 13 when the roms came out in twrp and I thought it must have come from miui 13 but now I'm convinced it's from twrp because the problem starts again!
 
Update done on mi 11 without problem!
On the other hand I have the impression that it is the installations via twrp which drains the battery!
Because with the first 2 versions released miui 14 in fastboot the battery held up very well and there this week the battery melted at a glance!
I had already noticed the problem with miui 13 when the roms came out in twrp and I thought it must have come from miui 13 but now I'm convinced it's from twrp because the problem starts again!
False.
 
  • Like
Reactions: jeffrom
I flashed the previous rom again by fastboot and after booting I had twrp already installed so things are going well.
Yes now!! Working fine on MI12 Pro
 
Last edited:
Holla,

that was a difficult birth to play up this update. But it did work after several attempts. I use the "TWRP_[BOOT]3.6.2_12-Mi12_v6.0_A13-cupid-skkk.img". I don't want to install TWRP on my phone. At the first try I got error messages in TWRP during the installation. After reading here on the forum I tried installing it a second time and it went through. So all is well again, with a new image!



Thank you.

Xiaomi 12
 
Thanks, working fine on my Poco F3 with OrangeFox Recovery 11.1.1.5.

For Poco F3 Users, i can recommend you OrangeFox Recovery ( the same version than above for A13 ). Download the .zip, take the boot.img from it, then do "fastboot boot boot.img". Once you are inside OrangeFox, flash the complete OrangeFox zip, and you are done.

When you flash rom, you can check the box "Install OrangeFox After flashing ROM" and you can check "Add Magisk" too if you want. There is magisk 25.2 in built with manager to disable modules in the recovery.
 
Hey I tried rebooting my phone but its stuck on fast boot, even when I shut it down fully, even when I try to exit it via

fastboot reboot
I had same issue with my 12su. What I did was use fastboot and flash A13 twrp using fastboot flash recovery _ab twrp'name'.img. Then using the boot img from the last fastboot ROM, flash that again using fastboot flash boot_ab boot.img. Then fastboot.exe reboot recovery. This installs A13 twrp with old boot image. It allowed me to get a working twrp. Don't know why I had to go this route but it worked
 
  • Like
  • Love
Reactions: Ryoma and Eroticus
Status
Not open for further replies.

Similar threads