Develop Bugs

chase mobile app workaround for rooted devices

Oasis feng has an early release of his app island
It isolates the banking app from your phone enough that the app does not detect that your phone is rooted the new version of the Chase mobile app even with root cloak and other methods still detects that your phone is rooted and after multiple attempts to make it work this was the only one that was successful
https://play.google.com/store/apps/details?id=com.oasisfeng.island
I'm not a developer not getting anything for promoting this app it just works and it's free and enabled me to get my banking app on my rooted device
I used to use this app until it wasn't working with the latest revision of Android but it works perfectly fine again and my previous use was to have two game accounts on the same phone running at the same time that I now use another app called multiple accounts that lets me run as many instances of the same app as I want but does not isolate it from your phone

kamisan said:
Oasis feng has an early release of his app island
It isolates the banking app from your phone enough that the app does not detect that your phone is rooted the new version of the Chase mobile app even with root cloak and other methods still detects that your phone is rooted and after multiple attempts to make it work this was the only one that was successful
https://play.google.com/store/apps/details?id=com.oasisfeng.island
I'm not a developer not getting anything for promoting this app it just works and it's free and enabled me to get my banking app on my rooted device
I used to use this app until it wasn't working with the latest revision of Android but it works perfectly fine again and my previous use was to have two game accounts on the same phone running at the same time that I now use another app called multiple accounts that lets me run as many instances of the same app as I want but does not isolate it from your phone
Click to expand...
Click to collapse
Chase works fine for me rooted. Maybe not if you're using something like Xposed though.

jsgraphicart said:
Chase works fine for me rooted. Maybe not if you're using something like Xposed though.
Click to expand...
Click to collapse
Works fine for me rooted and edexposed using core patch module for exposed to hide root

jsgraphicart said:
Chase works fine for me rooted. Maybe not if you're using something like Xposed though.
Click to expand...
Click to collapse
Are you doing any kind of hiding for root? I am about to unlock BL and root but I cant if chase isnt going to work.

14christ said:
Are you doing any kind of hiding for root? I am about to unlock BL and root but I cant if chase isnt going to work.
Click to expand...
Click to collapse
Magisk pretty much does all the work. I have it selected for Magisk Hide but I don't know if I did that or Magisk did. Also, I beleive Magisk will hide the unlocked bootloader automatically. Not 100% sure but basically, it's all done through Magisk. And Chase works normally.

Yeah its amazing how far Magisk has come since the last time I used it on a Huawei back in Magisk 12 days. Its so seamless and easy now to install modules and they just, work! its a real pleasure being rooted now especially on the OnePlus.

To everyone saying Chase is working normally just with Magisk hide: have you tried scanning/depositing checks? Mine works fine but detects root when I try to deposit.

Legion303 said:
To everyone saying Chase is working normally just with Magisk hide: have you tried scanning/depositing checks? Mine works fine but detects root when I try to deposit.
Click to expand...
Click to collapse
Same here.

I think Chase Bank should mind their own business.

I can use and get into Chase but I cannot get biometrics login to work. I'm passing SafetyNet and using DenyList on Chase. Chase is somehow still detecting root.

Cares said:
I can use and get into Chase but I cannot get biometrics login to work. I'm passing SafetyNet and using DenyList on Chase. Chase is somehow still detecting root.
Click to expand...
Click to collapse
Same here. All my other banking and credit card apps work with fingerprint. Not Chase. Have tried uninstalling, removing saved data, and reinstalling to no avail. And yes it is in magisk hide. Really frustrating. I hate companies trying to tell me how secure I should be.

thejase said:
Same here. All my other banking and credit card apps work with fingerprint. Not Chase. Have tried uninstalling, removing saved data, and reinstalling to no avail. And yes it is in magisk hide. Really frustrating. I hate companies trying to tell me how secure I should be.
Click to expand...
Click to collapse
The latest update broke biometrics. For now, use v4.271.

thejase said:
Same here. All my other banking and credit card apps work with fingerprint. Not Chase. Have tried uninstalling, removing saved data, and reinstalling to no avail. And yes it is in magisk hide. Really frustrating. I hate companies trying to tell me how secure I should be.
Click to expand...
Click to collapse
I ran across the solution. Try using magisk module Shamiko. Works great so far!
Shamiko v0.4.4

