Database Develop

Blackberry Work App and Magisk

I've seen a few threads on the Blackberry Work app, but they all seemed have become idle at the end of 2017. Has anyone been able to run new versions of Blacberry Work with the new versions of Magisk?
I'm running an unrooted custom ROM, but the way new versions of the ROM are compiled (using Android Clang) are triggering the checker. Was hoping I could flash Magisk to hide root and custom rom detection from the app.

It depends on what the app is detecting, of course, but take a look under "Hiding root from apps" in the troubleshooting guide. The rest of the post might have some useful tips as well.

I ended up installing Magisk and hiding from the app. It works really well, so we can go ahead and close this thread. Thanks for the follow up.

napes22 said:
I ended up installing Magisk and hiding from the app. It works really well, so we can go ahead and close this thread. Thanks for the follow up.
Click to expand...
Click to collapse
Is BB Work still working for you with Magisk? Our company moved to BB Good (now Work) years ago. I stopped rooting back then since it was too much of a hassle to figure out and I need to have my work email. If this works, the only thing holding me back would be getting official updates from OnePlus. I have the 5T.

jvnat said:
Is BB Work still working for you with Magisk? Our company moved to BB Good (now Work) years ago. I stopped rooting back then since it was too much of a hassle to figure out and I need to have my work email. If this works, the only thing holding me back would be getting official updates from OnePlus. I have the 5T.
Click to expand...
Click to collapse
Yes I can confirm that magisk root does work with BB Work. You have to use the "hide" function in the Magisk Manager and select BB work.
FYI
I am using a stock rom with root.
Tip: don't use xposed framework if you want a working BB work app.

I flashed Magisk in my redmi note 3 kate and installed the magisk manager apk app, everything is working fine, but my question is: Should I install phhSuperUse, rather than this variant has SU because it was built to be installed with magisk ?
Excuse me, I'm not very familiar with the subject and I've been reading about this and I'm a little confused
---------- Post added at 10:22 PM ---------- Previous post was at 10:20 PM ----------
What is the difference when using the magisk modules?
always use xposed framework plus S.U. But since I can no longer download some apps in play store I have resorted to install magisk on my device.

Hello,
Is it still working ?
It work with Good for Enterprise , but i am not able to install UEM Client and BB Work ?
UEM Client seems fine and show device as unrooted but then setting up Blackberrry Dynamics failed due to that , any idea ?
Regards,

Darkwa said:
Yes I can confirm that magisk root does work with BB Work. You have to use the "hide" function in the Magisk Manager and select BB work.
FYI
I am using a stock rom with root.
Tip: don't use xposed framework if you want a working BB work app.
Click to expand...
Click to collapse
I have a message bb work data wiped. And installation fails at the last point. How can I solve it?
Greetings
Wysłane z mojego MI 6 przy użyciu Tapatalka

As of yesterday, blackberry is detecting my root for some reason. Nothing has changed so my guess is that it has something to do with my company's policy changing? At this point I'm very confused

napes22 said:
As of yesterday, blackberry is detecting my root for some reason. Nothing has changed so my guess is that it has something to do with my company's policy changing? At this point I'm very confused
Click to expand...
Click to collapse
I am in the same boat. I can no longer get Magisk 18.0 and BB Work (or any of the BB enterprise apps) to function. I immediately get the "jailbroken" message. I have no idea what changed. :crying:
I am going to try 18.1 and will report if things change.

DaCHeF36 said:
I am in the same boat. I can no longer get Magisk 18.0 and BB Work (or any of the BB enterprise apps) to function. I immediately get the "jailbroken" message. I have no idea what changed. :crying:
I am going to try 18.1 and will report if things change.
Click to expand...
Click to collapse
Magisk 18.1, Manager 7.0, and following this guide is what works:
https://www.didgeridoohan.com/magisk/MagiskHide
Make sure the "Basics" are taken care of, manually.
Hide Magisk Manager package under settings, MagiskHide "Work" only now (no "Work Profile" choice present in the new version). I removed all root-requiring apps. The combo here worked. I may go one by one to see if any of those apps made a difference. Regardless, it works following those instructions. Good luck. :good:

