Database Info

Bypass SafetyNet Attestation

I'm trying to bypass the SafetyNet chore by using MagiskHide and tools like this one.
I have yet to have success.
I have read lots of information about the topic, but most seems irrelevant and obsolete.
I use a custom ROM with Root enabled.
Can anyone please point me in the right direction of solving this issue?
Thank you.

It would help if you stated which ROM or Android version you are on...

pnin said:
It would help if you stated which ROM or Android version you are on...
Click to expand...
Click to collapse
Android 11, Octavi OS.

I see... can't really help, no experience.

Magisk, Universal SafetyNetFix and MagiskHideProps

robogo1982 said:
Magisk, Universal SafetyNetFix and MagiskHideProps
Click to expand...
Click to collapse
Of course, I have that installed and working according to tutorials, already...
Still, not working.

"Fixed" it by appending `LEGACY_MIFARE_READER=1` to `/system/vendor/etc/libnfc-nci.conf`.
However, this breaks my SIM service. Not sure, how those features are related, but here we are.

Another reboot seems to have fixed the SIM service issue.
Is this really it? Is the NFC problem really fixed after such a long time?
I cannot believe it.
I will test this for some time, just to be sure....

Did you force basic attestation in props?

I'm using ArrowOS 12 (ArrowOS 11 before that) and never had problems with SafetyNet.
Using latest Magisk, Zygisk and DenyList enabled. As for modules, I use GPay SQLite Fix and Universal SafetyNet fix. No other fixes or modules were necessary

if it's for banking apps, just check "Google services" on DenyList (first of all click the dots on right upper corner and check system apps). I was fighting that some time ago.
there's no need to install modules or do anything else, just check all apps U need on DenyList but the main app to deny is still "Google Services"

xSokol said:
if it's for banking apps, just check "Google services" on DenyList (first of all click the dots on right upper corner and check system apps). I was fighting that some time ago.
Click to expand...
Click to collapse
Enabled DenyList, checked Google Play Services and it stays checked. Checking Google Services Framework gets reverted each time I visit DenyList. There is no "Google services".
I found `*.gservices` as a sub-category of Google Services Framework. Disabled. Rebooted several times, after trying out multiple possibilities, but none did work. One time, even basic attestation was broken, which needed another reboot to fix.

no, sorry for my rush, it was about Google Play Services. I have never "denied" Google Services Framework.
what I would do is uninstall modules like "safetynet fix" and reboot to twrp, there's a fix for zygisk, install that one.
then reboot to system, clear all the data of an disobedient app, then go to Magisk DenyList and look for the app, check all services and search for Google Play Services again (I have to check it aftet every reboot somehow).
I just have had similar issue an hour ago with Revolut app because I crashed my system and had to dirty flash what swiped Magisk.
just be patient, it's not hard or complicated work

xSokol said:
there's a fix for zygisk, install that one.
Click to expand...
Click to collapse
Which one? Where? How?
xSokol said:
clear all the data of an disobedient app, then go to Magisk DenyList and look for the app, check all services
Click to expand...
Click to collapse
Check the app or what services? What exactly?

ok, then..
if You go in TWRP to "advanced" and then to "magisk" (sorry if the name isn't correct, I don't focus on names of options) and there are options like "install magisk 24..." or "uninstall magisk 24...", under that there are fixes, so You should find it, it's under "SafetyNet Fix". You need Zygisk, so get fix for Zygisk.
I was about the app that's not working, if You click on the bar with the name it will show its services. in standard Magisk denies only the main service of an app, but some apps require checking all of them.

hello @Aki-to , did U manage?

xSokol said:
hello @Aki-to , did U manage?
Click to expand...
Click to collapse
I did not dare to go into TWRP, because I am not absolutely sure if data or storage encryption works perfectly fine with TWRP on Android 11. I don't want to boot into TWRP and have everything encrypted and therefore unusable.
I did so many flashes and some of them had this problem, but I cannot remember if it was because of a failed flash or because it actually did not work.
I also do not want to remove encryption in Android Security Settings every single time I visit TWRP.
Posts like the following also sound very concerning.
[FIXED] How to remove data encryption in TWRP
Users of TWRP 3.1 on Doogee Mix (including myself) faced the mammoth problem of an encrypted storage after unlocking the bootloader and flashing the custom recovery. This problem is not peculiar to the Doogee Mix, any other device with TWRP 3.1+...
forum.xda-developers.com

