Related
I've had a N5 since they came out, however I haven't rooted until now. I read GFE has some root detection built in. I'm am wondering my options to continue to use this app?
Probably an Xposed module.
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.
I've a VoLTE/VoWiFi activated Telstra/Boost SIM that's confirmed to work fine with both stock-standard Moto G 5G Plus & iPhone 11 Pro Max, delivering those features in Australia.
Rog Phones in general & Rog phone 5 in particular are known to lack VoLTE/VoWiFi features with all of the Australian carriers. ASUS Zentalk forum has a few threads about it. (Of course, I too escalated it there for any official help, but none will be forthcoming anytime soon, from what I understand ). I'm genuinely in need of VoLTE at work due to terrible 3G but decent 4G there; and at home in need of VoWiFi due to terrible 3G but excellent WiFi backed by snappy fibre Internet connection.
My phone is an ASUS_I005DA model with build number WW_18.0840.2106.86. Neither "4G Calling" nor "Wi-Fi calling" settings are visible by default, but upon dialling "*#*#3642623344#*#*", those options become available. Though those features can be activated/toggled (and they stick around till the next reboot), they actually don't really make those features work (i.e., phone still drops down to 3G when making phone calls; similarly, calls simply don't go through WiFi, as is proven in airplane mode with WiFi on). This I understand is due to lack of .mbn files for the modem to support Australian carriers in general, Telstra in particular. (I gather that with previous Rog phone models, by injecting .mbn file(s) into the modem image, folks were able to get VoLTE and VoWiFi working in Australia.) I'm essentially looking for precise/tested/proven steps to accomplish just that but on Rog Phone 5.
This is where I've had it both boot loader unlocked & the system rooted with Magisk, in preparation for undertaking any and all such steps.
Has anybody been able to successfully access modem (i.e., Qualcomm Snapdragon X60 modem on Snapdragon 888 SoC found on this phone) from Windows or Linux systems for this sort of work? If yes, especially for Windows, what drivers did you use? (name, version info & where to download them from would greatly help) What additional software did you use on the Windows computer end (such as QPST) & on the phone end (such as QCOMDiagMode.apk & what version & from where was it sourced please?) etc. would be of great help.
A dumb question: Would it be at all possible to flash modem with updated image (incorporating the necessary .mbn file(s)) from within Android itself? Or Android itself doesn't have ADB to help with such tasks?? Just curious as I'm fine to work off either Windows or Linux end.
Thanks in advance for any useful guidance & direction.
The most likely answer would be to find how they made or picked the files with the 3 and try to make or find parallel 5 versions. The files should be compatible with fastboot (mbn is one of the extensions they use for firmware images).
[Guide] Enabling VoLTE/VoWiFi v2
Preface With this guide I can officially deprecate the other guide I wrote, as we will no longer have to hack together a solution by loading profiles for other carriers. Meaning, that this should just work provided an mbn exists for your carrier...
forum.xda-developers.com
It's also going to be an extremely experimental process, so the only tested and proven way will be to let someone else do it first. Hopefully you can find someone else in Australia with the same issue that is willing to put their device up for testing.
Is there a working guide to enable the AsusVoLTE App on Android 11 ?
Mine keeps saying root is not available,
and the USB command to enable PDC mode -
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
doesnt work for me..
any ideas ?
JazonX said:
Is there a working guide to enable the AsusVoLTE App on Android 11 ?
Mine keeps saying root is not available,
and the USB command to enable PDC mode -
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
doesnt work for me..
any ideas ?
Click to expand...
Click to collapse
Can't detect root · Issue #2 · HomerSp/AsusVoLTE
Hi, I'm trying to use your app but any button returns: Failed enabling <feature>, are you rooted? The strange thing is that I have rooted my phone with Magisk and root checker is successful... Can ...
github.com
If you look at the code for the app, it is basically performing the setprop commands on your behalf. Not sure how far you'll get with the app fixed.
Regardless, I sent along a pull request to fix root detection
Do not hardcode su binary path by AbandonedCart · Pull Request #3 · HomerSp/AsusVoLTE
This fixes an issue where rooted devices are not recognized (#2)
github.com
twistedumbrella said:
Can't detect root · Issue #2 · HomerSp/AsusVoLTE
Hi, I'm trying to use your app but any button returns: Failed enabling <feature>, are you rooted? The strange thing is that I have rooted my phone with Magisk and root checker is successful... Can ...
github.com
If you look at the code for the app, it is basically performing the setprop commands on your behalf. Not sure how far you'll get with the app fixed.
Regardless, I sent along a pull request to fix root detection
Do not hardcode su binary path by AbandonedCart · Pull Request #3 · HomerSp/AsusVoLTE
This fixes an issue where rooted devices are not recognized (#2)
github.com
Click to expand...
Click to collapse
The setprop command didn't trigger anything like it did on the ROG II.
That why I wanted to try the app..
Just noticed the pull request! Hope @HomerSp would look into it.
JazonX said:
The setprop command didn't trigger anything like it did on the ROG II.
That why I wanted to try the app..
Just noticed the pull request! Hope @HomerSp would look into it.
Click to expand...
Click to collapse
AsusVoLTE/MainActivity.java at master · HomerSp/AsusVoLTE
Enable VoLTE/VoWiFi on the ROG Phone 2. Contribute to HomerSp/AsusVoLTE development by creating an account on GitHub.
github.com
It's literally running the setprop commands, but...
[MOD-ish] AsusVoLTE w/ Root Fix
This is a temporary solution to a pending pull request. This thread will be deprecated if or when the official release is updated. I don't have the original signing key, but there is really no reason to attempt reverse engineering an app that's...
forum.xda-developers.com
Edit: moved to a separate thread, since it is not specific to this issue
I've had VoLTE show up on mine from day one with no problems, using Vodafone AU. I don't get VoWifi though - I don't know if that's dependent on your ISP. I use TPG for broadband at home.
That's great to hear! Thanks for your confirmation.
"Vodafone Wi-Fi Calling is not available to customers on prepaid plans" in Australia, according to this: https://www.vodafone.com.au/support/device/wi-fi-calling
Perhaps you're their prepaid user?
Hopefully, official VoLTE and VoWiFi support for Telstra and Optus isn't too far, seeing how unofficial community support isn't ready just yet.
Did you managed to find a way to write .mbn? In AsusRogPhone2 it was easy (via Diag mode, efstools etc, with A10 though), but in AsusRogPhone5 efstools freezes every time at port listening stage, so this methos it's a no go for now, for some unknown reason.
Vodafone in Australia has VOLTE and WIFI calling for Rog 5. I went from Vodafone (had Volte) to Telstra (Had literally nothing, had 10 support tickets with telstra that first month in regards to getting volte, wifi calling and reception issues) said screw it, went right back to Vodafone, and boom had both Wifi calling and VOLTE on the Rog 5. Plus my reception is god tier. Telstra only supports certain phones (literally like 2 series) and thats it. So yeah. Thats how I solved the VOLTE issue. Should have just stuck with Voda to begin with, but wanted to give Telstra a go. Never again. Garbage service.
Just to wrap-up my original request, as of Nov 2021 firmware update, thanks to ASUS incorporating necessary MBN file(s) for Telstra (and Optus too from what I've heard at other forums) in that firmware update, after dialling Enhanced-4G code, VoLTE and VoWiFi functionalities become available in Settings. Toggling those options does successfully activate both of those functionalities on Telstra network. According to what I've heard on Whirlpool, even Optus is now supported in the same way.
Alas, those settings don't stick over a reboot, so what procedure needs to be done after every reboot. Perhaps ASUS will make them stick in a future firmware update.
It's possible to make them stick across reboots on a rooted phone, using setprop tool.
Thanks
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...
Dear all, I am writing here because I have a very specific issue and I need to deal with it myself.
I have Xiaomi Poco x3 nfc, and I love this phone to bits. I never bothered rooting or flashing any roms so far because I was always happy with stock. Recently however, an issue has popped up.
Grindr, an app I use regularly, has recently pushed an update down our throats that cuts off your access if you are spoofing your location. This is a hazard for me, because I cannot have strangers know exactly how many meters I am from them. So far, I've been able to use mock gps fine, until this update. Mock GPS works even if your phone is not rooted so I used that. However, it no longer serves me now
How can I workaround this? Would root/installing a custom ROM, help with this? Is there a superior way of spoofing your location that Grindr wouldn't be able to detect? Please advise, I literally have no clue how to do this, the last phone I rooted and flashed was the Galaxy S lol. (Original one)
Appreciate the views but a response would be helpful. I can't be the only person on this forum interested in spoofing location
Chrsp said:
How can I workaround this?
Click to expand...
Click to collapse
The app is detecting that you are spoofing the location. To bypass that in unrooted device, you will need to decompile the apk and remove the checks which do that. If you are in rooted device with Magisk, you only need to install this LSPosed module: https://github.com/ThePieMonster/HideMockLocation
If you can't find a modded apk or made one yourself, you will need to root the phone
Ok thx for the help. Will Grindr detect magisk?
Or maybe are you able to provide me with a modded Grindr apk?
Lastly. I'm in stock. Never rooted or unlocked anything. How do I get started?