Database Info

Make Super Mario Run work on Rooted Android Devices

This is a starter thread for getting Nintendo's latest Android app (which has finally come from iOS over three months later), Super Mario Run, to work on Android devices that have been rooted and possibly have no Google Play Store installed. Developers, please contribute your findings!

It worked with root but I got an error when I finished the tutorial. Then I saved my game with a Nintendo account and I cleared game data. I've used magisk hide with this game and I can play again

apfo said:
It worked with root but I got an error when I finished the tutorial. Then I saved my game with a Nintendo account and I cleared game data. I've used magisk hide with this game and I can play again
Click to expand...
Click to collapse
I used magisk too but I can't find where I can hide.. can you help me? Do I need to install a module?

n0m1s said:
I used magisk too but I can't find where I can hide.. can you help me? Do I need to install a module?
Click to expand...
Click to collapse
After you've installed Magisk you just need to go to the Settings in the Magisk Manager APP and enable Magiskhide and then you should See a new tab for Magisk hide in the Manager APP and just select the Apps you want to hide root.
(Sorry for my Bad English)

ApollosRage said:
After you've installed Magisk you just need to go to the Settings in the Magisk Manager APP and enable Magiskhide and then you should See a new tab for Magisk hide in the Manager APP and just select the Apps you want to hide root.
(Sorry for my Bad English)
Click to expand...
Click to collapse
Thanks for that, but it's not working too

ApollosRage said:
After you've installed Magisk you just need to go to the Settings in the Magisk Manager APP and enable Magiskhide and then you should See a new tab for Magisk hide in the Manager APP and just select the Apps you want to hide root.
(Sorry for my Bad English)
Click to expand...
Click to collapse
I did exactly what you did and it worked fine for me.

So do I flash via twrp the zip in the magisk post?

I use magisk to hide mario but when i pass the tutorial send error 804 5100 and have to delete the Account:.xml located in /data/data/com.nintendo.zara/sharedfolder and then log in with my account so brings my save but i complete 1 course and the same error again and have to do it all over again, does anybody find a solution for this?

Is magisk a supersu replacement or can I just install alongside? It also says it requires 5.x so no 4.4?

Magisk work great for me

simbin said:
Is magisk a supersu replacement or can I just install alongside? It also says it requires 5.x so no 4.4?
Click to expand...
Click to collapse
it is a supersu replacement but the magisk is great and has better functions and the moduls are great, forget the turning off part and the the recovery and flash the zip, the magisk do it all for you!

Mago6246 said:
it is a supersu replacement but the magisk is great and has better functions and the moduls are great, forget the turning off part and the the recovery and flash the zip, the magisk do it all for you!
Click to expand...
Click to collapse
Don't think magisk works with cm12 on Amzn Fire Phone bc bootloader isn't actually unlocked. They should limit SafetyNet to Leaderboards - pretty sure that's what all the fuss is about. Fine, Nintendont take my money!

Magisk Manager won't install Magisk on my rooted S7 Edge. I've read that it's not compatible with Samsung devices right now, don't know if that's true. How else can I make Super Mario Run work?

suhide give me bootloop with lineos so I will try magisk

simbin said:
Is magisk a supersu replacement or can I just install alongside? It also says it requires 5.x so no 4.4?
Click to expand...
Click to collapse
Yes, You can use it alongside with SuperSU.

Hi !
Same error for me... I installed Magisk, uninstalled SuperSU, set the Super Mario App to hide but i still get the error...
Did I miss something ?
Thanks
Rooted Nexus 5 running Cataclysm 6.0.1

Miitomo was patched using a special security bypasser made for it, and also with XPosed and RootCloak. Is there a similar method for those who seem to have issues using Magisk?
I myself haven't tried Magisk. I'll see how it works on my Galaxy S7. :fingers-crossed:

Xda, please merge this thread with the other thread that I made. I accidentally made a duplicate.

I do not have Google Play services installed, and it seems to need it.

I'm currently running Magisk with Magisk Hide on and RootCloak as well and it keeps erroring out. Currently the only workaround I've found is deleting the deviceAccount xml file in the app prefs folder. I have a feeling it has something to do with xposed or safetynet that's causing it to fail. I enjoy the game enough that I wouldn't mind buying it, but not if Nintendo is going to lock users out like this.