there's no need to remove encryption, nothing abiut that.
I just have changed MIUI to 13 today, didn't change anything on TWRP, just installed Magisk from TWRP and checked all the bank apps, GPay and Google Play Services

Aki-to said:
"Fixed" it by appending `LEGACY_MIFARE_READER=1` to `/system/vendor/etc/libnfc-nci.conf`.
However, this breaks my SIM service. Not sure, how those features are related, but here we are.
Click to expand...
Click to collapse
Hi, could you share your Magisk module?

Haobin said:
Hi, could you share your Magisk module?
Click to expand...
Click to collapse
Sure, wanted to do that, anyway, but forgot about it.

Question Wallet with Root?

I haven't been able to get wallet to not detect root, so I can't add a card. I have magisk installed with universal safetynet fix. I've also set wallet, and play store to deny.
Anything else I'm missing?
I also get CTS profile match failed.

omf05 said:
I haven't been able to get wallet to not detect root, so I can't add a card. I have magisk installed with universal safetynet fix. I've also set wallet, and play store to deny.
Anything else I'm missing?
I also get CTS profile match failed.
Click to expand...
Click to collapse
Search in this forum. There's a magisk safety net patch that got mine working.

Bxperiaz3 said:
Search in this forum. There's a magisk safety net patch that got mine working.
Click to expand...
Click to collapse
I have the lastest patch installed for Safetynet. I'm wondering if maybe it's because I'm on the newest Pixel Update.
Guess I'll test out somethings when I get home.

Mine is working fine. Follow instructions on p7 pro thread.

omf05 said:
I have the lastest patch installed for Safetynet. I'm wondering if maybe it's because I'm on the newest Pixel Update.
Guess I'll test out somethings when I get home.
Click to expand...
Click to collapse
Which latest patch? You need to have this one installed.

Yeah...he probably doesn't have Displax's mod one...he's the fourth person I've seen on this forum that's come from the regular USNF forum wondering why the usual one's not passing...
side note: it's either that or people applying the Magisk OTA update method not knowing Magisk developer hasn't applied the difference to patch and restore init_boot versus boot...
OP, use the one Lughnasadh above linked...
Also -- the obligatory after applying the module, don't forget to clear cache & data of Google Play Services, Google Play Store, Google Play Protect, and Google Service Framework....
*note: also don't forget to install systemless hosts....
Also, you should check your Safetynet status using the 2 apps YASNAC and Play Integrity API Checker from the Play Store...if you're not passing those 2 (other than Strong_Integrity), you're not gonna pass wallet...

Lughnasadh said:
Which latest patch? You need to have this one installed.
Click to expand...
Click to collapse
Yeah, that's the one I have installed.
simplepinoi177 said:
Yeah...he probably doesn't have Displax's mod one...he's the fourth person I've seen on this forum that's come from the regular USNF forum wondering why the usual one's not passing...
side note: it's either that or people applying the Magisk OTA update method not knowing Magisk developer hasn't applied the difference to patch and restore init_boot versus boot...
OP, use the one Lughnasadh above linked...
Also -- the obligatory after applying the module, don't forget to clear cache & data of Google Play Services, Google Play Store, Google Play Protect, and Google Service Framework....
*note: also don't forget to install systemless hosts....
Also, you should check your Safetynet status using the 2 apps YASNAC and Play Integrity API Checker from the Play Store...if you're not passing those 2 (other than Strong_Integrity), you're not gonna pass wallet...
Click to expand...
Click to collapse
Thanks,
I must have missed something when I was doing it, was up pretty late lol

Some apps disappeared on the Play Store after I rooted my phone.

When I first rooted my phone, everything was fine but after a few days some apps started showing up as "This app won't work on your device"
It wouldn't be a problem since I can just download the APK's, but I need to use the Revolut app, it is only available as a mobile app and when you don't install it from the Play store, it just doesn't work.
Can anyone show me a workaround for this?
Maybe a way to trick play store into letting me download all the apps as usual
or a way to trick the app into thinking it's been installed from the play store.
I thought about locking the bootloader again (OEM) but it'll wipe all data, and I don't want that. Because it's been a few months since I rooted my phone and I have a lot of data.
My phone is Samsung Galaxy S10E - SM-G970F if this info means anything.

