Database Develop

Doubt about Xposed and A/B partition devices

I have a doubt about xposed systems on A/B partitions, for if anyone knows about this (maybe Pixel users):
Let's say you have your full setup on any slot rocking it (let's say huge modifications like xposed & maybe others (twrp, magisk/supersu, custom kernel, etc) on slot A) and suddently an OTA comes and flashes new full stock rom version on slot B and tries to run it succesfully on next reboot. And suddently after the reboot you find yourself on the updated new stock version on slot B without xposed (and without twrp&others too) in a clean instalation.
Now in this scenario..
a) slot A (which should have the xposed system you were rocking before the OTA and the succesfull slot change) is untouched or it is ruined with a copy from slot B after the succesfull boot??
b) if slot A survived untouched, can you just do a "fastboot --set-active=a" command and just reboot into the xposed system like before the OTA, or this doesnt work after the OTA and is ruined in some way?
c) if b) works (it should right.. right?), will the system try do download the OTA again asap you boot the old version on the slot A?
d) there's any way to block the Update Engine from updating, for example to wait till xposed is adapted for new version. For us Xposed users, waiting till new xposed version comes is a mantra that we have to do, and if we can't block OTAs or just undo what the Update Engine does... we're screwed?
Anyone on this scenario? I'm considering getting an A/B phone but this thing looks like a headache for anyone who likes to flash stuff and specially xposed.. since everything else you can reflash it on the new version mostly in a matter of hours/few days, xposed takes months to adapt.
I'd be glad if any Pixel xposed user could shed light onto those questions.
Thanks!

Noone seriously?

I have p2xl. I am not sure how a/b slots work for sure.
What I do know is that I have turned off automatic automatic updates under developer settings. I manually flash the stock ota image from google via twrp. Then reflssh twrp, custom kernel, and then magisk, the m ahisk installer has an Xposed built for magisk.
I usually just check google ota domtime around the 5th or 6th of each month.

smartymcfly said:
I have p2xl. I am not sure how a/b slots work for sure.
What I do know is that I have turned off automatic automatic updates under developer settings. I manually flash the stock ota image from google via twrp. Then reflssh twrp, custom kernel, and then magisk, the m ahisk installer has an Xposed built for magisk.
I usually just check google ota domtime around the 5th or 6th of each month.
Click to expand...
Click to collapse
Interesting, so if you disable automatic updates, you never turned on the phone and found a clean installation without xposed and such?
thanks!

RusherDude said:
Interesting, so if you disable automatic updates, you never turned on the phone and dounf a clean installation without xposed and such?
thanks!
Click to expand...
Click to collapse
If there is an update, it sends me a notification to ask if I want to update. And because xposed is installed I do not think it can actually follow through with the update on it's own because it breaks google's safetynet.
The only time I have turned on my phone and found it without magisk and root and xposed was when I 1st turned it on, and one time I had to do a factory restore when I did unlock bootloader because I also had to send another command that is only on pixel 2xl that to unlock_critical in addition to it. That is it.

smartymcfly said:
If there is an update, it sends me a notification to ask if I want to update. And because xposed is installed I do not think it can actually follow through with the update on it's own because it breaks google's safetynet.
The only time I have turned on my phone and found it without magisk and root and xposed was when I 1st turned it on, and one time I had to do a factory restore when I did unlock bootloader because I also had to send another command that is only on pixel 2xl that to unlock_critical in addition to it. That is it.
Click to expand...
Click to collapse
Awesome to hear
Btw, I don't think it would have a problem updating even if xposed is installing, normally the problem with incremental OTAs are if partitions are touched or not, and unlocking bootloader per se already breaks safetynet but OTAs can be installed, so safetynet is ignored, and in this A/B layout stuff would probably just be flashed on the other slot like if it had happened in the background. This is an interesting question if anyone knows it.

Moving from Oreo to Pie with no TA keys

