yashsingh1/xdaforums huggingface dataset:
[Magisk] 73sydney:
Sadly there looks like no way to automate Google Play Services and Google Play Store data clear via magisk.....without a reboot...

Its arguably quicker to:

1) Toggle Airplane Mode On

2) Open Settings >Apps>Show System Apps

3) Lcoate Google Play Services & Google Play Store and clear data

4) Toggle Airplane Mode Off

5) Open Play Store and check certification

Im going to put the airplane mode & data clear steps in after the CTS check steps in the pre installation checks, and before installing the module, i think we've seen enough evidence its probably needed regardless of whether CTS/evalType passes (and not as an optional step ONLY if you fail as it currently is), and it cant hurt....

---------- Post added at 12:06 PM ---------- Previous post was at 11:47 AM ----------

Added this new section to my OP:
[Magisk] pndwal:
Not fully understanding this, probably as I don't have a Pixel.

But are you still using Displax's HardwareOff module? If so you may want to revisit this:

https://xdaforums.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703/post83581685

As I mentioned, you have a greater chance of using device specific features, or, at least, manufacturer specific, using configured MagiskHide Props Config to 'force' Basic Attestation. You can use an earlier model chosen by default, or experiment with your own choice... (HardwareOff simply removes model identifiers.) PW
[Magisk] niko26:
Pixel phones offer a better backup function. This can make things a lot easier in case you have to replace/re-install your phone. I wish backup and migration on Android was as simple as on iOS :( That's really one major reason why I would consider switching to iOS.

Correct, I am still using Displax HardwareOff module. Thanks for confirming that the Props Config is a more elegant and flexible solution. The thing is... I have tried setting it to a previous Pixel version, however - it still kept on failing ctsProfile, showing that the evalType was still set to HARDWARE.
[Magisk] pndwal:
Strange. Which model? Default one chosen?

Are you sure you are using it correctly?; removed conflicting HardwareOff first, leaving fingerprint, device simulation (this function disables 'Force Basic') etc alone, just settling option for 'Force Basic', trying default setting/model first? Did you reboot, clear data for play services, etc?

Hadn't heard [MENTION=4667597]Didgeridoohan[/MENTION] had chosen any models on Google's list for Hardware Attestation yet, but you could always try even earlier Pixel model if he messed up, or model was added by Google!

Al least Pixel specific functions are more likely to work if you do this. Fat chance w/ model props set to 'BASIC', not a model at all... (I'm betting you'll even get 'Pixel-type backup' (whatever it is) back using another pixel model; Displax's 'basic' model simply doesn't exist!)

Official reading:

https://github.com/Magisk-Modules-R.../master/README.md#force-basic-key-attestation PW
[Magisk] niko26:
Tried it with Google Pixel 4 XL as a profile for example, also Pixel 3.

Have you read about how Google enforces hw checks? From what I understood is that you can't get around it - unless you switch to BASIC check, but then you don't have a Pixel device. If I understand it correctly you can't have BASIC check and Google Pixel type at the same time.

No, I am not 100% sure that I am using it correctly ;) It's not that easy to find the proper info on the forums. Very often you have conflicting information.

Reboot certainly, clearing data is not necessary for a CTS check inside Magisk,right?

I don't think you have have best of both worlds.

As said, my knowledge is quite limited in this area.
[Magisk] djjohnnyblaze:
Not sure about this. I own a pixel 3a and I have never had to do anything with props. Safety net passes with basic. From what I recall it is not rolled out to all devices. Even pixel.
[Magisk] pndwal:
But what is the default model chosen? - doesn't 4xl use Hardware? How would that work? Not sure re 3.

Edit: Just checked, and seems both these models are set to use Hardware, so that explains why it failed. If you had just used default model, I understand it would have shown Nexus 5. This would help with at least some model specific functions (not sure about pixel backup etc).

:confused: Of course.

HardwareOff and MagiskHide Props Config both get around it by removing prop values that are on Google's server end list, which triggers Hardware Attestation (for now). HardwareOff uses a fake value, MagiskHide Props Config uses older real model from same OEM by default.

Not sure what you mean by 'Google Pixel type'. Hardware Attestation is not exclusive to Pixel... And 'force Basic' is working for other devices too. I'm not familiar with Pixel specific features/apps/functions that may be affected by loss of correct model props however.

I just gave you the official link from the Dev! PLEASE read THAT.

