Database Info

Banking App problem with root device.

Hello all
Greetings of the day!!
I have rooted my one plus 6 with Magisk Only. My problem is that one of my banking application namely "Payzapp" by HDFC bank is not open because of phone's rooted. It's say that "your phone is rooted and pertaining to security matter". I tried to hide in MAGISK HIDE BUT VAIN. Screen shot attached for ready reference.
PLS HELP.
Regards
Hunk
https://ibb.co/72vq6VL

Try this.
1. Uninstall the app completely.
2. Open Magisk Manager. Select Hide Magisk Manager from Settings.
3. Reinstall app from Play Store. Do not open yet.
4. Open Magisk Manager and apply Magisk Hide on that app.
5. Open the app.

Thanks for the reply. I tried your method but vain.
Please help.:crying:

Hunk03 said:
Thanks for the reply. I tried your method but vain.
Please help.:crying:
Click to expand...
Click to collapse
Do you pass safetynet? Play Store certified? Play Store and Google Services Framework also hidden with Magisk hide?

qbanlinxx said:
Do you pass safetynet? Play Store certified? Play Store and Google Services Framework also hidden with Magisk hide?
Click to expand...
Click to collapse
I successfully pass safety net. Playstore certified. But ain't do playstore and google services hiden with magisk hide. Now I'm doing this , and report you after this task.
EDIT:- I followed your step, but vain.

Hunk03 said:
I successfully pass safety net. Playstore certified. But ain't do playstore and google services hiden with magisk hide. Now I'm doing this , and report you after this task.
EDIT:- I followed your step, but vain.
Click to expand...
Click to collapse
Did you clear data to the banking app?

Many banking apps use root detection methods that do not rely on magisk. If the above doesn't work you may be out of luck.

qbanlinxx said:
Did you clear data to the banking app?
Click to expand...
Click to collapse
Sorry for the late reply. I tried all the method but Vain.

iElvis said:
Many banking apps use root detection methods that do not rely on magisk. If the above doesn't work you may be out of luck.
Click to expand...
Click to collapse
I think you are right. Is there any other possibility/solution to come-out from this problem? As i relied on the subject Banking App.
Regards

Look into the canary update channel for Magisk.
It's the only way I can get my banking soda to work with Magisk.

SafetyNet CTS Failed

Hello Guys, after I flashed the 20.7.9 EU Beta. I got Safety Net Failed. Is there any way to fix this issue? Thanks.
FYI. My phone is not rooted yet.

Now I already root my phone. And I got this

I wonder if this is related to hardware attestation?
https://www.xda-developers.com/safetynet-hardware-attestation-hide-root-magisk/

edward014 said:
Now I already root my phone. And I got this
Click to expand...
Click to collapse
Apparently, you forgot to hide your magisk with magiskhide in the option. That results in your basic integrity failed.
And for the ctsprofile part, since your evalType showed basic, you may give "Magiskhide props config" a try.
Or, you may just try eu dev 20.7.3, Several reported it passes safetynet check.

Hi all, I passed now the SafetyNet. I just use the MAGISK STABLE and use the command for Magisk Hide Props Config module.

Which commands you used and how exactly did you executed them?

Snah001 said:
Which commands you used and how exactly did you executed them?
Click to expand...
Click to collapse
Use termux and type su -c props and follow or choose the steps that will appear.

I understand but what choice you made in the props?

Snah001 said:
I understand but what choice you made in the props?
Click to expand...
Click to collapse
-Su -c props
-1
-F (Pick certified fingerprint)
-6
-21
-2
-Yes
-Yes

Snah001 said:
I understand but what choice you made in the props?
Click to expand...
Click to collapse
Btw.
Device: Poco F2 Pro
Rooted Magisk Stable 20.4
ROM: Latest beta EU 7.9

Unfortunately doesn't work.
I am on rooted EEA btw.
Tried several fp's but no luck.
The hardware attestation is messing with us.

Snah001 said:
Unfortunately doesn't work.
I am on rooted EEA btw.
Tried several fp's but no luck.
The hardware attestation is messing with us.
Click to expand...
Click to collapse
Give eu a try, they did some effort on the hw attestation or you may try alter some props to fake your phone to another model to get evalType basic.
Simply changing fp is not gonna help on this hw attestation thing.

edward014 said:
-Su -c props
-1
-F (Pick certified fingerprint)
-6
-21
-2
-Yes
-Yes
Click to expand...
Click to collapse
So you use poco X2 fingerprint?

valkyrjur said:
So you use poco X2 fingerprint?
Click to expand...
Click to collapse
I used google. Not Poco X2 or Poco f2 Pro. Dont use also magisk canary. Use stable one

