[GUIDE] How to install Xiaomi.eu ROM for Redmi Note 9 Pro EU


And back to joyous talk, I'm awaiting the 11.0.5 fastboot version to be re-released.
With twrp only from 3rd parties or people doing their own modifications and system locked and boot loops etc I'd rather use fastboot for now until we get a twrp version that's officially announced as supported by the Xiaomi.EU team.

I was not really surprised reading earlier that a few people here are willing to risk bricking their devices for the latest firmware minutes after its uploaded.
Please remember people that updating a phone can be like updating your computer or bios especially if it's not from the official company there's a risk that you will end up with a completely dead device with your photos etc lost and will have to buy a new phone.

It is always better to slightly wait and see how the firmware behaves in the wild before updating your phone.

Haven't we learned that and got it into our heads already from companies like Microsoft with their Windows 10 releases and updates?

If you want to be one of those on the front remember that you end up testing what may have bugs that get fixed for others that wait.
If you don't want possibilities of bugs you should wait.

Also why do some of you crave a new version?
It's not like it suddenly changes the way how you receive calls messages and use apps.
And in fact I see many demanding to update only to then want to downgrade because somehow there battery life seemed shorter or there were bugs etc.

Be smart and if you are technical and skilled then yes you can try if not it's better to wait a bit than to think your cool by having the latest the day of release.

We really so much on technology that we should make sure things are stable and meets our needs.
 
  • Like
Reactions: MrEasy, Yemble, Manjula Fernando and 1 other person
drguild said:
And back to joyous talk, I'm awaiting the 11.0.5 fastboot version to be re-released.
With twrp only from 3rd parties or people doing their own modifications and system locked and boot loops etc I'd rather use fastboot for now until we get a twrp version that's officially announced as supported by the Xiaomi.EU team.

I was not really surprised reading earlier that a few people here are willing to risk bricking their devices for the latest firmware minutes after its uploaded.
Please remember people that updating a phone can be like updating your computer or bios especially if it's not from the official company there's a risk that you will end up with a completely dead device with your photos etc lost and will have to buy a new phone.

It is always better to slightly wait and see how the firmware behaves in the wild before updating your phone.

Haven't we learned that and got it into our heads already from companies like Microsoft with their Windows 10 releases and updates?

If you want to be one of those on the front remember that you end up testing what may have bugs for others that wait.
If you don't want possibilities of bugs you should wait.

Also why do some of you crave a new version?
It's not like it suddenly changes the way how you receive calls messages and use apps.
And in fact I see many demanding to update only to then want to downgrade because somehow there battery life seemed shorter or there were bugs etc.

Be smart and if you are technical and skilled then yes you can try if not it's better to wait a bit than to think your cool by having the latest the day of release.

We really so much on technology that we should make sure things are stable and meets our needs.
Click to expand...
You said:
"'until we get a twrp version that's officially announced as supported by the Xiaomi.EU team.'
TWRP are not under EU DEV responsibility, so forget your expectation.
 
LOLO9393 said:
You said:
"'until we get a twrp version that's officially announced as supported by the Xiaomi.EU team.'
TWRP are not under EU DEV responsibility, so forget your expectation.
Click to expand...
I know Xiaomi.EU do not make twrp.
But if they are going to only release a version that relies on twrp or a 3rd party flasher and not fastboot or OTA to flash then they should make sure both the flasher and their rom is working on said device so people know that a certain version is what they support to flash their rom.

Remember to install a rom we need to put it on somehow.

If we get a rom without a flasher or one that bricks or has issues with devices then the ROM maker is kinda slightly responsible for providing that way as the only method and not testing or promoting methods to properly and safely install there rom.

Think about it as this if there was no fastboot version and no twrp that worked or was safe or ended up bricking devices and no one could install and run the rom here then it's that not somehow on the rom developers for releasing and promoting a rom that no one can use our safely without testing things if flasher bricks devices or whatever because it's somehow not there reasonability?

Also from the first post.

We will release fastboot ROM versions until TWRP for joyeuse is released.

Which means they will need to announce a compatible safe and working supported TWRP version at some stage as OTA relies on it also as per first post.
So yep I'll keep using fastboot and wait till they announce that compatible version instead of these twrp versions with various levels of support before using twrp for this.
 
Last edited:
  • Like
Reactions: Yemble, Manjula Fernando, sir_bazz and 2 others
"We will release fastboot ROM versions until TWRP for joyeuse is released"

