[GUIDE][alioth] How to install Xiaomi.eu ROM for Xiaomi Redmi K40


C

Ciprzx

Members
Jun 7, 2021
9
15
angyone1 said:
what??? o_O
the main reason why I switched to xiaomi.eu is to no longer have the Poco launcher buggy and without animations ... and what do you do, flash the xiaomi.eu and install the Poco launcher? lololol don't you notice it doesn't have app opening and closing animations?
Click to expand...
I installed Xiaomi.eu because is without ads, it doesn't bother me that poco launcher is without animation
 
  • Like
Reactions: LOLO9393
S

sunil87658

Members
Aug 31, 2021
1
3
hi, I am on latest Indian stable Miui 12.5 version. Can I flash latest EU beta fastboot rom? Bootloader is unlocked. Should i just click First_install_with_data_format_bat.rom? and also do I need to change the device name in this bat.rom file?
 
A

angyone1

Members
Aug 7, 2018
126
40
sunil87658 said:
hi, I am on latest Indian stable Miui 12.5 version. Can I flash latest EU beta fastboot rom? Bootloader is unlocked. Should i just click First_install_with_data_format_bat.rom? and also do I need to change the device name in this bat.rom file?
Click to expand...
no new fastboot rom for poco f3... latest fastboot rom are xiaomi.eu_multi_HMK40_POCOF3_21.4.22_v12-11-fastboot.... from april...
 
LOLO9393

LOLO9393

Members
Feb 8, 2016
2,903
322
sunil87658 said:
hi, I am on latest Indian stable Miui 12.5 version. Can I flash latest EU beta fastboot rom? Bootloader is unlocked. Should i just click First_install_with_data_format_bat.rom? and also do I need to change the device name in this bat.rom file?
Click to expand...
You mustn't use this old premise rom.
You must download latest Weekly or Stable and install it via TWRP.
just boot it in fastboot and install the rom latest.
 
TaFN07

TaFN07

Members
Apr 2, 2019
84
30
My phone model is Mi 11 i and I want to ask what is the procedure for switching from the global to the European version. From what I read there is no TWRP for haydn. For Mi 11i you can use TWRP from k40 pro if there is one? can someone help please with the steps to follow to pass on I. I applied for bootloader unlock and I have to wait 168 hours.
IMG_20210902_185207.jpg
IMG_20210902_135120.jpg
 
Last edited:
gogocar62

gogocar62

Members
Apr 22, 2021
617
182
TaFN07 said:
My phone model is Mi 11 i and I want to ask what is the procedure for switching from the global to the European version. From what I read there is no TWRP for haydn. For Mi 11i you can use TWRP from k40 pro if there is one? can someone help please with the steps to follow to pass on I. I applied for bootloader unlock and I have to wait 168 hours.
Click to expand...
Here is the installation guide for xiaomi.eu ROM for your model (haydn)
 
  • Like
Reactions: TaFN07
O

owninthefoam

Members
Sep 14, 2021
4
5
Can someone please help me.
I have new k40 with Chinese ROM. I followed the guide for first install xiaomi.eu ROM.

But it is now not booting.

When running windows_fastboot_first_install_with_data_format.bat in administrator CMD I get the following:

Code: 
Finished. Total time: 0.031s
Erasing 'userdata'                                 OKAY [  0.094s]

        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 = 472760280 (230839 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

And then a windows program crash popup,
"make_f2fs.exe has stopped working"

Could it be because I didn't enable developer mode and/or OEM unlocking / USB debugging?
The guide didn't say to do it so I didn't think about it.

I don't know what to do next. My phones stuck on boot screen :'(

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: alioth
product: alioth
Sending 'dsp_ab' (65536 KB) OKAY [ 1.801s]
Writing 'dsp_ab' (bootloader) Partition dsp_a flashed successfully
(bootloader) Partition dsp_b flashed successfully
OKAY [ 0.212s]
Finished. Total time: 2.042s
Sending 'xbl_config_ab' (100 KB) OKAY [ 0.011s]
Writing 'xbl_config_ab' (bootloader) Partition xbl_config_a flashed successfully
(bootloader) Partition xbl_config_b flashed successfully
OKAY [ 0.012s]
Finished. Total time: 0.048s
Sending 'boot_ab' (131072 KB) OKAY [ 3.411s]
Writing 'boot_ab' (bootloader) Partition boot_a flashed successfully
(bootloader) Partition boot_b flashed successfully
OKAY [ 0.416s]
Finished. Total time: 3.856s
Sending 'modem_ab' (257132 KB) OKAY [ 6.894s]
Writing 'modem_ab' (bootloader) Partition modem_a flashed successfully
(bootloader) Partition modem_b flashed successfully
OKAY [ 0.803s]
Finished. Total time: 7.726s
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.008s]
Finished. Total time: 0.035s
Sending 'tz_ab' (3104 KB) OKAY [ 0.090s]
Writing 'tz_ab' (bootloader) Partition tz_a flashed successfully
(bootloader) Partition tz_b flashed successfully
OKAY [ 0.014s]
Finished. Total time: 0.129s
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.006s]
Finished. Total time: 0.040s
Sending 'bluetooth_ab' (412 KB) OKAY [ 0.023s]
Writing 'bluetooth_ab' (bootloader) Partition bluetooth_a flashed successfully
(bootloader) Partition bluetooth_b flashed successfully
OKAY [ 0.008s]
Finished. Total time: 0.062s
Sending 'abl_ab' (204 KB) OKAY [ 0.015s]
Writing 'abl_ab' (bootloader) Partition abl_a flashed successfully
(bootloader) Partition abl_b flashed successfully
OKAY [ 0.007s]
Finished. Total time: 0.050s
Sending 'dtbo_ab' (32768 KB) OKAY [ 0.875s]
Writing 'dtbo_ab' (bootloader) Partition dtbo_a flashed successfully
(bootloader) Partition dtbo_b flashed successfully
OKAY [ 0.109s]
Finished. Total time: 1.015s
Sending 'featenabler_ab' (88 KB) OKAY [ 0.008s]
Writing 'featenabler_ab' (bootloader) Partition featenabler_a flashed successfully
(bootloader) Partition featenabler_b flashed successfully
OKAY [ 0.008s]
Finished. Total time: 0.044s
Sending 'vendor_boot_ab' (1556 KB) OKAY [ 0.045s]
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.084s
Sending 'keymaster_ab' (256 KB) OKAY [ 0.010s]
Writing 'keymaster_ab' (bootloader) Partition keymaster_a flashed successfully
(bootloader) Partition keymaster_b flashed successfully
OKAY [ 0.006s]
Finished. Total time: 0.046s
Sending 'uefisecapp_ab' (124 KB) OKAY [ 0.006s]
Writing 'uefisecapp_ab' (bootloader) Partition uefisecapp_a flashed successfully
(bootloader) Partition uefisecapp_b flashed successfully
OKAY [ 0.008s]
Finished. Total time: 0.052s
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.007s]
Finished. Total time: 0.037s
Sending 'xbl_ab' (3464 KB) OKAY [ 0.099s]
Writing 'xbl_ab' (bootloader) Partition xbl_a flashed successfully
(bootloader) Partition xbl_b flashed successfully
OKAY [ 0.022s]
Finished. Total time: 0.155s
Sending 'cmnlib_ab' (384 KB) OKAY [ 0.017s]
Writing 'cmnlib_ab' (bootloader) Partition cmnlib_a flashed successfully
(bootloader) Partition cmnlib_b flashed successfully
OKAY [ 0.008s]
Finished. Total time: 0.051s
Sending 'cmnlib64_ab' (500 KB) OKAY [ 0.018s]
Writing 'cmnlib64_ab' (bootloader) Partition cmnlib64_a flashed successfully
(bootloader) Partition cmnlib64_b flashed successfully
OKAY [ 0.010s]
Finished. Total time: 0.061s
Sending 'devcfg_ab' (56 KB) OKAY [ 0.004s]
Writing 'devcfg_ab' (bootloader) Partition devcfg_a flashed successfully
(bootloader) Partition devcfg_b flashed successfully
OKAY [ 0.008s]
Finished. Total time: 0.045s
Sending 'hyp_ab' (436 KB) OKAY [ 0.010s]
Writing 'hyp_ab' (bootloader) Partition hyp_a flashed successfully
(bootloader) Partition hyp_b flashed successfully
OKAY [ 0.008s]
Finished. Total time: 0.053s
Sending 'imagefv_ab' (20 KB) OKAY [ 0.003s]
Writing 'imagefv_ab' (bootloader) Partition imagefv_a flashed successfully
(bootloader) Partition imagefv_b flashed successfully
OKAY [ 0.007s]
Finished. Total time: 0.045s
Sending 'aop_ab' (200 KB) OKAY [ 0.012s]
Writing 'aop_ab' (bootloader) Partition aop_a flashed successfully
(bootloader) Partition aop_b flashed successfully
OKAY [ 0.006s]
Finished. Total time: 0.043s
Sending 'cust' (417604 KB) OKAY [ 10.438s]
Writing 'cust' OKAY [ 0.001s]
Finished. Total time: 10.720s
Sending sparse 'super' 1/7 (741089 KB) OKAY [ 19.446s]
Writing 'super' OKAY [ 0.001s]
Sending sparse 'super' 2/7 (781660 KB) OKAY [ 19.932s]
Writing 'super' OKAY [ 0.002s]
Sending sparse 'super' 3/7 (771052 KB) OKAY [ 20.155s]
Writing 'super' OKAY [ 0.001s]
Sending sparse 'super' 4/7 (769024 KB) OKAY [ 21.292s]
Writing 'super' OKAY [ 0.001s]
Sending sparse 'super' 5/7 (776132 KB) OKAY [ 26.935s]
Writing 'super' OKAY [ 0.002s]
Sending sparse 'super' 6/7 (758172 KB) OKAY [ 20.392s]
Writing 'super' OKAY [ 0.001s]
Sending sparse 'super' 7/7 (687924 KB) OKAY [ 16.972s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 164.356s
Setting current slot to 'a' OKAY [ 0.003s]
Finished. Total time: 35.668s
Erasing 'metadata' OKAY [ 0.002s]
Finished. Total time: 0.031s
Erasing 'userdata' OKAY [ 0.094s]

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 = 472760280 (230839 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
 
gogocar62

gogocar62

Members
Apr 22, 2021
617
182
Everything is in the instructions I provided. What more do you need?

Proceed from point 5.
After starting TWRP, insert the zip. ROM to phone.
 
  • Like
Reactions: Poney70
O

owninthefoam

Members
Sep 14, 2021
4
5
gogocar62 said:
Everything is in the instructions I provided. What more do you need?

Proceed from point 5.
After starting TWRP, insert the zipper. ROM to phone.
Click to expand...
Thank you I got it installed.
However how can I put the ROM onto the phone storage if it won't boot? Is there a way for me to do it through adb or something ?
 
D

dominicsyyy

Members
Mar 27, 2021
5
13
installed xiaomi 12.5.14 and still having problems with third party sms app not having dual sim support, any fix for this? thanks
 
P

pistap

Members
Oct 7, 2021
19
5
hello everyone, i installed xiaomi.eu weekly. I would love to go back to stock miui. Can I flash through Nebrassy recovery? So from xiaomi.eu to miui stable through twrp. Or can you only install through fasboot? Thanks very much.
 
LOLO9393

LOLO9393

Members
Feb 8, 2016
2,903
322
pistap said:
hello everyone, i installed xiaomi.eu weekly. I would love to go back to stock miui. Can I flash through Nebrassy recovery? So from xiaomi.eu to miui stable through twrp. Or can you only install through fasboot? Thanks very much.
Click to expand...
Why do you post different question at different place?
stop spamming!
 
P

pistap

Members
Oct 7, 2021
19
5
LOLO9393 said:
Why do you post different question at different place?
stop spamming!
Click to expand...
This is not spam! I need help because I can't flash. I want to go back to stock miui. That's all. Unfortunately there are problems with mi flash tool. I'm 60+ now and I don't joke anymore.
 
Last edited:
LOLO9393

LOLO9393

Members
Feb 8, 2016
2,903
322
pistap said:
PC With Intel processor. I can run adb commands, sideload, install twrp, flash xiaomi.eu and other rom, only miui eea doesn't work. Xiaomi tool gets stuck when super flashing comes. „Super" is not flashed, installation crashes. Here is my problem:


Thanks
9728bb7b7dce7f6edce5c95b54842737.jpg
Click to expand...
Your third screenshot has the msg to be understood. It is blurred and we can't read it for you.
What is the reported mismatch in object made of?
 
Last edited:
You must log in or register to reply here.

Similar threads

ingbrzy
[GUIDE][haydn] How to install Xiaomi.eu ROM for Xiaomi Redmi K40 Pro
Replies
137
Views
42K
Xiaomi Redmi K40 / Pro / Plus
kleiders3010
K
ingbrzy
  • Sticky
[GUIDE][odin] How to install Xiaomi.eu ROM for Xiaomi MIX 4
Replies
68
Views
11K
Xiaomi MIX 4
katerpanne
katerpanne
gogocar62
How to install Xiaomi.eu ROM for Redmi K40 / Poco F3 / Mi 11X
Replies
168
Views
44K
Xiaomi Redmi K40 / Pro / Plus
gogocar62
gogocar62
ingbrzy
  • Sticky
[GUIDE] How to install Xiaomi.eu ROM for Xiaomi MI10S
Replies
44
Views
14K
Xiaomi Mi 10/Pro /10Lite/Ultra/10T/Pro/Lite/10S
katerpanne
katerpanne
ingbrzy
  • Sticky
[GUIDE][sweet] How to install Xiaomi.eu ROM for Xiaomi Redmi Note 10 Pro
Replies
90
Views
37K
Xiaomi Redmi Note 10 / Pro
Invisible
Invisible
Top Bottom