yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
audio_effects conf and xml and soundfx (with libstdc++ in the same folder) belong to V4A - disable V4A and retest

Btw, for me, sus sometimes detects V4A, sometimes not - but systematically, after each reboot it always detects them or always not

BusyBox, if installed systemlessly, should not be visible

My Canary 25206 with Zygisk, MagiskHide module, Sensitive props - with BusyBox and ToyBox modules (mounted also to /system/xbin but not detected) and with ReVanced YT as attached (hence my results with Delta in the post #55033 Magisk thread were better - only ReVanced YT was detected there)
[Magisk] Spartacus500:
My Samsung Galaxy S7 edge Custom Pie 9.0 Rom NFE info Fingerprint has been tampered 🤔 How to fix 🤔
[Magisk] pndwal:
Are you using MHPC instead of a USNF solution for deviceIntegrity?... PW
[Magisk] david003:
Yes, thank you. I was a little confused regarding the various versions of magisk, official vs. canary vs. delta.
[Magisk] pndwal:
BusyBox is @osm0sis' systemless... All my modules:

Improvement due to SUList use?

... Anyway, seems @david003's app detects only Dirty... and not Found... items here since it works fine w/ Canary 25209. (Member had 25.2, 25200). PW
[Magisk] m0han:
Riru ain't doing bad either. I have a few more modules, though.
[Magisk] pndwal:
Mmm I have DisableFlagSecure as LSPosed module... Do you still use AML?... PW
[Magisk] m0han:
Which version? Why isn't it seen in the list? Combo screenshot of the list of my modules attached.

Yes. Is it not required? See my modules. But, I have an issue - if anything takes over the microphone while I'm listening to music or watching video, Viper loses it's effect (Driver status shows Processing: No). After the takeover ends, I have to disable and re-enable 'Legacy Mode' in Viper settings to get the effect back. Any way to resolve this? I'm on Android 12.1. Would @zgfg have something to say?
[Magisk] pndwal:
I have no such issues, but apparently AML can interfere w/ Viper... (just going by memory here...) Anyway it's only needed if you have multiple audio mods AFAIK... Not needed for viper...

Guess when driver status shows Processing: No it says 'Abnormal' too?... As long as Legacy is enabled you can disable V4AFX module and reboot then enable and reboot again to restore...

@zgfg may have more... We both generally use this build now which seems to fix old issues too:

https://github.com/programminghoch10/ViPER4AndroidRepackaged

... I just wanted to test something with original V4AFX and haven't reverted...

I'd disable AML and give ViPER4AndroidRepackaged a blast around the block... PW
[Magisk] zgfg:
I use V4A 64-bit Beta:

GitHub - AndroidAudioMods/ViPER4Android: ViPER4Android app configuration files

ViPER4Android app configuration files. Contribute to AndroidAudioMods/ViPER4Android development by creating an account on GitHub.

github.com

(also Legacy mode)

I need AML since I also run JamesDSP
[Magisk] zgfg:
As replied in the previous post, I use V4A 64-bit re-ingeneered

I don't have (never had also with your V4A version) issues with loosing the audio focus on alerts or so - there would be a ringing or so, but V4A continues to process its music
[Magisk] Spartacus500:
I have such modules, I removed the universal SafetyNet fix, but it did nothing 🤔
[Magisk] m0han:
Is this the 64-bit beta? Install app, flash module in Magisk, reboot? Anything else to be done?
[Magisk] zgfg:
I think you must set Legacy mode (I always do)

Also, settings are now at the different path:

/Documents/ViPER4Android

Hence you must enable Master limiter and configure the tweaks (read on the GitHub about the status, what was ported)

Btw, package names for the apps are different, make sure you uninstall the old V4A
[Magisk] pndwal:
I though it might be due to MHPC globally setting props but not...

USNF used targeted spoofing of fingerprint prop so should be ok... I'd swap it for @Displax modded build as official is broken ATM...

You won't need the sensitive props module with USNF as it already does this... (I believe Shamiko does too!)... I'd try disabling that and check again...

You don't actually need USNF as your device is too old for keymaster 3, but targeted USNF is the best way to spoof a fingerprint prop which you may need since you have custom ROM...

If your ROM spoofs fingerprint prop itself, you could remove USNF and add gms attestation/droidguard (Google Play Services com.google.android.gms.unstable) process to denylist to hide root, and add any one of the following to set sensitive props to Google expected values:

-Your SafetyNet Sensitive Props module

- Shamiko

- MagiskHide Props Config module left unconfigured (This resets sensitive props by default is loaded)

... You should not need more than one of these running, but try swapping if deviceIntegrity doesn't pass...

🤠 PW
[Magisk] m0han:
Did all this. But, does not work. Disabled, Re-enabled, Rebooted.....
[Magisk] Spartacus500:
Unfortunately, it does not help, maybe the fault that I edited the build.prop file 🤔
[Magisk] zgfg:
Screenshots look ok, don't know why you have "Not enabled" except that it's still Beta v0.3.0

I assume you have uninstalled the V4A module v2.7.2.1 (Repackaged)

Try also: disable AML and other audio modules you have, reboot and maybe re-install this 64-bit V4A (over the installed one)

You could check if there are similar issues reported on the GitHub and I don't know if there is a TG support channel.

There are few active V4A threads on XDA, to ask there
[Magisk] m0han:
Uninstalled app, module, rebooted, installed 0.3.0, configured, rebooted, rinse, wash, repeat....

Yes, did all that. I had only AML; don't have that anymore.

OK. I posted about my issue as I found references to Viper here. I'll stop now (already too OT for this thread?) and go back to the working v2.7.2.1. Thanks for all your guidance.
[Magisk] v.konvict:
Anyone with a solution to 8ball pool game. I am passing safetynet and even my banking apps are working fine but it crashes with root.
[Magisk] immortalwon:
I was forced to upgrade to displax's module today. Pokemon go kept failing to login, which means k-dragons original may be patched.

I recommend making safetynet fix modules closed source to make it harder for google to patch, but that's just me.
[Magisk] pndwal:
Official USNF has been failing most users with at least intermittent failures since last release... Maybe you were just lucky, maybe Pokemon increased check...

As far as Google is concerned, I doubt they're responding to USNF bypasses, but they are continually adjusting their implementation, mainly adding new prop based hardware-backed attestation enforcements for newer devices that have so far been easy enough to bypass but must be added to USNF...

Even if closed, USNF would be among the simplest pieces of code for a Google reverser to understand, and they wouldn't even need to reverse it to add new enforcements...

Google aren't worried about USNF or this 'White Hat' community... And the banks can use strongIntegrity if they're worried whenever they wish thanks to Google! 🙃 PW
[Magisk] immortalwon:
Use hide my app list lsposed module.

Good points but it doesn't hurt to be on the cautious side, no? Make them work for their money is my motto.

Also, it seems they have strengthened their integrity checks for device and basic because sometimes it fails, sometimes it passes. It is not consistent. Hopefully @Displax can figure out a solution to this inconsistent passing.
[Magisk] v.konvict:
Hide my list lsposed doesnt work with 8ball pool as well
[Magisk] immortalwon:
You're right just tried it myself. The app might be detecting debugging mode or bootloader integrity
[Magisk] pndwal:
Still dont think it's a recent Google change...

2.4.0 was largely about a new "way to bypass Play Integrity that doesn't require spoofing the build fingerprint permanently... Just like the original goal of Universal SafetyNet Fix, this minimizes adverse effects by spoofing dynamically at runtime only when necessary"...

Read 'a new way to bypass Play Integrity that spoofs the build fingerprint part-time... Just like the original goal of Universal SafetyNet Fix, this minimizes adverse effects by spoofing dynamically only at gms runtime'...

However, this was released badly broken and still is.

@Displax has built a couple of fixes for the issues with part-time spoofing, and it seems to work for most users, but it may still not be working for all...

Assuming you are not using a custom rom that integrates SNF or other spoofing for integrity verdicts which can also cause issues, I'd try reverting to @Displax's v2.3.1-MOD_3.0 which predates the fraught @kdrag0n build fingerprint spoofing method and was also working well for most...

@Displax may have some better ideas... it's now knock off time in Kyiv (for some). PW
[Magisk] Displax:
Custom MIUI/Xiaomi Eu - basically they are the only ones harmful ROMs left that override PROPS from my MOD.

Something in these firmware constantly and aggressively changes variables and does it wrong. So the developers of such stupid firmware should fix it.
[Magisk] pndwal:
Thanks for this excellent information!

Seems @immortalwon has a OnePlus device however(?)... A different issue perhaps? PW
[Magisk] mindtrappergr:
Indeed. What is interesting is that in latest stable version of Xiaomi EU your 2.4.x version works great. But in all dev builds, after February, it fails. 2.3.1_mod3 works fine though.
[Magisk] immortalwon:
I think I fixed it. I cleared playstore and play services storage and cache. Installed play integrity fix lsposed module and now it never fails. Removed UNSF module as well.
[Magisk] m0han:
Update FYI: To make it work one might have to flash Audio-Modification-Library_v4.2_(57).zip also. I did and the latest v0.3.0 works now.
[Magisk] pndwal:
You don't need AML; just need to force Neon driver to reset...

With legacy mode selected, disable the module in Magisk and reboot. Enable the module and reboot again. Check Driver status = Normal. Volla!.. PW
[Magisk] droidman1992:
Did anyone test this module with the new Magisk version 26.1 which has a new version of Zygisk, I would like to upgrade my Magisk, however, I don't want my SafetyNet to trip up and want to ensure the module works.

I'm running Lineage OS 20 Official (Android 13) on my OnePlus 7 Pro.
[Magisk] rogers11:
On my Pixel 4a it works like before.
[Magisk] dagey:
I got it to work by uninstalling and downgrading to a previous version 5.11.2 that I grabbed from apkmirror. Not sure if I'm allowed to post the apk here but this is the link:

8 Ball Pool 5.11.2 (arm64-v8a) (Android 4.4+) APK Download by Miniclip.com - APKMirror

8 Ball Pool 5.11.2 (arm64-v8a) (Android 4.4+) APK Download by Miniclip.com - APKMirror Free and safe Android APK downloads

www.apkmirror.com
[Magisk] pndwal:
Moved this here:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-88420495 👍 PW
[Magisk] fkofilee:
Anybody a Starling Bank User? With the latest update on P7P to the App and Base OS - I can no longer hide my root. Doesnt matter what I do and it is still being detected.
[Magisk] giociampa:
I had the same issue - if you block access to firebaseremoteconfig.googleapis.com (via Adaway or similar) then it works again

(I found this on this post)
[Magisk] immortalwon:
Well, after disabling and removing the old magicpropsconfig hider 6.1.2, the discontinued version, safetynet and play integrity are passing 3/4 of the time. It could go the whole day without failing and then mysterious fail for no reason. Other then that, displax PI bypass mod is working as intended.
[Magisk] pndwal:
You could try this earlier, pre-runtime-only spoofing (2.4.0, ie. part time spoofing), @Displax modded build:

https://github.com/Displax/safetynet-fix/releases/tag/v2.3.1-MOD_3.0

It apparently worked for this user:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/post-88411445

👍 PW
[Magisk] immortalwon:
Will test this out for a few days and report back.
[Magisk] Spartacus500:
Test Android 9.0 Pie Samsung NFE

SafetyNet Fix v2.3.1-MOD_3.0

MEETS_BASIC_INTEGRITY ✅

MEETS_DEVICE_INTEGRITY ✅

Today update

SafetyNet Fix v2.4.0

MEETS_BASIC_INTEGRITY ✅

MEETS_DEVICE_INTEGRITY ❌
[Magisk] Tomek0000:
Spartacus500

You used mod version , as replacement please use 2.4 the mod version too.​
[Magisk] JSilver2021:
Working on LOS 20 with Magisk 26.1 and Displax's USNF v2.4.0-MOD_1.2.

YASNAC all Pass!
[Magisk] shoey63:
Don't update from Displax mod version.

It will put you on broken official version.
[Magisk] Zaxx32:
My details:

Pixel 6a

Stock A13 w/ April update

Magisk 26.1 root and 26.1 app

Am I correct to use safetynet-fix-v2.3.1-MOD_3.0?

and do I use V4A FX 0.3.0 module (1.15MB) w/ 0.3.0 app in legacy mode

or the V4A FX-repackagedhoch63 (81.8MB) w/ 0.3.0 app that I seen posted as working? I noted the huge size difference...oO

Think it's 0.3.0 w/ 0.3.0 iirc...I think I've confused myself by reading waay to many posts that don't apply to my setup + severe sleep deprivation. 😟 😔

TIA! ...2 B continued AFTER some sleep!
[Magisk] Nergal di Cuthah:
Probably should upgrade to 2.4.0 mod 1.2 it starts the spoof earlier than 2.3.1
[Magisk] pndwal:
Try that if you have issues with safetynet-fix-v2-4-0-mod_1-2... Many don't...

Either should be fine... Repackaged may set up more easily...

However if driver status in original module shows Abnormal just force it to reset thus: enable Legacy mode, disable module in Magisk app, reboot, enable module in Magisk app, reboot again and check driver status... All should be good...

Sleep well, PW
[Magisk] richardmace:
Fixed the Google wallet issue for me.

I'm on Magisk 24.1
[Magisk] Lughnasadh:
You'll likely have to use the V4A 0.3.0 (Re-engineered) module and app (in Legacy Mode). The hoch63 version probably won't work for you given your device and Android OS version.
[Magisk] immortalwon:
Posted this in the P.I integrity thread, sorry to double post about this again. No one bothered to respond.

Can someone help me bypass this root detection of my credit card app?

https://play.google.com/store/apps/details?id=io.ionic.access&hl=en_US&gl=US - Card access app

It recently started crashing, means they are detecting something from magisk and/or modules.

Magisk Alpha 26.1

List of modules:
[Magisk] Zaxx32:
Gotcha...hoch63 is out!

And I should go w/ safetynet-fix-v2.3.1-MOD_3.0 for integrity

if I recall correctly...correct? Thx again brother! 🍻
[Magisk] zgfg:
Sorry, cannot test - screenshot
[Magisk] Lughnasadh:
Displax's v2.4.0-MOD_1.2 should work for you.
[Magisk] Zaxx32:
Lmao....gotcha and ty! I'm about to fall out...😴😴
[Magisk] paddymcg1:
This just got Google Wallet working on my Redmi Note 10 5G on MIUI 14! 😁 Thank you so much, my phone feels complete now! 😁
[Magisk] m0han:
Did that a few times. No go. All good with 'AML flashed and rebooted'. Just an FYI for folks like me.
[Magisk] chiteroman:
Lol, this is interesting. I need to check it.
[Magisk] immortalwon:
If I was you, I would spoof custom device props using the new rom your using to see if you still pass strong integrity. Find out from the rom developer what exactly it spoofs, then use magicprops config to change them manually. I imagine it's closed source, and he will refuse to state the changes.
[Magisk] chiteroman:
All ROMs I installed fail STRONG because it fails DEVICE, the exception is xiaomi.eu that already include some patches that pass DEVICE (they included a spoof).

Well, I don't like the stock rom of my phone, so I will stay in xiaomi.eu (it's the most stable).