hmm, try unrooting it, install all apps you need, and then re-root it again.

NikolaTechGuy said:
hmm, try unrooting it, install all apps you need, and then re-root it again.
Click to expand...
Click to collapse
Rooting wipes all the data tho

Quidney said:
When I first rooted my phone, everything was fine but after a few days some apps started showing up as "This app won't work on your device"
It wouldn't be a problem since I can just download the APK's, but I need to use the Revolut app, it is only available as a mobile app and when you don't install it from the Play store, it just doesn't work.
Can anyone show me a workaround for this?
Maybe a way to trick play store into letting me download all the apps as usual
or a way to trick the app into thinking it's been installed from the play store.
I thought about locking the bootloader again (OEM) but it'll wipe all data, and I don't want that. Because it's been a few months since I rooted my phone and I have a lot of data.
My phone is Samsung Galaxy S10E - SM-G970F if this info means anything.
Click to expand...
Click to collapse
you must pass safetynet as well as play integrity api in order for the apps to reappear. You can check this status by downloading the application YASNAC for safetynet status and Play Integrity API checker for checking play integrity status.
If your using magisk then you can flash safetynetfix module from here.
Flashing it should make the Basic integrity and cts profile check from False to true in yasnac
It should also turn Basic Integrity and Device Integrity from a Cross to a Tick
Strong integrity will always fail for rooted users. so forget abt that
Then go to apps > find playstore > storage > clear data
Open playstore again and you'll see an outdated UI dont worry it'll restore on the next app opening
in playstore then tap on your profile picture at the top right then go to settings. Scroll down and see if the device is play protect certified.
If it is the apps should reappear.
This is way too overkill tbh. you could just install Aurora store and call it a day since its litt playstore without accounts and stuff.

Captain_cookie_200 said:
you must pass safetynet as well as play integrity api in order for the apps to reappear. You can check this status by downloading the application YASNAC for safetynet status and Play Integrity API checker for checking play integrity status.
If your using magisk then you can flash safetynetfix module from here.
Flashing it should make the Basic integrity and cts profile check from False to true in yasnac
It should also turn Basic Integrity and Device Integrity from a Cross to a Tick
Strong integrity will always fail for rooted users. so forget abt that
Then go to apps > find playstore > storage > clear data
Open playstore again and you'll see an outdated UI dont worry it'll restore on the next app opening
in playstore then tap on your profile picture at the top right then go to settings. Scroll down and see if the device is play protect certified.
If it is the apps should reappear.
This is way too overkill tbh. you could just install Aurora store and call it a day since its litt playstore without accounts and stuff.
Click to expand...
Click to collapse
Yes but if I install it from the Aurora store I won't be able to use Revolut probably.
Also I installed the module, and though the YASNAC check has 2 ticks, the Play Integrity checker says failed on "Device integrity" and "strong integrity." What do i do then?

Quidney said:
Yes but if I install it from the Aurora store I won't be able to use Revolut probably.
Also I installed the module, and though the YASNAC check has 2 ticks, the Play Integrity checker says failed on "Device integrity" and "strong integrity." What do i do then?
Click to expand...
Click to collapse
hm what method of rooting do you use?

Captain_cookie_200 said:
hm what method of rooting do you use?
Click to expand...
Click to collapse
if you flashed the safetynet fix in magisk already then im afriad i dont know what else is wrong

Captain_cookie_200 said:
hm what method of rooting do you use?
Click to expand...
Click to collapse
Downloaded the firmware, and changed it using magisk, flashed it using ODIN.
It's Magisk 25.2
Zygisk: Yes
Ramdisk: No
But I also have the "Hide Magisk" option, and Systemless Hosts module

Captain_cookie_200 said:
if you flashed the safetynet fix in magisk already then im afriad i dont know what else is wrong
Click to expand...
Click to collapse
Yep I did.

