Database Develop

Magisk vs Banking Apps

Hi All,
I am experiencing issues with certain banking apps.
Starling Bank
and
Barclays
These two will not run however other banking apps do.
I have Magisk 17.1 running perfectly with Magisk hide turned on for those apps and changed the package name of Magisk manager and even tried uninstalling the manager as a test.
CTS Profile and SafteyNet are both passed and eveything else is working for all other apps.
Has anybody else had experience with these 2 apps ?
Im thinking maby they are detecting certain root applications but i have no idea how to find out which one i should try to uninstall.
Any help/advice/assistance would be greatly appreciated.
Thanks

Tried Magisk hide?
Edit: Never mind, didn't read that part. Try uninstalling Magisk completely.
Edit 1: Did you try clearing the app's data after hiding? The apps "remember" that the device is rooted.

I had tried uninstalling magisk using the uninstaller zip so i was completely unrooted and still didnt work that was also after clearing the app data and i ahve also tried uninstalling the apps then reinstalling them, because of this i think they have some root apps detection for example maby if titanium backup is installed it wont run. The problem is how do i know which apps its checking for i have lots of apps on my phone 500+ and to go through all root ones will take me ages. is there an easy way to find out ?
There is a thread here i have just found about this issue:
https://community.starlingbank.com/t/incorrect-android-root-detection/5068/246
even unrooted phones are being detected as rooted and its working for some with Magisk but not for others.
How do i go about getting the apps list that it detects as "unsafe"

Barclays vs Magisk
I have the same problem, magisk v17. 2, safetynet passes, but i cannot run absa bank (part of barclays). Anyone with a solution please?

Did you disable USB debug?

I've got them both running only with v16. On v17.1 or v17.2 only Barclycard.

Banks app detects root after update v18.0 (with Magisk Hide and hidden Manager)

Hi, thanks for reading.
I've used Magisk 17.3 with all my bank apps perfectly, with Magisk hide and Magisk manager hidden.
After update to 18.0 and update manager to 6.1, the bank apps start detecting root status, and stop working.
So, I've flashed back to 17.3 and old manager 6.0.1, and everything's back to working normally.
My system:
Poco F1
LineageOS 16.0 built 27/11/2018
The apps are from Thai's banks:
SCB EASY: detected root, still working
TMB Touch: detected root, stop working
KTB Next: detected root, working partially
If you'd want any log or anything, please also tell me how to get them.

Adios2nd said:
Hi, thanks for reading.
I've used Magisk 17.3 with all my bank apps perfectly, with Magisk hide and Magisk manager hidden.
After update to 18.0 and update manager to 6.1, the bank apps start detecting root status, and stop working.
So, I've flashed back to 17.3 and old manager 6.0.1, and everything's back to working normally.
My system:
Poco F1
LineageOS 16.0 built 27/11/2018
The apps are from Thai's banks:
SCB EASY: detected root, still working
TMB Touch: detected root, stop working
KTB Next: detected root, working partially
If you'd want any log or anything, please also tell me how to get them.
Click to expand...
Click to collapse
1.restore magisk manager with original package.
2.disable hide app.
3.reboot.
4.rehide msgisk manager.
5.rehide app.
6.reboot.
it work for nexus 6p.
Sent from my Nexus 6P using Tapatalk

Can confirm that this works, thanks.
For me, it started getting detected on 17.x even before updating to 18, right after the banking app (Sparkasse) was updated.
LG G6.

hsiehboss said:
1.restore magisk manager with original package.
2.disable hide app.
3.reboot.
4.rehide msgisk manager.
5.rehide app.
6.reboot.
it work for nexus 6p.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
This didn't work for me. I had to downgrade back to 17.1 to get my banking app working again. Appears that the root detection prevention is a regression in this latest version.
-- SSS

hsiehboss said:
1.restore magisk manager with original package.
2.disable hide app.
3.reboot.
4.rehide msgisk manager.
5.rehide app.
6.reboot.
it work for nexus 6p.
Click to expand...
Click to collapse
This doesn't work for me.
Did all of these...still got detected.

I have the same problem. Magisk says: ctsProfile: False and Google Pay don't work. Also my Banking App detects root.

I flashed today the latest Los 15 build and the crt false error is till there after flashing magisk 18. The same error is also with 17.4...

