How To Guide [ROM][MIUI][sweet] Xiaomi.eu ROM for Redmi Note 10 Pro

[Ashle]

• MIUI: V14.0.2.0..TKFMIXM
• 
  
• Android: 13
• 
  
• ROM: HMNote10Pro 14.0.2.0.TKFMIXM
• 
  
• MODEL: sweet
• 
  
• Size: 4 GB
• 
  
• Date: 27.04.2023
• 
  
• Fastboot
• 
  
• Stable MIUI based on Android 13.
  Updated Android Security Patch to April 2023. Increased system security.

https://sourceforge.net/projects/xi....TKFMIXM_v14-13.zip/download?use_mirror=netix

 

[Fostel]

• MIUI: V14.0.2.0..TKFMIXM
• 
  
• Android: 13
• 
  
• ROM: HMNote10Pro 14.0.2.0.TKFMIXM
• 
  
• MODEL: sweet
• 
  
• Size: 4 GB
• 
  
• Date: 27.04.2023
• 
  
• Recovery
• 
  
• Stable MIUI based on Android 13.
  Updated Android Security Patch to April 2023. Increased system security.

https://sourceforge.net/projects/xi....TKFMIXM_v14-13.zip/download?use_mirror=netix

Tried with official TWRP and xiaomi.eu suggested TWRP (TeamWin).
Followed the guide:

MIUI 14 - MIUI 14 STABLE RELEASE

Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...

xiaomi.eu

but I couldn't "Copy the ROM zip file to the internal storage" so tried ADB sideload.

$ adb sideload xiaomi.eu_multi_HMNote10Pro_V14.0.2.0.TKFMIXM_v14-13.zip
adb: failed to read command: Success

With fastboot method, I got "device unknown"

What is going on?

 

[YuRuMii]

Tried with official TWRP and xiaomi.eu suggested TWRP (TeamWin).
Followed the guide:

MIUI 14 - MIUI 14 STABLE RELEASE

Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...

xiaomi.eu

but I couldn't "Copy the ROM zip file to the internal storage" so tried ADB sideload.

$ adb sideload xiaomi.eu_multi_HMNote10Pro_V14.0.2.0.TKFMIXM_v14-13.zip
adb: failed to read command: Success

With fastboot method, I got "device unknown"

View attachment 5905379

What is going on?

extract the zip then run batch file

 

[thxjxs]

Tried with official TWRP and xiaomi.eu suggested TWRP (TeamWin).
Followed the guide:

MIUI 14 - MIUI 14 STABLE RELEASE

Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...

xiaomi.eu

but I couldn't "Copy the ROM zip file to the internal storage" so tried ADB sideload.

$ adb sideload xiaomi.eu_multi_HMNote10Pro_V14.0.2.0.TKFMIXM_v14-13.zip
adb: failed to read command: Success

With fastboot method, I got "device unknown"

View attachment 5905379

What is going on?

i faced the same issue, and went back on the eu forums to do a quick readup... its mentioned here in the first post on stable releases that the rom zip file for sweet is a hybrid one, meaning that it can be flashed both via recovery as well as fastboot and as @YuRuMii pointed out, there are 6 script files in the unzipped rom file... fastboot_first_install_with_data_format and fastboot_update_rom each for linux, macos and windows (batch files)

if i remember correctly, you can switch to fastboot mode and then either run the desired script (batch file if you're using windows) file either by simply double clicking it or theoretically it should work with the mi flash tool also, just select the desired script file from the bottom right drop down menu after selecting the unzipped folder of the rom (although theoretically it should work, i haven't checked the mi-flash-tool method, therefore not sure)

if the above methods still haven't worked (which i think is the case for you) and the device incompatible message still shows up, you can open up the script file you chose in a text editor of your choice and just comment away the lines that check for the device id (those lines are there just to prevent the rom of one device, say sweet, being flashed on another device, say alioth), which should definitely work

for the windows batch script windows_fastboot_first_install_with_data_format for example, it should be the lines

for /f "tokens=2" %%D in ('%fastboot% getvar product 2^>^&1 ^| findstr /l /b /c:"product:"') do set device=%%D
if "%device%" neq "sweet" echo Compatible devices: sweet & echo Your device: %device% & pause & exit /B 1

make your own judgement calls as necessary if you're using any of the other scripts

 

[Ashle]

Unzip the file and run windows_fastboot_first_install_with_data_format.bat

 

[Fostel]

extract the zip then run batch file

That is what I've done with a fastboot method. According to the linked guide. The error (screenshot) is a result of running the script (I am on Linux).

 

[Fostel]

i faced the same issue, and went back on the eu forums to do a quick readup... its mentioned here in the first post on stable releases that the rom zip file for sweet is a hybrid one, meaning that it can be flashed both via recovery as well as fastboot and as @YuRuMii pointed out, there are 6 script files in the unzipped rom file... fastboot_first_install_with_data_format and fastboot_update_rom each for linux, macos and windows (batch files)

