How to install Xiaomi.eu ROM for devices A/B


Thank You Mark, I didn't knew that there was any answer on this thread as I was thinking I would get an alert by mail so sorry if I didn't answer. Anyway I've tried again on my laptop, installed everything and used a usual samsung usb cable and it worked first try ! So I'm enjoying that custom rom for a few days since. Waiting for MiUI 13 now !
 
  • Like
Reactions: Mark F
Hello.
I have Mi 11 Lite 5G. Unlocked the bootloader and installed weekly xiaomi.eu (22.2.9).
How can i update it now? The Updater app shows me there is update but nothing happens?
 
Update of A12 devices via Fastboot:
- Download our ROM zip file
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system:
- wait until the phone restarts itself

--- For Windows OS - windows_fastboot_update_rom.bat
--- For Linux - linux_fastboot_update_rom.sh
--- For MacOS - macos_fastboot_update_rom.sh
 
  • Like
Reactions: JakSpoon
gogocar62 said:
Update of A12 devices via Fastboot:
- Download our ROM zip file
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system:
- wait until the phone restarts itself

--- For Windows OS - windows_fastboot_update_rom.bat
--- For Linux - linux_fastboot_update_rom.sh
--- For MacOS - macos_fastboot_update_rom.sh
Click to expand...

Thanks @gogocar62 for all this tutorial updates!

One question:
I have a mi 11 ultra with unlocked bootloader, in which I installed the EU 12.5.20 rom through your guide a few months ago, using the TWRP.

Now, if I wanted to upgrade to MIUI 13, would it be enough for me to follow your updated procedure, without any particular adjustments? In this case I will lose the TWRP right? will I be able to safely put it back when the suitable ROM arrives, and no longer in fastboot mode?
 
- If you want to upgrade to MIUI 13 follow the instructions. You do not have to make any adjustments, the data will be preserved.
- Yes, you will lose TWRP. When the recovery ROM is released, you will update in TWRP. (You start TWRP from PC)
 
  • Love
Reactions: JakSpoon
Sorry for not understanding but is there an install option via TWRP for the Mi 11 Lite 5G (renoir)?

In the list it only says fastboot but on https://xiaomifirmwareupdater.com/miui/renoir/ there is a recovery ROM? Just not sure if it's trustworthy or if I'm better off with the fastboot mode?

Thank you all so much for your kind help :)
 
Sorry for not understanding but is there an install option via TWRP for the Mi 11 Lite 5G (renoir)?
Click to expand...
No, it doesn't exist.

In the list it only says fastboot but on https://xiaomifirmwareupdater.com/miui/renoir/ there is a recovery ROM?
Click to expand...
I don't understand why you refer to the official ROM when you want to install a ROM from xiaomi.eu ?

If you are downloading a ROM or following instructions from other sources, then do not seek support here.
 
Last edited:
  • Like
Reactions: JakSpoon and katerpanne
Hi guys, TWRP is not working with MIUI 13? I installed EU ROM but TWRP cant find my storage at all.
 
TWRP does not work on Android 12. It cannot decrypt the data partition (if the screen lock is set).
For this reason, the fastboot installation / upgrade method is used.
 
  • Like
Reactions: katerpanne and JakSpoon
The repository can then be displayed.
It depends on which recovery version (TWRP, OF, etc.) and phone model.
 
I have Mi 11 Lite 5G (renoir),
I was on global stable MIUI 12.5, I unlocked the bootloader, and clicked `windows_fastboot_first_install_with_data_format.bat` to install EU MIUI 13 rom.
After installation, my device was stuck in boot menu.

What should I do now?
 
katerpanne said:
dont click… look in how to and look for any issues in the cmd window

Click to expand...

I tried install via fastboot again, this is the CMD output:

Code: 
D:\Android\Mi115G\xiaomi.eu_multi_MI11Lite5G_V13.0.7.0.SKICNXM_v13-12-fastboot>windows_fastboot_first_install_with_data_format.bat
Waiting for device...
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
Setting current slot to 'a'                        OKAY [  0.008s]
Finished. Total time: 0.009s
Sending 'dsp_a' (65536 KB)                         OKAY [  1.680s]
Writing 'dsp_a'                                    OKAY [  0.256s]
Finished. Total time: 1.965s
Sending 'dsp_b' (65536 KB)                         OKAY [  1.529s]
Writing 'dsp_b'                                    OKAY [  0.216s]
Finished. Total time: 1.753s
Sending 'xbl_config_a' (212 KB)                    OKAY [  0.008s]
Writing 'xbl_config_a'                             OKAY [  0.002s]
Finished. Total time: 0.026s
Sending 'xbl_config_b' (212 KB)                    OKAY [  0.006s]
Writing 'xbl_config_b'                             OKAY [  0.002s]
Finished. Total time: 0.017s
Sending 'boot_a' (196608 KB)                       OKAY [  5.022s]
Writing 'boot_a'                                   OKAY [  0.663s]
Finished. Total time: 5.696s
Sending 'boot_b' (196608 KB)                       OKAY [  4.606s]
Writing 'boot_b'                                   OKAY [  0.672s]
Finished. Total time: 5.288s
Sending 'modem_a' (197084 KB)                      OKAY [  5.063s]
Writing 'modem_a'                                  OKAY [  0.695s]
Finished. Total time: 5.773s
Sending 'modem_b' (197084 KB)                      OKAY [  4.633s]
Writing 'modem_b'                                  OKAY [  0.673s]
Finished. Total time: 5.315s
Sending 'vbmeta_system_a' (4 KB)                   OKAY [  0.002s]
Writing 'vbmeta_system_a'                          OKAY [  0.001s]
Finished. Total time: 0.019s
Sending 'vbmeta_system_b' (4 KB)                   OKAY [  0.002s]
Writing 'vbmeta_system_b'                          OKAY [  0.001s]
Finished. Total time: 0.011s
Sending 'tz_a' (3592 KB)                           OKAY [  0.093s]
Writing 'tz_a'                                     OKAY [  0.015s]
Finished. Total time: 0.118s
Sending 'tz_b' (3592 KB)                           OKAY [  0.084s]
Writing 'tz_b'                                     OKAY [  0.018s]
Finished. Total time: 0.111s
Sending 'vbmeta_a' (4 KB)                          OKAY [  0.002s]
Writing 'vbmeta_a'                                 OKAY [  0.001s]
Finished. Total time: 0.013s
Sending 'vbmeta_b' (4 KB)                          OKAY [  0.002s]
Writing 'vbmeta_b'                                 OKAY [  0.002s]
Finished. Total time: 0.011s
Sending 'bluetooth_a' (1228 KB)                    OKAY [  0.034s]
Writing 'bluetooth_a'                              OKAY [  0.008s]
Finished. Total time: 0.051s
Sending 'bluetooth_b' (1228 KB)                    OKAY [  0.029s]
Writing 'bluetooth_b'                              OKAY [  0.008s]
Finished. Total time: 0.046s
Sending 'abl_a' (204 KB)                           OKAY [  0.007s]
Writing 'abl_a'                                    OKAY [  0.003s]
Finished. Total time: 0.018s
Sending 'abl_b' (204 KB)                           OKAY [  0.006s]
Writing 'abl_b'                                    OKAY [  0.003s]
Finished. Total time: 0.017s
Sending 'cpucp_a' (128 KB)                         OKAY [  0.004s]
Writing 'cpucp_a'                                  OKAY [  0.002s]
Finished. Total time: 0.016s
Sending 'cpucp_b' (128 KB)                         OKAY [  0.005s]
Writing 'cpucp_b'                                  OKAY [  0.003s]
Finished. Total time: 0.018s
Sending 'dtbo_a' (16384 KB)                        OKAY [  0.421s]
Writing 'dtbo_a'                                   OKAY [  0.054s]
Finished. Total time: 0.484s
Sending 'dtbo_b' (16384 KB)                        OKAY [  0.384s]
Writing 'dtbo_b'                                   OKAY [  0.055s]
Finished. Total time: 0.446s
Sending 'featenabler_a' (88 KB)                    OKAY [  0.003s]
Writing 'featenabler_a'                            OKAY [  0.002s]
Finished. Total time: 0.023s
Sending 'featenabler_b' (88 KB)                    OKAY [  0.004s]
Writing 'featenabler_b'                            OKAY [  0.003s]
Finished. Total time: 0.015s
Sending 'vendor_boot_a' (5908 KB)                  OKAY [  0.153s]
Writing 'vendor_boot_a'                            OKAY [  0.021s]
Finished. Total time: 0.184s
Sending 'vendor_boot_b' (5908 KB)                  OKAY [  0.140s]
Writing 'vendor_boot_b'                            OKAY [  0.022s]
Finished. Total time: 0.170s
Sending 'keymaster_a' (260 KB)                     OKAY [  0.009s]
Writing 'keymaster_a'                              OKAY [  0.003s]
Finished. Total time: 0.022s
Sending 'keymaster_b' (260 KB)                     OKAY [  0.008s]
Writing 'keymaster_b'                              OKAY [  0.004s]
Finished. Total time: 0.021s
Sending 'uefisecapp_a' (124 KB)                    OKAY [  0.005s]
Writing 'uefisecapp_a'                             OKAY [  0.004s]
Finished. Total time: 0.018s
Sending 'uefisecapp_b' (124 KB)                    OKAY [  0.004s]
Writing 'uefisecapp_b'                             OKAY [  0.004s]
Finished. Total time: 0.018s
Sending 'qupfw_a' (56 KB)                          OKAY [  0.003s]
Writing 'qupfw_a'                                  OKAY [  0.002s]
Finished. Total time: 0.013s
Sending 'qupfw_b' (56 KB)                          OKAY [  0.003s]
Writing 'qupfw_b'                                  OKAY [  0.001s]
Finished. Total time: 0.013s
Sending 'xbl_a' (3392 KB)                          OKAY [  0.089s]
Writing 'xbl_a'                                    OKAY [  0.007s]
Finished. Total time: 0.106s
Sending 'xbl_b' (3392 KB)                          OKAY [  0.082s]
Writing 'xbl_b'                                    OKAY [  0.006s]
Finished. Total time: 0.096s
Sending 'devcfg_a' (48 KB)                         OKAY [  0.003s]
Writing 'devcfg_a'                                 OKAY [  0.002s]
Finished. Total time: 0.013s
Sending 'devcfg_b' (48 KB)                         OKAY [  0.002s]
Writing 'devcfg_b'                                 OKAY [  0.001s]
Finished. Total time: 0.012s
Sending 'hyp_a' (3580 KB)                          OKAY [  0.094s]
Writing 'hyp_a'                                    OKAY [  0.016s]
Finished. Total time: 0.119s
Sending 'hyp_b' (3580 KB)                          OKAY [  0.085s]
Writing 'hyp_b'                                    OKAY [  0.017s]
Finished. Total time: 0.112s
Sending 'imagefv_a' (2048 KB)                      OKAY [  0.062s]
Writing 'imagefv_a'                                OKAY [  0.012s]
Finished. Total time: 0.082s
Sending 'imagefv_b' (2048 KB)                      OKAY [  0.057s]
Writing 'imagefv_b'                                OKAY [  0.012s]
Finished. Total time: 0.077s
Sending 'shrm_a' (48 KB)                           OKAY [  0.003s]
Writing 'shrm_a'                                   OKAY [  0.002s]
Finished. Total time: 0.013s
Sending 'shrm_b' (48 KB)                           OKAY [  0.003s]
Writing 'shrm_b'                                   OKAY [  0.001s]
Finished. Total time: 0.013s
Sending 'aop_a' (204 KB)                           OKAY [  0.007s]
Writing 'aop_a'                                    OKAY [  0.004s]
Finished. Total time: 0.020s
Sending 'aop_b' (204 KB)                           OKAY [  0.006s]
Writing 'aop_b'                                    OKAY [  0.003s]
Finished. Total time: 0.019s
Sending 'cust' (415132 KB)                         OKAY [  9.800s]
Writing 'cust'                                     OKAY [  0.005s]
Finished. Total time: 10.741s
Sending sparse 'super' 1/9 (721176 KB)             OKAY [ 17.354s]
Writing 'super'                                    OKAY [  0.011s]
Sending sparse 'super' 2/9 (738176 KB)             OKAY [ 17.834s]
Writing 'super'                                    OKAY [  0.001s]
Sending sparse 'super' 3/9 (768968 KB)             OKAY [ 18.569s]
Writing 'super'                                    OKAY [  0.002s]
Sending sparse 'super' 4/9 (732308 KB)             OKAY [ 17.711s]
Writing 'super'                                    OKAY [  0.011s]
Sending sparse 'super' 5/9 (725396 KB)             OKAY [ 17.707s]
Writing 'super'                                    OKAY [  0.005s]
Sending sparse 'super' 6/9 (779116 KB)             OKAY [ 18.814s]
Writing 'super'                                    OKAY [  0.002s]
Sending sparse 'super' 7/9 (786316 KB)             OKAY [ 18.925s]
Writing 'super'                                    OKAY [  0.010s]
Sending sparse 'super' 8/9 (786360 KB)             OKAY [ 18.957s]
Writing 'super'                                    OKAY [  0.007s]
Sending sparse 'super' 9/9 (88732 KB)              OKAY [  5.911s]
Writing 'super'                                    OKAY [  3.069s]
Finished. Total time: 174.868s
Erasing 'metadata'                                 OKAY [ 10.540s]
Finished. Total time: 10.723s
Erasing 'metadata'                                 OKAY [  0.020s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 0.044s
Setting current slot to 'a'                        OKAY [  0.008s]
Finished. Total time: 0.010s
Rebooting                                          OKAY [  0.000s]
Finished. Total time: 0.002s

D:\Android\Mi115G\xiaomi.eu_multi_MI11Lite5G_V13.0.7.0.SKICNXM_v13-12-fastboot>

Device still boot into recovery menu.

Edit:
I have to manually wipe in recovery menu in order to boot normally!
 
Last edited:
gogocar62 said:
The repository can then be displayed.
It depends on which recovery version (TWRP, OF, etc.) and phone model.
Click to expand...
So what's the problem for recovery android 12 roms [for example original global roms]?
Do I understand well? First disable all locks [fingerprint, pattern.] then install miui 13, then root if needed], after that when the twrp is no needed set all locks again.

