[GUIDE] How to Pass SafetyNet on Xiaomi.eu

[Slim K]

I tried to follow your instructions but they are simply outdated or they don't correspond to what I see.
You can see my image attached.

So, where should "3 custom" be if for #3 we have ELEPHONE?

You have to reboot your phone sometimes for it to be detected, it should look like the attached screenshots. If it still doesn't work, then download attached pre-config file and unzip in your phone using a file explorer and put in this path:

/Storage/emulated/0/

And reboot. It should reconfigure itself automatically.

 

[Jonny993]

You have to reboot your phone sometimes for it to be detected, it should look like the attached screenshots. If it still doesn't work, then download attached pre-config file and unzip in your phone using a file explorer and put in this path:

/Storage/emulated/0/

And reboot. It should reconfigure itself automatically.

I tried copying the files in the sdcard0 as you told me to do and once I reboot, it ends in a bootloop.
Had to go into TWRP and delete the folder to prevent it.
If you have other brilliant ideas to share I would be glad to test them out lol

 

[StroyYa]

@Jonny993
You just have to copy the file into the base directory of the phone.

 

[Jonny993]

@Jonny993
You just have to copy the file into the base directory of the phone.

ok so... in the meantime thanks for your support..
secondly, I succeeded in copying that damn file over sdcard (for some reason when you extract the file it creates the folder with the same name, resulting in the error I was having!)

So I configured using your guide but still safetynet is false!
I found out I'm using EUROPEAN version of MIUI and set it accordingly.
Any help, now?

 

[Slim K]

ok so... in the meantime thanks for your support..
secondly, I succeeded in copying that damn file over sdcard (for some reason when you extract the file it creates the folder with the same name, resulting in the error I was having!)

So I configured using your guide but still safetynet is false!
I found out I'm using EUROPEAN version of MIUI and set it accordingly.
Any help, now?

As you have noticed, I wrote the word FILE and not Folder but anyways, using Magisk prop module alone won't solve your problem. Basic integrity being false means there is a mismatch between vendor and system img in configuration (the reason my backup from the prop module aka my "config" got you in a bootloop), also I have the EU version as well.
On stock MIUI basic integrity should always be true, unless your ROM is corrupted. As the name Basic integrity implies.
What you can do is collect the logs and post them here by inputting 8 in the first menu in props, attach it here and wait for somebody (including me) to try to look into it. If this is urgent I suggest flashing stock fastboot 12.0.3.0 and then updating using updater in settings.

 

[Jonny993]

As you have noticed, I wrote the word FILE and not Folder but anyways, using Magisk prop module alone won't solve your problem. Basic integrity being false means there is a mismatch between vendor and system img in configuration (the reason my backup from the prop module aka my "config" got you in a bootloop), also I have the EU version as well.
On stock MIUI basic integrity should always be true, unless your ROM is corrupted. As the name Basic integrity implies.
What you can do is collect the logs and post them here by inputting 8 in the first menu in props, attach it here and wait for somebody (including me) to try to look into it. If this is urgent I suggest flashing stock fastboot 12.0.3.0 and then updating using updater in settings.

I'm a little bit confused, am I on EU or GLOBAL rom?
I should be on GLOBAL according to what the About phone tells but not according to the printlist file:

"POCO X3 NFC European (10)OCOOCO X3 NFC=POCO/surya_eea/surya:10/QKQ1.200512.002/V12.0.2.0.QJGEUXM:user/release-keys__2020-08-01
POCO X3 NFC Global (10)OCOOCO X3 NFC=POCO/surya_global/surya:10/QKQ1.200512.002/V12.0.2.0.QJGMIXM:user/release-keys__2020-08-01"

As you can see, the "QJGEUXM" is associated to the EUROPEAN version in this file...

However, I had to compress again the file with the logs otherwise xda wouldn't have let me upload it.
Hope you guys can help me about it!

p.s. I bought this phone on amazon less than 2 weeks ago, waited for the 7 days to end and unlocked the bootloader.
Installed magisk and tried the safetynet check.
I didn't install anything, just updated the rom using the updates coming from XIAOMI..
Why can't I pass integrity check??

 

[pnin]

I'm still on global ROM, unlocked and rooted with Magisk -- and failing "ctsProfile". Will keep trying and report back.