DaCHeF36 said:
Magisk 18.1, Manager 7.0, and following this guide is what works:
https://www.didgeridoohan.com/magisk/MagiskHide
Make sure the "Basics" are taken care of, manually.
Hide Magisk Manager package under settings, MagiskHide "Work" only now (no "Work Profile" choice present in the new version). I removed all root-requiring apps. The combo here worked. I may go one by one to see if any of those apps made a difference. Regardless, it works following those instructions. Good luck. :good:
Click to expand...
Click to collapse
Perfection, thanks so much. Running DU on taimen with Magisk 18.1 substratum TitaniumBackup Franco app. All good!
Sent from my Pixel 2 XL using Tapatalk

Blackberry Appstore
bigknowz said:
Perfection, thanks so much. Running DU on taimen with Magisk 18.1 substratum TitaniumBackup Franco app. All good!
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
@DaCHeF36 Spoke too soon, not able to load BB Access or Appstore, thoughts?

bigknowz said:
@DaCHeF36 Spoke too soon, not able to load BB Access or Appstore, thoughts?
Click to expand...
Click to collapse
I'm not sure about the Appstore, but I am stuck at an "Authenticating" screen for Access. If I make any progress I'll let you know.

Canary
DaCHeF36 said:
I'm not sure about the Appstore, but I am stuck at an "Authenticating" screen for Access. If I make any progress I'll let you know.
Click to expand...
Click to collapse
Everything works on Canary, running 18100.

bigknowz said:
Everything works on Canary, running 18100.
Click to expand...
Click to collapse
Magisk 19.0 and the new 7.1.1 Manager combination seem to work with all BB apps. Maybe it's just me, but the Work Profile option returned in Hide.

Are there any dependencies for BB apps we need to also hide from Magisk?

DaCHeF36 said:
Magisk 19.0 and the new 7.1.1 Manager combination seem to work with all BB apps. Maybe it's just me, but the Work Profile option returned in Hide.
Click to expand...
Click to collapse
I only need to use the BB work app, are you hiding any other app except BB Work ? Also,a) are you hiding the Magisk Manager, b)using Magisk Hide to hide BB Work or c)doing both?

TarunN5 said:
I only need to use the BB work app, are you hiding any other app except BB Work ? Also,a) are you hiding the Magisk Manager, b)using Magisk Hide to hide BB Work or c)doing both?
Click to expand...
Click to collapse
Work and Work profile setup are hidden. Work profile setup is definitely there again. I use Access, Tasks, and Connect too. I have them all hidden even though that may be overkill. I hide Magisk Manager using the built in package option too. I also followed the guide to ensure that all settings like debug, etc. were off. Gold. I excluded the BB apps from auto-updating. I don't plan to upgrade them unless the back-end requires it at some point.

DaCHeF36 said:
Work and Work profile setup are hidden. Work profile setup is definitely there again. I use Access, Tasks, and Connect too. I have them all hidden even though that may be overkill. I hide Magisk Manager using the built in package option too. I also followed the guide to ensure that all settings like debug, etc. were off. Gold. I excluded the BB apps from auto-updating. I don't plan to upgrade them unless the back-end requires it at some point.
Click to expand...
Click to collapse
Thanks, can you please tell me what exactly do you mean by "work profile" and "work profile setup". The app I see is i dont see a work profile app in the play store either. Can you also please send a screenshot of the BB apps that you have hidden in Magisk? This is the first time I'm using BB on my phone so pardon my noobness

Apps refuse to start because phone being rooted but it isn't!

At least 2 of my Apps refuse to start. One is my banking app and they do not offer any other way of interaction.
The problem is that the phone in fact is not rooted! It's just "OEM unlocked" to be prepared for root (which I need for E.g. titanium backup, but only maybe once a month).
Please give me a way out of this vicious circle!
I cannot remove the OEM unlock because it requires full wipe every time. Or is there a way?
Or what can I possibly tell the App Provider to improved their Code so that Oneplus phone state is being recognized (more) correctly?
Any help would be greatly appreciated.

Use Magisk I guess? Use it to hide root from that app.

Reeb_Lam said:
Use Magisk I guess? Use it to hide root from that app.
Click to expand...
Click to collapse
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?

