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

[DeFOUR]

i just got stuck too :\
into

Setting current slot to 'b'/'a'

hopefully @Poney70 or @ingbrzy can help

Then you can flash back to China rom, start over again.
It works for me.

How did u flashed china Rom again?

 

[DeFOUR]

To successfully flash Xiaomi.eu "fastboot" ROMs, "update to the latest China ROM version" seems to be a bad advice for some devices... (like Mi 11 Pro, Mi 11 Ultra and so Redmi K40 Pro?)...

The only solution I know is to pay for an EDL Unbrick Service (like this one: Telegram -or- @Angeluss69) and ask them to flash a previous "China" fastboot ROM version (12.0.5.0, download link => here) and keep the bootloader unlocked.

On 12.0.5.0, finish the first setup wizard (MIUI 12 setup) then try to flash a Xiaomi.eu"fastboot" ROM again...

Also i think has to be in the first post of this thread, i fixed by edl then updated to 12.0.9 again by turning on auto updates by mistake hahaha
Bow i have to downgrade again

 

[Lim-Dul]

Well great. I don't know what's up but the MiFlash tool stopped working properly. Whenever I try to flash a Chinese ROM it just shows 'success' after 1-5 seconds and nothing happens...
I think with this behavior I won't be able to flash through EDL...

 

[max.ouyang]

Dunno if I'm following the procedure correctly, but it didn't help.
What I did was basically:
Run modified script that tried switching to slot B (set_active other), it got stuck
Pressed ctrl+C
Rebooted phone into fastboot (Power + Vol-)
Ran original script, it got stuck on switching to slot A

Pressed ctrl+C

That's the difference!
I never did this part. Just push the buttons!
After pw+vl-, the phone get into fastboot, AND the script run the rest lines!

 

[DeFOUR]

Pressed ctrl+C

That's the difference!
I never did this part. Just push the buttons!
After pw+vl-, the phone get into fastboot, AND the script run the rest lines!

Yes but for me after running the rest lines nothing happens

Anyways i got mine sorted finally and im running latest stable Xiaomi EU now
got EDL CN FW (12.0.5) and then flashed the EU ROM and all seems to be working (hopefully)
will setup my device now

 

[Lim-Dul]

OK - LOL, I have no idea how I did that. I fixed the phone. 0_o
Just random flashing with various combinations of images resulted in it working... Don't ask me how - suddenly the behavior changed. Been doing it for like 2 days straight. I am on Xiaomi.eu V12.0.9.0. Not gonna flash the newest ROM cause I'm scared now.

 

[max.ouyang]

Yes but for me after running the rest lines nothing happens

If I am right, after this, the phone boot into fastboot tokes a few more sec, and show open lock at the top.
When it happens you might succeed next flash.

 

[max.ouyang]

I

OK - LOL, I have no idea how I did that. I fixed the phone. 0_o
Just random flashing with various combinations of images resulted in it working... Don't ask me how - suddenly the behavior changed. Been doing it for like 2 days straight. I am on Xiaomi.eu V12.0.9.0. Not gonna flash the newest ROM cause I'm scared now.

I stucked for two weeks.

 

[DeFOUR]

OK - LOL, I have no idea how I did that. I fixed the phone. 0_o

Thats great, congratulations and enjoy

anyways, flash EU from CN 12.0.5 worked like a charm, now im on 12.0.9 EU and all fine
except one of my payment apps which is important hopefully i fix it ...

 

[Lim-Dul]

If I am right, after this, the phone boot into fastboot tokes a few more sec, and show open lock at the top.
When it happens you might succeed next flash.

Indeed, I sadly cannot write any kind of reliable step-by-step report what I did but it was a combination of flashing the latest Xiaomi.eu and Xiaomi.eu Stable. The original China ROM wasn't even involved since it was failing for me on flashing Super anyways (CRC error on Sparse).
I was also switching slots back and forth.
I believe I flashed Xiaomi.eu latest, it failed (on slot-switch), flashed Xiaomi.eu latest, it went through but didn't boot (Bootloader bootloop) and then I flashed Xiaomi.eu stable (same slot) and it suddenly worked... 0_o

 

[max.ouyang]

OK.
Maybe the trick is just swap slot and pw+vl- flash again.
Who knows
After my first real successful flash, I upgrade weekly rom. It works well.
Anyway, congrats.

 

[mbird]

Hello there,
Thank you xiaomi.eu-experts one million times for your very great work for public community.
Only short question. I have Xiaomi Redmi K40 Pro Plus.
My phone is bootloader unlocked and runs your fastboot ROM.
Can I later change to TWRP with OTA updates without loosing data on the phone?
When TWRP is released, can i still install it? Over the now installed fastboot ROM?
Is there a tutorial for that type of update/upgrade?
Thank you sincerely.

 

[Lim-Dul]

Hello there,
Thank you xiaomi.eu-experts one million times for your very great work for public community.
Only short question. I have Xiaomi Redmi K40 Pro Plus.
My phone is bootloader unlocked and runs your fastboot ROM.
Can I later change to TWRP with OTA updates without loosing data on the phone?
When TWRP is released, can i still install it? Over the now installed fastboot ROM?
Is there a tutorial for that type of update/upgrade?
Thank you sincerely.