Can't successfully hide root with magisk 18.1 for square reader app

I've been rooting my Android phones since about 2012, but today I got a point of sale card reader for my business and I'm not having any luck hiding root from the app (square reader app). The app wont work at all so I tried a number of options in magisk manager (magisk hide the app, hide magisk manager, enable core mode only) rebooting between each try and clearing the square reader app data and setting it up fresh each time, but still no luck
I tried to uninstall magisk but the app still didn't work. So I eventually flashed back to stock and got rid of magisk all together, now the app works but I don't have root...
I tried installing magisk again after I got the app to work and hiding root from the app before I opened it up again, but it still somehow knew the device was rooted
Can anyone suggest anything I haven't tried? Or is there an alternative to rooting the OnePlus 6 (other than magisk) and hiding root? I had a bit of a look around but didn't find anything.
Thanks

I had to go back to 18.0, heard 18.2 works as well.

qbanlinxx said:
I had to go back to 18.0, heard 18.2 works as well.
Click to expand...
Click to collapse
Thanks for your reply. I tried with 18.0, damn, it still doesn't work, it still picks up that the phone is rooted
I tried the 18.2 canary build as well (18.2-e72c6685) no luck either
This app must be looking somewhere out of the ordinary for evidence of root in the phone

I have a bank application and facing the same problem. Hope someone can help us to make applications run by hiding the root
I think recent applications are looking for if knox security is tripped !! so in this case Magisk will not help

Ooohhh had to subscribe to this as I face the exact same issue!! Been trying to get my Square reader to work for a while with root and could never figure out how they are detecting root. Using Pixel XL here

Google changed something in Safety Net in play services, it passes, yet for me, google pay fails. That COULD be the issue, though I read 18.2 fixes that. Another option I helped a friend with is if it's detecting magisk itself via the files, culprit here was pokemon go.
Try opening your Magisk settings, the tick "hide magisk manager" clear the repo cache, and rename or delete the MagiskManager folder on the root of your storage. Reboot, clear data from the square app, and try again. Keep in mind, you have to unhide magisk to update it.

Skreelink said:
Google changed something in Safety Net in play services, it passes, yet for me, google pay fails. That COULD be the issue, though I read 18.2 fixes that. Another option I helped a friend with is if it's detecting magisk itself via the files, culprit here was pokemon go.
Try opening your Magisk settings, the tick "hide magisk manager" clear the repo cache, and rename or delete the MagiskManager folder on the root of your storage. Reboot, clear data from the square app, and try again. Keep in mind, you have to unhide magisk to update it.
Click to expand...
Click to collapse
In my case, I dont think its detecting the files. The reason i say that is because I play Pokemon Go just fine with no issues. So whatever Square is doing, its something different then what PoGo is doing.

Idledev said:
In my case, I dont think its detecting the files. The reason i say that is because I play Pokemon Go just fine with no issues. So whatever Square is doing, its something different then what PoGo is doing.
Click to expand...
Click to collapse
I agree, I have no problem hiding magisk and root from other apps, the square reader app must be somehow different. I've even gone through my storage and deleted any files or folders that might suggest the phone is rooted, but still no luck...
I also went into battery optimization settings to stop magisk from being put to sleep (which might stop magisk hide from working..?), that didn't work either.
I've found a temporary workaround to my problem anyway, I realized that I can share my internet (wifi hotspot) with my ipod touch, this way square reader works as the ipod touch isn't jailbroken or modified. It just means I have to carry around my ipod touch with me, which is a better trade off for me than having a stock, non root phone

Managed to get it working today! Upgraded my Pixel XL to the Android Q beta. By doing this, I had to run Magisk canary build. Installed square, enabled Magisk hide, rebooted and it worked fine! Not sure if the Android Q beta has anything to do with it,but give the canary builds of Magisk a try

Idledev said:
Managed to get it working today! Upgraded my Pixel XL to the Android Q beta. By doing this, I had to run Magisk canary build. Installed square, enabled Magisk hide, rebooted and it worked fine! Not sure if the Android Q beta has anything to do with it,but give the canary builds of Magisk a try
Click to expand...
Click to collapse
That's awesome! What canary build did you use?
I tried the latest build a few weeks ago and it didn't work for me

Build 18120