ako673de said:
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?
Click to expand...
Click to collapse
You need to do some reading about Safetynet. If you're OEM unlocked you fail Verified Boot checks. Most custom Kernels include a bypass for this. Magisk alone should also work. I think you missed one important step:
Open Play Store Settings. Scroll down. It says 'Uncertified' at the bottom, right? Now install and set up Magisk. Go to system App Settings and clear Data and Cache for Play Store. Return to the Play Store Settings and scroll down. Now it should say 'Certified'. It might not be immediate, but it will happen. Now your Banking Apps work.
If you don't want, or have no luck with Magisk, simply flash a Custom Kernel that bypasses Verified Boot, and works with OOS.
Simple.

Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?

ako673de said:
Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?
Click to expand...
Click to collapse
Link to other Thread?
I don't know Magisk but are you hiding Root from your Banking App? Have you cleared Data and Cache for the Banking App since getting Certified?

First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?

ako673de said:
Any other idea?
Click to expand...
Click to collapse
Nope. If Play Store says Certified you should be good to go. I can only imagine it's a Magisk issue. Post screenshots of your config and let the Magisk experts pick through them. Maybe there's something not set up correctly.

ako673de said:
First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?
Click to expand...
Click to collapse
Hide Magisk Manager. I had to do that to get my banking app to work.
Edit: you may need to reboot after hiding Magisk Manager and clear you banking app's data before it works.
Sent from my OnePlus3T using XDA Labs

Thank you, indeed that WORKED! Well, at least for 2 out of 3 Apps. I think I can tell which one: "HVB banking". Maybe could somebody cross-check this one on his/her phone?

After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?

ako673de said:
After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?
Click to expand...
Click to collapse
Did you reflash custom kernel after update?

I'm not using any. What I did right after the update is to disable dm-verity (with a patched boot.img), like I did last time. But magisk is not yet re-installed because I wanted to see at least once the HypoVereinsbank App working, which it in fact does (different to last time when the phone was not rooted as well, and the store not certified!).

ako673de said:
But magisk is not yet re-installed
Click to expand...
Click to collapse
That's why... You can't pass the ctsProfile check if your bootloader is unlocked, and if you can't pass the ctsProfile check the Play Store won't be certified. You need Magisk for that...

Now I'm getting confused. The initial mail of this thread explains the situation as it was when I opened this thread:
--> Original ROM, no root, and banking apps didn't work <--
The advice to clear data of the PlayStore immediately brought the PlayStore back to "certified".
This is clearly in contrast to what you're saying now.
I can imagine only one reason: Maybe the older PlayStore had a bug and therefore was able to "certify" even with unlocked bootloader?
Sidenote: My main intention to do the firmware upgrade was that the "safety net checks" in Magisk suddenly stopped working one day (with the error message "invalid response", most probably you know what I'm talking about, I've read some comments from you on this issue). Therefore it's maybe really not too unlikely that Google has changed something very basic. Could you please confirm?
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).

ako673de said:
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/MagiskHide#hn_The_response_is_invalid

Sorry, now comes a probably often asked question: do I need the safetynet check option in magisk for something real? Or do the alternative apps fulfill all possible needs? What are these needs? Isn't that exactly what the PlayStore does to determine "certified"?

After quite some months of absolutely no "root" problems with any of my apps, since today o2banking again doesn't work.
I tried to update Magisk, but after update of the Magisk manager app to v7.1.1(203) it reports that Magisk is not installed at all, and any update of Magisk itself resulted in just the same. So I reverted back to v6.1.0(165) and everything seems to be okay, except that o2banking doesn't work. SafetyNet is clean, Magisk is hidden for o2banking and Magisk manager is repacked.
Does anybody know what the problem might be? Especially with that new version of the manager app, but also with Magisk v19.0 which cannot be installed from v6.1.0 (max. is v18.1). Any ideas welcome! I'm now on OOS 5.0.8 by the way.
SOLVED it myself: As mentioned somewhere in the update FAQ of Magisk there was a bug in manager v6.1.0 that causes the updated v7.1.1 to co-exist with the old version if the old version has been re-packed. If anybody encounters the same problem, the solution is at the bottom of this page: https://www.didgeridoohan.com/magisk/ManagerIssues.
o2banking will then still not work. Update to v19.0 is mandatory. But that is no problem then any more...

probably your banking app identified oxygen os as custom rom and have root. 1 out of 3 banking app in my phone doesn't work with lineageos even though i already hide magisk, but when running oxygen os with magisk hide, and also hide magisk manager (turn it on in magisk manager setting) all 3 banking app work just fine. maybe try sending a message to bank app developer to add oxygen os as exception.

