yashsingh1/xdaforums huggingface dataset:
[Magisk] djjohnnyblaze:
For anyone who has the same issue I did, you can use magisk hide props config and select pixel 4a. Worked for me.
[Magisk] warrencoakley:
The update has arrived for me but i haven't installed it yet.

I have magisk hide props config installed but how do select Pixel 4a?
[Magisk] warrencoakley:
Where do i go from here?
[Magisk] djjohnnyblaze:
You only need to do this if you update to the latest google play services update and Magisk shows HARDWARE when testing safetynet.

1. Install magisk hide props module and reboot

2. open terminal emulator on device

3. su command

4. props command

5. Follow below menus:

2 (Force BASIC key attestation)

f (Pick from device list)

7 (Google, choose this if you own a Pixel device, choose different manufacturer that matches your device if different)

Then just choose a model closest but not the same as the model you are currently running. Reboot the device and check in Magisk if SafetyNet shows BASIC now. If it does then the props changes worked.

If it still shows HARDWARE then:

1 open terminal emulator on device

2. su command

3. props command

4. Choose 'r' to reset all options/settings

5. Reboot Device

Then follow the above steps again to try and force BASIC attestation again

Cheers!
[Magisk] warrencoakley:
Yep worked. I'm on a Pixel 2 XL and changed it to 4a and all is good. Even have the new assistant 2.0 aswell. Just need to get call screening working
[Magisk] Klownicle:
I lost verification myself as well just today and I've been pushed to Hardware. I didn't update any apps knowingly tho.

I've ensured I am running the latest magisk as I just downloaded and updated both manager and the canary build. Made no difference unfortunately. I know I was on Basic before so I'm not sure why it suddenly changed. Do the google play services update without your permission even if you've set updates to not be automatic in Google play?

Edit: Followed the instructions and that appears to have worked for me, back to being a basic ***** :D
[Magisk] warrencoakley:
Yep you can't ignore it once it comes it will reboot your phone in time
[Magisk] Klownicle:
So with the Pixel 4a change, is this to say it will eventually happen with that?
[Magisk] warrencoakley:
I'm not sure all of this is not forever but at the moment this method works
[Magisk] 73sydney:
I have to ask, why are you spoofing a 4a when you have a Pixel 2 XL (like me)?

Im starting to think its abotu the other thigns mentioned in your post.

As for call screening, i view that as amythical thing. I tried all the so called "methods"

Theres always just 2 guys claiming they work lol

Update: nevermind, i just saw your posts in the MagiskHide Props config thread :)
[Magisk] pndwal:
[MENTION=4950275]djjohnnyblaze[/MENTION] has Pixel 3a, so reasonably chose Pixel 4a.

I would have thought that choosing 4XL etc if using 2XL would likewise make sense.

The whole point of choosing a real model is to give Manufacturer / device specific functions / features / apps the best chance to work by spoofing a device also on an OEM's list for enabling these, and we simply can't use the actual model because the mechanism exploited to force Basic Attestation is the triggering of a fallback to Basic caused by a prop mismatch (at present).

Therefore, choosing the closest cousin will generally usually be best for device specific functionality.

Of course, simply changing model prop(s) to "nonsense prop", or anything else, will suffice to 'force' Basic, as mismatched props is all that is really needed. PW
[Magisk] warrencoakley:
I tried the 4XL and SafetyNet was still tripping and i was experiencing some overheating. Again as you stated it doesnt really matter what you pick once it's forces basic. It runs smoothly with no lags or issues
[Magisk] pndwal:
Ah! That makes more sense... But how was SafetyNet tripping? (ctsProfile, basicIntegrity, and/or evalType Hardware?)... And tried 3XL? PW
[Magisk] warrencoakley:
I've no idea it was just coming back as failed. When i changed it to the 4a it was successful again and i got the new assistant 2.0 which for some reason i don't get with the 4XL props
[Magisk] Nik0LaAs:
Had the same issue after a google play update yesterday on my Pixel 3.

I followed the instructions and modified the props with Pixel 3 XL.

It worked, but I wonder, what are the effects to do this ? Do I have to expect other issues for changing the phone model ?
[Magisk] Didgeridoohan:
Very good thinking, and a spot-on question.

Yes, it is very possible that one might experience issues from changing the model. In your case though I think it might be less of an issue, since the two devices are so similar.
[Magisk] RealCaracas:
Hello! I'm on BASICS now also following the steps :) ... I have a Pixel 2 XL and choose a Pixel 2 which is the most exact model :P