Quidney said:
Yep I did.
Click to expand...
Click to collapse
i dont know then. i passed safety net on one ui 5 on galaxy A32 4G using that module

Captain_cookie_200 said:
i dont know then. i passed safety net on one ui 5 on galaxy A32 4G using that module
Click to expand...
Click to collapse
I also passed the check after the 25th reboot. It took some time to adjust I guess.
But I cannot hide my magisk launcher, it gets detected by Revolut. Welp

Quidney said:
I also passed the check after the 25th reboot. It took some time to adjust I guess.
But I cannot hide my magisk launcher, it gets detected by Revolut. Welp
Click to expand...
Click to collapse
Actually there is a way to fix that as well.
First of all go to magisk then press the gear icon on top right then select Hide the Magisk app. Allow it to install unknown apps. Give it a good name Let it do its work. do not go to home or anywhere while it is reinstalling the apk as something else
Second of all download shamiko from here.
First make sure you have enforce denylist disabled in the magisk's settings. Yep disabled. if it is enabled toggle it off
Then flash shamiko and reboot. Now once you boot back into the system. Open magisk again (or the new reinstalled renamed magisk app) and go to settings and then go to configure denylist. Now find your app and press the checkbox
Now see if it bypasses the root detection. if not then clear all your apps in your recents and try again. This trick always helps to get around apps with root checks.

Captain_cookie_200 said:
Actually there is a way to fix that as well.
First of all go to magisk then press the gear icon on top right then select Hide the Magisk app. Allow it to install unknown apps. Give it a good name Let it do its work. do not go to home or anywhere while it is reinstalling the apk as something else
Second of all download shamiko from here.
First make sure you have enforce denylist disabled in the magisk's settings. Yep disabled. if it is enabled toggle it off
Then flash shamiko and reboot. Now once you boot back into the system. Open magisk again (or the new reinstalled renamed magisk app) and go to settings and then go to configure denylist. Now find your app and press the checkbox
Now see if it bypasses the root detection. if not then clear all your apps in your recents and try again. This trick always helps to get around apps with root checks.
Click to expand...
Click to collapse
Just noticed since you have magisk hide your either using magisk delta or an older version of magisk. I guess you could just use magisk hide but incase that isnt working the method above is the way to go.

Captain_cookie_200 said:
Just noticed since you have magisk hide your either using magisk delta or an older version of magisk. I guess you could just use magisk hide but incase that isnt working the method above is the way to go.
Click to expand...
Click to collapse
I have 25.2 (25200), Zygisk.
But There's an option in the settings right now it says "Restore the Magisk App" because I've already hidden it.

Captain_cookie_200 said:
Actually there is a way to fix that as well.
First of all go to magisk then press the gear icon on top right then select Hide the Magisk app. Allow it to install unknown apps. Give it a good name Let it do its work. do not go to home or anywhere while it is reinstalling the apk as something else
Second of all download shamiko from here.
First make sure you have enforce denylist disabled in the magisk's settings. Yep disabled. if it is enabled toggle it off
Then flash shamiko and reboot. Now once you boot back into the system. Open magisk again (or the new reinstalled renamed magisk app) and go to settings and then go to configure denylist. Now find your app and press the checkbox
Now see if it bypasses the root detection. if not then clear all your apps in your recents and try again. This trick always helps to get around apps with root checks.
Click to expand...
Click to collapse
I'm on the phone with my friend while she sleeps so I cannot reboot the phone >_<
But I'll update you tomorrow probably if it works.

Quidney said:
I have 25.2 (25200), Zygisk.
But There's an option in the settings right now it says "Restore the Magisk App" because I've already hidden it.
Click to expand...
Click to collapse
oh i see. wait how.do you have magisk hide then

Quidney said:
I'm on the phone with my friend while she sleeps so I cannot reboot the phone >_<
But I'll update you tomorrow probably if it works.
Click to expand...
Click to collapse
oh i see. i just tested it on my device and yes it works. the shamiko method is listed prevents the root detection. hope it works fine for you

Captain_cookie_200 said:
oh i see. wait how.do you have magisk hide then
Click to expand...
Click to collapse
I don't have "Magisk Hide" I think that is another feature (Superuser -> Hide) which does not exist for me.