Did you notice my edit? It was a problem with magisk manager update and magisk main version. Now everything is back up and running.

[Discussion] Bypass root detection Fidor banking app

Hi, my original plan was keeping my OP7 root-free because I need that banking app - which has an incredibly good root detection.
Long story short, a few days later and went back to my old habits... Magisk, Kernel, you name it. And the banking app stopped working again.
I do pass the safetynet test, have repackaged Magisk Manager. Google Pay is working like a charme. But Fidor bank seems to be better than Google, at least in this regard. I tried logging traffic using adguard, the app does not connect to anything, no dns requests as well.
Most of the times the app won't start at all, sometimes the first screen flashes for a very short period, and sometimes chrome opens with a webpage from the bank telling me my device is modified. How the **** do they know?
Maybe you guys may have a hint in what direction I could continue poking, because carrying a second phone just for banking is a little bit overkill...

h0l said:
Hi, my original plan was keeping my OP7 root-free because I need that banking app - which has an incredibly good root detection.
Long story short, a few days later and went back to my old habits... Magisk, Kernel, you name it. And the banking app stopped working again.
I do pass the safetynet test, have repackaged Magisk Manager. Google Pay is working like a charme. But Fidor bank seems to be better than Google, at least in this regard. I tried logging traffic using adguard, the app does not connect to anything, no dns requests as well.
Most of the times the app won't start at all, sometimes the first screen flashes for a very short period, and sometimes chrome opens with a webpage from the bank telling me my device is modified. How the **** do they know?
Maybe you guys may have a hint in what direction I could continue poking, because carrying a second phone just for banking is a little bit overkill...
Click to expand...
Click to collapse
Did you clear data of the banking app after Repackaging Magisk & adding it to Magisk Hide? I assume you did it.
Sent from my OnePlus6T using XDA Labs

DarkSJ1998 said:
Did you clear data of the banking app after Repackaging Magisk & adding it to Magisk Hide? I assume you did it.
Sent from my OnePlus6T using XDA Labs
Click to expand...
Click to collapse
I did. And rebooted. And reinstalled. And combinations of those.
A short screenrecord of what is happening as soon as I try to open the app can be found here (youtube link)

I have the exact same Problem
Everything works: Netflix, other banking apps, etc.. Just Fidor. I do not really know how their detection works, but I assume it's not just a root detection.
The weird thing is, it worked flawlessly 2 years ago Now it's just annoying..
Waited a few versions oft Magisk now, however nothing changes.
You're not alone

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

Same problem here ... since the new fidor version v3.14 is out, no way to getting it to work. Downgrade to 3.12 is futile, it forces the update to 3.14 immediately.