Probably not if configured MagiskHide Props Config 'force Basic' option correctly (but I think you haven't followed instructions). Try clearing Data when clearing caches is not enough.

... Well, that's what MagiskHide Props Config options are DESIGNED to give you, but SOMETIMES can't.

... Then search for / read whatever OFFICIAL docs you can find... You have it here on a plate mate! PW
[Magisk] niko26:
Correct.

My Pixel 4 XL got replaced. My previous Pixel 4 XL's CTS check was done without hardware. Magisks showed it as certified. On this replaced Pixel 4 XL things were a bit more difficult :(

---------- Post added at 02:55 AM ---------- Previous post was at 02:35 AM ----------

You should follow the discussion about some 4XL using hardware based verification. It was said that Google seems to have changed something on their backend which made *some* devices to suddenly not passing the CTS check, because it was switch to h/w based method.

My previous Pixel 4 XL was not using he h/w based method.

Not sure what you mean with "default model chosen".

How?

As said, using props with a Pixel 4 XL profile tripped CTS check, it switched it to h/w based. I can't rule out that I've made a mistake.

Here are the two cases incl. my results:

Switch to BASIC CTS check (for example using Displax's module) - cool, but my Pixel backups are not working. But at least I could install GPay because CTS check passes.

Switch to props using a Pixel 4 XL profile (using the Magisk Props Config) - CTS check fails because it switches to Hardware based verification. Pixel backups work at least. CTS check fails.

So *how* do I get all of these at the same time...?

* the Pixel backups working, (so CTS check is NOT in Basic mode)

* CTS check to pass

Backups is one thing. The other thing is that unlimited photo storage upload at original quality is lost (well... If you came from the original Pixel 1 - so tampering with the model props will remove the ability to upload photos in original quality without counting it against your storage quota).

I am not sure how other features are being enabled/disabled when Feature Drops are offered from Google. From what I recall certain features (wallpapers for example - not interesting for me though) are limited to certain models.

I did already ;)

Why would I need to clear any cache or data if the CTS check already fails from within Magisks Manager? Or are you implying that clearing Data and Caches might give different results within the CTS check in MM?

If the CTS check already fails, I don't see any reason to try to clear caches in other parts of the system. Please feel free to correct my.

That's what I said. *shrug*

Official? What do you mean? You can see in this thread that even the devs here are learning new things. From the outside It is not easy to distinguish between users who give proper advice to users who give false advise. Mind - you're into this topic. It's easier for you to distinguish than it is for me ;)
[Magisk] pndwal:
I follow on John's Twitter, GitHub, Magisk General Discussion thread and related threads here and elsewhere.

Pixel 4 XL model is on Google's list (to use Hardware Attestation) now. Perhaps it wasn't then. (Nothing to do with different 4 XL.) End of story.

Sounding more and more like you haven't tried this option in MagiskHide Props Config / read official link I sent you.

You generally only have to enable it (nothing more), and it chooses a model by default...

I've read about how Google enforces Hardware checks, hardware backed keymaster authorizations, cryptographic key storage, verifiedBootState, SecurityLevel, Trusted Execution Environment (TEE), etc etc.

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

Model props? Then OF COURSE it tripped ctsProfile! If you used pixel 4 XL for model, you changed nothing. The mistake's a given! If it was prop(s) other than model, you shouldn't have touched them, at least till you sorted out Force Basic function.

Others have ctsProfile pass using this on 4 XL, even recently

https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228/post83584063

... including John, for that matter.

Edit: See post below also! :good:

So did you check you get Nexus 5 as spoofed model, as you will if default setting is set properly?...

Been there... Fat chance w/ fake model (HardwareOff), possibility with MagiskHide Props Config's real models (Nexus 5 etc).

Yep, device specific stuff again! You'll just have to try / choose other models / experiment! No chance to change behaviour w/ model listed as 'BASIC' as Pixels apps will just go 'whats that????'...

Again:

Great! (I thought it was clear at least.)

Already said shouldn't normally be necessary, but it has apparently helped some when 'clearing caches is not enough'. Of course, this is to get Playstore certification, G Pay working, not ctsProfile.

On some devices you can though! MagiskHide Props Config 'Force Basic' is designed to give you the best chance. HardwareOff simply isn't/doesn't, unless basic attestation is all you want.

Official as in From the Dev himself, not just user comments (as in link I posted, other GitHub docs etc).

