yashsingh1/xdaforums huggingface dataset:
[Magisk] pippo45454:
Hi,I mean authentication for bank app does not work.....for all other apps fingerprints works....

Do you have suggestions?
[Magisk] zgfg:
Please understand that device fingerprint has nothing with the finger and the fingerprint sensor - they just share the same name.

As you reported in the other thread, your SafetyNet is now passing.

Btw, is there any other way you could authenticate to your banking app?

If that babking apo detects root (and because of that does not allow you to authenticate by any means, not only by finger) then please use the guide how to potentially hide root from some aops (I sent you by PM)
[Magisk] TheGame455:
Xiaomi Redmi 7A (Android 9.0):

Xiaomi/pine/pine:9/PKQ1.190319.001/V11.0.7.0.PCMMIXM:user/release-keys

Xiaomi Redmi 7A (Android 10):

Xiaomi/pine/pine:10/QKQ1.191014.001/V11.0.3.0.QCMMIXM:user/release-keys

It would be nice if you could check and add these. Thanks in advance!
[Magisk] ipdev:
Do you have the matching security date for these prints?

Little hard to test them without the correct date. ;)

Cheers. :cowboy:
[Magisk] TheGame455:
Yes I do, here they are:

Android 9.0: 2020-03-01

Android 10: 2020-07-01

Those should be the correct dates, sorry for any hassle.
[Magisk] retroboy80:
Samsung M21

Samsung Galaxy M21 SM-M215F (10):Samsung:SM-M215F=samsung/m21nsxx/m21:10/QP1A.190711.020/M215FXXU2ATI9:user/release-keys__2020-09-01

thank you for your work!
[Magisk] Techguy777:
Yes thanks that confirms what i'm saying with not full root. No system write access. I have 415MBs left in system partition so a little bit of room. This is really troubling because in my eyes its like partial root. Sure you can do about 90 percent of stuff with magisk but not system changes. For instances the build prop its not really changed and the system knows that its like spoofing more than editing. Now I know this isn't anyone's fault but it sucks. You truly can't mod anything serious like making your security patch a different date. I tried with the magisk props it still doesnt work because the system reads the real build prop on boot and knows it does not match. I have an S6 tablet samsung and S7 edge phone. Me personally Id rather go back to the days of system root. I really wonder if they will shut root down one day. Is there anyway at all to mod the system with adb or twrp terminal or will it just boot loop? IM on android 10 one UI 2.5 so its really up to date and fstab says mnt_flags system ro,barrier=1,discard

---------- Post added at 03:51 PM ---------- Previous post was at 03:46 PM ----------

Heres my fstab, wouldnt we be able to edit this file to get full access just like the data partition?

#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>

#/dev/block/bootdevice/by-name/system / ext4 ro,barrier=1,discard wait,slotselect

#/dev/block/bootdevice/by-name/metadata /metadata ext4 noatime,nosuid,nodev,discard wait,formattable

/dev/block/bootdevice/by-name/userdata	/data	f2fs	noatime,nosuid,nodev,discard,usrquota,grpquota,fsync_mode=nobarrier,reserve_root=32768,resgid=5678	latemount,wait,check,=ice,quota,reservedsize=128M

#/dev/block/bootdevice/by-name/bluetooth /vendor/bt_firmware vfat ro,shortname=lower,uid=1002,gid=3002,dmask=227,fmask=337,context=u:object_r:bt_firmware_file:s0 wait,slotselect
[Magisk] zgfg:
To make (real) changes to fstab, you would need to flash to vendor from TWRP, but then also followed by reformatting the system.

However, with SAR, you can have vendor under the system (system as root) ... so you may better go for custom ROMs

Btw, if you followed the developping story about SafetyNet (ups and downs), here and in the Magisk thread, you could see that once Google decides to close the pipe firmly and to no more rely on the spoofed props to fall to Basic CTS attest but if they fully enforce Hardware CTS on the all realatively new phones/chipsets, then Magisk could no more hide that Bootloader was unlocked - and you could no more cheat to Plyastore, banking apps, Google Pay, etc.

If you prove that you can really break their grandiose SafetyNet scheme (Hardware CTS attest), you could apply for a million dollar price from Google themselves

Bcs of all that, earlier this year TJW decided to downgrade Magisk Hide default to Off, to warn every user that hiding Magisk and root becomes optional, no more granted nor guaranteed.

You can read more of a philosophical debate on TJW Twitter site

