yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
You can download practically any app, including the Google apps like GBoard, GMaps, etc from https://www.apkmirror.com

But if you are not using any app that complains about SafetyNet, why should you bother, have the GApps, Magisk, enjoy

Ofc, you would not be able to use GPay, but I doubt that even if you trick the SafetyNet to pass, that your Chinese firmware is not ready for GPay by NFC, and that you could never make it work

SafetyNet calls to the Google API, it requires to have Google Play Services installed

Let's do it quick and dirty. Use some root file explorer - advising you to install MiXPlorer. Grant it root and go to Root, then navigate to /data/adb/modules/MagiskHidePropsConf

Find the system prop file in that folder.

Make it there a backup copy system.bak, and don't touch the rest

Open system.prop as a text file - MiXPlorer can do everything for you.

Lines starting with # are comments, they don't count.

Over the rest of the lines, paste the following stuff:

ro.product.model=davinci

ro.build.fingerprint=Xiaomi/davinci_eea/davinci:10/QKQ1.190825.002

ro.build.version.security_patch=2020-07-01

Reboot and getprop those three props (they have to return those values you pasted to the file), and check your SafetyNet

Once you are done, revert system.bak to system.prop, reboot and erase from your memory any reminisce about that back-door to MHPC?

Btw, you asked about updating Magisk to Beta (or latest Canary). Why not, this will soon become Stable as well

With that new Magisk Manager, SafetyNet test will show you visually if CTS Profile attestation used Basic or Hardware mode (so no need for analyzing the logcat anymorey).

If it uses Basic (passing CTS or not), then further playing with Forcing CTS to Basic makes no sense - then something else brakes your CTS

Brw, [MENTION=4667597]Didgeridoohan[/MENTION] and me independently tested with your stock fingerprint and got it passing the SafetyNet.

Hence there must be something else causing you to fail, like that GApps you had to install to that Chinese firmware
[Magisk] pungat:
Thank you for the quick reply.

Samsung Galaxy A01 Core SM-A013G Android 10 Go Edition (Region XID) :

ro.build.fingerprint = samsung/a01corextc/a01core:10/QP1A.190711.020/A013GXXU1ATGE:user/release-keys

ro.build.version.security_patch = 2020-07-01
[Magisk] Mirardt:
[MENTION=7786725]zgfg[/MENTION]

Thank you, I'm gonna try that when I'm back home.

Just a quick clarification question: You mean the specific GApps that my seller used might cause the problem and if I installed them from another source or apk it might solve the problem, not that "Google Apps in general cause problems on your device", right? In that case, I could wipe and reflash Magisk with twrp and try to install those google apps from another source or with another installer and it could solve the problem, right?
[Magisk] zgfg:
I don't know what kind of GApps can fix your SafetyNet.

Actually, I don't know how is it with other Xiaomi phones and with Chinese firmwares, but for most other Xiaomi phones people can simply flash the global, eea, etc and forget about the cn firmware (if they bought with).

But your model is only for Chinese market and I don't see any other firmware:

https://xiaomifirmwareupdater.com/miui/cezanne

Btw, how about 4g and possibly 5g if you are not in China, does it work or did you have to tweak something
[Magisk] Mirardt:
Yeah its probably because of the Mediatek chip that everybody is hesitant. As I understand it, xiaomi.eu doesnt do anything with devices that come with a Mediatek chip.

4G works, tomorrow I will know if 5g works.

I do have a big issue with voLTE and voWifi though, I just can't make them work. Other than that, passing the google safety test and bloatware, the phone is a dream. 120hz OLED that gets really bright and everything else I could wish for for about 300€. The Safety Test stuff im working on with you guys and as far as I understand it, bloatware is no issue to remove with a rooted phone.

Oh and also before the root my banking apps push tan worked and after the root it refuses to start. Not sure if that is relevent / helps in any way. This is another thing that I just assume I can work around after passing Safety Net.
[Magisk] JaboJG:
The GApps with our phone should be installed by using the preinstalled GetApps app. Like in this video https://www.youtube.com/watch?v=Tz7Vi68kbuU

MIUI is just a skin for Android, it's not a separate OS. It's like OneUI for Samsung. Everything has the capability to work, e.g. I just got my country's COVID-19 Exposure Notifications app working.

What you need is a fingerprint that will let CTS Profile pass. Once that passes then you should be able to use Google Pay. Make sure you've chosen the HCE Wallet option in the NFC settings and given all the permissions required for Google Pay, Play Services Framework, and Google Services Framework.
[Magisk] Didgeridoohan:
There's a discrepancy I'd like to clear up...