Just reporting success with OP instructions and "POCO X2" setting -- safetynet status is now set to "Basic". Will try other options next...

.

 

[PrussianWolf]

I'm a little bit confused, am I on EU or GLOBAL rom?
I should be on GLOBAL according to what the About phone tells but not according to the printlist file:

"POCO X3 NFC European (10)OCOOCO X3 NFC=POCO/surya_eea/surya:10/QKQ1.200512.002/V12.0.2.0.QJGEUXM:user/release-keys__2020-08-01
POCO X3 NFC Global (10)OCOOCO X3 NFC=POCO/surya_global/surya:10/QKQ1.200512.002/V12.0.2.0.QJGMIXM:user/release-keys__2020-08-01"

As you can see, the "QJGEUXM" is associated to the EUROPEAN version in this file...

However, I had to compress again the file with the logs otherwise xda wouldn't have let me upload it.
Hope you guys can help me about it!

p.s. I bought this phone on amazon less than 2 weeks ago, waited for the 7 days to end and unlocked the bootloader.
Installed magisk and tried the safetynet check.
I didn't install anything, just updated the rom using the updates coming from XIAOMI..
Why can't I pass integrity check??

Easy to solve. You're on European ROM (surya_eea), of course (EU).

The problem is the difference between the MIUI version and the security-patch's date of your phone (marked with red color) and the description in the printslist (marked with blue color)! You're on MIUI V12.0.4.0.QJGEUXM, security patch 2020-10-01 and your printslist says V12.0.2.0.QJGEUXM, security patch 2020-08-01.

Just simple change the printslist-file (with a text-editor like Wordpad or similar else) to:

POCO X3 NFC European (10)OCOOCO X3 NFC=POCO/surya_eea/surya:10/QKQ1.200512.002/V12.0.4.0.QJGEUXM:user/release-keys__2020-10-01
POCO X3 NFC Global (10)OCOOCO X3 NFC=POCO/surya_global/surya:10/QKQ1.200512.002/V12.0.4.0.QJGMIXM:user/release-keys__2020-10-01

Got it? Have fun!

^^

 

[Jonny993]

Easy to solve. You're on European ROM (surya_eea), of course (EU).

The problem is the difference between the MIUI version and the security-patch's date of your phone (marked with red color) and the description in the printslist (marked with blue color)! You're on MIUI V12.0.4.0.QJGEUXM, security patch 2020-10-01 and your printslist says V12.0.2.0.QJGEUXM, security patch 2020-08-01.

Just simple change the printslist-file (with a text-editor like Wordpad or similar else) to:

POCO X3 NFC European (10)OCOOCO X3 NFC=POCO/surya_eea/surya:10/QKQ1.200512.002/V12.0.4.0.QJGEUXM:user/release-keys__2020-10-01
POCO X3 NFC Global (10)OCOOCO X3 NFC=POCO/surya_global/surya:10/QKQ1.200512.002/V12.0.4.0.QJGMIXM:user/release-keys__2020-10-01

Got it? Have fun!

^^

But why does it say "GLOBAL" on the info screen?
However, gave it a go with the updates on the printlists file but still, unable to get the safetynet check.
Still having both values to false no matter what I do..

Now my question: why would I ever want it to be true in the first place?
What am I missing now?

This is a "secondary" phone which I use for gaming purposes, I don't have sim cards on it, I don't use it for payments so... is it really necessary for me this safetynet to true?

 

[Slim K]

But why does it say "GLOBAL" on the info screen?
Now my question: why would I ever want it to be true in the first place?
What am I missing now?
This is a "secondary" phone which I use for gaming purposes, I don't have sim cards on it, I don't use it for payments so... is it really necessary for me this safetynet to true?

To answer Briefly:
1- Historically speaking; Xiaomi manufactured phone have two versions: one for the chinese market and a separate one for the global market, hence the Global description. The only true difference between Global EU and other global versions are the pre-installed apps, the amount of ads...etc to conform to EU regulations, and some underlying configuration changes but that's it.
2- You aren't missing a lot by not passing Safetynet, only apps that check for it will not work. That includes for example: Netflix, amozon video, McDonald's app and most Banking apps.
3- An interesting thing happened a few weeks ago, I bought the Aliexpress 64gb version as a gift to my uncle and confirmed with my own eyes that it's not the EU version, but when I updated it to 12.0.4.0, it downloaded the EU version (w/o any interference from me) and changed to EU version. I suspected also because of EU regulations.

