SafetyNet fails on C.20 update for OnePlus 8 Pro

[qriozum]

The "C.20" update for OnePlus 8 Pro based on Android 12 and the OxygenOS 12.1 overlay in correlation with "SafetyNet-Fix v2.2.1" completely blocks the fingerprint scanner. Uninstalling this module from "Magisk" restores the operation of the fingerprint scanner.

In addition, the "CTS Profile Matched" check grid is not passed.

After turning off "Safetynet-Fix v2.2.1" it completely breaks down:

• CTS Profile Matched,
• Basic Integrity,
• Advice: Restore to factory ROM Lock Bootloader. Consequently, contactless payments do not work, GooglePlay has the status of uncertified.

The fingerprint scanner seems to work fine after loading "Safetynet-fix v2.3.0". The only thing that fails is the safety net for "CTS Profile Matched"

[Doggie52]

The fix for the fingerprint issue is well-documented in the issues: https://github.com/kdrag0n/safetynet-fix/issues/179#issuecomment-1117424078

The CTS fail is new with the latest OP update.

[qriozum]

The fix for the fingerprint issue is well-documented in the issues: #179 (comment)

The CTS fail is new with the latest OP update.

179 Doesn't Fix "CTS" problem.

colleague @frnode compiled version v2.3.0 including the changes you wrote about in # 179 but unfortunately it does not work after updating OnePlus build C.20

[frnode]

Hello, I will update my OnePlus 8T in the next few days and try to see what is blocking. If I find, I will update the fork.

[qriozum]

@frnode The fingerprint scanner in C.20 update works fine after applying your build "v2.3.0". The only problem is "CTS Profile Match" which does not pass the test and "GooglePay" does not work.

[Displax]

@frnode The fingerprint scanner in C.20 update works fine after applying your build "v2.3.0". The only problem is "CTS Profile Match" which does not pass the test and "GooglePay" does not work.

Use Magiskhide Props Config

[qriozum]

Use Magiskhide Props Config

I checked "Magiskhide Props Config v6.1.2-v137" - it doesn't work on "CTS Profile Matched".

Unless I'm not doing something properly :(

[Displax]

Use Magiskhide Props Config

I checked "Magiskhide Props Config v6.1.2-v137" - it doesn't work on "CTS Profile Matched".

Unless I'm not doing something properly :(

You need setup it properly. Set to custom valid build.fingerprint

[frnode]

@Displax MagiskHide is not required I think? Because OnePlus' "build.fingerprint" is valid with Google, why change it (I don't fully know the verification system). When I check my "ro.build.fingerprint" it matches the latest version of OnePlus 8T (C20) OnePlus/OnePlus8T_EEA/OnePlus8T:12/RKQ1.211119.001/R.GDPR.202205172258:user/release-keys Maybe I'm wrong, I would like you to explain to me in this case.

Thanks

[qriozum]

@Displax

Musisz go poprawnie skonfigurować. Ustaw na niestandardowy prawidłowy build.fingerprint

My current fingerprint: OnePlus/OnePlus8PRO_EEA/OnePlus8pro: 12/RKQ1.211119.001/Q.GDPR 202205180039: user/release-keys.

Currently, "CTS Profile Matched" does not pass.

From the list of available fingerprint possible to set up for the European version and the "OnePlus 8 Pro" model for Android 10 and 11.

I have never used "Magiskhide" and for now I do not know if the change of Fingerprint will not affect more long -term system updates and whether it will be possible to return to the "factory" entry since it is not on the list available in "Magiskhide".

If you can write a few words of tips - I will be very grateful. Thank you.

best regards

[rori999]

I've tried both the available MagiskHide props fingerprint for Android 10 and 11 but it doesnt work on C20. I do get a valid CTS profile however I lose fingerprint and google pay stays disabled.

[qriozum]

@rori999

I've tried both the available MagiskHide props fingerprint for Android 10 and 11 but it doesnt work on C20. I do get a valid CTS profile however I lose fingerprint and google pay stays disabled.

Do you have a blocked, non-working fingerprint scanner on the smartphone screen even for "Safety-Fix V2.3.0"? For me, after using "Safety -Fix V2.3.0" - the scanner works properly.

[rori999]

@rori999

I've tried both the available MagiskHide props fingerprint for Android 10 and 11 but it doesnt work on C20. I do get a valid CTS profile however I lose fingerprint and google pay stays disabled.

Do you have a blocked, non-working fingerprint scanner on the smartphone screen even for "Safety-Fix V2.3.0"? For me, after using "Safety -Fix V2.3.0" - the scanner works properly.

With just the "Safety -Fix V2.3.0" and no magiskhide props the fingerprint scanner works. But CTS profile fails and no Google Pay. Perhaps there was confusion as the magiskhide props fingerprint is something different than the real fingerprint.

[ruszok]

Maybe someone have valid fingerprint from c11, C15, C16, c17? Then we can use it - this should works.

[frnode]

@rori999

I've tried both the available MagiskHide props fingerprint for Android 10 and 11 but it doesnt work on C20. I do get a valid CTS profile however I lose fingerprint and google pay stays disabled.