Used Google XL3 and 4 and both did not work.
Also I tried to find in a logcat (after performing the safetynet check) if it states that attestation is hardware backed but couldn't find it in the logcat.
Edit: got Safetynet check to work.
In Playstore it still says "not certified" but safetynet check is now both ok.
Force closed manually Playstore app and it shows now "certified".
Used: https://forum.xda-developers.com/showpost.php?p=83028387&postcount=40658

Snah001 said:
Used Google XL3 and 4 and both did not work.
Also I tried to find in a logcat (after performing the safetynet check) if it states that attestation is hardware backed but couldn't find it in the logcat.
Edit: got Safetynet check to work.
In Playstore it still says "not certified" but safetynet check is now both ok.
Used: https://forum.xda-developers.com/showpost.php?p=83028387&postcount=40658
Click to expand...
Click to collapse
Try force closing, clearing data and cache for the playstore app then restart the app and check again.

pedro1977 said:
Try force closing, clearing data and cache for the playstore app then restart the app and check again.
Click to expand...
Click to collapse
Did you read my edit to my post?
Deleted all app data also as the dev of the zip file recommended.

Snah001 said:
Did you read my edit to my post?
Deleted all app data also as the dev of the zip file recommended.
Click to expand...
Click to collapse
I saw your modules provided about hardware. But I'm not using that one.
Just try Busy Box only and Magisk Hide Props Config Modules and try also to Hide Your magisk manager and Hide your Banking apps as well.
PS: Ignore this reply if you're successfully and no issue with your safetynet check now. Thank you!

As posted I used the zip to change the model name and it works perfect and it shows certified.

Snah001 said:
As posted I used the zip to change the model name and it works perfect and it shows certified.
View attachment 5059129View attachment 5059131
Click to expand...
Click to collapse
Using that module, Both CTS profile and Basicintegrity will True or verified? Also in Playstore? Right? Btw, thanks to this info bro!

Banking App does not Work with Root

Hey, my Banking apps arent working. Im rooted on One Plus 7 Android 10.0.10 with Magisk 21.1.
I hide Magisk in its Settings and Restarted but didnt worked for me. Please help!
Banking App: VR-SecureGo

Silazius said:
Hey, my Banking apps arent working. Im rooted on One Plus 7 Android 10.0.10 with Magisk 21.1.
I hide Magisk in its Settings and Restarted but didnt worked for me. Please help!
Banking App: VR-SecureGo
Click to expand...
Click to collapse
Settings/Hide magisk manager and reboot, then tap shield icon the bottom, and tap Magisk hide and check then bank app.

Shyciii said:
Settings/Hide magisk manager and reboot, then tap shield icon the bottom, and tap Magisk hide and check then bank app.
Click to expand...
Click to collapse
Did not Worked...
Is there any other option?

Silazius said:
Did not Worked...
Is there any other option?
Click to expand...
Click to collapse
In order for certain apps to work your device will need to pass safetynet check some apps include banking, entertainment and even a few games. You can check this from within Magisk Manger itself. Some custom roms do not support safetynet and therefore it will not pass while on those roms. However, most do such as LineageOS among others. If you need to pass safetynet then making sure software and vendor is updated is your first step, I don't know all the steps as I am unfamiliar with the process but this applies for any device with Magisk not just the OnePlus 7

Silazius said:
Did not Worked...
Is there any other option?
Click to expand...
Click to collapse

Mr.Conkel said:
In order for certain apps to work your device will need to pass safetynet check some apps include banking, entertainment and even a few games. You can check this from within Magisk Manger itself. Some custom roms do not support safetynet and therefore it will not pass while on those roms. However, most do such as LineageOS among others. If you need to pass safetynet then making sure software and vendor is updated is your first step, I don't know all the steps as I am unfamiliar with the process but this applies for any device with Magisk not just the OnePlus 7
Click to expand...
Click to collapse

Saftynet is okei... So what should i do now?

Considering your passing it, you may want to contact the devs of your rom on this one. Not sure why it wouldn't work even with a successful check but that is your best bet assuming your not on stock that is.

I have Oneplus 8 pro . and i have same problem,
the bank app updated their safety and the old way don't work.
also i pass saftynet.

Silazius said:
Did not Worked...
Is there any other option?
Click to expand...
Click to collapse
XPrivacyLua together Magisk Hide is enough.
Try using my app VD INFOS, you can see every detectable thing. (Root/Magisk/Xposed/Riru/and others.)
And then you can fix what needs to be fixed.
[APP][v1.10] VD Infos (Package: com.vitaodoidao.vdinfos)
(Para quem fala PORTUGUÊS, o próximo post está totalmente traduzido !) VD Infos v1.10 As we all know, Android is a super powerful and super versatile operating system. What nobody tells you is that all your personal details and confidential...
forum.xda-developers.com