Tell me if I'm wrong but I believe we have two different reports: the original report where root is detected, and the ctsProfile/basicIntegrity failing. The second one is a regression fixed by rebooting device (however, it is annoying to reboot 10 times a day because suddenly SafetyNet fails for no reason).

I am using Magisk Hide Props module, and after 18.0 update Santander App detects root, even with Magisk Manager says I pass safetynet

It's happened with my bank app as it detected root & saftynet false and have to downgrade to ver.17.2
Sent from my SM-C900F using Tapatalk

See in install app delete old magisk manager, after install magisk 18.0 new magisk manager rename to manager.

I have same problem. After install v18 magisk, same bank app can detect the system is rooted. Downgrade to v17.2, all bank app become normal.

Same here since Magisk 18 my BankApp (Intesa Sanpaolo) start and says that there is a safety problem and it close, if I choose Magiskhide it doesn't start at all.
SafetyNet check spin without an end.
With Magisk 17.1 and 17.3 no problem at all.

Same problem here, after upgrading to Magisk 18 claiming to better hide root in the history, apps now suddenly detect root.
This affects also the Safety Net check and Google Pay... so far, Root Hiding in 18.0 seems COMPLETELY broken.
A solution would be great.

Later... after downgrading to Magisk 17.2, MagiskHide is working for me again and Safetynet checks succeed. The dev is aware of the problem, an issue is open on the Magisk Github (#907)

After uninstalling and reinstalling my bankapp now works without any problem and doesn't detect root even if is not under Magisk hide

I can confirm the v18 update breaks something and BOTH safety net checks fail. So all apps detect you are rooted, especially bank apps and Get Pay. Downgrading back to v17 restored everything to normal.
The only thing I could think of is the installation method. I did the direct install rather than installing the zip via recovery. Not sure if it makes a difference but I will wait for next release.
I am on a Pixel 2 with Android Pie updated to the Aug 2018 release.
---------- Post added at 12:47 PM ---------- Previous post was at 12:43 PM ----------
Harlock1978 said:
After uninstalling and reinstalling my bankapp now works without any problem and doesn't detect root even if is not under Magisk hide
Click to expand...
Click to collapse
I did not uninstall but tried clearing bank app data and cache and the problem persisted. Magisk still showing all red for safetyNet. Just sharing testing feedback.

@Djtrip83 Did you try just toggling MagiskHide off and on once after updating to v18? Sometimes MagiskHide simply needs a restart after an update...

I did that too. Toggled Hide on and off for all apps. Repackaged Magisk. Turned off USB debugging. Removed modules installed. Tried everything I thought would work. Even restored hosts in case Ad Away affected something on /system.
The only thing I did not do was remove root apps and re-install them to re-grant permissions after the Magisk update. And I wonder now if uninstalling Magisk completely and make a brand new clean install with v18 would work rather than upgrading.
I was at a loss so I downgraded. Sorry I don't have a log to share. However, v17 works fine.

Djtrip83 said:
I did that too. Toggled Hide on and off for all apps. Repackaged Magisk. Turned off USB debugging. Removed modules installed. Tried everything I thought would work. Even restored hosts in case Ad Away affected something on /system.
The only thing I did not do was remove root apps and re-install them to re-grant permissions after the Magisk update. And I wonder now if uninstalling Magisk completely and make a brand new clean install with v18 would work rather than upgrading.
I was at a loss so I downgraded. Sorry I don't have a log to share. However, v17 works fine.
Click to expand...
Click to collapse
We might be misunderstanding each other, but what I'm talking about is simply to go to the Manager settings and change the toggle for MagiskHide to off and then on. No need to do anything to the Hide list or anything else... Did you do that? As I said, that's sometimes something you the to do after an update, but it's rare.

Xposed causes Snapchat to temporarily lock account?

I have a Samsung Galaxy S6 SM-G920W8 with the UlTiMaTe NouGaT S8+ Full Port V3.1 ROM. I am rooted with Magisk V18.0, and have Snapchat enabled in Magisk Hide. Every time I install Xposed v89.3 by topjohnwu, I get a message from Snapchat team a few hours later saying that my account is being temporarily locked for 12+ hours. Is anyone else experiencing the same issue? Is there a way to stop this? Is this caused by Xposed?

Xposed or root, i dont know but i had to say goodbye to snapchat since there is no way to get it working on rooted devices,i unroot, login, then root and after a couple of hours or maybe a day cant log in...titanium backup didnt do the trick neither, it is server syncd so they find out and block u

Yes, you have to hide root from Snapchat using Magisk Hide and uninstall Snapchat.
Then flash Xposed uninstall by flashing the uninstaller zip in recovery, reboot to system, install Snapchat and hide root from it and login, once logged in reboot to recovery, flash Xposed, reboot to system and it should work and stay working.
Repeat process in future if necessary.

Redline said:
Yes, you have to hide root from Snapchat using Magisk Hide and uninstall Snapchat.
Then flash Xposed uninstall by flashing the uninstaller zip in recovery, reboot to system, install Snapchat and hide root from it and login, once logged in reboot to recovery, flash Xposed, reboot to system and it should work and stay working.
Repeat process in future if necessary.
Click to expand...
Click to collapse
That will work for MAYBE a few days. SC scans your phone now for xposed/root and will instantly ban it. Also, it keeps your device id stored on a blacklist so you'd have to change that too. They've gotten a lot sneaker about it. You can use an app like xprivacy lua or app ops to block this reading permission but it'll probably crash SC constantly. A few guys and I are trying to spoof the reading and device id and not get it to freak out but it's a slow process

agraceful said:
That will work for MAYBE a few days. SC scans your phone now for xposed/root and will instantly ban it. Also, it keeps your device id stored on a blacklist so you'd have to change that too. They've gotten a lot sneaker about it. You can use an app like xprivacy lua or app ops to block this reading permission but it'll probably crash SC constantly. A few guys and I are trying to spoof the reading and device id and not get it to freak out but it's a slow process
Click to expand...
Click to collapse
Can't say I've ever only had it work for a few days, or only ever had it maybe work. It's worked for months now without issue.
I've also not had Snapchat "scan my phone" and I don't do anything special in that department, just regular Magisk Hide.
I've had it stop working once, months ago as I said above, and I just did the process and it started working again, no device ID change or blocking of permissions.

Redline said:
Can't say I've ever only had it work for a few days, or only ever had it maybe work. It's worked for months now without issue.
I've also not had Snapchat "scan my phone" and I don't do anything special in that department, just regular Magisk Hide.
I've had it stop working once, months ago as I said above, and I just did the process and it started working again, no device ID change or blocking of permissions.
Click to expand...
Click to collapse
If you gave sc storage permission, then yes it does scan your phone periodically. It's declared in detail, in apps like app ops. Anyway though, without anyone capturing logs of when the ban is done (I'm talking to everyone that runs a sc mod of any sort) , nobody can really come up with the exact reason for them, only make educated guesses because it seems to not be one thing related \_(•-•)_/ Happy snapping!