Hi everyone,
I was one of the early "plungers" for the XZ1c, so I unlocked my bootloader without any TA key backup, flashed Oreo (47.1.A.12.145), and got by with Xperifix. But now I want to upgrade to Pie for a plethora of reasons (e.g. development).
I did a bit of reading here and there, and I came up with a set of steps for me to follow (and maybe anyone else who wants to attempt the same). Please do correct me if I'm wrong, and risk a brick:
Method A:
Backup all my stuff (a combination of manually, TitaniumBackup, Google, Sony)
Download the official stock firmware for Pie (47.2.A.10.45) via Xperifirm.
Flash Pie with a full format, to prevent any instabilities from apps.
Flash j4nn's bootloader unlock hide kernel to get root + Magisk (v18.1).
Restore backups.
Method b:
Backup all my stuff (a combination of manually, TitaniumBackup, Google, Sony)
Download the latest firmware and kernel for Pie (47.2.A.8.24) from janjan's thread.
Flash Pie with a full format, to prevent any instabilities from apps.
Flash janjan's kernel to get root + Magisk (v?).
Restore backups.
I'm leaning towards method A, as it'll be a newer version of Pie, but I do have some questions I couldn't manage to find a clear answer for:
Will Google Pay work with either method? This is kind of a deal breaker for me, as contactless payments are prevalent in my region.
Is there a reason to use Newflasher over Flashtool? I had used Flashtool for my XZ1c (even before they added official support in 0.9.24.3).
Does the gimmicky slo-mo video camera feature still work?
Is it possible to get TWRP with j4nn's method?

