yashsingh1/xdaforums huggingface dataset:
[Magisk] Drahy:
As I already said. Changing the module properties triggers "updating xxx from xxx apps" process during startup - this did not happen and sometimes does not happen. I am not sure how to trigger this event but by this I know the changes were applied and I pass safety check - this process is usually triggered by system update or firmware update but should be triggered by also this props changing. Otherwise I do not pass it and changes are really not applied.
[Magisk] sielhadi:
I'm sorry do you mean that you pass the safetynet
[Magisk] Didgeridoohan:
That unfortunately doesn't tell me much of anything... "Updating app" thingy is expected when you change the fingerprint, but not on subsequent boots. Until you current the prop again, that is.

The only way to know for sure if the props set or not is to check the value, so if you're still interested in digging into this there's something you can do. Next time that it seems like the props haven't changed, run the getprop command in a terminal emulator to see what the value is. Example with the fingerprint:

getprop ro.build.fingerprint

And then you can do that for any other props you've set as well
[Magisk] Didgeridoohan:
Yup. I pass on all my ancient devices... We'll see if it lasts.
[Magisk] sielhadi:
What about the new devices. If yes could you please tell me how did you do that
[Magisk] Drahy:
All i know is that when this process does not start during reboot when changing any props (and reboot) these props are not really applied. Not sure how to trigger it manually. Maybe delete Dalvic cache but I am not sure how to delete it on official Samsung ROM... Sometimes it says updating, sometimes it says optimizing... not sure if there is difference...
[Magisk] Didgeridoohan:
I only have ancient devices (at least that I've rooted). The newest one is a OnePlus 3T... Changing the device fingerprint is all I need to do.
[Magisk] Didgeridoohan:
If you ever manage to catch the getprop value for one of those times I'll be very interested to know the result. And also the module logs from the same instance.
[Magisk] Drahy:
The result shows the fingerprint is applied but it really is not... what is not to understnad here? I even sent you logs from before already when it happened. You said from logs it seems ok but it was not. When the "optimizing apps" process was triggered then it was applied and I finally passed the Safety net.

The same is happening now. I updated Magisk to 21 and during start it "optimized the apps" and I lost safety net but all props "seem" ok in the logs. I applied them again in the terminal now I need to trigger the optimization process again...
[Magisk] Didgeridoohan:
Ok... I'm just trying to figure out what's going on when you say that the props aren't applied. Like you say, so far I haven't seen anything wrong with the props you've set.

I guess we're not gonna get any further with troubleshooting this at the moment. If you figure anything more out, give me a holler. (y)
[Magisk] Akerhage:
Is three any way to get Google Pay to work again today? Using Xiaomi mi note 10. I have bootloader unlocked but not rooted. Got the same error yesterday. I only have my card virtually and need to pay for new passport today.

Can I reset my phone, install a "real, valid, standard, original" ROM and have my phone valid for Google Pay. I have a few hours today so I can manage to re install all apps and connect my cards again etc.

Just need a phone where Google Pay is working 100%. But maybe I cannot go back to that phone state when already been tampering with bootloader etc?
[Magisk] Didgeridoohan:
Restoring your device to fully stock (important!) and then relocking the bootloader should solve things for you.
[Magisk] pippo45454:
Hi,

1 months ago I activate cts false changing props setting with terminal to.product.model to unknown value.

Yesterday I update Magisk, manager and your 112 version and now I can't bypass anymore cts profile in any way with my redmy 9 pro... It's strange...

Do you have any suggestions?this methods work every time but now not anymore..
[Magisk] Didgeridoohan:
See the reply I just made to your PM to me...
[Magisk] zgfg:
See all the posts here (and in Magisk thread), failing now for everybody.

Newer phones, unlocked bootloader - even with Basic, CTS now fails.

That's it (for now)
[Magisk] Akerhage:
How to do this? Just flash a original ROM? Is there any guide, or maybe if you could send med a PM on some instructions? Thanks!
[Magisk] Didgeridoohan:
That's what you need, yes. This is the kind of info you'll usually find in your device's forum though. A bit off-topic here...
[Magisk] Akerhage:
I did find the file but to many people have downloaded it already, so I cannot download the file from google drive..seems to be the only mirror to downliad from. I will try with the Mi Note 10-forum. Thanks for helping out.
[Magisk] :
Same here on my Mi A2 Jasmine_Sprout. I'm on Evolution X 5.3 (A11) and don't even have Magisk installed. Until 2 days ago everything was fine. Now cts profile fails though I'm not even rooted.

😢
[Magisk] Didgeridoohan:
In other words, the unlocked bootloader (possibly even custom ROM) is a prime suspect rather than Magisk.
[Magisk] kazemitsui:
Hi There, I have a Pixel 4a5g on the December patch, rooted, and cannot pass SafetyNet anymore.

Previously, I was using the Force BASIC Key -> Pixel 3A and I was able to Pass SafetyNet, then I randomly was like ok lets change it to a Pixel XL. I also passed SafetyNet. I honestly thought this would allow me to have unlimited storage on google photos, it did not work...

Today I decided to switch my Basic Key back to a Pixel 3A, and I no longer pass SafetyNet, specifically the ctsProfile.

I tried to reset everything using a terminal emulator with "su -c props" and selecting the "r" choice. Then setting it back to a pixel 3a in the Force Basic Key, but I still fail ctsProfile check.

I literally did not do anything else to this. Anyone know how to resolve this?

When I originally rooted my phone and passed safetyNet, I followed this guide

How to unlock the bootloader and root the Google Pixel 4a

Looking to root your brand new Google Pixel 4a? Here's how to unlock the bootloader and root the latest mid-ranger Pixel smartphone!

www.xda-developers.com

(Optional) Step 4 – Passing SafetyNet on your Google Pixel 4a

And did that and it worked, now it doesn't work at all...
[Magisk] Didgeridoohan:
@kazemitsui If you look through this thread and also the main Magisk thread you'll see that quite a lot of people are failing CTS since yesterday. Google might be tinkering with things again...
[Magisk] kazemitsui:
Thanks, I did go back to the Pixel 4a5g thread on rooting right after I posted, and saw that people were failing CTS. I guess it was all a coincidence that I decided to switch my device key on the same day...

Hopefully it is resolved soon!
[Magisk] zagi988:
Yup, Xperia XZ1 with unofficial LOS 17.1 failing CTS since this morning... Even tho it was working perfectly for almost a year with fingerprint set to official XZ1. Something for sure is happening.
[Magisk] heihachi34:
Just to let you'll know. I was on latest magisk v21.2 and manager 8.0.5. was working well. All of a sudden yesterday I had CTSprofile "attestation failed".

I tried all the methods possible.

Tried different fingerprints.

Tried matching security_patch dates.

Tried rebooting.

Reinstalling Rom. (Which was safetynet pass before).

Tried device emulation options.

Tried changing boot (post fs and late service).

Manually changed and matched fingerprint and sec_patch dates.

No luck at all.

Only way is to go back full stock. And I hate it.

Waiting to let this get solved asap.

Thanks for all your guidance.View attachment 5185821
[Magisk] mx597turbo:
Is this affecting Android 10 as well, or just A11?
[Magisk] zagi988:
I'm on 10, LOS 17.1 so it's affecting 10 too.
[Magisk] heihachi34:
I am at Q (Android 10) it's affecting me sleeplessly.
[Magisk] Hawkeye77:
Me too.

My Pixel 2 was working great until the latest Magisk Manager Update.

Patiently waiting for fix...........
[Magisk] Didgeridoohan:
Here's the daily reminder that it's not at all necessary (and even encouraged not to) post along the lines of "here too, please fix" (or any variants thereof). And this applies to the main Magisk thread as well, not only here (but this is my thread, and I like it without clutter)...

CTS is failing for many users, we know.

There's currently no fix or workaround (heck, no-one even knows why yet).

Please only post if you've got new info.
[Magisk] zgfg:
It's not about Magisk (not Manager) update, but due to the Google change - please read the whole communication here

It affected yesterday us who are on Beta or Canary and did not have any Magisk update last week.

It was just a coincidence for Magisk Stable users who yesterday finally updated to Magisk 21.2 and independently got affected by Google CTS attestation changes (part of attesting is in GMS on the phone, part is on the server - hence Google does not need to update your phone if they change policies)

It affected also e.g. users of Xiaomi.eu A11, where with unlocked Bootloader but without Magisk (and without any props faking), they had SafetyNet ok - but since yesterday CTS is also failing for them (and although showing Basic eval type)

So, no bug in Magisk update and not expecting any 'fix' (unless the new trick to fake Google will be discovered).

Or if Google is again still experimenting and if they soon pull off
[Magisk] angiotell:
I've a Samsung Galaxu S10+. Any way to return to stock rom? Please
[Magisk] kevin01523:
there is new info

the author made a module. but only works on a11

and caused boot loop on android 10 and below

I do hope you could include his fix on your module but supports a10 and below

keystore: Block key attestation for Google Play Services · ProtonAOSP/android_system_security@15633a3

In order to enforce SafetyNet security, Google Play Services is now using hardware attestation for ctsProfile validation in all cases, even when basic attestation is selected. The SafetyNet API res...

github.com
[Magisk] Dydnlee:
[QUOTE = "kevin01523, gönderi: 84280845, üye: 10519543"]

yeni bilgi var

yazar bir modül hazırladı. ama sadece a11'de çalışır

[URL unfurl = "true"] https://github.com/ProtonAOSP/andro...mmit/15633a3d29bf727b83083f2c49d906c16527d389 [/ URL]

[/ALINTI]

Android 10 😥😥
[Magisk] Didgeridoohan:
Interesting. I'll take a look and possibly implement here. Thanks.
[Magisk] Golf c:
Back in the saddle.
[Magisk] kevin01523:
android 11?
[Magisk] zgfg:
By itself/Google, you changed something or how?
[Magisk] Golf c:
Two posts above
[Magisk] tenow:
Has anyone tested kdrag0n module on Android 10? I can't upgrade to 11 because of systemless hosts freezes
[Magisk] fubo73:
It does not work on android 10
[Magisk] cmstlist:
Excuse my ignorance, but how does one install that fix module? I don't see a module download link on that Github.
[Magisk] dunderball:
Where can I find the module? The post looks like a git commit for a custom rom.
[Magisk] Didgeridoohan:
Download the code as a zip and repack it so that the module files and folders are directly in the root of the zip rather in the "safetynet-fix-master" directory.
[Magisk] Didgeridoohan:
https://github.com/kdrag0n/safetynet-fix

Edit: and also see my post right above this.
[Magisk] Golf c:
MM is in his telegram group. He has already updated it for more devices. Only works on A11 for now.

https://xdaforums.com/t/rom-pixel-5-official-protonaosp-11-3-0.4188129/post-83887319
[Magisk] cmstlist:
Got it thanks! And works!

Now for a more delicate task, how to get Google Pay working again without totally resetting Google Services. Don't want to do that because it would zap the data used by my local COVID exposure notification app.
[Magisk] DocMAX:
is there a chance that someday safepass will never work on hacked phones? if so then we should start to begin using normal phones?
[Magisk] MarcinLewkowicz:
Of course. I think it's the aim of Google.

Loot at the accepted answer:

Magisk will fail Safety-Net hereafter. Why?

Recently, Google made security changes which make sure safety-net fails check when Magisk is installed. This was Tweeted by John Wu (Magisk developer) , here and here. Some excerpts: So here we...

android.stackexchange.com
[Magisk] bartleby999:
Yes. Download stock rom and flash it with Odin.
[Magisk] dimm0k:
this would be great if we don't need another separate mod
[Magisk] zgfg:
Thanks, it works on Xiaomi.eu A11
[Magisk] Golf c:
For the time being. Lol 😂
[Magisk] jonathan240196:
And for Xiaomi.eu 12.0.6.0 Android 10 stable ROM ?
[Magisk] mamama07:
Same here, it's working like a charm. I attach a zip-module from previous link. Flash it via magisk manager ONLY in android 11. ONLY ANDROID 11 (in my case xiaomi eu, mi9, Android 11)
[Magisk] pndwal:
I notice this added value benefit of the @kdrag0n fix over current 'force Basic' MHPC solution for ctsProfile (apart from it no longer working for most 🤐):

Hope you can implement this very much... Would love to see solution for Android 10 and earlier ROMs also! All best, PW
[Magisk] onlyrafin:
Mine.... Working just fine

Device: POCO F1

Custom Rom: AEX 7.3 (Android 10)

View attachment 5186049
[Magisk] elphamale:
I found a workaround that allowed me to bind a card in GPay and make a payment on Anrdoid 10.

It does not allow to pass safetynet or make ctsprofile true - it only makes GPay work.

I am not an author of this hack do I know who made it - credit to the guys on 4pda forums. Also I am not an android developer and don't exactly know how most things work.

The workaround is:

0. (Optional) Before applying workaround I cleared all data google play services, google pay and google services framework.

1. Download GooglePay_fix (this file), unzip it and find a file dg.db. For some reason I wasn't able to attach it to this post.

2. Delete everything in your device's /data/data/com.google.android.gms/app_dg_cache and change this folder's attributes to read-only: 444 or r--r--r--

3. Go to /data/data/com.google.android.gms/databases/ and delete dg.db and dg.db-journal.

4. Copy downloaded dg.db in /data/data/com.google.android.gms/databases/ and assign it read only attributes (444 or r--r--r--).

5. Compare checksums of both files. If they don't match then do steps 3-4 again until they do.

6. Reboot.

7. (Optional) Bind a card in GPay again and try to make a payment with it.

8. (Optional) Restrain yourself from checking SafetyNet - it will be false.

Its only 2 hours after I applied this and so far I only did 2 payments with ~40 minutes between them. It may break down in the future.

Also I don't know if it fixes any other apps that depend on SafetyNet.
[Magisk] Didgeridoohan:
@elphamale That's great, but has nothing at all to do with this thread. Please post it in one is the GPay threads instead.

Edit: and when you do, maybe you can clarify how it's any different from this: https://xdaforums.com/t/working-magisk-with-google-pay-as-of-gms-17-1-22-on-pie.3929950/
[Magisk] fizbanrapper:
Zip file fixed profile check on my pixel 3 xl
[Magisk] Didgeridoohan:
Did you edit this yourself, or is it from @kdrag0n? It's always a good idea to specify the source when throwing out zips... Better yet, if there's a link to an original source post that.
[Magisk] tenow:
it's @kdrag0n module, from kdrag0n's Telegram but modified for Android 10 by someone else, reuploaded there.
[Magisk] elphamale:
Sorry I thought the info may be helpful or related. Please delete that post and this one if you think it isn't needed here.

Also, I haven't seen the solution in the link.
[Magisk] ktdt00:
Worked on my Pix3. Play Store showing "Certified" and Gpay re-allowed contactless payments after I clicked "Check Software" in the warning dialog inside the app.
[Magisk] jhobc:
Thanks! SafetyNet passing perfectly now! :)