[MENTION=4667597]Didgeridoohan[/MENTION] takes pains to keep his wiki clear and up-to-date, and most have no problem if they follow his (official) steps / method. Users certainly can help, but that's beside the point.

Sorry if I seemed irritated, but my advice has been given in good faith, has been wholly accurate despite your skepticism, and I just want to avoid unnecessary repetition.

To have the best of Pixel w/ SafetyNet Pass, I'm sure you'll need to get to grips with MagiskHide Props Config usage, which is the most advanced solutionto date. AFAIK it's 'Force Basic' option is working on ALL devices, incl Pixel 4 XL!

The principle is the same as in Displax's module in any case, so I'm just saying, for your benefit, you must be doing something wrong if it's not working... And it shouldn't be to hard to figure out what, especially if you try / check suggestions (eg, initial model = Nexus 5).

Sincerely, PW :cowboy:
[Magisk] drup88:
Just wanted to let you guys know I just factory image flashed android 11.

Flashed magisk

Magisk hide applied as per below screenshot.

Installed magisk hide props

Enabled fingerprint of my pixel 4 xl and forced basic attes

Passing safetynet, added cards and successfully been paying for a week now.

Yet to test xposed.

https://ibb.co/jrZ2C46

https://ibb.co/gZnT3jf

https://ibb.co/HtNkPQy

https://ibb.co/p3vkXZg
[Magisk] niko26:
Here is a quote from Didgeridoohan

https://xdaforums.com/showpost.php?p=83243335&postcount=8

So I expected the hardware off module to do the same as MagicProps.

Anyway, I appreciate your comments - really. Don't take things the wrong way if I ask things and question some statements ;)

Currently I have switched of the hardware off module and have no MagicProps whatsoever running. GPay still works. So I'll keep everything as it is right now.

When I have to reinstall everything again (happens about once a year for me ;) ) - I will try to follow your guidelines, and will - if this is okay for you - contact you again. Maybe we can do a "one-to-one session". I will document everything then so people can benefit of your (hard) work and time you spent here supporting them :) Would that be okay for you, [MENTION=7550078]pndwal[/MENTION] ?
[Magisk] pndwal:
Well, that's because the user (who opened that short thread) had already found a working solution for his problem, ie. passing ctsProfile, in HardwareOff module.

[MENTION=4667597]Didgeridoohan[/MENTION] posted to let him know that his solution would also have worked had he selected the correct option, (not changed fingerprint), which is essentially what I'm telling you.

Because, for his purpose, both do essentially the same thing, Didge, ever modest, acknowledged that, and said 'but you're good to go'.

For your purpose, getting device specific features working along with ctsProfile pass, Didge's is necessarily the better option. A large part of the reason he added 'Force Basic' option to MagiskHide Props Config was to spoof real models/devices from the same OEM to achieve this.

So Context is everything here.

... But don't forget the reasons I / [MENTION=9317193]73sydney[/MENTION] gave you not to revert!

Sure, but I don't know why you don't do it now!

You'll avoid losing Playstore certification / many available apps (while Google's 'reprieve' lasts) etc, and you may just get your Pixel - style backups working! (This is likely if Google uses the same backup system for Nexus 5, or other non-HardwareBackedAttestation devices you could select to spoof). But perhaps I'm more curious about these possibilities than you are!

All the best with it. PW
[Magisk] niko26:
For GPay the other module was sufficient enough for me.

Yes, same goes here. For GPay the other, more simple solution was good enough for me.

Yes, that was after I have reverted the changes ;)

Because it works ok for me right now ;)

Since I have reverted the changes, the backups are working as expected. :)
[Magisk] Izy:
is there a solid fix

did sydneys guide which worked for awhile

then it stopped working

so i installed ed exposed and it was working again

then that stopped working

so tried from the start again

not working at all
[Magisk] Didgeridoohan:
[MENTION=2552655]niko26[/MENTION] and [MENTION=7550078]pndwal[/MENTION]

That was long, and I have to admit I only skimmed large parts of that conversation.

This might have been covered already, but regarding getting basic attestation and keeping your device as a Pixel:

From what I've seen, the 2s and the 3a (as seen in this very thread, reported by [MENTION=4950275]djjohnnyblaze[/MENTION]) use basic attestation. Picking one of those should work.
[Magisk] niko26:
Thanks for the suggestion.

