[GUIDE][venus|star|mars] How to install Xiaomi.eu ROM for Xiaomi MI11 / Pro / Ultra


deepblue2000

Members
Apr 14, 2017
823
102
Im not sure if I'm allowed to post this but did anyone try this method?


Regards

Sent from my MI 8 Explorer Edition using Tapatalk
yeah I saw this too, I have downloaded this miflashpro (and Qualcomm_QDLoader_HS-USB_Driver), I can sign in and it says that my computer is now bound. would be interesting if it is working, then the users dont have to pay anymore

But I got no bricked phone to test ;)
 
Last edited:

Zencooler

Members
Aug 24, 2020
133
40
Guys, can you please confirm - if somebody of you is on the Global rom on Mi 11 Ultra - if SafetyNet is passed and what is widevine level on this specific rom?
Thanks in advance.
 

Zencooler

Members
Aug 24, 2020
133
40
yeah I saw this too, I have downloaded this miflashpro (and Qualcomm_QDLoader_HS-USB_Driver), I can sign in and it says that my computer is now bound. would be interesting if it is working, then the users dont have to pay anymore

But I got no bricked phone to test ;)
How did you get this miflashpro to download? The link from the Cyanogenmod page (listed above) doesn't work.
Can you give the link you used for downloading, please?

Thank you. Regards!
 

jmikepr

Members
Apr 22, 2021
53
10
Wooooooww. YESSSS SO PUMPED. $90 to edl services later. (2 different guys highly recommend Unbrick.RU) And a full day of banging my head. I Flashed to 12.5.2 .EU from Global 12.0.1. Did nothing different than the other times it bricked.

Global 12.0.1 to .EU is the way to go.
 

deepblue2000

Members
Apr 14, 2017
823
102
so for Pro/Ultra CN devices is the advise to:

unlock bootloader --> install global 12.0.1 --> Install Xiaomi.eu Stable 12.5.2 (we know now, global 12.0.1 to stable 12.5.2 xiaomi.eu works without bricks)
and after that, there should be no problem to switch to weekly and do the updates each week. or update the stable if there is a stable update.
(windows update bat)

(for other users)
 
Last edited:

TheDJVG

Members
Mar 28, 2019
33
20
Is there a reason why xiaomi.eu_multi_MI11Pro_MI11Ultra_V12.0.13.0.RKACNXM_v12-11-fastboot.zip has been removed from the stable downloads? If it has been removed in favor of xiaomi.eu_multi_MI11Pro_MI11Ultra_V12.5.2.0.RKACNXM_v12-11-fastboot.zip does the latter now pass SafetyNet? I'm not looking to root/magisk.
 

garyc

Members
Apr 20, 2021
33
10
so for Pro/Ultra CN devices is the advise to:

unlock bootloader --> install global 12.0.1 --> Install Xiaomi.eu Stable 12.5.2 (we know now, global 12.0.1 to stable 12.5.2 xiaomi.eu works without bricks)
and after that, there should be no problem to switch to weekly and do the updates each week. or update the stable if there is a stable update.
(windows update bat)

(for other users)
I'm on EEA 12.0.6 but will try again a little later.
 

jmikepr

Members
Apr 22, 2021
53
10
Can someone tell me what the font is on China ROM. I do not like the font on .EU. It's the same as Global. I want to see if I can use the China ROM font.
 

4fun20

Members
Feb 18, 2021
93
30
Hi, just unlocked the BL :)
prepareing now.
Mi 11 ultra CN Model 12GB RAM/256GB ROM.
Starting from CN12.0.13 to EU.MIUI 12.1= xiaomi.eu_multi_MI11Pro_MI11Ultra_V12.5.2.0.RKACNXM_v12-11-fastboot
usb debugging = on
usb debugging (security) = off

Wish me luck xD

DONE! MIUI is booting.
HEre is my Log:
Code:
Microsoft Windows [Version 10.0.19042.928]
(c) Microsoft Corporation. Alle Rechte vorbehalten.

C:\WINDOWS\system32>cd C:\Users\XXXX\Desktop\mi11rom\xiaomi.eu_multi_MI11Pro_MI11Ultra_V12.5.2.0.RKACNXM_v12-11-fastboot