Mi 9T Pro + Magisk Canary + MIUI EU (20.12.9 - Android 10)
[Magisk] MoL_82:
Same on Samsung S9. But Root Checker shows it cannot acces Google Play Services.
[Magisk] Didgeridoohan:
Do you and that person have permission to alter and redistribute the zip? Always important to consider before throwing stuff out there.

And, as I said before, providing the source of stuff you share is also a very good idea (for future reference).
[Magisk] Didgeridoohan:
Helpful, sure. Related to this thread? Nah...

I have not yet looked closer at what you posted, but the method in the link I gave you is very similar.
[Magisk] Dydnlee:
Note 8 pro Android 10 cts profile true 👍👍
[Magisk] Didgeridoohan:
Ok. New daily reminder.

It's not at all necessary to post here that the new SafetyNet fix zip works. We know it does...
[Magisk] XXX-Man26:
With that zip from kdrag0n I can pass safetynet but gpay still says device not secure and nfc payment is disabled.

Mi 10, android 11, xiaomi.eu rom
[Magisk] dunderball:
Brilliant. Works great on Pixel 3a. I didn't even need to install the Props module. Safety net passed and my device is ready for nfc payments again.
[Magisk] Didgeridoohan:
GPay discussions:

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/
[Magisk] AndDiSa:
@XXX-Man26 most likely the last result is stored persistently on your device try to follow the instructions from https://xdaforums.com/t/working-magisk-with-google-pay-as-of-gms-17-1-22-on-pie.3929950/
[Magisk] dunderball:
Brilliant. Works great on my Pixel 3a. Did not even need to install the Props module. Safetynet passes and payments working again. Thanks!