This worked for me. Thanks @Chance Ill ! Only after i upgraded magisk did it work. Had to turn on zygisk in magisk settings and turn on enforce deny list. Then configure deny list and add app to it. Worked. Not sure if it was shamiko that did it or the other settings within magisk. I'm just happy to have it working and hope this info helps someone.

It's definitely the module. All of the above was already enabled on my device prior to using shamiko. Only then was root not detected. Either way, glad I could help!

Thanks. Shamigo worked for me.

I had no problems getting the basic app functionality to work while rooted on my OnePlus 8, but it would NOT allow biometric sign-in. I assumed that it was detecting the unlocked bootloader, because YASNAC gave me the all clear

Safety Net starts passing on rooted phone

I don't know what happen but SafetyNet starts passing. I have rooted Moto Z3 Play, unlocked bootloader, Magisk 20.4, EdXposed 91.0 (YAHFA v0.4.6.4, updated today), a few Magisk, and EdXposed modules. Before hardware SafetyNet checks I could pay by phone. After Google forcing SafetyNet hardware attestation I could not. I accepted it because I was more concerned with control than with the possibility of paying by phone in the store.
Today morning I updated Riru - EdXposed (YAHFA) module in Magisk Manager. Then reboot. During the day I rebooted the phone once again. In the evening I ran Google Play Store to update my apps. I was surprised that Play was updating Netflix. Normally I updated it manually by downloading the apk file. Then I was testing Safety Net with Magisk, SafetyNet attest and SafetyNet test - all green. I was able to add a card to GPay. Even "attest" records in dg.db has 0, without blocking write mode. Here some screenshots.

The new update of EdXposed in the Magisk Manager passes SN, nothing new.

But John Wu (Magisk developer) said there was no way for hardware attestation on unlocked devices. Any software hiding will not work. That what he said.

QkiZMR said:
I don't know what happen but SafetyNet starts passing. I have rooted Moto Z3 Play, unlocked bootloader, Magisk 20.4, EdXposed 91.0 (YAHFA v0.4.6.4, updated today), a few Magisk, and EdXposed modules. Before hardware SafetyNet checks I could pay by phone. After Google forcing SafetyNet hardware attestation I could not. I accepted it because I was more concerned with control than with the possibility of paying by phone in the store.
Today morning I updated Riru - EdXposed (YAHFA) module in Magisk Manager. Then reboot. During the day I rebooted the phone once again. In the evening I ran Google Play Store to update my apps. I was surprised that Play was updating Netflix. Normally I updated it manually by downloading the apk file. Then I was testing Safety Net with Magisk, SafetyNet attest and SafetyNet test - all green. I was able to add a card to GPay. Even "attest" records in dg.db has 0, without blocking write mode. Here some screenshots.
Click to expand...
Click to collapse
Will gpay work, can you pay in shops?
Sent from my BASIC using Tapatalk

I added card successfully to gpay. I suppose that it will be working but I need to check. I wasn't in shop yet ?
I think that is working because evaluation type is basic.

QkiZMR said:
I added card successfully to gpay. I suppose that it will be working but I need to check. I wasn't in shop yet [emoji846]
I think that is working because evaluation type is basic.
Click to expand...
Click to collapse
When you're in the gpay app and you turn on nfc, does it say-hold to reader?
Sent from my BASIC using Tapatalk

Al765436 said:
When you're in the gpay app and you turn on nfc, does it say-hold to reader?
Click to expand...
Click to collapse
Text in Polish, but it means "move closer to the reader".

QkiZMR said:
Text in Polish, but it means "move closer to the reader".
Click to expand...
Click to collapse
Yes that means it should be working, thx
Sent from my BASIC using Tapatalk

Al765436 said:
Yes that means it should be working, thx
Click to expand...
Click to collapse
I confirm payments works fine.

QkiZMR said:
I don't know what happen but SafetyNet starts passing.
Click to expand...
Click to collapse
I second you mate ( see it here ) :good:
Hardware attestation hack to basic attestation is needed, I gotta say.