Seems to be that Snapchat is detecting Xposed, whether it be non-systemless up to 8.1 oreo (v90 beta-3), systemless by topjohnwu, or systemless for 7.0-9.0 (EdXposed). I used Snapchat with non-systemless Xposed by rovo89 up till a month ago when I upgraded to PIE, then I used EdXposed. My new 9.0 PIE setup worked well with SnapFreedom and EdXposed until I upgraded EdXposed and Snapchat to 10.51.0.0 when I got my first ban.
Plan for attack (haven't tried, banned on alt) to use Snapchat and Xposed (Possibly also Xposed modules?) without ban:
-Use AppCloner to rebuild the snapchat apk with minimal permissions (I have premium version). I was going to go this route, but AppCloner rebuilds com.snapchat.android to com.snapchat.androie, breaking SnapFreedom. Bare permisisons: CAMERA, MICROPHONE, and maybe LOCATION? PHONE permission will give away your IMEI and other stuff, and STORAGE may trigger Xposed detection.
-Use LuckyPatcher to deny snapchat certain perissmions, including read external storage.
This thread got me thinking: https://forum.xda-developers.com/xposed/xposed-root-snapchat-uninstall-xposed-t3909199

I am using Pixen OS android 10 on oneplus 6. I have magisk root and want to install xposed. How to prevent snapchat account lock?

Snapchat won't sign in, how to fix?

Alright so I'm running magisk 18.0 on OnePlus 3T with xposed framework. I was able to sign into Snapchat before xposed when I used magisk hide and all the other things you're supposed to do. I'm obviously aware I triggered safety net by using xposed, what's the fastest way to get safetynet to pass again so I can sign into Snapchat? Is it as simple as disabling xposed? Please walk me through this, thanks

JayTheKid said:
Alright so I'm running magisk 18.0 on OnePlus 3T with xposed framework. I was able to sign into Snapchat before xposed when I used magisk hide and all the other things you're supposed to do. I'm obviously aware I triggered safety net by using xposed, what's the fastest way to get safetynet to pass again so I can sign into Snapchat? Is it as simple as disabling xposed? Please walk me through this, thanks
Click to expand...
Click to collapse
The reason I'm having this issue is because Snapchat randomly signed me out today and my restore point in titanium backup was too old

I had it too. Sign out clear data and cache and forced stop
Go hide in Magisk.
Reboot.
Clear data and storage again m
Open MM & turn off Magisk Hide.
Wait a few seconds.
Toggle Magisk Hide back on.
Force stop and clear Snapchat again.
Now before rebooting go ahead give it the permissions you want it to have.
Theory: don't give it the "phone" permission at first it at all if you can help it.
Reboot
Let everything finish loading and settling in, wait a couple minutes then try again.
If it's still messed up, is the account locked on their end until you call?
Let me know.

JayTheKid said:
Alright so I'm running magisk 18.0 on OnePlus 3T with xposed framework. I was able to sign into Snapchat before xposed when I used magisk hide and all the other things you're supposed to do. I'm obviously aware I triggered safety net by using xposed, what's the fastest way to get safetynet to pass again so I can sign into Snapchat? Is it as simple as disabling xposed? Please walk me through this, thanks
Click to expand...
Click to collapse
vonDubenshire said:
I had it too. Sign out clear data and cache and forced stop
Go hide in Magisk.
Reboot.
Clear data and storage again m
Open MM & turn off Magisk Hide.
Wait a few seconds.
Toggle Magisk Hide back on.
Force stop and clear Snapchat again.
Now before rebooting go ahead give it the permissions you want it to have.
Theory: don't give it the "phone" permission at first it at all if you can help it.
Reboot
Let everything finish loading and settling in, wait a couple minutes then try again.
If it's still messed up, is the account locked on their end until you call?
Let me know.
Click to expand...
Click to collapse
I turned off xposed in magisk and the installer, retoggled magisk hide for Snapchat and rebooted. Account was locked, what triggers this? I was using snap with Xposed undetected for months and then it randomly acts up. You mentioned not giving it phone permission, is that how they catch you? The only other thing I could think of that caught me was my cable app (spectrum TV) makes me disable usb debugging to use it

JayTheKid said:
I turned off xposed in magisk and the installer, retoggled magisk hide for Snapchat and rebooted. Account was locked, what triggers this? I was using snap with Xposed undetected for months and then it randomly acts up. You mentioned not giving it phone permission, is that how they catch you? The only other thing I could think of that caught me was my cable app (spectrum TV) makes me disable usb debugging to use it
Click to expand...
Click to collapse
The phone permissions allows the app to see the phone's IMEI code. I think maybe that detected you are on a rooted phone using that information.

How to use Snapchat with magisk (After Ban)
Follow these steps to use Snapchat with magisk -
1.) Update to latest Magisk stable build v20.0 - https://github.com/topjohnwu/Magisk/releases/download/v20.0/Magisk-v20.0.zip
2.) After updating magisk, Go to Magisk Manager > Magisk Hide and check/enable Snapchat and Google Services (all services have to be marked).
3.) Hide Magisk Manager by it self, go to Magisk Manager > Settings and "Hide Magisk Manager" so it will repack Magisk Manager with random name.
4.) Delete "busybox" binary from /system/xbin directory and install BusyBox module from Magisk Manager > Downloads.
5.) Clear data and cache of Snapchat, try to login this time, it will work for sure, if it doesn't, login to this and click unlock my account - https://accounts.snapchat.com/accounts/login?continue=https://accounts.snapchat.com/accounts/welcome
I have tried this myself and it works, my first main account was permanent banned on magisk canary build, After that I deleted that account and started out with fresh new account.
Tested on -
Samsung Galaxy S9+
Rom - Ultimate Rom v11.3
Magisk - v20.0 (Stable)
Kernel - ElementalX