Do you know whether it is, expected behavior that when using the Pixel 4 (XL) profile, that it will still trip because it will switch to hardware based check?
[Magisk] Didgeridoohan:
Yes. Since the Pixel 4 and 4 XL use hardware attestation, that will be used if you pick one of those models. And with hardware backed key attestation there is so far (and likely never will be) no way to hide an unlocked bootloader.
[Magisk] pndwal:
Of course it's expected that 4 XL 'profile' will trip ctsProfile (keeping Hardware Attestation on), because that's the 'profile' you already have!... And 4 XL is on Google's list to use Hardware Attestation!... So nothing will change!... Simple!... (Sorry to keep spelling it out, but you're still not seeing the basic principle... Somehow :( )

Of course, he's speaking SPECIFICALLY about 'profile' for 'Force Basic' function (model props), not Fingerprint or something else. :)

What he's saying is that while picking Nexus 5 (default, it seems), Pixel 2(s?) or Pixel 3a will achieve Basic Attestation / ctsProfile pass (as none of these is on Google's list to trigger Hardware based Attestation as yet), using Pixel 2(s?) or Pixel 3a 'profile', should 'work to keep your device as a Pixel' in ADDITION to to 'forcing' Basic Attestation... This would give you a better chance to use 'Pixel style' backup than would the (default) Nexus 5 'profile'.

Really hope that clears things up a bit. :cowboy: PW

---------- Post added at 09:22 PM ---------- Previous post was at 09:15 PM ----------

Thanks mate. But can't find 2s... Just 2? PW
[Magisk] pndwal:
Sorry, new version of what? PW
[Magisk] niko26:
You also said...

"just settling option for 'Force Basic', trying default setting/model first?"

Default setting / model first sounded like... Using the Pixel 4 XL profile. THAT I have tried and told you, it's not going to work.

I needed a confirmation for that using that profile makes no difference (as expected from me).

Pixel 4 has different features than 3. Again, different Pixel models have different features which are only enable per model. That I have already explained you a few times.

I don't have ANY benefit in going back and applying a previous Pixel model profile, which you keep on insisting I should do ??*♂️

What are you referring to here? He didn't mention the word profile in his posting.

As said - I have zero benefit from switching to Pixel 3's "profile".
[Magisk] Didgeridoohan:
Twos. Plural... To lazy to write "Pixel 2 and 2 XL". :p
[Magisk] Mysticblaze347:
I'm sorry, I seen magisk discussion, not the google pay part.
[Magisk] pndwal:
Default model Pixel 4 XL reverts to is Nexus 5, as I keep saying. That's why I've urged you to check your model shows as Nexus 5 a few times, just to check you're doing 'Force Basic' right... And correct! 4 XL is NOT the default model for this setting, nor will it work!

Quite. That's why you'll need to experiment with what you can do with different spoofed 'Basic Attestation' models. I don't have your hardware.

I've simply been trying to help you 'get the best of both worlds', ctsProfile pass and at least some device specific features, by getting Force Basic function working with a real spoofed model in the first place... After which you can try various models, eg those suggested by Didge... Or not...

Come on, no one's insisting, even Didge. It was only ever a suggestion, albeit a good one...

No. You used it. That's why I put it in secondary quote marks...

Well, only if you want ctsProfile pass / Playstore certification along with device specific features that may not work without Pixel model props... Otherwise, no worries!

Sorry to rile you sport... Tried my best to help. :p PW

---------- Post added at 10:36 PM ---------- Previous post was at 10:30 PM ----------

No worries! Enjoy new Magisk!

- In case you still need it, here it is:

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

---------- Post added at 10:42 PM ---------- Previous post was at 10:36 PM ----------

Haha, and I even checked for it! :silly:

Thanks. PW
[Magisk] monkeyhatchet:
I've been having some issues with 3rd party apps trying to access biometric on my p4 since using magisk props config to get gpay working - banking apps and similar that once used face unlock don't have that option anymore. Any ideas?
[Magisk] Didgeridoohan:
The device is probably perceived as a device that doesn't have face unlock, because of the prop changes.
[Magisk] monkeyhatchet:
I figured as much, however the fingerprint I used was of the P4 as well - on Android 10 I could still use 3rd party face unlock. Further, how come GPay can recognize face unlock, but 3rd party can't?

If i were to revert the props, presumably safetynet is tripped again? or is there any other solution?
[Magisk] Didgeridoohan:
Since you're using a Pixel 4 fingerprint on a Pixel 4 I'm guessing you are on a custom ROM, correct? Also, I'm assuming you're using the "Force BASIC key attestation feature" as well, right?