I don't want to claim to be an expert, considering my problems with the fastboot ROM but the difference between the recovery and fastboot ROMs, from what I understand, is just the flashing method. That's why official ROMs also usually come in both flavors, especially the stable versions. When TWRP comes out you'll just flash the recovery partition, which won't affect all the other partitions and just switch the update method to recovery. I think the Xiaomi.eu devs will probably stop publishing fastboot ROMs at this point since in general this is a much lower level procedure with fewer safety nets and more potential for screw-ups. More screw-ups means more complaints and more support requests for the devs.

 

[Cz0rt]

I believe I flashed Xiaomi.eu latest, it failed (on slot-switch), flashed Xiaomi.eu latest, it went through but didn't boot (Bootloader bootloop) and then I flashed Xiaomi.eu stable (same slot) and it suddenly worked... 0_o

I had same problem followed above

I flashed Xiaomi.eu stable on slot b, it completed but still in boot loop
Flashed Xiaomi.eu weekly on slot a, it hanged on Setting current slot to 'a' so I rebooted phone into fastboot (Power + Vol-) it finished but went to fastboot again
Then flashed Xiaomi.eu stable on slot a and it rebooted correctly into MIUI

Why it works ? ¯\_(ツ)_/¯

Anyway thanks for tip man

 

[Lim-Dul]

I had same problem followed above

I flashed Xiaomi.eu stable on slot b, it completed but still in boot loop
Flashed Xiaomi.eu weekly on slot a, it hanged on Setting current slot to 'a' so I rebooted phone into fastboot (Power + Vol-) it finished but went to fastboot again
Then flashed Xiaomi.eu stable on slot a and it rebooted correctly into MIUI

Why it works ? ¯\_(ツ)_/¯

Anyway thanks for tip man

Cool! So together with @max.ouyang 's observations we're getting close to a reliable solution to the bootloop problem. I have to admit, I managed to soft-brick my phone again after fixing it by trying to flash Xiaomi.eu 21.4.22 but also managed to unbrick it as well by using a similar procedure. I think Power + Vol- is optional, so is the slot-switching, the important thing is:
1. Flash 21.4.22, get stuck on 'setting current slot to a'
2. Either Ctrl+C out of the script or Reboot via Power + Vol-
3. RE-flash 21.4.22 for good measure - it will still be in a bootloop but switch slots successfuly (important part is getting the script to run through fully at least once, if you got it to complete via Power + Vol- you might skip this step but don't complain if this doesn't work)
4. Flash Xiaomi.eu V12.0.9.0.RKKCNXM stable

The main warning I'd put out there is to NOT use the unstable builds (d'oh) as they seem to be causing problems for at least some users/devices depending on what official ROM version you're coming from. If you really want to flash at this point, stick with stable and just flash weekly after you manage to successfully flash stable first (and it might still not work like in my case).

P.S. It's funny that I went through all this trouble when the phone is not usable for me as a daily driver until a reliable rooting process via TWRP is possible; won't be manually patching any boot images with Magisk and do any more fastboot chores for sure.

 

[Alhex]

Hi Guys,
I need your Help. I boot my K40 Pro into Fastboot and Connect it to my PC with the original USB-C Cable on a USB 2.0 Port. USB Debugging is active and Bootloader is unlocked. But after i click on the windows_fastboot_update_rom.bat with Admin rights my Device didnt start the Flash procedure. The Flash Script doesnt start. Its like i did nothing. Its the same with the windows_fastboot_first_install_with_data_format.bat. I come from MIUI 12.0.4.0(RKBMIXM) Global.
I am grateful for any advice.

 

[Lim-Dul]

Hi Guys,
I need your Help. I boot my K40 Pro into Fastboot and Connect it to my PC with the original USB-C Cable on a USB 2.0 Port. USB Debugging is active and Bootloader is unlocked. But after i click on the windows_fastboot_update_rom.bat with Admin rights my Device didnt start the Flash procedure. The Flash Script doesnt start. Its like i did nothing. Its the same with the windows_fastboot_first_install_with_data_format.bat. I come from MIUI 12.0.4.0(RKBMIXM) Global.
I am grateful for any advice.

Don't click on the script. Open up a command prompt or powershell window with elevated privileges, navigate to the directory where the scripts are and then execute them by typing in the name.

 

[Alhex]

Don't click on the script. Open up a command prompt or powershell window with elevated privileges, navigate to the directory where the scripts are and then execute them by typing in the name.

I tried it that way and I got the same result.
Edit: I found the Reason. The ADB Drivers wasnt installed. Thx

 

[KiraYoshikage]

Ok, so I have a freshly bought k40 pro and it's running 12.0.9.0 stable with its bootloader unlocked. Which EU rom can I flash safely? I've been reading about so many bricks in this thread and I'm scared to hell and back. Any help would be appreciated it as I haven't flashed a rom in years, I want to come back to the power user scene but Xiaomi is so different and confusing.

 

[Lim-Dul]

