Read the guides on the 1st page. You're going to install with the TWRP method so follow these steps. If the guide is too difficult then I might suggest to ask a friend before you're getting in too deep.
MIUI 13 MIUI 13 STABLE RELEASE
- Thread starter ingbrzy
- Start date
Sorry my bad, until i wait bootloader unlock its changed from fastboot to recoveryYou need to read the first page and pay special attention to the table and the word "recovery".
You won't believe how powerful the search function is on this forum. Just humor me and try it for a laugh
My bad Thnx i am good, i got newest twrp installed suscesfuly, now waiting until rom copies to phone storage and flash it
i am xiaomi.eu lover form mi 8 pro so its long time mi 8 pro> mi 10 > mi 12 pro wife got aslo mi 11 we love xiaomi.eu team Thnx agian
Hi,
Mi 10t Lite user here.
Does anybody know if the latest stable has google assistant hotword (hey google) working (screen on + screen off)?
+ Is there an option to have the "mi" boot logo + device name remain? (its changed to redmi note 9 pro when I installed this rom in the past)
Thanks
Mi 10t Lite user here.
Does anybody know if the latest stable has google assistant hotword (hey google) working (screen on + screen off)?
+ Is there an option to have the "mi" boot logo + device name remain? (its changed to redmi note 9 pro when I installed this rom in the past)
Thanks
- Oct 6, 2016
- 9,510
- 322
If you have the Global model, then the name will be "Mi 10T Lite".Hi,
Mi 10t Lite user here.
Does anybody know if the latest stable has google assistant hotword (hey google) working (screen on + screen off)?
+ Is there an option to have the "mi" boot logo + device name remain? (its changed to redmi note 9 pro when I installed this rom in the past)
Thanks
As for the boot logo, the ROM is originally made for the Chinese model and just happens to have support for the Global model as well. Not sure why that bothers you so much, but you can try flashing logo.img from an official Global ROM, if available.
- Oct 6, 2016
- 9,510
- 322
Should work fine, even when the screen is off, as long as it's the Global model.
TuxLin
Members
- May 15, 2022
- 68
- 30
TWRP for Mi 10T Lite includes an option to change Logo directly from the Recovery itself.
TuxLin
Members
- May 15, 2022
- 68
- 30
samirglima
Members
- Jun 15, 2021
- 75
- 30
That's what appeared. Does it understand that my device is still on version 12.5.15?
Attachments
samirglima
Members
- Jun 15, 2021
- 75
- 30
If the ROM file you downloaded says Fastboot, then it's Fastboot. If the file extension is .zip, then it is via recovery. I think for your device it is still fasboot, there is no custom recovery for it.
- Sep 25, 2017
- 242
- 67
Open Updater (with Internet on) few more times and check that command output again.
I have installed xiaomi eu - it seems to be working OK - other then my call logs were not restored.
During the installation I got the following errors:
What do you think, should I re-flesh?
During the installation I got the following errors:
Code:
.\windows_fastboot_first_install_with_data_format.bat
Waiting for device...
You are going to wipe your data and internal storage.
It will delete all your files and photos stored on internal storage.
Do you agree? (Y/N) Y
##################################################################
Please wait. The device will reboot when installation is finished.
##################################################################
Sending 'cmnlib64' (500 KB) OKAY [ 0.013s]
Writing 'cmnlib64' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'abl' (204 KB) OKAY [ 0.005s]
Writing 'abl' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'modem' (164972 KB) OKAY [ 4.080s]
Writing 'modem' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'cmnlib' (386 KB) OKAY [ 0.010s]
Writing 'cmnlib' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'hyp' (395 KB) OKAY [ 0.010s]
Writing 'hyp' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'keymaster' (232 KB) OKAY [ 0.006s]
Writing 'keymaster' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'tz' (2936 KB) OKAY [ 0.075s]
Writing 'tz' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'aop' (173 KB) OKAY [ 0.004s]
Writing 'aop' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'xbl_config' (94 KB) OKAY [ 0.003s]
Writing 'xbl_config' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'storsec' (19 KB) OKAY [ 0.001s]
Writing 'storsec' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'uefisecapp' (121 KB) OKAY [ 0.004s]
Writing 'uefisecapp' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'qupfw' (53 KB) OKAY [ 0.002s]
Writing 'qupfw' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'featenabler' (84 KB) OKAY [ 0.003s]
Writing 'featenabler' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'dsp' (65536 KB) OKAY [ 1.711s]
Writing 'dsp' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'bluetooth' (220 KB) OKAY [ 0.006s]
Writing 'bluetooth' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'devcfg' (42 KB) OKAY [ 0.001s]
Writing 'devcfg' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'xbl' (3253 KB) OKAY [ 0.084s]
Writing 'xbl' OKAY [ 0.082s]
Finished. Total time: 0.177s
Sending 'cmnlib64bak' (500 KB) OKAY [ 0.013s]
Writing 'cmnlib64bak' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'ablbak' (204 KB) OKAY [ 0.005s]
Writing 'ablbak' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'cmnlibbak' (386 KB) OKAY [ 0.010s]
Writing 'cmnlibbak' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'hypbak' (395 KB) OKAY [ 0.009s]
Writing 'hypbak' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'tzbak' (2936 KB) OKAY [ 0.071s]
Writing 'tzbak' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'aopbak' (173 KB) OKAY [ 0.005s]
Writing 'aopbak' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'xbl_configbak' (94 KB) OKAY [ 0.003s]
Writing 'xbl_configbak' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'qupfwbak' (53 KB) OKAY [ 0.002s]
Writing 'qupfwbak' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'devcfgbak' (42 KB) OKAY [ 0.002s]
Writing 'devcfgbak' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'xblbak' (3253 KB) OKAY [ 0.079s]
Writing 'xblbak' OKAY [ 0.065s]
Finished. Total time: 0.149s
Sending 'boot' (41480 KB) OKAY [ 0.997s]
Writing 'boot' OKAY [ 0.270s]
Finished. Total time: 1.431s
Sending 'dtbo' (32768 KB) OKAY [ 0.798s]
Writing 'dtbo' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'logo' (30404 KB) OKAY [ 0.726s]
Writing 'logo' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'vbmeta' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'vbmeta_system' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_system' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending sparse 'cust' 1/2 (258144 KB) OKAY [ 6.375s]
Writing 'cust' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending sparse 'super' 1/22 (254884 KB) OKAY [ 6.220s]
Writing 'super' OKAY [ 1.266s]
Sending sparse 'super' 2/22 (262140 KB) OKAY [ 6.542s]
Writing 'super' OKAY [ 1.561s]
Sending sparse 'super' 3/22 (262140 KB) OKAY [ 6.556s]
Writing 'super' OKAY [ 1.801s]
Sending sparse 'super' 4/22 (262140 KB) OKAY [ 6.389s]
Writing 'super' OKAY [ 2.665s]
Sending sparse 'super' 5/22 (248872 KB) OKAY [ 6.025s]
Writing 'super' OKAY [ 1.636s]
Sending sparse 'super' 6/22 (253620 KB) OKAY [ 6.131s]
Writing 'super' OKAY [ 2.927s]
Sending sparse 'super' 7/22 (262140 KB) OKAY [ 6.305s]
Writing 'super' OKAY [ 2.379s]
Sending sparse 'super' 8/22 (262140 KB) OKAY [ 6.308s]
Writing 'super' OKAY [ 2.967s]
Sending sparse 'super' 9/22 (258072 KB) OKAY [ 6.194s]
Writing 'super' OKAY [ 1.305s]
Sending sparse 'super' 10/22 (229700 KB) OKAY [ 5.488s]
Writing 'super' OKAY [ 1.147s]
Sending sparse 'super' 11/22 (262140 KB) OKAY [ 6.346s]
Writing 'super' OKAY [ 1.376s]
Writing 'super' OKAY [ 2.552s]
Sending sparse 'super' 13/22 (238184 KB) OKAY [ 5.719s]
Sending sparse 'super' 17/22 (253664 KB) OKAY [ 6.089s]
Writing 'super' OKAY [ 2.973s]
Sending sparse 'super' 18/22 (259200 KB) OKAY [ 6.166s]
Writing 'super' OKAY [ 1.329s]
Sending sparse 'super' 19/22 (262140 KB) OKAY [ 6.271s]
Writing 'super' OKAY [ 1.749s]
Sending sparse 'super' 20/22 (262140 KB) OKAY [ 6.310s]
Writing 'super' OKAY [ 4.289s]
Sending sparse 'super' 21/22 (262140 KB) OKAY [ 6.290s]
Writing 'super' OKAY [ 1.887s]
Sending sparse 'super' 22/22 (131384 KB) OKAY [ 3.153s]
Writing 'super' OKAY [ 2.427s]
Finished. Total time: 178.608s
Erasing 'metadata' OKAY [ 0.006s]
Finished. Total time: 0.008s
Erasing 'userdata' OKAY [ 1.630s]
Finished. Total time: 1.631s
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.001sWhat do you think, should I re-flesh?
hi evryone,
i want to update my Mi11 (venus) from "MI11_V13.0.8.0.SKBCNXM" to "MI11_V13.0.9.0.SKBCNXM_v13-12". I have booted to twrp and was dont ask to enter a passwort or pin, is that why i can't see any files from the internal storage? and how can I fix it? i have tried moun-> decrypt but it doesent work, i have tried older twrp versions and it doesnt work. Can anyone help me?
i want to update my Mi11 (venus) from "MI11_V13.0.8.0.SKBCNXM" to "MI11_V13.0.9.0.SKBCNXM_v13-12". I have booted to twrp and was dont ask to enter a passwort or pin, is that why i can't see any files from the internal storage? and how can I fix it? i have tried moun-> decrypt but it doesent work, i have tried older twrp versions and it doesnt work. Can anyone help me?
- Oct 6, 2016
- 9,510
- 322
Something is terribly wrong with your flashing process, never seen something like this. Might be some unzipping issue.
Hmm, very interesting - the ROM seems to be fine and I have all functionalities (even "hey google"
).Does having a TWRP non-official recovery for android 12 can cause the issue?
Can this be because I came from another custom ROM (pixel experience)?
- Oct 6, 2016
- 9,510
- 322
I have no idea. Most of the firmware images were not flashed.Hmm, very interesting - the ROM seems to be fine and I have all functionalities (even "hey google"
Does having a TWRP non-official recovery for android 12 can cause the issue?
Can this be because I came from another custom ROM (pixel experience)?
MeiGuddet
Members
- Apr 29, 2016
- 1,480
- 297
You are trying to flash an A12 recovery ROM. So why the heck are you using OLDER recovery versions instead of a NEW A12 COMPATIBLE version?
Please read installation instruction carefully.
Hello. İ have some bugs and questions.
1. İ have less battery time in poco x3 nfc Xiaomi eu 13 rom. How can i fix it?
2. When i update google play system device restarts twice and back to old system update september 2021. Why?
3. Sometimes after restart notification volume go down to 50%. How to fix it?
4. İ disabled wake screen on notification but sometimes it wakes screen.
5. Screen time in settings not showing.
1. İ have less battery time in poco x3 nfc Xiaomi eu 13 rom. How can i fix it?
2. When i update google play system device restarts twice and back to old system update september 2021. Why?
3. Sometimes after restart notification volume go down to 50%. How to fix it?
4. İ disabled wake screen on notification but sometimes it wakes screen.
5. Screen time in settings not showing.
hi does v13-12 mean its an android 12 rom? the chart says the VEUXG rom is based on global but i didnt think they had released an android 12 global rom for VEUXG
ok so installed MIUI 12.5 and did that yes thing. I rebooted after that and it is stuck on MIUI logo.
P.S When i installed MIUI 13 the twrp gave error as shown in my above post and after that the phone was restarting again and again (bootloop) where as now after MIUI 12 installation, the phone is stuck in MIUI logo and does not reboot.
I am unable to understand what to do. My laptop is showning error the last device you connected to PC has malfunctioned. I just wanna go back to stock now :'(
Xiaomi Community
Xiaomi Community
You could have saved yourself a lot of time by checking those yourself.
What exactly do you want?
When you say "stuck" how much time are you talking about?
You know it takes about 5 minutes after a clean install to unpack apps and setup the system, right?
You are explaining your problem very poorly. At least for my understanding.
Judging by your previous posts - when installing MIUI13 there obviusly wasn't any succesful install, thus no OS to boot, thus bootloop. That's how I understand this.
Last edited:
