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


Firedance61

Members
Aug 29, 2018
128
40
Question to all

is the flash process with a global MI 11 the same as with the CN version or are there differences?
 

deepblue2000

Members
Apr 14, 2017
898
182
always the same

**
but I still do not understand why so many people are bricking their Mi11s... I still belive they doing anything wrong,
there cant be an other reason, cause it is working for the most users (who doing it right)..
(I think they are not starting the cmd as admin, for it is important step, and I would not use powershell, only cmd)

As I flashed the rom the first time, I had no errors (like many others with mkfs...)
 
Last edited:

SoulOfUniverse

Members
Jan 21, 2021
51
30
always the same

**
but I still do not understand why so many people are bricking their Mi11s... I still belive they doing anything wrong,
there cant be an other reason, cause it is working for the most users (who doing it right)..
(I think they are not starting the cmd as admin, for it is important step, and I would not use powershell, only cmd)

As I flashed the rom the first time, I had no errors (like many others with mkfs...)
Ppwershell is the wrapper around standard CMD but with additional functionality from powershell

Sent from my M2011K2C using Tapatalk
 

hrdcrjnky

Members
Feb 26, 2016
14
15
To be honest I have no idea :D
I followed the instructions closely... First upgraded to the newest version, then unlocked the bootloader.
I booted one more time after unlock to make sure all is okay and then executed the script, which ran successfully. But after that only fastboot for me.

So, bad luck I guess. Don't know...
So I did it again.... :D but this time successful!
I just risked paying again for edl flashing and did exactly the same steps as last time, got the same "make_f2fs failed" error, but this time
it booted straight away. I'm almost certain that flo87 was right and I should have set up the phone again after unlocking.
But who knows...
 

Karpfenhai

Members
Jul 17, 2016
890
102
So I did it again.... :D but this time successful!
I just risked paying again for edl flashing and did exactly the same steps as last time, got the same "make_f2fs failed" error, but this time
it booted straight away. I'm almost certain that flo87 was right and I should have set up the phone again after unlocking.
But who knows...
I didn't do that but it worked for me without issues...

I also never checked oem unlock..

I got the phone, i added my account, requested unlock, checked the counter, 168 hours later I unlocked and flashed the eu Rom right after, the only thing i did was ota before flashing.

...back in January..

Regards.

Sent from my MI 8 Explorer Edition using Tapatalk
 

coolqi

Members
Feb 23, 2021
93
20
always the same

**
but I still do not understand why so many people are bricking their Mi11s... I still belive they doing anything wrong,
there cant be an other reason, cause it is working for the most users (who doing it right)..
(I think they are not starting the cmd as admin, for it is important step, and I would not use powershell, only cmd)

As I flashed the rom the first time, I had no errors (like many others with mkfs...)

My mistake is watching the video in this post, click update bat directly not the first time install bat. The vedio title is "Update guide on the video" I think it update from Miui 12 to 12.5, but actually it is update for Miui 12.5 itself.
When running in Miui 12, MUST install the first time bat, not update bat.

And also the video advise to use powershell, but actually do not need this, directly click the bat file will do, make too complex for first time installer.
 
Last edited:

Cacun

Members
Dec 24, 2016
54
20
Good Night!

Help!

I unlockbootloader succesfully and flash. at the end is error:
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: venus
product: venus
Sending 'vm-bootsys_ab' (263668 KB) OKAY [ 8.536s]
Writing 'vm-bootsys_ab' (bootloader) Partition vm-bootsys_a flashed successfully
(bootloader) Partition vm-bootsys_b flashed successfully
OKAY [ 1.199s]
Finished. Total time: 9.747s
Sending 'dsp_ab' (65536 KB) OKAY [ 2.122s]
Writing 'dsp_ab' (bootloader) Partition dsp_a flashed successfully
(bootloader) Partition dsp_b flashed successfully
OKAY [ 0.307s]
Finished. Total time: 2.442s
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.025s
Sending 'boot_ab' (196608 KB) OKAY [ 6.372s]
Writing 'boot_ab' (bootloader) Partition boot_a flashed successfully
(bootloader) Partition boot_b flashed successfully
OKAY [ 0.859s]
Finished. Total time: 7.243s
Sending 'modem_ab' (242268 KB) OKAY [ 7.855s]
Writing 'modem_ab' (bootloader) Partition modem_a flashed successfully
(bootloader) Partition modem_b flashed successfully
OKAY [ 1.052s]
Finished. Total time: 8.918s
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.004s]
Finished. Total time: 0.018s
Sending 'tz_ab' (3640 KB) OKAY [ 0.118s]
Writing 'tz_ab' (bootloader) Partition tz_a flashed successfully
(bootloader) Partition tz_b flashed successfully
OKAY [ 0.018s]
Finished. Total time: 0.146s
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.004s]
Finished. Total time: 0.015s
Sending 'bluetooth_ab' (1084 KB) OKAY [ 0.036s]
Writing 'bluetooth_ab' (bootloader) Partition bluetooth_a flashed successfully
(bootloader) Partition bluetooth_b flashed successfully
OKAY [ 0.009s]
Finished. Total time: 0.057s
Sending 'abl_ab' (204 KB) OKAY [ 0.008s]
Writing 'abl_ab' (bootloader) Partition abl_a flashed successfully
(bootloader) Partition abl_b flashed successfully
OKAY [ 0.006s]
Finished. Total time: 0.024s
Sending 'cpucp_ab' (100 KB) OKAY [ 0.004s]
Writing 'cpucp_ab' (bootloader) Partition cpucp_a flashed successfully
(bootloader) Partition cpucp_b flashed successfully
OKAY [ 0.006s]
Finished. Total time: 0.020s
Sending 'dtbo_ab' (8192 KB) OKAY [ 0.266s]
Writing 'dtbo_ab' (bootloader) Partition dtbo_a flashed successfully
(bootloader) Partition dtbo_b flashed successfully
OKAY [ 0.040s]
Finished. Total time: 0.319s
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.007s]
Finished. Total time: 0.025s
Sending 'vendor_boot_ab' (3692 KB) OKAY [ 0.120s]
Writing 'vendor_boot_ab' (bootloader) Partition vendor_boot_a flashed successfully
(bootloader) Partition vendor_boot_b flashed successfully
OKAY [ 0.028s]
Finished. Total time: 0.162s
Sending 'keymaster_ab' (260 KB) OKAY [ 0.010s]
Writing 'keymaster_ab' (bootloader) Partition keymaster_a flashed successfully
(bootloader) Partition keymaster_b flashed successfully
OKAY [ 0.007s]
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.008s]
Finished. Total time: 0.026s
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.006s]
Finished. Total time: 0.022s
Sending 'xbl_ab' (3584 KB) OKAY [ 0.118s]
Writing 'xbl_ab' (bootloader) Partition xbl_a flashed successfully
(bootloader) Partition xbl_b flashed successfully
OKAY [ 0.012s]
Finished. Total time: 0.141s
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' (3600 KB) OKAY [ 0.116s]
Writing 'hyp_ab' (bootloader) Partition hyp_a flashed successfully
(bootloader) Partition hyp_b flashed successfully
OKAY [ 0.021s]
Finished. Total time: 0.149s
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.004s]
Finished. Total time: 0.021s
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.019s
Sending 'aop_ab' (240 KB) OKAY [ 0.009s]
Writing 'aop_ab' (bootloader) Partition aop_a flashed successfully
(bootloader) Partition aop_b flashed successfully
OKAY [ 0.007s]
Finished. Total time: 0.028s
Sending 'cust' (417604 KB) OKAY [ 11.925s]
Writing 'cust' OKAY [ 0.015s]
Finished. Total time: 13.865s
Sending sparse 'super' 1/7 (738892 KB) OKAY [ 24.847s]
Writing 'super' OKAY [ 0.050s]
Sending sparse 'super' 2/7 (768540 KB) OKAY [ 25.859s]
Writing 'super' OKAY [ 0.031s]
Sending sparse 'super' 3/7 (751520 KB) OKAY [ 25.254s]
Writing 'super' OKAY [ 0.043s]
Sending sparse 'super' 4/7 (785908 KB) OKAY [ 26.512s]
Writing 'super' OKAY [ 0.004s]
Sending sparse 'super' 5/7 (768768 KB) OKAY [ 25.934s]
Writing 'super' OKAY [ 0.036s]
Sending sparse 'super' 6/7 (760128 KB) OKAY [ 25.615s]
Writing 'super' OKAY [ 0.005s]
Sending sparse 'super' 7/7 (771592 KB) OKAY [ 26.031s]
Writing 'super' OKAY [ 0.005s]
Finished. Total time: 276.826s
Setting current slot to 'a' OKAY [ 15.702s]
Finished. Total time: 15.944s
Erasing 'metadata' OKAY [ 1.154s]
Finished. Total time: 1.262s
Erasing 'userdata' OKAY [ 0.592s]

F2FS-tools: mkfs.f2fs Ver: 1.13.0 (2019-09-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 = 470990808 (229975 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 556] Filling sit area at offset 0x00600000
C:\Users\josem\Downloads\Xiaomi_MI_11\xiaomi.eu_multi_MI11_21.3.11_v12-11-fastboot\platform-tools-windows/make_f2fs failed: 3221225477
fastboot: error: Cannot generate image for userdata
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.002s
PS C:\Users\josem\Downloads\Xiaomi_MI_11\xiaomi.eu_multi_MI11_21.3.11_v12-11-fastboot>
I stucked on fastboot after flash rom

Good night again.
My smartphone is global and was purchased at the Portuguese MISTORE, it already came with the global rom.
I tried everything they say here, but nothing worked and I always go back to fastboot. The error that always gives me is in the "super" flash, as you can see in the attached images. Is it due to having unlocked bootloader and not restarting the password when unlocking?
I'm thinking of sending here to Mistore, will they refuse due to the unlock bootloader? Thank you for any contribution you can make to me.
 

Attachments

  • MiFlash1.jpg
    MiFlash1.jpg
    119.4 KB · Views: 160
  • MiFlash2.jpg
    MiFlash2.jpg
    85 KB · Views: 146

Karpfenhai

Members
Jul 17, 2016
890
102
Good night again.
My smartphone is global and was purchased at the Portuguese MISTORE, it already came with the global rom.
I tried everything they say here, but nothing worked and I always go back to fastboot. The error that always gives me is in the "super" flash, as you can see in the attached images. Is it due to having unlocked bootloader and not restarting the password when unlocking?
I'm thinking of sending here to Mistore, will they refuse due to the unlock bootloader? Thank you for any contribution you can make to me.
That could be related to a bad download (did you verify crc?) or bad usb / cable, how often did you try?

Sent from my Mi11
 

Cacun

Members
Dec 24, 2016
54
20
That could be related to a bad download (did you verify crc?) or bad usb / cable, how often did you try?

Sent from my Mi11

Hello.
Yes I checked crc.
The USB cable is the original and the two programs I tried to detect the phone. and start the whole process and flash the various phases, they only stop at the "super" flash, as you can see in the images.
 

Karpfenhai

Members
Jul 17, 2016
890
102
Hello.
Yes I checked crc.
The USB cable is the original and the two programs I tried to detect the phone. and start the whole process and flash the various phases, they only stop at the "super" flash, as you can see in the images.
You could try fastboot format system prior flashing the rom.

You gave up on .eu Rom?



Sent from my Mi11
 

Cacun

Members
Dec 24, 2016
54
20
You could try fastboot format system prior flashing the rom.

You gave up on .eu Rom?



Sent from my Mi11

How do I do that?
I stayed here on fastboot after flashing xiaomi.eu_multi_MI11_21.3.11_v12-11-fastboot, because I was in the global. I've been here since MI5, ..., MI9, MI10 and always with miaomi.eu, now on MI 11, with no twrp, I tried this fastboot but never left. I don't know what went wrong and I got the tel. in bootloop on fastboot.
 

Karpfenhai

Members
Jul 17, 2016
890
102
How do I do that?
I stayed here on fastboot after flashing xiaomi.eu_multi_MI11_21.3.11_v12-11-fastboot, because I was in the global. I've been here since MI5, ..., MI9, MI10 and always with miaomi.eu, now on MI 11, with no twrp, I tried this fastboot but never left. I don't know what went wrong and I got the tel. in bootloop on fastboot.
Creating Userdata seems to be buggy with Windows, I would try to concentrate on that since the flash process itself was working...

Note, “make_f2fs failed: 3221225477
fastboot: error: Cannot generate image for userdata“

This error usually means your Android sdk is not meant for the version you're about to install (to old) so ensure the binary which you are using is the one delivered with the rom.zip.

Also, some people advice to keep the folder name as short as possible.


Fastboot is capable of formatting / erasing particular partitions, so formatting userdata can be done by yourself, just decompile the script and see if you can do the make2fs part manually, this should render the phone working again, flash eu rom once more, maybe on native Linux?

Regards.

Sent from my MI 8 Explorer Edition using Tapatalk
 
Last edited:

Cacun

Members
Dec 24, 2016
54
20
Creating Userdata seems to be buggy with Windows, I would try to concentrate on that since the flash process itself was working...

Note, “make_f2fs failed: 3221225477
fastboot: error: Cannot generate image for userdata“

This error usually means your Android sdk is not meant for the version you're about to install (to old) so ensure the binary which you are using is the one delivered with the rom.zip.

Also, some people advice to keep the folder name as short as possible.


Fastboot is capable of formatting / erasing particular partitions, so formatting userdata can be done by yourself, just decompile the script and see if you can do the make2fs part manually, this should render the phone working again, flash eu rom once more, maybe on native Linux?

Regards.

Sent from my MI 8 Explorer Edition using Tapatalk

Thanks
I'll try
 

body-mg

Members
Feb 21, 2017
16
15
Flashed Xiaomi.eu V12.0.22.0 yesterday successfully. Thanks for the Team.

My hints (nothing new):
- Use the oldest USB-Port on PC
- unlock zipfile on win10
- use classic cmd as admin
- use c drive
- use short directory names
 

inzaghi75

Members
Jan 17, 2021
60
20
Flashed Xiaomi.eu V12.0.22.0 yesterday successfully. Thanks for the Team.

My hints (nothing new):
- Use the oldest USB-Port on PC
- unlock zipfile on win10
- use classic cmd as admin
- use c drive
- use short directory names
How is your batterylife?
 

metegun

Members
Feb 9, 2021
33
20
I'm also curious how's the Mi 11 battery life on EU ROM stable. Is it more better than the weekly ROM?

I switched from beta 21.2.25 to stable 12.0.22. I can confirm battery life is much better on the stable rom.
My recharching period went up from around every 20 hours to 28-30 hours..
 

Mrboombastixx

Members
Feb 14, 2021
126
40
I switched from beta 21.2.25 to stable 12.0.22. I can confirm battery life is much better on the stable rom.
My recharching period went up from around every 20 hours to 28-30 hours..
Excellent news, If you can share the screenshot of your battery graph it would be a massive. Thanks.
 

Cacun

Members
Dec 24, 2016
54
20
Flashed Xiaomi.eu V12.0.22.0 yesterday successfully. Thanks for the Team.

My hints (nothing new):
- Use the oldest USB-Port on PC
- unlock zipfile on win10
- use classic cmd as admin
- use c drive
- use short directory names

I tried it, but mine is still on fastboot.
Still giving the same error: C: \ xiaomi.eu \ platform-tools-windows / make_f2fs failed: 3221225477 fastboot: error: Cannot generate image for userdata.
I don't know what else to do, I'm about to give up.
 

Cacun

Members
Dec 24, 2016
54
20
Someone can explain this to me:

C:\Xiaomi\XiaomiTool2\res\tools>fastboot flash userdata userdata.img
Sending sparse 'userdata' 1/2 (738856 KB) OKAY [ 21.141s]
Writing 'userdata' OKAY [ 0.016s]
Sending sparse 'userdata' 2/2 (181376 KB) OKAY [ 10.280s]
Writing 'userdata' OKAY [ 0.678s]
Finished. Total time: 32.136s

C:\Xiaomi\XiaomiTool2\res\tools>fastboot format userdata
CreateProcess failed: O sistema não conseguiu localizar o ficheiro especificado. (2)
fastboot: error: Cannot generate image for userdata