[GUIDE][venus|star|mars] How to install Xiaomi.eu ROM for Xiaomi MI11 / Pro / Ultra
- Thread starter ingbrzy
- Start date
goodguyavi
Members
- Jul 1, 2016
- 82
- 20
- Feb 11, 2012
- 11,595
- 322
xiaomi.eu_multi_MI11Pro_MI11Ultra_21.4.15_v12-11-fastboot.zip
with MD5 0d59ec218061051fe415f6c8d3424b73
for 21.4.22 is delayed
Mark F
Members
- Aug 15, 2020
- 802
- 102
Here is the responce print out form the command prompt. Mine stopped on swapping banks but run second time, still on fastboot but may be someone can see something in this:
Latest Weekly,
SHA1:
9a0b44c93d43c2e7cc0932072abec7f13d0dff8b
MD5:
0d59ec218061051fe415f6c8d3424b73
Latest Weekly,
SHA1:
9a0b44c93d43c2e7cc0932072abec7f13d0dff8b
MD5:
0d59ec218061051fe415f6c8d3424b73
Code:
Microsoft Windows [Version 10.0.19042.746]
(c) 2020 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>cd C:\Xiaomi 11 Ultra\xiaomi.eu_multi_MI11Pro_MI11Ultra_21.4.15_v12-11-fastboot
C:\Xiaomi 11 Ultra\xiaomi.eu_multi_MI11Pro_MI11Ultra_21.4.15_v12-11-fastboot>windows_fastboot_first_install_with_data_format.bat
C:\Xiaomi 11 Ultra\xiaomi.eu_multi_MI11Pro_MI11Ultra_21.4.15_v12-11-fastboot>windows_fastboot_first_install_with_data_format.bat
C:\Xiaomi 11 Ultra\xiaomi.eu_multi_MI11Pro_MI11Ultra_21.4.15_v12-11-fastboot>windows_fastboot_first_install_with_data_format.bat
C:\Xiaomi 11 Ultra\xiaomi.eu_multi_MI11Pro_MI11Ultra_21.4.15_v12-11-fastboot>windows_fastboot_first_install_with_data_format.bat
C:\Xiaomi 11 Ultra\xiaomi.eu_multi_MI11Pro_MI11Ultra_21.4.15_v12-11-fastboot>windows_fastboot_first_install_with_data_format.bat
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
product: star
Sending 'dsp_ab' (65536 KB) OKAY [ 1.661s]
Writing 'dsp_ab' (bootloader) Partition dsp_a flashed successfully
(bootloader) Partition dsp_b flashed successfully
OKAY [ 0.128s]
Finished. Total time: 1.805s
Sending 'xbl_config_ab' (216 KB) OKAY [ 0.008s]
Writing 'xbl_config_ab' (bootloader) Partition xbl_config_a flashed successfully
(bootloader) Partition xbl_config_b flashed successfully
OKAY [ 0.005s]
Finished. Total time: 0.043s
Sending 'boot_ab' (196608 KB) OKAY [ 4.935s]
Writing 'boot_ab' (bootloader) Partition boot_a flashed successfully
(bootloader) Partition boot_b flashed successfully
OKAY [ 0.388s]
Finished. Total time: 5.340s
Sending 'modem_ab' (262220 KB) OKAY [ 6.649s]
Writing 'modem_ab' (bootloader) Partition modem_a flashed successfully
(bootloader) Partition modem_b flashed successfully
OKAY [ 0.497s]
Finished. Total time: 7.162s
Sending 'vbmeta_system_ab' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_ab' (bootloader) Partition vbmeta_system_a flashed successfully
(bootloader) Partition vbmeta_system_b flashed successfully
OKAY [ 0.005s]
Finished. Total time: 0.022s
Sending 'tz_ab' (3660 KB) OKAY [ 0.091s]
Writing 'tz_ab' (bootloader) Partition tz_a flashed successfully
(bootloader) Partition tz_b flashed successfully
OKAY [ 0.012s]
Finished. Total time: 0.122s
Sending 'vbmeta_ab' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta_ab' (bootloader) Partition vbmeta_a flashed successfully
(bootloader) Partition vbmeta_b flashed successfully
OKAY [ 0.005s]
Finished. Total time: 0.023s
Sending 'bluetooth_ab' (1084 KB) OKAY [ 0.016s]
Writing 'bluetooth_ab' (bootloader) Partition bluetooth_a flashed successfully
(bootloader) Partition bluetooth_b flashed successfully
OKAY [ 0.000s]
Finished. Total time: 0.047s
Sending 'abl_ab' (204 KB) OKAY [ 0.016s]
Writing 'abl_ab' (bootloader) Partition abl_a flashed successfully
(bootloader) Partition abl_b flashed successfully
OKAY [ 0.000s]
Finished. Total time: 0.016s
Sending 'cpucp_ab' (104 KB) OKAY [ 0.000s]
Writing 'cpucp_ab' (bootloader) Partition cpucp_a flashed successfully
(bootloader) Partition cpucp_b flashed successfully
OKAY [ 0.016s]
Finished. Total time: 0.031s
Sending 'dtbo_ab' (16384 KB) OKAY [ 0.406s]
Writing 'dtbo_ab' (bootloader) Partition dtbo_a flashed successfully
(bootloader) Partition dtbo_b flashed successfully
OKAY [ 0.031s]
Finished. Total time: 0.469s
Sending 'featenabler_ab' (88 KB) OKAY [ 0.000s]
Writing 'featenabler_ab' (bootloader) Partition featenabler_a flashed successfully
(bootloader) Partition featenabler_b flashed successfully
OKAY [ 0.016s]
Finished. Total time: 0.031s
Sending 'vendor_boot_ab' (3816 KB) OKAY [ 0.094s]
Writing 'vendor_boot_ab' (bootloader) Partition vendor_boot_a flashed successfully
(bootloader) Partition vendor_boot_b flashed successfully
OKAY [ 0.047s]
Finished. Total time: 0.172s
Sending 'keymaster_ab' (260 KB) OKAY [ 0.008s]
Writing 'keymaster_ab' (bootloader) Partition keymaster_a flashed successfully
(bootloader) Partition keymaster_b flashed successfully
OKAY [ 0.006s]
Finished. Total time: 0.032s
Sending 'uefisecapp_ab' (124 KB) OKAY [ 0.005s]
Writing 'uefisecapp_ab' (bootloader) Partition uefisecapp_a flashed successfully
(bootloader) Partition uefisecapp_b flashed successfully
OKAY [ 0.006s]
Finished. Total time: 0.025s
Sending 'qupfw_ab' (56 KB) OKAY [ 0.003s]
Writing 'qupfw_ab' (bootloader) Partition qupfw_a flashed successfully
(bootloader) Partition qupfw_b flashed successfully
OKAY [ 0.007s]
Finished. Total time: 0.028s
Sending 'xbl_ab' (3592 KB) OKAY [ 0.089s]
Writing 'xbl_ab' (bootloader) Partition xbl_a flashed successfully
(bootloader) Partition xbl_b flashed successfully
OKAY [ 0.020s]
Finished. Total time: 0.137s
Sending 'devcfg_ab' (52 KB) OKAY [ 0.003s]
Writing 'devcfg_ab' (bootloader) Partition devcfg_a flashed successfully
(bootloader) Partition devcfg_b flashed successfully
OKAY [ 0.007s]
Finished. Total time: 0.029s
Sending 'hyp_ab' (3604 KB) OKAY [ 0.090s]
Writing 'hyp_ab' (bootloader) Partition hyp_a flashed successfully
(bootloader) Partition hyp_b flashed successfully
OKAY [ 0.018s]
Finished. Total time: 0.132s
Sending 'imagefv_ab' (28 KB) OKAY [ 0.003s]
Writing 'imagefv_ab' (bootloader) Partition imagefv_a flashed successfully
(bootloader) Partition imagefv_b flashed successfully
OKAY [ 0.003s]
Finished. Total time: 0.022s
Sending 'shrm_ab' (48 KB) OKAY [ 0.003s]
Writing 'shrm_ab' (bootloader) Partition shrm_a flashed successfully
(bootloader) Partition shrm_b flashed successfully
OKAY [ 0.004s]
Finished. Total time: 0.022s
Sending 'aop_ab' (240 KB) OKAY [ 0.008s]
Writing 'aop_ab' (bootloader) Partition aop_a flashed successfully
(bootloader) Partition aop_b flashed successfully
OKAY [ 0.005s]
Finished. Total time: 0.030s
Sending 'cust' (418624 KB) OKAY [ 11.724s]
Writing 'cust' OKAY [ 0.006s]
Finished. Total time: 11.749s
Sending sparse 'super' 1/8 (784569 KB) OKAY [ 20.486s]
Writing 'super' OKAY [ 0.004s]
Sending sparse 'super' 2/8 (784873 KB) OKAY [ 20.529s]
Writing 'super' OKAY [ 0.009s]
Sending sparse 'super' 3/8 (786380 KB) OKAY [ 20.439s]
Writing 'super' OKAY [ 0.003s]
Sending sparse 'super' 4/8 (766276 KB) OKAY [ 20.033s]
Writing 'super' OKAY [ 0.005s]
Sending sparse 'super' 5/8 (733088 KB) OKAY [ 19.167s]
Writing 'super' OKAY [ 0.009s]
Sending sparse 'super' 6/8 (759556 KB) OKAY [ 19.850s]
Writing 'super' OKAY [ 0.002s]
Sending sparse 'super' 7/8 (768464 KB) OKAY [ 20.001s]
Writing 'super' OKAY [ 0.005s]
Sending sparse 'super' 8/8 (608684 KB) OKAY [ 15.909s]
Writing 'super' OKAY [ 0.000s]
Finished. Total time: 156.992s
Setting current slot to 'a' OKAY [ 14.390s]
Finished. Total time: 14.515s
Erasing 'metadata' OKAY [ 6.323s]
Finished. Total time: 6.436s
Erasing 'userdata' OKAY [ 0.113s]
F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 972316632 (474763 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 587] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 621] Filling nat area at offset 0x02a00000
[f2fs_write_root_inode:1210] Writing root inode (hot node), 49600 0 200 at offset 0x00300544
[f2fs_write_default_quota:1286] Writing quota data, at offset 00049c01, 00049c02
[f2fs_write_qf_inode:1377] Writing quota inode (hot node), 49600 0 200 at offset 0x00300545
[f2fs_write_default_quota:1286] Writing quota data, at offset 00049c03, 00049c04
[f2fs_write_qf_inode:1377] Writing quota inode (hot node), 49600 0 200 at offset 0x00300546
[f2fs_update_nat_root:1431] Writing nat root, at offset 0x00002a00
[f2fs_add_default_dentry_root:1628] Writing default dentry root, at offset 0x00049c00
Info: Overprovision ratio = 0.290%
Info: Overprovision segments = 1381 (GC reserved = 697)
[f2fs_write_check_point_pack: 774] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 911] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack: 938] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack: 950] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack: 961] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack: 969] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack: 989] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack:1010] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1029] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1062] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.003s]
Writing 'userdata' OKAY [ 0.008s]
Erasing 'metadata' OKAY [ 6.237s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 7.947s
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.002s
C:\Xiaomi 11 Ultra\xiaomi.eu_multi_MI11Pro_MI11Ultra_21.4.15_v12-11-fastboot>
Last edited:
I can unlock tomorrow My Bootloader, so this will Work? Just Need to follow the Instruction on the First site of this Thread or Need anything Special ?
Basically nobody knows right now. Some people are flashing, some people are getting soft bricked. We need more data. My bootloader unlocks in 3 hours and I guess I'm going to give it a shot for the greater good.
I've flashed custom ROMs on Pixels about 100 times. Xiaomi is a bit different but overall I'm really comfortable with it.
Zencooler
Members
- Aug 24, 2020
- 149
- 40
I am back and I have checked this file.
Yes, exactly. This is the version I installed on Mi 11 Ultra 12/256GB Black.
But...
What is really strange the same version of file has been flashed on my friend's smartphone: Mi 11 Ultra 12/256GB White version and everything went well.
And one more thing that could help to recognise the issue. Flashing via Fastboot went well up to the point of flashing super.img then something went wrong with next points. During the first flash the script stucked on the point:
set_active a
And after waiting for this almost one hour I cancel the scipt at this point and start from the begining with next try.
This time it went to the end but it seems that the issue is with erasing data.
Here is the full log from the point of sussessfull flash of super.img:
Code:
Writing 'super' OKAY [ 0.009s]
Finished. Total time: 209.786s
Setting current slot to 'a' OKAY [ 12.905s]
Finished. Total time: 13.033s
Erasing 'metadata' OKAY [ 4.595s]
Finished. Total time: 4.714s
Erasing 'userdata' OKAY [ 0.111s]
F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 472473560 (230699 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 572] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 606] Filling nat area at offset 0x01a00000
[f2fs_write_root_inode:1195] Writing root inode (hot node), 2ba00 0 200 at offset 0x00178688
[f2fs_write_default_quota:1271] Writing quota data, at offset 0002c001, 0002c002
[f2fs_write_qf_inode:1362] Writing quota inode (hot node), 2ba00 0 200 at offset 0x00178689
[f2fs_write_default_quota:1271] Writing quota data, at offset 0002c003, 0002c004
[f2fs_write_qf_inode:1362] Writing quota inode (hot node), 2ba00 0 200 at offset 0x00178690
[f2fs_update_nat_root:1416] Writing nat root, at offset 0x00001a00
[f2fs_add_default_dentry_root:1613] Writing default dentry root, at offset 0x0002c000
Info: Overprovision ratio = 0.420%
Info: Overprovision segments = 964 (GC reserved = 484)
[f2fs_write_check_point_pack: 759] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 896] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack: 923] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack: 935] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack: 946] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack: 954] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack: 974] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack: 995] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1014] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1047] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.006s]
Writing 'userdata' OKAY [ 0.008s]
Erasing 'metadata' OKAY [ 6.146s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 7.731s
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.010sMaybe it could help to find what is the problem?
So... can I do something to solve it?
Once again: is it possible to flash global rom using Mi Flash? Does it make sense this kind of try?
Same thing happened to a few of us, first flash paused at slot change. Afterwards we needed EDL to flash an official rom.
Are you using Mi Flash to do this or the .bat file? You shouldn't be using Mi Flash.
.EU is not global ROM. Sorry you just weren't very clear.
anyone?
"
Im wating like 10 min now, dont know what to do
"
Code:
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
product: star
Sending 'dsp_ab' (65536 KB) OKAY [ 1.582s]
Writing 'dsp_ab' (bootloader) Partition dsp_a flashed successfully
(bootloader) Partition dsp_b flashed successfully
OKAY [ 0.126s]
Finished. Total time: 1.720s
Sending 'xbl_config_ab' (216 KB) OKAY [ 0.007s]
Writing 'xbl_config_ab' (bootloader) Partition xbl_config_a flashed successfully
(bootloader) Partition xbl_config_b flashed successfully
OKAY [ 0.003s]
Finished. Total time: 0.020s
Sending 'boot_ab' (196608 KB) OKAY [ 4.602s]
Writing 'boot_ab' (bootloader) Partition boot_a flashed successfully
(bootloader) Partition boot_b flashed successfully
OKAY [ 0.385s]
Finished. Total time: 4.997s
Sending 'modem_ab' (240556 KB) OKAY [ 5.823s]
Writing 'modem_ab' (bootloader) Partition modem_a flashed successfully
(bootloader) Partition modem_b flashed successfully
OKAY [ 0.461s]
Finished. Total time: 6.294s
Sending 'vbmeta_system_ab' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_ab' (bootloader) Partition vbmeta_system_a flashed successfully
(bootloader) Partition vbmeta_system_b flashed successfully
OKAY [ 0.002s]
Finished. Total time: 0.015s
Sending 'tz_ab' (3660 KB) OKAY [ 0.086s]
Writing 'tz_ab' (bootloader) Partition tz_a flashed successfully
(bootloader) Partition tz_b flashed successfully
OKAY [ 0.008s]
Finished. Total time: 0.104s
Sending 'vbmeta_ab' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_ab' (bootloader) Partition vbmeta_a flashed successfully
(bootloader) Partition vbmeta_b flashed successfully
OKAY [ 0.003s]
Finished. Total time: 0.014s
Sending 'bluetooth_ab' (1084 KB) OKAY [ 0.026s]
Writing 'bluetooth_ab' (bootloader) Partition bluetooth_a flashed successfully
(bootloader) Partition bluetooth_b flashed successfully
OKAY [ 0.004s]
Finished. Total time: 0.042s
Sending 'abl_ab' (204 KB) OKAY [ 0.007s]
Writing 'abl_ab' (bootloader) Partition abl_a flashed successfully
(bootloader) Partition abl_b flashed successfully
OKAY [ 0.012s]
Finished. Total time: 0.029s
Sending 'cpucp_ab' (104 KB) OKAY [ 0.004s]
Writing 'cpucp_ab' (bootloader) Partition cpucp_a flashed successfully
(bootloader) Partition cpucp_b flashed successfully
OKAY [ 0.003s]
Finished. Total time: 0.017s
Sending 'dtbo_ab' (16384 KB) OKAY [ 0.380s]
Writing 'dtbo_ab' (bootloader) Partition dtbo_a flashed successfully
(bootloader) Partition dtbo_b flashed successfully
OKAY [ 0.030s]
Finished. Total time: 0.419s
Sending 'featenabler_ab' (88 KB) OKAY [ 0.003s]
Writing 'featenabler_ab' (bootloader) Partition featenabler_a flashed successfully
(bootloader) Partition featenabler_b flashed successfully
OKAY [ 0.003s]
Finished. Total time: 0.017s
Sending 'vendor_boot_ab' (3816 KB) OKAY [ 0.090s]
Writing 'vendor_boot_ab' (bootloader) Partition vendor_boot_a flashed successfully
(bootloader) Partition vendor_boot_b flashed successfully
OKAY [ 0.010s]
Finished. Total time: 0.112s
Sending 'keymaster_ab' (260 KB) OKAY [ 0.007s]
Writing 'keymaster_ab' (bootloader) Partition keymaster_a flashed successfully
(bootloader) Partition keymaster_b flashed successfully
OKAY [ 0.003s]
Finished. Total time: 0.021s
Sending 'uefisecapp_ab' (124 KB) OKAY [ 0.004s]
Writing 'uefisecapp_ab' (bootloader) Partition uefisecapp_a flashed successfully
(bootloader) Partition uefisecapp_b flashed successfully
OKAY [ 0.003s]
Finished. Total time: 0.017s
Sending 'qupfw_ab' (56 KB) OKAY [ 0.002s]
Writing 'qupfw_ab' (bootloader) Partition qupfw_a flashed successfully
(bootloader) Partition qupfw_b flashed successfully
OKAY [ 0.003s]
Finished. Total time: 0.016s
Sending 'xbl_ab' (3592 KB) OKAY [ 0.089s]
Writing 'xbl_ab' (bootloader) Partition xbl_a flashed successfully
(bootloader) Partition xbl_b flashed successfully
OKAY [ 0.010s]
Finished. Total time: 0.109s
Sending 'devcfg_ab' (52 KB) OKAY [ 0.002s]
Writing 'devcfg_ab' (bootloader) Partition devcfg_a flashed successfully
(bootloader) Partition devcfg_b flashed successfully
OKAY [ 0.003s]
Finished. Total time: 0.015s
Sending 'hyp_ab' (3604 KB) OKAY [ 0.085s]
Writing 'hyp_ab' (bootloader) Partition hyp_a flashed successfully
(bootloader) Partition hyp_b flashed successfully
OKAY [ 0.012s]
Finished. Total time: 0.107s
Sending 'imagefv_ab' (28 KB) OKAY [ 0.002s]
Writing 'imagefv_ab' (bootloader) Partition imagefv_a flashed successfully
(bootloader) Partition imagefv_b flashed successfully
OKAY [ 0.002s]
Finished. Total time: 0.015s
Sending 'shrm_ab' (48 KB) OKAY [ 0.002s]
Writing 'shrm_ab' (bootloader) Partition shrm_a flashed successfully
(bootloader) Partition shrm_b flashed successfully
OKAY [ 0.003s]
Finished. Total time: 0.015s
Sending 'aop_ab' (240 KB) OKAY [ 0.008s]
Writing 'aop_ab' (bootloader) Partition aop_a flashed successfully
(bootloader) Partition aop_b flashed successfully
OKAY [ 0.002s]
Finished. Total time: 0.020s
Sending 'cust' (418624 KB)"Zencooler
Members
- Aug 24, 2020
- 149
- 40
BAT file of course (not Mi Flash).
The most important thing is that I flashed latest stable rom (xiaomi.eu_multi_MI11Pro_MI11Ultra_V12.5.2.0.RKACNXM_v12-11-fastboot) with MD5: 18e56d60def6bc08fd57c8bbe7730092
and this is happend on that version.
So, guys, please be carrefull !!!
- Feb 11, 2012
- 11,595
- 322
please try these steps..
- Download Platform-tools 30.0.4 https://dl.google.com/android/repository/platform-tools_r30.0.4-windows.zip
- Unpack it
- open command line in unpacked folder
- run command
- fastboot reboot
- Download Platform-tools 30.0.4 https://dl.google.com/android/repository/platform-tools_r30.0.4-windows.zip
- Unpack it
- open command line in unpacked folder
- run command
fastboot -w- fastboot reboot
okay. What about me? Im stuck in CMD like 30 min, can I close the window and open it once again?
I haven't flashed yet, but I've got platform tools 31.0.1 on my PC. Would you recommend using the older version of the time being as it relates to the Mi 11 Ultra?
I have a general question. For those who are getting soft bricked. Are you using CMD or Powershell?
- Feb 11, 2012
- 11,595
- 322
yes, we want to check if latest make.f2fs 1.14.0 isnt causing these issues..
so try older platform-tools 30.0.4 with make.f2fs 1.13.0
Similar threads