Do you have a blocked, non-working fingerprint scanner on the smartphone screen even for "Safety-Fix V2.3.0"? For me, after using "Safety -Fix V2.3.0" - the scanner works properly.

With just the "Safety -Fix V2.3.0" and no magiskhide props the fingerprint scanner works. But CTS profile fails and no Google Pay. Perhaps there was confusion as the magiskhide props fingerprint is something different than the real fingerprint.

Have you tried "Safety-Fix ​​V2.3.0" + MagiskHide with OnePlus 11 fingerprints available? If that works, I'll look into adding fingerprint tampering for OnePlus directly into SafetyNet-Fix.

Thanks for your return.

[rori999]

@rori999

I've tried both the available MagiskHide props fingerprint for Android 10 and 11 but it doesnt work on C20. I do get a valid CTS profile however I lose fingerprint and google pay stays disabled.

Do you have a blocked, non-working fingerprint scanner on the smartphone screen even for "Safety-Fix V2.3.0"? For me, after using "Safety -Fix V2.3.0" - the scanner works properly.

With just the "Safety -Fix V2.3.0" and no magiskhide props the fingerprint scanner works. But CTS profile fails and no Google Pay. Perhaps there was confusion as the magiskhide props fingerprint is something different than the real fingerprint.

Have you tried "Safety-Fix ​​V2.3.0" + MagiskHide with OnePlus 11 fingerprints available? If that works, I'll look into adding fingerprint tampering for OnePlus directly into SafetyNet-Fix.

Thanks for your return.

No as soon as I select a fingeprint from the list and reboot i use the fingerprint login. CTS profile will work but not google pay. I tried with Oneplus 8 Pro 10 and 11 fingerprints and also a couple of others but always same result: You lose fingerprint feature of the phone, CTS profile works fine and no google pay. Once I reset the fingerprint in Magisk hide. The fingerprint login works again but the CTS profile fails and Google Pay doesnt work.

[Doggie52]

I can confirm @rori999's findings - with MagiskHide Props Config set to the latest OnePlus 8T Europe fingerprint, I pass CTS but cannot use fingerprint scanner nor Google Pay.

[ruszok]

I can confirm @rori999's findings - with MagiskHide Props Config set to the latest OnePlus 8T Europe fingerprint, I pass CTS but cannot use fingerprint scanner nor Google Pay.

You can use ColorOS Magisk Module and than - magic - CTS pass, safety net pass, fingerprint reader works.

[Doggie52]

Sure but Google Pay doesn't work, so CTS passing is useless.

[ruszok]

Works fine. Maybe you must clear all data in Google play app

[qriozum]

Colleague @Doggie52 wrote about Google Pay (payments) and not Google Play (Market with applications).

On the other hand, if the GPLAY is identified as certified, the TS profile undergoes the test, payments should also theoretically go. But there is no certainty. The error made by OnePlus in software numbering may: "C.21" and in Dugim is "C.20".

Problems with fingerprint scanner and GP certification and CTS profile have people with telephones rooted as well as totally without modification. This only shows a problem committed by developers from OnePlus (OPPO).

BTW - @ruszok jesteś Polakiem? ;)

[ruszok]

CTS in Google pay: BTW @qriozum - taaa 🙃

[rori999]

Google play says certified but not Google Pay

[qriozum]

@ruszok dzięki, coś tam ruszyło, ale nie mam pewności czy w całości ;)

Theoretically and hypothetically, after using the colleague's description @ruszok safetynet, the CTS test passes, the fingerprint scanner works, adding cards (being on the history list) in GooglePay went well. I haven't been to any store yet to make the payment and I'm worried about the lack of a "colored" icon above the card and the message "not configured". None of the three tabs, despite being selected as the default, does not highlight the icon on the colored "G" and this message "not configured" does not disappear :(

I will see tomorrow during some payment, maybe then, after the transaction, the status of the card will change.

[rori999]

I went grocerie shopping today and the payment was refused. As I'm basically cashless (didn't bring my wallet) I was fortunate my Garmin watch worked well. So my experience is payment will not work.

[qriozum]

I went grocerie shopping today and the payment was refused. As I'm basically cashless (didn't bring my wallet) I was fortunate my Garmin watch worked well. So my experience is payment will not work.

@rori999 Does your CTS pass? GooglePlay certified? Were you able to add your cards on GooglePay?

[rori999]

Google play is certified. I've removed and re added a card but it says "not setup"

[qriozum]

You "not setup" is displayed as I do, after successfully adding a card to your wallet under the icon indicating a close -up (which is crossed out):

Now I have no way to check if the payment would pass with me because the next active store is still closed. For now, I'm getting down to Downgrade to A11 and intend to make flash "evox 6.4"

[qriozum]

Google play is certified. I've removed and re added a card but it says "not setup"

Checked, the method served by @ruszok works. The message in the GPAY on the card with the content "unspecified" which can be seen on my screenshot was only for the first payment. Flance has passed and a few more, also now, the inscription "bring to the reader" is now displayed ;)

regards q.

[firozpatel123]

I've tried the method, now I'm passing safety net but fingerprint don't work, have I done anything wrong, OnePlus 8 pro a12

[ruszok]

Please give log from Magisk where can see modules start order. It is important to install modules in the right order.