You've previously reported that the ro.product.model prop for your device is "Mi 9T", here:

https://xdaforums.com/showpost.php?p=83331537&postcount=3904

That also matches Google's records:

https://storage.googleapis.com/play_public/supported_devices.html

The prop value you've got here, "davinci" is the device (ro.product.device).

Are you simply using the device prop to force basic attestation, while the actual model makes it use hardware backed key attestation?
[Magisk] zgfg:
Glad you asked - you care about all your props?

I'm using "davinci" to force CTS to Basic mode (Google constantly changes things, one day it uses by itself Basic, mext day no more, I keep "davinci" just in case), stock value is "Mi 9T"
[Magisk] Didgeridoohan:
Yeah... I want the info in the module to be correct. :good:

Thanks for the clarification. You had me worried there. :D
[Magisk] Aijen:
Thanks a lot! One Request can Your please add Fingerprint for Xiaomi Redmi Note 5ALite (Ugglite) i extract it a valid fingerprint from AOSPExtenderd Custom Rom that pass Safety Net without problems and get my device certified in PS.

I share it because not all custom roms for this device pass the certified. Like Xiaomi.EU or MIUI.AM
[Magisk] Aijen:
Its for 7.1.2 nougat
[Magisk] UdoChudo:
Hi could you please update Mi note 2 Certifications to last version Miui 9.6.1.0 ?

If not pls tell me how to change Fingerprint of my phone to pass throught Cts ??
[Magisk] Didgeridoohan:
Regarding fingerprint (this can all be found in the documentation, linked in the OP):

Spoofing device's fingerprint to pass the ctsProfile check

Can I use any fingerprint?

Finding a certified fingerprint

I still can't pass the ctsProfile check

Regarding SafetyNet:

https://didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
[Magisk] UdoChudo:
I already read all of this but don't understand how i can add custom certs in to list could you please tell me step by step how i can do this ?

i already found certs

BUILD_FINGERPRINT :=

Xiaomi/scorpio/scorpio:8.0.0/OPR1.170623.032/V9.6.1.0.OADCNFD:user/release-keys

but i don't understand what i need to write in printslist file ?

Sorry for stupid question
[Magisk] Didgeridoohan:
Ooops! :eek:

Seems like a chunk of that part of the documentation accidentally got deleted a couple of updates ago. I'm about to push an update for another couple of fixes, so I'll take care of that as well. I'll also include the fingerprint you provided (tested and working)... Thank you for alerting me to the broken docs. :good:
[Magisk] Didgeridoohan:
Update to v2.3.5-v23

So, another bugfix release. But, I took the opportunity to also do a couple of small improvements.

[MENTION=1319544]MajinkenSword[/MENTION] I don't know if this update will fix your issue, but please test. If the issues still persists, try uninstalling the module and reinstalling.

Changelog

v2.3.5

Fixed issue with busybox version detection.

Fixed the documentation. Some parts had been accidentally deleted. Oops...

Improved log collecting.

Added and updated fingerprints for the Xiaomi Mi Note 2 and Redmi Note 5A Lite, list v23. Thank you to [MENTION=6550184]Aijen[/MENTION] and [MENTION=8892402]UdoChudo[/MENTION].

Minor improvements here and there. Hopefully I haven't broken something this time...
[Magisk] UdoChudo:
Meh....Unfortunately...but i don't got solved my problem with ctsProfile. already try reinstall module and reset configs with reboot phone...
[Magisk] Didgeridoohan:
Keep reading the docs:

https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check

https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config#logs