Passing Strong isn't expected but I won't change rom, as long as it works I won't touch anything XD.

Yes, if they do it open source, Google maybe can patch it.

Conclusion, the xiaomi.eu rom is the only one with which I can pass the Strong, the AOSP rom as ArrowOS force the evaluationType in BASIC and with that I can not pass the Strong.

The stock rom does not pass the Device by default, it may detect that my bootloader is unlocked and make it always fails.

So I'm not going to make a big deal out of it, I just got lucky and we'll see what Google's verdict will be. I hope they haven't seen my first images I sent where you could see the model of my phone...
[Magisk] chiteroman:
We'll see what Google does in the future, whether it will force the use of Strong for certain things or whether it will just stay there with no use at all. But I fear that certain apps like banking or even games will use it as an anticheat, for example, games like Pokémon Go require you to pass SafetyNet. In June next year we might meet again in this thread XD.
[Magisk] SoundDrill:
Solution is to have backup systems. Relying on a modded phone is kinda asking for it.

Glances at my rooted bacon with lineage 18.1 that I main.

Regardless: A good solution might be to carry cash, as a backup.
[Magisk] kevinco1:
If you don't trust Google and Wallet with your data (?) then why not just use the original debit/credit card you added to wallet itself to make online purchases?

With that option you cut Google from the whole process and you're just using your bank for purchases without any third parties