@TheFuzzy, concerning janjan's kernel, there is no drmfix included in pie releases, so that kernel seems to be only somehow tuned stock kernel.
My kernel releases are stock identical, no tuning at all, the only difference to stock is the kernel patch to hide bootloader unlocked state.
I believe this is a great benefit even in case of lost drm keys, if you need to use google pay or such apps. And yes, by following alternate use guide, my kernel can be flashed and used with twrp.
As tested by @russel5 (with some help and ideas from me), google pay now seems to use Android Attest Key (as I've expected long ago to happen) to truly detect bootloader unlock state.
In case you have Android Attest Key _working_ (see here to find out), even my kernel would not help to hide bootloader unlock (you can test that with the linked Auditor app even while running my kernel).
Destroying Android Attest Key seems to help to make google pay working as tested by russel5 - I did not test that myself, but @russel5 might confirm (thanks again for your testing and your finds, russel5).
But it seems to be irreversible change - we might still try to do some backup and restore tests...

@j4nn Thanks for the info! It is a bit confusing to keep up with the differences between the different methods.
I used your bootloader with 47.2.A.10.45, and it works like a charm.
I flashed your kernel directly as I'm not interested in FOTA. I've not tried to flash TWRP as I was afraid it might break the bootloader hide unlock patch (unless there is a specific order to follow, i.e. flashing it over TWRP or vice versa).
I ended up using Newflasher too, as I had read about not flashing the persist.sin file, and it seemed too tricky to do it with Flashtool.
One odd side effect is that I required the patched kernel to be flashed instead of booted from via adb, otherwise the device would boot loop and boot with the stock kernel instead.
I wasn't able to use your patched Auditor app as I don't have another phone at Nougat to verify. Indeed, Google Pay did pick up on the bootloader unlock status (maybe because of the Attest Key), but I was able to re-enable it using the SQLite trick mentioned here. My banking apps work fine with MagiskHide, too.

@TheFuzzy, you may use my patched Auditor app just with your single phone, which you like to check your attest key in.
Just install the patched Auditor and scan the QR code available on google play store in the Auditor's screenshots, instead of using a second phone.
That will trigger the verification just fine and then the audit results are simply displayed on the phone.

Bootloader lock or hide

Hi,
I hope somebody can give me a hint.
I just got a used p20 pro with open bootloader but stock rom.
Unfortunately the Google security check has some "problems" with this situation and doesn't allow me to use several apps like Netflix, Google pay, etc.
So I'm looking for a way to easily fix this problem, the phone will be used by my parents.
Either lock the bootloader or "hide" it probably.
But how - I don't have the bootloader code - and I'm not too much into android rooting...
Usefull hints are appreciated.
Merry xmas
Mounty

You're on thin ice my pedigree chum..
Avoid flashing anything that would allow a block of any kind which is an absolute reality.
Having used absolutely every ROM and OS from 8.1 to 10
My advice. Flash AOSIP and then ask in thread to get safety net working.
Literally nothing else it worth your time.
Unless you're strange and like EMUI.
In such case, stuck with stock.
Just be aware you're in a position that a lot of people would kill for.

Google have done some **** stuff to make people who have unlocked bootloader a nightmare. I don't think there is a way to hide it unless you use Magisk

mounty77 said:
the phone will be used by my parents.
Click to expand...
Click to collapse
If they are not some kind of advanced users, unlocked bootloader has exactly 0 added value for them. Search the forum for flushing methods, the ones that will warn you that this method re-locks the bootloader, flush the latest stock ROM for your region and live a happy and calm life.

As a suggestion.. Use Magisk with Safety patch and you're done. You can keep the bootloader unlocked and still bypass google restrictions. (Install apps like netflix, etc.)
My phone is on 9.0.1.328 and works fine.

Horayken said:
As a suggestion.. Use Magisk with Safety patch and you're done. You can keep the bootloader unlocked and still bypass google restrictions. (Install apps like netflix, etc.)
My phone is on 9.0.1.328 and works fine.
Click to expand...
Click to collapse
Hi,
Thx so far, I think I'll try the magisk thing.
Are there any downsides on this? Will Ota updates still work?
I already downloaded and installed magisk manager, but I was not able to install magisk via magisk manager.
I downloaded the zip file and tried to install it.
But I only got the attached error.
I think I have to patch something?!
Any advise?
Thx
Mounty

mounty77 said:
Hi,
Thx so far, I think I'll try the magisk thing.
Are there any downsides on this? Will Ota updates still work?
I already downloaded and installed magisk manager, but I was not able to install magisk via magisk manager.
I downloaded the zip file and tried to install it.
But I only got the attached error.
I think I have to patch something?!
Any advise?
Thx
Mounty
Click to expand...
Click to collapse
You need to patch the ramdisk recovery file with magisk, flash it and you are good to go. It's a 5 min procedure. Let me know if you need more help with that.
This way you will hide your unlocked bootloader and you will pass safetynet.
Only downside is that if there is an ota update you will need to flash the original ramdisk recovery, do the ota and then do ramdisk recovery file patch again.
If you lock the bootloader then you won't be able to unlock it again as you won't have the code (unless you got the code from the previous owner too).

abyssq said:
You need to patch the ramdisk recovery file with magisk, flash it and you are good to go. It's a 5 min procedure. Let me know if you need more help with that.
This way you will hide your unlocked bootloader and you will pass safetynet.
Only downside is that if there is an ota update you will need to flash the original ramdisk recovery, do the ota and then do ramdisk recovery file patch again.
If you lock the bootloader then you won't be able to unlock it again as you won't have the code (unless you got the code from the previous owner too).
Click to expand...
Click to collapse
Hi,
thx for your offer/advise. I’ll try this way - it sounds most promising to me.
Can I do this on the mobile only, or do I need a pc?
Where / How do I find the ramdisk recovery?

BL Lock
I can lock (yes, lock) your bootloader for free.
Contact me at Telegram (@AntiEngineer), you don't need to open up your device.

abyssq said:
You need to patch the ramdisk recovery file with magisk, flash it and you are good to go. It's a 5 min procedure. Let me know if you need more help with that.
This way you will hide your unlocked bootloader and you will pass safetynet.
Only downside is that if there is an ota update you will need to flash the original ramdisk recovery, do the ota and then do ramdisk recovery file patch again.
If you lock the bootloader then you won't be able to unlock it again as you won't have the code (unless you got the code from the previous owner too).
Click to expand...
Click to collapse
Hi,
unfortionatly I wasn´t sucessfull till now.
At https://openkirin.net/ is a very usefull description availaible but I´m still searching for the RAMDISK Extract. I found that database where you can donwload several versions, but mine wasn´t provided there
https://pro-teammt.ru/en/online-firmware-database/
My Version is:
CLT-L29
10.0.0.138 (C432E3R1P3log)
Anybody knows where I can download that`?
Best regards
mounty

@mounty77
You are on Android 10 Beta?
Root on Android 10 Beta not working for me.

You are on Android 10 Beta?
Root on Android 10 Beta not working for me.
Click to expand...
Click to collapse
No Root, just unlocked bootloader... I want to hide the unlock of the bootloader

mounty77 said:
No Root, just unlocked bootloader... I want to hide the unlock of the bootloader
Click to expand...
Click to collapse
Installing a "RECOVERY_RAMDIS.img" patched with Magisk is rooting the phone.

I´m fine if i have to root it to hide the open bootloader

Stock MIUI flash (from MiFlash) gives me ctsprofile False

I was having trouble getting cts profile = true on Pixel Experience ROMs and someone gave me a vbmeta to flash...now I have ctsprofile - true on Pixel Experience ROMS but even after doing a full stock flash on MiFlash, stock MIUI gives me ctsprofile - FALSE...Any ideas on how I can fix this issues,? Thanks in advance!

Because you have a unlocked bootloader lol. Good custom roms like PE and eu.miui do some sweet trickery to fix this. Only way to fix is relock bootloader on stock rom or root and use magisk hide and see how Google is feeling today.

hoopsnake said:
Because you have a unlocked bootloader lol. Good custom roms like PE and eu.miui do some sweet trickery to fix this. Only way to fix is relock bootloader on stock rom or root and use magisk hide and see how Google is feeling today.
Click to expand...
Click to collapse
As far as I know, this is untrue, as before, i switched from PE to MIUI and still had SafetyNet check out. This time, I flashed a patched VBMeta someone sent me though, which could have caused the issue.

There's too many variables involved, was this before March? What build? What did you wipe in twrp? Root?
Having a unlocked bootloader on all devices on stock rom as of March fails safetynet end of story.
"John Wu has shared more details on the change on Twitter. He confirms that MagiskHide will continue to conceal root, but it might soon not hide the fact that your bootloader is unlocked anymore, since that's what SafetyNet checks for. Other than that, he expands on why he doesn't see a way around Google's new implementation"

hoopsnake said:
There's too many variables involved, was this before March? What build? What did you wipe in twrp? Root?
Having a unlocked bootloader on all devices on stock rom as of March fails safetynet end of story.
"John Wu has shared more details on the change on Twitter. He confirms that MagiskHide will continue to conceal root, but it might soon not hide the fact that your bootloader is unlocked anymore, since that's what SafetyNet checks for. Other than that, he expands on why he doesn't see a way around Google's new implementation"
Click to expand...
Click to collapse
Nope, got this phone only in April...I wiped everything in TWRP. The thing that changed is when I tried to boot PE and got DMVERIFY issues and couldnt get past the Mi boot screen, installed a patched VBMeta and now PE has CTSPROFILE TRUE and MIUI doesn't

I reflashed stock and locked my bootloader and as was said before, it now has ctsprofile true. Sadly, now anytime i unlock my bootloader, cts fails.

You shouldn't need to do that, PE boots fine without DM Verity, disable force encryption and vbmeta. All you do is format data, reboot recovery, wipe everything then immediately flash rom and reboot. Anyway when you flash fastboot rom vbmeta is replaced, I wouldn't mess around with that. The Google cts fix is coming very soon it'll fail on all custom roms so if it's that important for you then stock recovery locked bootloader is the only way.

Question Root support for Xiaomi 12 Pro

I was following the guide from https://topjohnwu.github.io/Magisk/install.html.
When I run the command
Code:
fastboot flash boot /path/to/magisk_patched.img
I get the following error :
Code:
>fastboot flash boot ./magisk_patched-24300_WbyGV.img
Sending 'boot_a' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Note that I had already waited 7 days and unlocked the device successfully with https://en.miui.com/unlock/download_en.html so I am not sure why the error is showing that my device is locked.
The Mi unlock tool said that my device was successfully unlocked.

Update : Never mind, I resolved it.
DEAR PEOPLE FROM THE FUTURE: Here's what we've figured out so far:
When you reboot into using `adb reboot fastboot` command we will land in fastbootd mode instead of fastboot mode. Turning off the mobile and using down arrow and power button together is the ideal way to reach the fastboot mode.
Magisk throws the above error when running in fastbootd mode, but the same command works great when running in fastboot mode.
So quick guide for rooting Xiaomi 12 Pro and passing Safetynet is to
1) unlock the device by using MIUI Unlock (It may take 7 days)
2) Follow the topjohnwu's guide to root your phone.
3) Enable zygisk and deny list in Magisk.
4) Apply the Universal Safetynet Fix module in Magisk

12 Pro doesnt have A / B partition as 12?
[ROOT]ing Xiaomi 12 with Magisk
Sources used: https://www.getdroidtips.com/root-xiaomi-12-and-12-pro/ 1. First unlock your bootloader. This thread does not cover this. I suggest you do not try to tamper with the 1week~ time gate you will encounter else it may get longer should...
forum.xda-developers.com

seems it went well
Code:
fastboot flash boot MI12pro_magisk_patched-24300_xl4XD.img
Sending 'boot_a' (196608 KB) OKAY [ 4.672s]
Writing 'boot_a' OKAY [ 0.381s]
Finished. Total time: 5.861s
Anyway , how to find out if device has A/B partition?

killeriq said:
seems it went well
Code:
fastboot flash boot MI12pro_magisk_patched-24300_xl4XD.img
Sending 'boot_a' (196608 KB) OKAY [ 4.672s]
Writing 'boot_a' OKAY [ 0.381s]
Finished. Total time: 5.861s
Anyway , how to find out if device has A/B partition?
Click to expand...
Click to collapse
You can see from the result "Sending 'boot_a'" that it has A/B partition. But as far as I know you don't have to flash in both the partitions. Just default flash boot command should be enough.
Good to know that it went well!

It is really complicated for a normal being to root this device, and I consider that I have a certain "skill" in this area. At the moment it is not possible to use Orange Fox, TWRP and even less to use Magisk in an uncomplicated way. Is there a specific reason?

what I did to root my Xiaomi 12 pro (using eu rom but the proceedure will be same for stock rom too)
DO AT YOUR OWN RISK
1. Unlock the device
2. get boot image of your current rom & latest magisk app from github
3. install magisk app & patch the boot image with magisk app
4. reboot bootloader => adb reboot bootloader which opens fastboot, do not use adb reboot fastboot which will open fastbootd
5. open terminal in your pc and using fastboot boot magisk_patched.img boot into magisk patched boot, then fastboot reboot
6. now you can use root till u reboot so open magisk app now and install magisk using direct install method which will patch stock boot image which is currently being used.
7. reboot device
8. (Optional)enable zygisk, denylist and configure deny list
9. (Optional)I install all the modules which I want to like lsposed, energized protection, sui etc.
10. (Optional) if you are facing issues with any banking or other apps which recognises root or lsposed use hidemyapplist xposed module, if still issue persist then disable denylist and flash Shamiko magisk module it won't work with denylist enabled.
Q. Won't it be sufficient if we flash boot image directly?
A. you can, but do flash both partitions xiaomi 12 pro, I personally faced an issue with this method once so I don't flash and instead use magisk app to patch.
Q. Do we need Safety net module?
A. In my use case no after enabling zygisk and configuring denylist u can basically stop apps from using root by denying their requests so safety net test will pass once you configure it in denylist remember to turn on google services and banking apps at least in denylist.
Q. My Banking app still recognize root, how to hide it?
A. If u have lsposed use HideMyAppList module and configure all the apps which are to be not allowed to use root, if it still doesn't work then use Shamiko module with hide my app list module, to use Shamiko you have to disable denylist.
Q. Can I unroot?
A. Yes you can just flash original boot or use uninstall option in magisk app or update your rom, there are many ways to remove root access.
Q. Are all apps working?
A. yes I am from india, here all banking/Wallets/UPI apps are working after configuring denylist and hidemyapplist module, As of now I am not using Shamiko

Same here, I rooted my 12 Pro and its working great.
What I did first I flashed the xiaomi EU stable Rom first, then extracted boot file, patched and flashed via fastboot. No need for TWRP at all and I wont bother installing it either. Fastboot application is straight forward and smooth

Hi i have a question by Miunlocker is written that i cant use fingerprint unlocking after Bootloader Unlocking. is that true? Or can i activate that later again with MagiskHide Props config, safety netfix and so on? or is that forever not possible with unlock and root? Cause then i think about getting an other Phone. Regards and thanks

raymann89 said:
Hi i have a question by Miunlocker is written that i cant use fingerprint unlocking after Bootloader Unlocking. is that true? Or can i activate that later again with MagiskHide Props config, safety netfix and so on? or is that forever not possible with unlock and root? Cause then i think about getting an other Phone. Regards and thanks
Click to expand...
Click to collapse
Their warnings are very misleading. Everything works as it should, except Mi device location, but you have Google device location for that purpose. My phone is unlocked and rooted, so I'm speaking from experience. SafetyNet passes, bank apps work, PayPal works, etc...

yes that that whole thing work i know, i have at the monent an oneplus 10 pro rooted, but i was worried cause there statments thats why i asked, but good to know that everything works with magisk, thank you Yes i mean the device location dont interest me persoanlly

Hi i have a few Questions, my Unlock Waiting Time is Today over, and i wanted to ask first - is it better to use the XiaomiEU Roms rather then the Global Version? Then after that, by my Oneplus before i just Unlocked, rooted with magisk as Patch File from Payloader and enabled then the hide list and the other Settings with Fingerprint. Now for the Xiaomi is TWRP Available so better use that ? and With Xiaomi EU Rom, TWRP and Magisk Hidemyapps and Safetynetfix iam able to use Banking Apps and Gpay ? thanks and sorry for the many Questons

raymann89 said:
Hi i have a few Questions, my Unlock Waiting Time is Today over, and i wanted to ask first - is it better to use the XiaomiEU Roms rather then the Global Version? Then after that, by my Oneplus before i just Unlocked, rooted with magisk as Patch File from Payloader and enabled then the hide list and the other Settings with Fingerprint. Now for the Xiaomi is TWRP Available so better use that ? and With Xiaomi EU Rom, TWRP and Magisk Hidemyapps and Safetynetfix iam able to use Banking Apps and Gpay ? thanks and sorry for the many Questons
Click to expand...
Click to collapse
Xiaomi Eu roms are better than stock and
no need to root, the play store is certified.

Okay thanks, so i take the XiaomiEU Rom. No i want to Root cause i cant acess Android/data without root and thats annoying for me in some games and apps that the XiaomiEU Rom has an Safetynet inside i read yes.

Whether the Xiaomi.EU roms are better than stock is highly subjective. They may be better than the stock chinese rom for international use, but others have reported that the EEA and Global ROMs are working perfectly, the EEA adheres to the necessary privacy and advertising laws and they are developed & distributed by Xiaomi officially.
Additionally xiaomi.eu roms are not official in any way, are not open source, and are "modified" by a group of unknown people who take no responsibility for their version whatsoever, so there is definitely a trust aspect you need to be aware of and if you ever have any problems it is just too bad.

murakh said:
Whether the Xiaomi.EU roms are better than stock is highly subjective. They may be better than the stock chinese rom for international use, but others have reported that the EEA and Global ROMs are working perfectly, the EEA adheres to the necessary privacy and advertising laws and they are developed & distributed by Xiaomi officially.
Additionally xiaomi.eu roms are not official in any way, are not open source, and are "modified" by a group of unknown people who take no responsibility for their version whatsoever, so there is definitely a trust aspect you need to be aware of and if you ever have any problems it is just too bad.
Click to expand...
Click to collapse
11 years that they provide roms, do you really believe that they are unknown, present on XDA on multiple devices.
Their roms have been taken over by MUIMIX, ONE os, Mi rom etc, without bringing anything more apart from a few additional options for some and for others nothing and having tried them all on different devices I always came back to the Xiaomi EU.
Ads and restrictions of EEA or Global roms no thanks.
What is interesting is to keep the bootloader unlocked because in the event of a problem, recovery will be possible and relatively simple, which will not be the case on a stock ROM with the bootloader locked.
Xiaomi sends updates on a stable rom but the update is a stable beta, many have had their phones blocked because of this with phones no longer guaranteed.
When a build has a problem, it is reuploaded the same day, which is really not the case with official Xiaomi.
Try to do better.
Spoiler: Xiaomi EU rom
Based on China Stable / Weekly builds
3way reboot menu (in dev settings)
MIUI Contacts and Dialer
Removed ads in MIUI system apps
MIUI Dialer and Messages apps
Steps counter in Assistant screen
More shortcuts on left lockscreen
Wake up gestures for all devices
AI preloading option in MIUI Lab for all devices
Option to auto-expand first notification
Notifications priority settings
More edit options in Gallery app
Enabled MiDrive in File Explorer
Added landscape mode for SMS app
Sunrise/Sunset in the weather app
Google apps support integrated
Removed 5GHz region restrictions
Confirm dials from call logs
Morning report on alarm at morning
More apps supported for AOD notifications
More styles for AOD screen
Raise to wake gesture
AOD notification received animation
Tap fingerprint sensor to wake toggle
More Camera features
Double tap to lock screen
Battery AI scenes
Allowed disabling specific system apps
Importing theme .mtz from zhuti.xiaomi.com via ThemeManager
No useless Chinese bloatware apps
More free RAM due to less background processes
Mi Video, Mi Music, Mi Browser: No any useless Chinese content
No possibility to re-lock bootloader accidentally with flash any xiaomi.eu release
Added real 27 languages translation made by Official MIUI Fansites and MIUI Fans
Added EU T9 dialer support
Added charging sound switch
Optimized GPS settings for EU
Optimized Battery consumption
Optimized RAM consumption
Added GSMalphabet into SMS app options
SafetyNet passed by default (Google Pay)
Play Store Certified
Deodexed
Added automated tasks in Security app
Added game speed booster
Widevine L1 (for supported devices)

NOSS8 said:
11 years that they provide roms, do you really believe that they are unknown, present on XDA on multiple devices.
Click to expand...
Click to collapse
Not officially on XDA, only as an installation guide since their ROMs do not meed the requirements.
NOSS8 said:
Their roms have been taken over by MUIMIX, ONE os, Mi rom etc, without bringing anything more apart from a few additional options for some and for others nothing and having tried them all on different devices I always came back to the Xiaomi EU.
Click to expand...
Click to collapse
Subjective preference. Subjective, as I indicated.
NOSS8 said:
Ads and restrictions of EEA or Global roms no thanks.
Click to expand...
Click to collapse
Subjective preference again.
NOSS8 said:
Try to do better.
Click to expand...
Click to collapse
Nowhere did I insult you, and this insult is unnecessary. My response was to the original question of whether xiaomi.eu was better or not. My response was less subjective and highlighted multiple other user's experiences of global & EEA (although even Chinese ROM with google services activated gets a lot of praise thesedays and that is what I use, but again that is my subjective preference which I am not trying to get anyone else to follow and did not even mention it).
Not that there is anything wrong with a subjective answer, yet to make a better informed choice either multiple subjective inputs are needed, or a non-subjective comparison.