yashsingh1/xdaforums huggingface dataset:
[Android Software Development] antonioxerez:
Let me jump into this as well.

I have 2 banks app. One works OK just with Zygisk hiding.

The other one (ING Direct) does not. I have tried with Displax fork and it allows me to go further than without it (it asks me user credentials) but, when it is about to showing my homepage it gives me the same error than without this module...

Do you think this could be because I need to wait for an update of this safetynet fix? Or there is something else I can try?

Thanks in advance!! :)
[Android Software Development] chiteroman:
Try to hide Magisk app, install Shamiko (you must disable enforce deny list) or use Magisk Alpha
[Android Software Development] antonioxerez:
Thanks, I have just tried with no success.

I have Magisk 26.1 hidden with other name, modules Shamiko 0.7.2 and denylist disabled but in the list, the bank app marked.

And I have tried 3 scenarios:

- With Universal Safetynet fix module 2.4.0

- With Safetynet fix module 2.4.0 mod 1.2 (by kdragOn)

- With no safetynet fix module installed

But with no sucess :(

What about Magisk alpha? How can install it? Do I need to uninstall the current one before? Something to be done from fastboot or just apk installing like other apks?

Thanks :)
[Android Software Development] chiteroman:
To install Magisk Alpha you need to download apk and install it, gives it root permissions and install directly from the app. After the reboot you can uninstall older Magisk app.

Or you can completly uninstall Magisk and install Magisk Alpha using TWRP.
[Android Software Development] antonioxerez:
THanks, when I install it and select "install from app" it asks me for an img or tar file.

I suppose it referes to boot.img but I do not have this boot.img from rom/firmware. I have one that already was patched with Magisk v26 ... I suppose I can not use that, right? do you know how to extract boot.img or if I need another file and not boot.img?
[Android Software Development] immortalwon:
just rename magisk.apk to magisk.zip, flash it via custom recovery and boot into android OS. Open magisk app and click direct installation. Flashing the magisk.zip from recovery gives you temporary root until you direct install.
[Android Software Development] antonioxerez:
mmmm, I think root permissions is not the issue because I have granted root permissions to alpha Magisk.

Anyway, about flashing a zip from my recovery I think is not possible... I have LineageOS recovery, not TWRP. The only option I have is "sideload files". I think this is not the same or will it work the sameway if I rename the apk to zip and sideload it through recovery?

Thanks for answering
[Android Software Development] immortalwon:
You could sideload a zip, yes. Should work the same way as sideloading in TWRP.
[Android Software Development] antonioxerez:
Thanks a lot, it finally worked with Magisk alpha so, because it has worked this way, I tried to uninstall magisk alpha and normal magisk and reinstalling normal magisk and it is working as well without any module installed ... so I do not know what happened in the first place... could be that it just needed to make the initial bank app start without rooting and, after this first start, root the device and apply "denylist" in Magisk...

Thanks all of you for your support :)
[Android Software Development] chiteroman:
The real question is why are you using LineageOS recovery, do you have that ROM? I don't recommend LOS because it doesn't "hack" to bypass detections, use this module to hide LOS: https://github.com/Magisk-Modules-Alt-Repo/sensitive_props/releases/latest
[Android Software Development] antonioxerez:
sorry, I thought I had LineageOS recovery but it seems I have "PixelOS recovery" (that could be is the same, because the interface is exactly the same than LOS recovery...)

P.S. I tried that module as well with no success... anyway, I finally have bank app working :)
[Android Software Development] Essentrix:
Hi,

I can pass safelynet on YASNAC but not Play integrity API checker.

Most bank apps work except one.

Currently using Magisk 26.1, hidden, no enforce list, Shamiko, USNF 2 4.0 mod 1.2.

Noticed you mentioned Magisk alpha. How is this different to Magisk 26.1 and can I go back to 26.1 afterwards if it makes no difference?

I'm using rooted stock 13, no TWRP.
[Android Software Development] Nergal di Cuthah:
Alpha is a cutting edge fork of magisk that tries things before john wu maybe adds. It is not made by wu, but developed by prolific contributors of magisk.
[Android Software Development] chiteroman:
It's closed source and use an undetected Zygisk, you can reinstall original Magisk if you don't like Alpha. Also there are 2 Magisk "alpha", the official (called Magisk Canary) and the vvb2060, the good one is the vvb2060 Magisk. You can download it from his Telegram: https://t.me/s/magiskalpha
[Android Software Development] Mowca:
Hello