And, MIUI is finicky... There are many reports of not being able to pass ctsProfile by changing the device fingerprint. Especially on the China builds.
[Magisk] UdoChudo:
I try pass safety on Global Beta Miui 10....Meh..i will try MiuiPro rom maybe this will help
[Magisk] Didgeridoohan:
Everything looks like it should in the logs (except that you didn't update to the new and shiny release :crying:).

A different ROM might help...
[Magisk] MajinkenSword:
Thank you! Issue seems to have been fixed. ? cheers!
[Magisk] aredpanda:
[MENTION=4667597]Didgeridoohan[/MENTION]

Hello there, I'm coming here as a last effort to get this really weird device to bypass safety net. The phone is a Blackview Ultra Plus and I've already setup Magisk in it with Magisk Hide and all that, however the phone is still failing SN on both ctsProfile and integrity. What chances do I have to bypass this using this module?

Thanks in advanced for any reply

edit: this is the current state of affairs, looks pretty bad:
[Magisk] Didgeridoohan:
None.

This module will only help you bypass the ctsProfile check by using a certified fingerprint. If you can't pass the basicIntegrity check you've got something else going on.

Take a look here and first see if the device fulfills the basic requirements and if MagiskHide works at all:

https://www.didgeridoohan.com/magisk/MagiskHide

If it does (I'm suspecting the kernel is missing the mount namespace support, though), you can keep reading for tips and tricks.

After having done all that, if you still can't get things working, make sure to read through the section about grabbing logs and providing details:

https://www.didgeridoohan.com/magisk/MagiskHideHelp

And please post any further MagiskHide/SafetyNet troubleshooting and queries in the General support thread. I wan't to keep the off-topic away from this thread as much as possible. I'll answer you there if needs be...

Edit: And could you please edit your post to remove that image. It takes up the entire screen (and then some) if you happen to be on a computer... Use the attach feature or at least add HIDE tags to the image. Thank you.
[Magisk] Purecut:
Hi,

I just want to say thank you. After running your script the SafetyNet check passed.

I'm using a Sony Xperia Z5C and before your script I had the ctsProfile: false, because I use the "LineageOS 14.1 Berni's alternative builds" and this build used a not certified fingerprint. After your script everything passed green :)
[Magisk] Marbodal:
I passed ctsprofile and basicintegrity with v2.3.4 on my Huawei Y6 (ATU-L21) with the fingerprint from the Oneplus 6 but after updating to v2.3.5 the ctsprofile failed. Just a heads up from my side.

---------- Post added at 04:01 PM ---------- Previous post was at 03:48 PM ----------

I passed ctsprofile and basicintegrity with v2.3.4 on my Huawei Y6 (ATU-L21) with the fingerprint from the Oneplus 6 but after updating to v2.3.5 the ctsprofile failed. Just a heads up from my side.

EDIT: Here is the log files if it would help anything

https://files.fm/u/s26etdn4
[Magisk] Didgeridoohan:
There was absolutely no change in how the fingerprint is set between v2.3.4 and v2.3.5. And your logs show that everything is set as it should. There's something else going on. Don't know what... Sorry.
[Magisk] Marbodal:
Changed the fingerprint to P20 Pro and now it work :)
[Magisk] AxE_09:
Hi, can you please add the fingerprint sensor for Asus Zenfone Max Pro M1 ZB602KL as I'm having the same problem of cts profile being false and basic integrity as true. Thank You
[Magisk] Didgeridoohan:
If someone can provide one for me, sure. Here are the instructions:

https://github.com/Magisk-Modules-R...ter/README.md#finding-a-certified-fingerprint

Edit: You can also use any fingerprint available in the list. Explained here:

https://github.com/Magisk-Modules-R...ob/master/README.md#can-i-use-any-fingerprint
[Magisk] andrea0807:
I installed this module but in my case it doesn't work, safetynet check doesn't pass the check.

I have a poco F2 Pro with rom xiaomi.eu weekly (Android 11)

Can i solve?
[Magisk] Didgeridoohan:
Have you set it up with a certified fingerprint? And have you made sure that MagiskHide is active? Do you have mods like EdXposed installed? Etc...

If you can't provide that info, providing the module logs might show something.
[Magisk] andrea0807:
What does certified fingerprint mean?

I registered my fingerprint normally in the settings.

Magisk Hide is activated and magisk is installed with a random name.

I have not installed Xposed

View attachment 5109707

Inviato dal mio Redmi K30 Pro utilizzando Tapatalk
[Magisk] neroes:
Hi, how do I get the following app to work:

https://play.google.com/store/apps/details?id=de.volkswagen.mitarbeiterapp&hl=de

unfortunately I am pointed out to root.

Xiaomi Mi9

CrDroid 6.10

Magisk 21.0

Manager 8.0.0

MagiskHide Props Config v5.3.5-v104

SaftyCheck OK
[Magisk] Didgeridoohan:
With "certified fingerprint" I mean one of the prints from the list in the module. You need to activate that or the module won't do anything.

If you have picked a print and CTS still fails, have you confirmed that MagiskHide is actually working? Toggled it off and on again?

And if you want further help I need the module logs. Follow the link in my last post.
[Magisk] Didgeridoohan:
That's a little off-topic for this thread. You're passing SafetyNet, so everything's good there...

Take a look here, and then post on the general support thread if you need further help after testing these tricks and tips:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] ipdev:
Little OT here. ;)

