So a year ago i rooted my OnePlus 8t and i still have oos 13 anyway I'm trying to bypass postfinance root check but anything seems to work (zygisk block , shamiko , securitynet tried) on yasnac it runs the check perfectly and i tried to cancel the cache and the memory many times but anything...
There are any other options or i must deroot the phone?
NewNoSignal said:
So a year ago i rooted my OnePlus 8t and i still have oos 13 anyway I'm trying to bypass postfinance root check but anything seems to work (zygisk block , shamiko , securitynet tried) on yasnac it runs the check perfectly and i tried to cancel the cache and the memory many times but anything...
There are any other options or i must deroot the phone?
Click to expand...
Click to collapse
So I know nothing of OnePlus (I've only experience in Samsung & Pixels), so I don't know if any of the following suggestions work on your phone.....
First of all, safetynet is becoming depreciated and will become completely depreciated by '24; what many apps now use for "safety" detection is Play Integrity API -- in which using the Play Integrity API Checker app or more comprehensive root checker TB Checker is a better way to see how your device passes established safety checks more than YASNAC and passing them (or certain checks) may be required to get your app running with root.
Among Zygisk DenyList and Shamiko as viable root hiding methods, there is also
Magisk Delta [Magisk fork] (which returns Magisk Hide),
UniversalSafetyNetFix [Magisk module] (if main branch isn't successful, Displax's fork often times is more successful),
HideMyApplist (HMA) [LSPosed module],
Bootloader Spoofer [Xposed module] (to spoof locked bootloader) {this method is new}.
Also, hopefully you are employing Shamiko correctly where you configure the Zygisk DenyList but do not enable/Enforce it -- if that interferes, apparently there is a "whitelist" mode for Shamiko.
P.S. Also, I hope you've also made sure to Hide Magisk (essentially renaming the app manager name) in settings -- you never mentioned doing this in the OP...
I've read these other methods have fairly good success particularly on banking apps where Zygisk DenyList and Shamiko don't...
sometimes you have to try/work them in different combinations with each other to get it passed....
Again, I do not know if any of these work with your device, so I suggest going through their respective threads (if they have one in your device's subforum, that would be best) to see if/how they work with your device and/or you could post & inquire if/how they do/might....
simplepinoi177 said:
So I know nothing of OnePlus (I've only experience in Samsung & Pixels), so I don't know if any of the following suggestions work on your phone.....
First of all, safetynet is becoming depreciated and will become completely depreciated by '24; what many apps now use for "safety" detection is Play Integrity API -- in which using the Play Integrity API Checker app or more comprehensive root checker TB Checker is a better way to see how your device passes established safety checks more than YASNAC and passing them (or certain checks) may be required to get your app running with root.
Among Zygisk DenyList and Shamiko as viable root hiding methods, there is also
Magisk Delta [Magisk fork] (which returns Magisk Hide),
UniversalSafetyNetFix [Magisk module] (if main branch isn't successful, Displax's fork often times is more successful),
HideMyApplist (HMA) [LSPosed module],
Bootloader Spoofer [Xposed module] (to spoof locked bootloader) {this method is new}.
Also, hopefully you are employing Shamiko correctly where you configure the Zygisk DenyList but do not enable/Enforce it -- if that interferes, apparently there is a "whitelist" mode for Shamiko.
P.S. Also, I hope you've also made sure to Hide Magisk (essentially renaming the app manager name) in settings -- you never mentioned doing this in the OP...
I've read these other methods have fairly good success particularly on banking apps where Zygisk DenyList and Shamiko don't...
sometimes you have to try/work them in different combinations with each other to get it passed....
Again, I do not know if any of these work with your device, so I suggest going through their respective threads (if they have one in your device's subforum, that would be best) to see if/how they work with your device and/or you could post & inquire if/how they do/might....
Click to expand...
Click to collapse
Ah yes i renamed it too now I'm going home and try all you just wrote i hope it works
Thanks for the help anyway
I don't install any of those apps.
Couldn't you simply login to the banking site using your browser?
blackhawk said:
I don't install any of those apps.
Couldn't you simply login to the banking site using your browser?
Click to expand...
Click to collapse
well in nnot that easy i have to scan a qr code from the app to somehow activate my account? i dont'know for sure i don't know german too well XD anyway is not that easy
NewNoSignal said:
well in nnot that easy i have to scan a qr code from the app to somehow activate my account? i dont'know for sure i don't know german too well XD anyway is not that easy
Click to expand...
Click to collapse
I just use passwords, the KISS principle.
I use a secure browser like Brave.
No issues in over 7 years. Login takes seconds.
simplepinoi177 said:
So I know nothing of OnePlus (I've only experience in Samsung & Pixels), so I don't know if any of the following suggestions work on your phone.....
First of all, safetynet is becoming depreciated and will become completely depreciated by '24; what many apps now use for "safety" detection is Play Integrity API -- in which using the Play Integrity API Checker app or more comprehensive root checker TB Checker is a better way to see how your device passes established safety checks more than YASNAC and passing them (or certain checks) may be required to get your app running with root.
Among Zygisk DenyList and Shamiko as viable root hiding methods, there is also
Magisk Delta [Magisk fork] (which returns Magisk Hide),
UniversalSafetyNetFix [Magisk module] (if main branch isn't successful, Displax's fork often times is more successful),
HideMyApplist (HMA) [LSPosed module],
Bootloader Spoofer [Xposed module] (to spoof locked bootloader) {this method is new}.
Also, hopefully you are employing Shamiko correctly where you configure the Zygisk DenyList but do not enable/Enforce it -- if that interferes, apparently there is a "whitelist" mode for Shamiko.
P.S. Also, I hope you've also made sure to Hide Magisk (essentially renaming the app manager name) in settings -- you never mentioned doing this in the OP...
I've read these other methods have fairly good success particularly on banking apps where Zygisk DenyList and Shamiko don't...
sometimes you have to try/work them in different combinations with each other to get it passed....
Again, I do not know if any of these work with your device, so I suggest going through their respective threads (if they have one in your device's subforum, that would be best) to see if/how they work with your device and/or you could post & inquire if/how they do/might....
Click to expand...
Click to collapse
I MADE IT was suficient to swap magisk and install universalsafetynetfix (i installed directly the displax's one)
thank you very very much
NewNoSignal said:
I MADE IT was suficient to swap magisk and install universalsafetynetfix (i installed directly the displax's one)
thank you very very much
Click to expand...
Click to collapse
GREAT!
Glad I helped you get there! I know how much of a relief it is to not need to unroot and/or relock the bootloader and have the phone be wiped (at least that's how it is on Samsung & Pixels)
Nice to know that USNF and Magisk Delta (I assume that's what you meant with "swap magisk") work well enough on OnePlus...
Related
All,
I've been fighting with this for a while and I swear that I'm doing everything right (at least, I think I am).
Here's what I'm running:
1. euro build
2. magisk 23.0 (canary build)
I go through the setup, oem unlock and reboot again. I always run into a problem with magisk patched img and safety net failing.
The threads out there have gotten too thick and off-topic with folks asking for other stuff unrelated to the task at hand. I'm beyond confused with all the threads and need a clean and cohesive approach. Again, people, I need a better direction on this. No one-liners and smart ass answers.
Thank you to those that respond with a solid tutorial. Go layman if need be. =)
Magisk is dropping support for hiding root access from apps
Magisk, the popular Android rooting tool, will continue to be developed by topjohnwu, but without its root hiding feature called MagiskHide.
www.xda-developers.com
I recommend following this YouTube tutorial step by step. Also, The Magisk 23.0 build STILL has MagiskHide at the moment, so you may want to enable that.
TL;DR, you'll have to install Riru, LSposed, and XPrivacyLua and their respective magisk modules. While the video showed how to pass SafetyNet and get Google Play "Device is Certified", you can implement the same processes to ANY app having issues with root.
dude6595 said:
Magisk is dropping support for hiding root access from apps
Magisk, the popular Android rooting tool, will continue to be developed by topjohnwu, but without its root hiding feature called MagiskHide.
www.xda-developers.com
Click to expand...
Click to collapse
Once again: Everything that counts is money!
There will be other devs presenting solutions for root and hiding root so that we won't need Magisk any longer.
Until then I'll stay with 23.0
Tried to follow ALL the methods for previous 6 roots and Gpay fixes and can't seem to find a method. Any ideas? I know this is a new phone so perhaps I have to wait, but just curious if there was somethign I may have missed. Followed this method:
fl3xtra said:
Tried to follow ALL the methods for previous 6 roots and Gpay fixes and can't seem to find a method. Any ideas? I know this is a new phone so perhaps I have to wait, but just curious if there was somethign I may have missed. Followed this method:
Click to expand...
Click to collapse
See this post and read the few pages before and after that to get an understanding of what is going on. Basically, Play Integrity API is replacing SafetyNet API so adjustments had to be made.
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Also this...
[Magisk] Google wallet (pay) with magisk
Saw on reddit that some people have issues with google pay, since the new update added some new checks. So here is what you do: - Update Magisk to 25.2, Update magisk app to 25.2 as well - Rename Magisk app if you havent already - [ OPTIONAL ]...
forum.xda-developers.com
I havent tried on this phone but every device I use I've had success with https://github.com/kdrag0n/safetynet-fix
tlxxxsracer said:
I havent tried on this phone but every device I use I've had success with https://github.com/kdrag0n/safetynet-fix
Click to expand...
Click to collapse
From what I read (I could be wrong), Google made changes to their authentication in June 2022.
I literally just got it to work 30 min ago. I followed instructions here: https://forum.xda-developers.com/t/...tynet-fix-2-3-1.4217823/page-91#post-87198517
Not sure if step #1 did anything since I don't have MagiskHidePropsConfig configured in any special way. I think it was the modded safetynet fix that did the trick.
Can you share your steps on rooting? Where did you get the boot.img?
Indian gpay or wallet gpay
z0mghii said:
Can you share your steps on rooting? Where did you get the boot.img?
Click to expand...
Click to collapse
I use a Verizon MVNO as my carrier so i downloaded the factory image that's already available on Google. Extracted boot.img from there.
I believe that not all factory images are available yet so you may have to wait if you don't use Verizon or Verizon mvno. (Might be available on Monday.)
Lughnasadh said:
See this post and read the few pages before and after that to get an understanding of what is going on. Basically, Play Integrity API is replacing SafetyNet API so adjustments had to be made.
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Also this...
[Magisk] Google wallet (pay) with magisk
Saw on reddit that some people have issues with google pay, since the new update added some new checks. So here is what you do: - Update Magisk to 25.2, Update magisk app to 25.2 as well - Rename Magisk app if you havent already - [ OPTIONAL ]...
forum.xda-developers.com
Click to expand...
Click to collapse
I got it to work. The one thing I did differently than some other guides is I changed my phone to a Pixel 4a under props config. Seems to work now and haven't had any issues.
Rooting this phone will be the same as every other Pixel phone. Of course rooting and keeping apps like banking and GPay is an ongoing battle between Google and developers. The requirement to root and use those apps will change as Google updates their security methods, but again that won't be a "per phone" issue, it will be the same methods for all rooted Pixel phones.
Any idea how this affects Felica models? (the ones sold in Japan)
fl3xtra said:
I got it to work. The one thing I did differently than some other guides is I changed my phone to a Pixel 4a under props config. Seems to work now and haven't had any issues.
Click to expand...
Click to collapse
That shouldn't be necessary, assuming you're not running some custom rom.
Anyway, I didn't do that, and google pay and wallet work fine on this phone using magisk with the stock android 13 rom.
Lughnasadh said:
See this post and read the few pages before and after that to get an understanding of what is going on. Basically, Play Integrity API is replacing SafetyNet API so adjustments had to be made.
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Also this...
[Magisk] Google wallet (pay) with magisk
Saw on reddit that some people have issues with google pay, since the new update added some new checks. So here is what you do: - Update Magisk to 25.2, Update magisk app to 25.2 as well - Rename Magisk app if you havent already - [ OPTIONAL ]...
forum.xda-developers.com
Click to expand...
Click to collapse
Folks, the answer is RIGHT HERE.
The issue is NOT device fingerprints or authentication. Google has deprecated the SafetyNet API for the new Play Integrity API, which makes it impossible to spoof an evaluationType of MEETS_STRONG_INTEGRITY.
The solution, as @Lughnasadh shared, is the modified Universal SafetyNet FIx module shared by Displax, which forces the system to use the legacy SafetyNet attestation. This is only a temporary solution, as the time may eventually come when Google removes support for SafetyNet altogether from their apps. There is no permanent solution, nor will there ever be, because spoofing hardware backed device integrity is not possible due to hardware key attestation and the Android Trusted Execution Environment.
I have zero interest in rooting my phone, but because 5G/VoLTE/VoWiFi are not supported in my country (Slovakia) I had to root it. After successful root, passing SafetyNet and pretty much make everything to work as expected, my Company Portal is detecting root when running Teams and Outlook provisioned by my Company Portal despite having them in DenyList. Is there anyone who managed to pass this?
Thank you.
Happened to me as well. I used Shamiko magisk module and it's all good now.
@chaos193, did you use Riru along?
Or maybe even better question if you don't mind - what modules are you using to successfully pass SafetyNet and hide root?
Can you list them one by one, please?
Either use Shamiko or MagiskHidePropsConf to mask additional properties. I can confirm that InTune Company Portal works fine with SafetyNetFix + Shamiko
p4ra said:
@chaos193, did you use Riru along?
Or maybe even better question if you don't mind - what modules are you using to successfully pass SafetyNet and hide root?
Can you list them one by one, please?
Click to expand...
Click to collapse
It's pretty much what @craigacgomez said. I used Shamiko 0.6 alongside LSposed zygisk release. I'm pretty sure LSposed is not needed but I have it just in case.
chaos193 said:
It's pretty much what @craigacgomez said. I used Shamiko 0.6 alongside LSposed zygisk release. I'm pretty sure LSposed is not needed but I have it just in case.
Click to expand...
Click to collapse
Quick question @chaos193 - I haven't updated Shamiko to 0.6 as the update states that it requires Magisk 25205+. Reckon that would be magisk canary? Or as you using 0.6 with Magisk stable?
WhoIsJohnGalt1979 said:
Quick question @chaos193 - I haven't updated Shamiko to 0.6 as the update states that it requires Magisk 25205+. Reckon that would be magisk canary? Or as you using 0.6 with Magisk stable?
Click to expand...
Click to collapse
I used it with magisk stable 25.2. I think we are all using magisk stable to root our phone right?
I have tried your suggestions, but still does not seem to work. Adding screenshots.
Can you help me, please? What is wrong with my setup?
Following steps work 100% - I had the same issue.
1. Use magisk canary.
2. Install universal safetynet fix MOD 2.0 from displax (Google for "displax github")
3. Use latest shamiko module
4. Activate zygisk
5. Don't enforce denylist
6. Go to denylist and chose all Microsoft apps and tick ALL options for each app.
7. Hide magisk app
I had issue with a specific banking app which detects root by most of the methods. I made it working by using shamiko + airfrozen which i was not really liking.
Now i wnded up with a forked project of magisk bu Husky called magisk delta which brought back magisk hide along with zygisk. With this i don't need shamiko, magiskpropshide, airfrozen or any modules for hiding the root from apps. Yes for safetynet you can use the modded veraion by D. Below is the link. If you are interested have a look at Magisk Delta by HuskyDG... I use the magisk delta canary builds...
I have made it work with first approach. I did a restart of the phone and it worked.
What I am wondering though is the following - I have used the VoLTE/VoWiFi/5G Magisk module, but I don't see the "HD" icon during the call, even though I can browse the internet (when I am not on WiFi). And despite 5G coverage of my current carrier in my area, I don't see 5G icon.
Is there any other module I am missing for this last piece of puzzle?
And last but not least. What scares me the most is that next OTA will completely screw me over after setting everything up. I wish there was a clear tutorial on how to OTA and keep the root without wiping everything out.
p4ra said:
I have made it work with first approach. I did a restart of the phone and it worked.
What I am wondering though is the following - I have used the VoLTE/VoWiFi/5G Magisk module, but I don't see the "HD" icon during the call, even though I can browse the internet (when I am not on WiFi). And despite 5G coverage of my current carrier in my area, I don't see 5G icon.
Is there any other module I am missing for this last piece of puzzle?
And last but not least. What scares me the most is that next OTA will completely screw me over after setting everything up. I wish there was a clear tutorial on how to OTA and keep the root without wiping everything out.
Click to expand...
Click to collapse
I'm not quite sure which VoLTE/VoWiFi/5G Magisk module you are referring to, but I believe enabling 5G requires modified mbn files specific to your country/region.
Regarding OTAs, there are two "How To" guides here with all the details you need.
Blaze1001 said:
Following steps work 100% - I had the same issue.
1. Use magisk canary.
2. Install universal safetynet fix MOD 2.0 from displax (Google for "displax github")
3. Use latest shamiko module
4. Activate zygisk
5. Don't enforce denylist
6. Go to denylist and chose all Microsoft apps and tick ALL options for each app.
7. Hide magisk app
Click to expand...
Click to collapse
I have done exactly this but it still detects
Oneplus 7 pro
LineageOS 19.1 Nov 27th nightly build
This should be all that's needed to pass the compliance checks for Intune
1. Magisk (Zygisk mode)
2. SafetyNet v2.3.1-MOD_2.0
3. Shamiko v0.5.1 (or higher)
4. Magisk deny-list for the following apps (without Enforce deny-list)
a. Company Portal (Intune)b. Microsoft Authenticator (if you use it)c. Microsoft Defender (if you use it)5. Make sure you clear app data for the apps in the deny list after adding them to the deny list
Don't know about this specific app, but in the past I had issues with detection of an "unsecure" device, that was related to ADB debugging being enabled in developer settings...
craigacgomez said:
This should be all that's needed to pass the compliance checks for Intune
1. Magisk (Zygisk mode)
2. SafetyNet v2.3.1-MOD_2.0
3. Shamiko v0.5.1 (or higher)
4. Magisk deny-list for the following apps (without Enforce deny-list)
a. Company Portal (Intune)b. Microsoft Authenticator (if you use it)c. Microsoft Defender (if you use it)5. Make sure you clear app data for the apps in the deny list after adding them to the deny list
Click to expand...
Click to collapse
s3axel said:
Don't know about this specific app, but in the past I had issues with detection of an "unsecure" device, that was related to ADB debugging being enabled in developer settings...
Click to expand...
Click to collapse
Still doesn't work. Its weird because it worked for one night and the next morning it stopped.
UPDATE: its LSPosed I think. But this is the only way to force dark mode on some apps....
UPDATE 2: I disabled forced dark mode on all Microsoft apps in LSPosed plugin and its looking good so far...
UPDATE 3: Had a full day with not a single root detection notification. Looks solid!
s3axel said:
Don't know about this specific app, but in the past I had issues with detection of an "unsecure" device, that was related to ADB debugging being enabled in developer settings...
Click to expand...
Click to collapse
one of the worse parts of it, if not the worst, is that nobody knows what it detects and there's no guide that applies to each and every device,
I tried in 3 devices, the exact same steps and files, etc, it worked on the 1st one, but on the other two.. no!
For all those who still got issues as another idea: Does Google Wallet work ? Is the device play protect certified ?
I ask because to get Wallet to work (and presumably other apps that rely on Safetynet and/or Play Protect certification) the additional step after #5 in the list above is: clear data for Google Play Services and Google Play Store, then reboot (your device will ask for Google backup configuration again).....
I got the same issue with an App called "SwissID". It recognizes magisk for some reason. All other Apps work (like banking, google wallet etc.)
chaos193 said:
It's pretty much what @craigacgomez said. I used Shamiko 0.6 alongside LSposed zygisk release. I'm pretty sure LSposed is not needed but I have it just in case.
Click to expand...
Click to collapse
Its work to me!!! Thanks
Hi All,
I have recently updated Barclays mobile app on my OnePlus 6 rooted running LOS 19 but the app today detected the root (probably the latest update enable that). So I have cleared the data and cache however I cannot go through the menu to access my account and I get error 00006 now.
I have magisk hide enabled and this has been working with Barclays and the other banking app for a year now (excluding Santander which detects the root anyway)
Do you have any suggestions, please?
I'm in the same boat. Magisk delta with zygisk and app hidden etc etc incl. deny list latest Barclays app still detects root. Have even tried deleting Fox folder, in case it starts seeing that recovery folder. Tried lastest canary build, still the same. Anyone had success with running the latest Barclays app rooted? Poco F3 user BTW, but the principles should be the same...
Do you know if removing the root (magisk) fixes the issue?
reg66 said:
I'm in the same boat. Magisk delta with zygisk and app hidden etc etc incl. deny list latest Barclays app still detects root. Have even tried deleting Fox folder, in case it starts seeing that recovery folder. Tried lastest canary build, still the same. Anyone had success with running the latest Barclays app rooted? Poco F3 user BTW, but the principles should be the same...
Click to expand...
Click to collapse
danc.940 said:
Do you know if removing the root (magisk) fixes the issue?
Click to expand...
Click to collapse
Nope, haven't tried yet... But i'm guessing after removing root and clearing app data it would work...
reg66 said:
Nope, haven't tried yet... But i'm guessing after removing root and clearing app data it would work...
Click to expand...
Click to collapse
Actually, the app might still recognise custom rom. Can't face stock miui just over banking app. What a blow
reg66 said:
Actually, the app might still recognise custom rom. Can't face stock miui just over banking app. What a blow
Click to expand...
Click to collapse
Is there a way to hide also the unlocked bootloader? We won't know until we try it I guess. There is also a Reddit post where many people seem to have the same problem.
Keep an eye on that too until we find a solution.
Do you know where we could get the version of the app that still works with magisk? Is it possible to export the app? Maybe we can find someone with an old version and ask them to share the apk?
A way to roll back has been posted by u/SuzannaBadger in the Reddit thread, pasting here for visibility:
Hi,
I've found a temp fix for this for now.
Steps are as below:
1. Uninstall the current Barclays banking app.
2. Go to play store,settings,network settings and turn off 'auto update apps'
3. Download the old Barclays app from: https://barclays-bank-plc-banking.en.uptodown.com/android/download (it's legit)
4. Install the app.
5. Go into Majisk, settings, configure denylist and tick all Barclays options (may already be ticked, if this is the case ignore step 5)
6. Restart phone.
7. Open Barclays app and setup as you usually would.
Hopefully this works for you. Applist detector is even detecting I have the Majisk app (even though I have Shamiko and have hidden it) but the Barclays app still works as it's the previous version.
Click to expand...
Click to collapse
reg66 said:
Actually, the app might still recognise custom rom. Can't face stock miui just over banking app. What a blow
Click to expand...
Click to collapse
Is there a way to hide also the unlocked bootloader? We won't know until we try it I guess. There is also a Reddit post where many people seem to have the same problem.
https://www.reddit.com/r/Magisk/comments/118yl7n
Keep an eye on that too until we find a solution.
Do you know where we could get the version of the app that still works with magisk? Is it possible to export the app? Maybe we can find someone with an old version and ask them to share the apk?
Jenpyon said:
A way to roll back has been posted by u/SuzannaBadger in the Reddit thread, pasting here for visibility:
Click to expand...
Click to collapse
Great thanks for the update.
danc.940 said:
Is there a way to hide also the unlocked bootloader? We won't know until we try it I guess. There is also a Reddit post where many people seem to have the same problem.
Keep an eye on that too until we find a solution.
Do you know where we could get the version of the app that still works with magisk? Is it possible to export the app? Maybe we can find someone with an old version and ask them to share the apk?
Click to expand...
Click to collapse
Not sure about hiding unlock BL, never looked into it. If you've used the linked 2.72.2 barclays app, as i have, be sure to disable auto update in google playstore
EDIT: just seen it in step 2!! however, i just selected do not auto update for that specific app, rather than all apps
danc.940 said:
Do you know if removing the root (magisk) fixes the issue?
Click to expand...
Click to collapse
Yes it does fix the issue. I've checked and now have a hard choice of either restore magisk needing BCR heavily.
danc.940 said:
Is there a way to hide also the unlocked bootloader? We won't know until we try it I guess. There is also a Reddit post where many people seem to have the same problem.
Keep an eye on that too until we find a solution.
Do you know where we could get the version of the app that still works with magisk? Is it possible to export the app? Maybe we can find someone with an old version and ask them to share the apk?
Click to expand...
Click to collapse
Hiding unlocked bootloader most likely wouldn't help as just removing Magisk leaving bootloader unlocked makes Barclays app working perfectly. So they still just detect root and Magisk some other way. What was interesting was that when I removed Magisk and Barclays functionality was restored I run hidden Magisk app to restore Magisk. It asked to restore main Magisk app that I did. And even without restoring Magisk partition and rebooting Barclays stopped working having only Magisk app installed without root.
reg66 said:
I'm in the same boat. Magisk delta with zygisk and app hidden etc etc incl. deny list latest Barclays app still detects root. Have even tried deleting Fox folder, in case it starts seeing that recovery folder. Tried lastest canary build, still the same. Anyone had success with running the latest Barclays app rooted? Poco F3 user BTW, but the principles should be the same...
Click to expand...
Click to collapse
Try downloading an app called Ice Box and freeze Magisk with it.
That fixed the issue for the bank app I use.
See my replies here guys Post
All I've posted my notes on the reddit page above
Also I have a Santander account and I could never get this app working either!!!
Note this method still doesn't work on Santander!!
sound2005 said:
See my replies here guys Post
All I've posted my notes on the reddit page above
Also I have a Santander account and I could never get this app working either!!!
Note this method still doesn't work on Santander!!
Click to expand...
Click to collapse
Followed steps exactly. Still root is detected
reg66 said:
Followed steps exactly. Still root is detected
Click to expand...
Click to collapse
Thanks for replying back.
What issues did you get, ie FC, root detected etc..?
I'm going to keep trying on my phone and see if I can get this working
Ok guys, this method works 100%!!!
Test on my Samsung Note 8 (Android 10, Custom Rom)
Install this module:
GitHub - HuskyDG/MagiskHide at v1.6
Portable MagiskHide. Contribute to HuskyDG/MagiskHide development by creating an account on GitHub.
github.com
and wipe Barclays data, thats it!!!
Best to have Zygisk off and configure the denylist to get this working
Configure Magisk apps
As Magisk app does not allow you to configure denylist when zygisk is off. You must toggle Zygisk on temprorily (not reboot) to configurate denylist and toggle Zygisk off after done.
Note that any modules that uses Zygisk will be disabled!!
sound2005 said:
Ok guys, this method works 100%!!!
Test on my Samsung Note 8 (Android 10, Custom Rom)
Install this module:
GitHub - HuskyDG/MagiskHide at v1.6
Portable MagiskHide. Contribute to HuskyDG/MagiskHide development by creating an account on GitHub.
github.com
and wipe Barclays data, thats it!!!
Best to have Zygisk off and configure the denylist to get this working
Configure Magisk apps
As Magisk app does not allow you to configure denylist when zygisk is off. You must toggle Zygisk on temprorily (not reboot) to configurate denylist and toggle Zygisk off after done.
Note that any modules that uses Zygisk will be disabled!!
Click to expand...
Click to collapse
I'd tried this with Zygisk off but then USNF had become off and device didn't pass Safetynet. Then with Zygisk on and this module on Barclays still showed 0006. Denylist was configured for Barclays and not enforced.
atreal said:
I'd tried this with Zygisk off but then USNF had become off and device didn't pass Safetynet. Then with Zygisk on and this module on Barclays still showed 0006. Denylist was configured for Barclays and not enforced.
Click to expand...
Click to collapse
Try switching Zygisk on and off.
Reboot phone, wipe data and cache for play store and Barclays and try again mate
sound2005 said:
Try switching Zygisk on and off.
Reboot phone, wipe data and cache for play store and Barclays and try again mate
Click to expand...
Click to collapse
Well. Have to put thoroughly what exactly I meant been done.
1. Added Magiskhide module to Magisk and turned it on. Magisk was last stable 25.2
2. Uninstalled Barclays. Installed Barclays without running it yet.
3. Add Barclays to Denylist. Turn Zygisk off.
Reboot
4. Checked Safetynet with YASNAC. It failed. Checked modules page in Magisk - USNF was off apparently as Zygisk was off. YASNAC had been passed before all this attempts with this module when USNF was on.
4. Run Barclays - 0006.
5. Clear Barclays data. Turn Zygisk on in Magisk.
Reboot
6. YASNAC passed as USNF became on.
7. Run Barclays - 0006
And may I ask to give some light on what is meant that "it is better to keep Zygisk off". What does this "better" mean? Must be off? Then how do they mean to bypass Safetynet with USNF off?
atreal said:
Well. Have to put thoroughly what exactly I meant been done.
1. Added Magiskhide module to Magisk and turned it on. Magisk was last stable 25.2
2. Uninstalled Barclays. Installed Barclays without running it yet.
3. Add Barclays to Denylist. Turn Zygisk off.
Reboot
4. Checked Safetynet with YASNAC. It failed. Checked modules page in Magisk - USNF was off apparently as Zygisk was off. YASNAC had been passed before all this attempts with this module when USNF was on.
4. Run Barclays - 0006.
5. Clear Barclays data. Turn Zygisk on in Magisk.
Reboot
6. YASNAC passed as USNF became on.
7. Run Barclays - 0006
And may I ask to give some light on what is meant that "it is better to keep Zygisk off". What does this "better" mean? Must be off? Then how do they mean to bypass Safetynet with USNF off?
Click to expand...
Click to collapse
Hi
By all means you can try my setup:
Modules enabled:
Magiskhide (by Husky)
Magiskhide Props Config
Systemless host
Magisk v25.2 hidden
Denylist has been configured and Zygisk switch is off.
In Denylist I have the following as blocked:
Google play store
Google play services
My bank app
Oysercard app
Please note I've messed around extensively trying to get this to work and a lot of stuff I've added and remove to test out, so some modules (or even apps on the denylist) may no longer need to be there.
Also on step 3, could you turn Zygisk on (the app will tell you to reboot to apply changes) but do not reboot yet!!!, then turn off Zygist then reboot your phone.
Once rebooted clear cache and data for play store and Barclays
Then try banking app again.
If this still doesn't work, you may have a module triggering Barclays to recognise you have root, in which case you may need to disable/remove said modules.
One prime culprit would be Lsposed, if you have this then remove this as well.
Also please note, taken from developers site:
Configure Magisk apps
As Magisk app does not allow you to configure denylist when zygisk is off. You must toggle Zygisk on temprorily (not reboot) to configurate denylist and toggle Zygisk off after done.
Barclays App used to work just fine until about one week ago, when the latest version has been pushed. And they are now switching to an app-only authentication method (no more SMS, no more PINSentry, and definitely not possible through their website). So, if the app can't be used, I will have to either stop using root (which has been really helpful so far), or find a different bank which has an app that works (I believe it's very unlikely).
The Barclays App Version is: 2.73.2 , released in 16/02/2023
Specs:
OnePlus 7
Android 11 (OOS 11.0.2.1GM57BA)
Unlocked Bootloader
TWRP
Rooted with Magisk (25.2):
magisk app hidden
Zygisk enabled
enforce deny list: Enabled (I tried with enabled and disabled)
Deny List:
ALL Google stuff (absolutely anything that had "google" in their name)
Phone (just for safety, I added everything related to phone and dialer)
Barclays App
Magisk Modules:
App Systemizer v17.3.1
Buybox for Android NDK v1.3.4.1
Debloater (Terminal Emulator) v17.3.3
Disable Screenshot Camera Sounds v1.4
Energized Protection v1.3.5
Magisk Hide Props Config v6.12
OnePlus 7 Volume Booster Mod v2
OOS11 Debloater v7
Shamiko v0.6
Systemless Hosts 1.0 (Magisk)
Universal SafetyNet Fix (kdrag0n, modded by Displax) v2.3.1
Play Integrity API Checker:
device integrity: YES
basic integrity: YES
strong integrity: NO
What is happening:
Barclays App is starting
It prompts for registration (asks to set up a PIN)
Throws Error 00006 (which, after some research, seems to be related to Root)
What I did:
Looked for TWRP folder to delete it (I couldn't find it, perhaps I deleted it in the past, however if you can point me to all possible locations where it could be, I'd greatly appreciate it)
Tried both Shamiko and Universal SafetyNet Fix
Deleted storage, cache, from google, barclays, reboot, even uninstalled and reinstalled apps, all the works...
I tried with both Enforce Deny List Enabled and Disabled
Nothing of the above helped with making Barclays App work. Any Suggestions?
Best option atm is use the last version of the Barclays app which still worked (2.72.2) and disable auto update.
Any official way to get the 2.27.2 version? Obviously, because is a banking app, I don't trust mirrors and unofficial repos.
Thanks.
derei said:
Any official way to get the 2.27.2 version? Obviously, because is a banking app, I don't trust mirrors and unofficial repos.
Thanks.
Click to expand...
Click to collapse
https://barclays-bank-plc-banking.en.uptodown.com/android/download/90801956
That is the one I used. I understand your concerns, I was in the same boat before I downloaded it.. But I really need the app working myself. Worked fine though..