But I think I have still a problem with Google Pay... All cards shows that is "Not configured"

I have not tested yet, but this is not normal right? All is configured correctly in Google Pay and NFC is active...

[IMG="Screenshot"]https://i.ibb.co/DpTg1HZ/pay.png[/IMG]
[Magisk] Didgeridoohan:
I am quite useless when it comes to troubleshooting GPay. It's not available here, never used it, probably wouldn't even if I could... :laugh:

There's are a couple of useful links in the 1st post of this thread. Take a look if that module can help you out.
[Magisk] RealCaracas:
OK thanks....

Any other on BASICS GPay works ok??
[Magisk] RealCaracas:
Ok... Next step was to delete data from Google Pay and Google Play Services.. All good now... :)

I also did change to 4a and have new assistant :P
[Magisk] sigitm:
Hi guys,

I have OnePlus Nord with rooted stock rom, latest Magisk, latest EdXposed canary yahfa.

Sadly still cannot make GPay to work.

MagiskHide is active and GPay, GPS, GSF are all selected.

Also installed "MagiskHide Props Config" and "GPay SQLite Fix" Magisk modules.

SafetyNet test passes (evalType: basic).

If I delete GPS data, I can use GPay again (but I have to reconfigure all my credit cards for contactless).

However, after about 1 day, GPay says "Your phone is no longer ready for contactless payments" and disables contactless payments.

What can I do?
[Magisk] sliding_billy:
4a fingerprint is working flawlessly (AKA no side effects) and passing SafetyNet while getting rid of the contactless GPay issue on both a Pixel 3 running stock rooted and a Pixel 3XL running DU.
[Magisk] warrencoakley:
Just wondering are you still on the 4a fingerprint and getting the new assistant 2.0? i was up until yesterday which seems it has reverted back to the standard one.
[Magisk] djjohnnyblaze:
Not sure how to tell if I have assistant 2.0 but don't believe anything has changed for me.
[Magisk] warrencoakley:
Mine has now. Assistant 2.0

Did you manage to get call screening working?
[Magisk] djjohnnyblaze:
Yea call screening was working for me even before the changes.
[Magisk] warrencoakley:
Oh really? Hmmm! Not sure why it is not working for me. I've tried everything.
[Magisk] OGIGA:
Strange, I had Google Pay working for a while and last night, it stopped working. I didn't change anything. basicIntegrity fails, ctsProfile fails, evalType BASIC. Don't know what gives.
[Magisk] warrencoakley:
There was an automatic update pushed by Google services. If it states hardware instead of basic it has installed. You'll need to change your Magisk props to Google 4a, clear GMS cache and it will pass again.
[Magisk] damador:
mi note 10 , latest magic , lates eu rom basic integrity passed cts passed Eval Type basic - cant get Gplay working
[Magisk] biyor:
Same here, didn't change nothing

Enviado desde mi BASIC mediante Tapatalk
[Magisk] pndwal:
So have you installed SQlite GPay fix module and binaries? Or used manual SQlite method? You'll need one of these. I prefer module solution.

If not, suggest you read whole post 'Magisk module for it here' linked in OP, and other info there. PW
[Magisk] useformildaccess:
Both hooking mechanisms (SandHook and YAHFA) of EdXposed are tripping both basic integrity and CTS profile of SafetyNet with basic attestation on my device as well. It is also failing device certification in play store? I have cleared both the cache and data in airplane mode for Google Pay, Play Store, and Play Services as well as made sure that they are still checked in Magisk Hide and EdXposed Blacklist – but nothing. Any solutions, ideas, or suggestions to point me in any direction I am missing?

Device: OnePlus 7T

Build: Oxygen OS 10.0.14.HD65AA

Security Update: September 1, 2020

Google Play System Update: September 1, 2020

Magisk Canary: ver. 4e0a3f5e

EdXposed Canary: ver. 0.5.0.6-android_r (4564)​
[Magisk] zencooler:
Remove EdExposed, install Magisk Props Config and change the attestation to basic choosing any other One Plus phone (e. g. One Plus 8). Restart phone and voilà. Should work for you [emoji106]
[Magisk] useformildaccess:
Even though Magisk already reports evalType Basic, force basic attestation? Is that gonna resolve basic integrity fail?
[Magisk] zencooler:
You have to check it. Follow [MENTION=9317193]73sydney[/MENTION] guide and you will see if it helps. But remember to remove EdExposed before this changes.