I haven't been able to pay over the phone for a few days.

Yasnac fails "cts profile match" test.

How to solve this problem?

Samsung s10e.

Lineageos 18.1

Magik 23.0

modules:

MagiskHide Props Config v6.1.2

Universal safetynet Fix v2.4.0 by kdrag0n
[Android Software Development] Essentrix:
Thanks for the feedback. Do you think its likely to improve my chances of passing safetynet with play integrity API checker?
[Android Software Development] chiteroman:
Magisk Alpha is only required for some apps that detect official Magisk zygote injection. You should pass Play Integrity (device and basic) with official Magisk.

Send screenshot of PI result.
[Android Software Development] pndwal:
Alpha works because after disabling Zygisk (which you need to do ATM) you have MagiskHide (old style) restored...

You need to hide root from Starling but you cannot use Denylist or Shamiko as both require Zygisk, and even with native bridge loaded Zygisk (already implemented in Alpha, but still not fully hidable as is evident by Starling detections) injection/hooking is detected by memory scanning (or other means?)...

Some have reported that Starling app gives you a week's grace from when it detects root until it fails to open... Just a guess on my part, but you may need a non-Zygisk hide solution again when/if that occurs.

🤠 PW
[Android Software Development] Essentrix:
Here's my results for both
[Android Software Development] pndwal:
Disable MHPC... Say if LOS is official or unofficial... ensure you have no mods like selinux switched to permissive flashed from custom recovery... Test with all Magisk modules disabled also, except latest @kdragon USNF... 👍 PW
[Android Software Development] Essentrix:
Thanks for the detailed feedback. As you'll see in my feedback to another post, I have mixed results with the current setup.

Not sure of the best way forward.

Still appreciate access to you guys; you're quite an amazing wealth of knowledge!
[Android Software Development] pndwal:
Please see my reply above to @Mowca...

Please say device, Rom, what mods/modules you have etc...

One thing to note (often causing issues like yours), - passing ctsProfileMatch with basic attestation has been superseded by deviceIntegrity, but requirements have also been heightened, eg you can no longer run without security enhanced linux, ie. with permissive selinux, so ensure you use current modules for mods like Viper4Android that don't alter system security, and that any custom ROM is properly set to enforce selinux. ROMs should only be released to public with selinux working... Permissive disables many requirements for development/testing purposes only; if a rom relies on permissive selinux it's half baked and insecure.

No.

🙂 PW
[Android Software Development] chiteroman:
WTF, I never seen that. If you pass Safetynet, you must pass basic Play Integrity... Maybe SELinux problems? It's interesting.
[Android Software Development] pndwal:
Native bridge loading should make Zygisk properly hidable just like N/B-Riru, and it works for many apps that previously detected Zygisk already. My tests and info. here:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-88467665

and in following post...

However it seems that Starling is still able to detect Zygisk, so looks like either more work needs doing on core Zygisk loading etc, or Shamiko (LSP Zygisk companion hiding app) needs further improvement before Zygisk is truly undetectable... This seems to be the crux of the issue with Starling Bank...

I think John avoids calling Canary Magisk 'Alpha' partly due to the existence of vvb2060 Alpha fork, and to prevent confusion. 😬

... Her telegram. 😉 PW
[Android Software Development] Essentrix:
A52s 5G rooted stock

Magisk 26.1 no TWRP

Shamiko, systemless hosts,

USNF 2.4 mod 1.2

V4AFX 2.7.2.1 repackaged

Zygisk LSPosed

Corepatch

All latest versions
[Android Software Development] pndwal:
What's corepatch? PW
[Android Software Development] Essentrix:
Wow, I'm surprised it's something you guys haven't seen before.

Looked a little weird to me.

Still my most important bank apps work so not a big deal. Google wallet picks up root but don't really need it.

Thanks for being such a great resource. Open if you have any further thoughts.

A LSPosed module
[Android Software Development] pndwal:
I've seen it. Cause was permissive selinux; we can pass SafetyNet (basicIntegrity and ctsProfileMatch) with that but not PI basicIntegrity... This additional requirement would probably have come to S/N except that it's superseded by PI, so this API got the stricter basicIntegrity requirement...

I don't yet know of other reasons (enhanced requirements) however, but it's likely there are others.

Try this: disable all Magisk modules, reboot, clear Google Play Services data, enable only latest @Displax USNF, reboot and check again...