Did you change what device is used for the basic attestation? If not you'll be presenting as a Nexus 5...

Try changing the device used for "Force BASIC key attestation" to a Pixel 4 XL (if you haven't already). Some users have found that it now is possible to use devices that should be using hardware backed key attestation to force the basic attestation, as long as it isn't the same device as the one you have.
[Magisk] monkeyhatchet:
I am not on a custom rom, Stock Android 11

Force basic is active as well as edit device fingerprint. Was the latter unnecessary on stock? In any case your fix switching force basic to 4XL worked! thanks so much
[Magisk] Didgeridoohan:
If you're on stock, changing the device fingerprint is completely superfluous.
[Magisk] pndwal:
This is true for this user (w/ Stock Pixel ROM).

Just to qualify this for others however, selecting a fingerprint is useful for anyone with an UNCERTIFIED Stock ROM (China MIUI, etc).

It's the only way my MiPad 4 on stock could pass ctsProfile for example. PW
[Magisk] dante`afk:
does the current versin of magisk and hide work with gpay to make it work?
[Magisk] warrencoakley:
Canary does with a few modules installed too.
[Magisk] mr-tical:
Did you paid already or in theory?

I updated OS to october update, Magisk to latest canary and when I open GPay, the sign of contactless payment is crossed out.

Also, when I try to add Google Framework Service to MagiskHide, I can't, it deselect automatically itself.

Can you look at my videos and confirm (or not) is this a bugs or no?

I didn't tried to pay yet on this config after update.

https://photos.app.goo.gl/z6WrPJjg4TGyBzuS8
[Magisk] Didgeridoohan:
https://github.com/topjohnwu/Magisk/issues/3306#issuecomment-706473118
[Magisk] warrencoakley:
Just make sure you're on Canary build.

Install:

GPay SQLite Fix,

Magiskhide Props Config,

Seamless Hosts

Clear cache and storage in GPay and re add cards
[Magisk] mr-tical:
Yes, I'm sure, I'm on canary latest.

GPay SQLite Fix, > what for?

Magiskhide Props Config, > installed

Seamless Hosts > what for?

Sorry for questions, but I didn't need that before Oct update.
[Magisk] warrencoakley:
This is what's installed for mine to work. Without them it fails.
[Magisk] mr-tical:
Understand. Do you have the same contacless mark as I in video or do you have normal? Can you show?

I installed everything and still the same mark.

I don't want to reset Google Pay and re-add cards, because I will lost payment history in the app :/
[Magisk] warrencoakley:
Try just clearing the cache
[Magisk] mr-tical:
I tried and not helped :(
[Magisk] warrencoakley:
We'll try installing the other modules i told you
[Magisk] mr-tical:
I did all.
[Magisk] zencooler:
You didn't install most important module: GPay SQLite Fix. This is key to block attestation changed in GMS database.

Try to install them all and then switch to airplane mode (switch off the radio) and then clear data and cache of GMS (Google Play Services) and then switch off Airplane mode and add your cards in GPay. It should work for you [emoji106]
[Magisk] warrencoakley:
You need to install the GPay module as i stated in my previous post to you
[Magisk] mr-tical:
Ok I managed to install GPay SQLite Fix, I was looking for this in Magisk Modules.. :(

Buuuuuut, after thousand reboots, force close apps etc, finaly it ends up with clearing Google Pay storage data as well, finaly added cards again, history in app is lost but I think it's working (cards added, contactless mark is on, normal).

Really really long time I had no such problems like today, I was starting to think about relocking bootloader and get the F* out this stuff, jeeeesus...Android..

The newer Android, the more problems and harder to make simple tasks :)

Thank you for help.
[Magisk] zencooler:
Glad to hear you finally solved the issue.

Yes, the Google Pay and newest GMS are horrible and seems to become more difficult in next versions...

Good luck and regards!
[Magisk] djjohnnyblaze:
So ... I received a google play services update today that required a reboot and guess what? My device is now set to HARDWARE and failing safetynet.

I am using the Google pixel 3a. What is required via magiskhide props config to pass safetynet now?

Thanks in advance!
[Magisk] Abolfazl:
I amI am still on September 1 Google Play Security update and my phone has just notified me that because it is rooted, I cannot use Google Pay. I am running Google Pixel 3 with latest canary of Magisk.