Also I checked your boot logs and indeed as I suspected it throws a bunch of fsverity errors at startup, hinting at your Rom being corrupted somehow. So I advise you, since you have root, to backup persist.img and fastboot to a fresh install, then restoring that img back manually.

 

[Jonny993]

To answer Briefly:
1- Historically speaking; Xiaomi manufactured phone have two versions: one for the chinese market and a separate one for the global market, hence the Global description. The only true difference between Global EU and other global versions are the pre-installed apps, the amount of ads...etc to conform to EU regulations, and some underlying configuration changes but that's it.
2- You aren't missing a lot by not passing Safetynet, only apps that check for it will not work. That includes for example: Netflix, amozon video, McDonald's app and most Banking apps.
3- An interesting thing happened a few weeks ago, I bought the Aliexpress 64gb version as a gift to my uncle and confirmed with my own eyes that it's not the EU version, but when I updated it to 12.0.4.0, it downloaded the EU version (w/o any interference from me) and changed to EU version. I suspected also because of EU regulations.

Also I checked your boot logs and indeed as I suspected it throws a bunch of fsverity errors at startup, hinting at your Rom being corrupted somehow. So I advise you, since you have root, to backup persist.img and fastboot to a fresh install, then restoring that img back manually.

Thank you very much for this awesome description, it helped making things a lot clearer!
I just checked and Amazon Prime Video works without any problem while Mc Donald’s for example doesn’t.
Lucky me I don’t use it nor I use Netflix or the phone for paying purposes..
But I’m interested in what you said about the rom being corrupted but I’m not entirely sure how to do what you said.
Maybe you can link me to some guide, just to be sure we don’t finish OT here.

Thanks guys for your time and patience

 

[Slim K]

But I’m interested in what you said about the rom being corrupted but I’m not entirely sure how to do what you said.
Maybe you can link me to some guide, just to be sure we don’t finish OT here.

Thanks guys for your time and patience

PM me and I will write a guide for you so we don't OT. I usually have it off but just opened my inbox for you :good:

 

[technotika]

More easy :

Hide Magisk Manager on settings of Magisk Manager
Install this module
Done

Thanks for this

 

[payas0]

Interesting.

The POCO X3 fingerprint is now available in the MagiskHideprops module. I tried to use that. But it still failed cts. So as per OPs instruction, I used POCO X2 fingerprints and now it passes safety net.

EDIT: A bit more elegant solution than using a different device fingerprint.

1. Use POCO X3 NFC Global fingerprint.
2. Use custom attestation value: POCO X3 NFC Global

I passed SafetyNet this way.

 

[aterus]

Good morning guys,
I'm sorry to bring this up again. especially since the X3 is already available in the fingerprints-list now.
BUT: I've tried several methods/combinations which have been mentioned here but my SafetyNet in Magisk still fails on all levels (basicIntegrity and ctsProfile).

Prehistory: I'm on Stock ROM, Poco X3 NFC European Version, waited the time to unlock the bootloader, flashed TWRP and installed the Magisk.zip to get root. Then I've installed Busybox and HidePorps modules within Magisk and tried the settings which are mentioned here.

I've attatched my log files, so maybe one of you can spot where I fail.


// EDIT: Ok nevermind! I should have activated "Magiskhide" in the Magisksettings .. *facepalm*

 

[bamzzz]

Interesting.

The POCO X3 fingerprint is now available in the MagiskHideprops module. I tried to use that. But it still failed cts. So as per OPs instruction, I used POCO X2 fingerprints and now it passes safety net.

EDIT: A bit more elegant solution than using a different device fingerprint.

1. Use POCO X3 NFC Global fingerprint.
2. Use custom attestation value: POCO X3 NFC Global

I passed SafetyNet this way.

Working perfectl on Global Rom 12.0.4.0

 

[payas0]

Working perfectl on Global Rom 12.0.4.0

Just yesterday I noticed that there's already a separate entry for European and Global fingerprints in MagiskHideProps. Just worth noting.