C:\Users\XXXX\Desktop\mi11rom\xiaomi.eu_multi_MI11Pro_MI11Ultra_V12.5.2.0.RKACNXM_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.572s]
Writing 'dsp_ab'                                   (bootloader) Partition dsp_a flashed successfully
(bootloader) Partition dsp_b flashed successfully
OKAY [  0.129s]
Finished. Total time: 1.709s
Sending 'xbl_config_ab' (216 KB)                   OKAY [  0.006s]
Writing 'xbl_config_ab'                            (bootloader) Partition xbl_config_a flashed successfully
(bootloader) Partition xbl_config_b flashed successfully
OKAY [  0.004s]
Finished. Total time: 0.021s
Sending 'boot_ab' (196608 KB)                      OKAY [  4.714s]
Writing 'boot_ab'                                  (bootloader) Partition boot_a flashed successfully
(bootloader) Partition boot_b flashed successfully
OKAY [  0.389s]
Finished. Total time: 5.112s
Sending 'modem_ab' (240556 KB)                     OKAY [  5.768s]
Writing 'modem_ab'                                 (bootloader) Partition modem_a flashed successfully
(bootloader) Partition modem_b flashed successfully
OKAY [  0.459s]
Finished. Total time: 6.238s
Sending 'vbmeta_system_ab' (4 KB)                  OKAY [  0.002s]
Writing 'vbmeta_system_ab'                         (bootloader) Partition vbmeta_system_a flashed successfully
(bootloader) Partition vbmeta_system_b flashed successfully
OKAY [  0.003s]
Finished. Total time: 0.016s
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.009s]
Finished. Total time: 0.104s
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.003s]
Finished. Total time: 0.016s
Sending 'bluetooth_ab' (1084 KB)                   OKAY [  0.028s]
Writing 'bluetooth_ab'                             (bootloader) Partition bluetooth_a flashed successfully
(bootloader) Partition bluetooth_b flashed successfully
OKAY [  0.005s]
Finished. Total time: 0.044s
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.003s]
Finished. Total time: 0.020s
Sending 'cpucp_ab' (104 KB)                        OKAY [  0.005s]
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.394s]
Writing 'dtbo_ab'                                  (bootloader) Partition dtbo_a flashed successfully
(bootloader) Partition dtbo_b flashed successfully
OKAY [  0.039s]
Finished. Total time: 0.442s
Sending 'featenabler_ab' (88 KB)                   OKAY [  0.004s]
Writing 'featenabler_ab'                           (bootloader) Partition featenabler_a flashed successfully
(bootloader) Partition featenabler_b flashed successfully
OKAY [  0.003s]
Finished. Total time: 0.018s
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.009s]
Finished. Total time: 0.110s
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.003s]
Finished. Total time: 0.022s
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.003s]
Finished. Total time: 0.018s
Sending 'qupfw_ab' (56 KB)                         OKAY [  0.004s]
Writing 'qupfw_ab'                                 (bootloader) Partition qupfw_a flashed successfully
(bootloader) Partition qupfw_b flashed successfully
OKAY [  0.004s]
Finished. Total time: 0.016s
Sending 'xbl_ab' (3592 KB)                         OKAY [  0.085s]
Writing 'xbl_ab'                                   (bootloader) Partition xbl_a flashed successfully
(bootloader) Partition xbl_b flashed successfully
OKAY [  0.010s]
Finished. Total time: 0.105s
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.003s]
Finished. Total time: 0.016s
Sending 'hyp_ab' (3604 KB)                         OKAY [  0.089s]
Writing 'hyp_ab'                                   (bootloader) Partition hyp_a flashed successfully
(bootloader) Partition hyp_b flashed successfully
OKAY [  0.012s]
Finished. Total time: 0.110s
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.016s
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.003s]
Finished. Total time: 0.016s
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.003s]
Finished. Total time: 0.021s
Sending 'cust' (418624 KB)                         OKAY [  9.640s]
Writing 'cust'                                     OKAY [  0.010s]
Finished. Total time: 9.989s
Sending sparse 'super' 1/8 (784625 KB)             OKAY [ 18.527s]
Writing 'super'                                    OKAY [  0.004s]
Sending sparse 'super' 2/8 (784913 KB)             OKAY [ 18.605s]
Writing 'super'                                    OKAY [  0.008s]
Sending sparse 'super' 3/8 (786380 KB)             OKAY [ 18.659s]
Writing 'super'                                    OKAY [  0.007s]
Sending sparse 'super' 4/8 (781276 KB)             OKAY [ 18.537s]
Writing 'super'                                    OKAY [  0.005s]
Sending sparse 'super' 5/8 (736004 KB)             OKAY [ 17.480s]
Writing 'super'                                    OKAY [  0.006s]
Sending sparse 'super' 6/8 (784616 KB)             OKAY [ 18.618s]
Writing 'super'                                    OKAY [  0.009s]
Sending sparse 'super' 7/8 (785216 KB)             OKAY [ 18.614s]
Writing 'super'                                    OKAY [  0.003s]
Sending sparse 'super' 8/8 (386452 KB)             OKAY [  9.198s]
Writing 'super'                                    OKAY [  0.003s]
Finished. Total time: 149.379s
Setting current slot to 'a'                        OKAY [ 12.982s]
Finished. Total time: 13.114s
Erasing 'metadata'                                 OKAY [  4.798s]
Finished. Total time: 4.912s
Erasing 'userdata'                                 OKAY [  0.233s]

        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.004s]
