Hello,
I have an unlocked, rooted Pixel 7, Android 13 panther. My device is rooted, and the bootloader is unlocked. I have Magisk 25.2 installed with Zygisk and enforce denylist active.
I cannot seem to get my device to pass SafetyNet. I use YASNAC and am continually getting a CTS profile Match Fail.
I have installed the magisks modules, Universal SafetyNet fix, and Magisk Hide Props Config.
I cannot figure out a sequence of options using Hide Props Config that will get me to pass SafetyNet.
Is there anyone who might have any suggestions?
i have the exact same issue
captain_howdy said:
Hello,
I have an unlocked, rooted Pixel 7, Android 13 panther. My device is rooted, and the bootloader is unlocked. I have Magisk 25.2 installed with Zygisk and enforce denylist active.
I cannot seem to get my device to pass SafetyNet. I use YASNAC and am continually getting a CTS profile Match Fail.
I have installed the magisks modules, Universal SafetyNet fix, and Magisk Hide Props Config.
I cannot figure out a sequence of options using Hide Props Config that will get me to pass SafetyNet.
Is there anyone who might have any suggestions?
Click to expand...
Click to collapse
dangercl0se said:
i have the exact same issue
Click to expand...
Click to collapse
you both need to check out the post below (or better yet, get from his Github) and use Displax's updated mod to Universal SafetyNet fix. The original USNF hadn't worked with the Pixel 6 (or Pixel 7), where his original mod worked and passed everything but Strong Integrity. Then, when it came to the Pixel 7 Pro, he needed to mod it again and we all have been using his mod_2.0 to get things to work.
Of course, after applying the module and putting Google Play Store, Google Services Framework, & Google Play Protect Service in the Denylist (every entry in its subdirectory ticked), be sure to clear data from them to make sure you get the best chance at passing safetynet...
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
simplepinoi177 said:
you both need to check out the post below (or better yet, get from his Github) and use Displax's updated mod to Universal SafetyNet fix. The original USNF hadn't worked with the Pixel 6 (or Pixel 7), where his original mod worked and passed everything but Strong Integrity. Then, when it came to the Pixel 7 Pro, he needed to mod it again and we all have been using his mod_2.0 to get things to work.
Of course, after applying the module and putting Google Play Store, Google Services Framework, & Google Play Protect Service in the Denylist (every entry in its subdirectory ticked), be sure to clear data from them to make sure you get the best chance at passing safetynet...
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Click to expand...
Click to collapse
the 2.0 file worked for me, i get CTS pass now
but cannot hide root from Citibank app though. any chance you may know a fix? or the citibank guys are that good?
I vey same issue with my bank app Bt Pay. Only reason i cant stay rooted.
dangercl0se said:
the 2.0 file worked for me, i get CTS pass now
but cannot hide root from Citibank app though. any chance you may know a fix? or the citibank guys are that good?
Click to expand...
Click to collapse
Need Shamiko. Set apps in deny list but don't enforce the deny list.
LLStarks said:
Need Shamiko. Set apps in deny list but don't enable the deny list.
Click to expand...
Click to collapse
Unless the app is even "smarter". Like my own bank app.
dangercl0se said:
the 2.0 file worked for me, i get CTS pass now
but cannot hide root from Citibank app though. any chance you may know a fix? or the citibank guys are that good?
Click to expand...
Click to collapse
I was having trouble with Chase a while back. What I did was clear the banking app's cache/data, enable airplane mode, and reboot after passing safetynet adding the banking app to DenyList. I was then able to log in and successfully hide root from the app. Good luck!
LLStarks said:
Need Shamiko. Set apps in deny list but don't enforce the deny list.
Click to expand...
Click to collapse
still doesn't work, citibank can detect magisk (which was hidden) before i login lol
dangercl0se said:
the 2.0 file worked for me, i get CTS pass now
but cannot hide root from Citibank app though. any chance you may know a fix? or the citibank guys are that good?
Click to expand...
Click to collapse
I use the Citibank app myself and am able to get it to work. You gotta make sure that everything under its sub-directory is ticked as well -- just checked and there's 4 entries in its subdirectory that needs to be ticked. Another thing that might help is to Click Hide the Magisk app; when you hide it, you'll have the optional opportunity to change the Magisk app's name to whatever you wish. Also, you can do what kornball said below as that's also a good idea as well.
kornball said:
I was having trouble with Chase a while back. What I did was clear the banking app's cache/data, enable airplane mode, and reboot after passing safetynet adding the banking app to DenyList. I was then able to log in and successfully hide root from the app. Good luck!
Click to expand...
Click to collapse
Try to use Ice Box app and freeze magisk, then see if banking app works. I had to do that on my last phone. You can easily open magisk by opening ice box app first.
Weird stuff, folks. I imagine that something else is being done amiss as I have a similar setup and don't have any safetynet issues that affect the access to my banking apps/GPay/Prime Video/etc.
I don't even use Displax's USNF mod. Heck, I barely even use the denylist.
I would suggest that you wipe the device clean, re-image it with the latest A13 build, re-root and then set everything up again. But this time, do not install the Magisk Hide Props. That is only needed for those on custom ROMs (which I imagine you aren't using).
dangercl0se said:
still doesn't work, citibank can detect magisk (which was hidden) before i login lol
Click to expand...
Click to collapse
Did you enable Zygisk?
I'm honestly having trouble with Chase at the moment. Usually I'm able to hide Magisk enough to get fingerprints working.
The Citi app doesn't work for me either, despite all other workarounds, and everything else works other than setting the fingerprint reader for use with the Chase app (but that can be worked around while temporarily not rooted). I'll just use the Citi website if I need to.
LLStarks said:
Did you enable Zygisk?
I'm honestly having trouble with Chase at the moment. Usually I'm able to hide Magisk enough to get fingerprints working.
Click to expand...
Click to collapse
I forgot to set the fingerprint before I rooted when I updated the firmware, but I'm just going to try to remember to do it on the next firmware update, hopefully. I never found any other workaround that always works.
roirraW edor ehT said:
The Citi app doesn't work for me either, despite all other workarounds, and everything else works other than setting the fingerprint reader for use with the Chase app (but that can be worked around while temporarily not rooted). I'll just use the Citi website if I need to.
I forgot to set the fingerprint before I rooted when I updated the firmware, but I'm just going to try to remember to do it on the next firmware update, hopefully. I never found any other workaround that always works.
Click to expand...
Click to collapse
For Chase, here's how I got it to work on my P6 previously. There's an old thread where someone installed a downgraded version, but I didn't need to do that:
I force stopped the app and cleared cache/data. I then enabled airplane mode, went into the Chase app and entered my credentials. I hit the fingerprint option and hit "sign on." I got the error saying no data connection available. I reenabled data and signed on.
kornball said:
For Chase, here's how I got it to work on my P6 previously. There's an old thread where someone installed a downgraded version, but I didn't need to do that:
I force stopped the app and cleared cache/data. I then enabled airplane mode, went into the Chase app and entered my credentials. I hit the fingerprint option and hit "sign on." I got the error saying no data connection available. I reenabled data and signed on.
Click to expand...
Click to collapse
I've tried that before on my Pixel 6 Pro and it didn't work. I just tried it again, exactly as you said, and it didn't work for me this time either. I'm glad it works for you. It's no big deal for me to do it while unrooted - just too lazy to unroot until I have to manually update the firmware anyway.
The downgrade app solution worked for a short while, but the app requires that it's reasonably up to date to work at all, so that option was never for the long term.
kornball said:
For Chase, here's how I got it to work on my P6 previously. There's an old thread where someone installed a downgraded version, but I didn't need to do that:
I force stopped the app and cleared cache/data. I then enabled airplane mode, went into the Chase app and entered my credentials. I hit the fingerprint option and hit "sign on." I got the error saying no data connection available. I reenabled data and signed on.
Click to expand...
Click to collapse
This unfortunately did not work for me. I pass safetynet and have magisk hidden as well as Chase on the deny list with all the ticks selected.
roirraW edor ehT said:
The Citi app doesn't work for me either, despite all other workarounds, and everything else works other than setting the fingerprint reader for use with the Chase app (but that can be worked around while temporarily not rooted). I'll just use the Citi website if I need to.
I forgot to set the fingerprint before I rooted when I updated the firmware, but I'm just going to try to remember to do it on the next firmware update, hopefully. I never found any other workaround that always works.
Click to expand...
Click to collapse
I can't believe you and dangercl0se haven't gotten Citi app to work!!! You, the creator the the quintessential guide of whom I followed step by step to get my root working, are having troubles with it when I haven't done anything particular or different than you would have done?! Doesn't seem right to me....i'm baffled as to why things are seamless for some people are are stubborn/difficult for others....
simplepinoi177 said:
you both need to check out the post below (or better yet, get from his Github) and use Displax's updated mod to Universal SafetyNet fix. The original USNF hadn't worked with the Pixel 6 (or Pixel 7), where his original mod worked and passed everything but Strong Integrity. Then, when it came to the Pixel 7 Pro, he needed to mod it again and we all have been using his mod_2.0 to get things to work.
Of course, after applying the module and putting Google Play Store, Google Services Framework, & Google Play Protect Service in the Denylist (every entry in its subdirectory ticked), be sure to clear data from them to make sure you get the best chance at passing safetynet...
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Click to expand...
Click to collapse
Did all this, still failing for me.
Beefheart said:
Did all this, still failing for me.
Click to expand...
Click to collapse
I can only assume you mean passing safetynet and not getting the banking apps to work....
Only thing left that I can think of that I didn't include in that post is to make sure you have "systemless hosts" module installed as well; i know it's pretty obvious but just trying to cover all the bases....
If so and still failing, I suggest going to roirraW "edor" ehT's guide/thread -- it's probably the most active thread on this forum and is where many is bringing up their failing to pass it while going through all the steps...
*there's also Homeboy76's guide HERE if it's clearer/easier to follow for you...
unfortunately there's no real debug logs to state why it's not working out, so the best that I can suggest is that you're going to have be a lot more descriptive on what & how you "did all this" with luck that that'll show something you may have missed and/or start from scratch and follow each and every step exactly of roirraW "edor" ehT's/Homeboy76's guide and hope it works out that way.
Good luck to you and I hope this helps...
Related
I'm trying to enable fingerprint sign on in the Wells Fargo app on my rooted, magisk pixel 2 on the latest march update. I've tried a couple times to enable it and it tells me that fingerprint sign on is currently unavailable. Anybody else experiencing the same issue?
enzyne said:
I'm trying to enable fingerprint sign on in the Wells Fargo app on my rooted, magisk pixel 2 on the latest march update. I've tried a couple times to enable it and it tells me that fingerprint sign on is currently unavailable. Anybody else experiencing the same issue?
Click to expand...
Click to collapse
Working for me, but I'm stock.
I'm rooted with TWRP flashed. Other apps (like Walmart) that require fingerprint find it, but my banking app (PNC) doesn't, and doesn't work at all (restarts during a check deposit), so there's something causing a problem somewhere.
Rukbat said:
I'm rooted with TWRP flashed. Other apps (like Walmart) that require fingerprint find it, but my banking app (PNC) doesn't, and doesn't work at all (restarts during a check deposit), so there's something causing a problem somewhere.
Click to expand...
Click to collapse
Are you using Magisk? I use the PNC app and have it selected with magisk hide and fingerprint works.
1.Try depositing a check.
2. What version of the app are you running?
So just an update I was after a day able to add fingerprint sign on. I just got this account so that may be why. I dont have paper checks to deposit that often but if i ever get one i will report back.
Rukbat said:
1.Try depositing a check.
2. What version of the app are you running?
Click to expand...
Click to collapse
I'm running 4.3.1. It crashes now when the camera would open to capture a check image, but it used to work before. I hadn't used it in a while so must be something broken in an update... All the other functions except for check deposit are working.
Same version - and that's the only reason I use the app. Since I'm on the desktop all day, I do everything else on the desktop. Tech support promised that they'd have a fix out by end of March, beginning of April at the latest. Nothing yet. Oh - when it crashes, it comes up with the name and password screen when you rerun it, and won't accept the fingerprint.
A company I used to work for had a sign hanging in their cafeteria that said that it costs $1,000 to get a customer, but you can lose one with a single wrong word. I think I'm about to become one of PNC's "lost customers". The local Walmart, where I am at least once a week, has a bank branch inside (and the store is pretty much around the corner). The next time I'm there, I'm talking to them. Even if they don't have an app, I'm there all the time anyway. And PNC is 4 miles across town. It will be interesting to see if the app eventually works, but this isn't how you run a software department. (I know - I spent 45 years developing software, most of them either as lead or as head of the department. An "I can't use the program because it doesn't work" would immediately put that bug at the top of my) list - and get someone assigned to fix it.)
The latest updates to these apps on the 18th and 19th of June 2018 produce "Error 04 Security Check failed" at launch. Dismissing the message exits the app.
Rolling back to the previous versions of the apps or even a year old version fixes the problem (for now).
Are these apps finally rejecting 'insecure' devices?
I've got the same error.
It was working this morning but root was disabled as I had done a software update a few days ago and not reinstalled magisk.
Installed 05.09.0000.43.0 May 14, 2018 from apkmonk and I can login again.
Every week I'm almost finding more reasons to give up on rooting. I only use it for a few convenience things mainly but they are so useful. I couldn't have a phone without online banking though...
Just point your stock web browser at nwolb.com.
intrepidis said:
Just point your stock web browser at nwolb.com.
Click to expand...
Click to collapse
Not really the same though? The login process takes longer, the information isn't as nicely formatted etc..
roll back to the previous update.
jeffbesoz said:
Agree with you. :good::good:
Click to expand...
Click to collapse
If you use natwest current version you will get this error if you are rooted - I tried using magisk and hide root but that did not work.
use natwest app version V05.03.0001.125.0 this one will not detect root but it is not as secure as the latest version
https://natwest.en.aptoide.com/?store_name=monadiva&app_id=30626821
I spoke to Natwest support about this and got a call back from one of their techies... he stated that the error message was not from the Natwest app, but from Android itself... this could mean (if true) that Natwest isn't checking for root, but offloading the check onto Google Pay, which in turn gives the error 04...
shayraz said:
I spoke to Natwest support about this and got a call back from one of their techies... he stated that the error message was not from the Natwest app, but from Android itself... this could mean (if true) that Natwest isn't checking for root, but offloading the check onto Google Pay, which in turn gives the error 04...
Click to expand...
Click to collapse
Interesting..
I also saw that they are now saying that finger print logins will not work unless you update. Can't do fingerprint anyway because of root etc..
Update: I received a text message saying that older versions of the app will no longer work in 30 days.
You are using an old version of our app which we will be switching off in 30 days. To continue to use our Mobile Banking app, you will need to update your phones operating system to 6.0 and visit your app store to update to the latest version of our app. If you are unable to update your phones operating system, you can continue to use Online Banking as an alternative.
Click to expand...
Click to collapse
The most recent version of the app (Dec-3rd-2018, 05.14.0000.63.0) continues to give the aforementioned error message. In the meantime, I will continue to use version 05.14.0000.36.0.
It would be nice for Natwest to give an official statement on this.
htr5 said:
Update: I received a text message saying that older versions of the app will no longer work in 30 days.
The most recent version of the app (Dec-3rd-2018, 05.14.0000.63.0) continues to give the aforementioned error message. In the meantime, I will continue to use version 05.14.0000.36.0.
It would be nice for Natwest to give an official statement on this.
Click to expand...
Click to collapse
I've not received a text but keep getting a popup when I login...
Not sure what version I'm on though ... no idea what will do if it stops working
I had the same problem too. I have figured out that the incompatibility seems not to be with root but with Xposed.
The app works with root enabled, it does not when Xposed is on.
Here how I managed to make it work:
I uninstalled the app, disabled root from my settings, turned off Xposed, restarted the phone and then installed the app again.
The RBS app worked perfectly, also with root on, until I re-enabled Xposed. Once I enable Xposed, I get the Error 04 message.
It works again every time I disable Xposed and restart the phone. It is a bit of a workaround but it works, and luckily it is not an app I use every day.
I am on an S5 with Lineage 15.1.
I can also confirm the issue is with xposed. If you turn off xposed from the installer and an then reboot, the app banking app will work fine.
I have tried installing NatWest in the work profile using the Islands app but it didn't work. The Sudohide xposed module also didn't work. There are no relevant permissions in the NatWest app that can be revoked.
Maybe something similar to DBXposed module could be a workaround?
https://forum.xda-developers.com/xposed/modules/dbxposed-bypass-root-xposed-detection-t3536406
I have no experience in compiling or programming though
I suppose if you turn off Xposed from the installer all of the xposed modules stop working?
Got my 29 day count down now before this version of Natwest stops working .. ugh ... theres just a few simple things I have on Xposed but they make the phone so much better.. e.g. Xinsta and ChromePie
oli356 said:
I suppose if you turn off Xposed from the installer all of the xposed modules stop working?
Got my 29 day count down now before this version of Natwest stops working .. ugh ... theres just a few simple things I have on Xposed but they make the phone so much better.. e.g. Xinsta and ChromePie
Click to expand...
Click to collapse
I have systemless Xposed installed meaning that it can be disabled really easily from within the app. A soft reboot keeps some of my modules to continue working such as the cosmetic tweaks.
The reboot process takes about 45 seconds each way but I'm finding myself using the browser website for quick transfers anyway.
Hi guys, i was researching a bit how to make natwest app working along with magisk and edxposed, i found that adding natwest to edxposed blacklist did the job, since i saw natwest has an activity looking for hooks...
As simple fingerprint works
Of course also box checked in magisk hide
pincopallowfs said:
Hi guys, i was researching a bit how to make natwest app working along with magisk and edxposed, i found that adding natwest to edxposed blacklist did the job, since i saw natwest has an activity looking for hooks...
As simple fingerprint works
Of course also box checked in magisk hide
Click to expand...
Click to collapse
Frustratingly this doesn't work for me.
Brig1979 said:
Frustratingly this doesn't work for me.
Click to expand...
Click to collapse
Have you cleared natwest data app before?
After set natwest in magiskhide and set natwest in edxposed blacklist can try to clean dalvik and reboot...
It's kinda strange indeed, on my tablet lenovo running aospextended natwest works outofthebox without doin nothing apart from set it into magiskhide, on mi mix3 it worked only after setting it into magiskhide and edxposed blacklist.... It should work as well putting magisk into core mode, but no modules get loaded, so you need reboot, use natwest and then reboot again to reload modules...
pincopallowfs said:
Have you cleared natwest data app before?
After set natwest in magiskhide and set natwest in edxposed blacklist can try to clean dalvik and reboot...
It's kinda strange indeed, on my tablet lenovo running aospextended natwest works outofthebox without doin nothing apart from set it into magiskhide, on mi mix3 it worked only after setting it into magiskhide and edxposed blacklist.... It should work as well putting magisk into core mode, but no modules get loaded, so you need reboot, use natwest and then reboot again to reload modules...
Click to expand...
Click to collapse
Completely forgot to answer this, but i'd tried literally everything!
Updated the natwest app last night and it's now working again (I do still have it added to the the blacklist in Edxposed, and magisk hide set)
I also updated to 05.18.0000.85.0 and it is working now with xposed and root. I am not using any masking tools.
Updated to latest version today as it said app would stop working in couple of days. With magisk hide on and xposed disabled I still get an error and can't login.
Hi, recently Google pay stopped working for me.
I get "you can no longer use Google pay to pay in shops" error. I was on magisk 17.1 and it worked fine for some time then after few weeks it stopped working for no apparent reason.
I updated to magisk 18.1 hoping it would fix it, but the issue still persists.
Before anyone asks, yes I did tick google pay in magisk hide menu.
Does anyone have any ideas?
Edit:
I pass safety net and other apps that don't work with root work without any problem.
https://forum.xda-developers.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
try with magisk canary build 18.2 and tez Hider, clean cache of google pay first:
https://forum.xda-developers.com/apps/magisk/module-tez-hider-t3796567
mati11233 said:
Hi, recently Google pay stopped working for me.
I get "you can no longer use Google pay to pay in shops" error. I was on magisk 17.1 and it worked fine for some time then after few weeks it stopped working for no apparent reason.
I updated to magisk 18.1 hoping it would fix it, but the issue still persists.
Before anyone asks, yes I did tick google pay in magisk hide menu.
Does anyone have any ideas?
Edit:
I pass safety net and other apps that don't work with root work without any problem.
Click to expand...
Click to collapse
Magisk Canary works good, tested it like 6 hours ago
Please follow the discussion of the same issue on the Magisk subforum. As posted by @add_pl the link is
https://forum.xda-developers.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
Keeping the discussion in one place would mean that we arent restarting the discussion numerous times. It would also mean that you would get the solution quicker.
Thanks for the help. I downloaded magisk canary and everything is working fine. I thought it was some issue with my phone not a global issue.
With stable magisk version (current 18.1), you can try revoking Telephone permission from Google Play Services whenever you want to use Google Pay. You need to reassign this permission in order to be able to use other Google applications like Android Auto, Youtube, but revoking Telephone permission from GPS just works fine.
panchaln said:
With stable magisk version (current 18.1), you can try revoking Telephone permission from Google Play Services whenever you want to use Google Pay. You need to reassign this permission in order to be able to use other Google applications like Android Auto, Youtube, but revoking Telephone permission from GPS just works fine.
Click to expand...
Click to collapse
I find revoking telephone permissions from Play services to not work as when you try to run GPay, it will require enabling or else it wont run.
18.2 is the only solution i have found that worked for me.
tofuboi01 said:
I find revoking telephone permissions from Play services to not work as when you try to run GPay, it will require enabling or else it wont run.
18.2 is the only solution i have found that worked for me.
Click to expand...
Click to collapse
Can you check once by clearing cache of GPay and GPS? Also, play protect certification in Play store settings should show 'Device is certified' and safety net check in magisk should pass. Need to select GPay in magisk hide as well. This is working fine for me but yes, It requires enabling/disabling Telephone permission from Google Pay Services (not from Google pay actually) every now and then.
If it is working fine with Magisk 18.2 (that too without doing any manual steps as above), that is better than above
OnePlus 7 , OOS 10.0.7 GM57BA
- rooted with Magisk
- busybox installed
- NO Xposed!!
- magisk package name changed
- magisk Hide enabled in settings
- safetyNet passed
- packages hidden: Barclays and com.anfroid.phone
Issue: cannot set up fingerprint authentication in Barclays app. It works well in any other apps. When following the procedure, the app throws an error T0009 and the message "Error during fingerprint authentication/registration"
I contacted the Barclays team, they don't seem to have the error in their errors list. Possibly to be forwarded from the system?
I also tried to hidein magisk the fingerprint authentication services com.qualcomm.qti.biometrics.fingerprint.service
Maybe I didn't hide all services involved in fingerprint authentication? What else should I try to hide from root?
I'm looking for suggestions.
Hi,
i've got the same issue for ages (with my previous OP6 too) and it's the same with the BA Amex app.
I think it's just an issue of these apps with our OP7 phone?
Have you ever been able to make it work with the phone un-rooted?
bay12 said:
Hi,
i've got the same issue for ages (with my previous OP6 too) and it's the same with the BA Amex app.
I think it's just an issue of these apps with our OP7 phone?
Have you ever been able to make it work with the phone un-rooted?
Click to expand...
Click to collapse
Yes, my wife's phone (also OP) was never rooted and it worked just fine. OP5T, then OP7 and now OP8. And yes, the OP7 Which is mine now,was hers before.
On the default phone configuration it seems to be working just fine.
derei said:
Yes, my wife's phone (also OP) was never rooted and it worked just fine. OP5T, then OP7 and now OP8. And yes, the OP7 Which is mine now,was hers before.
On the default phone configuration it seems to be working just fine.
Click to expand...
Click to collapse
oh interesting! i don't think i've ever tried to used these apps with an unrooted phone.
Please let me know if you manage to solve this issue
Same problem forever with Barclays and OP6
I have the same issue with my OP8T, rooted with patched Magisk image, MagiskHide, but otherwise stock OS. I'm also unable to get any useful information out of Barclays.
This worked fine on my OP3T so it seems to be something with the newer phones.
Hello guys,
I have the same issue with my OP8P, magisk hide,safety net passed. I have another banking app which is working perfect but this for some reason it is not working
I've just had my S9+ replaced on insurance. However I've had to have the phone replaced again as the first replacement they sent had an issue with the touchscreen.
My original phone worked fine with fingerprint authentication in banking apps.
The first replacement I rooted with Magisk and both my banking apps worked OK, but the newest replacement doesn't work with either banking app and just errors when trying to enable fingerprint authentication.
All phones were running the same Alexis ROM, same configuration with Magisk and same kernel.
Really weird.
So sometime throughout today my gpay started failing cts and I also got a notification to update my phone's firmware. Lol
I'm still on August as I haven't had a chance to update yet. I am also running Canary Magisk and Kirisakura so clearly in not taking the OTA.
I guess Google decided to push out some server side stuff. Anyway just thought I'd throw this out there for anyone else with the same to know they are not alone.
CyberpodS2 said:
So sometime throughout today my gpay started failing cts and I also got a notification to update my phone's firmware. Lol
I'm still on August as I haven't had a chance to update yet. I am also running Canary Magisk and Kirisakura so clearly in not taking the OTA.
I guess Google decided to push out some server side stuff. Anyway just thought I'd throw this out there for anyone else with the same to know they are not alone.
Click to expand...
Click to collapse
Same thing happened to me this morning with google pay.
Notification saying google pay can't be used because of uncertified software out of nowhere. Fact is, it's a cat and mouse game. We find an exploit, google patches it.
Try to check if hardware verification is enabled
If hardware verification is enabled, CTS will fail
There are currently three solutions
1.Replace ROM, some ROM hardware verification will not be enabled
2.use MagiskHide Props config Change fingerprint
3.Use the module I made to change the name of the phone to the code name, which can maintain the original fingerprint
cracky.ice said:
Try to check if hardware verification is enabled
If hardware verification is enabled, CTS will fail
There are currently three solutions
1.Replace ROM, some ROM hardware verification will not be enabled
2.use MagiskHide Props config Change fingerprint
3.Use the module I made to change the name of the phone to the code name, which can maintain the original fingerprint
Click to expand...
Click to collapse
I just use the basic module and I'm good... I just wanted to head off the rush of posts about this. Figured it would at least corral some of them into one thread.
CyberpodS2 said:
I just use the basic module and I'm good... I just wanted to head off the rush of posts about this. Figured it would at least corral some of them into one thread.
Click to expand...
Click to collapse
It is very difficult to merge threads, because everyone has different ways, and even the wrong way makes developers difficult