I can't seem to get Tap & Pay to work, despite having it set up.
In a possibly unrelated note, I can't get Xposed to work at all. Once I get it all set up and do a reboot, com.android.systemui just spam crashes until I disable Xposed.
darthespa said:
I can't seem to get Tap & Pay to work, despite having it set up.
In a possibly unrelated note, I can't get Xposed to work at all. Once I get it all set up and do a reboot, com.android.systemui just spam crashes until I disable Xposed.
Click to expand...
Click to collapse
I don't have my phone handy, but I think I had to install a different version of Xposed for KitKat. I know that I definitely had to get a different version of GravityBox, and I had to remove MotoXposed entirely.
I'm on the first 4.4 soak. A couple issues I've found so far are:
1) "Wireless display" (miracast) performance is horrible. I've got the Netgear receiver and it works great with my laptop & Nexus 7, but is awful with my Droid Maxx.
2) USB OTG doesn't work anymore. I was able to sorta get it working by installing an app, but the app crashes after mounting/unmounting. StickMount does not work. (I forget which app I'm using right now.)
Hello folks of XDA, especially the Italians one since i'm creating this thread to address one of the most wanted feature of the Italian Intesa San Paolo home banking mobile application for Android, that is making PayGo work with a custom ROM, rooted phone, ecc....
Now let's first state what PayGo is and what's the problem:
PayGo it's a feature of the application that allows you to emulate the contactless chip of one of you credit/debit card through NFC.
PayGo requires your phone to be unrooted and unmodified.
Every attempt to hide the modifications through Magisk Hide allows you to pass the initial warning of the application about Root and Custom ROM but the feature then fails to start with an unknown error.
So, summing up, PayGo won't work even if you pass SafetyNet checks and no one seems to understand what it checks.
Now, I'm a developer but I'm not even close to understand how security checks and stuff works under the hood in Android but my guess is that PayGo checks somehow if the bootloader is unlocked or not. Following this intuition I Googled how to check from application code if the bootloader is unlocked or not. One answer on Andorid Stack Exchange seemed to be really useful: it states that from a dialer app you can check if the bootloader is unlocked or not. Now, that answer reminded me that I was always wondering why Intesa San Paolo app was asking for phone permissions even if it never used them (at least apparently) and an idea popped to my mind:
what if the app asks for phone permissions only to check as dialer if the phone has unlocked bootloader or not?
Well, I revoked phone permission to the app and tried to open PayGo and guess what, it asks phone permissions right away! If you deny them and check "don't ask me again" it won't even open anymore, so my guess may be right.
The problem now is to understand what values is returned to the dialer and how to modify it so that we can test it.
Any good soul that can offer a solution through, i don't know, a Magisk module or something?
Thank you for your time in reading this, I hope it helps someone
@Diomorgan, @Errtu73, @olivercervera may find this thread useful
Have you tried disabling ADB debugging? I have personally tested PayGo and works
olivercervera said:
Have you tried disabling ADB debugging? I have personally tested PayGo and works
Click to expand...
Click to collapse
Yes, it passes the first warning but then fails to start with unknown error
You are lucky because I'm customer of the Intesa group (although I usually don't use this app)
As I said earlier, it works perfectly on my device. The issue is specific to your ROM/device.
I just activated the App and PayGo right now...
olivercervera said:
You are lucky because I'm customer of the Intesa group (although I usually don't use this app)
As I said earlier, it works perfectly on my device. The issue is specific to your ROM/device.
I just activated the App and PayGo right now...
Click to expand...
Click to collapse
Well I tried it on a OnePlus One with Sultanxda LOS but no luck, same on LG G4 with official LOS. Which phone and ROM are you using?
I'll try with my OnePlus 5 keeping the stock ROM, hoping it will work
Lamba92 said:
Well I tried it on a OnePlus One with Sultanxda LOS but no luck, same on LG G4 with official LOS. Which phone and ROM are you using?
I'll try with my OnePlus 5 keeping the stock ROM, hoping it will work
Click to expand...
Click to collapse
I'm on Xiaomi Mi5 and LOS 15.1 (Android 8.1)
LOS is not the problem, probably there was something weird in the ROMs you tried. Some old ROMs are implemented in a way that Magisk can't really work/hide everything, most of them before SafetyNet/Magisk era.
Try with stock ROM and Magisk, you should be fine.
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...