Writing 'userdata'                                 OKAY [  0.011s]
Erasing 'metadata'                                 OKAY [  6.130s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 6.947s
Rebooting                                          OKAY [  0.001s]
Finished. Total time: 0.002s
 
Last edited:

jmikepr

Members
Apr 22, 2021
53
10
Hi, just unlocked the BL :)
prepareing now.
Starting from CN12.0.13 to EU.MIUI 12.1= xiaomi.eu_multi_MI11Pro_MI11Ultra_V12.5.2.0.RKACNXM_v12-11-fastboot
usb debugging = on
usb debugging (security) = off

Wish me luck xD

If you fail. Use edl service unbrick.ru. Go to global 12.0.1. Them flash .EU. Seems to be working for everyone.
 

4fun20

Members
Feb 18, 2021
93
30
If you fail. Use edl service unbrick.ru. Go to global 12.0.1. Them flash .EU. Seems to be working for everyone.
All done succsessfully :)

Is it safe now to flash BETA xiaomi.eu_multi_MI11Pro_MI11Ultra_21.4.21_v12-11-fastboot.zip ?
 

hjirik

Members
Jun 2, 2015
12
15
Mi 11 classic - is it ok to flash from china stable 12.5.4.0 to actual eu dev rom 21.4.*? Someone has already tried? Just last couple of days of waiting and iam gonna to flash.

Odesláno z mého Mi 9 Lite pomocí Tapatalk
 

kvbvs

Members
Apr 21, 2021
34
10
Hi guys, two questions for you (mi 11 ultra xiaomi.eu 12.5.2):
1. I didnt check this on china rom but while I turn on rear display my main screen is kinda "laggy" like 60hz
2. My rear display still wont show notification (had same problem on china)
 

Mrboombastixx

Members
Feb 14, 2021
126
40
Mi 11 classic - is it ok to flash from china stable 12.5.4.0 to actual eu dev rom 21.4.*? Someone has already tried? Just last couple of days of waiting and iam gonna to flash.

Odesláno z mého Mi 9 Lite pomocí Tapatalk
I've just flashed from CN stable 12.5.4.0 to EU ROM weekly 21.4.21 on Mi 11 "venus" with no problem at all.
 
  • Like
Reactions: hjirik

Undisputed99

Members
Apr 22, 2021
11
3
MiFlashPro 4.3.1220.29

MiFlashPro 6.3.318.42

Qualcomm_QDLoader_HS-USB_Driver_64bit

and Qualcomm_Flash_Image_Loader_v2.0.1.9
For what is that? Which one we Need? I am currently on 12.5 Stable and want to flash global 12.0.6 do i Need Those Tools?