serajr said:
I second you mate ( see it here ) :good:
Hardware attestation hack to basic attestation is needed, I gotta say.
Click to expand...
Click to collapse
I know. I said it in my third post. The best thing is that I not needed to clear any google play/google services data. It just began working ?

Question Banking apps on rooted Pixel 6/Pro?

Hello everyone,
I haven't unlocked my P6P's bootloader or rooted yet, but have read that banking apps won't work after rooting/unlocking the bootloader.
Does anybody use Monzo and can confirm the app doesn't work? Also, do you think they'll find a solution to this issue any soon?
Thanks a lot!

Monzo won't work if device is rooted. Magisk used to have the Hide feature but I'm not sure if it's still working as I no longer root.
Many apps like banks or GPay also won't work if SafetyNet is tripped, again something MagiskHide used to be able to mask.

Yes all working here gpay, Banking apps and so on. Just use the guide for rooted and safety net pass here on xda. And additional do one thing:
Install Airfrozen app from Playstore,
Freeze magisk app in Airfrozen that's it all will work, if you need root just unfreeze it again use your root stuff and freeze again

All banking apps working for me...rooted.. without safetynet fix...

This is not Pixel 2 forum lol

Nekromantik said:
This is not Pixel 2 forum lol
Click to expand...
Click to collapse
I mean if you read the contents of the post you'd know he was talking about the pixel 6 pro lol

Nekromantik said:
This is not Pixel 2 forum lol
Click to expand...
Click to collapse
Thanks for heads up! Just fixed the title
And thanks everyone else for your replies! Good to know it's still possible to use banking apps, though with some tweaks.

This guide has all you need: https://forum.xda-developers.com/t/working-safetynet-with-pixel-6-pro-android-12.4354149/
Basically as long as you hide the Magisk app, and use the USNF module (latest Zygisk version is available for free now), you should be golden with most banking apps - just add them to the exception list.

anyone able to get fingerprint working with the Chase and Amex apps? both of these were fine, but now they won't let me unlock with fingerprint. running the latest Canary with 2.2 USNF

dimm0k said:
anyone able to get fingerprint working with the Chase and Amex apps? both of these were fine, but now they won't let me unlock with fingerprint. running the latest Canary with 2.2 USNF
Click to expand...
Click to collapse
I got chase working fine. I made sure chase was in deny list then cleared chase data/cache. Reboot. I uninstalled magisk app then was able to get fp to work. Even works after I installed Magisk app again.

eg1122 said:
I got chase working fine. I made sure chase was in deny list then cleared chase data/cache. Reboot. I uninstalled magisk app then was able to get fp to work. Even works after I installed Magisk app again.
Click to expand...
Click to collapse
when you added the Chase app to the deny list, did you select both entries under it or just the default one?

dimm0k said:
when you added the Chase app to the deny list, did you select both entries under it or just the default one?
Click to expand...
Click to collapse
Both

I didn't have to deny a single thing for GPay or Chase.
Install Magisk alpha. Enable zygisk. Install newest zygisk-based Universal SafetyNet Fix. Confirm that YASNAC shows you passing. Done.
There's no need to do exotic stuff but it's best to do this before ever trying your apps to avoid having to clear their storage.

Monzo does work on a rooted device. Starling doe not.

Question Gpay stuck on the loading screen [Lineage 18.1] [MicroG]

Hi, I'm trying to run Google Pay on my OnePlus with Lineage 18.1 + MicroG. I passed the SafetyNet, but Gpay still doesn't work. I added my Google account in the MicroG settings and hid root from Gpay in the Magisk's DenyList

My banking app also gives me issues. Can't use NFC payment because it detects root. It was the same on my previous Realme X2 Pro and I wask never able to solve it. Magisk hide, then later denylist; safetynet passes, but nothing. If someone finds a solution that would be great.
I'm on OOS 11 though.