If it will not solve your issue the only way is to start from the very beginning - I mean flash clean rom and then set up all again.
[Magisk] useformildaccess:
I do pass SafetyNet with EdXposed module disabled in Magisk. Had it been hardware based attestation tripping SafetyNet, then it would have been tripped just because the bootloader is unlocked even with EdXposed disabled. I don't know if it is that EdXposed is being detected by the latest Google Play system update. It would help if anybody with a tripped basic integrity check and report their recent Google Play system update under their device security settings.
[Magisk] pndwal:
You are correct. If Magisk Manager reports Basic evalType, there is no need to force Basic.

The Basics (for everyone):

basicIntegrity (not to be confused at all w/ Basic Attestation) is usually tripped by rogue Magisk Modules (using noncompliant bind mechanism etc) and/or EDXposed / Xposed:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post82166469

Check link to EDXposed thread from this post for current state of play re. passing SafetyNet.

If basicIntegrity is failing, resolve this FIRST by eliminating the above, ie. removing / disabling, rebooting, then clearing Google Play Services cache (and possibly data in Google Play Services, Google Play Store, and Google Services Framework) before checking SafetyNet. Don't try to fix ctsProfile first, as tripped basicIntegrity will ALWAYS trip ctsProfile in turn. Nb. ctsProfile pass with basicIntegrity fail in Magisk Manager is a FAKE (on device but not on Google server end) pass, and only occurs if a fake-SafetyNet-pass-generating Xposed module is active.

ctsProfile can only be fixed by MagiskHide Props Config if basicIntegrity already passes. If ctsProfile is failing and evalType is Hardware, you need to use Force Basic Attestation function to select a model prop value that DIFFERS, even slightly, from the actual model to cause the mismatch that triggers fallback to Basic. (Nb. A real model is not needed either, just a different value; 'Cheeseburger' will work to Force Basic Attestation as it doesn't match actual model prop value.)

However, selecting a real device model as close as possible to yours will spoof that device, so this is usually best to keep device-specific functionally (OEM app stores, exclusive apps, backup features, etc etc) working. Newer models from same OEM are often the best choice. Nb. default setting usually uses older models.

If ctsProfile is failing and evalType is Basic, changing Fingerprint prop will be needed for some custom ROMs, and uncertified stock (Chinese, etc) ROMs. (For stock certified ROM, fingerprint change is unnecessary.)

Any certified fingerprint (even for different device /model / manufacturer) can be used, and will usually work, especially if originally for the same Android version, but using a different device fingerprint may affect device-specific functionality also, so selecting a fingerprint for the same / similar device, or at least from the same manufacturer, is preferable. PW
[Magisk] useformildaccess:
Thanks [MENTION=7550078]pndwal[/MENTION]. Turns out EdXposed 4564 is tripping SafetyNet. 4563 YAHFA is said to not in threads below.

https://xdaforums.com/xposed/development/official-edxposed-successor-xposed-t4070199/page40

https://xdaforums.com/pixel-4-xl/how-to/xposed-discussion-thread-t3992607/page37
[Magisk] useformildaccess:
I have a long-winded question for you, [MENTION=7550078]pndwal[/MENTION] and [MENTION=9317193]73sydney[/MENTION]. With EdXposed enabled, SafetyNet gets tripped at spontaneous first attempts but passes at follow-up subsequent attempts. It is suggested that disabling battery optimization for both Magisk and EdXposed managers would resolve the issue but it has persisted. At Google Play Services update and other silent hot updates, usually during charge cycles, Google Play Store checks for SafetyNet and minutes to hours later, due to the intermittent SafetyNet fails mentioned above, it renders apps like Netflix incompatible although the device remains certified. And few time instances later, Google Pay fails security requirements. Gpay SQLite Fix Magisk module successfully addresses this issue and keeps Google Pay operational but apps like Netflix are still listed incompatible. A cumbersome workaround I have found was to constantly check for SafetyNet while the phone is on the charger so to make sure the device is still passing SafetyNet. So, my question is, is there a Gpay SQLite Fix Magisk module equivalent that resolves the issue with Google Play Store? Thanks in advance.
[Magisk] 73sydney:
I hope im reading your question rigth when i answer below :)

I have a simple question/solution for you: restart your device more often - to avoid the updates being an issue.

<sermon on>

Like my best friend, who used to have to, due to no internet acccess at his lcoation, use the hotspot on his phone...comes for coffee one day and says "my internet isnt working on my PC, i have the hotspot turned on but nothing".

Slight digression, but topical in my life, especially last week, we IT people get bad press for suggesting to people to "try turning it off, and back on", but theres merit in it

Me: "Whens the last time you restarted the device?"

