Related
My banking app (NAB Mobile Banking), like most, doesn't like it if my phone doesn't pass CTS or if it's rooted when setting up tap-and-pay.
Since I've started using Magisk I've had lots of trouble getting this banking app to work properly.
This is how I have learnt to set it up .
1. Install Magisk. I'm using 15.3.
2. Wipe the app's data in Settings>Apps. But *do not* start the banking app!
3. Hide the app in Magisk.
4. Reboot the phone.
5. Set up the banking app.
At this stage it's usable but in order to be able to survive reboots and restoring from backups I do the following:
6. Hide Magisk Manager. If I don't do this the app will lose the tap-and-pay capability on reboot.
(Thanks @Didgeridoohan for the suggestion)
Old
6. Backup the app using Titanium Backup (TB).
7. Freeze the app using TB before rebooting the phone for whatever reason. If I don't do this the app will lose the tap-and-pay capability.
I take my backups in this state.
Once the phone has rebooted I then:
8. Defrost the app in TB.
9. Make the app the default for tap-and-pay as this gets lost by the freeze/defrost process.
If I have forgotten to freeze the app across reboots then tap-and-pay won't work. However I can:
10. Use TB to restore the app's data, set it as the default for tap-and-pay and I'm good to go.
End Old
The following actions will break the tap-and-pay function and require me to go through the setup process all over again:
a. Setting a new lock screen password, even it's the same as the previous one.
b. Wiping /data in TWRP because even though I restore the backup the lock screen password gets broken requiring me to do the following:
i. Run the following commands in TWRP Terminal to remove the current password before rebooting the system:
Code:
cd /data/system
rm gatekeeper.* locksettings.*
ii. Set a new lock screen password (see point (a) above).
My details:
Phone: OnePlus 3T
OS: OxygenOS 5.0.1
Root: Magisk 15.3, Magisk Manager 5.5.5
Banking app: https://play.google.com/store/apps/details?id=au.com.nab.mobile
Security: Password set and required on start up; fingerprint setup
You don't mention anything about hiding the Manager. Does that make a difference?
Didgeridoohan said:
You don't mention anything about hiding the Manager. Does that make a difference?
Click to expand...
Click to collapse
I never considered that.
I may try that to see if it makes a difference.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
I never considered that.
I may try that to see if it makes a difference.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
For some apps it makes all the difference...
If you haven't checked it out already, there's a bunch of tips like that in the troubleshooting guide.
Different but somewhat related: Since I'm on a custom ROM, Magisk Hide doesn't properly enable passing SafetyNet. The only way I could get it to work was to enable Magisk Hide for specific apps and to install the Universal SafetyNet Fix module (https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431). Maybe you could try that module too and see if it helps.
Didgeridoohan said:
For some apps it makes all the difference...
If you haven't checked it out already, there's a bunch of tips like that in the troubleshooting guide.
Click to expand...
Click to collapse
So, I tried hiding Magisk Manager and now I can reboot the phone without causing issues for the banking app. Thanks very much for the suggestion!
I did read [some of ] the installation and trouble shooting guide but, even now, I wouldn't have tried hiding the manager because my app can be set up properly without issues. It's only the reboot that caused problems. And hiding the manager has fixed this.
I've updated the OP to reflect this.
Sent from my OnePlus3T using XDA Labs
I am curious if anyone has gotten Chase Pay working with Magisk installed. I have turned off xposed ( which is known to fail safetynet), turned on magisk hide, did Magisk random package regeneration, and passed safetynet, but Chase Pay still gives me the error of having root on my phone. My Android Pay is working just fine since I pass SafetyNet, but Chase Pay doesn't.
c19932 said:
I am curious if anyone has gotten Chase Pay working with Magisk installed. I have turned off xposed ( which is known to fail safetynet), turned on magisk hide, did Magisk random package regeneration, and passed safetynet, but Chase Pay still gives me the error of having root on my phone. My Android Pay is working just fine since I pass SafetyNet, but Chase Pay doesn't.
Click to expand...
Click to collapse
You may have skipped a step. At this point, try clearing the Chase Pay app data, reboot, then run and sign into Chase Pay again. That is, once it has "seen" Magisk, it remembers it until you clear its stored data.
At least, that works for me. The only thing that doesn't work is fingerprint sign-on. When I enable that in Chase Pay, it complains that the devices is rooted, and will not enable this feature. The rest of the app seems to work, however. If anyone finds a solution to that issue, please share.
I also have no issues with Android/google pay but chase pay is giving the root error.
I have done steps 1-6 without chase pay working properly. Is there any way to check the chase pay error log and see where it is getting stopped?
I don't think I have ever rooted my Galaxy S7 and I don't even know how.
But I am getting rooted/Malware error with Chase Pay ( I can login but does not let me pay)
I checked with couple applications such as root checker and safteynet and both say that I am not rooted and my phone pass the safety test. Anyone know what the problem is? and how to fix it?
Chase Pay is also saying my phone is rooted. I get beyond the intro so Magisk hide is working to some degree. After that when tapping the pay button is when I get the error.
Tuxedo.Bond said:
Chase Pay is also saying my phone is rooted. I get beyond the intro so Magisk hide is working to some degree. After that when tapping the pay button is when I get the error.
Click to expand...
Click to collapse
Did you hide Magisk Manager (in Magisk Manager>Settings) before setting up Chase Pay?
Screenshot of the settings after hiding by the Manager attached.
Sent from my OnePlus3T using XDA Labs
Yes, hiding Magisk Manager did the trick. Thanks!
BillGoss said:
Did you hide Magisk Manager (in Magisk Manager>Settings) before setting up Chase Pay?
Screenshot of the settings after hiding by the Manager attached.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Hi
So I am about to try the same path for the NAB app. From reading the thread I need to
Magisk Manager
Hide for the app
hide the manager
clean the nab app data/cache
reboot
then start the NAB app'
tried that but app keeps crashing on attempting to create nab pay
EDIT
tried removing data/cache again - seemed to work.
So what happens if I unhide magisk manager ???
KeyzerSuze said:
Hi
So I am about to try the same path for the NAB app. From reading the thread I need to
Magisk Manager
Hide for the app
hide the manager
clean the nab app data/cache
reboot
then start the NAB app'
tried that but app keeps crashing on attempting to create nab pay
EDIT
tried removing data/cache again - seemed to work.
So what happens if I unhide magisk manager ???
Click to expand...
Click to collapse
If you unhide the manager, then NAB pay will stop working if you reboot.
I've also found that even with everything hidden, NAB pay will stop working after some time (a week?).
I've switched to Google Pay which works a lot better and doesn't require hiding the manager.
Sent from my OnePlus3T using XDA Labs
Didgeridoohan said:
You don't mention anything about hiding the Manager. Does that make a difference?
Click to expand...
Click to collapse
Thank you!
This is annoying the hell out of me. I can't get Chase Pay to work. I've gone into Titanium backup and deleted the data for the app. Went into app settings and deleted the storage & cache for the app. Made sure the app is hidden in Magisk and made sure Magisk is hidden. Rebooted phone and still says the app is detecting root. What am I doing wrong?
defens23 said:
This is annoying the hell out of me. I can't get Chase Pay to work. I've gone into Titanium backup and deleted the data for the app. Went into app settings and deleted the storage & cache for the app. Made sure the app is hidden in Magisk and made sure Magisk is hidden. Rebooted phone and still says the app is detecting root. What am I doing wrong?
Click to expand...
Click to collapse
Are you on Magisk 17.1 and have your removed the Magisk folder from your user storage (/sdcard)?
Sent from my OnePlus3T using XDA Labs
BillGoss said:
Are you on Magisk 17.1 and have your removed the Magisk folder from your user storage (/sdcard)?
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Yes. I'm on 17.1. No I didn't delete the folder. I'll try that.
defens23 said:
Yes. I'm on 17.1. No I didn't delete the folder. I'll try that.
Click to expand...
Click to collapse
Delete the folder, delete the Chase app storage, reboot.
Sent from my OnePlus3T using XDA Labs
I recently rooted my new Mi A2 Lite using Magisk.
So my current banking app detected the root and now I cannot use it anymore. I tried Root Cloak and MagiskHide but both of them did not work either. It still shows the message saying my phone is rooted.
How do I debug that now. I need it to be working anyhow.
App: K-Plus; play.google.com/store/apps/details?id=com.kasikorn.retail.mbanking.wap
https://didgeridoohan.com/magisk/MagiskHideHidingRoot
arunsharmaofficial said:
I recently rooted my new Mi A2 Lite using Magisk.
So my current banking app detected the root and now I cannot use it anymore. I tried Root Cloak and MagiskHide but both of them did not work either. It still shows the message saying my phone is rooted.
How do I debug that now. I need it to be working anyhow.
App: K-Plus; play.google.com/store/apps/details?id=com.kasikorn.retail.mbanking.wap
Click to expand...
Click to collapse
I recently had the same problem, but with a different banking app.
What helped me in the past was to hide Magisk Manager with a random package name. It is an option in Magisk Manager itself. Unfortunately it doesn't work anymore but i could mask Magisk Manager with the Samsung app S Secure and now it's working again .
This was included in my Galaxy S7 ROM so you probably need to find the apk for the app or find a similiar working app for your phone model.
Hope this helps.
Daci54 said:
I recently had the same problem, but with a different banking app.
What helped me in the past was to hide Magisk Manager with a random package name. It is an option in Magisk Manager itself. Unfortunately it doesn't work anymore but i could mask Magisk Manager with the Samsung app S Secure and now it's working again .
This was included in my Galaxy S7 ROM so you probably need to find the apk for the app or find a similiar working app for your phone model.
Hope this helps.
Click to expand...
Click to collapse
Alright! Can you clarify what on how to hide Magisk with a different package name. I am still pretty new to Magisk. Thanks.
arunsharmaofficial said:
Alright! Can you clarify what on how to hide Magisk with a different package name. I am still pretty new to Magisk. Thanks.
Click to expand...
Click to collapse
Open Magisk Manager, go to settings and tap on Hide Magisk Manager. If your banking app doesn't work right away try a restart. If it still doesn't work try to mask Magisk Manager with S Secure or similiar apps.
The magisk hide feature does not work
nm180618 said:
The magisk hide feature does not work
Click to expand...
Click to collapse
It does work, the steps I took were:
1) Install Banking app
2) Open it and get notified about the phone being rooted
3) Use Magisk Hide feature to hide the Banking app
4) Go to phone's app settings
5) Baking app settings
6) Clear storage data (Clearing only the cache could work too, I didn't test it)
7) Profit!
Hope that works for you.
Magisk hide doesn't seem to be working for me. Magisk says it's working and safety net passes, but I've tested multiple apps and they can see that I'm rooted. Hiding magisk with a random package name doesn't work either.
Yesterday I installed magisk and went to hide options and checked my banking app. I was amazed to see banking app allowing me to do everything without limited functionality due to "root" like before. But today banking app detected root again and limited all functions, how? There haven't been any updates for banking app yet it seemed to no longer be fooled by magisk.
Same goes for me with the K-Plus app as well. (สวัสดีคับผม) Use Magisk Hide to hide the root access but it crashes the bank app instead.
Not sure what I've missed.
Gpay and banking are still detecting root/custom rom
Magisk and manager installed.
module SaMoDXv1 installed.
Safteynet is showing green
gpay and banking apps hidden
Using hide magisk function
removed all Magisk related stuff from SD card.
Cleared cache from gpay and banking apps .
Turned off usb debugging.
What else is there?
Just installed root checker basic, it sees root. I hide magisk from it and it still sees root. Is that right?
beythas said:
Same goes for me with the K-Plus app as well. (สวัสดีคับผม) Use Magisk Hide to hide the root access but it crashes the bank app instead.
Click to expand...
Click to collapse
Try following the 'Promon' section in https://github.com/Ingan121/UDSBypass
Hi,
I'ould like installing Fde.ai on my One plus 6 rooted with Ice Renovate 11.1 rom, but I'm not sure that installation is compatible with "Rice tweaks", a tweak app for this rom no my device.
Peraphs there is someone who does know the answer?
Tks and regards.
Roberto
What I do
Go to setting -> Magisk Hide -> disable then enable.
This way worked with me .
I used Magisk Manager v 7.2.0 (213).
Magisk v 19.3 (19300).
What worked for me is using the "Hide Magisk Manager" feature in settings. Now apps are not promoting about device being rooted and are running fine now.
Anyone solved this problem?
I still have a banking app with this problem. I tried many times but still not working.
Magisk hide dont work for this app.
nguyenlinh said:
Anyone solved this problem?
I still have a banking app with this problem. I tried many times but still not working.
Magisk hide dont work for this app.
Click to expand...
Click to collapse
So far there are very few apps that I've seen that can not be tricked with tips from the guide linked in the second post of this thread. Give it a shot...
Can you try it?
https://play.google.com/store/apps/details?id=vietcombank.itcenter.smartotpcorp
I Cannot run this app.
Thanks
nguyenlinh said:
Can you try it?
https://play.google.com/store/apps/details?id=vietcombank.itcenter.smartotpcorp
I Cannot run this app.
Thanks
Click to expand...
Click to collapse
Runs fine with the app on the Hide list and the Magisk Manager repackaged with a random name.
More:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Can someone check this for me?
https://play.google.com/store/apps/details?id=no.apps.dnbnor&hl=en_US
Iam using MH v60 with 19.3 still nothing. Iam fighting with that about 4 months now((((
This app (https://play.google.com/store/apps/details?id=com.TMBTOUCH.PRODUCTION&hl=en) has found a way to detect magisk WITH magisk hide hide and package rename.
I don't really know how, I've just updated the app, then BOOM.
I've recheck everything, reinstall, even remove magisk doesn't help.
PS. all with latest magisk 20.3.
Well, Magisk can hide from it just fine (I just tested and had no issues). Which means it's likely something else about your device that's triggering the app.
First make sure that MagiskHide is working properly (test SafetyNet), and if it doesn't try toggling MagiskHide off and on again. More tips here:
https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
No it's not.
I did hide it, also change repack name.
Attached screenshot.
As my test shows, Magisk is perfectly capable of hiding from the app. But, as I said, there's likely something about your setup/device that is triggering it.
Have you tested if MagiskHide works? Have you checked for tips in the link I posted?
Yes Magisk hide works with all other of my bank apps, 5 of them, so far.
Actually, Magisk hide worked with this app since 3 years ago, when I've started using Magisk. But a couple days ago, the app was updated, and boom!!! So, I think they find a way to bypass the hide.
Unless your device is outdated and can't utilise the full potential of Magisk's capabilities (full app obfuscation isn't available on Android versions less than 9, for example, but that info is already covered in the linked guide), the app is not circumventing MagiskHide.
There are many other ways of detecting "root" that has nothing directly to do with Magisk (again, see the linked guide).
Maybe magisk is works fine but this application has some problem in inside. "this device does not to meet the minimum security requirements for this app" it's mean security patch is older than this app require as i think, or maybe this app is broken.
For context I have "treble_arm64_bvS-userdebug 11 RQ3A.211001.001 eng.crossg.20211108.032335 test-keys" LineageOS custom rom with magisk and safetynet granted (thanks to riru module)
But my banking app got recently updated https://play.google.com/store/apps/details?id=com.cm_prod.bad and now refuses to let me connect because "For security reasons this application does'nt support emulators anymore"
This app has MagiskHide applied otherwise it detects root and refuses to let me connect
I know MagiskHide is discontinued but is there a Magisk module or a tweak that could resolve my issue ?
Thanks in advance for any help
Try install IsLand and add app that detect Magisk into IsLand, also hide magisk app by repacking magisk with random package
Dawnowl444 said:
For context I have "treble_arm64_bvS-userdebug 11 RQ3A.211001.001 eng.crossg.20211108.032335 test-keys" LineageOS custom rom with magisk and safetynet granted (thanks to riru module)
But my banking app got recently updated https://play.google.com/store/apps/details?id=com.cm_prod.bad and now refuses to let me connect because "For security reasons this application does'nt support emulators anymore"
This app has MagiskHide applied otherwise it detects root and refuses to let me connect
I know MagiskHide is discontinued but is there a Magisk module or a tweak that could resolve my issue ?
Thanks in advance for any help
Click to expand...
Click to collapse
https://github.com/kdrag0n/safetynet-fix make sure you use the one for magisk hide not zygisk.
Also make sure that magisk manager is hidden ex in magisk manager settings hide magisk rename. Also make sure gms(play services), play store, and your banking app is hidden
toolhas4degrees said:
https://github.com/kdrag0n/safetynet-fix make sure you use the one for magisk hide not zygisk.
Also make sure that magisk manager is hidden ex in magisk manager settings hide magisk rename. Also make sure gms(play services), play store, and your banking app is hidden
Click to expand...
Click to collapse
There are more and more app now can detect magisk stub apk (random package). Your tutorial is old and already have a post about how to do this ))
Well thanks for your responses and yes I have already have already rename Magisk with random id, I have universal safety net fix with riru, and MagiskHide enabled with my banking app (otherwise it detects root as is). And tough that all of this was enough (I do pass safetynet for now) but seems that it is not for my banking app...
@huskydg.11455139 I installed IsLand but I was a bit too much surprised with all the professional profil tweaking that it was doing without my consent... I kinda panic and uninstall the all thing...
But :
- I don't get in what way this will hide the fact that my banking app detect Magisk as an emulator
- When an app is "professionalised" what does it do and what does happen to my saves ?
- I do need MagiskHide to hide root otherwise my banking app detects it either way, can I do that while having IsLand enabled ?
Dawnowl444 said:
Well thanks for your responses and yes I have already have already rename Magisk with random id, I have universal safety net fix with riru, and MagiskHide enabled with my banking app (otherwise it detects root as is). And tough that all of this was enough (I do pass safetynet for now) but seems that it is not for my banking app...
@huskydg.11455139 I installed IsLand but I was a bit too much surprised with all the professional profil tweaking that it was doing without my consent... I kinda panic and uninstall the all thing...
But :
- I don't get in what way this will hide the fact that my banking app detect Magisk as an emulator
- When an app is "professionalised" what does it do and what does happen to my saves ?
- I do need MagiskHide to hide root otherwise my banking app detects it either way, can I do that while having IsLand enabled ?
Click to expand...
Click to collapse
IsLand is second space, any app in IsLand cannot collect anything in Primary space, prevent it collects app list and scan these apk to detect random package magisk app
You can apply MagiskHide / MagiskDenyList for any app in IsLand
I used this to bypass Techcombank, PUBG NEW STATE which can even detect random package magisk app (stub.apk) without freezing Magisk app
Or Hide your list app by using Xposed module: Hide My List App, because now more and more app can detect magisk even it has random package.
With combo (MagiskHide)+(Random Package Magisk app)
huskydg said:
IsLand is second space, any app in IsLand cannot collect anything in Primary space, prevent it collects app list and scan these apk to detect random package magisk app
You can apply MagiskHide / MagiskDenyList for any app in IsLand
I used this to bypass Techcombank, PUBG NEW STATE which can even detect random package magisk app (stub.apk) without freezing Magisk app
Or Hide your list app by using Xposed module: Hide My List App, because now more and more app can detect magisk even it has random package.
With combo (MagiskHide)+(Random Package Magisk app)
Click to expand...
Click to collapse
Well I did just now tried IsLand and my banking app still detects that my phone is considered as an emulator.
But the thing is MagiskHide and random package repacking do work as long as hiding root is concerned, otherwise by banking app do warn me that it detects root. But I wonder if in that process MagiskHide use some technics that are ones of an emulator in the process and my banking app do detects that...
Dawnowl444 said:
Well I did just now tried IsLand and my banking app still detects that my phone is considered as an emulator.
But the thing is MagiskHide and random package repacking do work as long as hiding root is concerned, otherwise by banking app do warn me that it detects root. But I wonder if in that process MagiskHide use some technics that are ones of an emulator in the process and my banking app do detects that...
Click to expand...
Click to collapse
Are you using Custom ROM?
huskydg said:
Are you using Custom ROM?
Click to expand...
Click to collapse
Well yes I'm using AndyYan's Lineage OS (Android 11) rom thanks to phh experimentation from the Treble Project.
This could could be a thing but I'ts weird that my banking app is warning me about emulator and not custom rom (instead of WhatsApp that clearly says that it detects custom rom).
I'm just speculating at this point but I have my bootloader unlock and the phh/AndyYan rom is userdebug. I think the unlock bootloader is spoofed by safetynet fix but I don't know if the userdebug variant can be detect and can be sign of an emulator...
Dawnowl444 said:
Well yes I'm using AndyYan's Lineage OS (Android 11) rom thanks to phh experimentation from the Treble Project.
This could could be a thing but I'ts weird that my banking app is warning me about emulator and not custom rom (instead of WhatsApp that clearly says that it detects custom rom).
I'm just speculating at this point but I have my bootloader unlock and the phh/AndyYan rom is userdebug. I think the unlock bootloader is spoofed by safetynet fix but I don't know if the userdebug variant can be detect and can be sign of an emulator...
Click to expand...
Click to collapse
So that's why, most Custom ROM has broken rules, do you know? Also app can easily detect if you are running Custom ROM
huskydg said:
So that's why, most Custom ROM has broken rules, do you know? Also app can easily detect if you are running Custom ROM
Click to expand...
Click to collapse
Welp same here but it just bug me that my app detects "emulator" and not custom rom... But it's could be some nonsens from by banking app after all...
And weird think that I need to disable MagiskHide, that is still usefull to me, for Momo checking.
So then I should try to spoof my build id and other stuff that can say that I have custom rom?
Dawnowl444 said:
Welp same here but it just bug me that my app detects "emulator" and not custom rom... But it's could be some nonsens from by banking app after all...
And weird think that I need to disable MagiskHide, that is still usefull to me, for Momo checking.
So then I should try to spoof my build id and other stuff that can say that I have custom rom?
Click to expand...
Click to collapse
Maybe they can mark custom ROM as emulator just to make you fear (sometime they said they found something but not that thing). who know?
Try restore to stock rom (no root) and check
huskydg said:
Maybe they can mark custom ROM as emulator just to make you fear (sometime they said they found something but not that thing). who know?
Try restore to stock rom (no root) and check
Click to expand...
Click to collapse
Yeah sometimes they say stuff because they found root or "insecurity" but the app says something completely different.
I will loose all my data if I restore stock rom plus it's a Chinese bloated rom, so I won't do that. I do really like Lineage OS so I will stay out there. But yeah it will most definitively work with stock rom not rooted that's obvious (well I say that but I still have TWRP and unlock bootloader)
huskydg said:
There are more and more app now can detect magisk stub apk (random package). Your tutorial is old and already have a post about how to do this ))
Click to expand...
Click to collapse
If you are using xposed, you can use dev opts hide and hide my applist modules to hide anything you want. I was going with the simplest answer to see if all the first checks were in place.
toolhas4degrees said:
If you are using xposed, you can use dev opts hide and hide my applist modules to hide anything you want. I was going with the simplest answer to see if all the first checks were in place.
And wasn't tutorial was a question
Click to expand...
Click to collapse
Not all apps you can apply the same way
huskydg said:
Not all apps you can apply the same way
Click to expand...
Click to collapse
Actually you can if they are more invasive you will need more hiding than magisk hide can give you. Which are the lsposed method example of what I said also lua module can do some of it also depends which module you prefer. I use hide my applist and dev opts
Go search lsposed and how to use hide my applist
toolhas4degrees said:
Actually you can if they are more invasive you will need more hiding than magisk hide can give you. Which are the lsposed method example of what I said also lua module can do some of it also depends which module you prefer. I use hide my applist and dev opts
Go search lsposed and how to use hide my applist
Click to expand...
Click to collapse
You think I don't know this , don't you?
If you do you wouldn't be here asking.
Maybe you should try using them correctly and clearing data and cache of the app.
toolhas4degrees said:
If you do you wouldn't be here asking.
Maybe you should try using them correctly and clearing data and cache of the app.
Click to expand...
Click to collapse
What's the question I am asking?
toolhas4degrees said:
If you do you wouldn't be here asking.
Maybe you should try using them correctly and clearing data and cache of the app.
Click to expand...
Click to collapse
Maybe you misunderstand what i am taking?
A banking app I've been using for years has always worked after putting it on the Deny List. I updated it recently and it now won't work with Magisk installed regardless of what I do.
As soon as I patch the boot image with Magisk it complains that the device is rooted and locks me out. That's without even installing the Magisk app, also without Zygisk etc.
I can pass SafetyNet and Play Protect certification with Universal Safety Net Fix and Magisk Hide Props Config modules. However that doesn't make the banking app work.
So far I've also tried:
* Magisk Delta, Zygisk off, with sulist on whitelist mode (also tried Delta's Magisk Hide)
* Shamiko
* Hide My Applist (various configs)
* Disabling root from Magisk app
* Renaming the Magisk app
* Downgrading the banking app (it no longer detects root but locks me out until I upgrade)
* Cloning the banking app to Work Profile with Shelter (this is the only thing that gets rid of the message about being rooted. But then it bizarrely claims it can't connect to the server to login!?)
I'm now at a loss as to what else to try. Any ideas please?
What's the banking app name?
Also install Ruru and see what might be the problem. Make the same steps you use to hide your banking apps. Also clear data of Ruru before each test.
Releases · byxiaorun/Ruru
An android sample app of detecting suspicious apps like magisk manager - byxiaorun/Ruru
github.com
makeyourself said:
A banking app I've been using for years has always worked after putting it on the Deny List. I updated it recently and it now won't work with Magisk installed regardless of what I do.
As soon as I patch the boot image with Magisk it complains that the device is rooted and locks me out. That's without even installing the Magisk app, also without Zygisk etc.
I can pass SafetyNet and Play Protect certification with Universal Safety Net Fix and Magisk Hide Props Config modules. However that doesn't make the banking app work.
So far I've also tried:
* Magisk Delta, Zygisk off, with sulist on whitelist mode (also tried Delta's Magisk Hide)
* Shamiko
* Hide My Applist (various configs)
* Disabling root from Magisk app
* Renaming the Magisk app
* Downgrading the banking app (it no longer detects root but locks me out until I upgrade)
* Cloning the banking app to Work Profile with Shelter (this is the only thing that gets rid of the message about being rooted. But then it bizarrely claims it can't connect to the server to login!?)
I'm now at a loss as to what else to try. Any ideas please?
Click to expand...
Click to collapse
I have found some banking apps are calling an external site and somehow they are detecting reporting back root. I had an issue with Halifax and Starling before.
Starling for me tripped over the last few days, and I used pcap droid to trace what hosts it was calling during app start up.
I found that when i blocked the following address:-
firebaseremoteconfig.googleapis.com
it all worked OK.
Try it if you use Adaway or a DNS provider and add this to your blacklist
spida_singh said:
I have found some banking apps are calling an external site and somehow they are detecting reportign back root. I had an issue with Haliafx and Starling before.
Starlign for me tripped over the last few days, and i used pcap droid to trace what hosts it was calling during app start up.
I found that when i blocked the following address:-
firebaseremoteconfig.googleapis.com
it all worked OK.
Try it if you use Adaway or a DNS provider and add this to your blacklist
Click to expand...
Click to collapse
I was wondering why Starling suddenly started failing - thanks!
Try hide root with some google apps on deny list. (u can search "html", "webview", "feedback" then enable hide them all apps which include these words.
giociampa said:
I was wondering why Starling suddenly started failing - thanks!
Click to expand...
Click to collapse
Ta
For ref - Process for Noobies is here;
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
Files and all
spida_singh said:
I have found some banking apps are calling an external site and somehow they are detecting reportign back root. I had an issue with Haliafx and Starling before.
Starlign for me tripped over the last few days, and i used pcap droid to trace what hosts it was calling during app start up.
I found that when i blocked the following address:-
firebaseremoteconfig.googleapis.com
it all worked OK.
Try it if you use Adaway or a DNS provider and add this to your blacklist
Click to expand...
Click to collapse
Thanks. Worked for me on my 6t using LOS20 and Starling
surajpai524 said:
What's the banking app name?
Click to expand...
Click to collapse
Starling
surajpai524 said:
Also install Ruru and see what might be the problem. Make the same steps you use to hide your banking apps. Also clear data of Ruru before each test.
Releases · byxiaorun/Ruru
An android sample app of detecting suspicious apps like magisk manager - byxiaorun/Ruru
github.com
Click to expand...
Click to collapse
If I rename/repackage the Magisk app and use Deny List then the only things Ruru detects is the Magisk app itself (even though it's renamed) and TWRP. TWRP doesn't seem to be the problem because the banking app doesn't seem to care if I've got that installed so long as Magisk isn't installed to ramdisk. And the banking app is clearly detecting something other than just the Magisk app because it trips after flashing Magisk from recovery, even if the Magisk app isn't installed.
I think @spida_singh may have a solution though!
spida_singh said:
I have found some banking apps are calling an external site and somehow they are detecting reporting back root. I had an issue with Halifax and Starling before.
Starling for me tripped over the last few days, and I used pcap droid to trace what hosts it was calling during app start up.
I found that when i blocked the following address:-
firebaseremoteconfig.googleapis.com
it all worked OK.
Try it if you use Adaway or a DNS provider and add this to your blacklist
Click to expand...
Click to collapse
Thanks very much, yes it's Starling I'm having the problem with! Have not tried your solution yet but will do when I have time. Edit: Just tried and it works !!
I did have a look at the DNS requests from the Starling app and I think I may have even noticed the domain name you mention. But wouldn't have guessed it was that causing it! I'd be interested to know how that works... Are Google apps (I have minimal amount installed) spying on my applist and reporting it to my bank!? Kind of creepy! Also quite weird seeing as Google Pay/Wallet doesn't complain!
makeyourself said:
Thanks very much, yes it's Starling I'm having the problem with! Have not tried your solution yet but will do when I have time.
I did have a look at the DNS requests from the Starling app and I think I may have even noticed the domain name you mention. But wouldn't have guessed it was that causing it! I'd be interested to know how that works... Are Google apps (I have minimal amount installed) spying on my applist and reporting it to my bank!? Kind of creepy! Also quite weird seeing as Google Pay/Wallet doesn't complain!
Click to expand...
Click to collapse
Starling will manage the API in how it works for their app, only they will know, i honesltly have no idea, i know Halifax have done this in the past, and now Starling, and simply blocking it allows the app to work, but, as you, im intrigued to know what the app is 'reading' and sending back to report the device is rooted.
PCAP droid can check the payload and dump it to see what was happening with that request, and whats being sent back.
spida_singh said:
Starling will manage the API in how it works for their app, only they will know, i honesltly have no idea, i know Halifax have done this in the past, and now Starling, and simply blocking it allows the app to work, but, as you, im intrigued to know what the app is 'reading' and sending back to report the device is rooted.
PCAP droid can check the payload and dump it to see what was happening with that request, and whats being sent back.
Click to expand...
Click to collapse
Id like to know too - But use my file from post #7 and it should work
I think I spoke to soon. It's still showing up for me when I quit the Starling app.
I tried Starling app and at first it detected root but once I added to Deny list in Magisk. It didn't detect and went to login page.
My root detection bypass configs:-
Magisk (Not hidden/ Name unchanged / Not Frozen)
Magisk Deny List
Shamiko 0.7
Hide My AppList (LSPosed Module)
Universal SafetyNet Fix mod by Displex
I don't know other behaviour like after login and stuff, since I don't have an account.
Ruru screenshot: even with xposed modules and Magisk app not hidden
Prof. Yaffle said:
I think I spoke to soon. It's still showing up for me when I quit the Starling app.
Click to expand...
Click to collapse
Do you have the the domain mentioned above blacklisted in Adaway and the app on Magisk Deny List with Deny List enforcing? All working fine here now.
I also have USNF (kdrag0n) and Magisk Hide Props Config installed. Magisk 26.1
Also you have to clear the app's data before that message will go away.
Yes, I've tried it added manually and also with the file. Same result both ways. I have the Magisk app hidden, Starling in the Deny list but Enforce disabled as I'm using Shamiko.
Edit
I've just cleared the Starling app data and it seems okay at the moment
FYI - Latest May update for Pixel and Starling latest update now break the method in this thread - Searching for workaround
fkofilee said:
FYI - Latest May update for Pixel and Starling latest update now break the method in this thread - Searching for workaround
Click to expand...
Click to collapse
I'm running the latest starling absolutely fine on my Pixel 6. Same set-up (latest linesgeos nightly)
Magisk Delta
USNF by displax
PCAP block list still contains this host
What is your setup?
Official Magisk, UNSF from Displax, Fingerprint Props.
Adaway still contains the host file I made.
My OnePlus 6t on the latest Lineageos 20 nightly seems fine with Shamiko, USNF Mod and the blocked host in Adaway