hi need help on dbs banking app detecting root starting from December 2021, i am unable to hide root from dbs digibank app tried magisk hide, xprivacylua. But gpay is working fine . Device htc u11 rooted with magisk 24.1
One more thing if I unroot my device dbs bank app works fine but gpay detecting unlocked bootloader and stopped working
Solved - zygisk and shamiko do the thing
raokashan said:
hi need help on dbs banking app detecting root starting from December 2021, i am unable to hide root from dbs digibank app tried magisk hide, xprivacylua. But gpay is working fine . Device htc u11 rooted with magisk 24.1
One more thing if I unroot my device dbs bank app works fine but gpay detecting unlocked bootloader and stopped working
Click to expand...
Click to collapse
Just try using Magisk brother or you can also try with Magisk 23.0, and just hide the app fully.. and also just change the name of Magisk app.
Already did that no use
raokashan said:
Already did that no use
Click to expand...
Click to collapse
Bypass DBS banking App
Resently BDS banking app(India) is updated.is there any modules to make that work...:rolleyes:
forum.xda-developers.com
Check this out
Tried every version of magisk from 20 to 24.1 no luck, someone got working for this help me
After June update Kotak Bank app also stopped working. It is detecting root even after Universal Safetynet Fix + Shamiko.
abhinavkumar842 said:
After June update Kotak Bank app also stopped working. It is detecting root even after Universal Safetynet Fix + Shamiko.
Click to expand...
Click to collapse
Yeah, cant say what they did within app or server side detecting root, but safety net is passed
raokashan said:
Yeah, cant say what they did within app or server side detecting root, but safety net is passed
Click to expand...
Click to collapse
They did something within the app, nothing server side to detect root. I am able to use older version of Kotak app and disabled auto update.
Can you share apk
raokashan said:
Can you share apk
Click to expand...
Click to collapse
Extracted using another app from older device, most likely it wont work but you can try after renaming it ofcourse. If it doesnt work you can always use net-banking instead of mobile-banking using phone browser, it is also quite secured with OTP codes & password.
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Tech = Spy-Biz said:
Extracted using another app from older device, most likely it wont work but you can try after renaming it ofcourse. If it doesnt work you can always use net-banking instead of mobile-banking.
Click to expand...
Click to collapse
Not working
raokashan said:
Not working
Click to expand...
Click to collapse
now check and see,
In my old phone J2 2018 A7 using Magisk 23 version 5.3.3 is working but under magisk hide the service [ (isolated) BlaBlaBla ] does not show as [ (isolated) Detect Root BlaBlaBla ] so when I install the same version 5.3.3 on A11 it shows [ (isolated) Detect Root BlaBlaBla ] under magisk hide. What that could mean is KB 5.3.3 version bank app is OPTIMIZING itself depending on android version installed in the device.
Version 534 working fine on my device after updating to 536 started detecting root, and i don't have a backup too, if anyone have 534 version share it
L
raokashan said:
Version 534 working fine on my device after updating to 536 started detecting root, and i don't have a backup too, if anyone have 534 version share it
Click to expand...
Click to collapse
Look by apkmirror
@Tech = Spy-Biz kbank-811 v537 got working with usnf modded version
raokashan said:
@Tech = Spy-Biz kbank-811 v537 got working with usnf modded version
Click to expand...
Click to collapse
Yup v537 working.
( FYI, I used Android 11 GSI + USNF MOD Version + Signature Spoofing Enabled + microG Gapps Module with microG-GooglePlayStore frozen + 6 Services from v537 disabled + I installed v537 from aurora ) So thats either a miracle or the KB app Dev had mercy on KB clients
ICICI iMobile from Aurora is working too .
RBL Mobank detects Developer Mode ON & also detects Aurora download & installed using package installer, so wont work unless google Account present which means have to keep that peeemp-azz playstore app inside the phone with a peemped-azz gmail account on the phone, I find all this unnecessary on part of the bank bcoz i know one of the older versions of KB App was working with Superuser permission from Magisk app .
If a bank app asks for SU permissions to work then thats a tradeoff the bank customers wouldnt really mind much bcoz there are plenty other possibly shady apps like SeFix App (malware flagged by Malwarebytes) using root privileges as well (I uninstalled it ofcourse).
I just wish the bank acts more maturedly with its customers coz its relation with its customers is a financial one not to spy on its customers which thankfully its not doing uptill now. By the word "Maturedly" I meant the banks should allow their customers to use rooted devices and should rather focus on other means to find out if security breach is happening real-time or offline remotely from a cloned SIM Card etc. For example -The banks can have some kind of software to check with their customers Mobile Carrier if there are multiple SIM cards registered under the same phone number, that would be better than to cause incovenience to its customers by not allowing them to use their bank app on rooted devices. It doesnt make any business sense unless google is paying/forcing the banks to make their customers use google accounts and Gapps. Thats really sick man! They can just create 2-step Verification or maybe 3 or 4 step verification for their banking apps instead of forcing clients to use google. Absolutely sold-out garbage peemping going on between the banks and google admob. I'm sick to the point of vomit looking at how LOW google is ready to stoop just to secure mainly one presumably sweet corner of the world and to make ships full of spy-money! What a PEEEEMP!
Will it work if you download an un-rooted version of VM's like VMOS, Virtual Android, etc.?
Related
It looks like it should with Magisk, but I can't seem to get it to work. I have pay hidden, using magisk 17.1 and passing safety net. It sticks at card verification. It says "verifying with bank", then kicks me to the payment screen where it says "verification needed". Clicking on that gives me a momentary waiting circle, but nothing else happens. I've tried it with 2 different cards. US998, RR oreo 8.1.
nola mike said:
It looks like it should with Magisk, but I can't seem to get it to work. I have pay hidden, using magisk 17.1 and passing safety net. It sticks at card verification. It says "verifying with bank", then kicks me to the payment screen where it says "verification needed". Clicking on that gives me a momentary waiting circle, but nothing else happens. I've tried it with 2 different cards. US998, RR oreo 8.1.
Click to expand...
Click to collapse
That's not an issue with Pay. If Magisk was being blocked by root/unlocked bootloader, you would get a message when you first fire up Pay that your phone can't be verified so "Google Pay can't run on this device".
Have you contacted your bank to make sure they support it? If it's not being verified with your bank, sounds like you need to call them. For the last few years, my bank didn't. It wasn't until this past year that they actually allowed it.
I'm not sure what the issue was. It wasn't with the bank(s). I was having the same issue with all the cards I tried. Eventually did a wipe and it worked.
nola mike said:
I'm not sure what the issue was. It wasn't with the bank(s). I was having the same issue with all the cards I tried. Eventually did a wipe and it worked.
Click to expand...
Click to collapse
Well that's weird. Glad it's working though! :good:
After installing Google Pay, hide it using Magisk Hide, and Hide Magisk Manager in Magisk Settings. Then remove phone permission from Google Play Services and Play Store. Now you can register Pay on your rooted phone. After registration is complete, you should allow phone permission to Play Services and Play Store. This trick works always, I've tested with multiple custom roms with and without selinux enforcing.
If we want to reuse root features should we give phone permissions again ?
If we want to use Google pay again later should we re hide magisk and permissions ?
JackFrost said:
After installing Google Pay, hide it using Magisk Hide, and Hide Magisk Manager in Magisk Settings. Then remove phone permission from Google Play Services and Play Store. Now you can register Pay on your rooted phone. After registration is complete, you should allow phone permission to Play Services and Play Store. This trick works always, I've tested with multiple custom roms with and without selinux enforcing.
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
Sent from my Redmi 4 using Tapatalk
Yes and No
cneeli78 said:
If we want to reuse root features should we give phone permissions again ?
If we want to use Google pay again later should we re hide magisk and permissions ?
Sent from my Redmi 4 using Tapatalk
Click to expand...
Click to collapse
Phone permissions have nothing to do with root features, I didn't exactly understand what do you mean by reuse root features but I don't recall any root solution app or framework asking for Phone Permission. If you are asking about granting phone permission to Google Play Services after Google Pay registration, you should do it, it's not recommended to deny phone permission to Google Play Services. And once you hide Magisk you don't need to change it's state as Magisk will continue to work as expected whether it's hidden or not.
JackFrost said:
After installing Google Pay, hide it using Magisk Hide, and Hide Magisk Manager in Magisk Settings. Then remove phone permission from Google Play Services and Play Store. Now you can register Pay on your rooted phone. After registration is complete, you should allow phone permission to Play Services and Play Store. This trick works always, I've tested with multiple custom roms with and without selinux enforcing.
Click to expand...
Click to collapse
Yes it's working
JackFrost said:
After installing Google Pay, hide it using Magisk Hide, and Hide Magisk Manager in Magisk Settings. Then remove phone permission from Google Play Services and Play Store. Now you can register Pay on your rooted phone. After registration is complete, you should allow phone permission to Play Services and Play Store. This trick works always, I've tested with multiple custom roms with and without selinux enforcing.
Click to expand...
Click to collapse
thanks.its working
You are welcome
Arokia said:
Yes it's working
Click to expand...
Click to collapse
Karthik Arun said:
thanks.its working
Click to expand...
Click to collapse
There is a thanks button you can press if I could help you
JackFrost said:
There is a thanks button you can press if I could help you
Click to expand...
Click to collapse
Am I doing something wrong? I did everything but when I deny phone permissions I get a pop up saying its required to open google pay and cannot get passed that
raguilera510 said:
Am I doing something wrong? I did everything but when I deny phone permissions I get a pop up saying its required to open google pay and cannot get passed that
Click to expand...
Click to collapse
Did you by any chance remove phone permission from Google Pay app? You need to turn off telephone permission from Google Play Services and Google Play Store. Google Pay app needs phone permission to verify the phone number, don't turn off phone permission from Pay, do it for only play store and play services. Hope that helped.
Does not work
Once I renable telephone permission for Google Play Services, googlepay does not work anymore. Asks me to register and then I cannot register as I dont pass the security test. I am on lineage os 15.1
Non rooted lineageOS
I am a real newbie but i do use google pay a lot.
Will google pay just work on lineageOS that wasnt rooted or with magisk install, only with an unlocked bootloader. Or will i need extra work to do before i can use it?
kekekelasomot said:
I am a real newbie but i do use google pay a lot.
Will google pay just work on lineageOS that wasnt rooted or with magisk install, only with an unlocked bootloader. Or will i need extra work to do before i can use it?
Click to expand...
Click to collapse
Extra work? There's no extra work to install Magisk. It's part of the instructions when unlocking the bootloader and installing TWRP. Magisk Hide (part of Magisk Manager) lets Google Pay work.
When you unlock the bootloader and install TWRP (which you need to install ROMs), the next steps in the process include flashing three files IN TWRP: the no root checker, the no encryption and Magisk. I'm not clear why you would just stop short of finishing the process.
Unless you use Magisk Hide, simply unlocking the bootloader will cause Google Pay to then fail -- even without installing TWRP or a ROM.
Unlocked bootloader by itself -- without Magisk Hide (a part of Magisk) -- will cause Safety Net to fail. Google Pay will not work.
Why do you want Lineage OS without root? That's like owning a car with internal combustion engine, but refusing to put in gasoline. (or refusing to charge a Tesla.) You can do it, but to me it doesn't make sense.
You might as well stay on stock unrooted firmware.
I have stock rooted firmware. I'm not using any custom ROMs -- but at least I have root and my Magisk mods.
ChazzMatt said:
Extra work? There's no extra work to install Magisk. It's part of the instructions when unlocking the bootloader and installing TWRP. Magisk Hide (part of Magisk Manager) lets Google Pay work.
When you unlock the bootloader and install TWRP (which you need to install ROMs), the next steps in the process include flashing three files IN TWRP: the no root checker, the no encryption and Magisk. I'm not clear why you would just stop short of finishing the process.
Unless you use Magisk Hide, simply unlocking the bootloader will cause Google Pay to then fail -- even without installing TWRP or a ROM.
Unlocked bootloader by itself -- without Magisk Hide (a part of Magisk) -- will cause Safety Net to fail. Google Pay will not work.
Why do you want Lineage OS without root? That's like owning a car with internal combustion engine, but refusing to put in gasoline. (or refusing to charge a Tesla.) You can do it, but to me it doesn't make sense.
You might as well stay on stock unrooted firmware.
I have stock rooted firmware. I'm not using any custom ROMs -- but at least I have root and my Magisk mods.
Click to expand...
Click to collapse
Thank you. Just flash magisk and hide google pay using it. From what i under stand is i have root access+ unlocked bootloader+ google pay functionalities. And the reason not to root is just because i want the feel of stock android+some nice modification
Recently had this problem with G Pay also. Found where some just deleted 'cache' and 'data' from Google Play and Play Services. That worked for me too. Of course hide Magisk etc first.
AsItLies said:
Recently had this problem with G Pay also. Found where some just deleted 'cache' and 'data' from Google Play and Play Services. That worked for me too. Of course hide Magisk etc first.
Click to expand...
Click to collapse
Thank you. That's all I had to do to get it working for me.
Hi, I'm not able to get Google Pay working on my rooted V30. I unlocked bootloader and flashed TWRP, no checker, no encryption, using chazzdave's WTF tutorial. Now have Havoc installed. I have hidden root from play, play services, and pay. I've hidden magisk by scrambling APK. I've cleared cache and data of play, play services, and pay. I've revoked telephone permission for play services and play store, although I had to re-enable play services telephone permission during card setup because pay wouldn't go any further. But nothing. Just error message that root is enabled and cannot proceed.
One of my banking apps which didn't work on root is working after hiding from magisk, but no Google pay. Has something updated and a loophole been closed?
Thanks
Forsh said:
Hi, I'm not able to get Google Pay working on my rooted V30. I unlocked bootloader and flashed TWRP, no checker, no encryption, using chazzdave's WTF tutorial. Now have Havoc installed. I have hidden root from play, play services, and pay. I've hidden magisk by scrambling APK. I've cleared cache and data of play, play services, and pay. I've revoked telephone permission for play services and play store, although I had to re-enable play services telephone permission during card setup because pay wouldn't go any further. But nothing. Just error message that root is enabled and cannot proceed.
One of my banking apps which didn't work on root is working after hiding from magisk, but no Google pay. Has something updated and a loophole been closed?
Thanks
Click to expand...
Click to collapse
Use Magisk v19. I believe it's a beta at the moment
PhonePe is a UPI based Payments Platform which offers immense cashbacks.
[BOLD] (Haven't used before? Get ₹100 in your Wallet using my referral: https://phon.pe/ru_debo8w9xb ) [/BOLD]
Since the latest update, PhonePe has taken counter-active measures against Root Users.
If you have used SuperSU, then you've to get through the helluva process of getting MagiskSU.
If you've MagiskSU, then you're covered. Simply go to Magisk Hide, search for PhonePe and enable the checkbox next to PhonePe.
You might want to clear Cache (optional) and voila your transactions are now happening.
Update: You can use Island by Oasis Feng to create a Sandboxed Work Environment and install the app to achieve the same results!:silly:
debmaj2 said:
Since the latest update, PhonePe has taken counter-active measures against Root Users.
Click to expand...
Click to collapse
Are You Sure About This ?
i also can not send money but i can receive
i'm rooted with superSu
Root tool
What is the Rooting tool you used to root ?
reza48 said:
Are You Sure About This ?
i also can not send money but i can receive
i'm rooted with superSu
Click to expand...
Click to collapse
Yes, just backup, load Custom ROM and Clean Flash Magisk
Joymerry said:
What is the Rooting tool you used to root ?
Click to expand...
Click to collapse
It's not a tool, it a method, MagiskSU.
Hi,
I wanted to know if this still works. For me, once I put PhonePe into magisk hide, it simply doens't open. It just shows white screen and freezes. With GPay, it is not able to verify my OTP. Can someone confirm if there are any other alternative option
senthilrameshjv said:
Hi,
I wanted to know if this still works. For me, once I put PhonePe into magisk hide, it simply doens't open. It just shows white screen and freezes. With GPay, it is not able to verify my OTP. Can someone confirm if there are any other alternative option
Click to expand...
Click to collapse
Updated OP
Did all the steps mentioned above. Still doesn't work
debmaj2 said:
PhonePe is a UPI based Payments Platform which offers immense cashbacks.
[BOLD] (Haven't used before? Get ₹100 in your Wallet using my referral: https://phon.pe/ru_debo8w9xb ) [/BOLD]
Since the latest update, PhonePe has taken counter-active measures against Root Users.
If you have used SuperSU, then you've to get through the helluva process of getting MagiskSU.
If you've MagiskSU, then you're covered. Simply go to Magisk Hide, search for PhonePe and enable the checkbox next to PhonePe.
You might want to clear Cache (optional) and voila your transactions are now happening.
Update: You can use Island by Oasis Feng to create a Sandboxed Work Environment and install the app to achieve the same results!:silly:
Click to expand...
Click to collapse
Please check screenshots for more details.
Its working thankyou
Latest PhonePe app not visible in magisk hide.
I have installed phonepe(latest) and the app itself is not visible inside the magisk hide options. Any workaround?
Phonepe app not working with Latest LSposed, Zygisk, Shamiko SNFix. App opens and runs, but when UPI transaction is attempted, then it prompts that not allowed on rooted device.
RootBeer clears the device as Non Rooted.
Momo detects Xposed framework, Zygisk and Injected Zygote
PhonePe app "TRANSACTION FAILED DUE TO SECURITY REASON" on POCOPHONE + LOS16
POCOPHONE with LOS16 Unofficial. THIS IS NOT A ROOTED DEVICE, only LOS 16 flashed on it.
On the Phonepe app cant get UPI transactions through, keep getting this message "TRANSACTION FAILED DUE TO SECURITY REASON"
Phonepe app has phone and sms access.
google play store disabled, google play services enabled with no permissions granted to it. wifi + cellular data access enabled.
Also keep getting this error while connecting the device to the internet - "google play services error - android setup is having trouble with google play services. please try again" not sure if this is related to the failing transaction
Thanks in advance.
TheFirstGladiator said:
POCOPHONE with LOS16 Unofficial. THIS IS NOT A ROOTED DEVICE, only LOS 16 flashed on it.
On the Phonepe app cant get UPI transactions through, keep getting this message "TRANSACTION FAILED DUE TO SECURITY REASON"
Phonepe app has phone and sms access.
google play store disabled, google play services enabled with no permissions granted to it. wifi + cellular data access enabled.
Also keep getting this error while connecting the device to the internet - "google play services error - android setup is having trouble with google play services. please try again" not sure if this is related to the failing transaction
Thanks in advance.
Click to expand...
Click to collapse
check for safety net. i too use phonepe , only way to make transaction work is to hide it in magisk hide
Mohan0004 said:
check for safety net. i too use phonepe , only way to make transaction work is to hide it in magisk hide
Click to expand...
Click to collapse
The device doesnt pass the safetynet test due to CTS PROFILE MATCH failure. This in not a rooted device. No magisk on it, only flashed LOS16 on it.
Would this device have to be rooted to get magisk hide? Is there any non root solution considering the device isnt rooted?
TheFirstGladiator said:
The device doesnt pass the safetynet test due to CTS PROFILE MATCH failure. This in not a rooted device. No magisk on it, only flashed LOS16 on it.
Would this device have to be rooted to get magisk hide? Is there any non root solution considering the device isnt rooted?
Click to expand...
Click to collapse
This is happening on all LOS based roms afaik. Try AOSP based roms if you want to use banking apps without rooting your phone
viv29 said:
This is happening on all LOS based roms afaik. Try AOSP based roms if you want to use banking apps without rooting your phone
Click to expand...
Click to collapse
Gapps pico is flashed on this device, is there any not root solution for this situation? any solution is greatly appreciated.
TheFirstGladiator said:
Gapps pico is flashed on this device, is there any not root solution for this situation? any solution is greatly appreciated.
Click to expand...
Click to collapse
use pe instead los
Am I mistaken or you cannot use any banking app on a phone that has its bootloader unlocked?
Mohan0004 said:
use pe instead los
Click to expand...
Click to collapse
PE serves a different user base and LOS has its own purpose. Any other solution?
Ortobrox1312 said:
Am I mistaken or you cannot use any banking app on a phone that has its bootloader unlocked?
Click to expand...
Click to collapse
Any not root solution on LOS for someone who doesnt want to flash magisk or root the pocophone but yet access payment apps?
Not that I know of, though Im not really acquainted with it either, but there are some disclaimers when you install a banking app, for example an NFC payment one that does state that bootlocker unlocked, rooted or any devices that have their software tampered with are not eligible for use of such apps. (Or so)
I am facing the same problem..google tez is working fine but upi in phonepy is not working....did uh find any solution to this problem..?
Phonepe Customer care no.9002223308 / 9330921710
All over India Aajjo co Customer care helplineany complaint regarding debit or credit card cheque book balance enquiry
UCO Bank customer care helpline number balance enquiry
Customer STOMER CARE HELP-LINE 9330921710
6294203577
Any Transaction Failure please contact Hr . 24*7
9002223308
Headquarters -9002223308
Noida secter-+919002223308
Banglore-+916294203577
Chennai t-nagar-+9002223308
You will not pass safetynet if your bootloader is unlocked
Google has updated their safety net api to use hardware attestation to pass. If your bootloader is unlocked, say goodbye to netflix, McDonald's, poGo, banking apps and a lot more that use safetynet.
The developer of magisk has stated nothing can be done about it, you can look up his twitter and XDA. Google will start implementing the new safety net with hardware attestation stage by stage to all devices in coming days.
For now not everyone is affected but eventually will be since it is being rolled out in stages. You're one of the guys that got affected in the early stage
You have to either choose between banking apps or a custom rom/unlocked bootloader/root.
jahraKaL said:
Google has updated their safety net api to use hardware attestation to pass. If your bootloader is unlocked, say goodbye to netflix, McDonald's, poGo, banking apps and a lot more that use safetynet.
The developer of magisk has stated nothing can be done about it, you can look up his twitter and XDA. Google will start implementing the new safety net with hardware attestation stage by stage to all devices in coming days.
For now not everyone is affected but eventually will be since it is being rolled out in stages. You're one of the guys that got affected in the early stage
You have to either choose between banking apps or a custom rom/unlocked bootloader/root.
Click to expand...
Click to collapse
I don't know if you're wrong or not, that's not for me to decide, but banking apps are working now, EVEN NETFLIX. If you have xposed, just uninstall it. Install magisk hide module from magisk manager and hide magisk from settings of magisk manager and you're good to go.
---------- Post added at 07:26 PM ---------- Previous post was at 07:24 PM ----------
jahraKaL said:
Google has updated their safety net api to use hardware attestation to pass. If your bootloader is unlocked, say goodbye to netflix, McDonald's, poGo, banking apps and a lot more that use safetynet.
The developer of magisk has stated nothing can be done about it, you can look up his twitter and XDA. Google will start implementing the new safety net with hardware attestation stage by stage to all devices in coming days.
For now not everyone is affected but eventually will be since it is being rolled out in stages. You're one of the guys that got affected in the early stage
You have to either choose between banking apps or a custom rom/unlocked bootloader/root.
Click to expand...
Click to collapse
And bootloader has nothing to do with hardware attestation. It's not a physical thing that you unlock. It's software related that boots up the recovery and the OS.
A13 stock. Magisk 25203. PS Remote Play app 5.5, and hidden in the Magisk deny list, like other apps.
Other typical root detecting apps foiled, but not this one. Hiding the Magisk manager itself didn't help.
Suggestions?
Assuming you're on the stock ROM, else you might need to use MagiskHide Props Config. Try turning on Zygisk and adding Displax's version of USNF and Shamiko (note: Shamiko is a closed-source root hider, so your call if you trust it). Keep in mind that if you use Shamiko, then the "enforce deny list" switch needs to be off. Shamiko reads from the list and handles it instead (so you do still need to have Google Play Services and PS Remote Play in the deny list). So far I haven't had anything detect root with this setup as long as it's in my deny list, though I don't have a PlayStation so I can't test it with this specifically.
I am on A13 stock. I'll look into this. FWIW, one doesn't need a PlayStation to see the app PS Remote App fail the root check, which is upon opening it, resulting in error 88001003
PS Remote Play - Apps on Google Play
Access your PS5 or PS4 wherever you go.
play.google.com
Interesting, it's happening the moment you open the app? I don't have a Playstation account, but I can open the app and get in far enough to see the account login screen with no error. That's on my system with the above utilities installed as well as Magisk and LSposed, running the Android 13 QPR1 beta. If you set all that up and it's still happening, try clearing the PS Remote Play app's data, too.
Jaitsu said:
Interesting, it's happening the moment you open the app?
Click to expand...
Click to collapse
Yes. It may be using some data from the general PS App to auto-login, but it appears as instantaneous error to me, even after full storage/cache wipe and force close.
I just updated USNF, and installed the MOD version on top of that as you suggested, still no go. Disney+, Nintendo, other apps that check still work. Play Store certified, pass YASNAC.
Haven't tried the Shamiko thing yet
Are you hiding the Magisk app itself?
I'm using Canary manager, btw
deusfaux said:
Yes. It may be using some data from the general PS App to auto-login, but it appears as instantaneous error to me, even after full storage/cache wipe and force close.
I just updated USNF, and installed the MOD version on top of that as you suggested, still no go. Disney+, Nintendo, other apps that check still work. Play Store certified, pass YASNAC.
Haven't tried the Shamiko thing yet
Are you hiding the Magisk app itself?
I'm using Canary manager, btw
Click to expand...
Click to collapse
I am hiding the Magisk app itself, with the default "Settings" name. Normal release (25.2/25200) of Magisk. Do you have any other root-related apps the PS Remote Play app might be looking for? (Though I myself have Fox's Magisk Module Manager, LP, the TWRP app, and Franco Kernel Manager installed on my phone and they don't seem to be setting it off.)
I'd suggest turning off USB debugging. I had similar issue with some of my banking and other apps and tried every possible solution but didn't work. Finally I read somewhere to turn off USB debugging and Eureka!!
I've narrowed it to something the recent app version 5.5 is doing
Versions 5.0 and earlier have no problems loading.
My USB debugging is/was off.
It must be looking at / for some other app I have installed, which is really annoying to troubleshoot
Hello,
As you said, I downgraded the app to the version 5.0 ans now I can login
But I can't associate the playstation
It ask me to upgrade to the last version and if i refuse, the association failes.
Do you have the same problem ?
Thx
twingo_man said:
Hello,
As you said, I downgraded the app to the version 5.0 ans now I can login
But I can't associate the playstation
It ask me to upgrade to the last version and if i refuse, the association failes.
Do you have the same problem ?
Thx
Click to expand...
Click to collapse
Ver 5.01 asked me if I wanted to update but i could choose 'later' and successfully connect to my PS5
i choose later but I can't connect to my ps5
i will try to put it on wifi...
twingo_man said:
i choose later but I can't connect to my ps5
i will try to put it on wifi...
Click to expand...
Click to collapse
We should also try to determine what exactly latest version is detecting and preventing app from working
I have a rooted Samsung SG10Exynos/OS9 that bypasses SafetyNet with the help of Magisk 26.0 & safetynet-fix-v2.4.0-MOD_1.2 (meets BASIC INTERGITY) that I have been using the Starling Bank app 2.92.1.79025 without an issue. I stupidly upgraded to the latest version and got the attached screenshot saying that I had 14 days to restore the device to factory settings (I was still able to use the app after pressing ok). I even more stupidly thought that I could revert back to the previous version that I was using, using Titanium Backup which failed (the app would just flash continuous on launch) and then Swift backup (where it would just repeatedly crash even even before being launched requiring a force stop)
If I wipe data/uninstall/restart phone and install fresh from google play, I now get the attached screenshot saying again to restore to factory, but the button says close app. So being a digital bank, I'm now locked out of my account.
I've tried to install previous versions from APKMirror mirror after wiping data/uninstall/restarting phone, and then just restoring my data with my Titanium/Swift backups but still no joy.
Does anyone know how to downgrade/install not the latest version of Starling Bank, which doesn't have the increased STRONG INTERGITY check?
nukescript said:
I have a rooted Samsung SG10Exynos/OS9 that bypasses SafetyNet with the help of Magisk 26.0 & safetynet-fix-v2.4.0-MOD_1.2 (meets BASIC INTERGITY) that I have been using the Starling Bank app 2.92.1.79025 without an issue. I stupidly upgraded to the latest version and got the attached screenshot saying that I had 14 days to restore the device to factory settings (I was still able to use the app after pressing ok). I even more stupidly thought that I could revert back to the previous version that I was using, using Titanium Backup which failed (the app would just flash continuous on launch) and then Swift backup (where it would just repeatedly crash even even before being launched requiring a force stop)
If I wipe data/uninstall/restart phone and install fresh from google play, I now get the attached screenshot saying again to restore to factory, but the button says close app. So being a digital bank, I'm now locked out of my account.
I've tried to install previous versions from APKMirror mirror after wiping data/uninstall/restarting phone, and then just restoring my data with my Titanium/Swift backups but still no joy.
Does anyone know how to downgrade/install not the latest version of Starling Bank, which doesn't have the increased STRONG INTERGITY check?
Click to expand...
Click to collapse
It will force you to use the latest app.
Block firebaseremoteconfig.googleapis.com
theoneofgod said:
It will force you to use the latest app.
Block firebaseremoteconfig.googleapis.com
Click to expand...
Click to collapse
Also having the same issue. Is this something I should be blocking in Zygiskhide? I can't see it there. Googling the above isn't helping me.
Undeadwolfy said:
Also having the same issue. Is this something I should be blocking in Zygiskhide? I can't see it there. Googling the above isn't helping me.
Click to expand...
Click to collapse
You could try Magisk Delta as it now acts as whitelist so you add only what you want with root. This won't bypass Starling security though. You need to also block address above.
Undeadwolfy said:
Also having the same issue. Is this something I should be blocking in Zygiskhide? I can't see it there. Googling the above isn't helping me.
Click to expand...
Click to collapse
Blocking this address (firebaseremoteconfig.googleapis.com) through AdAway has fixed it for me! That is along with all the things that were needed to run it previously.
theoneofgod said:
You could try Magisk Delta as it now acts as whitelist so you add only what you want with root. This won't bypass Starling security though. You need to also block address above.
Click to expand...
Click to collapse
I think the part where I'm stuck is, what would you suggest to block that address? I can't do that in HMA or in Denylist because it doesn't exist.
I've tried blocking in AdAway and manually adding and still getting Starling recognising root.
I've blocked anything Google Play Services, Play Protect, Wallet too. Starling is my main bank. Has only been an issue in the last couple weeks.
A13 P6 Pro running the April security update 13 (TQ2A.230405.003.E1), Magisk 26101, USNF 2.4.0 Mod 1.2, passing Safetynet Basic+ CTS.
Will look at Magisk Delta next.
marian42 said:
Blocking this address (firebaseremoteconfig.googleapis.com) through AdAway has fixed it for me! That is along with all the things that were needed to run it previously.
Click to expand...
Click to collapse
This isn't working for me :/. Can you share what other modules you're running/how you've set up Magisk?
I followed the directions in this video.
I didn't do the final step where he renames the Magisk app, seems that it isn't necesary.
The YASNAC app shows that the device passes "Basic integrity" and "CTS profile match".
Also remember that blocking firebaseremoteconfig.googleapis.com might break other apps that use this domain (I've found one so far).
Undeadwolfy said:
I think the part where I'm stuck is, what would you suggest to block that address? I can't do that in HMA or in Denylist because it doesn't exist.
I've tried blocking in AdAway and manually adding and still getting Starling recognising root.
I've blocked anything Google Play Services, Play Protect, Wallet too. Starling is my main bank. Has only been an issue in the last couple weeks.
A13 P6 Pro running the April security update 13 (TQ2A.230405.003.E1), Magisk 26101, USNF 2.4.0 Mod 1.2, passing Safetynet Basic+ CTS.
Will look at Magisk Delta next.
Click to expand...
Click to collapse
It's a recent update that broke it.
Try Magisk 26.1, enable Zygisk and enforce deny list. Add systemless hosts. Add only Starling to the deny list.
Install safetynet fix 2.4.0 mod 1.2 by displax.
Add the domain I posted to adaway blocklist. Make sure its enabled and in root mode.
theoneofgod said:
It's a recent update that broke it.
Try Magisk 26.1, enable Zygisk and enforce deny list. Add systemless hosts. Add only Starling to the deny list.
Install safetynet fix 2.4.0 mod 1.2 by displax.
Add the domain I posted to adaway blocklist. Make sure its enabled and in root mode.
Click to expand...
Click to collapse
That's exactly how I have it running now. No change.
Undeadwolfy said:
That's exactly how I have it running now. No change.
Click to expand...
Click to collapse
It's the domain that did it for me. Working fine as of now.
theoneofgod said:
It's the domain that did it for me. Working fine as of now.
Click to expand...
Click to collapse
Thanks for updating. I have both of these in my AdAway too
Code:
firebaseinstallations.googleapis.com
firebaseremoteconfig.googleapis.com
Nothing doing
Undeadwolfy said:
Thanks for updating. I have both of these in my AdAway too
Code:
firebaseinstallations.googleapis.com
firebaseremoteconfig.googleapis.com
Nothing doing
Click to expand...
Click to collapse
Clean install for Starling? I'm trying to think if I did something else.
Oh. Have you "hidden" Magisk?
Just to weigh in here, I can confirm blocking:
firebaseremoteconfig.googleapis.com
Does indeed allow the Starling app to work. Yes blocking Firebase is going to stop some applications working, but you could always pause AdAway until you are done using the problematic app then resume AdAway when you want to use Starling.
Many thanks @theoneofgod
Not working
Reverting the Starling app back to version 2.95.1.79953 fixes things - just don't forget to re-add it to the Deny List.
I'll probably stay on this version until a new fix is found for the current version 2.96.0.80202.
darsh said:
Reverting the Starling app back to version 2.95.1.79953 fixes things - just don't forget to re-add it to the Deny List.
I'll probably stay on this version until a new fix is found for the current version 2.96.0.80202.
Click to expand...
Click to collapse
Wild, even this didn't work for me. No idea why I'm having issues.
Hi All
Quick update - Can confirm that rolling back to 2.95.1.79953 does fix things for now
This is using adaway to block the Firebase URLs in a custom host file and using enforce denylist. It doesnt work beyond that for now.
I swapped over to Magisk Alpha for now but i dont know what Starling are doing in the background to see that you have root at this point. Its very annoying
- Edit 2
They seem to be detecting the Enforce Denylist in Magisk (In any form)
Disabling it on version 2.95.1 shows the app can see root. Enabling it allows the app to proceed as if you are not rooted.
Give KernelSU a try if you can. No modules or any workarounds required.
theoneofgod said:
Give KernelSU a try if you can. No modules or any workarounds required.
Click to expand...
Click to collapse
Isnt that the same as the setting in magisk that hides root from everything not on the su list. Which also doesnt work.