[youtube]90WD_ats6eE[/youtube] and root is no more the good ole root
[Magisk] LiveTeXon:
Cannot pass ctsProfile at all

Hey, I have an problem with my SM-G975F (Galaxy S10 Plus Beyond Version) I activate Device Fingerprint and Force BASIC key attestation but the ctsProfile won´t go to true... I have the newest Samsung Firmware and Mods from Magisk.
[Magisk] Techguy777:
I knew all of that Im not honestly not worried. Ive never used magisk hide or anything like that. I don't use any banking apps nor do I play any online games like fornite, pubg, pokemon go, and whatever else. My only concern is that chrome now won't work if it finds root or edxposed which is fixable at the moment. I also don't like that netflix likes to not give me fullhd even though I paid for it with my S6 if Im rooted without a permissive kernel. SO netflix goes if they do decide to be dicks even further. Listen 1 thing is for sure if people into android development refused to pay for netflix and used a free tv app like show box than they would reconsider. If America rooted the way other countries do things would change because America is a cash cow.
[Magisk] zgfg:
I can disable Magisk Hide (and reboot), making Magisk, root and the fact that Bootloader is unlocked fully exposed, but my Chrome still works happily
[Magisk] zgfg:
Wrong thread, deleted
[Magisk] Mirardt:
Hello there :)

My name is Mirardt and I'm a first time ever Android user (yay!). The phone I fell in love with is the K30 Ultra and boy, I didn't know what I was signing up to ...

But instead of boring you with the story, here is a summary: Google Pay, Chrome etc. didnt work so I unlocked the phone, flashed twrp and Magsik, installed Magiskhide props config and tried out everything there is regarding fingerprints (as far as I understand it). I tried 4 different fingerprints.

Its always the same as even before unlocked the phone: basic integrity is true, ctsProfile is false.

I would be infinitely thankful for help.

Mirardt
[Magisk] zgfg:
Congrats that you have achieved all that as a newcomer

If not yet, Magisk Hide must be enabled in Magisk Manager settings

If it's stock firmware, you should have used the MHPC option to enforce Basic CTS attest, not messing up with the fingerprint

Finally, there is a thread how to fix GPay

https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
[Magisk] Mirardt:
Thank you!

Magisk Hide is enabled.

Oh wow I didn't get this at all. Now i reseted all options/settings, rebootet and then "force[d] BASIC key attestation" with the Redmi K30 Pro, then rebooted. Unfortunately, it still doesnt work.

Should I try differfent devices, too? If not, any idea what else to do?

Looking forward to try out that GPay solution after my ctsProfile passes!

Thank you so much for your help!!

edit: tested it on a bunch of devices now, no difference.
[Magisk] zgfg:
Please what you get if you execute:

getprop ro.product.model

Also, are you running Canary Magisk Manager, to post its SafetyNet test screenshot, to see whether the CTS attest was really forced to the Basic mode

Alternatively, you can obtain the same info by analyzing a logcat from the particular SafetyNet checker:

https://xdaforums.com/showpost.php?p=82935207&postcount=40368

Do you have any Magisk module installed - disable all, reboot and retest.

Maybe you installed some apps requiring root?
[Magisk] Mirardt:
I get "cezanne".

Logs are attached.

No modules installed, except MHPC.

Also, I tried the GPay solution and it doesn't work.

Thank you :)

edit: I think my Terminal and SQLite Editor required root access, also the Logcat reader. Probably not what you meant, right?
[Magisk] ipdev:
Gave them a quick test and split results for me.

Pixel 3aXL - Fail. Nexus 7 (2013 WiFi) - Pass.

Not the first or last time this will happen.

Not sure why some prints work across the board, while others will fail on some devices.

As long as the print passes Didgeridoohan's test, he will add it to the list.

Quick test and it worked for me.

Looks like you have a 9 Pro (joyeuse) ?

curtana is a 9S (could also be called a 9 Pro..)

Did I ever mention I hate Xiaomi's name/branding strategy? :eek:

From Google's certified list.

Redmi Redmi Note 9 Pro curtana Redmi Note 9 Pro

Redmi Redmi Note 9 Pro curtana curtana

Redmi Redmi Note 9 Pro joyeuse Redmi Note 9 Pro

Redmi Redmi Note 9S curtana Redmi Note 9 Pro

Redmi Redmi Note 9S curtana Redmi Note 9S

I grabbed the July EEA builds.

The ones that match the build you mention.

curtana is QJW instead of QJZ

Give the 9 Pro and/or 9S print a try and see if it fixes your problem.

Not sure why it would but, just to make sure. ;)