Also, check selinux (in terminal emulator type getenforce with su) and in Play integrity API Checker click <> at top and screenshot raw JSON response... PW
[Android Software Development] zgfg:
SafetyNet-fix (at least 1.1.1) does not include uninstall.sh script, hence remove file will do just the same as if you delete its folder (or put disable file).

Btw, xou can check if there is the uninstall.sh file in the folder (same folder where you put remove or disable files)

However, this is pure systemless module, adding/replacing few ro.* props and few system files

Module does not replace them hard way - it gives to Magisk and Magisk mounts the changes on every reboot.

Once the module is deleted or disabled, there will be no mounting and hence no more the changes on next reboot(s)

Therefore, it must be something else - some system app does not like the changes when they are active, it caches/saves what it finds and even when you remove/disable the module it still remembers

You could try wiping the Cache
[Android Software Development] BrimoFan123:
Thank you for your explanation.

Could you please how to wipe the Cache in adb? Or should to boot to recovery and do that from there (if there is an option to wipe only cache) ?

EDIT1: No, there is no uninstall.sh in /data/adb/modules/safetynet-fix

EDIT2: In Recovery there is Wipe Cache action so I pressed it but still PIN doesn't unlock my phone :-(
[Android Software Development] zgfg:
There is an option in TWRP - Wipe / Advanced / select Cache / swipe to wipe

For stock Recovery it depends what they included or not, you should try on your device

For wiping cache by adb I don't know - when I need I use TWRP
[Android Software Development] BrimoFan123:
Already did Wipe Cache in Stock recovery - still the same: PIN doen't unlcok the phone, juest is going back to present logon screen, no information that the PIN is wrong (because is correct one)

Any other suggestion?

I have adb root access so it should be possible to fix it.... I can't believe it isn't a solution for this issue.
[Android Software Development] BrimoFan123:
What is the file keystore in /data/adb/modules/safetynet-fix/system/bin/ ?

I have pulled it to local machine and its 484 KB file with some crypted content.

I have renamed this file and still nothing in all scenarios: with patched ramdisk, with stock ramdisk, with "disable" file present or missing... I'm out of ideas now.
[Android Software Development] Dante63:
Recreate your pin and fingerprints, if you noticed, you can unlock your phone without fingerprint or pin, as if you don't have any, in settings it shows you have, remove fingerprints, settings will crash, lockscreen will change into none, reboot your phone and change lockscreen to pin or whatever, then add fingerprints and change your lockscreen to fingerprint, you might struggle, might crash few times, once you're done, it should work but many apps will fail to call biometrics...
[Android Software Development] psiphiguy:
Interesting, I've installed the module in Magisk, rebooted, and it is NOT working on my OnePlus 8 Pro (OOS 11.0.2.2 with Android 11)

Attestation still fails for basic.

Ideas?
[Android Software Development] BrimoFan123:
I can't unlock the phone at all.

When locksettings.db is renamed phone indeed is not asking for PIN or fingerprint but it is not booting.... there is constant message "Phone is starting" only .
[Android Software Development] Dante63:
Try swipping on the screen, don't go for pin or use your fingerprint... just swipe... that's how my phone worked
[Android Software Development] BrimoFan123:
Exactly this is what I'm doing: after the reboot I swipe the screen and "Phone is starting"

I think this is because I have encrypted enabled so when I renamed locksettings.db to locksettings-bad.db then the LineageOS can't be started because PIN or fingerprint is needed to decrypt.

I still don't get why correct PIN doesn't work (when I rename back locksettings-bad.db to its original name) Im sure it is correct because when I type it I'm not getting a message "Wrong PIN" but phone's screen is just return to lock screen.
[Android Software Development] Dante63:
Keep things as they are originally and try the swiping or choose camera if you have the shortcut outside or access settings from above, don't go for pin or fingerprint because the don't match the security patch anymore
[Android Software Development] BrimoFan123:
Unfortunately I have no camera shortcut on the lock screen but whatever I choose on lock screen, for instance: Emergency information and select Edit it always invoke PIN for input.

But as I have wrote previously: I have adb root access so it should be possible to do something at this level of permissions directly but this is out of my knowledge.
[Android Software Development] Dante63:
I suggest to rename or (backup&delete) the following,

locksettings.db

locksettings.db-shm

locksettings.db-wal

Gatekeeper.password.key

Gatekeeper.pattern.key