Ok, so I have a freshly bought k40 pro and it's running 12.0.9.0 stable with its bootloader unlocked. Which EU rom can I flash safely? I've been reading about so many bricks in this thread and I'm scared to hell and back. Any help would be appreciated it as I haven't flashed a rom in years, I want to come back to the power user scene but Xiaomi is so different and confusing.

First things first is not having anything of importance on your new phone. If that's the case, then you can flash away and pray to the fastboot gods that it works as you will be able to unbrick eventually.

My post-factum advice, considering how much time unbricking cost me (though I think we have this procedure down by now), would be: wait till TWRP is out.

 

[KiraYoshikage]

First things first is not having anything of importance on your new phone. If that's the case, then you can flash away and pray to the fastboot gods that it works as you will be able to unbrick eventually.

My post-factum advice, considering how much time unbricking cost me (though I think we have this procedure down by now), would be: wait till TWRP is out.

Your story scared me the most ngl chief :')

If I'm on 12.0.9.0 then I'm supposed to use xiaomi.eu_multi_HMK40Pro_MI11i_V12.0.9.0.RKKCNXM_v12-11-fastboot correct? Like nothing else is actually needed? Also did you flash the correct rom yourself that had a stable release before u got the brick? I was genuinely confused as to what caused yours.

Also is there any news on them releasing TWRP for newer devices? From what I can see most new devices have no TWRP right now.

 

[Lim-Dul]

Your story scared me the most ngl chief :')

If I'm on 12.0.9.0 then I'm supposed to use xiaomi.eu_multi_HMK40Pro_MI11i_V12.0.9.0.RKKCNXM_v12-11-fastboot correct? Like nothing else is actually needed? Also did you flash the correct rom yourself that had a stable release before u got the brick? I was genuinely confused as to what caused yours

I was on the latest China ROM through the updater and the first ROM I flashed was the weekly ROM, which never worked for me, even after a cycle of 2 successful flashes/unbricks. Now I'm at V12.0.9.0.RKKCNXM indeed.
Generally, if your flash fails (e.g. upon swiching slots, which is what most people got hung up on according to the thread), you should still be able to go to Xiaomi.eu V12.0.9.0.RKKCNXM.
Funnily enough, I'm unable to go back to China stable anymore though.

Precautions to take, just to maximize luck:
* Use a USB 2.0 port (I used USB-C to USB-C initially)
* Run the script in an elevated prompt/PowerShell session

Other than that it's just executing the batch file and hoping for the best.

 

[KiraYoshikage]

I was on the latest China ROM through the updater and the first ROM I flashed was the weekly ROM, which never worked for me, even after a cycle of 2 successful flashes/unbricks. Now I'm at V12.0.9.0.RKKCNXM indeed.
Generally, if your flash fails (e.g. upon swiching slots, which is what most people got hung up on according to the thread), you should still be able to go to Xiaomi.eu V12.0.9.0.RKKCNXM.
Funnily enough, I'm unable to go back to China stable anymore though.

Precautions to take, just to maximize luck:
* Use a USB 2.0 port (I used USB-C to USB-C initially)
* Run the script in an elevated prompt/PowerShell session

Other than that it's just executing the batch file and hoping for the best.

Which exactly was the weekly rom exactly? Aren't the weekly roms only meant to be used after the eu rom is already installed or am I referring to sth else completely?

Dumb question but how exactly do I run the script in an elevated prompt/PowerShell session?

So using the official type-c to usb on one of my usb 2.0 ports on my motherboard so work just fine?

Many thanks for the replies!

 

[Lim-Dul]

Which exactly was the weekly rom exactly? Aren't the weekly roms only meant to be used after the eu rom is already installed or am I referring to sth else completely?

Dumb question but how exactly do I run the script in an elevated prompt/PowerShell session?

So using the official type-c to usb on one of my usb 2.0 ports on my motherboard so work just fine?

Many thanks for the replies!

1. It was xiaomi.eu_multi_HMK40Pro_MI11i_21.4.22_v12-11-fastboot.zip and it was around a week ago. It never worked for me, even when flashing from Xiaomi.eu stable.
2. One way to do it: Press the Windows button. Type in powershell and right-click on the shortcut that pops up in the search, select 'Run as Administrator' in the menu. You then need to navigate to the script directory via (a) cd command(s)and then execute the script in its directory by invoking .\windows_fastboot_first_install_with_data_format.bat

If the above sounds daunting or incomprehensible to you, then, without any prejudice, dissing or patronizing, you should probably not do it or you'll end up paying 30-35 USD to some Russian EDL flashing service (as I was close to do!).

3. Yes. It's probably superstition but then I pretty much ignored all the advice and it didn't work for me, so what do I know. The successful flashes I did carry out with the provided cable and suck-o-ports (USB 2.0).

 

[KiraYoshikage]

Yeah, I'll just stick with Poco Launcher and some other nice tweaks that make the Chinese rom bearable. I pretty much comprehend all of this, even got the powershell to run the proper script but I just pussied out. It's not worth the risk, I just want this phone to be an emulation beast and thats pretty much it. I'll root it and flash a global rom when it's safe with a TWRP. Thanks for all the advice nonetheless!!