I'm facing exactly the same issue, my bank's app checks if OEM unlock is active and if so, it fails to start. This thing cannot be hid by Magisk.

Deus. said:
I'm facing exactly the same issue, my bank's app checks if OEM unlock is active and if so, it fails to start. This thing cannot be hid by Magisk.
Click to expand...
Click to collapse
You can hide it easily.
Just unlock bootloader first and then, erase nvdata.
Nvdata contains developer settings, like "oem unlock".
But, if you aready have an unlocked bootloader, the settings "oem unlock" doesn't change nothing.

Question Google Pay after Root

Hi,
I was reading that if I root my Poco X3 Pro with magisk can't use google pay with nfc .
That true ? There is way to unlock google pay to use with nfc ?

astronomy2021 said:
can't use google pay with nfc .
Click to expand...
Click to collapse
That's not true. Install MagiskHide Props Config module and everything will be fine.

wojownikhaha said:
That's not true. Install MagiskHide Props Config module and everything will be fine.
Click to expand...
Click to collapse
My card will works just normal like without root yes ?

On Xiaomi.eu i was able to get Google Pay contactless payments to work by enabling Magisk Hide for all Google apps incl. Pay, but I also had to install HideProps as well as this module: https://github.com/stylemessiah/GPay-SQLite-Fix
On stock it may not be all required. Test it out, some combination of this should work.

Thanks for help have a nice day and be safe

kamild_ said:
On Xiaomi.eu i was able to get Google Pay contactless payments to work by enabling Magisk Hide for all Google apps incl. Pay, but I also had to install HideProps as well as this module: https://github.com/stylemessiah/GPay-SQLite-Fix
On stock it may not be all required. Test it out, some combination of this should work.
Click to expand...
Click to collapse
For me it still says I dont meet security requirements.
What fingerprint did you choose for the device props?
Any more advice on how ye got it working?

23silver said:
For me it still says I dont meet security requirements.
What fingerprint did you choose for the device props?
Any more advice on how ye got it working?
Click to expand...
Click to collapse
If you pass Safetynet, it shouldn't be needed to use the HideProps module.
I don't really use MIUI anymore but doublechecking Safetynet and using the GPay SQLite Fix module is usually the key for me to setting up GPay. You need to install a busybox module and reboot before installing the fix btw.

Barclays banking app (UK) with root

Hi All,
I have recently updated Barclays mobile app on my OnePlus 6 rooted running LOS 19 but the app today detected the root (probably the latest update enable that). So I have cleared the data and cache however I cannot go through the menu to access my account and I get error 00006 now.
I have magisk hide enabled and this has been working with Barclays and the other banking app for a year now (excluding Santander which detects the root anyway)
Do you have any suggestions, please?

I'm in the same boat. Magisk delta with zygisk and app hidden etc etc incl. deny list latest Barclays app still detects root. Have even tried deleting Fox folder, in case it starts seeing that recovery folder. Tried lastest canary build, still the same. Anyone had success with running the latest Barclays app rooted? Poco F3 user BTW, but the principles should be the same...

Do you know if removing the root (magisk) fixes the issue?
reg66 said:
I'm in the same boat. Magisk delta with zygisk and app hidden etc etc incl. deny list latest Barclays app still detects root. Have even tried deleting Fox folder, in case it starts seeing that recovery folder. Tried lastest canary build, still the same. Anyone had success with running the latest Barclays app rooted? Poco F3 user BTW, but the principles should be the same...
Click to expand...
Click to collapse

danc.940 said:
Do you know if removing the root (magisk) fixes the issue?
Click to expand...
Click to collapse
Nope, haven't tried yet... But i'm guessing after removing root and clearing app data it would work...

reg66 said:
Nope, haven't tried yet... But i'm guessing after removing root and clearing app data it would work...
Click to expand...
Click to collapse
Actually, the app might still recognise custom rom. Can't face stock miui just over banking app. What a blow

reg66 said:
Actually, the app might still recognise custom rom. Can't face stock miui just over banking app. What a blow
Click to expand...
Click to collapse
Is there a way to hide also the unlocked bootloader? We won't know until we try it I guess. There is also a Reddit post where many people seem to have the same problem.
Keep an eye on that too until we find a solution.
Do you know where we could get the version of the app that still works with magisk? Is it possible to export the app? Maybe we can find someone with an old version and ask them to share the apk?