Just rename the attached file to printslist to use.

Custom fingerprints list GitHub - Link

Cheers all. :cowboy:
[Magisk] ptuner:
Hello developers,

I am trying to use this app to spoof the IDs, running lineage OS 16 on OP5. My props are not being spoofed it seems using this in the terminal, I have also used many other spoofing like modules from edxposed, and they dont seem to do the trick too, so it seems to be some sort of universal problem with my system.. I check about phone, and apps like CPU Checker and CPU-Z, phone name and build number remain the same... Phone is rooted, magisk installed, edxposed, no GAPPS or microgapps, etc.

Someone please help.
[Magisk] pippo45454:
Thank a lot for your work

Could I ask you you to describe the procedure step by step?

I don't understand how to change printlist
[Magisk] zgfg:
Yes, ofc, MHPC, logcat, and so are not suspect, I wanted to be sure you have no EdXposed or something that opens another story how to pass SafetyNet.

And as you said earlier, it doesn't make sense to try with GPay instructions until you first fix CTS profile - hence you can disable modules for GPay for now

Your Basic Integrity passes but CTS profile fails although using Basic type:

>> "ctsProfileMatch":false,

>> "basicIntegrity":true,

>> "evaluationType":"BASIC'

which means that MHCP did its part but it didn't help

(you could test by disabling MHCP in Magisk Manager and reboot - MHCP will remember its settings for future, once it wiuld be-enabled again, then your model should become Mi 10 Ultra or similar, with evaluation Type: HARDWARE)

It means there is something else causing CTS profile to fail (but you say no other modules or changes by other root apps)?!

What is your MIUI firmware, global/eea/indian/russian/chinese or maybe eu weakly build, some beta A11?

I will try by faking your fingerprint, please post the results for:

>> getprop ro.build.fingerprint

>> getprop ro.build.version.security_patch
[Magisk] Mde1:
Please Add POCO M2 PRO to the list

POCO M2 Pro not on the list :rolleyes: . I am not being able to use Google Pay & Banking apps on my POCO M2 PRO :crying: :crying: :crying:. Can I use POCO X2 for POCO M2 Pro ??? :confused: . Please Update !
[Magisk] Mirardt:
Oh ok I deinstalled GPay for now. As for apps, the only "suspicious" ones I know of is the chinese app GG that installed google services, including one with a bullet as an image with the number "2020" on it. All google services were preinstalled by the company that sold me the phone, but I had to reinstall google services via that GG app after unlocked the phone. I attached an image with all my apps.

After disabling MHPC and rebooting my basic integrity was still true. This also was the state before unlocking and rooting, basic integrity was true and CTSprofile match was false. I attached the logs.

My MIUI firmware is chinese, MIUI version: 12.0.12 .

Oh wow, nice! I got the following responses:

getprop ro.build.fingerprint Redmi/cezanne/cezanne:10/QP1A.190711.020/V12.0.12.0.QJNCNXM:user/release-keys :/ $ getprop ro.build.version.security_patch 2020-09-01 :/ $

<3
[Magisk] Didgeridoohan:
Oh crap... I spend a couple of days off XDA and the thread litteraly explodes! I'll try to adress everything (that haven't already been adressed), but if you've asked something in the past few days and you do not get a reply from me soon (and with "soon" I mean within the next 24 hours or so), hit me up again.
[Magisk] Didgeridoohan:
That very likely doesn't have anything to do with root... And there's no advantage/difference really between "system" and "systemless" root. None is more "root" than the other. Even SuperSU was systemless as far back as Android 6 (I believe it was, memory is a bit muddy on that detail).

Current reasons why it doesn't work mounting /system as rw are usually (but probably not limited to):

You're trying to mount /system rw on a SAR device. "System as root" means that you need to mount the root directory, "/".