Hopefully this will remove everything...
[Android Software Development] zgfg:
IDK would it help but you can try to boot into Safe mode, then maybe you could do something (?)
[Android Software Development] BrimoFan123:
I checked with renaming those files and folders already:

/data/system/locksettings.db

/data/system/users/0/settings_fingerprint.xml

/data/system/users/0/fpdata

PIN pattern doesn't appear but swiping screen cause constant "Phone is starting"

I have no other files what you suggesting (at least not in /data/system/)
[Android Software Development] BrimoFan123:
There is no Safe mode for my device Huawei Mate 10. I was searching for it some time ago.
[Android Software Development] zgfg:
And you tried Wipe cache from eRecovery:

- connect to charger

- press and keep pressing Vol+

- boot (while keeping pressed Vol+)

Then choose Wipe cache or so
[Android Software Development] BrimoFan123:
In Huawei eRecovery there are only those actions available:

Download latest version and recovery

Wipe data/factory reset

Reboot

Shutdown

In Recovery I did already few time Cache Wipe
[Android Software Development] zgfg:
Ok, it was time ago when I played with their two recoveries and never know about those wiping options

Anyway, you could also try Download (install) latest - it shall not do Factory reset (unless you take it) but I cannot guarantee would it fix.

Upon reinstalling, you will need to root again

Btw, are you on EMUI 8 or 9 (i.e., do you install Magisk to Ramdisk or eRecovery)?
[Android Software Development] BrimoFan123:
I'm running LineageOS 16.0 Build 6 which is EMUI 8 based ROM so I patch RAMDISK.img with Magisk.

I'm in dialog with OpenKIRIN guys on Telegram so maybe they will suggest something more.

Personally I'm thinking also about to flash again LineageOS 16.0 Build 6 as SYSTEM.img but I don't know if that fix the issue as I don't know exactly what happened that correct PIN nor fingerprint doesn't unlock the phone.

If that will not work I will also try "Download latest version and recovery" in eRecovery as you suggesting.
[Android Software Development] Essentrix:
Thanks for the update. Made some progress...
[Android Software Development] pndwal:
Please say what you did... PW
[Android Software Development] Essentrix:
Hi, followed your thoughts and cleared Google Play Services data.

Also remembered I had a modded Google Play. Went back to original.
[Android Software Development] immortalwon:
Has anyone figured out how to bypass 8 ball pool & or KFC app usa root detection?

8 Ball Pool - Apps on Google Play

Play online multiplayer or PvP Pool games and compete with your friends!

play.google.com

KFC US - Ordering App - Apps on Google Play

KFC-US Mobile App

play.google.com

How the device is rooted:

Magisk Alpha 26.101

Shamiko latest --------> GP services, playstore, framework on deny list including KFC & 8 Ball pool.

Hidemyapp list

What could these 2 apps be detecting???
[Android Software Development] missionman:
I updated module to V2.4.0 but im still getting CTS Profile Match Fail.

Pixel 7 Pro, Android 13. Rooted usinng Magisk 26.1

How do I get CTS Profile Match to pass?

I got a Pass on Device Certification, its just the CTS fail.

It also says HARDWARE_BACKED under Evaluation Type instead of BASIC like it should says if it passes.
[Android Software Development] zgfg:
2.4 0 from this thread (wrong) or the proper 2.4.0-mod_1.2 from another thread

If needed, please spend 5 minutes to read last few pages here...
[Android Software Development] rg_gapa:
I know how difficult nowadays is to pass SafetyNet / Play Integration, but maybe there's still something obvious that I'm missing, so I'm looking for advice.

I pass verification at my OnePlus 7T with LineageOS 20 and below, pretty common as I guess, configuration:

- Magisk 26.1

- hidden Magisk app

- Zygisk enabled (without Enforce DenyList)

- DenyList configured for Google Play Service, Play Store, Applist Detector, TB Checker, YASNAC, hidden magisk app, banking apps etc.

- Shamiko 0.7.2

- Universal SafetyNet Fix 2.4.0

- Zygisk LSPosed 1.8.6

- Hide My Applist configured for the same apps as in Magisk DenyList, to hide LSPosed and all root apps

By passing verification I mean:

- SafetyNet Basic + CTS in YASNAC

- All tests in TB Checker (Play Integrity, Root Check, Xposed Check)

-- without SafetyNet Strong integrity and Virtual integrity

- All tests in Applist Detector