Why is there no fastboot ROM for V11.0.5?
 
Tschoran said:
"We will release fastboot ROM versions until TWRP for joyeuse is released"

Why is there no fastboot ROM for V11.0.5?
Click to expand...
It is because you have a TWRP and it is normal way to upgrade EU rom for everybody via OTA. Just mind it.
 
LOLO9393 said:
It is because you have a TWRP and it is normal way to upgrade EU rom for everybody via OTA. Just mind it.
Click to expand...
Actually it's because they did release a fastboot but pulled it due to boot loop if you read above.
So they are probably working on redoing the fastboot version.

Also the Xiaomi firmware update site has the 11.0.5 as global the EEA is 11.0.4 still.

As for the twrp there's no fully supported version yet it's what people have made compatible and if you read the dedicated thread it seems you have to follow a exact procedure else any deviation will result in the rom not booting.

I'm just awaiting a fastboot version when they are ready.
People for the last few versions have said no more fastboot versions because we now have twrp, that's just incorrect as there has not been a official announcement from the developers here about such thing.

So people please stop spreading false info unless you have a official announcement to link to that there will be no more fastboot versions.
 
Tschoran said:
There is still no OFFICIAL TWRP.
Click to expand...
Local ROM for phone Mi Max3 also use unofficial TWRP from LR.Team - its because unofficial TWRP is better than original TWRP.
Unofficial TWRP for Redmi Note 9/9S is from LR.TEAM.
 
drguild said:
Actually it's because they did release a fastboot but pulled it due to boot loop if you read above.
So they are probably working on redoing the fastboot version.

Also the Xiaomi firmware update site has the 11.0.5 as global the EEA is 11.0.4 still.

As for the twrp there's no fully supported version yet it's what people have made compatible and if you read the dedicated thread it seems you have to follow a exact procedure else any deviation will result in the rom not booting.

I'm just awaiting a fastboot version when they are ready.
People for the last few versions have said no more fastboot versions because we now have twrp, that's just incorrect as there has not been a official announcement from the developers here about such thing.

So people please stop spreading false info unless you have a official announcement to link to that there will be no more fastboot versions.
Click to expand...
If you need to live "official" you have better to stay stock rom and don't expect thing that people here are can not give you.
 
  • Like
Reactions: Austrofred
drguild said:
So people please stop spreading false info unless you have a official announcement to link to that there will be no more fastboot versions.
Click to expand...
I have information that the new versions will only be Recovery versions to TWRP. Because we already have TWRP for both Note 9 Pro and 9S.
And the new version will be there only when the new global ROM is released, ie the number 11.0.6. or higher.
 
rbarat said:
I have information that the new versions will only be Recovery versions to TWRP. Because we already have TWRP for both Note 9 Pro and 9S.
And the new version will be there only when the new global ROM is released, ie the number 11.0.6. or higher.
Click to expand...
Can you post some verified info please a link to the source the emails with the headers etc to back up your post.

I would just be happy if a developer tag came here and told us direct what's going on.

And who said I needed the official rom etc.
I've been a IT tech and enthusiast for years.
Did not say anything about awaiting a official twrp or rom.
Just an announcement from the actual team here themselves than just us generals on this forum thinking we know what the developers here haven't actually said.

Please don't read into that I'm all official. This is a stable rom from a decent team unlike the single people on XDA making there own versions.
 
Last edited:
  • Like
Reactions: MrEasy and Yemble
drguild said:
Can you post some verified info please a link to the source the emails with the headers etc to back up your post.
Click to expand...
In addition to this website, there is also a Czech and Slovak website https://www.miuios.cz/, which is operated by the same people as the website https://xiaomi.eu/ Somewhere there I got that info.

I don't understand what you're talking about. It is better for authors to develop recovery versions of ROM, this is the normal way. For Redmi Note 9 Pro / 9S, they made a Fastboot version just because it wasn't TWRP. And since TWRP already exists, there is no need to bother with the Fastboot version.
This closes this topic to me.
 
Last edited:
  • Like
Reactions: LOLO9393
Tschoran said:
That was not my question. I don´t want to brick my phone with an unofficial TWRP.
Click to expand...
Sure it's possible, but the fact that you dont seem to know about how, you can easily mess something up and there were also reported Problems with the fastboot Version for 11.0.5 i would recommend you to wait or go with TWRP as it is more likely that you mess up with fastboot than with the already confirmed working TWRP.
Kindly regards
 
