Hi,
For those who have issues with (french) banking apps like Boursorama Banque and Orange Bank when activating fingerprint login on a device with custom kernel, you can try changing the SELinux to enforcing.
I was unable to activate fingerprint within the banking apps, always getting an initialization error just with every custom kernel used (ElementalX, Blu_spark, Franko etc.).
I used this : https://forum.xda-developers.com/apps/magisk/selinux-mode-inverter-t3775271 and maybe you'll have to uninstall / reinstall the banking app.
Hope it helps.
Related
I recently downloaded an app called "Island" from the google play store and stumpled across this problem:
"The security policy prevents the creation of a work profile because a Custom OS has been installed on this device.
I have a Samsung Galaxy S7 (7.0)
Rooted with Unofficial Xposed Framework (by PurifyOS)
Also have Superkernel v2.70 installed.
Is there a way to bypass this using an Xposed module or other rooted applications?
You can try xTouchWiz Xposed module which has a function to fake the system status as Official instead of Custom under the security hacks section.
Alternatively you can use Magisk which should hide everything but Xposed from apps.
What worked for me was connecting the device to wifi or putting in an activated sim card before doing the work profile setup process.
Same problem here (S9 Soldier Rom), did someone made it work?
No one yet?
Has anyone gotten this to work?
Beanvee7 said:
You can try xTouchWiz Xposed module which has a function to fake the system status as Official instead of Custom under the security hacks section.
Alternatively you can use Magisk which should hide everything but Xposed from apps.
Click to expand...
Click to collapse
I don't have Xposed but I recently rooted with Magisk. And MagiskHide is not working for this. Do we have to hide system apps as well? I actually get this error when I add my Gsuite work account.
Hello everyone I currently have an issue to install some banking apps and MobileIron.
I cant use google pay, postfinance TWINT and Mobileiron (because of root getting detected or not passing safetynet or xposed.)
I am not passing Safetynet unless I check "only use core functions" in magisk.
I am hiding MobileIron with MagiskHide and I am also hiding Xposed Installer from MobileIron with suhide.
I already tried having another app block root and xposed detection for MobileIron (uncheck)
What can I do to get it to work?
Please don't tell me to just "unroot" or go back to stock.
Have a great day!
Uninstall xposed , Nothing else i can say
I now the issue well with Postfinance Twint on my rooted Samsung Galaxy S5.
Uninstalling xposed will show no effect, because your phone is locked with a root detection. The only solution I've found was to install the old version 1.1.16.0, the last version before root detecting. This works fine for me (except the QR-Scanner which shows "Error 13: The Scandit SDK license validation failed", but you can use the code input instead).
If someone knows a better solution: post it!
Reading this I stopped my thoughts about rooting. I'm using many banking apps, most of all SEQR for nfc payments. I see myself running into problems getting my finance apps to work once rooted...
lucajasonmiani said:
Hello everyone I currently have an issue to install some banking apps and MobileIron.
I cant use google pay, postfinance TWINT and Mobileiron (because of root getting detected or not passing safetynet or xposed.)
I am not passing Safetynet unless I check "only use core functions" in magisk.
I am hiding MobileIron with MagiskHide and I am also hiding Xposed Installer from MobileIron with suhide.
I already tried having another app block root and xposed detection for MobileIron (uncheck)
What can I do to get it to work?
Please don't tell me to just "unroot" or go back to stock.
Have a great day!
Click to expand...
Click to collapse
did you try "Hide Magisk Manager" option in Magisk Manager?
maybe your bank app is looking for Magisk Manager package too.
I'm not using app that you mention but you can try .
No problems with new version 2.0.20.0 (PostFinance Twint) on rooted Samsung Galaxy S5
I had a similar problem with my banking app. I solved it by installing island app. It basically creates an "island" where you can separate specific apps from the rest of your phone apps. When I put my banking app in the island it worked perfectly (also used magisk hide).
You'll have two versions of the same app when you do this. Just remember to always run the island version of the app not the normal version. There will be a small icon indicating which is which.
Hope it works with you!
lo2ay said:
I had a similar problem with my banking app. I solved it by installing island app. It basically creates an "island" where you can separate specific apps from the rest of your phone apps. When I put my banking app in the island it worked perfectly (also used magisk hide).
You'll have two versions of the same app when you do this. Just remember to always run the island version of the app not the normal version. There will be a small icon indicating which is which.
Hope it works with you!
Click to expand...
Click to collapse
Even with the island app, tez app is not working.
If you want to make your Google Pay work, make sure you followed those steps below
Use AOSP/LOS or OEM Based rom. MIUI 7 and 8 have problems with SafetyNet [Even if you have Magisk installed]
***MOST IMPORTANT***
[###ROOT###]
Check your Selinux Mode in the About Phone section in Settings.
Selinux is another Google Protection featured with Kitkat in 2014
If you have Permissive, change it to Enforcing using this app [Download Attached Files]
Reboot after applying Enforcing. Don't Delete Selinux Mode Changer, You will lose your Enforcing and will be switched back to Permissive
Use Magisk only - Don't use SuperSu, it doesn't have Hiding features and it is not supported anymore
If magisk triggers your SafetyNet (Main reason why Google pay stops working) install the SafetyPatch module or Magisk Hide Props or check your SafetyNet. That will fix your safety net.
Don't use XPOSED, it will trigger safety net even if magisk hide working. Xposed modify Boot.IMG, the reason for the safety net to trigger. If you cant live without Xposed, use EDXPOSED magisk module, install Riru core, riru edxposed and Xposed installer that will not trigger your safety net (Please note: Android 5.1 Android 6.0 get bootloop because of EdXposed, sorry guys no luck)
Don't Update you GOOGLE PAY - google updates security patch, magisk too Update your Google pay rarely
Always update your magisk and try to download magisk from Github.
Check your Safety net and make sure your Selinux is in Enforcing Mode
???
If that helped you, you are welcome
thanks for this solution.
Regards
Ginifa
dviree said:
???
Click to expand...
Click to collapse
Not sure what is so funny?....
Not able to install
amelbeabk said:
That Google Pay image says your phone is rooted, but it says that as an example as what could have tripped off Safety Net.
Safety Net failing doesn't mean you a rooted. Safety Net is designed to fail if you have an Unlocked bootloader.
Click to expand...
Click to collapse
It sucks, but for things like Google Pay, I'd strongly suggest that you just give up. Google is contractually obligated to play this game with you and try to prevent you from using it on a rooted "insecure" device so they can process card payments.
I have moto G5+ with unlocked bootloader and magisk. Google pay works fine and saftey net does not fail if bootloader is unlocked
I have a custom rom. Only way to get Magist working was to install EdXposed and hide module. SafetyNet Test also says safetynet passes but my gpay doesnt want to work. Assuming its seeing edxposed perhaps. Anything else i can do
dk0dave said:
I have moto G5+ with unlocked bootloader and magisk. Google pay works fine and saftey net does not fail if bootloader is unlocked
Click to expand...
Click to collapse
I also have moto G5+, But still not unlock boothloader. I need study more for unlocked it, however this comment is helpful to get a decision for me, Thanks.
Tutuapp Movie HD Cokernutx
Google Play warns me to uninstall SELinux Changer, then shuts my phone down. I tried uninstalling it then rebooting, but the phone is behaving extremely oddly and shutting down by itself.
Now I have to format it, just to be sure.
murick_show said:
If you want to make your Google Pay work, make sure you followed those steps below
Use AOSP/LOS or OEM Based rom. MIUI 7 and 8 have problems with SafetyNet [Even if you have Magisk installed]
***MOST IMPORTANT***
[###ROOT###]
Check your Selinux Mode in the About Phone section in Settings.
Selinux is another Google Protection featured with Kitkat in 2014
If you have Permissive, change it to Enforcing using this app [Download Attached Files]
Reboot after applying Enforcing. Don't Delete Selinux Mode Changer, You will lose your Enforcing and will be switched back to Permissive
Use Magisk only - Don't use SuperSu, it doesn't have Hiding features and it is not supported anymore
If magisk triggers your SafetyNet (Main reason why Google pay stops working) install the SafetyPatch module or Magisk Hide Props or check your SafetyNet. That will fix your safety net.
Don't use XPOSED, it will trigger safety net even if magisk hide working. Xposed modify Boot.IMG, the reason for the safety net to trigger. If you cant live without Xposed, use EDXPOSED magisk module, install Riru core, riru edxposed and Xposed installer that will not trigger your safety net (Please note: Android 5.1 Android 6.0 get bootloop because of EdXposed, sorry guys no luck)
Don't Update you GOOGLE PAY - google updates security patch, magisk too Update your Google pay rarely
Always update your magisk and try to download magisk from Github.
Check your Safety net and make sure your Selinux is in Enforcing Mode
Click to expand...
Click to collapse
Hello, hope you can help, installed Beyond ROM and Thunderstorm kernel. Google pay not working, SE for Android status shows 'enforcing' when the apk is installed the 'permissions' and ''enforcing' tabs are greyed out. Thank you
Hi all,
Let's tell you my story,
OP6, unlocked, no TWRP, Magisk 20.3 (safetynet is OK) , I used to use my contactless payement app (French Banque populaire app called "Paiement mobile") thanks to Magisk hide, never had to pay more attention to hide root, no need to hide manager, always works with Magisk Hide only.
Updating from OOS 10.3.2 to 10.3.3 and Magisk 20.4.
Everything seems to me fine. I launch once the payement app, no warning.
Thinking about tweaking to make work VoLTE, I tried to find a way to easly save precious data (can't remember the name of the partition name), and finally found that Wanam created an app called "Partition backup and restore" which do that job.
I Installed it and accepted to grant root access.
And at this moment, I got a toast message from my bank app tells me it has detected a security problem.
Since the message, evreytime I open the bank app, it detected the root...
I tried to reinstall it, verify hiding, clear caches, uninstall the partition backup app, contact Wanam, he doesn't understand how his app can reveal the root to my bank app, hide Magisk manager, disable dev mode, oem debug, phone permission to Google Play Services and other, and maybe other things I don't remember... Read so many threads...
My other root-needed apps work.
Rootbear tells me all is OK except BUSYBOX BINARY (can't find something about it).
You're my last chance before getting stock with MSMTool (don't need root anymore).
Thanks in advance guys.
Edit : used Msmtool to go back to stock. No more problem.
Barclays App used to work just fine until about one week ago, when the latest version has been pushed. And they are now switching to an app-only authentication method (no more SMS, no more PINSentry, and definitely not possible through their website). So, if the app can't be used, I will have to either stop using root (which has been really helpful so far), or find a different bank which has an app that works (I believe it's very unlikely).
The Barclays App Version is: 2.73.2 , released in 16/02/2023
Specs:
OnePlus 7
Android 11 (OOS 11.0.2.1GM57BA)
Unlocked Bootloader
TWRP
Rooted with Magisk (25.2):
magisk app hidden
Zygisk enabled
enforce deny list: Enabled (I tried with enabled and disabled)
Deny List:
ALL Google stuff (absolutely anything that had "google" in their name)
Phone (just for safety, I added everything related to phone and dialer)
Barclays App
Magisk Modules:
App Systemizer v17.3.1
Buybox for Android NDK v1.3.4.1
Debloater (Terminal Emulator) v17.3.3
Disable Screenshot Camera Sounds v1.4
Energized Protection v1.3.5
Magisk Hide Props Config v6.12
OnePlus 7 Volume Booster Mod v2
OOS11 Debloater v7
Shamiko v0.6
Systemless Hosts 1.0 (Magisk)
Universal SafetyNet Fix (kdrag0n, modded by Displax) v2.3.1
Play Integrity API Checker:
device integrity: YES
basic integrity: YES
strong integrity: NO
What is happening:
Barclays App is starting
It prompts for registration (asks to set up a PIN)
Throws Error 00006 (which, after some research, seems to be related to Root)
What I did:
Looked for TWRP folder to delete it (I couldn't find it, perhaps I deleted it in the past, however if you can point me to all possible locations where it could be, I'd greatly appreciate it)
Tried both Shamiko and Universal SafetyNet Fix
Deleted storage, cache, from google, barclays, reboot, even uninstalled and reinstalled apps, all the works...
I tried with both Enforce Deny List Enabled and Disabled
Nothing of the above helped with making Barclays App work. Any Suggestions?
Best option atm is use the last version of the Barclays app which still worked (2.72.2) and disable auto update.
Any official way to get the 2.27.2 version? Obviously, because is a banking app, I don't trust mirrors and unofficial repos.
Thanks.
derei said:
Any official way to get the 2.27.2 version? Obviously, because is a banking app, I don't trust mirrors and unofficial repos.
Thanks.
Click to expand...
Click to collapse
https://barclays-bank-plc-banking.en.uptodown.com/android/download/90801956
That is the one I used. I understand your concerns, I was in the same boat before I downloaded it.. But I really need the app working myself. Worked fine though..