Systemless SuperSU was implemented for Android 6 but, systemless did work on some Samsung 5.1.1 builds.

Can you tell the last time I used TouchWiz. :D

Dynamic partitions might be what you are referring to?

source.android - Link

This may be out-of-date but, a good and comprehensive read to understand root and SELinux.

chainfire.eu - Link

Cheers. :cowboy:
[Magisk] andrea0807:
It works, great

Spoiler content hidden.

Inviato dal mio lmi utilizzando Tapatalk
[Magisk] Valiante:
I'm having trouble setting my "basic key attestation" to Pixel 3.

I go through all the appropriate prompts and select Pixel 3, then when I reboot it switches back to Nexus 5.

CTS profile and basicIntegrity fail. I know what I'm doing was working a few days prior before I updated the module.
[Magisk] pndwal:
Which is exactly as intended! This is default model selected for your device that doesn't use Hardware backed Attestation but is from the same OEM.

Your Pixel is now spoofing this device, at least in model props.

basicIntegrity failing is your problem.

Basic / Hardware Attestation type will be irrelevant if this is failing. You need to fix this first. It will necessarily trip ctsProfile, and it should pass regardless of ctsProfile status, or evalType.

After you have basicIntegrity, configure MagiskHide Props Config for fingerprint (if needed) and 'Force Basic', if in fact Magisk Manager is showing evalType as Hardware.

Nb. SafetyNet basicIntegrity and Basic Attestation are two different things, and shouldn't be confused.

Nb2. Even 'fixed' Canary EdXposed modules are now tripping basicIntegrity again, and must be removed or disabled.

Nb3. After getting full SafetyNet Pass, you can set device for Force Basic function manually. Changing from Nexus 5 to a Pixel device may allow mor device specific features / apps / functions to work. Dev here mentioned Pixels 3a, 2 and 2XL all reportedly work (allow Basic evalType). PW
[Magisk] ipdev:
So I am now confused again. :confused:

This is the second (third) time this has come up.

Where is this Nexus 5 value coming from?

I just tried it again, and I do not see a Nexus 5 as a default, recommended, preset, set or changed to.

Yes I have rebooted and every thing I set using MHPC stays what I set it to.

Regardless.

If a Pixel 3 or Pixel 3a is chosen as the device to use with Force BASIC key attestation, it should not change after a reboot.

I use the Force BASIC option on Poco F2 Pro and Pixel 4a.

Both are set to use Pixel 3a XL to force basic.

I switched to Pixel 3 just to see if it would make a difference.

No matter how many times I reboot, it never changes unless I change it.

Poco F2 is stock MIUI Global, no fingerprint set.

Pixel 4a is running DU Android 10, fingerprint is set to Poco F2 at the moment.

Testing the 12.0.4.0 F2 Pro fingerprint.

A little clarification on why this would change without user interaction or where this Nexus 5 setting comes in would be appreciated.

Cheers all. :cowboy:
[Magisk] pndwal:
https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228/post83592979 :good:

Hope that clears that up.

You may know if Pixel 3 actually uses Basic Attestation. Its possible that Force Hardware is entirely unnecessary for Pixel 3, but the fact that the user Didge is replying to in link above selected Force Basic for a Pixel 3, and that Didge has only mentioned Pixels 3a, 2 and 2XL for Basic evalType suggests this is in fact needed/it's set to use Hardware.

If Pixel 3 uses Hardware, it seems Force Basic should invoke Pixel 5 as per all Google devices.

I suspected the user I replied to is actually trying to remedy basicIntegrity fail by using Force Basic function. Many seem to confuse the two 'basics'.

Thinking it through, if it actually does use Basic attestation but is not flagged as one of those that does in MagiskHide Props Config, I suppose it will still invoke a device on that MHPC OEM list for 'Basic' in any case.

Regardless, he needs to remedy basicIntegrity fail. PW
[Magisk] ipdev:
That post initially put it out of my head (closed the topic) until the last one.

This is the third user that specifically stated they selected a device under the Force BASIC option and it was changed to a Nexus 5 after a reboot.

To explain a little more.

When I select option 2 Force BASIC key attestation

It shows the stock value of the device.

Select a device to use to Force BASIC and Reboot.