if i remember correctly, you can switch to fastboot mode and then either run the desired script (batch file if you're using windows) file either by simply double clicking it or theoretically it should work with the mi flash tool also, just select the desired script file from the bottom right drop down menu after selecting the unzipped folder of the rom (although theoretically it should work, i haven't checked the mi-flash-tool method, therefore not sure)

if the above methods still haven't worked (which i think is the case for you) and the device incompatible message still shows up, you can open up the script file you chose in a text editor of your choice and just comment away the lines that check for the device id (those lines are there just to prevent the rom of one device, say sweet, being flashed on another device, say alioth), which should definitely work

for the windows batch script windows_fastboot_first_install_with_data_format for example, it should be the lines

for /f "tokens=2" %%D in ('%fastboot% getvar product 2^>^&1 ^| findstr /l /b /c:"product:"') do set device=%%D
if "%device%" neq "sweet" echo Compatible devices: sweet & echo Your device: %device% & pause & exit /B 1

make your own judgement calls as necessary if you're using any of the other scripts

Thank you for your time replying.
Yes, I used the script in the terminal. The device unknown made me panic for a bit but I was able to run the official stock 14.0.2 and also the unofficial Lineage 20. They run ok.

Just to confirm. My device is a 'sweet' UK model that came with a Global MIUI but some software was reporting sweet_eea.

1. Does it matter (sweet vs sweet_eea) at this point?
2. Is the

   xiaomi.eu_multi_HMNote10Pro_V14.0.2.0.TKFMIXM_v14-13.zip

   a proper file for my device?

 

[pnin]

1. Don't think so -- looks like an irrelevant variant in present context;
2. I believe so (although I'm still on V14.0.1.0).

 

[hyperboarean]

Does it have spatial audio? And Dolby Atmos?

 

[romuser87]

Coming back from different custom roms to Xiaomi.eu after a long time. Works great so far. Better than expected, no stutter most of the time.

However, is there a decent Kernel to use for better performance and battery life? its already good, but maybe ther is something better?

 

[abi.naaim]

I'm currently using MiuiEu 13.0.15.0 in Redmi Note 10 Pro (Sweetin), so what's the procedure/way if I want to upgrade MiuiEu 14?

 

[t0masz]

As I understand Xiaomi.eu rom by default has Mi Dialer, Mi Contacts and Mi Messaging but you can disable these and install Google alternatives instead from the Play Store, right?

Does it support 108MP camera?

Does Google Pay work as usual?

 

[manthes]

I have four questions

1. Does it have stock miui cam?
2. Does it support focal touch?
3. Any deep sleep problems?
4. Can i install it with orange fox or mi flash? (because of focal touch i can't use twrp)

 

[pnin]

I have four questions

1. Does it have stock miui cam?
2. Does it support focal touch?
3. Any deep sleep problems?
4. Can i install it with orange fox or mi flash? (because of focal touch i can't use twrp)

I have a recent 6/128GB sweet with Focaltech (fts_ts) touch running Xiaomi.eu v14.0.1.0 (debloated!):

1. Yes
2. Yes
3. Not that I could notice
4. I believe so (although I used the fastboot method myself, Aryan's OF hadn't yet been released...)

Haven't had the leisure to update yet...

 

[manthes]

I tried the rom. Except that it has more control over the apps permissions i can't say that it is superior than stock rom.
But my problem is that notifications from messenger etc don't arrive or they arrive after many minutes have passed

 

[Floyd-74]

One problem that has been getting worse since version 13 is that apps have their access rights revoked. When I change this manually, I also want these settings to be permanent and not be changed again by the system after some time.

 

[t0masz]

I tried the rom. Except that it has more control over the apps permissions i can't say that it is superior than stock rom.
But my problem is that notifications from messenger etc don't arrive or they arrive after many minutes have passed

if your talking about Facebook Messenger then this has been an issue for a while, not MIUI specific either

 

[david003]

if your talking about Facebook Messenger then this has been an issue for a while, not MIUI specific either

For what it's worth, I ran xiaomi.eu for a long time and also had problems with Facebook Messenger notifications. After moving to an AOSP-based ROM with MicroG, that problem disappeared. I get immediate notifications now.

 

[t0masz]

For what it's worth, I ran xiaomi.eu for a long time and also had problems with Facebook Messenger notifications. After moving to an AOSP-based ROM with MicroG, that problem disappeared. I get immediate notifications now.

I and my gf both run AOSP roms (crDroid and Pixel Experience respectively) on Xiaomis and sometimes we don't get Messenger notifications as well. these has been happening for the past 6 months or something

 

[t0masz]

Can you flash GAPPS on top of Xiaomi.eu rom so that Google Phone/Contacts and Google Messages register as system apps?