Quidney said:
I don't have "Magisk Hide" I think that is another feature (Superuser -> Hide) which does not exist for me.
Click to expand...
Click to collapse
magisk hide was removed. anyways try the shamiko method and tell if it works

Captain_cookie_200 said:
magisk hide was removed. anyways try the shamiko method and tell if it works
Click to expand...
Click to collapse
Yep everything worked out. I have Revolut now, and it doesn't detect magisk or root.
I still don't have Google Pay, but that's a job for future me.

Barclays banking app (UK) with root

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.

I Broke Magisk

It updated today, and now I can't open it and I keep getting error messages to say it keeps stopping.
I'd been holding off on the update because I knew there was something going on with the developer going to Google and all the root/hide stuff being disabled. Not sure how to roll back or what to do.

koberulz said:
It updated today, and now I can't open it and I keep getting error messages to say it keeps stopping.
I'd been holding off on the update because I knew there was something going on with the developer going to Google and all the root/hide stuff being disabled. Not sure how to roll back or what to do.
Click to expand...
Click to collapse
Can you uninstall Magisk and install the stable or last working canary app?

simplepinoi177 said:
Can you uninstall Magisk and install the stable or last working canary app?
Click to expand...
Click to collapse
No clue, I'm not sure what its status is these days. That's why I was hesitant to update (I've also been knocking back the Android 12 system update for the same reason).

koberulz said:
No clue, I'm not sure what its status is these days. That's why I was hesitant to update (I've also been knocking back the Android 12 system update for the same reason).
Click to expand...
Click to collapse
You can't uninstall the Magisk app; like from the App section in Settings or app info of the app? I'm not talking about the applied Magisk patched boot image.
Because I'm thinking you can just uninstall the Magisk app (as it's glitching and force closing), and try installing the stable or earlier canary builds...

simplepinoi177 said:
You can't uninstall the Magisk app; like from the App section in Settings or app info of the app? I'm not talking about the applied Magisk patched boot image.
Because I'm thinking you can just uninstall the Magisk app (as it's glitching and force closing), and try installing the stable or earlier canary builds...
Click to expand...
Click to collapse
I don't know how that would affect root, or Magisk hide, as I know a lot of that has been nuked since topjohnwu got hired at Google.
I also currently have Magisk hiding itself, which may make even an uninstall difficult if I even knew what to install over the top of it.

koberulz said:
I don't know how that would affect root, or Magisk hide, as I know a lot of that has been nuked since topjohnwu got hired at Google.
I also currently have Magisk hiding itself, which may make even an uninstall difficult if I even knew what to install over the top of it.
Click to expand...
Click to collapse
Uninstalling the Magisk Manager app would not affect root; you might not be able to run certain rooted apps properly without granting them root access, but that's because of not having the Magisk app to grant it.
I don't know about topjohnwu being hired and working for Google or what not, but Magisk is still being currently worked on and developed so it has not been "nuked"...
How is Magisk Manager hidden "itself" if you claim you attempt to run the app and it force-closes? The only way for Magisk Manager to "hide itself" is that it merely renames itself (to a name you can choose; default is "Settings") so it's not detected by any root detection. In any case, you should be able to find it in the Apps list in Settings/Apps, and uninstall it that way.
As to what to install over the top of it, installing the latest stable 25.2 would be the best idea -- the Magisk App does not need to match the version that is patched and flashed to your boot partition...

simplepinoi177 said:
I don't know about topjohnwu being hired and working for Google or what not, but Magisk is still being currently worked on and developed so it has not been "nuked"...
Click to expand...
Click to collapse
My understanding was that he got hired and they said he had to give it up, there was some negotiation and they let him continue working on it as long as Magisk Hide was removed as a feature.
But this isn't something that really interests me all that much, so I don't keep up with the news on it. I more just check in whenever I get a new phone in order to figure out how to root it.
simplepinoi177 said:
How is Magisk Manager hidden "itself" if you claim you attempt to run the app and it force-closes? The only way for Magisk Manager to "hide itself" is that it merely renames itself (to a name you can choose; default is "Settings")
Click to expand...
Click to collapse
Yes, this is what I was referring to.