Run props again and under option 2 it will show the device I select.

I have never seen Nexus 5 show up.

I have tried this on other devices that do not require it and none show up or change to a Nexus 5.

I would have to charge up my Nexus 5 and try but, at that point it would be silly just so I could see a Nexus 5 as a default value. ;)

Plus I think it's back on a stock google rom at the moment. I was testing a module on different SDK levels the other week.

That is why I am more confused, because I can not make it show, recommend or change to a Nexus 5.

Normally I am good at breaking things. (Head down, run full speed at wall. Hulk Smash.) :D

This option is either solid, good at bending or I am just not finding the week point. ;)

I reset MHPC and took a few screenshots along the way on my Pixel 4a and Poco F2.

Cheers. :cowboy:
[Magisk] pndwal:
It's OK mate!

But you need to select first option in Force BASIC Key Attestation screen:

y - Yes (use default value)

Default is Nexus 5 for Google devices.

Seems you always use "Expert Mode" (f - Pick from device list)!... Figures... :D

Simple "y" option exists for those who don't like multiple choice!

Edit: Anyhow, I'm chuffed if you prefer "f". I just remembered, it was my suggestion! (...Not the "f".) ;)

Question for Didge:

Why'd you use "f"? (dare I ask.) ... "Forced" I imagine? ...or "Fools"? PW
[Magisk] Didgeridoohan:
It might be that you're experiencing a small error in your module settings file. If you want me to check it out you can post the module logs here (or send to me through PM if you prefer).

You could also just try resetting the module ("Reset all options/settings" in the menu). That will completely clear our the settings file and you can start over. You don't even have to reboot directly after the reset, but can enable forced basic attestation and pick your device if choice immediately (and then reboot).

That should get you going, but I would of course appreciate a peek at those logs...
[Magisk] Didgeridoohan:
[MENTION=7280276]ipdev[/MENTION] Yes, [MENTION=7550078]pndwal[/MENTION] is correct. If you just select "yes" without picking a device you will get the default value. Which for Google is the Nexus 5. And, there seems to be a hard to find bug where the settings entry for this feature in some cases gets corrupted and can't be properly read (so it reverts to the default).

The reason the option uses "f" is that I initially called the menu entry "Pick from fingerprints list" (since I'm using the module prints list to get the module values). That got confusing though and some users thought they would need to pick a certain fingerprint for the feature to work, etc. Therefore I changed the entry name to "Pick from device list", but forgot about the assigned letter. It's on my to-do list for the next update...
[Magisk] pndwal:
Would that cause his SafetyNet basicIntegrity fail though?

As mentioned, my suspicion was that other issues (EdXposed etc?) are the real problem.

Sounded to me as if MHPC is working exactly as intended, although he is concluding ctsProfile is failing because it's not working... I guess BASIC evalType check would confirm that it is working.

Aw, f is more exciting! Might get people asking you more questions... "F"ix-device-specific-functions-when-default-setting-doesn't-work?... "F"or-those-wanting-more?... "F"ound-a-better-device-to-spoof-for-this?... "F"un-and-games-trying-to-make-value-added-features-work?... or just "F"un-mode!...

... Better "F"orget that. :( PW
[Magisk] Displax:
Pixel`s update

Pixel 2=google/walleye/walleye:11/RP1A.201005.004/6782484:user/release-keys__2020-10-05
Pixel 2 XL=google/taimen/taimen:11/RP1A.201005.004/6782484:user/release-keys__2020-10-05
Pixel 3=google/blueline/blueline:11/RP1A.201005.004/6782484:user/release-keys__2020-10-05
Pixel 3 XL=google/crosshatch/crosshatch:11/RP1A.201005.004/6782484:user/release-keys__2020-10-05
Pixel 3a=google/sargo/sargo:11/RP1A.201005.004/6782484:user/release-keys__2020-10-05
Pixel 3a XL=google/bonito/bonito:11/RP1A.201005.004/6782484:user/release-keys__2020-10-05
Pixel 4=google/flame/flame:11/RP1A.201005.004/6782484:user/release-keys__2020-10-05
Pixel 4 XL=google/coral/coral:11/RP1A.201005.004/6782484:user/release-keys__2020-10-05
Pixel 4a=google/sunfish/sunfish:11/RP1A.201005.006/6828489:user/release-keys__2020-10-05
[Magisk] ipdev:
A quick update for the prints list.

Poco F2 Pro Global V12.0.4.0

Cheers. :cowboy: