yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Gordietm:
I'd just like to clarify what is the final safety net fix zip we should be using?

There was the test zip (that worked for me), then the MOD 2.0u zip.
[Android Software Development] casouzaj:
ATTENTION!!! This version messed up with Pixel Launcher in my Xperia XZ2, running AwakenOS 2.10 (A12L). After boot up, screen kept showing `phone is starting...` like forever. I removed the safetynet-fix folder from /data/adb/modules, booted to system, and installed the previous version from Displax (released today) from Magisk (Delta Canary, if it matters). After reboot, Pixel Laucher was back to work again.
[Android Software Development] Kris Chen:
Well, it's not a problem for me because my Pixel 6 pro with stock A13 rom and a MOD pixel launcher.

I flashed this MOD without any problem ~
[Android Software Development] Sasy969:
View attachment 5736189

I was referring about this
[Android Software Development] JakeDHS07:
Try new release that was posted and you should pass all but Strong which is expected due to basic fallback
[Android Software Development] Sasy969:
Just tried now with SFNF mod 2.0 and nothing changes
[Android Software Development] JakeDHS07:
Then you need to check your denylist and make sure you have the proper setup. It's important that Play Protect Service and Google Framework also be denied with Play Store and Wallet/Pay
[Android Software Development] Sasy969:
I don't have play protect in my list
[Android Software Development] JakeDHS07:
Hit the menu at the top right and choose show system apps. Then you should see it under G
[Android Software Development] Sasy969:
I know i am a noob, but i have just tried this way 🤣i don't know why the check symbol doesn't show up for AA and FrameworkView attachment 5736211
[Android Software Development] 73sydney:
What doesnt need to be in the Deny List:

Play Protect

Google Framework

Wallet/Pay (technically - mine hasnt been hidden in 4 months and counting)
[Android Software Development] 73sydney:
People hide stuff thats not necessary - sometimes every Google package

You do not need:

Carrier Services

Google Services Framework
[Android Software Development] JakeDHS07:
It can't hurt. They don't need Root anyways. But just trying to help them get passing.
[Android Software Development] Sasy969:
Ok but I'm still unable to add card to Gpay
[Android Software Development] JakeDHS07:
Services showing up checked means something is wrong as with the fix mod properly installed it should be showing up as unchecked. Install the attached module by @Displax in Magisk Modules then reboot and check again.
[Android Software Development] Sasy969:
I'm so sorry to bother you, but have already done this View attachment 5736219
[Android Software Development] JakeDHS07:
Well with that installed and proper configured DenyList you'll be passing all but Strong Integrity. Make sure you clear data on Play Store and Services then reboot. If you're not clearing data the old failure will still be there.
[Android Software Development] Displax:
You install old version. Update to new.
[Android Software Development] Sasy969:
Also with the mod 2.0 always same resultView attachment 5736261View attachment 5736263
[Android Software Development] JakeDHS07:
There was an error in the earlier upload of 2.0. Redownload the corrected version of the module and install now. Then reboot.
[Android Software Development] 73sydney:
Au contraire...

And I refer the gentlemen to the Book Of Didgeridoohan

"

Apps on the MagiskHide list

If apps on the MagiskHide list are force closing, simply remove them from the list. You should only add the apps and processes that actually detect root. Adding anything else to the list, that doesn't need to be there, may cause instabilities in your system (also see "System instabilities" above) Note: It's not about the number of apps on the list, but which apps are added."

Please refrain from advocating unnecessary packages, please and thank you

All Magisk users should have this bookmarked:

{{color text="Magisk and MagiskHide Installation and Troubleshooting gu:Magisk and MagiskHide Installation and Troubleshooting guide

didgeridoohan.com
[Android Software Development] Sasy969:
Nothing to do
[Android Software Development] JakeDHS07:
Just download and install this module it will overwrite the previous version and should be working. Again this has been tested and proven as working when properly configured. If you follow the steps and advice given here the issue will be resolved.
[Android Software Development] Nbsss:
Any advantage of the new release 2.3.1-MOD over the test release?

The test is working fine on my p7p
[Android Software Development] zgfg:
Sorry guys but this is going out of control, this mod version, 2.0 but in that post, etc

Wouldn't be possible to upgrade the official @kdrag0n USNF module, or that @Displax posts releases on his GitHub project and that the latest release would be the relevant one.

Btw, he can also use jsonUpdate mechanism that his module can update automatically
[Android Software Development] JakeDHS07:
I'm not sure why the official module hasn't been updated. But @Displax did upload the corrected version to GitHub earlier today after the error was discovered by a few of us last night. That version is valid and up and what I attached to my previous post.
[Android Software Development] zgfg:
There could be releases on his GitGub page, that users can download there the latest/valid zip instead of searching and digging through the posts

Besides, module can have updateJson mechanism that everybody would be able to update to the latest/correct version by simply clicking to Update - when updated version becomes available
[Android Software Development] JakeDHS07:
That GitHub is right here : https://github.com/Displax/safetynet-fix/tree/integrity

As for the update mechanism that's a great idea. I'm sure there's a reason it hasn't been implemented by @Displax. If I had to guess it's because he is creating a MOD and not the original creator of the module @kdrag0n. Hopefully kdrag0n will have time to update the official release soon and everything will be back to normal. In the meantime that's why these forums exist. To give resources to and assist. 💪
[Android Software Development] YMatrix:
A bit off topic:

I'm facing a dilemma - I'm using the old version of the @Displax mod and it's working, but there is a new version out...

Update? Or live by the rule don't touch what's working?

What to do?! What to do?! 😝

I guess for now I'll live by the rule of if it's working, it doesn't need fixing🤣
[Android Software Development] JakeDHS07:
I was facing this exact same dilemma earlier. However, I had enough time to test and I love being up to date on everything. It's a compulsion so I tested the re-uploaded 2.0 everything passes it still working only then did I get rid of the test version 😂
[Android Software Development] zgfg:
Ok, sorry, I see, the releases are also there:

Releases · Displax/safetynet-fix

SafetyNet & Play Integrity API workarounds for Magisk - Displax/safetynet-fix

github.com

Hence that is the right place to always download his latest version
[Android Software Development] pndwal:
May be something funny w/ crdroid ROMs

- https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-87484949

- https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-87486193

- https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87488331

- especially the way they integrate Safety net Fix etc may be interfering with Magisk USNF module...

Try the wipes + disable (or uninstall) and reboot before reinstall that worked for some as linked above...

Also, try to pass S/N / PI deviceIntegrity just with @Displax modded USNF - disable all other modules, ensure Zygisk = Yes, have nothing in denylist... PW
[Android Software Development] pndwal:
Do whatever you like... New fix is only for Pixel 7 and other devices launched with Android 13... It shouldn't break fix for earlier devices as ro.product.first_api_level
is only adjusted when set to 33. API level 33 is Android 13)...

Nb. @Displax fixes are much appreciated, but are to be considered interim fixes... He has submitted each PI fix to his pull request in official USNF; the latest is now in PR by @anirudhgupta109 but @kdrago0n is still considering improved methods etc before merging these...

@ Displax updates this post here:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87198517

🤠 PW
[Android Software Development] m0han:
The module I'm using is in the screenshot. Should it be updated to the current 'safetynet-fix-v2.3.1-MOD_2.0'?

p.s.: I'm running AICP A12.1 on Poco X3 Karna, rooted with the latest Magisk Delta Canary (Riru, no Zygisk, MagiskHide....).
[Android Software Development] JakeDHS07:
If you choose to you can but it will make no difference for that device as it's only affecting those that launched with A13.
[Android Software Development] m0han:
Had I seen this before submitting my post earlier, it would've saved everyone some work.
[Android Software Development] JakeDHS07:
No worries. I'm bored and binge watching The Shield anyways till I fall asleep 😂. This is just giving me something to do.
[Android Software Development] Sasy969:
First of all thanks for your help, but neither this worked.
[Android Software Development] pndwal:
Re. old MagiskHide John originally said this:

https://xdaforums.com/t/magisk-the-magic-mask-for-android.3473445/post-70363391

I know this passive mechanism didn't change much during MagiskHide's existence, however I haven't dug into the code to see if modern denylist implementation now actually does hijack app_process (Zygote) by means of Zygisk which would largely overcome these response timing issues etc...

I suspect the mechanism may well have changed as I know better root hiding was central to John's original published motivation for adopting a means to inject into zygote in Magisk, moreover, while MagiskHide was 'sunsetted' with some code preserved in new denylist, denylist and Zygisk were actually developed in tandem during the period John was 'AWOL' undergoing his/Magisk project's Google review process...

Perhaps someone who's checked the code could say for sure if denyist process monitor implementation still uses Zygote ptracing and/or similar, still requires 'Scan zygote multiple times' etc, or if we now do have active hijacking of app_processes (Zygote) using Zygisk... 🙃 PW
[Android Software Development] zgfg:
Btw, it would be good if in @Displax module.prop,

line:

version=v2.3.1

will be changed to:

version=v2.3.1-Mod-2.0

That one csn see under Magisk, Modules, what version of USNF is running.

Currently for the official USNF, for old one from Displax, his newer, DOS fix - they all show the same v2.3.1 in the Magisk, Modules and one cannot distinguish which one was the last installed

Also, I'm curious about that service.sh

AFAIK, it is Zygisk module hence it uses the native code to target only GMS

Eg, I had previously tested: I removed service.sh (and rebooted), and the module still worked to pass PI Basic and Device Integrity (by using its Zygisk native code implemenation)
[Android Software Development] pndwal:
It's a Zygisk module which is what allows for targeted prop changes...

@Displax's added A6 fingerprint change for PI targets GMS also... For some reason he applied new ro.product.first_api_level change globally, (for LV A13) but has now deferred to @anirudhgupta109's implementation which doesn't set the prop at early boot. @kdrag0n has commented he likes this better but still has concerns:

https://github.com/kdrag0n/safetynet-fix/pull/225#issuecomment-1279854419

PW
[Android Software Development] zgfg:
I'm saying that I don't see a reason for service.sh script (scripts target props changes for ALL)

Zygisk modules mainly work by their native code (unzip the module and look into its zygisk folder, or look for the same in /adb/modules...)

And I just tested again, with completely removed service.sh, the module still works fine.

Ok, I have no A13 but A12, but nonetheless
[Android Software Development] pndwal:
Just checked it.

Of the three current (critical) prop changes made to cause mismatches triggering hardware verdict enforcement

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87575455

only the last, ro.product.first_api_level (for LV A13), is set in service.sh, now in late start, which explains why the module still works for you with this disabled... seems this prop change doesn't break encryption (perhaps @Displax fix did?), but seems @kdrag0n may prefer to see it set to target GMS along with ro.product.model and ro.build.fingerprint...

I see other (non critical) prop changes to avoid breaking OEM hardware etc are also set here so we'd need consider those fixes if removing service.sh. PW
[Android Software Development] ipdev:
Then you would not like the test version I am using. 😜

[GitHub] - service.sh​

Cheers. :cowboy:
[Android Software Development] m0han:
Feedback: The new mod(ule) does not load for me (not using Zygisk); the earlier one does.
[Android Software Development] pndwal:
So earlier loaded w/o Zygisk?... Last official did restore support for Android 7... I believe this is just for old MagiskHide features (sensitive prop resets etc) as there's no need to work around hardware attestation in A7 and Zygisk parts not needed...

Seems if @Displax mod version previously had this, he's removed something... In guessing you'll see an extra change in service.sh, but could be elsewhere... You could check... I haven't got time ATM. 🙃

Of course older modded version is fine for all but A13 launch version devices... Also I see no need for use w/o Zygisk parts on anything other than Android 7 etc...

🤠 PW
[Android Software Development] denunity:
im on the Android 13 october patch security dont pass integrity api with Diplax safety net fix mod 2.0. How can this be solved?
[Android Software Development] JakeDHS07:
If the mod is properly installed than it must be the DenyList. Check that everything is checked that should be. Play Store and Wallet/Pay especially.
[Android Software Development] m0han:
Please check this post for my setup. Been a long time since I last used Zygisk.
[Android Software Development] denunity:
What should I do in this case if problem with denylist?
[Android Software Development] JakeDHS07:
Deny root to those that should be. Clear data on Play Store and Services and then reboot
[Android Software Development] denunity:
okay, but why in integrity checker dont pass meets_device_integrity?
[Android Software Development] JakeDHS07:
If root isn't denied to the reporters of root status then it will return a failure
[Android Software Development] pndwal:
I have last official USNF since I haven't needed any further bypasses for hardware verdict enforcement on my Xiaomi RN8T w/ A10 MIUI...

I just disabled Zygisk, rebooted and get the same message, so it seems your Displax moded USNF is behaving just like official...

I'm guessing it must disable Zygisk parts and run only if Android 7 is detected...

I'm not sure what use the module is to you w/o Zygisk parts (these are the main features, ie fallback to Basic attestation and bypasses for hardware verdict enforcement) in any case, even on Delta Magisk fork on your modern 2SI device...

@huskydg has a Riru USNF fork to enable these functions w/ Riru xhook; I haven't checked, but he may well have updated that for those wanting Play Integrity fixes w/ Zygisk-less Magisk...

Also I have no Idea why previous @Displax might run for you w/o Zygisk... Perhaps you had some further mod? Actually enabled Zygisk? Some Delta peculiarity? Spoofing Android 7?... Really no clue, but it shouldn't normally work like that... 😬 PW
[Android Software Development] pndwal:
Please say device, ROM, YASNAC result... PW
[Android Software Development] m0han:
I know I am gonna get flamed for this....

.... but, somewhere along the way I noted that Debug Environment is not flagged when I use that module. Nothing else, AFAIK. :LOL:

View attachment 5737309View attachment 5737313

View attachment 5737317View attachment 5737319View attachment 5737321
[Android Software Development] 73sydney:
ill hold him down while you administer The Treatment @pndwal
[Android Software Development] zgfg:
Sorry, I miss. Which module?
[Android Software Development] m0han:
The one in the screenshot in this post.
[Android Software Development] denunity:
did not help:(
[Android Software Development] denunity:
Poco F3, Cherish OS
[Android Software Development] pndwal:
What results with previous version from here?:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87198517 PW
[Android Software Development] ysco:
I also still have issues that Google wallet is not working.

Installed the latest fix and added to the deny list wallet/playstore/playservices. Deleted app data ect.ect.

Info phone.

Pixel pro 7

Latest stock android 13 (api33)

Unlocked boot loader

Magisk installed.

Spoiler content hidden.

I posted some screenshots and hope someone can let me know what is wrong as there are some bad checks.

Thanks in advance.

Regards ysco..

{Mod edit: Spoiler added for better reading and scrolling experiences. - Oswald Boelcke}
[Android Software Development] pndwal:
Further, if above doesn't help it seems you have issue common to Po co F3 here (showed up in crdroid ROM):

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-87482247

and posts following...

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-87484949

I believe the issue was conflict with integrated SafetyNet fix in ROM. Other device custom ROMs have had this issue also...

You may be able to fix by disabling modded USNF, rebooting, anabling again, rebooting again, or doing similarly but actually ununstalling/reinstalling:

- https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87486829

- https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87488331

- https://xdaforums.com/t/rom-12-1-of...rdroid-v8-10-15-10-2022.4386959/post-87490145

Anyway, my post linked above was mentioned in poco crdroid thread:

https://xdaforums.com/t/rom-12-1-of...rdroid-v8-10-15-10-2022.4386959/post-87485439

... Dev responded:

https://xdaforums.com/t/rom-12-1-of...rdroid-v8-10-15-10-2022.4386959/post-87485489

and fixed crDroidAndroid-12.1-20221015-alioth-v8.10:

https://xdaforums.com/t/rom-12-1-of...rdroid-v8-10-15-10-2022.4386959/post-87577173

Your ROM may need a similar fix... (Is there an XDA forum?... seems not...)... Or you might like above A12.1 ROM... seems it might get A13 soon when LOS base is properly adapted:

https://xdaforums.com/t/rom-12-1-of...rdroid-v8-10-15-10-2022.4386959/post-87565559

👀 PW
[Android Software Development] pndwal:
So you have the requisite deviceIntegrity pass... See this; scroll down to Related Issues:

https://xdaforums.com/t/...agisk-discussion-thread.3906703/post-87481637

👍 PW
[Android Software Development] ihavenolifee:
According to the new mod 2.0 for A13, it should work on strong integrity? Does this work for anyone? I couldn't get this to work on my end.

Also, is there any reason you would need strong integrity to be met?

> "Bypassing forced STRONG integrity for devices that shipped with Android 13+ (Pixel`s 7 )"
[Android Software Development] JakeDHS07:
That means it's bypassing Strong integrity being forced on the device not that it would pass. Strong integrity is a different form of attestation which is as of yet undefeated. This mod bypasses that and falls back to the previous basic attestation which can be passed. Strong integrity failing is expected.
[Android Software Development] ihavenolifee:
Makes more sense. That's what I figured haha. Thanks for the clarification
[Android Software Development] ysco:
Thx for the reply mate 😉

Have read al but seems I try't it al, I can't even add my cards. Will follow the steps again when I m home again. Regards ysco..
[Android Software Development] Vulhirk:
I am using a beta rom and the debug environment option appears in this rom. After many bank applications used shamiko and usf together, there was no problem, but some applications are giving errors due to the debug environment option. Is there a way to solve this?
[Android Software Development] ysco:
Well i have try everthing and i still can't get it to work. My bank apps are blocked correct in magisk so that works but i can not connect a bank card into google wallet. Everytime the same errors.

Is this a Pixel 7 pro related issue with a13 ?? are there members that have it working on this specific phone model ??

Regards ysco..
[Android Software Development] JakeDHS07:
Wallet working fine on my P7P with latest mod installed and DenyList configured.
[Android Software Development] pndwal:
Really @Displax shouldn't say "Bypassing forced STRONG integrity" as STRONG integrity is a verdict label description... This label may optionally be used by banks but hasn't been spotted in the wild as yet!

He really means it "bypasses the Play Integrity API's check for device support for hardware-backed attestation and/or enforcement of hardware-backed attestation based verdict" which is needed for passing deviceIntegrity.

This much the same as bypassing SafetyNet API's check for device support for hardware-backed attestation and enforcement of a hardware-backed verdict which is needed for passing CTS Profile match per:

https://github.com/kdrag0n/safetyne...ails.md#how-does-universal-safetynet-fix-work

... Even this correction is not strictly correct... The Shipping API level prop based (latest) HK verdict bypass is only achieved if both the previous fingerprint prop based bypass and the original model prop based bypass are working also...

🤠 PW
[Android Software Development] zgfg:
Yo are right but for someone new the answer may lead to missunderstanding

Strong Integrity requires that CTS Profile was validated by Trusted Execution Environment (TEE)

USNF tricks the PI API, saying that user has an older device for whom Google does not require the use of TEE.

Hence instead of being validated through TEE, CTS Profile was 'validated' through 'software' where it was actually possible to fake the positive validation

Hence, when you see in PI Checker that Basic and Device Integrity passed while Strong failed, it does not mean that TEE was asked and that TEE returned CTS Profile failure (that would be the real red flag)

Instead it just means that CTS Profile validation through TEE was skipped all together (hence it is not known what TEE would say), and that instead the less reliable 'validation' through 'software' was submitted (therefore, that validation MIGHT have been prone to faking, but anybody can only 'guess' was it faked or not and since not having the TEE validation would hopefully accept this one that is less trustworthy)
[Android Software Development] ysco:
Hello Mate,

Hmm strange that i can`t get it working. Im now trying different fingerprints settings in the prop but still no luck.

Would you mind to post the steps that u used and the exact modules and magisk settings. I would be gratefull if you can take the time to post the instructions.If it works for you then it also should work for me.

Thanks in advance.

Regards, ysco..
[Android Software Development] JakeDHS07:
I'm using stock rom and only the 2.0 mod by Displax with the DenyList setup. That's all. No changing fingerprints or prop settings.
[Android Software Development] ysco:
Well that's strange, i also have stockrom and tried also the steps you mentioned and still no luck. I assume you are rooted otherwise you wouldn't need the Displax safetynet fix. If i folow the instrucions and check with Yasnac after install the safetynet fix and check play integrity checker then it have the correct checkmarks. There is no way i can add my bankcards. i always get this message see (screenshot)View attachment 5738111View attachment 5738115View attachment 5738117View attachment 5738119
[Android Software Development] JakeDHS07:
Have you cleared the data on Store, Services, Wallet since you set it all up? If not do that as it will reset the earlier failures.