EDIT: Whoops! Sorry for the double post!!!
[Magisk] heihachi34:
Doesn't work with SM-G975F ( S10 plus). Tried flashing it through magisk got bootloops.

Had to restore nandroid backup.
[Magisk] Didgeridoohan:
Not surprising... It's bound to not work with every device.
[Magisk] heihachi34:
EDIT:

It worked after I changed the security patch date to default. And re-installed the fingerprint.

Android 10 stock rom

Magisk 21.2

Magisk manager v8.0.5

CTSprofile ✅

Basic integrity ✅

Playstore (Device is certified) ✅

S10 plus 1TB edition

Thanks for the support everyone.

For now.
[Magisk] djjohnnyblaze:
the new method (magisk module A11 fix) is working perfectly for me on my Pixel 3a as well. It works without changing my fingerprint as well.
[Magisk] reizo111:
It works on my custom compiled RR rom, Android 10, Xiaomi Redmi Note 9 PRO (joyeuse), thanks to whomever came up with that for Android 10. Please mention the source as official GitHub for this fix states Android 11 only.
[Magisk] s0d4:
First of all, thanks to everybody for working continously to get Safety Net running with unlocked bootloader and even with Magisk installed.

After applying the new fix for A10 I also pass safety net within magisk, but safety net checker app resports "failed - no access to google play services".