Your device uses the "whatever" file system (I can't remember the name, and since I'm trying to reply to a bunch of posts in a limited time I'm not gonna look it up) that simply cannot be mounted rw. Google introduced that with the Pixel 4, I believe (again, muddy memory).

Regarding your issues with trying to change the security patch date:

It might of course be that whatever problem you have happens earlier in the boot process, but have you tried changing the execution for that particular custom prop to post-fs-data? Earlier than that is hard to get...

If you provide the module logs (with the module set up as you want it and when it doesn't work as exptected) it'll be easier to help.

You mean you want to have a custom prints list? But according to the message you sent me you are passing CTS already, so using a different fingerprint shouldn't help with that... Unless of course the app in question is disabling the fingerprint authentication because it's not supported on your device. But, it's more likely that the app is actually detecting Magisk and disabling the feature because of that (yet, detecting Magisk even with MagiskHide active and the Manager repackaged with a random name is rather trivial if you know what you're doing).

Take a look here if any of these tips help: https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

If you really wan't to use a custom prints list it's documented here: https://github.com/Magisk-Modules-R...lob/master/README.md#custom-fingerprints-list

I guess you might already have read that, so that might not be much help... If you still need help with that let me know, but you could also provide whatever print it is you're trying to use and I'll add it to the list (I'm planning a fingerprints list update in the next couple of days, when life permits).

First the question: https://github.com/Magisk-Modules-R...ob/master/README.md#can-i-use-any-fingerprint

Second, the last statement: https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x

This is most likely why you can't pass CTS. Chinese firmwares aren't usually certified with Google (wich is confirmed by the fact that GApps didn't come preinstalled on your device).

Solution: Use one of the certified fingerprints from the included list.
[Magisk] Didgeridoohan:
Phew... Wasn't that bad actually.

I think I got everything (in this thread at least, I've been mentioned quite a bit elsewhere the past couple of days).

Back to real life!
[Magisk] Mirardt:
I tried with 4 different fingerprints and non of them worked. Logs are here: https://xdaforums.com/showpost.php?p=83627921&postcount=4153

Thanks a lot for helping and for making the module! :angel:
[Magisk] Didgeridoohan:
Ok. Thanks for confirming... I haven't looked at those logs yet, but will as soon as I can.

You said that you have enabled MagiskHide, but have you tried toggling it off and on again? That sometimes work/is necessary.
[Magisk] Mirardt:
Thanks for that! Yep I did toggle it.

edit: there is an update to Magisk available, should I update it or rather let everything as it is for now?
[Magisk] Dr.MI:
Meizu 16th

Hi,

If you could add this fingerprint that would be great.

Meizu 16th

ro.build.fingerprint=Meizu/meizu_16th/16th:8.1.0/OPM1.171019.026/1554756792:user/release-keys

ro.product.flyme.model=M1882

ro.build.version.security_patch=2019-03-01

Thanks in advance.
[Magisk] zgfg:
Strange, I can pass SafetyNet with your exact props:

>> ro.product.model=cezanne

>> ro.build.fingerprint=Redmi/cezanne/cezanne:10/QP1A.190711.020/V12.0.12.0.QJNCNXM:user/release-keys

>> ro.build.version.security_patch=2020-09-01

You have MIUI 12/Android 10, stable Chinese.

In your post you wrote that you had to install GApps. I don't know but that's probably the reason for failing your CTS (even with evaluation type Basic)

Btw, you previously wrote that you already tried with four other fingerprints but no avail.

Maybe you could try once again, taking the fingerprint from (my) Xiaomi Mi 9T, MIUI 12, Android 10, but also by forcing the CTS Basic option, so that you would have altogether (my daily props setup, I never had any problem with):

>> ro.product.model=davinci

>> ro.build.fingerprint=Xiaomi/davinci_eea/davinci:10/QKQ1.190825.002/V12.0.2.0.QFJEUXM:user/release-keys

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

Your device is only for Chinese market and I see only CN firmwares, yours stable and weekly. I don't know could you make it to pass SafetyNet with either of them and how.

There is no XDA forum for your device, to share the ideas and results with other users
[Magisk] Some_Random_Username:
Hello, here are latest fingerprints for OnePlus devices running OxygenOS.

OnePlus 7 GM1901 and GM1905 OnePlus/OnePlus7/OnePlus7:10/QKQ1.190716.003/2009152051:user/release-keys__2020-09-01

OnePlus 7 GM1903 OnePlus/OnePlus7_EEA/OnePlus7:10/QKQ1.190716.003/2009281503:user/release-keys__2020-09-01

OnePlus 7 Pro GM1911 and GM1917 OnePlus/OnePlus7Pro/OnePlus7Pro:10/QKQ1.190716.003/2009281532:user/release-keys__2020-09-01

OnePlus 7 Pro GM1913 OnePlus/OnePlus7Pro_EEA/OnePlus7Pro:10/QKQ1.190716.003/2009281503:user/release-keys__2020-09-01

OnePlus 7 Pro NR GM1920 OnePlus/OnePlus7ProNR_EEA/OnePlus7ProNR:10/QKQ1.190716.003/2009072253:user/release-keys__2020-09-01

OnePlus 7T HD1901 and HD1905 OnePlus/OnePlus7T/OnePlus7T:10/QKQ1.190716.003/2009281618:user/release-keys__2020-09-01

OnePlus 7T HD1903 OnePlus/OnePlus7T_EEA/OnePlus7T:10/QKQ1.190716.003/2009281503:user/release-keys__2020-09-01

OnePlus 7T Pro HD1911 and HD1917 OnePlus/OnePlus7TPro/OnePlus7TPro:10/QKQ1.190716.003/2009281542:user/release-keys__2020-09-01

OnePlus 7T Pro HD1913 OnePlus/OnePlus7TPro_EEA/OnePlus7TPro:10/QKQ1.190716.003/2009281503:user/release-keys__2020-09-01

OnePlus 7T Pro NR HD1925 OnePlus/OnePlus7TProNR/OnePlus7TProNR:10/QKQ1.190716.003/2009150235:user/release-keys__2020-08-01

OnePlus 8 IN2015 OnePlus/OnePlus8/OnePlus8:11/RP1A.201005.001/2009181200:user/release-keys__2020-09-01

OnePlus 8 Pro IN2025 OnePlus/OnePlus8Pro/OnePlus8Pro:11/RP1A.201005.001/2009181200:user/release-keys__2020-09-01

OnePlus Nord Global AC2003 OnePlus/Nord/Nord:10/QKQ1.200412.002/2009260426:user/release-keys__2020-09-01

OnePlus Nord European AC2003 OnePlus/Nord_EEA/Nord:10/QKQ1.200412.002/2009260426:user/release-keys__2020-09-01

OnePlus Nord AC2001 OnePlus/Nord_IND/Nord:10/QKQ1.200412.002/2009260350:user/release-keys__2020-09-01

Additionally here's a new fingerprint for EU variant of OPPO Find X2 Neo (CPH2009): OPPO/CPH2009EEA/OP4C2DL1:10/QKQ1.200216.002/1596223341:user/release-keys__2020-08-05 , here's the full getprop if you're interested https://pastebin.com/5VJHfBKF
[Magisk] Didgeridoohan:
Just finished some testing, and all recenly submitted fingerprints are passing CTS. Yay. Expect an updated fingerprints list within a day or so (probably sooner).
[Magisk] pungat:
Please add => Samsung Galaxy A01 Core Android 10 Go Edition (Region XID) :

samsung/a01corextc/a01core:10/QP1A.190711.020/A013GXXU1ATGE:user/release-keys
[Magisk] Mirardt:
But if I don't install GApps i cant use the phone right? I mean i can only use it with chinese apps. ^^

Should I wipe my device with twrp, reflash Magisk and try CTS a SafetyNET test? Or would it automatically fail since there are no google apps installed?

Maybe something about my Sellers apps is weird, I assumed since its ThradingShenzen they would know what they are doing.

I tried but it kinda didnt work. When i clicked on "Force BASIC key attestation" and then just "yes", it showed me something about a Mi 3, so i deactivated it and picked the Mi9T Global from the list. After that, it gave me a different product.model and no security version at all. Did I do something wrong? I screenshoted it.

Thats so sad. As iphone user for a decade I always regretted the most that i was bound by apples idea of what I can and can't do with my device. If there won't be any solution to this it would be pretty ironic. Also I kinda "ecpected" there to be a "solution to everything", since its Android. Probably a mistake. :D

Is there anything else I can do?

Also thank you so much for spending time on helping me! :angel:
[Magisk] JaboJG:
You typed getprob and not getprop :P
[Magisk] Didgeridoohan:
Thank you, I'll test it out. But, first I also need the security patch date for that print.
[Magisk] Didgeridoohan:
[MENTION=11129403]Mirardt[/MENTION] I've taken a quick look at your logs and haven't seen anything obvious that might be causing you issues.

I did test your device's fingerprint and it passes CTS, so it's certified. Which is funny, since your device doesn't come when GApps preinstalled... Why bother certifying it, if you're not gonna use it? I guess they might be reusing the fingerprint.

I have a faint memory of a similar situation, and I did search around a bit but couldn't find anything. Once I'm not busy like hell I'll try to look closer...
[Magisk] Mirardt:
Oooooooups :D

Now I get the correct date that matches yours. So the only difference is mine shows ro.product.model=Mi 9T, not ro.product.model=davinci

Yeah that sounds weird. So should i test to wipe and make the security test or is it irrelevent? Also might the new Magisk version work?

Thank you so much for doing that! <3