Database Develop

Magisk and Blackberry Work app

I haven't been able to find a thread on this. So here goes… I'm not able to get the Blackberry Work app that my firm uses to load without detecting root on Magisk v14.0,
What i have tried so far:
- Hide the app using Magisk hide
- Hide Magisk Manager
- Restarting the phone after applying settings above
- Switching between Core/Non-core modes
I can't imagine i am the only one experiencing this issue. Would be real greatly if someone could advise if Magisk can be configured to circumvante BB Work's detection. I really need this app for work (non pun intended)

Which version of BlackBerry Work are you using? Is it newer than 2.7.1.822? Is it asking you for an unlock code?
There was a problem with Huawei devices in some versions. They already fixed it, but for unknown reason 2.7.1.822 is still the latest that works on my Zenfone 2.
Wysłane z mojego ASUS_Z00A przy użyciu Tapatalka

I'm using the latest version. I can get pass all the password/codes, the problem starts after that. The app detects the root after login and i'm bounched back to the logon screen again. If i try to login now, it'll block me and i'm asked to contact my system admin.
I'll try to use the version you mentioned below when i get to the office tomorrow and see how it goes.

Still looking for a way to run Blackberry work app on rooted android!
Has anyone found a way??

deepchakra said:
Still looking for a way to run Blackberry work app on rooted android!
Has anyone found a way??
Click to expand...
Click to collapse
I've just checked this and the current version of BB Work from Google Play doesn't work with Magisk.
The last version that works fine is 2.7.1.822
Wysłane z mojego ASUS_Z00A przy użyciu Tapatalka

If you run a ROM unrooted, will Blackberry Work still detect the unlocked bootloader and/or custom recovery?

Can i write a Magisk module to spoof the device name that blackberry work reads? My company has a policy that only allows iPhones on blackberry work.

Anyone have a solution? I'm am running stock Android pie rooted and can't get bb work to work.

stu5797 said:
Anyone have a solution? I'm am running stock Android pie rooted and can't get bb work to work.
Click to expand...
Click to collapse
Im also running Pie. I have BB Work and UEM Client working fine on my setup with Magisk 17 and manager 5.9.6 or whatever that recent one is. I think the key is you need to use Elemental x kernel as well. So assuming you already have TWRP installed then you would:
1. Boot to TWRP
2. Install Elemental X Kernal
3. Install Magisk 17
4. Install Verified Boot signer v8
5. reboot and if you havent already install Magisk Manager
6. Make sure magisk manager is "hidden" in the settings, also use Magisk Hide to hide all the BB apps as well as one called something like "android.auto_generated.rro_..." I also run it in Core Only mode.
7. Reboot, delete any BB apps you might have already installed and then redownload and resetup. Just make sure everything is Hidden in Magisk Hide before launching it the first time. I can assure you that BB apps can be gotten to work with Magisk and Anrdoid 9.
---------- Post added at 08:47 AM ---------- Previous post was at 08:46 AM ----------
napes22 said:
If you run a ROM unrooted, will Blackberry Work still detect the unlocked bootloader and/or custom recovery?
Click to expand...
Click to collapse
No it wont.

Thanks so much. I noticed if you install blackberry work and it detects anything, the code deactivates so you can not use the app. It must be a prefect install or it won't work

stu5797 said:
Thanks so much. I noticed if you install blackberry work and it detects anything the code deactivates so you can use the app. It must be a prefect install or it won't work
Click to expand...
Click to collapse
Make sure you hide Magisk Manager and that you use Magisk hide to hide Magisk from both Blackberry Work and Blackberry Work profile.
If you take those 2 steps it'll work.

napes22 said:
Make sure you hide Magisk Manager and that you use Magisk hide to hide Magisk from both Blackberry Work and Blackberry Work profile.
If you take those 2 steps it'll work.
Click to expand...
Click to collapse
This works perfectly. Excellent. :good:

What is "Blackberry Work profile"? I don't see that in the list of apps...

Is anyone still using latest app with magisk?

someuser08 said:
Is anyone still using latest app with magisk?
Click to expand...
Click to collapse
2.16.0.1156 BB Work (disabled auto update) on LineageOS 15.1 (Oreo 8.1.0). Magisk 18.1 with Manager 7.0.0. It's still working albeit the phone must be rebooted from time to time because Magisk disappears. This has been an issue for me on the past few versions of Magisk installed systemless.

I can't seem to get it to work for the last half of year (it was OK before). Its almost like work app detecting something else rather than root...

someuser08 said:
I can't seem to get it to work for the last half of year (it was OK before). Its almost like work app detecting something else rather than root...
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/blackberry-app-magisk-t3742178/page2

I removed magisk completely and it still doesn't work for me - I now think its detection of custom ROMs or unlocked bootloaders that kick in...

someuser08 said:
I removed magisk completely and it still doesn't work for me - I now think its detection of custom ROMs or unlocked bootloaders that kick in...
Click to expand...
Click to collapse
I have auto update turned off on my BB apps now. Currently running 2.16.0.1156 still. With Magisk 19.0 and Manager 7.1.1, all BB apps are working on LineageOS 15.1 (Oreo 8.1). If you use the "Basic" configuration guide for Magisk on these versions, you should be in business.
Settings like debugging and dev options could be some off the culprits preventing proper detection circumvention.

I found an old phone, formatted internal storage and got LOS 15.1 on it. BB is the only app installed(no magisk). After retrieving policies from the server it self wipes due incompatible security policy. I can only assume it detects custom ROM (tried the same with AEX). Is there a module in magisk that makes your phone look like official factory state?

[Solved] Device not certified (G Play store)

...

cmmx said:
Never noticed this, so don't know if it's recent or not, but in the play store app's settings, it says my device is not certified. Haven't noticed any issues due to it yet, though.
Any input?
Click to expand...
Click to collapse
Upgrade to the latest version or install persona's b632 if you have kirin 620

..

cmmx said:
I already have the latest, b632.
I can't see how a custom rom could succeed where the stock one fails, though. Still I rather keep the phone stock ftm, at least until I get to decide what changes are applied and how.
Just reset and updated the app and no change. Phone isn't rooted.
Click to expand...
Click to collapse
I still get this problem some times if i switch from custom rom to stock, and i just reinstall rom again with a clean install and all is good, device get certified by google
Enviado desde mi hi6210sft mediante Tapatalk

...

cmmx said:
Never noticed this, so don't know if it's recent or not, but in the play store app's settings, it says my device is not certified. Haven't noticed any issues due to it yet, though.
Any input?
Click to expand...
Click to collapse
If You have root! Best Way to bypass It root Your phone with Magisk root

...

cmmx said:
I don't have root, and can't see why that would affect it, because what it says is the certification is for the device's hw (not sw), so it shouldn't matter if it's rooted or a custom rom or whatever (and I'm on stock Emui, anyway).
And it has nothing to do with Safety net either, because Magisk Manager (now) says it passes both cts and basic integrity (a week ago, the same version (other install) only passed basic integrity, and a couple months ago (other version) it didn't pass either one, with someone on Magisk thread even telling me that's because Magisk itself wasn't installed - guess what: it still isn't, yet it now passes both...).
Either way, I haven't noticed any problems from it, so far, so I'm just puzzled.
Click to expand...
Click to collapse
Bugged Google Play,just wipe data for gplay app.

...

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.

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

Question NFC

good evening. I have a problem and I want to know if it happens to someone too. I can't find any custom rom that has NFC support. All the ones I've tried don't even have an option to activate it. Does this have a solution? my device is redmi note 10 pro sweet. Thanks.

I've tried PixelOS and Xiaomi.eu and both have NFC options and can link with Google Pay (I've tried xiaomi.eu NFC pay and it worked, I didn't try PixelOS, but it has the options)

I remember someone asking this before a while back, and my response is frankly the same (and just as puzzled) - I don't think I've ever seen a sweet ROM that *didn't* have NFC support.

In M2101K6R Japanese versions, nfc does not work on aosp based roms. I am having the same problem

Hmm I am on cr droid and NFC seems to work. With apps like NFC Tools or MIFARE Classic Tool I can read NFC Tags.
Unfortunately Google Pay does not work for me. The pay terminal always say "try again". Dont know what the problem is there

wuslschweiz said:
Hmm I am on cr droid and NFC seems to work. With apps like NFC Tools or MIFARE Classic Tool I can read NFC Tags.
Unfortunately Google Pay does not work for me. The pay terminal always say "try again". Dont know what the problem is there
Click to expand...
Click to collapse
install safetynet fix 2.1 with magisk, then try again.
install safetynet test via playstore and run it. this should be passed now.
If gpay isnt working, go to magisk/settings and activate zygisk. after this, add all google services (use search with "google" and "gms") to the denial-list, reboot phone and try again
if this doesnt the trick, change ROM ;-)
Lineage OS 19.1 is just great. GPay and MIUI Cam working like charme.
links in my signature

I think phone should be encrypted for working NFC (payments).

ottili81 said:
install safetynet fix 2.1 with magisk, then try again.
install safetynet test via playstore and run it. this should be passed now.
If gpay isnt working, go to magisk/settings and activate zygisk. after this, add all google services (use search with "google" and "gms") to the denial-list, reboot phone and try again
if this doesnt the trick, change ROM ;-)
Lineage OS 19.1 is just great. GPay and MIUI Cam working like charme.
links in my signatur
Click to expand...
Click to collapse
I checked with this SafetyNet Test app. All tests passed without magisk. Anyway I would expect a fault message in google pay if something safety related is not ok, same as in banking apps, which are working fine.
Was also thinking to change to lineage but right now I am not motivated to reinstall the phone completely because its my daily driver^^
@otttili81 how can I see your signature?

wuslschweiz said:
I checked with this SafetyNet Test app. All tests passed without magisk. Anyway I would expect a fault message in google pay if something safety related is not ok, same as in banking apps, which are working fine.
Was also thinking to change to lineage but right now I am not motivated to reinstall the phone completely because its my daily driver^^
@otttili81 how can I see your signature?
Click to expand...
Click to collapse
Use Desktop PC to open XDA

Google Pay (well, Wallet now) can be incredibly finicky. Also sometimes it might seem like it has a security issue, but actually it's something else, like the card not being set up properly (but appearing like everything's fine).

Case_ said:
Google Pay (well, Wallet now) can be incredibly finicky. Also sometimes it might seem like it has a security issue, but actually it's something else, like the card not being set up properly (but appearing like everything's fine).
Click to expand...
Click to collapse
Yes everything looks fine in the wallet itself. Only when it comes to payment, the terminal refuses it. I tried several cards. Also reinstallation of the app.
Is there a possibility to check or test it except on the payment terminal?

@wuslschweiz What kernel are you running? Some kernels can cause issues like this.
I just came off a clean install of the current crDroid with Flame GApps last week and Google Pay was working perfectly fine, I didn't have to do a thing except the usual Zygisk deny list setup.

Case_ said:
@wuslschweiz What kernel are you running? Some kernels can cause issues like this.
I just came off a clean install of the current crDroid with Flame GApps last week and Google Pay was working perfectly fine, I didn't have to do a thing except the usual Zygisk deny list setup.
Click to expand...
Click to collapse
@Case_
Standard crDroid kernel 4.14.290-sigmaKernel-v1.0
I havent rooted my phone so no Magisk or Zygisk.
But good to know that Google Pay is working on your phone so the problem is my phone.
Now when you mention kernel I remember I seem to have a firmware problem (notification volume level is related to sound volume)
Maybe also something NFC/GPay is related to this.
Is it better to flash MIUI 13.8 firmware with miui flash tool or twrp?

Flash it with twrp

wuslschweiz said:
Hmm I am on cr droid and NFC seems to work. With apps like NFC Tools or MIFARE Classic Tool I can read NFC Tags.
Unfortunately Google Pay does not work for me. The pay terminal always say "try again". Dont know what the problem is there
Click to expand...
Click to collapse
GPay is a bit of hit and miss. Make sure it says 'Device is certified' in Playstore settings. It usually won't work without it. It's also very dependent on Kernel. There is also an option to reset NFC in settings, which helped me a few times.

Seems like I am just to dumb for Google Pay.
I reflashed Miui 13.08 firware via TWRP and then LOS 19.1L. Installed Magisk to restore Apps and Appdata wirh Alpha Backup Pro. Uninstalled Magisk (I dont need Root) Installed Google Pay, Still not working, same as bevore.
If I am motivated, maybe I try Google Pay on Stock MIUI...
Thx to all for the help

wuslschweiz said:
Seems like I am just to dumb for Google Pay.
I reflashed Miui 13.08 firware via TWRP and then LOS 19.1L. Installed Magisk to restore Apps and Appdata wirh Alpha Backup Pro. Uninstalled Magisk (I dont need Root) Installed Google Pay, Still not working, same as bevore.
If I am motivated, maybe I try Google Pay on Stock MIUI...
Thx to all for the help
Click to expand...
Click to collapse
Storage is encrypted? It won't work with out it.

pablo.see said:
Storage is encrypted? It won't work with out it.
Click to expand...
Click to collapse
I havent done anything special to encrypt it but when I boot into TWRP it requests a PW to decrypt so I assum it is encrypted