Hi guys, here I need your support for this phone! I need to use a banking app, but this doesn't work as safetynet finds it as irregular. I've installed magisk manager and I can hide apps (checked on a root checker app) but I still see not-certified on google play (and I have :false as result on safetynet on magisk manager).
I found some solutions, but all of them are stricly connected to a specific phone.
Is there something for our apollo? Cause I'd avoid to spend a lot of time when the solution is 'already' out there
Which rom do you have installed? ^^
I'm still using the stock one.
Actually I solved with the mobile bank app using magisk (suddenly it works), but I still don't have green flag on safety net
make sure to have the newest magisk version (now: 16.4) ,even pokemon works. etc., just add it to magisk hide.
The SafetyNet Basic Integrety is still okay on Vernee Apollo Lite, but the CTS Profile isn't (not certified by Google or whatever).
Flash this Magisk Module (Download) and then CTS Profile should work too.
Related
Been out of the root game for about 2 years now. I want to root the pixel 6. I take it it'll be the same as a couple years ago that root will cause gpay to not work even if safetynet passes. Is there a workaround to get gpay working at the moment?
Is there any other feature / apps that will stop working
Thanks
If you're planning to root, GPay will most likely detect your device was been tempered with unless you install Magisk to hide your root.
I'm using GPay on my Pixel 5 with Magisk 23014 and Universal SafetyNet Fix 2.2.0.
Download Magisk Canary 23014
In Magisk, go to Settings, enable Zygisk, enable Enforce DenyList
Download USNF 2.2.0 and install it in Magisk.
Reboot.
Open Magisk again, go to Settings, Configure DenyList.
Enable DenyList on ALL components of Google Play Services, Google Play Store, and GPay.
SafetyNet should now pass, and GPay should work.
You don't need to deny anything. My deny list is empty and off.
LLStarks said:
You don't need to deny anything. My deny list is empty and off.
Click to expand...
Click to collapse
Huh. I was just doing the same thing I did on Magisk 23001 with USNF 2.1.1.
Some apps will need to have root and Magisk hidden in order to function.
V0latyle said:
Huh. I was just doing the same thing I did on Magisk 23001 with USNF 2.1.1.
Some apps will need to have root and Magisk hidden in order to function.
Click to expand...
Click to collapse
This is unnecessary for current GPay operability.
Magisk 23014 + Hide Magisk (for all those apps that may specifically look for it) + USNF 2.2 + Zygisk Enabled + DenyList (add specific apps (not GPay or Google Play *) that still detect root (YMMV)).
SafetyNet (i.e. YASNAC to check, etc.) should pass and GPay should work.
It was even put in to USNF 2.2:
magisk: Remove Play Services from DenyList earlier · kdrag0n/[email protected]
This ensures that GMS will never start before it's removed from the DenyList, even if another module's service.sh is blocking our script. Suggested-by: osm0sis <[email protected]>
github.com
pershoot said:
This is unnecessary for current GPay operability.
Magisk 23014 + Hide Magisk (for all those apps that may specifically look for it) + USNF 2.2 + Zygisk Enabled + DenyList (add specific apps (not GPay or Google Play *) that still detect root (YMMV)).
SafetyNet (i.e. YASNAC to check, etc.) should pass and GPay should work.
It was even put in to USNF 2.2:
magisk: Remove Play Services from DenyList earlier · kdrag0n/[email protected]
This ensures that GMS will never start before it's removed from the DenyList, even if another module's service.sh is blocking our script. Suggested-by: osm0sis <[email protected]>
github.com
Click to expand...
Click to collapse
Nifty. Thanks for the update.
I have a rooted (magisk 24.3) Nord N10 5G, I have enabled zygota and installed the safetynet fix from github.
Using "yet another safetynet checker" app, my phone went from fail to pass in both SafetyNet checks.
I've also installed Snapchat and verified that it works (supposedly it shouldn't if you don't pass safetynet?).
However, Google Pay says "Phone does not meet security requirements"
So... is there any way to make it work?
AVAndronov said:
I have a rooted (magisk 24.3) Nord N10 5G, I have enabled zygota and installed the safetynet fix from github.
Using "yet another safetynet checker" app, my phone went from fail to pass in both SafetyNet checks.
I've also installed Snapchat and verified that it works (supposedly it shouldn't if you don't pass safetynet?).
However, Google Pay says "Phone does not meet security requirements"
So... is there any way to make it work?
Click to expand...
Click to collapse
Make sure you have Magisk Props Config, Universal Safetynet fix, and if those don't work try Shamiko https://t.me/magiskalpha
Download the latest Release.zip from telegram and install through Magisk. Then you'll have to enable the Denylist in the settings and then select Google Pay app and all your Google services and apps etc. Afterwards untick the "enforce denylist" since Shamiko will enforce your denylist now. Shamiko uses the Magisk list I believe but you must have it disabled after you're done selecting your apps like I said above.
JazzieBoi said:
Make sure you have Magisk Props Config, Universal Safetynet fix, and if those don't work try Shamiko https://t.me/magiskalpha
Download the latest Release.zip from telegram and install through Magisk. Then you'll have to enable the Denylist in the settings and then select Google Pay app and all your Google services and apps etc. Afterwards untick the "enforce denylist" since Shamiko will enforce your denylist now. Shamiko uses the Magisk list I believe but you must have it disabled after you're done selecting your apps like I said above.
Click to expand...
Click to collapse
Thank you.
For some reason, it did not occur to me that I should Denylist the Google apps. After I've added GPay to the list, it now passes all security checks., and I don't need any props config or Shamiko, just the Safetynet fix is enough!
AVAndronov said:
Thank you.
For some reason, it did not occur to me that I should Denylist the Google apps. After I've added GPay to the list, it now passes all security checks., and I don't need any props config or Shamiko, just the Safetynet fix is enough!
Click to expand...
Click to collapse
Okay I'm pleased to hear you've fixed it. Essentially, you'd only need Shamiko if you're having problems with certain apps like bank apps and things of that nature. Glad you can use GPay now. Enjoy your phone.
Is anyone one else having any issues getting GPay to work on the latest 11.0.10 security patch by chance?
I think I may have just done something out of order. I have 2 Nord N10 5Gs, one is on 11.0.0 and working fine, and I'm trying to setup the other one on 11.0.10 ... and I'm currently having issues.
I actually am able to get safetynet to pass the checks fine, but sometimes GPay seems to still insist that the "Phone does not meet security requirements". I even have zygisk enabled and GPay and services blocked.
One thing though, Google Play Services never stays checked in the Deny List for me. Does anyone else experience this too?
In general, it seems that with the latest security patch, i have to freeze the Magisk app otherwise several apps seem to detect it now, even with zygisk, hide, and renaming the magisk app package.
EDIT: The answer was too simple. MagiskHidePropsConfig, and spoof a valid device profile.
Hello, I would like to use Google Pay on my phone with Magisk Root, but I get the error message that the phone is rooted. After a short research I came across SafetyNet after a short test it turned out that the test failed. How can I fix this without losing root?
You can use this free app for checking the SafetyNet Status:
YASNAC - SafetyNet Checker - Apps on Google Play
Yet Another SafetyNet Attestation Checker
play.google.com
For passing the check you can read this:
How to pass SafetyNet on Android after rooting or installing a custom ROM
It is possible to pass SafetyNet, even after extensive modding like rooting or installing a custom ROM. Check out how to do that here!
www.xda-developers.com
Try the Universal SafetyNet Fix Magisk module.
Latest release is v2.3.1
- open magisk
- Install module "safetynet-fix-v2.3.1.zip"
- activate Zygisk
- activate denylist
- check Google Play store and Google Play Services
- open app info for Play Store and Google Services and delete data
- restart
- check with the app from first link
--->This is a working method as of May 2023 to have root on any rom version for redmi k20pro.
--->This will help you root and keep root hidden along with using lsposed modules.
--->These steps work on any device and any rom
You can find extra guides for the steps you dont understand by searching on xda forums. Some of these guides are linked to at the bottom of this post
Your bootloader needs to be unlocked to follow this guide. See link at bottom for guides to do the same.
****************************
I am not responsible for any data loss or damage. Follow at your own Risk
****************************
1. Install twrp or orangefox recovery on your phone.
2. Flash Magisk 25.2 (Version 26 has many issues. This version is better to use)
3. Reboot, install magisk apk(rename magisk.zip file to magisk.apk and install)
4. In magisk modules, install shamiko
5. In magisk modules, install safetynet 2.4.0
6. Add any app you want to hide root from in denylist of magisk. Additionally add Google play Services, Google play store, google services framework and google play protect to denylist(enable show system apps option in menu available on top right of denylist)
(IMP: Do not enable enforce denylist, Shamiko does this function)
7. If you have already logged into google play store and it shows device not certified in about section of play store -remove google account from phone and clear data of play store, play services, google services framework. Reboot amd try again. It will show certified status after about 10 minutes of logging in
8. Some custom roms may have device fingerprints which will get detected as custom rom. If that happens, use hide user debug and lineage props magisk module. Note: This version from github can only be flashed in Androidacy Fox Module Manager due to issue in zip packaging. Download this file which is just a properly repackaged version that can be flashed in any magisk manager.
Next install Reset Sensitive props magisk module. A combination of simply installing these modules will fix custom rom detection on any custom rom.(Example on opening whatsapp or GPay for first time)
Additional step(not necessary): Your rom may have additional build.prop entries that indicate a custom rom. Look for such build properties by opening build.prop in root browser on your device, then change any that have a custom rom name in them using magiskhideprops(Refer instructions to use magiskhideprops in the link)
9. Now, hide the magisk app in magisk app settings(set name to something like setting or app)
10. Freeze magisk manager app using link2sd/swift backup/ airfrozen or any other similar app. You can enable app when you need to install or disable modules or grant superuser access to new apps. You can also use Androidacy Fox MMM manager to find, install and remove magisk modules
_____________________________________________________________________________
Done, you can stop at this stage if you dont need lsposed.
Be warned that youw ill need to re-add any app you uninstall and reinstall in denylist.
If you want to use lsposed, continue with below steps after skipping step 10.
_____________________________________________________________________________
11. Install lsposed module 1.8.6 zygisk version
12. Install hide my appslist. Follow instructions in this link to learn how to correctly configure and hide magisk manager, lsposed and any other root apps you have.
You will need dataisolation enable magisk module if using android 10 and below for hidemyapplist to fully work.
13. Install Ruru and 'Play Integirty API Checker'.
Run Ruru and watch it pass all tests.(almost no banking app uses the level of detection used by ruru) Use play integrity api checker to check safetynet status - should pass basic integrity and cts profile.
Momo shows some messages like abnormal environement and TEE but that is ok.
Remember that you should enable denylist and Hide my applist for Ruru/Momo similar to how you enable for banking apps to hide.
Your root access is perfectly hidden now.
_____________________________________________________________________________
If you want to hide Developer Options_____________________________________________________________________________
You have a few options for this.
1. I personally turn usb debugging off in settings and use WADB app to enable wireless adb. I am using this on android 11 as other options dont fully hide or trigger xposed hook detection(which does not cause issues with the banking apps I have tested so far)This is not detected by any apps.
2. If on android 10 or lower, you can use hide user debug magisk module by huskydg which you can get from this telegram channel. I dont know if it can be linked here .
This effectively hides user debug without trigerring any root/xposed detection. Ruru may show 1 entry for usb debugging enabled but that is fine. If it doesnt work, it will show 2-3 detected entries for debugging mode.
I have uploaded the file here but dont know if it will last
3. If above options dont work,use devoptshide app, enable it in lsposed for apps you want to hide user debug from.This method will trigger xposed hook detection in Ruru but none of the banking apps i tested so far have an issue with that. Ruru may show 1 entry for usb debugging enabled but that is fine. If it doesnt work, it will show 2-3 detected entries for debugging mode.
4. I have not personally tested this but this module is an updated version of hide userdebug module by huskydg and it might help hide usb debugging on android 11 and up.You will have to try it yourself for now.I expect it to work.
GitHub - Magisk-Modules-Alt-Repo/ezme-nodebug: Change some props and "remove" LineageOS ones.
Change some props and "remove" LineageOS ones. Contribute to Magisk-Modules-Alt-Repo/ezme-nodebug development by creating an account on GitHub.
github.com
_____________________________________________________________________________
If an app detects root accidentally and refuses to run on your device again even if root is not detected again/ Spoof device ID for apps_____________________________________________________________________________
1. Now you need to use android faker lsposed module to randomize imei, max adress, android device id,hardware id.
Enable android faker in lsposed only for the app you want to change id for. Dont enable it for android system or android framework(Goal is to change id for a single app).Before doing these steps you need to clear data of play store, play services and google services framework, remove your google account from device settings and reboot. This will reset your gsf id.
This will give xposed hook detection in butbank apps dont seem to look for it.
2. If the above method does not work, use Xprivacylua. Enable for the app you want to change id, only use setting for device identifiers,use tracking, telephony data, analytics, get applications. Xprivacylua is not properly hidden even by Hide My Applist but apps dont look for it.So use this if above options does not work.
_____________________________________________________________________________
If you need to disable Widevine L1 DRM protection to use scrcpy screen mirroring etc
_____________________________________________________________________________
Install the liboemcryptodisabler module in magisk.Do note that widevine will drop to L3 but uninstallation brings it back to L1.
NOTE: Drm content cannot be mirrored on scrcpy if you are using android 12 or 13. Use roms with android version upto 11 if you need to watch drm protected content through scrcpy.(at your own risk. I do not advise illegal activity.)
Spoiler: liboemcryptodisabler
Magisk Modules Repository By Androidacy - Androidacy
This is the Androidacy Magisk Modules Repository, where you can search, browse, and download your favorite Magisk modules right now.
www.androidacy.com
Enjoy your properly hidden rooted device with all functionalities.
___________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________
I have added a few useful posts by other members if you dont know how to do any of the above mentioned steps. Any others steps can be learned with guides from XDA -Use search
1. Simple guide to flashing on K20 Pro
His advice on not using orangefox for custom roms other than stock miui/ xiaomi.eu roms may be right, I have not tried it. Orangefox personally works best for me.
2. Guide to flashing custom roms, changing between miui and custom roms
3. Bootloader unlock, twrp, root instructions and rom links
4. Common issues with Redmi K20 Pro | fingerprint unlock | ghost touch | Dim display | sensor issues | bluetooth and calling
Confirmed working in May 2023.
Guide will be eventually updated with Magisk Delta which is better for root hiding
I am amazed how smoothly my update went from old magisk version that started having issues. I followed first part of this tutorial (without lsposed), I downloaded newest versions of everything (magisk 26.1 - had to directly install magisk in magisk too, Shamiko-v0.7.1-166-release, rest same as in tutorial) and it just worked. No more problems with old magisk. Deny list is working flawlessly!, safetynet is passing, Google Play Store says that device is certified. Thank you so much for this tutorial!
czacha994 said:
I am amazed how smoothly my update went from old magisk version that started having issues. I followed first part of this tutorial (without lsposed), I downloaded newest versions of everything (magisk 26.1 - had to directly install magisk in magisk too, Shamiko-v0.7.1-166-release, rest same as in tutorial) and it just worked. No more problems with old magisk. Deny list is working flawlessly!, safetynet is passing, Google Play Store says that device is certified. Thank you so much for this tutorial!
Click to expand...
Click to collapse
As of right now, magisk 25.2 works much better than magisk 26.1. You can continue to use it if you dont face any issues.
I believe I followed all the steps correctly including downgrading to magisk 25.2, the only step that I might not have followed correctly would be using hidemyapplist, but I'm getting CTS profile mismatch in microG safetynet attestation test. I have an LE2115 with lineageos 20 (specifically lineage-20.0-20230514-nightly-lemonade-signed.zip). I do get the "orange state" warning when I turn on my phone, I could make that go away by flashing an older version something (I forgot what but I've done it before) in TWRP but I wanted to avoid that since the only APPARENT effect is the orange state warning and I don't know if it will break later in LOS as they keep updating. I'd appreciate any help you could give me to fix this.
EDIT: just used magiskhidepropsconf and edit fingerprint and set it to htc exodus and now I pass all tests.
I just rooted my phone and wanted to put out there how I got my bank (Santander UK) app working.
Hiding Magisk, using the Deny List and Zygisk, and using the Universal SafetyNet Fix package did not work.
What did work was using the Shelter app to create a sandbox and installing the Santander app in that.
Edit: It stopped working after a while, and I'm not quite sure why it worked at all in the sandbox when it wasn't unsandboxed. The phone passes safetynet so it ain't that. I'm wondering if its detecting the unlocked bootloader in some other way, and not the root.
Eavolution said:
I just rooted my phone and wanted to put out there how I got my bank (Santander UK) app working.
Hiding Magisk, using the Deny List and Zygisk, and using the Universal SafetyNet Fix package did not work.
What did work was using the Shelter app to create a sandbox and installing the Santander app in that.
Click to expand...
Click to collapse
Man! I wanted to use Shelter on my stock A52 4G to put proprietary apps in, but since it's had a custom OS on it before I can't use work accounts anymore. When I go back to LOS I'll have to try this, thanks!
@Eavolution what rooted phone/OS do you have? I'm unable to install Shelter on my rooted SG10Exynos/OS9 and get the same "Cannot create work profile.. a custom OS has been installed"
nukescript said:
@Eavolution what rooted phone/OS do you have? I'm unable to install Shelter on my rooted SG10Exynos/OS9 and get the same "Cannot create work profile.. a custom OS has been installed"
Click to expand...
Click to collapse
I'm on a redmi note 10 pro, rooted using a magisk modified boot.img with an unlocked bootloader on miui14, android 13. Weirdly the banks app only worked for a bit then put up a warning again and wouldn't let me use it. I wonder why it worked for a bit in a sandbox but not unsandboxed, and how it clocked from within the sandbox that the thing was rooted.
My phone passes safetynet with magisk set up how it is so it ain't using that, I have a suspicion that it's not detecting the root, but the unlocked bootloader.
I've got issues with both Barclays & Santander apps. I pass SafetyNet with the help of Magisk 26.0 & safetynet-fix-v2.4.0-MOD_1.2. It's the Play Integrity API that I cant bypass, and that these banking apps are using.
I have the same issue with Barclays App.
I found that using Magisk Delta, Barclays works again.
Unfortunately, Google Wallet doesn't work with Magisk Delta; it can detect root, but with the official version of Magisk Google Wallet works.
Basically:
Magisk Delta: Barclays works and Google Wallet doesn't work
Official Magisk: Barclays doesn't work (error 00006) and Google Wallet works
edit:
I'm on Samsung Galaxy A71 with Android 13 (Secirity patch level 1 April 2023)
These are the two Magisk setups I used:
Magisk v26.1 (Barclays doesn't work - Google Wallet Works)
MagiskHide Props Config v6.1.2-v137 (installed using this guide https://forum.xda-developers.com/t/magisk-google-wallet-pay-with-magisk.4471279/page-7)
Universal SafetyNet Fix v2.4.0 installed and enabled
Zygisk enabled
Enforce DenyList enabled
Magisk App hidden
Magisk Delta 25210 (Barclays works - Google Wallet doesn't work)
MagiskHide Props Config v6.1.2-v137 (installed using this guide https://forum.xda-developers.com/t/magisk-google-wallet-pay-with-magisk.4471279/page-7)
Universal SafetyNet Fix v2.4.0 installed and enabled
Zygisk enabled
Enforce SuList enabled
Magisk Delta App hidden
xsecret said:
I have the same issue with Barclays App.
I found that using Magisk Delta, Barclays works again.
Unfortunately, Google Wallet doesn't work with Magisk Delta; it can detect root, but with the official version of Magisk Google Wallet works.
Basically:
Magisk Delta: Barclays works and Google Wallet doesn't work
Official Magisk: Barclays doesn't work (error 00006) and Google Wallet works
edit:
I'm on Samsung Galaxy A71 with Android 13 (Secirity patch level 1 April 2023)
These are the two Magisk setups I used:
Magisk v26.1 (Barclays doesn't work - Google Wallet Works)
MagiskHide Props Config v6.1.2-v137 (installed using this guide https://forum.xda-developers.com/t/magisk-google-wallet-pay-with-magisk.4471279/page-7)
Universal SafetyNet Fix v2.4.0 installed and enabled
Zygisk enabled
Enforce DenyList enabled
Magisk App hidden
Magisk Delta 25210 (Barclays works - Google Wallet doesn't work)
MagiskHide Props Config v6.1.2-v137 (installed using this guide https://forum.xda-developers.com/t/magisk-google-wallet-pay-with-magisk.4471279/page-7)
Universal SafetyNet Fix v2.4.0 installed and enabled
Zygisk enabled
Enforce SuList enabled
Magisk Delta App hidden
Click to expand...
Click to collapse
Does this still work for you with latest barclays app?
first_damned said:
Does this still work for you with latest barclays app?
Click to expand...
Click to collapse
Actually I found a workaround, I'm currently using Magisk Alpha (26100) + Universal SafetyNet Fix (v2.4.0-MOD_1.2), and now I can use both Google Wallet and Barclays (latest version v2.79.0).
I think the modded version of Universal SafetyNet Fix fixed the problem, I think it works with Magisk Delta too (but I haven't tested it).
[MODULE] [MOD] Universal SafetyNet Fix
Universal SafetyNet Fix [MOD] Magisk module Hello. This is my modification [FORK] of the original Universal SafetyNet Fix module from @kdrag0n. Created for the (temporary?) restoration of working capacity in the conditions of constant change...
forum.xda-developers.com
xsecret said:
Actually I found a workaround, I'm currently using Magisk Alpha (26100) + Universal SafetyNet Fix (v2.4.0-MOD_1.2), and now I can use both Google Wallet and Barclays (latest version v2.79.0).
I think the modded version of Universal SafetyNet Fix fixed the problem, I think it works with Magisk Delta too (but I haven't tested it).
[MODULE] [MOD] Universal SafetyNet Fix
Universal SafetyNet Fix [MOD] Magisk module Hello. This is my modification [FORK] of the original Universal SafetyNet Fix module from @kdrag0n. Created for the (temporary?) restoration of working capacity in the conditions of constant change...
forum.xda-developers.com
Click to expand...
Click to collapse
Soumds promising. Please can you detail exactly what you did to get it working? And how did you install magisk alpha? Also on which rom does this work on? As I want to use it on lineage os. Thank you in advance this is very much appreciated!
first_damned said:
Soumds promising. Please can you detail exactly what you did to get it working? And how did you install magisk alpha? Also on which rom does this work on? As I want to use it on lineage os. Thank you in advance this is very much appreciated!
Click to expand...
Click to collapse
There's not much to explain, I just rooted my Galaxy A71 (with Android 13) following this guide:
How to Install Magisk on your Android Phone
Magisk is a powerful tool that can help you customize some aspects of your phone or even grant you root access. Here's how you can install it!
www.xda-developers.com
Then I installed Magisk Alpha v26.1 (when prompted, give root permissions to Magisk Alpha)
GitHub - vvb2060/magisk_files
Contribute to vvb2060/magisk_files development by creating an account on GitHub.
github.com
Then in Magisk Alpha I enabled the Zygisk and Enforce DenyList settings.
Then in Magisk Alpha under Configure DenyList settings select all the apps you want to hide the root, I suggest all your banking apps, Google Play Store, Google Services Framework, Google Wallet.
Some apps are not visible, so you need to turn on the Show system apps setting.
Then hide your Magisk Alpha app, so select Settings>Hide the Magisk app
Then I uninstalled Magisk (official), before uninstall Magisk (official) make sure that Magisk Alpha is correctly installed, otherwise you will lose the root and have to start from the beginning, so just make sure that (in Magisk Alpha) next to Zygisk and Ramdisk it says Yes.
Then I installed the Universal SafetyNet Fix v2.4.0 [MOD_1.3] module in Magisk Alpha:
Releases · Displax/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - Displax/safetynet-fix
github.com
Just download the zip file, and go Magisk Alpha>Modules>Install from storage and select the zip file to install the safety net fix, and reboot your phone.
By the way I just reinstalled Magisk (Official) v26.1 + SafetyNet v2.4.0 MOD_1.3, but Barclays app immediately detected the root (Google Wallet works), I guess Barclays implemented some algorithm to detect Magisk (official), maybe some files that are only present when Magisk (official) is installed?
Other tests I've done:
Barclays App works even if you don't hide Magisk Alpha app.
Barclays App works even if you don't uninstall Magisk (official), so if Magisk Alpha is installed and it's your root manager and Magisk (official) is installed without being your root manager, Barclays app still works.
Barclays App works event SafetyNet Fix module is not enabled (in Magisk Alpha), this module is used to make Google Wallet work
In the DenyList it is sufficient to enable the activities com.barclays.android.barclaysmobilebanking and com.barclays.android.barclaysmobilebanking_zygote, if you leave the other 3 activities disabled Barclays app will continue to work without detecting the root.
xsecret said:
There's not much to explain, I just rooted my Galaxy A71 (with Android 13) following this guide:
How to Install Magisk on your Android Phone
Magisk is a powerful tool that can help you customize some aspects of your phone or even grant you root access. Here's how you can install it!
www.xda-developers.com
Then I installed Magisk Alpha v26.1 (when prompted, give root permissions to Magisk Alpha)
GitHub - vvb2060/magisk_files
Contribute to vvb2060/magisk_files development by creating an account on GitHub.
github.com
Then in Magisk Alpha I enabled the Zygisk and Enforce DenyList settings.
Then in Magisk Alpha under Configure DenyList settings select all the apps you want to hide the root, I suggest all your banking apps, Google Play Store, Google Services Framework, Google Wallet.
Some apps are not visible, so you need to turn on the Show system apps setting.
Then hide your Magisk Alpha app, so select Settings>Hide the Magisk app
Then I uninstalled Magisk (official), before uninstall Magisk (official) make sure that Magisk Alpha is correctly installed, otherwise you will lose the root and have to start from the beginning, so just make sure that (in Magisk Alpha) next to Zygisk and Ramdisk it says Yes.
Then I installed the Universal SafetyNet Fix v2.4.0 [MOD_1.3] module in Magisk Alpha:
Releases · Displax/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - Displax/safetynet-fix
github.com
Just download the zip file, and go Magisk Alpha>Modules>Install from storage and select the zip file to install the safety net fix, and reboot your phone.
By the way I just reinstalled Magisk (Official) v26.1 + SafetyNet v2.4.0 MOD_1.3, but Barclays app immediately detected the root (Google Wallet works), I guess Barclays implemented some algorithm to detect Magisk (official), maybe some files that are only present when Magisk (official) is installed?
Other tests I've done:
Barclays App works even if you don't hide Magisk Alpha app.
Barclays App works even if you don't uninstall Magisk (official), so if Magisk Alpha is installed and it's your root manager and Magisk (official) is installed without being your root manager, Barclays app still works.
Barclays App works event SafetyNet Fix module is not enabled (in Magisk Alpha), this module is used to make Google Wallet work
In the DenyList it is sufficient to enable the activities com.barclays.android.barclaysmobilebanking and com.barclays.android.barclaysmobilebanking_zygote, if you leave the other 3 activities disabled Barclays app will continue to work without detecting the root.
Click to expand...
Click to collapse
Works top man!
Another test I did:
Barclays works even if Zygisk is disabled, but Google Wallet will not work because Universal Fix will be suspended, as this module requires Zygisk to work