A way to roll back has been posted by u/SuzannaBadger in the Reddit thread, pasting here for visibility:
Hi,
I've found a temp fix for this for now.
Steps are as below:
1. Uninstall the current Barclays banking app.
2. Go to play store,settings,network settings and turn off 'auto update apps'
3. Download the old Barclays app from: https://barclays-bank-plc-banking.en.uptodown.com/android/download (it's legit)
4. Install the app.
5. Go into Majisk, settings, configure denylist and tick all Barclays options (may already be ticked, if this is the case ignore step 5)
6. Restart phone.
7. Open Barclays app and setup as you usually would.
Hopefully this works for you. Applist detector is even detecting I have the Majisk app (even though I have Shamiko and have hidden it) but the Barclays app still works as it's the previous version.
Click to expand...
Click to collapse

reg66 said:
Actually, the app might still recognise custom rom. Can't face stock miui just over banking app. What a blow
Click to expand...
Click to collapse
Is there a way to hide also the unlocked bootloader? We won't know until we try it I guess. There is also a Reddit post where many people seem to have the same problem.
https://www.reddit.com/r/Magisk/comments/118yl7n
Keep an eye on that too until we find a solution.
Do you know where we could get the version of the app that still works with magisk? Is it possible to export the app? Maybe we can find someone with an old version and ask them to share the apk?
Jenpyon said:
A way to roll back has been posted by u/SuzannaBadger in the Reddit thread, pasting here for visibility:
Click to expand...
Click to collapse
Great thanks for the update.

danc.940 said:
Is there a way to hide also the unlocked bootloader? We won't know until we try it I guess. There is also a Reddit post where many people seem to have the same problem.
Keep an eye on that too until we find a solution.
Do you know where we could get the version of the app that still works with magisk? Is it possible to export the app? Maybe we can find someone with an old version and ask them to share the apk?
Click to expand...
Click to collapse
Not sure about hiding unlock BL, never looked into it. If you've used the linked 2.72.2 barclays app, as i have, be sure to disable auto update in google playstore
EDIT: just seen it in step 2!! however, i just selected do not auto update for that specific app, rather than all apps

danc.940 said:
Do you know if removing the root (magisk) fixes the issue?
Click to expand...
Click to collapse
Yes it does fix the issue. I've checked and now have a hard choice of either restore magisk needing BCR heavily.

danc.940 said:
Is there a way to hide also the unlocked bootloader? We won't know until we try it I guess. There is also a Reddit post where many people seem to have the same problem.
Keep an eye on that too until we find a solution.
Do you know where we could get the version of the app that still works with magisk? Is it possible to export the app? Maybe we can find someone with an old version and ask them to share the apk?
Click to expand...
Click to collapse
Hiding unlocked bootloader most likely wouldn't help as just removing Magisk leaving bootloader unlocked makes Barclays app working perfectly. So they still just detect root and Magisk some other way. What was interesting was that when I removed Magisk and Barclays functionality was restored I run hidden Magisk app to restore Magisk. It asked to restore main Magisk app that I did. And even without restoring Magisk partition and rebooting Barclays stopped working having only Magisk app installed without root.

reg66 said:
I'm in the same boat. Magisk delta with zygisk and app hidden etc etc incl. deny list latest Barclays app still detects root. Have even tried deleting Fox folder, in case it starts seeing that recovery folder. Tried lastest canary build, still the same. Anyone had success with running the latest Barclays app rooted? Poco F3 user BTW, but the principles should be the same...
Click to expand...
Click to collapse
Try downloading an app called Ice Box and freeze Magisk with it.
That fixed the issue for the bank app I use.

See my replies here guys Post
All I've posted my notes on the reddit page above
Also I have a Santander account and I could never get this app working either!!!
Note this method still doesn't work on Santander!!

sound2005 said:
See my replies here guys Post
All I've posted my notes on the reddit page above
Also I have a Santander account and I could never get this app working either!!!
Note this method still doesn't work on Santander!!
Click to expand...
Click to collapse
Followed steps exactly. Still root is detected

reg66 said:
Followed steps exactly. Still root is detected
Click to expand...
Click to collapse
Thanks for replying back.
What issues did you get, ie FC, root detected etc..?
I'm going to keep trying on my phone and see if I can get this working