As an amendment to my post above (where you'll find pretty much all you need to hide from almost any app), I've successfully tested and hidden root from Fidor v3.14.0.1.
https://forum.xda-developers.com/showpost.php?p=79997227&postcount=98

Thank you, the issue seems to have been addressed there. But as far as I can see, the canary version does not have the optional modules, correct? So I think, unfortunately I will have to wait for an adapted release of the regular magisk.

rpc75 said:
But as far as I can see, the canary version does not have the optional modules, correct?
Click to expand...
Click to collapse
I have no idea what that means... Magisk modules works just fine on the Canary releases.

Didgeridoohan said:
As an amendment to my post above (where you'll find pretty much all you need to hide from almost any app), I've successfully tested and hidden root from Fidor v3.14.0.1.
https://forum.xda-developers.com/showpost.php?p=79997227&postcount=98
Click to expand...
Click to collapse
Thanks for sharing!
I have successfully installed the canary Magisk, have Magisk hide enabled, safetynet pass etc.
All bank apps work after adding them to the hide list, for example trying "Kontist" w/o hide gave error, with hide it works.
However, Fidor (3.14.0.1) is still not working for me :/
The app stays open for 1-2 seconds on the canary build, quite a bit longer than on stable version (instant close), clean cache + clean app data, still no luck.
So Fidor must use another detection method that the other bank apps don't have.
Any advice would be greatly appreciated!

dagoban said:
Thanks for sharing!
I have successfully installed the canary Magisk, have Magisk hide enabled, safetynet pass etc.
All bank apps work after adding them to the hide list, for example trying "Kontist" w/o hide gave error, with hide it works.
However, Fidor (3.14.0.1) is still not working for me :/
The app stays open for 1-2 seconds on the canary build, quite a bit longer than on stable version (instant close), clean cache + clean app data, still no luck.
So Fidor must use another detection method that the other bank apps don't have.
Any advice would be greatly appreciated!
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

Similar Problem, my bank brought out a new app, that is detecting the root/custom rom somehow. The app closes and shows me security bull**** about root, jailbreak, custom roms. I don't know how everything should be hidden, SafetyNet checks out but this app can detect it. No idea how.

alike03 said:
Similar Problem, my bank brought out a new app, that is detecting the root/custom rom somehow. The app closes and shows me security bull**** about root, jailbreak, custom roms. I don't know how everything should be hidden, SafetyNet checks out but this app can detect it. No idea how.
Click to expand...
Click to collapse
Check the link, one post before yours...

Didgeridoohan said:
Check the link, one post before yours...
Click to expand...
Click to collapse
Thanks, I was already going through that one.
Turns out the Banking app was detecting the Original Magisk Package.
Hiding Magisk Manager itself fixed my problem. Thanks for the link.

Didgeridoohan said:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Click to expand...
Click to collapse
Still did not get Fidor to work. Crashes after the initial first 2-3 seconds. If I uninstall Magisk it works again. Disabling modules, delete files from sd-card, etc. didn't change a thing.
This also seem not to be the problem, since it works after uninstalling Magisk.
Fidor is hidden from Magisk, Magisk is repacked with other name.
Mind giving specific instructions on what you did to make Fidor work on your device?

Thyrador said:
Mind giving specific instructions on what you did to make Fidor work on your device?
Click to expand...
Click to collapse
It's all right there in the link provided. I'm not doing anything that's not described there... Of course, there's a whole lot of things there that I didn't do.
Here's my setup:
Android Pie.
Magisk v19.4 (19307), with hidden Manager.
The app on the Hide list.
My internal storage is full of Magisk files and I never bother to disable any modules (all of the ones I have installed can be hidden without issue). I also have OEM Unlocking disabled, but that's just by chance and not something I've done because of an app detecting it...

Didgeridoohan said:
It's all right there in the link provided. I'm not doing anything that's not described there... Of course, there's a whole lot of things there that I didn't do.
Here's my setup:
Android Pie.
Magisk v19.4 (19307), with hidden Manager.
The app on the Hide list.
My internal storage is full of Magisk files and I never bother to disable any modules (all of the ones I have installed can be hidden without issue). I also have OEM Unlocking disabled, but that's just by chance and not something I've done because of an app detecting it...
Click to expand...
Click to collapse
So basically same setup. Still doesn't work with latest Fidor Release.

Thyrador said:
So basically same setup. Still doesn't work with latest Fidor Release.
Click to expand...
Click to collapse
When you say "basically", what's the difference?

Didgeridoohan said:
When you say "basically", what's the difference?
Click to expand...
Click to collapse
That's the question. Even if I do a complete fresh install without anything else beside Magisk and Fidor: as soon as Magisk is running (hidden manager & Fidor, SafetyNet Pass and certified in PlayStore), Fidor stops working.

Thyrador said:
That's the question. Even if I do a complete fresh install without anything else beside Magisk and Fidor: as soon as Magisk is running (hidden manager & Fidor, SafetyNet Pass and certified in PlayStore), Fidor stops working.
Click to expand...
Click to collapse
You're going to have to start digging deeper then...

Bank app detecting root or modified system

I'm trying to use this app: play.google.com/store/apps/details?id=br.com.banrisul
I've added to the hiding list and enable core only mode, it still closes at startup after saying my phone is either root or running a modified system. I've tested with rootbeercheck and it doesn't detect root in any of its tests.
i.imgur.com/60Zs5IH.png

No issues opening the app here... That means Magisk is perfectly capable of hiding from it, but you might have something else in your setup that triggers it.
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

Didgeridoohan said:
No issues opening the app here... That means Magisk is perfectly capable of hiding from it, but you might have something else in your setup that triggers it.
Click to expand...
Click to collapse
but what exactly would trigger it? The link talks mostly about methods to hide magisk, I didn't find anything about what to do if magisk is working but the check fails. I've uninstalled titaniumbackup and rootbrowser. I've disable adb and developer options, I've deleted any folder or downloaded file related to magisk or those apps.
I'm running lineageos, would that be it? How would I go about it?

Could be any number of things... Your ROM might be one of them (more details about that?). It's pretty much impossible for me to do anything else but make educated guesses. The only thing I can say with relative certainty is that it shouldn't have anything to do with Magisk (since I can hide from the app just fine when testing).
You do pass SafetyNet, right? Could be that this is one of those apps that actually use SN.

Didgeridoohan said:
Could be any number of things... Your ROM might be one of them (more details about that?). It's pretty much impossible for me to do anything else but make educated guesses. The only thing I can say with relative certainty is that it shouldn't have anything to do with Magisk (since I can hide from the app just fine when testing).
You do pass SafetyNet, right? Could be that this is one of those apps that actually use SN.
Click to expand...
Click to collapse
It passes both checks.
I am running lineage OS 14.1 (Android 7.1.2) on a moto g4.

My main guess is that it's detecting something about your ROM. LOS is well known enough for apps to look for certain properties of it.

Didgeridoohan said:
My main guess is that it's detecting something about your ROM. LOS is well known enough for apps to look for certain properties of it.
Click to expand...
Click to collapse
Yes, after searching around a bit more I found about why. I completely forgot that I had flashed supersu on my phone before flashing magisk. So I guess that's what the app was freaking out about. So I flashed a supersu removal and reflashed my ROM, now the app is working normally
Thanks for the help!

Same problem
Hello everyone
After the last update of my banking app and wallet too
Both apps stopped starting due tl root device detection
While it was working well yesterday
I just updat apps to the last version
I think these app's developers find a way to detect magisk
Of course im hiding and randomly renaming it

hammohammo said:
Hello everyone
After the last update of my banking app and wallet too
Both apps stopped starting due tl root device detection
While it was working well yesterday
I just updat apps to the last version
I think these app's developers find a way to detect magisk
Of course im hiding and randomly renaming it
Click to expand...
Click to collapse
What version of the application do you want?

I have the latest version installed and it does not detect root

Google Pay with unlocked Bootloader without root (Android 10)

Hello,
I just flashed Xiaomi.eu ROM 9.10.17. How can I use Google Pay with it? I guess the unlocked Bootloader is preventing Google Pay? When I install Magisk Manager to check if I pass safety net it passes.

My experiences with google pay on Xiaomi.EU roms aren't great...
What you need to install is the magisk manager & hide all the google stuff.
Also you need to hide magisk itself.
https://github.com/davidramiro/gpay-gms-patch/blob/master/README.md
I guess you also need to do this.
But, for me it ain't working.. I guess the problem was with my bank.
Don't know why but I guess it had to be something with Android 10.
I went back to the official miui rom & Google Pay is working again.
I use Google Pay every day so I'm sticking with official rom.
Hope it will work when Miui 11 with Android 10 will be released.
My opinion if you want to do bankstuff & google pay. Stick to official rom.

Hello. for me, no worries. Google play works.

Did you delete your cards then reload them? The instructions said load your cards, but probably should've said delete your cards from Gpay first, follow that patch guide, then entire your cards onto Gpay from scratch.
Running MIUI 11 xiaomi.eu with unlocked bootloader, magisk rooted. Gpay works

So I have to be rooted with Magisk? Because I didn't want to have root anymore.

me it works without Magisk. I had to put the cards passing by miui 11. safetynet ok

Magisk+safety net module

meuhmeuh51 said:
Hello. for me, no worries. Google play works.
Click to expand...
Click to collapse
Google play? Or Google pay?

Works great on RevolutionOS Q

Use hce option under NFC switch in connection menu in the settings if gpay does not tell you that you cannot add any card. Otherwose there is a ton of posts on how to make gpay work on rooted devices

stock miui 11 EU google pay doesn't work (root or no root) something about the unlocked bootloader detection. i have for the life of me never got it to work besides one time it glitched and i did rot hide and extremely fast added a card. it added but never was able to pay with it.

xdarkmario said:
stock miui 11 EU google pay doesn't work (root or no root) something about the unlocked bootloader detection. i have for the life of me never got it to work besides one time it glitched and i did rot hide and extremely fast added a card. it added but never was able to pay with it.
Click to expand...
Click to collapse
Folks, check this thread:
https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
Method works great. Root needed. See steps that were successful for me at post #764 (4th post page 77) there. PW