No such item in xbin
I tried that too but i dont find any item such as busybox my Snapchat account can't be locked because its has been open in different phones
So give a solution what should i do i uninstall edxposed tried everything root switch root clock hut none of them really works its say oh on your temporarily login fails please try again later help needed seriously its been days
Running
Magisk 20.4 stable
Ed xposed 0.4.5.6 justins forks snadhook
Android 10

Magisk Zygisk + LSPosed Zygisk = black screen after boot

Hey,
I updated my Magisk v23 do Magisk v24.1 yesterday. I noticed that hiding root from apps doesn't work for me and LSPosed modules don't work either. I looked to see if LSPosed offers a module that works on Zygisk. As it turned out there is such a module, they have been working on such a version of LSPosed for months. Module I uploaded, it worked for some time. After a while I noticed that Google Pay does not want to use my card (it sees root). I installed the Universal Safetynet Fix module in Magisk. I restarted my OnePlus 7 Pro, then cleared the Google Services data, and poriously added the payment card. I was greatly surprised as I did another reboot to make sure all changes were applied. The phone booted, the boot process took a very long time compared to how it has always booted. At the end of the bootation I felt two vibrations and that was it. The boot process ended and there was a black screen. There was no Launcher, status bar or anything else visible. The only thing I noticed was 3 options in the white window after holding down the power button - a white window and 3 options: Lock, Restart and Power off.
I've tried for hours different tricks - uninstalling Magisk, getting rid of TWRP, flashing the official ROM in TWRP (without Magisk) and nothing worked. The effect is the same every time. To sum up, I regret that I updated Magisk to v24.1. I think that Zygisk mode and modules are still very underdeveloped. The whole situation caused me to lose all the data in the application. The only recovery is copying files via TWRP. I personally have no idea how to get out of this situation to keep a working system.