So that's great, right? However, if I left device for some time and re-run YASNAC CTS is failing. But If I'll run TB Checker and run tests there, everything is OK back again. After this even YASNAC once again shows passed CTS profile!

This random losing of CTS (until re-running TB Checker) confirms in daily usage, as some apps like banking one are randomly loosing ability to use fingerprint authentication or contactless payment. After running TB Checker and passing CTS once again I might add these payment features back to normal, so it's more like an annoyance than serious problem.

I've tried to reset Google Store/Services/Wallet data and adding some additional Magiks modules related to hidding props but this didn't change a thing, CTS is still failing from time to time, at random moments.

Do you have similar problems? Is there anything I might try to do, or maybe there're some ways to detect which activity at my phone is actually making CTS failing?

Edit: That might be useless post, I just discovered USNF v2.4.0-MOD_1.2... trying it out now.

Edit 2: Works perfectly lol :D
[Android Software Development] sakun-ice:
Can somebody help me? I can't get past safety net. I have installed the xiaomi.eu rom on my xiaomi 13. I have Magisk 26.1 with Zygisk. I have installed the modules universal safetynet fix 2.4 mod 1.2 and lsposed. I have added to the deny list: google play services, google play and google play framework. I have deleted the data from those apps and from the bank apps. I have also tried to install the Alpha app instead of Magisk and to hide the magisk app from the settings. But nothing works.

The strange thing is that before installing the xiaomi.eu rom it worked.
[Android Software Development] zgfg:
Xiaomi.eu ROMs can pass Play Integrity (once again, PI is now of interest, SN is deprecated, and if you pass PI you will also pass SN) since they have the spoof built-in

Cannot guarantee for all Xiaomi.eunROMs

Hence, have you tried Play Integrity checker prior than you installed Magisk?

For PI, you should pass Basic and Device Integrity but you cannot pass Strong Integrity (with the unlocked Bootloader)

---

If you switch from Magisk official to Magisk Alpha or Delta, it is not enough (actually, it's then almost as if you did not switch) to install Alpha or Delta app, but after that you also have to install Magisk Alpha or Delta (like through the app, Install, patch and flash the boot img or Direct Install but after reboot you then also have to configure your Magisk Alpha or Delta)
[Android Software Development] gigavolthavoc07:
Guys how can i use this module in kernelsu?
[Android Software Development] Nhatlienhoan:
OOS 13.1 on Oneplus 9 fail every safetynet with USNF 2.4.0 mod 1_2. Tried denylist, zygisk and all I used before and worked now don't. Please help and suggest solutions.
[Android Software Development] immortalwon:
Install latest shamiko module. Add google play store, google play services, google services framework to deny list. Clear all app data of above mentioned services and reboot and check again.
[Android Software Development] pndwal:
Disable all modules except USNF and try... Clear Google Play Services data too... If no dice, try older @Displax v2.3.1-MOD_3.0... 2.4.0 changes (part time spoofing etc) still cause issues on some devices and modded 2.3.1 works better for many... 👀 PW
[Android Software Development] Nhatlienhoan:
None works so far. :(
[Android Software Development] immortalwon:
Show us a list of which modules you are using with magisk
[Android Software Development] Nhatlienhoan:
Acc, shamiko (from your suggestion), systemless hosts, USNF 2.3.1 mod 3.0 (tried 2.3.1 mod 2.1 and 2.4.0 mod 1.2), v4a re 0.5.0, zygisk LSPosed.
[Android Software Development] immortalwon:
Ok now what settings are configured in magisk? Go to the deny list section, take some pictures, etc.
[Android Software Development] Nhatlienhoan:
View attachment 5925703

I notice that google framework auto uncheck everytime I open Magisk. Plus Google Play crashed when I clear data of G.Framework, so I restored it from my backup.
[Android Software Development] immortalwon:
You have to restart after clearing the data (not cache, all data) of G.play services, g play services framework, and g play store. Make sure "enforce deny list" is not enabled. It should work and it's also normal for the framework to disable itself, I just do it for good measure. Try again and report results. Don't worry about the crashes, it should be normal after a reboot. Make sure not to accidently uninstall any app updates as that will break the device sometimes.
[Android Software Development] Nhatlienhoan:
I got "Error retrieving information from server. DF-DFERH-01" message in Play store after restart.
[Android Software Development] immortalwon:
force stop play store, clear cache, make sure you are logged into to your gmail account and re-open play store
[Android Software Development] Nhatlienhoan:
Still that Error. (That's the reason I restore Framework data)