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.
Related
On Angler (Nexus 6p) I flashed the latest stock rom. (After a complete wipe) Afterwards I flashed TWRP and unzipped Magsik. Subsequently I did update to the latest version. After that I changed the packagename of Magsik manager. Furthermore I installed Xposed framework. Afterwards I enabled root hide for the TAN app:
https://play.google.com/store/apps/details?id=com.starfinanz.mobile.android.dkbpushtan&hl=en
This software is meant to give you the tan without using sms services.
Still, the app crashed right at the start without any error notification. Android Version is 8.1 and Magsik is v16. While I did the test, the bootloader was unlocked and TWRP was still the recovery. Can these two things affect the verification of the Banking app? I tried this several times ago in the past, but I was never to make this app running.
If anyone would be able to give helpful advice here, it would be very much appreciated.
Best,
scarline
I have heard that DKB Tan2Go does not work with newer Android versions like Oreo 8.1.x at all.
I can also confirm that. I tried it on a Sony cellphone. The cellphone was not rooted and with a completely new and 'clean' ROM. It was to no avail.
A friend has been forced to buy a chip reader. I am fortunate to be able to use normal TAN lists at the moment. If the DKB tries to exclude me from online banking, I will change the bank.
DKB Tan2Go seems to be one of the worst and most insecure apps ever. The reviews in Google PlayStore confirm this conclusion.
Maybe there will be a solution someday?
DKB TAN2go works with Magisk:
1. Install the TAN2go app (but don't open it)
2. Add the TAN2go app in Magsik Manager in the menu "Magisk Hide"
3. Reboot the phone (I don't know if this is necessary)
4. Open TAN2go, works fine.
**** DKB and this stupid security features which bring absoltuely no security.
That's exactly what I tried - without success. I read that it only worked with an old, obsolete version of Tan2Go. However, I could not find this version and I'm not sure if it still works at all. Did you have the latest version of Tan2Go from Google PlayStore? According to DKB, the recent Tan2Go does not work with devices that was once rooted or had a CustomROM. Even if you go back to stock the Root Counter changed and DKB Tan2Go will never work on this device. Unfortunately, I have to confirm that.
I am working on it to change the bank, because of that.
exaveal said:
DKB TAN2go works with Magisk:
**** DKB and this stupid security features which bring absoltuely no security.
Click to expand...
Click to collapse
Indeed!
Yes, I have installed the latests version of LineageOS, latest version von Magisk and the latests version of the TAN2go app.
I tried that to no avail. I heard once the root counter has a value other than 0, one can't go back. Probably it is also the Sony bootloader and it is different with other devices?
exaveal said:
Yes, I have installed the latests version of LineageOS, latest version von Magisk and the latests version of the TAN2go app.
Click to expand...
Click to collapse
I have a Xiomi Mi5 rooted with Magisk and Tan2go used to work for the last year or so. But yesterday I tried to make a transaction and BOOM! App crashed without an error message. Tried to use a newer Magisk, tried reinstalling the App, nothing helped.
The worst thing is that I do not know if some of my programs have a battery checker or a screen reader plugin that I am not aware of, or if Tan2Go suddenly detects my root. Regardless, crashing without an explanation is like the worst programming practice ever.
Since I do not need this kind of ****e in my life I will probably change Bank, I mean what good is an internet Bank if you cannot do transactions over your mobile device?
Well, willy-nilly I try to use the only other option from DKB: the German TAN Generator. Every other bank equips you with such a device, if they want you to use it. The DKB does not. Actually, I ordered the 3rd TAN Generator and fully paid for it. The first one drains the battery within days. The second one let me type in all the numbers and for no reason the TAN code does not show up on display.
These devices are very annoying anyway, because you have to type in a lot of numbers for every money transfer, the characters are very small (on the laptop) and you have to carry the TAN Generator + the DKB debitcard all the time. Of course this is less secure.
I would change the bank immediately, but want to keep the Visa credit card. I have higher limits on it. That's the only reason. As soon as I found an alternative bank in Europe, I will leave the DKB for good.
It dont worked with Lineage 14.1 but with 15.1 unoffical build on Samsung S4 together with latest Magisk .Rom from here
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-galaxy-s4-lte-android-8-1-oreo/
Works for me
Just tried again. It hasn't been working for me in the past. When downloading & opening the app, I had the same problems.
Then I simply followed the above advice: downloading the app again, didn't open it, hide with Magisk, reboot and opened the app - worked well and was able to register for tan2go.
I am using Lineage 16.0 and Magisk v18.0
DKB already updated their app - they patched it
kyodhin said:
Just tried again. It hasn't been working for me in the past. When downloading & opening the app, I had the same problems.
Then I simply followed the above advice: downloading the app again, didn't open it, hide with Magisk, reboot and opened the app - worked well and was able to register for tan2go.
I am using Lineage 16.0 and Magisk v18.0
Click to expand...
Click to collapse
The app version from September (version 2.3.0) does work, the newer app version from 4.4.19 (version 2.4.0) does not...
Tested working combination: Magisk 18.0, Magisk Manager 6.1, DKB version 2.3.0
Can confirm that, working with magisk and 2.3.0. Not working anymore with 2.4.0.
I have another Tan app from another bank and with the new version it also stops working. Seems that magisk is now quite to popular and they working on better detection. Magisk hide is useless on the recent version of these tan apps.
That really sucks. No way to get 2.4.0 working. Hoping for a magisk fix. Are the magisk developer informed that there are problems with magisk hide? I think others will have similar problems too.
I successfully got 2.4 working again, after it got updated and refused to start.
Following the steps from this post made it work again (German):
https://www.android-hilfe.de/forum/...trotz-magisk.901517-page-2.html#post-11532359
I installed Magisk 19.0 (beta) but contrary to the above mentioned post I left my Magisk modules installed as they were before the update.
Both the Magisk modules as well as TAN2Go 2.4 are now working again.
I had to authenticate the new TAN2Go installation by adding it as a "new device" using SMS verification.
I was not able to get it to run with the above mentioned instuctions.
Device: Nexus 6P (angler), ROM: LineageOS 15.1-20190419, Magisk modules: MagiskHide Props Config (required for ctsProfile test), Busybox for Android NDK (required for MagiskHide Props Config).
DKB Tan2Go crashes immediately when started.
Same for me. The above instruction doesn't work.
Downgrade to 2.3.0
I experienced the same problem. Had to do an important transfer yesterday. And of course Tan2Go-2.4.0 crashed. I'm using Magisk v18.1.
Today I did a downgrade via Aptoide to 2.3.0 and had to register the smartphone again via SMS. This worked without any problems.
To avoid the update problem and keep with 2.3.0:
Start Titanium Backup
Select the DKB Tan2Go App
Long click on the App.
Connect with Google Play Store (forced)
Long click the App again.
Disconnect from Google Play Store
Hope it helps. I don't think there's much to change in the DKB Api. I'll use 2.3.0 until they block it via the API.
If more people confirm the proposed solution with Magisk v19, I'll try it maybe.
I got it working with v2.4.0, but don't know which step was the solution. Switching to the "Canary" channel of Magisk or hiding the Magisk Manager in the settings. I think the last one was the solution.
Can you guys try and give feedback?
Don't forget to uninstall and install the app before testing again.
musv said:
If more people confirm the proposed solution with Magisk v19, I'll try it maybe.
Click to expand...
Click to collapse
I have the same issue. Hopefully it can be fixed via Magisk one day.
Worked with T2G 2.4, 19, 7.1.1
Walhalla said:
I got it working with v2.4.0, but don't know which step was the solution. Switching to the "Canary" channel of Magisk or hiding the Magisk Manager in the settings. I think the last one was the solution.
Can you guys try and give feedback?
Don't forget to uninstall and install the app before testing again.
Click to expand...
Click to collapse
Hi Walhalla,
Hi All
In Settings "General">"Hide" via other apk name it worked for me. V19.0, v7.1.1, Tan2Go 2.4
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
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.?
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
Guys, I have motorola edge 30 rooted via magisk(boot.img patched flash). Google wallet worked for few weeks even when I received warnings that my devices does not meet security requiremens) well last 2 weeks it's a nightmare. I completely remove cache and personal data from google play services. message device meets security requirements is restored and i can use wallet for day or two. then again this message appears when i open wallet your device DOES NOT meet security requirements and neither I can pay by google wallet it somehow warns my bank and it blocks my bank account and card. i call the bank clean cache and personal data from google services app. again my device MEETS security requirements and this works for day or 2. then again same thing your device DOES NOT meet security requirements are you kidding me?? I have turned off app autoupdate option in google account and google play services are in deny list in magisk. it does not seem to help at all. I have shamiko,magish hide props config and universal safety net modules installed.
any idea how to stop stupid google play services make my life miserable? thanks!
Please read this post. You need to install a Magisk module. You must be using minimum Magisk 24.
I have magisk latest version 26. let me check the link. i havent found module name. as stated i have 3 modules installed for this .
Lubo99 said:
I have magisk latest version 26. let me check the link. i havent found module name. as stated i have 3 modules installed for this .
Click to expand...
Click to collapse
Ah, I missed that.
The "official" Universal SafetyNet Fix by kdrag0n does not properly fix the Play Integrity issue, which is why you have to use the Displax mod. If you're on the stock ROM you don't need MagiskHide Props Config.
Make sure you're passing Play Integrity DEVICE and BASIC labels as described in the thread I linked, and if you continue to have issues with Wallet see this thread. I don't even have Wallet/GPay in Magisk DenyList, and they work fine.
V0latyle said:
Ah, I missed that.
The "official" Universal SafetyNet Fix by kdrag0n does not properly fix the Play Integrity issue, which is why you have to use the Displax mod. If you're on the stock ROM you don't need MagiskHide Props Config.
Make sure you're passing Play Integrity DEVICE and BASIC labels as described in the thread I linked, and if you continue to have issues with Wallet see this thread. I don't even have Wallet/GPay in Magisk DenyList, and they work fine.
Click to expand...
Click to collapse
i dont pass only the 3rd strong requirement which dont pass like 90 percent of phones lol. and wallet worked fine. i have reinstalled kdragon unsf by displax mod? lets see if it helps. I wonder why wallet is not yelling that you have magisk installed... lol.. as I am sure this app checks magisk presence too...
By the way when you check the picture magisk package dedpite i hide it! is exposed do you think it can be problem too? According app even fandím magisk package name can be a problem..
Lubo99 said:
i dont pass only the 3rd strong requirement which dont pass like 90 percent of phones lol. and wallet worked fine. i have reinstalled kdragon unsf by displax mod? lets see if it helps. I wonder why wallet is not yelling that you have magisk installed... lol.. as I am sure this app checks magisk presence too...
Click to expand...
Click to collapse
Don't assume. Address the basics first and go from there.
Lubo99 said:
By the way when you check the picture magisk package dedpite i hide it! is exposed do you think it can be problem too? According app even fandím magisk package name can be a problem..
Click to expand...
Click to collapse
What is your Play Integrity response? You seem to be skipping over the basics.
Displax USNF module changes DenyList. Keep in mind that DenyList is not MagiskHide and does not function the same way. Package name hiding is only necessary for apps that specifically detect it. In my case, none of the apps I use do, so the only module I use is USNF by Displax
Now i'm not skipping basics this is on all rooted phones i had. Strong integrity fails (attachment)but i was able to pay Google wallet. Question is which exact package or application IS telling Google wallet that there is security breach . So far Google wallet is not yelling anything after displax mod installed and autoupdates turned off .