i no have install LSPosed Zygisk
just install Safetynet Fix module Zygisk,and use Zygisk Black list,and change Magisk app name( i have install stub-release.apk this apk)
my all bank app can't detected Magisk,and work fine
google pay too

rf9992003 said:
i no have install LSPosed Zygisk
just install Safetynet Fix module Zygisk,and use Zygisk Black list,and change Magisk app name( i have install stub-release.apk this apk)
my all bank app can't detected Magisk,and work fine
google pay too
Click to expand...
Click to collapse
Exactly this, bank apps can't detect the new zygisk, at least for now, just hide magisk app, delete TWRP folder and use SNF zygisk module and the black list

hi
MisiekDP said:
Hey,
I updated my Magisk v23 do Magisk v24.1 yesterday. I noticed that hiding root from apps doesn't work for me and LSPosed modules don't work either. I looked to see if LSPosed offers a module that works on Zygisk. As it turned out there is such a module, they have been working on such a version of LSPosed for months. Module I uploaded, it worked for some time. After a while I noticed that Google Pay does not want to use my card (it sees root). I installed the Universal Safetynet Fix module in Magisk. I restarted my OnePlus 7 Pro, then cleared the Google Services data, and poriously added the payment card. I was greatly surprised as I did another reboot to make sure all changes were applied. The phone booted, the boot process took a very long time compared to how it has always booted. At the end of the bootation I felt two vibrations and that was it. The boot process ended and there was a black screen. There was no Launcher, status bar or anything else visible. The only thing I noticed was 3 options in the white window after holding down the power button - a white window and 3 options: Lock, Restart and Power off.
I've tried for hours different tricks - uninstalling Magisk, getting rid of TWRP, flashing the official ROM in TWRP (without Magisk) and nothing worked. The effect is the same every time. To sum up, I regret that I updated Magisk to v24.1. I think that Zygisk mode and modules are still very underdeveloped. The whole situation caused me to lose all the data in the application. The only recovery is copying files via TWRP. I personally have no idea how to get out of this situation to keep a working system.
Click to expand...
Click to collapse
Hello, were you able to solve this?

maycomathias93 said:
hi
Hello, were you able to solve this?
Click to expand...
Click to collapse
No. You have this same problem (phone not turning on)?

yes, the only solution in this case is to run uninstall magisk and install again without lsposed. For now use edxposed without safetynet (sorry for my google translate english)

Man, I solved this problem, going from Android 9 (custom ROM where I had the problem) to 10 (also custom ROM). I hope it helps you, greetings.