koberulz said:
Yes, this is what I was referring to.
Click to expand...
Click to collapse
koberulz said:
It updated today, and now I can't open it and I keep getting error messages to say it keeps stopping.
Click to expand...
Click to collapse
Again, I ask, as you stated; you try to open it -- so you must know what name it's under then (even though it's hidden since it being hidden is just it hiding its name) -- and it keeps force closing or stopping... so why can't you find the app details and uninstall it?

simplepinoi177 said:
Again, I ask, as you stated; you try to open it -- so you must know what name it's under then (even though it's hidden since it being hidden is just it hiding its name) -- and it keeps force closing or stopping... so why can't you find the app details and uninstall it?
Click to expand...
Click to collapse
Because I don't know how that will affect root/hide. I'm not sure what the status of Magisk is these days.

koberulz said:
Because I don't know how that will affect root/hide. I'm not sure what the status of Magisk is these days.
Click to expand...
Click to collapse
Magisk is pretty much the only way to root at this point -- I just learnt of another method KernelSU, but it seems pretty basic, especially in comparison to Magisk -- and the status of Magisk is that it is still very much active and actively developed; as it is the sole rooting method for numerous Android running devices, not just Pixels.
Your original issue is that Magisk Manager isn't working properly after updating and seems to be freezing/force-closing. The standard way of fixing that is to uninstall/remove the Magisk Manager app and re-install it (either the stable version or an earlier canary version that had worked previously).
Removing Magisk Manager app will NOT affect root and/or the patched boot partition. It WILL affect granting apps root access and will affect Magisk Hide (or Zygisk DenyList) -- but that will only last as far/long as rebooting and re-installing the Magisk Manager app. Once you re-install it, you will gain all of that back; it is only momentarily lost in between the uninstallation and re-installation.

simplepinoi177 said:
Magisk is pretty much the only way to root at this point -- I just learnt of another method KernelSU, but it seems pretty basic, especially in comparison to Magisk -- and the status of Magisk is that it is still very much active and actively developed; as it is the sole rooting method for numerous Android running devices, not just Pixels.
Your original issue is that Magisk Manager isn't working properly after updating and seems to be freezing/force-closing. The standard way of fixing that is to uninstall/remove the Magisk Manager app and re-install it (either the stable version or an earlier canary version that had worked previously).
Removing Magisk Manager app will NOT affect root and/or the patched boot partition. It WILL affect granting apps root access and will affect Magisk Hide (or Zygisk DenyList) -- but that will only last as far/long as rebooting and re-installing the Magisk Manager app. Once you re-install it, you will gain all of that back; it is only momentarily lost in between the uninstallation and re-installation.
Click to expand...
Click to collapse
Is there a dedicated Magisk thread? It's very difficult to find things on this forum, given how large it is.

koberulz said:
Is there a dedicated Magisk thread? It's very difficult to find things on this forum, given how large it is.
Click to expand...
Click to collapse
There are 2 threads.
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com

What's the difference?

koberulz said:
What's the difference?
Click to expand...
Click to collapse
dcarvil said:
There are 2 threads.
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Click to expand...
Click to collapse
The first one is the first, general Magisk thread (that is still active and currently discussed). The second is as it is stated in the headline -- "This is a discussion and help thread for the newer versions of Magisk".
Most likely this is where you should go for your issues -- and to see how actively developed it is currently being.
It's just as you said, you've been away from rooting/Magisk for a while; the newer version of Magisk contains/employs Zygisk -- "Zygisk is new generation Magisk hide...Zygisk is what the Magisk developers call running Magisk in the Zygote Process of Android. The Zygote Process is the first process that the OS starts when it boots up, ... Since zygote starts first after system, it can hide root without sending data to apps." (source) As such, that's why a new thread was created and why it is sub-titled as "The Age of Zygisk"...
*but there are many more methods of hiding root than Zygisk (or in conjunction with); Shamiko, Magisk Delta, HideMyApp, etc.
In the end, I'm sure they'll suggest what I've suggested to you in some fashion -- you'll have to uninstall the Magisk Manager (hidden or not), and re-install the stable or earlier canary versions. But it'll be better coming from the people in that thread...
Good luck!