Idledev said:
Build 18120
Click to expand...
Click to collapse
No luck for me...
I updated to the latest canary build, cleared all data from square reader app, selected magisk hide, rebooted the device. After it booted up I tried to run it and it still detected root. I have a feeling that the OnePlus OS does something that doesn't totally allow me to hide root from the square reader app. It's annoying because for other apps root can be hidden
Maybe there's something in the Android Q build that lets you hide root better

Something that seems reliable right now on 18.1, Pixel Experience and OOS :
Combine Magisk Hide with Magisk "Core Mode". This seems to do the trick for now, Google Pay is triggered with normal mode, but works in Core Mode. Same for Snapchat and banking apps like N26.
But within this, you can't use any module.
kage00 said:
I also went into battery optimization settings to stop magisk from being put to sleep (which might stop magisk hide from working..?), that didn't work either.
Click to expand...
Click to collapse
This is always a good idea, on OOS at least, Magisk being optimized sometimes prevents the granting of root rights to apps, it never reacts to kernel applications requesting root on startup for example.

There's an issue with Googlypay services apparently. You need to downgrade it (remove factory updates) so it's down to version 14.something and then it should work.
You need to disable admin rights and background data to try to prevent autoupdates as well. This thread may be useful?
https://forum.xda-developers.com/ap...e-pay-magisk-discussion-t3906703/post79155616

DaveW1972 said:
There's an issue with Googlypay services apparently. You need to downgrade it (remove factory updates) so it's down to version 14.something and then it should work.
You need to disable admin rights and background data to try to prevent autoupdates as well. This thread may be useful?
https://forum.xda-developers.com/ap...e-pay-magisk-discussion-t3906703/post79155616
Click to expand...
Click to collapse
Hmm, I'm running the magisk xXx ROM and google pay is completely debloated/removed. when I get a spare half hour I might try removing the xXx module and flashing back to stock and following the advice in that thread. I'll let you know how it goes

kage00 said:
Hmm, I'm running the magisk xXx ROM and google pay is completely debloated/removed. when I get a spare half hour I might try removing the xXx module and flashing back to stock and following the advice in that thread. I'll let you know how it goes
Click to expand...
Click to collapse
Ummm yeah.. then the problem doesn't lie within Google pay it lies within the modifications that you are using.
I have to say I have never had any issues with Google pay or Android pay or any banking app using magisk. I don't even have to hide anyting. Of course I'm also not using any modified ROMs or kernels either

Hi guys,
I have this issue for a couple years now and I just cannot find a solution!
Google Pay, and 4 banking app from two different countries work fine with my 1+6 (stock ROM OOS 9.0.9 with magisk 19.4 - 7.3.4) but Square does not.
Did anyone find a solution?
Magisk config:
Magisk hide
Two modules OOS phone record and youtube
No core mode
All banking app and Square hidden

Magisk not always active?

Hey,
phone unlocked/rooted with Magisk 17.3 - now 2 issues:
1. apps with root rights can not always use them. I have to start magisk app manually, close and reopen the app (e.g. SD Maid cleaning app) and then it has root rights again and works properly
a big problem seems to appear then on AFWall+, which is super slow for me. have to reopen especially instagram 3 times to get connection. I guess this is connected to the same issue with magisk, would be worth a try at least. anyone got an idea how I can fix the magisk issue?
2. apps that check for root (my online banking wont work on rooted phones) cant be tricked by the "magisk hide" function apparently. anyone got experience with that? what can i do?
thanks in advance guys :good:

steffenmix3 said:
Hey,
phone unlocked/rooted with Magisk 17.3 - now 2 issues:
1. apps with root rights can not always use them. I have to start magisk app manually, close and reopen the app (e.g. SD Maid cleaning app) and then it has root rights again and works properly
a big problem seems to appear then on AFWall+, which is super slow for me. have to reopen especially instagram 3 times to get connection. I guess this is connected to the same issue with magisk, would be worth a try at least. anyone got an idea how I can fix the magisk issue?
2. apps that check for root (my online banking wont work on rooted phones) cant be tricked by the "magisk hide" function apparently. anyone got experience with that? what can i do?
thanks in advance guys :good:
Click to expand...
Click to collapse
Flash latest magisk

yup for everyone who missed it....we had to skip v18 but the new v19 seems to be fully compatible #magisk

Question Company Portal (InTune) detects root - anyone else?

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

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.