Related
OOS 10.0.1
Magisk v20.1
EdXposed v0.4.5.5
SafetyNet first works and after some time it fails both ctsProfile and basicIntegrity
I also tried Magisk Hide Props Config
Same problem on my 6t. Still trying to find a solution. I fear that Gravitybox may be the culprit. Do you have it installed?
https://github.com/ElderDrivers/EdXposed/issues/386
Edxposed no longer passes Safety Net by default. You need to blacklist Google Play Store, Google Play Services and Google Framework as per this site.
Soumy1234 said:
https://github.com/ElderDrivers/EdXposed/issues/386
Edxposed no longer passes Safety Net by default. You need to blacklist Google Play Store, Google Play Services and Google Framework as per this site.
Click to expand...
Click to collapse
In addition try the hidden core module, works great for me.... No more safetynet issues...
kpmohamedhussain said:
In addition try the hidden core module, works great for me.... No more safetynet issues...
Click to expand...
Click to collapse
Thank you for recommending the Hidden Core Module! It works great on my OnePlus 7 Pro. After installing the module and blacklisting the Google Play Store, Google Play Services and Google Framework in EdXposed I was able to pass SafteyNet without a problem. One app (Mario Kart Tour) was still detecting root. I was able to get it working by clearing the cache and storage from the Play Store and Play Services and rebooting.
Be careful for those Edxposed modules which are not fully compatible to android 10.
Kris
Hirs_E_Fruit said:
OOS 10.0.1
Magisk v20.1
EdXposed v0.4.5.5
SafetyNet first works and after some time it fails both ctsProfile and basicIntegrity
I also tried Magisk Hide Props Config
Click to expand...
Click to collapse
I follow steps as link below and it works ! I can use Magisk + Edxposed and safetynet won't be crashed.(It would fail at every rebooting. Waiting for a while and it will pass safetynet check )
https://forum.xda-developers.com/pixel-4-xl/how-to/xposed-discussion-thread-t3992607
How does MagiskHide hide the bootloader status? I'm trying to find a way to replicate the same method with the latest canary release which has Zygisk instead of MagiskHide. Any help is appreciated.
It just changed a few props, all of which are integrated into MagiskHide Props Config (the "Edit MagiskHide props" option) and/or Universal SafetyNet Fix (which soon should be updated to work on Magisk build 23010+).
Didgeridoohan said:
It just changed a few props, all of which are integrated into MagiskHide Props Config (the "Edit MagiskHide props" option) and/or Universal SafetyNet Fix (which soon should be updated to work on Magisk build 23010+).
Click to expand...
Click to collapse
I just changed those props, it still fails attestation. It might be something different though, will check further. Thanks.
With Magisk Canary 23010 you'll also have to add the Play Services processes manually to the Deny list (gms and unstable). If you haven't done that, do so and try again. Could also be that you'll need to fool keystore to use basic attestation, but for those you'll have to use USNF v1.2.0 until the next release, since Riru doesn't play well with Zygisk.
Didgeridoohan said:
With Magisk Canary 23010 you'll also have to add the Play Services processes manually to the Deny list (gms and unstable). If you haven't done that, do so and try again. Could also be that you'll need to fool keystore to use basic attestation, but for those you'll have to use USNF v1.2.0 until the next release, since Riru doesn't play well with Zygisk.
Click to expand...
Click to collapse
Yeah, Riru apparently was the problem as when I removed Riru and downgraded Universal SafetyNet Fix ctsProfile now passes. Thanks for the aid!
Didgeridoohan said:
With Magisk Canary 23010 you'll also have to add the Play Services processes manually to the Deny list (gms and unstable). If you haven't done that, do so and try again. Could also be that you'll need to fool keystore to use basic attestation, but for those you'll have to use USNF v1.2.0 until the next release, since Riru doesn't play well with Zygisk.
Click to expand...
Click to collapse
Is there any update in 2022?
I'm using latest canary Magisk and latest USNF v2.2.1 on Android 11 but the unlocked bootloader is still detected.
Is there any solution? Thank you.
I've managed to hide root from the apps themselves by installing the Universal SafetyNet Fix and enabling Zygisk (Beta) and Enforce DenyList and adding the apps to the DenyList and I can use all the apps but now Play Store won't let me update Netflix or Revolut, as it says they're no longer compatible with my device.
I've now hidden the Magisk app, which hasn't helped, and I'm trying to install the Shamiko module from Telegram but if I choose "Normal Android Way" Magisk just closes and if I choose "File Way" it says "Unzip error". This isn't specific to the Shamiko zip though, it happens if I try to reinstall the Universal SafetyNet Fix zip.
I'm using the latest Magisk v24.1, although I notice that on the Home screen it says "Zygisk: No" even though it's enabled. The only other modules installed are Busybox, Call Recorder and Systemless Hosts.
EDIT: Nevermind. I found that this only happens when trying to install using ES File Explorer. If I use the default File Manager it works OK.
EDIT2: So I followed the steps here, from "Setup Fingerprint", setting it to Poco X3 NFC Global - Android 11, and cleared the data&cache for Play Store and Play Services and rebooted, and now the Play Store doesn't even show Netflix or Revolut, either in the list of installed apps or when I search for them. https://forum.xda-developers.com/t/rom-11-lineageos-official-surya-karna.4202533/post-84100067
EDIT3: I disabled "Enforce DenyList" and enabled the Shamiko (v0.4.3) module instead and rebooted and cleared the Play Store and Play Services cache again and now I'm back to where I was before, with Netflix and Revolut showing in the installed apps list (but not when I search for them) and unable to update as it says they're no longer compatible with my device.
EDIT4: Updated Universal SafetyNet Fix to v2.2.1 and used adb props to Force Basic Key attestation to surya (default value, was M200....). No change. Checking Safety Net with Root Checker says it fails.
Magisk 24.1, enabled Zygisk, enabled DenyList, added all Google apps to the DenyList. Renamed the Magisk package name.
Flashed kdrag0n's Universal SafetyNet fix, installed MagiskHide Props, enabled the surya fingerprint and forced basic attestation. All on LineageOS 18.1. Works fine, no issues so far. Didn't even need to clear data or cache for any apps, just rebooted the phone.
robogo1982 said:
Magisk 24.1, enabled Zygisk, enabled DenyList, added all Google apps to the DenyList. Renamed the Magisk package name.
Flashed kdrag0n's Universal SafetyNet fix, installed MagiskHide Props, enabled the surya fingerprint and forced basic attestation. All on LineageOS 18.1. Works fine, no issues so far. Didn't even need to clear data or cache for any apps, just rebooted the phone.
Click to expand...
Click to collapse
I'm using MIUI but I've literally done all of that and I still can't update Netflix or Revolut.
As explained by Lughnasadh here https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/post-86463103 we can't actually add Google Play Services to the DenyList, as doing so breaks USNF and it unticks automatically on reboot anyway. So I think all we can add to the list is Google Play Store.
doveman said:
I'm using MIUI but I've literally done all of that and I still can't update Netflix or Revolut.
As explained by Lughnasadh here https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/post-86463103 we can't actually add Google Play Services to the DenyList, as doing so breaks USNF and it unticks automatically on reboot anyway. So I think all we can add to the list is Google Play Store.
Click to expand...
Click to collapse
Why don't you guys simply stick to Magisk 23.0? Everything works fore with that version of Magisk
Noter2017 said:
Why don't you guys simply stick to Magisk 23.0? Everything works fore with that version of Magisk
Click to expand...
Click to collapse
I seem to have fixed this now by changing the device fingerprint from POCO X3 NFC Global to POCO X3 NFC Europe.
I have issues after the playstore updates. I can delete all data and at old version device is certified. But it updates itself and it's problem then on. Anyway to stop the playstore self update?
You could try Magisk's Detach module -- online repo is deprecated, but it is still around if you search for it...
I've had same issue about Revolut, I think Nerflix uses similar spies. but telling story short: I downloaded Revolut from ApkPure and cheched it on DenyList, reboot aaaaasaaaaaand it's all done, Revolut is getting updates and works as usuaully
I have zero interest in rooting my phone, but because 5G/VoLTE/VoWiFi are not supported in my country (Slovakia) I had to root it. After successful root, passing SafetyNet and pretty much make everything to work as expected, my Company Portal is detecting root when running Teams and Outlook provisioned by my Company Portal despite having them in DenyList. Is there anyone who managed to pass this?
Thank you.
Happened to me as well. I used Shamiko magisk module and it's all good now.
@chaos193, did you use Riru along?
Or maybe even better question if you don't mind - what modules are you using to successfully pass SafetyNet and hide root?
Can you list them one by one, please?
Either use Shamiko or MagiskHidePropsConf to mask additional properties. I can confirm that InTune Company Portal works fine with SafetyNetFix + Shamiko
p4ra said:
@chaos193, did you use Riru along?
Or maybe even better question if you don't mind - what modules are you using to successfully pass SafetyNet and hide root?
Can you list them one by one, please?
Click to expand...
Click to collapse
It's pretty much what @craigacgomez said. I used Shamiko 0.6 alongside LSposed zygisk release. I'm pretty sure LSposed is not needed but I have it just in case.
chaos193 said:
It's pretty much what @craigacgomez said. I used Shamiko 0.6 alongside LSposed zygisk release. I'm pretty sure LSposed is not needed but I have it just in case.
Click to expand...
Click to collapse
Quick question @chaos193 - I haven't updated Shamiko to 0.6 as the update states that it requires Magisk 25205+. Reckon that would be magisk canary? Or as you using 0.6 with Magisk stable?
WhoIsJohnGalt1979 said:
Quick question @chaos193 - I haven't updated Shamiko to 0.6 as the update states that it requires Magisk 25205+. Reckon that would be magisk canary? Or as you using 0.6 with Magisk stable?
Click to expand...
Click to collapse
I used it with magisk stable 25.2. I think we are all using magisk stable to root our phone right?
I have tried your suggestions, but still does not seem to work. Adding screenshots.
Can you help me, please? What is wrong with my setup?
Following steps work 100% - I had the same issue.
1. Use magisk canary.
2. Install universal safetynet fix MOD 2.0 from displax (Google for "displax github")
3. Use latest shamiko module
4. Activate zygisk
5. Don't enforce denylist
6. Go to denylist and chose all Microsoft apps and tick ALL options for each app.
7. Hide magisk app
I had issue with a specific banking app which detects root by most of the methods. I made it working by using shamiko + airfrozen which i was not really liking.
Now i wnded up with a forked project of magisk bu Husky called magisk delta which brought back magisk hide along with zygisk. With this i don't need shamiko, magiskpropshide, airfrozen or any modules for hiding the root from apps. Yes for safetynet you can use the modded veraion by D. Below is the link. If you are interested have a look at Magisk Delta by HuskyDG... I use the magisk delta canary builds...
I have made it work with first approach. I did a restart of the phone and it worked.
What I am wondering though is the following - I have used the VoLTE/VoWiFi/5G Magisk module, but I don't see the "HD" icon during the call, even though I can browse the internet (when I am not on WiFi). And despite 5G coverage of my current carrier in my area, I don't see 5G icon.
Is there any other module I am missing for this last piece of puzzle?
And last but not least. What scares me the most is that next OTA will completely screw me over after setting everything up. I wish there was a clear tutorial on how to OTA and keep the root without wiping everything out.
p4ra said:
I have made it work with first approach. I did a restart of the phone and it worked.
What I am wondering though is the following - I have used the VoLTE/VoWiFi/5G Magisk module, but I don't see the "HD" icon during the call, even though I can browse the internet (when I am not on WiFi). And despite 5G coverage of my current carrier in my area, I don't see 5G icon.
Is there any other module I am missing for this last piece of puzzle?
And last but not least. What scares me the most is that next OTA will completely screw me over after setting everything up. I wish there was a clear tutorial on how to OTA and keep the root without wiping everything out.
Click to expand...
Click to collapse
I'm not quite sure which VoLTE/VoWiFi/5G Magisk module you are referring to, but I believe enabling 5G requires modified mbn files specific to your country/region.
Regarding OTAs, there are two "How To" guides here with all the details you need.
Blaze1001 said:
Following steps work 100% - I had the same issue.
1. Use magisk canary.
2. Install universal safetynet fix MOD 2.0 from displax (Google for "displax github")
3. Use latest shamiko module
4. Activate zygisk
5. Don't enforce denylist
6. Go to denylist and chose all Microsoft apps and tick ALL options for each app.
7. Hide magisk app
Click to expand...
Click to collapse
I have done exactly this but it still detects
Oneplus 7 pro
LineageOS 19.1 Nov 27th nightly build
This should be all that's needed to pass the compliance checks for Intune
1. Magisk (Zygisk mode)
2. SafetyNet v2.3.1-MOD_2.0
3. Shamiko v0.5.1 (or higher)
4. Magisk deny-list for the following apps (without Enforce deny-list)
a. Company Portal (Intune)b. Microsoft Authenticator (if you use it)c. Microsoft Defender (if you use it)5. Make sure you clear app data for the apps in the deny list after adding them to the deny list
Don't know about this specific app, but in the past I had issues with detection of an "unsecure" device, that was related to ADB debugging being enabled in developer settings...
craigacgomez said:
This should be all that's needed to pass the compliance checks for Intune
1. Magisk (Zygisk mode)
2. SafetyNet v2.3.1-MOD_2.0
3. Shamiko v0.5.1 (or higher)
4. Magisk deny-list for the following apps (without Enforce deny-list)
a. Company Portal (Intune)b. Microsoft Authenticator (if you use it)c. Microsoft Defender (if you use it)5. Make sure you clear app data for the apps in the deny list after adding them to the deny list
Click to expand...
Click to collapse
s3axel said:
Don't know about this specific app, but in the past I had issues with detection of an "unsecure" device, that was related to ADB debugging being enabled in developer settings...
Click to expand...
Click to collapse
Still doesn't work. Its weird because it worked for one night and the next morning it stopped.
UPDATE: its LSPosed I think. But this is the only way to force dark mode on some apps....
UPDATE 2: I disabled forced dark mode on all Microsoft apps in LSPosed plugin and its looking good so far...
UPDATE 3: Had a full day with not a single root detection notification. Looks solid!
s3axel said:
Don't know about this specific app, but in the past I had issues with detection of an "unsecure" device, that was related to ADB debugging being enabled in developer settings...
Click to expand...
Click to collapse
one of the worse parts of it, if not the worst, is that nobody knows what it detects and there's no guide that applies to each and every device,
I tried in 3 devices, the exact same steps and files, etc, it worked on the 1st one, but on the other two.. no!
For all those who still got issues as another idea: Does Google Wallet work ? Is the device play protect certified ?
I ask because to get Wallet to work (and presumably other apps that rely on Safetynet and/or Play Protect certification) the additional step after #5 in the list above is: clear data for Google Play Services and Google Play Store, then reboot (your device will ask for Google backup configuration again).....
I got the same issue with an App called "SwissID". It recognizes magisk for some reason. All other Apps work (like banking, google wallet etc.)
chaos193 said:
It's pretty much what @craigacgomez said. I used Shamiko 0.6 alongside LSposed zygisk release. I'm pretty sure LSposed is not needed but I have it just in case.
Click to expand...
Click to collapse
Its work to me!!! Thanks
Hi All,
I have recently updated Barclays mobile app on my OnePlus 6 rooted running LOS 19 but the app today detected the root (probably the latest update enable that). So I have cleared the data and cache however I cannot go through the menu to access my account and I get error 00006 now.
I have magisk hide enabled and this has been working with Barclays and the other banking app for a year now (excluding Santander which detects the root anyway)
Do you have any suggestions, please?
I'm in the same boat. Magisk delta with zygisk and app hidden etc etc incl. deny list latest Barclays app still detects root. Have even tried deleting Fox folder, in case it starts seeing that recovery folder. Tried lastest canary build, still the same. Anyone had success with running the latest Barclays app rooted? Poco F3 user BTW, but the principles should be the same...
Do you know if removing the root (magisk) fixes the issue?
reg66 said:
I'm in the same boat. Magisk delta with zygisk and app hidden etc etc incl. deny list latest Barclays app still detects root. Have even tried deleting Fox folder, in case it starts seeing that recovery folder. Tried lastest canary build, still the same. Anyone had success with running the latest Barclays app rooted? Poco F3 user BTW, but the principles should be the same...
Click to expand...
Click to collapse
danc.940 said:
Do you know if removing the root (magisk) fixes the issue?
Click to expand...
Click to collapse
Nope, haven't tried yet... But i'm guessing after removing root and clearing app data it would work...
reg66 said:
Nope, haven't tried yet... But i'm guessing after removing root and clearing app data it would work...
Click to expand...
Click to collapse
Actually, the app might still recognise custom rom. Can't face stock miui just over banking app. What a blow
reg66 said:
Actually, the app might still recognise custom rom. Can't face stock miui just over banking app. What a blow
Click to expand...
Click to collapse
Is there a way to hide also the unlocked bootloader? We won't know until we try it I guess. There is also a Reddit post where many people seem to have the same problem.
Keep an eye on that too until we find a solution.
Do you know where we could get the version of the app that still works with magisk? Is it possible to export the app? Maybe we can find someone with an old version and ask them to share the apk?
A way to roll back has been posted by u/SuzannaBadger in the Reddit thread, pasting here for visibility:
Hi,
I've found a temp fix for this for now.
Steps are as below:
1. Uninstall the current Barclays banking app.
2. Go to play store,settings,network settings and turn off 'auto update apps'
3. Download the old Barclays app from: https://barclays-bank-plc-banking.en.uptodown.com/android/download (it's legit)
4. Install the app.
5. Go into Majisk, settings, configure denylist and tick all Barclays options (may already be ticked, if this is the case ignore step 5)
6. Restart phone.
7. Open Barclays app and setup as you usually would.
Hopefully this works for you. Applist detector is even detecting I have the Majisk app (even though I have Shamiko and have hidden it) but the Barclays app still works as it's the previous version.
Click to expand...
Click to collapse
reg66 said:
Actually, the app might still recognise custom rom. Can't face stock miui just over banking app. What a blow
Click to expand...
Click to collapse
Is there a way to hide also the unlocked bootloader? We won't know until we try it I guess. There is also a Reddit post where many people seem to have the same problem.
https://www.reddit.com/r/Magisk/comments/118yl7n
Keep an eye on that too until we find a solution.
Do you know where we could get the version of the app that still works with magisk? Is it possible to export the app? Maybe we can find someone with an old version and ask them to share the apk?
Jenpyon said:
A way to roll back has been posted by u/SuzannaBadger in the Reddit thread, pasting here for visibility:
Click to expand...
Click to collapse
Great thanks for the update.
danc.940 said:
Is there a way to hide also the unlocked bootloader? We won't know until we try it I guess. There is also a Reddit post where many people seem to have the same problem.
Keep an eye on that too until we find a solution.
Do you know where we could get the version of the app that still works with magisk? Is it possible to export the app? Maybe we can find someone with an old version and ask them to share the apk?
Click to expand...
Click to collapse
Not sure about hiding unlock BL, never looked into it. If you've used the linked 2.72.2 barclays app, as i have, be sure to disable auto update in google playstore
EDIT: just seen it in step 2!! however, i just selected do not auto update for that specific app, rather than all apps
danc.940 said:
Do you know if removing the root (magisk) fixes the issue?
Click to expand...
Click to collapse
Yes it does fix the issue. I've checked and now have a hard choice of either restore magisk needing BCR heavily.
danc.940 said:
Is there a way to hide also the unlocked bootloader? We won't know until we try it I guess. There is also a Reddit post where many people seem to have the same problem.
Keep an eye on that too until we find a solution.
Do you know where we could get the version of the app that still works with magisk? Is it possible to export the app? Maybe we can find someone with an old version and ask them to share the apk?
Click to expand...
Click to collapse
Hiding unlocked bootloader most likely wouldn't help as just removing Magisk leaving bootloader unlocked makes Barclays app working perfectly. So they still just detect root and Magisk some other way. What was interesting was that when I removed Magisk and Barclays functionality was restored I run hidden Magisk app to restore Magisk. It asked to restore main Magisk app that I did. And even without restoring Magisk partition and rebooting Barclays stopped working having only Magisk app installed without root.
reg66 said:
I'm in the same boat. Magisk delta with zygisk and app hidden etc etc incl. deny list latest Barclays app still detects root. Have even tried deleting Fox folder, in case it starts seeing that recovery folder. Tried lastest canary build, still the same. Anyone had success with running the latest Barclays app rooted? Poco F3 user BTW, but the principles should be the same...
Click to expand...
Click to collapse
Try downloading an app called Ice Box and freeze Magisk with it.
That fixed the issue for the bank app I use.
See my replies here guys Post
All I've posted my notes on the reddit page above
Also I have a Santander account and I could never get this app working either!!!
Note this method still doesn't work on Santander!!
sound2005 said:
See my replies here guys Post
All I've posted my notes on the reddit page above
Also I have a Santander account and I could never get this app working either!!!
Note this method still doesn't work on Santander!!
Click to expand...
Click to collapse
Followed steps exactly. Still root is detected
reg66 said:
Followed steps exactly. Still root is detected
Click to expand...
Click to collapse
Thanks for replying back.
What issues did you get, ie FC, root detected etc..?
I'm going to keep trying on my phone and see if I can get this working
Ok guys, this method works 100%!!!
Test on my Samsung Note 8 (Android 10, Custom Rom)
Install this module:
GitHub - HuskyDG/MagiskHide at v1.6
Portable MagiskHide. Contribute to HuskyDG/MagiskHide development by creating an account on GitHub.
github.com
and wipe Barclays data, thats it!!!
Best to have Zygisk off and configure the denylist to get this working
Configure Magisk apps
As Magisk app does not allow you to configure denylist when zygisk is off. You must toggle Zygisk on temprorily (not reboot) to configurate denylist and toggle Zygisk off after done.
Note that any modules that uses Zygisk will be disabled!!
sound2005 said:
Ok guys, this method works 100%!!!
Test on my Samsung Note 8 (Android 10, Custom Rom)
Install this module:
GitHub - HuskyDG/MagiskHide at v1.6
Portable MagiskHide. Contribute to HuskyDG/MagiskHide development by creating an account on GitHub.
github.com
and wipe Barclays data, thats it!!!
Best to have Zygisk off and configure the denylist to get this working
Configure Magisk apps
As Magisk app does not allow you to configure denylist when zygisk is off. You must toggle Zygisk on temprorily (not reboot) to configurate denylist and toggle Zygisk off after done.
Note that any modules that uses Zygisk will be disabled!!
Click to expand...
Click to collapse
I'd tried this with Zygisk off but then USNF had become off and device didn't pass Safetynet. Then with Zygisk on and this module on Barclays still showed 0006. Denylist was configured for Barclays and not enforced.
atreal said:
I'd tried this with Zygisk off but then USNF had become off and device didn't pass Safetynet. Then with Zygisk on and this module on Barclays still showed 0006. Denylist was configured for Barclays and not enforced.
Click to expand...
Click to collapse
Try switching Zygisk on and off.
Reboot phone, wipe data and cache for play store and Barclays and try again mate
sound2005 said:
Try switching Zygisk on and off.
Reboot phone, wipe data and cache for play store and Barclays and try again mate
Click to expand...
Click to collapse
Well. Have to put thoroughly what exactly I meant been done.
1. Added Magiskhide module to Magisk and turned it on. Magisk was last stable 25.2
2. Uninstalled Barclays. Installed Barclays without running it yet.
3. Add Barclays to Denylist. Turn Zygisk off.
Reboot
4. Checked Safetynet with YASNAC. It failed. Checked modules page in Magisk - USNF was off apparently as Zygisk was off. YASNAC had been passed before all this attempts with this module when USNF was on.
4. Run Barclays - 0006.
5. Clear Barclays data. Turn Zygisk on in Magisk.
Reboot
6. YASNAC passed as USNF became on.
7. Run Barclays - 0006
And may I ask to give some light on what is meant that "it is better to keep Zygisk off". What does this "better" mean? Must be off? Then how do they mean to bypass Safetynet with USNF off?
atreal said:
Well. Have to put thoroughly what exactly I meant been done.
1. Added Magiskhide module to Magisk and turned it on. Magisk was last stable 25.2
2. Uninstalled Barclays. Installed Barclays without running it yet.
3. Add Barclays to Denylist. Turn Zygisk off.
Reboot
4. Checked Safetynet with YASNAC. It failed. Checked modules page in Magisk - USNF was off apparently as Zygisk was off. YASNAC had been passed before all this attempts with this module when USNF was on.
4. Run Barclays - 0006.
5. Clear Barclays data. Turn Zygisk on in Magisk.
Reboot
6. YASNAC passed as USNF became on.
7. Run Barclays - 0006
And may I ask to give some light on what is meant that "it is better to keep Zygisk off". What does this "better" mean? Must be off? Then how do they mean to bypass Safetynet with USNF off?
Click to expand...
Click to collapse
Hi
By all means you can try my setup:
Modules enabled:
Magiskhide (by Husky)
Magiskhide Props Config
Systemless host
Magisk v25.2 hidden
Denylist has been configured and Zygisk switch is off.
In Denylist I have the following as blocked:
Google play store
Google play services
My bank app
Oysercard app
Please note I've messed around extensively trying to get this to work and a lot of stuff I've added and remove to test out, so some modules (or even apps on the denylist) may no longer need to be there.
Also on step 3, could you turn Zygisk on (the app will tell you to reboot to apply changes) but do not reboot yet!!!, then turn off Zygist then reboot your phone.
Once rebooted clear cache and data for play store and Barclays
Then try banking app again.
If this still doesn't work, you may have a module triggering Barclays to recognise you have root, in which case you may need to disable/remove said modules.
One prime culprit would be Lsposed, if you have this then remove this as well.
Also please note, taken from developers site:
Configure Magisk apps
As Magisk app does not allow you to configure denylist when zygisk is off. You must toggle Zygisk on temprorily (not reboot) to configurate denylist and toggle Zygisk off after done.