If you're at a brick and mortar and wallet isn't functioning then try the already mentioned cash or your debit card. I'd never leave the house with just the option to pay with wallet, life is unpredictable
[Magisk] Marianxs:
For now Google Wallet is stable on the S23 Ultra. But to be secure i have cash on me.

I ment i dont thrust Google with that they change apps so they wont work in future.
[Magisk] SoundDrill:
Absolutely, good choice.
[Magisk] dagey:
I'm having a lot of trouble figuring out what is causing my play integrity api check to fail all 3 check. No matter what steps I take, the integrity API check always returns that the test is UNEVALUATED. I've tried on a fresh install with only the safetynet-fix mod v 2.4 & 2.3, I've tried with Magisk 26, 25, as well as the debug release with su.d whitelist.

I am using CrDroid on Android 13 Moto Stylus 5G 2022, my data is encrypted and by default at boot selinux is set to permissive. I always correct selinux, clear the play services cache & data, I've ensured that zygisk is enabled with Magisk 25/26 and ensured that no services are checked in the hide list. I've gotten other checkers like momo to get as far as only showing errors regarding a custom rom & broken tee, but I'm not sure how to get past those issues. I tried with magisk props, and that also did not help. No matter what settings I set or state of the ssytem, the integrity API check always returns UNEVALUATED.