Hi,
I got my Redmi 9 Pro EU 9 days ago and already unlocked it. Following the instructions for installing (first page of this thread) the version xiaomi.eu_multi_HMNote9ProEU_V11.0.2.0.QJZMIXM_v11-10-fastboot
The phone boots and i checked the version, it was Xiaomi.eu V11.0.2

Today I try to install the Version xiaomi.eu_multi_HMNote9ProEU_V11.0.4.0.QJZMIXM_v11-10-fastboot but now I get this Error:
C:\xiaomi.eu_multi_HMNote9ProEU_V11.0.4.0.QJZMIXM_v11-10-fastboot>windows_fastboot_update_rom.bat
product: joyeuse
product: joyeuse
Sending 'boot' (15096 KB) OKAY [ 0.359s]
Writing 'boot' OKAY [ 0.067s]
Finished. Total time: 0.435s
Sending sparse 'super' 1/6 (786384 KB) OKAY [ 18.568s]
Writing 'super' OKAY [ 0.001s]
Sending sparse 'super' 2/6 (777826 KB) OKAY [ 19.230s]
Writing 'super' OKAY [ 0.000s]
Sending sparse 'super' 3/6 (775280 KB) OKAY [ 19.020s]
Writing 'super' OKAY [ 0.000s]
Sending sparse 'super' 4/6 (783919 KB) OKAY [ 27.262s]
Writing 'super' OKAY [ 0.000s]
Sending sparse 'super' 5/6 (786287 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
Sending 'cust' (34144 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
Sending 'cmnlib64' (503 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
Sending 'imagefv' (20 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
Sending 'cmnlib' (387 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
Sending 'hyp' (386 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
Sending 'keymaster' (232 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
Sending 'tz' (2919 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
Sending 'aop' (159 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
Sending 'xbl_config' (63 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
Sending 'bluetooth' (892 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
Sending 'uefisecapp' (123 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
Sending 'modem' (130636 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
Sending 'qupfw' (52 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
Sending 'abl' (204 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
Sending 'dsp' (32768 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
Sending 'devcfg' (42 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
Sending 'storsec' (20 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
Click to expand...

Any ideas?
thanks in advance


30 min later.....

Phone boots only to fastboot, so I installed xiaomi.eu_multi_HMNote9ProEU_V11.0.2.0.QJZMIXM_v11-10-fastboot again.
During FW Update I got the following errors, but the phone boots to Miui11 installation and I can start the Setup

Code: 
C:\xiaomi.eu_multi_HMNote9ProEU_V11.0.2.0.QJZMIXM_v11-10-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: joyeuse
product: joyeuse
Sending 'boot' (15096 KB)                          OKAY [  0.356s]
Writing 'boot'                                     OKAY [  0.066s]
Finished. Total time: 0.431s
Sending sparse 'super' 1/6 (779269 KB)             OKAY [ 18.526s]
Writing 'super'                                    OKAY [  0.001s]
Sending sparse 'super' 2/6 (778187 KB)             OKAY [ 19.210s]
Writing 'super'                                    OKAY [  0.001s]
Sending sparse 'super' 3/6 (734666 KB)             OKAY [ 18.020s]
Writing 'super'                                    OKAY [  0.000s]
Sending sparse 'super' 4/6 (785732 KB)             OKAY [ 21.571s]
Writing 'super'                                    OKAY [  0.001s]
Sending sparse 'super' 5/6 (784436 KB)             OKAY [ 27.351s]
Writing 'super'                                    OKAY [  0.001s]
Sending sparse 'super' 6/6 (298450 KB)             OKAY [ 17.220s]
Writing 'super'                                    OKAY [  0.000s]
Finished. Total time: 127.993s
fastboot: error: cannot load 'firmware-update/recovery.img': No such file or directory
Sending 'abl' (204 KB)                             OKAY [  0.010s]
Writing 'abl'                                      OKAY [  0.002s]
Finished. Total time: 0.021s
Sending 'ablbak' (204 KB)                          OKAY [  0.007s]
Writing 'ablbak'                                   OKAY [  0.004s]
Finished. Total time: 0.020s
Sending 'aop' (159 KB)                             OKAY [  0.007s]
Writing 'aop'                                      OKAY [  0.003s]
Finished. Total time: 0.018s
Sending 'aopbak' (159 KB)                          OKAY [  0.007s]
Writing 'aopbak'                                   OKAY [  0.002s]
Finished. Total time: 0.018s
Sending 'bluetooth' (892 KB)                       OKAY [  0.029s]
Writing 'bluetooth'                                OKAY [  0.007s]
Finished. Total time: 0.044s
Sending 'cmnlib' (387 KB)                          OKAY [  0.012s]
Writing 'cmnlib'                                   OKAY [  0.004s]
Finished. Total time: 0.024s
Sending 'cmnlibbak' (387 KB)                       OKAY [  0.015s]
Writing 'cmnlibbak'                                OKAY [  0.005s]
Finished. Total time: 0.028s
Sending 'cmnlib64' (503 KB)                        OKAY [  0.015s]
Writing 'cmnlib64'                                 OKAY [  0.007s]
Finished. Total time: 0.042s
Sending 'cmnlib64bak' (503 KB)                     OKAY [  0.013s]
Writing 'cmnlib64bak'                              OKAY [  0.005s]
Finished. Total time: 0.028s
Sending 'devcfg' (42 KB)                           OKAY [  0.006s]
Writing 'devcfg'                                   OKAY [  0.002s]
Finished. Total time: 0.016s
Sending 'devcfgbak' (42 KB)                        OKAY [  0.009s]
Writing 'devcfgbak'                                OKAY [  0.002s]
Finished. Total time: 0.019s
Sending 'dsp' (32768 KB)                           OKAY [  0.758s]
Writing 'dsp'                                      OKAY [  0.139s]
Finished. Total time: 0.905s
Sending 'dtbo' (8192 KB)                           OKAY [  0.199s]
Writing 'dtbo'                                     OKAY [  0.038s]
Finished. Total time: 0.246s
Sending 'hyp' (385 KB)                             OKAY [  0.013s]
Writing 'hyp'                                      OKAY [  0.007s]
Finished. Total time: 0.028s
Sending 'hypbak' (385 KB)                          OKAY [  0.012s]
Writing 'hypbak'                                   OKAY [  0.007s]
Finished. Total time: 0.029s
Sending 'imagefv' (20 KB)                          OKAY [  0.003s]
Writing 'imagefv'                                  OKAY [  0.002s]
Finished. Total time: 0.014s
Sending 'keymaster' (232 KB)                       OKAY [  0.009s]
Writing 'keymaster'                                OKAY [  0.003s]
Finished. Total time: 0.020s
Sending 'keymasterbak' (232 KB)                    OKAY [  0.008s]
Writing 'keymasterbak'                             OKAY [  0.004s]
Finished. Total time: 0.021s
fastboot: error: cannot load 'firmware-update/logo.img': No such file or directory
fastboot: error: cannot load 'firmware-update/multi_image.mbn': No such file or directory
Sending 'modem' (130252 KB)                        OKAY [  3.031s]
Writing 'modem'                                    OKAY [  0.578s]
Finished. Total time: 3.617s
Sending 'qupfw' (52 KB)                            OKAY [  0.009s]
Writing 'qupfw'                                    OKAY [  0.002s]
Finished. Total time: 0.022s
Sending 'qupfwbak' (52 KB)                         OKAY [  0.007s]
Writing 'qupfwbak'                                 OKAY [  0.002s]
Finished. Total time: 0.018s
Sending 'storsec' (20 KB)                          OKAY [  0.008s]
Writing 'storsec'                                  OKAY [  0.001s]
Finished. Total time: 0.019s
Sending 'tz' (2919 KB)                             OKAY [  0.070s]
Writing 'tz'                                       OKAY [  0.016s]
Finished. Total time: 0.094s
Sending 'tzbak' (2919 KB)                          OKAY [  0.074s]
Writing 'tzbak'                                    OKAY [  0.014s]
Finished. Total time: 0.097s
Sending 'uefisecapp' (123 KB)                      OKAY [  0.007s]
Writing 'uefisecapp'                               OKAY [  0.005s]
Finished. Total time: 0.021s
Sending 'uefisecappbak' (123 KB)                   OKAY [  0.006s]
Writing 'uefisecappbak'                            OKAY [  0.003s]
Finished. Total time: 0.018s
Sending 'vbmeta' (4 KB)                            OKAY [  0.007s]
Writing 'vbmeta'                                   OKAY [  0.001s]
Finished. Total time: 0.017s
Sending 'vbmeta_system' (4 KB)                     OKAY [  0.008s]
Writing 'vbmeta_system'                            OKAY [  0.001s]
Finished. Total time: 0.019s
Sending 'xbl' (3561 KB)                            OKAY [  0.091s]
Writing 'xbl'                                      OKAY [  0.065s]
Finished. Total time: 0.163s
Sending 'xblbak' (3561 KB)                         OKAY [  0.086s]
Writing 'xblbak'                                   OKAY [  0.192s]
Finished. Total time: 0.287s
Sending 'xbl_config' (63 KB)                       OKAY [  0.004s]
Writing 'xbl_config'                               OKAY [  0.007s]
Finished. Total time: 0.019s
Sending 'xbl_configbak' (63 KB)                    OKAY [  0.005s]
Writing 'xbl_configbak'                            OKAY [  0.006s]
Finished. Total time: 0.020s
Erasing 'userdata'                                 OKAY [  0.256s]

        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 = 219573912 (107213 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:\xiaomi.eu_multi_HMNote9ProEU_V11.0.2.0.QJZMIXM_v11-10-fastboot\platform-tools-windows/make_f2fs failed: 3221225477
fastboot: error: Cannot generate image for userdata
Rebooting                                          OKAY [  0.000s]
Finished. Total time: 0.001s
 
Last edited:
skonteron said:
Hi,
I got my Redmi 9 Pro EU 9 days ago and already unlocked it. Following the instructions for installing (first page of this thread) the version xiaomi.eu_multi_HMNote9ProEU_V11.0.2.0.QJZMIXM_v11-10-fastboot
The phone boots and i checked the version, it was Xiaomi.eu V11.0.2

Today I try to install the Version xiaomi.eu_multi_HMNote9ProEU_V11.0.4.0.QJZMIXM_v11-10-fastboot but now I get this Error:



Any ideas?
thanks in advance


30 min later.....

Phone boots only to fastboot, so I installed xiaomi.eu_multi_HMNote9ProEU_V11.0.2.0.QJZMIXM_v11-10-fastboot again.
During FW Update I got the following errors, but the phone boots to Miui11 installation and I can start the Setup

Code: 
C:\xiaomi.eu_multi_HMNote9ProEU_V11.0.2.0.QJZMIXM_v11-10-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: joyeuse
product: joyeuse
Sending 'boot' (15096 KB) OKAY [ 0.356s]
Writing 'boot' OKAY [ 0.066s]
Finished. Total time: 0.431s
Sending sparse 'super' 1/6 (779269 KB) OKAY [ 18.526s]
Writing 'super' OKAY [ 0.001s]
Sending sparse 'super' 2/6 (778187 KB) OKAY [ 19.210s]
Writing 'super' OKAY [ 0.001s]
Sending sparse 'super' 3/6 (734666 KB) OKAY [ 18.020s]
Writing 'super' OKAY [ 0.000s]
Sending sparse 'super' 4/6 (785732 KB) OKAY [ 21.571s]
Writing 'super' OKAY [ 0.001s]
Sending sparse 'super' 5/6 (784436 KB) OKAY [ 27.351s]
Writing 'super' OKAY [ 0.001s]
Sending sparse 'super' 6/6 (298450 KB) OKAY [ 17.220s]
Writing 'super' OKAY [ 0.000s]
Finished. Total time: 127.993s
fastboot: error: cannot load 'firmware-update/recovery.img': No such file or directory
Sending 'abl' (204 KB) OKAY [ 0.010s]
Writing 'abl' OKAY [ 0.002s]
Finished. Total time: 0.021s
Sending 'ablbak' (204 KB) OKAY [ 0.007s]
Writing 'ablbak' OKAY [ 0.004s]
Finished. Total time: 0.020s
Sending 'aop' (159 KB) OKAY [ 0.007s]
Writing 'aop' OKAY [ 0.003s]
Finished. Total time: 0.018s
Sending 'aopbak' (159 KB) OKAY [ 0.007s]
Writing 'aopbak' OKAY [ 0.002s]
Finished. Total time: 0.018s
Sending 'bluetooth' (892 KB) OKAY [ 0.029s]
Writing 'bluetooth' OKAY [ 0.007s]
Finished. Total time: 0.044s
Sending 'cmnlib' (387 KB) OKAY [ 0.012s]
Writing 'cmnlib' OKAY [ 0.004s]
Finished. Total time: 0.024s
Sending 'cmnlibbak' (387 KB) OKAY [ 0.015s]
Writing 'cmnlibbak' OKAY [ 0.005s]
Finished. Total time: 0.028s
Sending 'cmnlib64' (503 KB) OKAY [ 0.015s]
Writing 'cmnlib64' OKAY [ 0.007s]
Finished. Total time: 0.042s
Sending 'cmnlib64bak' (503 KB) OKAY [ 0.013s]
Writing 'cmnlib64bak' OKAY [ 0.005s]
Finished. Total time: 0.028s
Sending 'devcfg' (42 KB) OKAY [ 0.006s]
Writing 'devcfg' OKAY [ 0.002s]
Finished. Total time: 0.016s
Sending 'devcfgbak' (42 KB) OKAY [ 0.009s]
Writing 'devcfgbak' OKAY [ 0.002s]
Finished. Total time: 0.019s
Sending 'dsp' (32768 KB) OKAY [ 0.758s]
Writing 'dsp' OKAY [ 0.139s]
Finished. Total time: 0.905s
Sending 'dtbo' (8192 KB) OKAY [ 0.199s]
Writing 'dtbo' OKAY [ 0.038s]
Finished. Total time: 0.246s
Sending 'hyp' (385 KB) OKAY [ 0.013s]
Writing 'hyp' OKAY [ 0.007s]
Finished. Total time: 0.028s
Sending 'hypbak' (385 KB) OKAY [ 0.012s]
Writing 'hypbak' OKAY [ 0.007s]
Finished. Total time: 0.029s
Sending 'imagefv' (20 KB) OKAY [ 0.003s]
Writing 'imagefv' OKAY [ 0.002s]
Finished. Total time: 0.014s
Sending 'keymaster' (232 KB) OKAY [ 0.009s]
Writing 'keymaster' OKAY [ 0.003s]
Finished. Total time: 0.020s
Sending 'keymasterbak' (232 KB) OKAY [ 0.008s]
Writing 'keymasterbak' OKAY [ 0.004s]
Finished. Total time: 0.021s
fastboot: error: cannot load 'firmware-update/logo.img': No such file or directory
fastboot: error: cannot load 'firmware-update/multi_image.mbn': No such file or directory
Sending 'modem' (130252 KB) OKAY [ 3.031s]
Writing 'modem' OKAY [ 0.578s]
Finished. Total time: 3.617s
Sending 'qupfw' (52 KB) OKAY [ 0.009s]
Writing 'qupfw' OKAY [ 0.002s]
Finished. Total time: 0.022s
Sending 'qupfwbak' (52 KB) OKAY [ 0.007s]
Writing 'qupfwbak' OKAY [ 0.002s]
Finished. Total time: 0.018s
Sending 'storsec' (20 KB) OKAY [ 0.008s]
Writing 'storsec' OKAY [ 0.001s]
Finished. Total time: 0.019s
Sending 'tz' (2919 KB) OKAY [ 0.070s]
Writing 'tz' OKAY [ 0.016s]
Finished. Total time: 0.094s
Sending 'tzbak' (2919 KB) OKAY [ 0.074s]
Writing 'tzbak' OKAY [ 0.014s]
Finished. Total time: 0.097s
Sending 'uefisecapp' (123 KB) OKAY [ 0.007s]
Writing 'uefisecapp' OKAY [ 0.005s]
Finished. Total time: 0.021s
Sending 'uefisecappbak' (123 KB) OKAY [ 0.006s]
Writing 'uefisecappbak' OKAY [ 0.003s]
Finished. Total time: 0.018s
Sending 'vbmeta' (4 KB) OKAY [ 0.007s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.017s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.008s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Finished. Total time: 0.019s
Sending 'xbl' (3561 KB) OKAY [ 0.091s]
Writing 'xbl' OKAY [ 0.065s]
Finished. Total time: 0.163s
Sending 'xblbak' (3561 KB) OKAY [ 0.086s]
Writing 'xblbak' OKAY [ 0.192s]
Finished. Total time: 0.287s
Sending 'xbl_config' (63 KB) OKAY [ 0.004s]
Writing 'xbl_config' OKAY [ 0.007s]
Finished. Total time: 0.019s
Sending 'xbl_configbak' (63 KB) OKAY [ 0.005s]
Writing 'xbl_configbak' OKAY [ 0.006s]
Finished. Total time: 0.020s
Erasing 'userdata' OKAY [ 0.256s]

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 = 219573912 (107213 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:\xiaomi.eu_multi_HMNote9ProEU_V11.0.2.0.QJZMIXM_v11-10-fastboot\platform-tools-windows/make_f2fs failed: 3221225477
fastboot: error: Cannot generate image for userdata
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.001s
Click to expand...
Forget installing ROM via fastboot.
Just flash the TWRP and install ROM from there!
 
Hi all. I bought from Romania - EU a redmi note 9 pro 128/6 and when i want to unlock the bootloader it says that i have to wait more than 300 hrs. And now the question --> can i just flash (via fastboot) a xiaomi.eu rom without unlocking the bootloader? Without twrp (dont need it). Just the x.eu rom and NOT unlocking the bootloader. Thank you in advance.
 
boburobert said:
Hi all. I bought from Romania - EU a redmi note 9 pro 128/6 and when i want to unlock the bootloader it says that i have to wait more than 300 hrs. And now the question --> can i just flash (via fastboot) a xiaomi.eu rom without unlocking the bootloader? Without twrp (dont need it). Just the x.eu rom and NOT unlocking the bootloader. Thank you in advance.
Click to expand...
AFAIK, bootloader MUST be unlocked prior to installing any custom ROM, Xiaomi.eu included. You are correct in your assertion that TWRP is not required, if you use the Fastboot ROMs. Seven day wait is normal for unlocking Xiaomi phones... no idea why though !
 
  • Love
Reactions: LOLO9393
Hi,

I just unlocked my phone (joyeuse version) and tried to install xiaomi.eu_multi_HMNote9ProEU_V11.0.2.0.QJZMIXM as described on the first post.
I got few errors while doing that (same as skonteron had on his second try to rollback into this version, but the difference between his case and mine is that on his first try to install this version, all went good and only after rolling back to this version he had those errors. On my case, I got them from the very beginning).

I saw it was suggested to him to use TWRP, but I'm a bit confused as from what I understood 11.0.2.0 should be good for fastboot and TWRP is still not official for this phone. So - I'm not sure why I had those errors. Can anyone tell me what I did wrong?
Also - if TWRP is what I should still do, then:
1. Should I use the same zip file for that? Any special steps for installing the ROM other than booting to TWRP and install this zip (only)?
2. Will TWRP work with more recent versions (11.0.5.0)?

Will appreciate if someone could clear things up for me and help with those issue.
 
Chapshan said:
Hi,

I just unlocked my phone (joyeuse version) and tried to install xiaomi.eu_multi_HMNote9ProEU_V11.0.2.0.QJZMIXM as described on the first post.
I got few errors while doing that (same as skonteron had on his second try to rollback into this version, but the difference between his case and mine is that on his first try to install this version, all went good and only after rolling back to this version he had those errors. On my case, I got them from the very beginning).

I saw it was suggested to him to use TWRP, but I'm a bit confused as from what I understood 11.0.2.0 should be good for fastboot and TWRP is still not official for this phone. So - I'm not sure why I had those errors. Can anyone tell me what I did wrong?
Also - if TWRP is what I should still do, then:
1. Should I use the same zip file for that? Any special steps for installing the ROM other than booting to TWRP and install this zip (only)?
2. Will TWRP work with more recent versions (11.0.5.0)?

Will appreciate if someone could clear things up for me and help with those issue.
Click to expand...
You have to go with TWRP and only with it even unofficial...
It will not be any any official release in short time.
Latest EU rom are TWRP only and situation is under control now.
Check the relevant TWRP topic in RN9 forum section.
 
You must log in or register to reply here.

Similar threads

gogocar62
Fix Networks for GARNET
Replies
69
Views
18K
Mi General
gogocar62
gogocar62
gogocar62
Fix_SIM_ Xiaomi 14 Global verzion
Replies
59
Views
16K
Xiaomi 14 / Pro / Ultra
gogocar62
gogocar62
P
Bootlooped redmi note 9s
Replies
0
Views
1K
Redmi Note 9S / Pro / Max / ProEU
Pedforter
P
gogocar62
How to Install Stock ROM.
Replies
0
Views
2K
Mi General
gogocar62
gogocar62
ingbrzy
  • Sticky
[GUIDE] How to install Xiaomi.eu ROM for Xiaomi 13 series
Replies
90
Views
94K
Xiaomi 13 / Pro / Lite / Ultra
gogocar62
gogocar62
Top Bottom
Back