GooglePay works, Google Play Services show "Device is Certifieid" as well. But my Coorp. Email program still finds root and terminates it's function.

Any ideas how to fix?

(MIUI Global 12.0.1 A10 on Redmi Note 9 Pro (Joyeuse)).

View attachment 5186143 View attachment 5186141 View attachment 5186137
[Magisk] zgfg:
Don't worry about that app (try next time/day) - they have quota for the number of tests

Yesterday everybody was testing due to the failure, today due to the fix.

Yesterday I had the same problem with that app for a phone with bootloader locked, today morning (before the fix became popular) I was able to pass with that app on that phone

Also, on my rooted phone I flashed the fix early today and was also able to pass - now the same overquota problem with that app

The fix is ok, you can find two other SafetyNet checkers on the Playstore
[Magisk] XXX-Man26:
Deleting all data to gplay, play store and play services fixed problem (y)
[Magisk] ew:
I wanted to report - this is interesting. Moto G6Plus Android 10 Havoc OS. I have had basic failure and have not done anything about that yet.

Despite the failure, I was able to make a payment with gpay (this morning) and add a payment type (late yesterday)
[Magisk] _mysiak_:
I just cleared cache (not user data) of Google pay app, opened it again, clicked on the card saying that my device is not certified and after a while I got a message saying that I can use Gpay again.
[Magisk] zygorf:
Great to hear it's working for Android 10 and 11. Any fixes for Android 9 yet?