Him: "You have to restart a phone?"

Me: "Yes, theyre a computer, same logic applies, they need restarting occasionally to free up resources and just good maintenance"

Him: "Ive never restarted it since i bought it" (6 months)

He goes home and restarts it, and i get a txt "Youre right, all fixed"

Just last week, i had two MacBook Air's brought to me by another friend because "both suddenly stopped working"

I put the first one on my desk and press the power button...boots to login...

Me: "Okay, wheres the problem"

Him: "It wouldnt do this before"

Put the second one on the desk and press the power button...boots to login...

Me: "Okay, wheres the problem with this one"

Him: "It wouldnt do this before"

It had obviously updated, and he'd avoided resarting because "i needed to be online", and evenutally they'd crashed.

He then shut then down to bring to me

If only he'd simply rebooted them, i'd never have had to lose 10 minutes of my life looking at them....witht he shutdown, he got halfway there....

Reboots/Restarts - theyre real things people

Too many people in this modern "always connected" world are getitng lazy and forgetting to do the most basic things. A Reboot/restart is regular maintenance. Im online a lot, but when im not, my PC gets powered Off <---- people should try this more often, if not, they can at least restart their devices regularly

<sermon over>

To answer more fully have no idea how to programmitically, from a command line check for safetynet pass, therwise i would have used such a thing to made my module check for safetynet pass during installation, maybe someone does know how to do this, but not me. In any event that would then require polling, which i also do not know how to do via command line. Im sure the above is possible to do via an app, as we have that check in magisk, but im not an app developer, wouldnt have the first clue on howe to write an android app. and not looking to learn due to being already time poor. Sorry.

My module, as per the OP of the thread it comes from, only changes permissions on a database file, then edits it using SQL to set attestation values, and sets permission on it again, and hides relevant packages using MagiskHide. It does nothing to Google Play Services other than that.
[Magisk] f8192:
Hello! Is GPay working with root now? Mine started working for no reason, I just installed it today for a first time in a few months. Here are some screenshots https://imgur.com/a/YOhxiMx
[Magisk] pndwal:
Well, this seems to be a EdXposed issue, and I don't use this / only installed briefly to test how to restore SafetyNet after removal. I never had your intermittent SafetyNet fail, but I understand that there is much difficulty passing SafetyNet w/ EdXposed, and that mileage varies a lot with the various recent Canary builds. Was it any better with 4563 YAHFA?

It's also not clear whats occuring with SafetyNet. When you say 'tripped', is it basicIntegrity? Or ctsProfile?

Nb. After fail, Playstore often looses 'certified' status some time later. This is restored by fixing SafetyNet and clearing G Play services cache. Try clearing data for G Playstore, G Play services, G Services framework too. May need to clear cache / data for G Pay, Netflix etc also if these still fail. PW
[Magisk] useformildaccess:
Thanks [MENTION=9317193]73sydney[/MENTION] and [MENTION=7550078]pndwal[/MENTION].

SafetyNet fails with 4561 and 4564 but does pass with 4563 YAHFA but the same intermittent SafetryNet fail persists with a cascade effect of Netflix and other select few apps loosing compatibility for installation and updates in Google Play Store then Google Play losing contactless payment capability because device not meeting security requirements where the latter can be circumvented with [MENTION=9317193]73sydney[/MENTION] effective Magisk module.

The intermittent fail is for both basicIntegrity and ctsProfile.

Clearing Google Play Store data alone resolves all previously listed incompatible apps and they become available for installation and update again. The problem with that though, is that all apps that were disabled from auto-update in Google Play Store will become updated and need to be disabled from auto-update again. Even if you disable them from auto-update immediately after clearing the data of Google Play Store, they still become updated once after restart even though they still remain disabled from auto-update.
[Magisk] pndwal:
So that confirms it's an EdXposed problem. This is causing intermittent basicIntegrity fail I've not otherwise experienced, and ctsProfile failing is a direct result of this, as always occurs.

So it's only the basicIntegrity trips that need a solution... PW
[Magisk] patrickneil:
Question, does anyone know of a good way to test if Google Pay will work when I go to tap? I can get SafetyNet to pass both checks, but Google Pay still fails, maybe a third of the time. Other than getting my own pay terminal, how can I test if it'll work?
[Magisk] pndwal:
[MENTION=10852223]useformildaccess[/MENTION] & others -

FWIW, it seems v0.4.6.4 (4563) EdXposed is now Stable build as of yesterday.