Wysłane z mojego M2101K9G przy użyciu Tapatalka
 
Is there a problem with the Xiaomi stable mi11 lite 5g 13.0.8 ? Im trying to download it all night but the download speed is so slow (20 kb/s) that goes to 0 after 2 minutes and automatically cancel the process. Tried with Edge and chrome.
Sem título.png
 
Is there a default sim for messages/sms ? It prompts me every time whne I send a text to select the SIM. Is there a default to select SMS. Like calls and data is fine. But no option to send sms a default SMS. Please design an option to send default sms sim in Mi 11 - venus. if anyone is aware of the settings, please advise, Appreciate it. Thanks.
 
guicorassi said:
Is there a problem with the Xiaomi stable mi11 lite 5g 13.0.8 ? Im trying to download it all night but the download speed is so slow (20 kb/s) that goes to 0 after 2 minutes and automatically cancel the process. Tried with Edge and chrome.View attachment 41422
Click to expand...
It has to be a problem with your server. It took 50 seconds to download the 3.9 gb
 
Help please.

I tried to use the fastboot method to install the EU ROM now my mi 11 ultra is stuck on fastboot mode.
 
If you came from a different ROM, you must use the fastboot format command due to possible partition differences between them.
 
hi i have this version xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.5.0.SKACNXM_v13-12-fastboot.zip
how to update via windows to the new version without losing anything
 
You must log in or register to reply here.

Similar threads

A
Unlock HyperOS Bootloader on Chinese Device
Replies
13
Views
11K
Questions & Answers
ujvagyok
U
M
Stuck on boot loop after installing ROM!
Replies
5
Views
2K
Questions & Answers
medesnabbt
M
P
How to root RN13 (sapphire)?
Replies
6
Views
3K
Questions & Answers
pragyanone
P
emfSilverson
Joyeuse: GBoard voice typing not working
Replies
0
Views
639
Redmi Note 9S / Pro / Max / ProEU
emfSilverson
emfSilverson
ingbrzy
  • Locked
HyperOS 1.0 24.7.28 (Final)
Replies
292
Views
245K
HyperOS
Igor Eisberg
Igor Eisberg
Top Bottom
Back