I'm using a Mi Mix 3 5G so no official Android 10 or 11 ROMs exist.

Alternatively does anyone have a link to the kdrag0n telegram channel that is mentioned where this was originally posted? Thanks
[Magisk] tenow:
I got android 10 fix from this telegram https://t.me/proton_p5

but author says he's not planning to release 9
[Magisk] bluedog220:
Thank you ! Success!
[Magisk] DocMAX:
safetynet passes now, but google pay still detects rooted device
[Magisk] zgfg:
I've seen more than one or two posts how people fixed the GPay, look both in Magisk and MHCP threads
[Magisk] porotikos:
Working for me as well thank you so much. Xiaomi mi note 10 pro runni g android 10
[Magisk] pippo45454:
Do you know if safetynet-fix-master.zip work with MIUI 12.01 android 10?(redmi note 9 pro)
[Magisk] zgfg:
Use the version for A10 and try.

People reported that it works for A10 (I think somebody even for MIUI 12 but not exactly your phone), no reason it would not for you (I have A11 version and it works for Xiaomi.eu MIUI 12.5).

If certain (systemless - this one is) module does not work or you don't like it, you simply uninstall with no consequences
[Magisk] Fytdyh:
Does this module and magisk work for Android 11?
[Magisk] zgfg:
Please go through the posts as of today - how many people confirmed that it works
[Magisk] Drahy:
I tried this on my Samsung Galaxy A6 - and have bootloop now :-/ It tries to update system and optimize apps but then goes restart over and over - not sure how to go out of it now...
[Magisk] Drahy:
I am in safety mode how can I delete the mod from my phone manually? What should I delete?
[Magisk] drup88:
Thank you sir, working on Pixel 4 xl running Android 11 RP1A.200720.009
[Magisk] Fun_GKC:
For the universal safetynet fix, please visit the below telegram channel

https://t.me/proton_releases
[Magisk] zgfg:
You mean Magisk module?

Not from Safe mode, reboot to 'normal' Android mode, all modules will be disabled and you manage them from Magisk Manager

You will also have to enable again Magisk hide
[Magisk] pndwal:
Nothing. OTOH, after booting in safe mode, then simply rebooting to system, all modules are disabled and MagiskHide disabled. You can then remove or enable modules, and enable MagiskHide again as normal. PW
[Magisk] pndwal:
Can confirm new SafetyNet-Fix module supports Android 8 thru 11 now; Danny Lin has been burning the candle...

Also:

Releases are also now available directly from GitHub page (click Assets), so no need to post/use unauthorised links/files now it seems. 👍

https://github.com/kdrag0n/safetynet-fix

There may, of course, be some teething problems! PW
[Magisk] Dydnlee:
Android 9 and Android 10 note 8pro not work
[Magisk] zgfg:
Please continue discussion about Universal SafetyNet Fix to its new XDA thread:
[Magisk] detlev24:
Tested on Samsung Galaxy S9 with latest "DevBase v7.3" ROM from @_alexndr.

Yes, SafetyNet passes completely but unfortunately, Android became slow, started to freeze and rebooted often + put the phone in 'airplane mode' after some reboots.

Does anybody know of a working solution via this - MagiskHide Props Config - module? THX!
[Magisk] Didgeridoohan:
Nope... The trick with changing the model prop doesn't work anymore. You always get hardware backed key attestation now, if the hardware is available.