I just installed latest Magisk Canary 21006 / 313, then Ritu Core / Ritu EdXposed 4563 YAHFA (both from Magisk repo) on Mi Pad 4 for kicks... Well, just to test w/ SafetyNet.

Happily, I can report that this is passing 'out-of-the-box', and without even enabling App List mode / Pass SafetyNet! :good:

It also seems stable, with no intermittent basicIntegrity trips as yet. :)

https://xdaforums.com/xposed/development/official-edxposed-successor-xposed-t4070199/post83883807 PW
[Magisk] salva52:
Don't install 2.119 version, doens't works on my oneplus 7 pro rooted. I downgraded to 2.118, it's ok, no security fail now. I have lost safetynet pass same time, I don't know if it's a coincidence.
[Magisk] glennza:
I have a slightly different issue with my Sony Z5.

I was running stock 7.1.1 with Magisk root and all worked perfectly. I upgraded to LineageOS 17.1 and now it doesn't work!

I have installed the latest Magisk (21.1) and MagiskHideProps, I can pass safetynet and I get the all clear from GPay (see pics).

I can add cards, get clearance from the bank and everything looks perfect...

...but it doesn't work!

If I try to use it, nothing happens. Nothing at all!

I thought it must be an issue with NFC so I downloaded an NFC utility and it will scan and display the card data. I dont know what would cause this, any ideas?
[Magisk] beatschubser:
Man, Google Pay makes life so much easier, this thread proves it.
[Magisk] elreydenj:
Edit: I was able to add one card and now the second says I am rooted...

Try the newest beta. 16.0.86. Gpay now working again for me without any workarounds.
[Magisk] joker2mbr:
This Beta version worked for me too! Thanks for the tip. :)
[Magisk] Bluffer94:
Thanks for the hint.

Which version of Magisk do you use?
[Magisk] jasonbiggs:
nm
[Magisk] joker2mbr:
[deleted]
[Magisk] elhana:
Works for me too.
[Magisk] jasonbiggs:
Added my Mastercard, but visa could not!
[Magisk] xxxvego:
On 16.0.86 can add card but can`t configure to pay contactless.

I have ctsProfile: false, MagiskHide Props Config don`t work. How can I fix that?
[Magisk] Didgeridoohan:
If you explain what "don't work" mean, someone might be able to help with a fix...
[Magisk] xxxvego:
I flashed MagiskHide Props Config but still have ctsProfile false.
[Magisk] Didgeridoohan:
Sounds like you didn't read the manual... You also have to run the props script and pick a certified fingerprint. Then it'll work.
[Magisk] ndg99:
Working for me too on Google Pixel 3 XL with Mar 2019 update and Magisk 18.1.
[Magisk] bakemcbride21:
Verizon Pixel 2 running Magisk 18.1 (stable build), Magisk Manager 7.0 and Play Services 15.0.90 (United States - NJ)

Stopped working for me in stores and for paying bills in my financial apps in early March....I disabled the device admin for Google Pay and cleared cache and data on both Google Pay and Play Services and I also uninstalled updates from Play services which brought it back to version 12.xxx.xxx. (whatever came with the phone when purchased.)

Reboot....

Placed Google Pay on Magisk Hide

Updated Play services to 15.0.90

Re-enabled device admin on GPay

Entered GPay and set everything back up.

I was then able to add value to my Dunkin Donuts Card in the app via GPay and also pay in stores again.

Not sure if this will help anyone (it seems some people need to take greater steps) but my GPay is now working again everywhere! (be interesting to see what happens on the next Play Services update).
[Magisk] Nekromantik:
if you install beta will it still auto update to next beta?

---------- Post added at 07:19 PM ---------- Previous post was at 07:09 PM ----------

16.0.86 not working for me

cant add card
[Magisk] jcmm11:
No, it won't auto update until a stable with a larger version number comes out.
[Magisk] Nekromantik:
looks like I gotta downgrade again

new beta not working
[Magisk] xxxvego:
There is no certificated fingerprint for my device. I have Huawei P9 (L09) but ROM in for AL10 ( https://xdaforums.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849 ).

I can not use this module and I do not want to spoil anything, could you explain to me what I can do to make ctsProfile true?
[Magisk] Didgeridoohan:
To pass CTS, your device has to present a certified fingerprint to Google's servers. If there is no fingerprint available for you device in the list, you can pick whichever one you want that is certified. Or, if you don't want to do that, you're going to have to find a fingerprint that matches your device.

I suggest that you really do take a look in the module documentation, because everything I've just written is already explained there...
[Magisk] Pro4TLZZ:
have followed instructions and was able to re add contactless. will check if it auto updates