Arcide said:
My banking app also gives me issues. Can't use NFC payment because it detects root. It was the same on my previous Realme X2 Pro and I wask never able to solve it. Magisk hide, then later denylist; safetynet passes, but nothing. If someone finds a solution that would be great.
I'm on OOS 11 though.
Click to expand...
Click to collapse
Denylist works great for me, all bank apps didn't detect anything. Are you sure that you selected all activities corresponding to your bank app and enabled enforcement?

happyrage said:
Denylist works great for me, all bank apps didn't detect anything. Are you sure that you selected all activities corresponding to your bank app and enabled enforcement?
Click to expand...
Click to collapse
No sadly it doesn't work, and there's only one process that is shown. This app is a real f***ing piece of work.

I managed to get my Gpay up and running on Lineage. I can't exactly open the app, but I can access GPay to add a card via Settings. Youtube video to explain below.

How To Guide Rooted S22: How to make the new Google Wallet work

If you rooted using the method on this forum, and your Google Pay app was recently upgraded to Google Wallet, you will probably find that it doesn't work anymore. Even if you have the Universal SafetyNet Fix installed and SafetyNet shows as passing, the new payment app will still detect your device as rooted. This is because it now uses Google Play Integrity instead of SafetyNet.
There's a lot of discussion in this thread. But the short version is, if you want to get payments working again:
1. Install MagiskHide Props Config.
2. Follow the instructions on that page to change your device fingerprint to Samsung Galaxy S21 (A11).
That's it! Some people in the thread also cleared data for Google Play Services but I don't think I did. Also in that thread is a verification app (first version, official version) for Google Play Integrity that you can use to make sure your device fingerprint setting is correct.
So far I haven't noticed any side effects from changing the fingerprint. I was unable to receive any SMS messages after first changing, but I rebooted a second time and that issue went away.

Just install safetynet-fix-v2.3.1-MOD.zip in Magisk. That worked on my OnePlus Nord CE (EU).

Vattu said:
Just install safetynet-fix-v2.3.1-MOD.zip in Magisk. That worked on my OnePlus Nord CE (EU).
Click to expand...
Click to collapse
Yeah this thread is now out of date. The updated safetynet fix is a much better option now.

You don't need just the safetynet module. You need Shamiko along that.
So latest Safetynet + Shamiko 0.5.2 (the latest version right now) and you're all set. You gotta whitelist the banking apps you use and they'll work perfectly fine. These 2 were enough to allow my preferred ridiculous banking app to work without an issue, without any other modules or tweaking and such.

dragos281993 said:
You don't need just the safetynet module. You need Shamiko along that.
Click to expand...
Click to collapse
You only need Shamiko if you use LSposed, right? I don't use LSposed and it's been enough for me to put all of my annoying apps on the Magisk denylist.

aurny said:
You only need Shamiko if you use LSposed, right? I don't use LSposed and it's been enough for me to put all of my annoying apps on the Magisk denylist.
Click to expand...
Click to collapse
No. I only had Magisk installed with Zygisk turned on. I first installed Safetynet Fix then Shamiko. The first module wasn't enough for my preffered banking app to not detect that the bootloader was unlocked. Shamiko fixed that. I simply installed it as a module in Magisk

Thanks, good to know. I haven't had that issue yet but I'll remember this in case I need it in the future!

aurny said:
If you rooted using the method on this forum, and your Google Pay app was recently upgraded to Google Wallet, you will probably find that it doesn't work anymore. Even if you have the Universal SafetyNet Fix installed and SafetyNet shows as passing, the new payment app will still detect your device as rooted. This is because it now uses Google Play Integrity instead of SafetyNet.
There's a lot of discussion in this thread. But the short version is, if you want to get payments working again:
1. Install MagiskHide Props Config.
2. Follow the instructions on that page to change your device fingerprint to Samsung Galaxy S21 (A11).
That's it! Some people in the thread also cleared data for Google Play Services but I don't think I did. Also in that thread is a verification app (first version, official version) for Google Play Integrity that you can use to make sure your device fingerprint setting is correct.
So far I haven't noticed any side effects from changing the fingerprint. I was unable to receive any SMS messages after first changing, but I rebooted a second time and that issue went away.
Click to expand...
Click to collapse
Thank you very much, it worked perfectly.

This actually worked, thank you!