Does anyone have any ideas or suggestions?
[Magisk] zgfg:
Do you have GApps, particularly Google Play Services and Internet connection?
[Magisk] dagey:
Yes I have standard gapps along with play services and play store. I have WiFi and a data connection.
[Magisk] runekock:
When your rom runs permissive, it's probably because the dev knows that things break if selinux is enforced. Selinux relies on a wealth of policies that tells what's allowed, and if the rom doesn't have the right policies, no good can come from enforcing them.

I suggest you look for a rom that supports enforcing selinux. Or maybe work with the rom-dev to create the right policies.
[Magisk] toketin:
Hi, I'm on Lineage 20 on OnePlus Nord, I confirm that installing this module and on Magisk Manager enabling Zygisk + Enforce denylist (Revolut and Google Wallet enabled) I have Google Wallet working fine!

Thanks!
[Magisk] immortalwon:
It's been about a week. v2.3.1-MOD_3.0 is working quite good. I also had to re-configure adguard, maybe it was causing connectivity problems to play integrity servers @pndwal
[Magisk] Virnik0:
Hello, both oríginal as well as MOD version of SafetyNetFix works for all apps, but Google Wallet detects root few hours after setting everything up. Can be fixed by wiping GMS data, Google Play Framework and Google Play Services data and rebooting, but then few hours later, Wallet detects root again. Play store says that device is Certified and SafetyNet Checker also says that the device passes SafetyNet. Using Magisk 26.1 rooted Galaxy S22 (Exynos). Any tip what I may be doing wrong? Zygisk enabled, Magisk Hidden, GMS, Play Store, Play Services and Play Services Framework are in Deny List and Deny List is enforced.
[Magisk] immortalwon:
Use magisk alpha, at your own risk, with their custom shamiko. I would also firewall magisk alpha incase they have included any backdoors to CCP servers. I have been passing safetynet for and wallet for weeks now.
[Magisk] Virnik0:
Sorry, this is the first time I hear about Magisk Alpha or Shamiko. I am using Magisk for years now. Strange thing is that my wife has the same phone, but her stock rom is from January, my Stock from end of April. Her Wallet warns about integrity randomly, but payments works. In my case it works after setting it up, but later stops working.
[Magisk] Virnik0:
OK, so after few hours, Google Wallet fixed itself while using this MOD without wiping gms data (if I'd wipe it, I would have to reset/repair my watch). Awesome. Thank you!
[Magisk] immortalwon:
be specific, which version of the mod?
[Magisk] Virnik0:
safetynet-fix-v2.4.0-MOD_1.2.zip

It took it exactly 12 hours to fix itself. Enforce Deny List is off (must be)
[Magisk] matrix200200:
Today wallet stopped working (phone doesn't meet security requirements).

The phone is Galaxy S10E with LOS 19.1.

Currently using magiskhideprops and original kdrag0n safetynet fix.

Should I attempt installing mod instead?
[Magisk] pndwal:
You're everywhere man!

Yup, disable global fingerprint setting with MHPC and just install this USNF with fixes... 👍 PW
[Magisk] matrix200200:
I am a bit confused about the need to disable the hideprops.

Is it necessary?

In other words, do I need to revert the changes, then uninstall the hideprops, uninstall the safetynet original, install this one, install hideprops again and apply the required props changes?

Or can I just uninstall the original safetynet and install this one?
[Magisk] matrix200200:
OK I reset fingerprint (as per your recommendation, disable MHPC completely afterwards, removed the old module and installed this one.

And wiped GMS.

So far Wallet shows as functional again.

Hopefully it stays that way.

Just to understand, I don't need hideprops with this updated module, correct?
[Magisk] zgfg:
yes, that's the point
[Magisk] pndwal:
USNF now does targeted (to gms processes only) fingerprint prop spoofing, so there's no point using (the more invasive and problematic) MHPC global fingerprint spoofing...

USNF also sets other props needed to bypass hardware-backed verdict enforcement by Google (server end) for some devices, so for practically all devices prop changes needed for passing Play Integrity deviceIntegrity verdict are handled properly by USNF, and this mod fork addresses several other issues with the new part-time hiding mechanism, timing etc...

You may want to use MHPC prop spoofing for other purposes, but disable any S/N or PI related prop changes unless USNF is simply not working...

🤠 PW
[Magisk] matrix200200:
So far so good.

I even went to a bakery place and bought some brownies for testing purposes :LOL:
[Magisk] brambles1234:
Google wallet has stopped working for me. Banking app as work fine.

I disabled the MHPC and installed this mod fix 2.4.0-MOD_1.2. However Google wallet still says device doesn't meet requirements?

My set up

Lsposed 1.86

Shamiko 0.71

Xprivacy Lua

Magisk Hide Props 6.1.2

Seemless host 1.0

Universal Safety fix 2.40

I tried changing finger prints yesterday but still fails
[Magisk] Noweir:
InstaPay Egypt - Apps on Google Play

With InstaPay, Transfer money instantly 24/7, and pay your bills.

play.google.com

this app was working perfectly version 1.5.5 with shamiko and your mod but after app update 1.5.6 not working any more whatever i do.is there anyway to fix it
[Magisk] Devtick.:
Do you need to block certain google services from magisk DenyList, and if so which ones?