Ok guys, this method works 100%!!!
Test on my Samsung Note 8 (Android 10, Custom Rom)
Install this module:
GitHub - HuskyDG/MagiskHide at v1.6
Portable MagiskHide. Contribute to HuskyDG/MagiskHide development by creating an account on GitHub.
github.com
and wipe Barclays data, thats it!!!
Best to have Zygisk off and configure the denylist to get this working
Configure Magisk apps​
As Magisk app does not allow you to configure denylist when zygisk is off. You must toggle Zygisk on temprorily (not reboot) to configurate denylist and toggle Zygisk off after done.
Note that any modules that uses Zygisk will be disabled!!

sound2005 said:
Ok guys, this method works 100%!!!
Test on my Samsung Note 8 (Android 10, Custom Rom)
Install this module:
GitHub - HuskyDG/MagiskHide at v1.6
Portable MagiskHide. Contribute to HuskyDG/MagiskHide development by creating an account on GitHub.
github.com
and wipe Barclays data, thats it!!!
Best to have Zygisk off and configure the denylist to get this working
Configure Magisk apps​
As Magisk app does not allow you to configure denylist when zygisk is off. You must toggle Zygisk on temprorily (not reboot) to configurate denylist and toggle Zygisk off after done.
Note that any modules that uses Zygisk will be disabled!!
Click to expand...
Click to collapse
I'd tried this with Zygisk off but then USNF had become off and device didn't pass Safetynet. Then with Zygisk on and this module on Barclays still showed 0006. Denylist was configured for Barclays and not enforced.

atreal said:
I'd tried this with Zygisk off but then USNF had become off and device didn't pass Safetynet. Then with Zygisk on and this module on Barclays still showed 0006. Denylist was configured for Barclays and not enforced.
Click to expand...
Click to collapse
Try switching Zygisk on and off.
Reboot phone, wipe data and cache for play store and Barclays and try again mate

sound2005 said:
Try switching Zygisk on and off.
Reboot phone, wipe data and cache for play store and Barclays and try again mate
Click to expand...
Click to collapse
Well. Have to put thoroughly what exactly I meant been done.
1. Added Magiskhide module to Magisk and turned it on. Magisk was last stable 25.2
2. Uninstalled Barclays. Installed Barclays without running it yet.
3. Add Barclays to Denylist. Turn Zygisk off.
Reboot
4. Checked Safetynet with YASNAC. It failed. Checked modules page in Magisk - USNF was off apparently as Zygisk was off. YASNAC had been passed before all this attempts with this module when USNF was on.
4. Run Barclays - 0006.
5. Clear Barclays data. Turn Zygisk on in Magisk.
Reboot
6. YASNAC passed as USNF became on.
7. Run Barclays - 0006
And may I ask to give some light on what is meant that "it is better to keep Zygisk off". What does this "better" mean? Must be off? Then how do they mean to bypass Safetynet with USNF off?

atreal said:
Well. Have to put thoroughly what exactly I meant been done.
1. Added Magiskhide module to Magisk and turned it on. Magisk was last stable 25.2
2. Uninstalled Barclays. Installed Barclays without running it yet.
3. Add Barclays to Denylist. Turn Zygisk off.
Reboot
4. Checked Safetynet with YASNAC. It failed. Checked modules page in Magisk - USNF was off apparently as Zygisk was off. YASNAC had been passed before all this attempts with this module when USNF was on.
4. Run Barclays - 0006.
5. Clear Barclays data. Turn Zygisk on in Magisk.
Reboot
6. YASNAC passed as USNF became on.
7. Run Barclays - 0006
And may I ask to give some light on what is meant that "it is better to keep Zygisk off". What does this "better" mean? Must be off? Then how do they mean to bypass Safetynet with USNF off?
Click to expand...
Click to collapse
Hi
By all means you can try my setup:
Modules enabled:
Magiskhide (by Husky)
Magiskhide Props Config
Systemless host
Magisk v25.2 hidden
Denylist has been configured and Zygisk switch is off.
In Denylist I have the following as blocked:
Google play store
Google play services
My bank app
Oysercard app
Please note I've messed around extensively trying to get this to work and a lot of stuff I've added and remove to test out, so some modules (or even apps on the denylist) may no longer need to be there.
Also on step 3, could you turn Zygisk on (the app will tell you to reboot to apply changes) but do not reboot yet!!!, then turn off Zygist then reboot your phone.
Once rebooted clear cache and data for play store and Barclays
Then try banking app again.
If this still doesn't work, you may have a module triggering Barclays to recognise you have root, in which case you may need to disable/remove said modules.
One prime culprit would be Lsposed, if you have this then remove this as well.
Also please note, taken from developers site:
Configure Magisk apps
As Magisk app does not allow you to configure denylist when zygisk is off. You must toggle Zygisk on temprorily (not reboot) to configurate denylist and toggle Zygisk off after done.