yashsingh1/xdaforums huggingface dataset:
[Magisk] shaneaus:
Chase app detects boot and won't allow for a deposit of a check using the app.
[Magisk] ihavenolifee:
Same with me. With the updated app, it doesn't allow me to use quickactions or add new zelle reciepts or use chasepay points.

detects boot as in root?
[Magisk] blackice000:
Same here. No chase quickdeposits (the ONLY thing I use the app for!)

Rick
[Magisk] ihavenolifee:
I'm surprised noone has an idea how to resolve this. I wonder what files it looks for, since magisk hide and hiding the app still doesn't fix it
[Magisk] virajmalia:
I use chase app and all features like quickpay with magisk root.

You must enable Magisk Hide from Magisk app settings. Restart thr app and check the Magisk Hide option in the left side panel. Search for the Chase app and select that app.

Wipe all data for chase app and restart chase app. Login again.

Let me know if that works for you guys.
[Magisk] ihavenolifee:
This has been tried multiple times by multiple people.

It does not work for any of us.

What version app are you on?

Are you able to add new people to send on Zelle Quickpay?

Are you able to use reward points from a credit card?
[Magisk] danielg4:
Interesting: This only started happening TODAY for me. It was working fine yesterday. However, the app hasn't had any updates since Aug 25! The only thing that's conceivably different is the latest weekly update to LineageOS…

EDIT: Reverted to the previous build, and that is not the issue.
[Magisk] ihavenolifee:
That is very strange. Besides reverting to the previous build, have you tried anything else?
[Magisk] danielg4:
Yes, I first tried force-stopping the app, then clearing its cache and data, then hiding Magisk Manager, then starting the app again. Didn't work, and Lookout still finds the Manager, despite also having the checkmark in Magisk Hide. I do notice, though, that any time the app is first started, it takes a bit of time for it to detect root, during which time, you have full use of the app.
[Magisk] ihavenolifee:
hmm I did not notice that last part. When you say the app is "first started" do you mean after a data wipe/fresh install, or do you mean each time after the app is closed?
[Magisk] danielg4:
The app stays running after you close it, and will detect root right away when you open it again. If you either force-stop it or reboot, opening it again restarts the root detection, however long it takes.
[Magisk] ihavenolifee:
This is not the case for me, after a force-stop, it instantly detects root upon login
[Magisk] blackice000:
Same problem for me.

Rick
[Magisk] Abolfazl:
I have the same problem. Reinstalling app did nothing.
[Magisk] virajmalia:
v4.145

Yes, I can add new people on Zelle Quickpay.

I do not have a credit card with them, so can't say.
[Magisk] ihavenolifee:
Hmm. What rom/android version are you on?

I'd love to figure out how you manage to do it.
[Magisk] dewhite04:
I'm having the same issues. Specifically, I can login to my account through the app, but get the message about being "rooted" when I try to deposit a check.

I only root so that I can have call recording back after Google restricted other methods for app developers to provide it...
[Magisk] blackice000:
Yes.. Depositing checks would be nice. i can also still login and view various screens on my accounts, but no deposits. Pretty much the ONLY reason I have the Chase App installed in the first place.

Rick
[Magisk] ihavenolifee:
I havent tried to deposit a check, but even things like the new Quickbar doesn't work for me now. Kind of absurd
[Magisk] chrisross:
It's strange that it allows you to log in at all. On my Santander UK app I get 'root detected' as soon as I enter my user number.

It was working before a June update. I'm now unrooted and it still claims to detect root. I've narrowed it down to the unlocked bootloader. I haven't yet tried locking it, but it's the only thing left to try (RootBeer Sample says everything is OK).
[Magisk] arby80:
Interesting if I use the quicktoolbar now it pops up with a rooted message. But if I deposit using the drawer button it works fine.
[Magisk] danielg4:
This morning, there was an update to the Magisk Manager app, and now the issue appears to be fixed altogether!

However, the Chase app was updated yesterday, and I did not try it after that until today, and before I did, I also added Google Play Services to Magisk Hide.
[Magisk] ihavenolifee:
Seems like I still have the issue after the update. Lucky for you though. I wonder what is causing it.

are you on 21 or 20 for magisk?
[Magisk] ava1ar:
What message about root are you guys are getting? I am not seeing any clear-text message about it. This is what I am observing:

1. If I try to login, it says "We're temporarily unable to connect to Chase..." after I provide credentials and enter one-time code for login

2. If I try to click on "Sign up", only then I see something about rooting - message is "For your security, this feature is unavailable on devices that have been "rooted" or contain malware. Read our Security FAQ to use this feature."

I am on LOS 17.1 without Google services (I have microG installed) and with Magisk 21/Manager 8 and my system is not passing SafetyNet check. Is there a chance Chase on-boarded SafetyNet check into their app?

Interesting thing is that Chase is the only banking/financial app I have issues with - other 10 apps from different banks or payment services are working just fine. Not a big loss for me, but still curios is it possible to make it work?
[Magisk] ihavenolifee:
I am able to login but some features give me the same message as when you click to sign up.
[Magisk] ava1ar:
Do you have Google Play services installed? Does your phone passing SafetyNet checks?
[Magisk] ihavenolifee:
Yes and yes
[Magisk] danielg4:
20.4
[Magisk] Spartacus500:
Please link to Chase app for Google Play store
[Magisk] danielg4:
Here you go!
[Magisk] Spartacus500:
This application is well secured to sign up, it checks all applications installed on the phone, even those in the system and checks them in the Google Play store if they are safe, it says in the log that root has been detected and much more
[Magisk] danielg4:
But I don't have storage permissions granted to this app…
[Magisk] Spartacus500:
I understand, it works for me, as you can see, unfortunately I don't see a solution for the sign up button, even if you delete all files with the ending "... lookup, all files come back after starting the application and in the log it immediately says that root has been detected, , developer options enabled, usb debuging enabled etc...

---------- Post added at 10:33 PM ---------- Previous post was at 10:16 PM ----------

When the root information pops up:

Log Cat :

10-06 20:55:34.510 D/ViewRootImpl@386d972[LoginActivity](26565): stopped(true) old=false

10-06 20:55:34.510 D/ViewRootImpl@78d1556[LoginActivity](26565): stopped(true) old=false
[Magisk] HippoMan:
I wonder if there is a way to set up a chroot jail under Android. If so, then an entire pristine and safe looking OS could be installed in that jail, and anything else on the device would not be visible to any programs (including apps) that are running in that jail. If such a thing could be done, then apps like Chase could be set up to run inside of that jail.

This is similar to what the "Island" app tried to do, but chroot works at a lower level within the OS.

I tried a while ago to set up such a chroot jail on my Android device, but it didn't readily work, and I didn't have time for further investigation. Maybe now is a good time for me to resurrect that investigation.

.​
[Magisk] Spartacus500:
Hello, I recorded a log after pressing sign up, I found such an entry, I do not know what it means :confused:

10-08 18:42:40.629 E/LoadedApk(19861): java.lang.ClassNotFoundException: Didn't find class "androidx.core.app.CoreComponentFactory" on path: DexPathList[[zip file "/system/framework/android.test.mock.jar", zip file "/system/framework/android.test.runner.jar", zip file "/system/framework/org.apache.http.legacy.boot.jar", zip file "/data/app/com.chase.sig.android-VoBlPfdHYn4kxenIQFd3bQ==/base.apk"],nativeLibraryDirectories=[/data/app/com.chase.sig.android-VoBlPfdHYn4kxenIQFd3bQ==/lib/arm64, /data/app/com.chase.sig.android-VoBlPfdHYn4kxenIQFd3bQ==/base.apk!/lib/arm64-v8a, /system/lib64, /system/vendor/lib64]]
[Magisk] ihavenolifee:
Thank you so much for looking into it. Noone has really done so since.

This is extremely secure but it is a banking app so it is understandable.

Do you know which specific apps it could be checking in the GooglePlay store? I did not allow any of these permissions on the app too, which is surprisinglu.
[Magisk] Spartacus500:
If we kill the application, run it, then if we quickly click on the sign up or forgot the password, the menu opens, but if I try to register, whether I have internet enabled or not, it still fails, and the log of this reason:

[com.chase.sig.android/com.chase.sig.android.activity.SplashActivity[8121]#0] disconnect: not connected (req=1)
[Magisk] HippoMan:
Until (or unless) we figure out how to get past Chase's root detection, I have decided to utilize the following workaround:

* Install one of the many web browsers that are available for Android.

* Set the home page for this browser to be https://secure.chase.com/web/auth/dashboard .

Then, I just log into Chase via that browser. It takes one more step to log in, but then I have access to all capabilities from my Android device.

UPDATE: And I changed the icon and app name of that browser app to be the same icon and name which are used for the Chase app, so it even looks like I'm connecting via the Chase app when I select that browser.

FURTHER UPDATE: I also had to set the User-Agent string of that web browser to be the same as the one which is used by my standard desktop web browser. Many Android browsers allow the user to set a custom User-Agent string in this way.

<OPINIONATED-RANT>

The fact that root-checking security is so easily bypassed in this manner illustrates how stupid it is for Chase and other banking app developers to put root checking into their apps.

Normal web apps don't perform such root checking, and Chase and other financial institutions are perfectly happy to make their sites available to their customers via the web.

Furthermore, any of us who use desktop or laptop computers are utilitizing rooted machines. On these machines, there is a "root" user (or in the case of Windows machines, an "Administrator" user) that anyone can log in as, if they have the password. Furthermore, linux and MacOS machines have the sudo utility which can be easily utilized for running any desired applications as root. I believe there is a similar facility under Windows.

And yet, few, if any of the software packages that are offered for linux, MacOS, or Windows machines will be restricted or fail to work, just because there happens to be an accessible "root" or "Adminstrator" user or sudo-like executable on the machine.

Keep in mind that I carry my laptop with me to public places, and it could just as easily be stolen and hacked as my mobile device. I use anti-virus and other protective measures on my laptop.

Instead of making mobile-device users' lives more painfully complicated by restricting apps' capabilities for rooted mobile devices, banks and other app providers could simply take the same position with mobile apps as they do with applications that run on laptops and desktop machines: to force the users to accept responsibility for any hacking or security breaches which take place.

I would be glad to sign some sort of agreement with Chase in which I promise to absolve them of any responsibility for damages which can be proven to have occurred due to my device having been rooted.

Of course, I don't expect anything like this to actually come into being in today's world.

</OPINIONATED-RANT>

.​
[Magisk] Spartacus500:
From the info after clicking sign up and seeing info about root or installed malware, I think Magisk root is properly hiding root for Chase Bank, but the biggest problem is the scanning mechanism for all user and some system apps, it works like this when When the Chase application is started, the data of the scanned applications are collected very quickly and the evaluation is made, there are three: LOW, MEDIUM and HIGH, i.e. if a given application is detected as HIGH, Chase detects root. I tried to change in all applications from HIGH to LOW, but it does not change anything, Chase checks the applications again after each start and changes from LOW to HIGH ... In the file the login preferences is set to false, and even if I change to true, it is enough run Chase and the file is overwritten with false ...

���sr�o.fmn��ԩ4�V�� J�íI�ñI�óZ�úL�At�6Lcom/zimperium/zdetection/api/v1/apprisk/AppRiskLevel;L�Át�Ljava/lang/String;L�Ét�Ljava/util/List;L�Íq�~�L�Óq�~�L�Üq�~�L�áq�~�L�üq�~�xp��u	���������`~r�4com.zimperium.zdetection.api.v1.apprisk.AppRiskLevel����������xr�java.lang.Enum����������xpt�LOWt�Jhttps://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackupsr�java.util.ArrayListx����a��I�sizexp���w���sr�java.lang.Integer⠤���8�I�valuexr�java.lang.Number��� �����xp���+sq�~� ���xsq�~�

����w����xt�}http://files.softicons.com/download...rabhuswamy/png/80x80/Developer.pngt�Titanium Backupt�com.keramidas.TitaniumBackup~q�~�t�HIGH
[Magisk] HippoMan:
Hmm ... I wonder if there is a way to do the following:

Write a wrapper app which invokes the Chase app. That wrapper app could do this:

* temporarily change the DNS entry for play.google.com to a different site which runs a different "apps/details" procedure that doesn't return the info which triggers the "HIGH" setting for any app that is being queried.

* invoke the Chase app

* after the Chase app exits, restore the normal DNS

UPDATE: Also, I wonder if there is a way to patch the Chase app with a fake "com.zimperium.zdetection" package.

FURTHER UPDATE: This check also looks for the app's icon at the files.softicons.com site. The DNS site spoofing suggested above could also override that site.

.​
[Magisk] ava1ar:
Thanks for all the discovery you did - very helpful. From the message above I am making conclusion that all this advanced checks are not done by Chase themselves, they are using following solution for that: https://www.zimperium.com/zdefend. And there are probably other apps which use same framework for "risk" detection...
[Magisk] TraderJack:
It takes about 10 seconds for zimperium to run it's root detection. If you force close the app and then launch it again you have about 10 seconds from launch to login and execute any of the menus.

If you setup the little quick action tiles in the app for what you need, you can launch them. I tried this with Deposit Checks and Ultimate rewards and was able to do both.

It seems that Deposit Checks will also always work if you access it from the left hand menu instead of the quick tiles.

EDIT: Also, if you setup fingerprint auth for the app you can log in quicker to launch the action.
[Magisk] Spartacus500:
1. Developer Mode

2. USB Debugging Mode

3. Device Encryption

4. Screen Lock

5. App Risk installed

6. Device Rooting

I fix this :

1. Developer Mode

2. USB Debugging Mode

3. Screen Lock

4. Device Encryption

5. App Risk installed

6. Device Rooting

Device Encryption & App Risk installed, this problem "Device Rooting"
[Magisk] ava1ar:
Do you have a list of apps, which are checked by app?
[Magisk] HippoMan:
Given that "Deposit checks" works from the left-hand menu -- as well as "Find ATM & branch" and "See bill activities" -- it seems like using the normal Chase app along side of the modified-web-app workaround that I described above (

https://xdaforums.com/showpost.php?p=83667431&postcount=59 ) will provide all of the online Chase functionality that is needed.

As far as I know, any functions that might be still be blocked in the original app will be available via the web-based access. Of course, I agree that it would be ideal if we could use the original app for everything, but given that web access to Chase provides a user experience which is very similar to that of the app, this seems to be a small price to pay.

.​
[Magisk] Spartacus500:
These applications. The strangest thing is that it even detects some system applications as dangerous :eek:
[Magisk] Spartacus500:
Does anyone with Magisk root and an unlocked OEM bootloader have device encryption enabled ?
[Magisk] ava1ar:
I thought encryption is on by default. How to check? Does this mean encryption is on?
[Magisk] Spartacus500:
Yes, you have device encryption turned on. What Android version and do you have TWRP with Magisk root :confused:
[Magisk] ava1ar:
This is Moto G7, LOS 17.1 with MicroG and Magisk. No TWRP is flashed.
[Magisk] dewhite04:
FYI - I recently was notified of an update to the Magisk App, which I installed. I didn't expect this would resolve any issues, but for good fun I uninstalled the Chase App, Reinstalled, Rechecked the Magisk Hide options for both Chase Apps on my phone, and ran the App again. After authenticating and logging in, Presto! I am now able to deposit checks again.

I have no illusions that I solved any problems or figured anything out, but it works again for me and I'm not going to jack with it again unless I have to...
[Magisk] HippoMan:
You are lucky!

Which phone are you using, which OS is it running, and which version of Magisk and Magisk Manager did you install?

.​
[Magisk] Spartacus500:
I managed to eliminate all security except one, device encryption, chase me on Samsung S7 9.0 Pie NFE Custom Rom only detects that the device is not encrypted, unfortunately I'm afraid to encrypt the device having TWRP, unlocked OEM Bootloader and Root Magisk, and I am very I wonder if after encryption the chase would not detect root and dangerous applications ?
[Magisk] dewhite04:
I'd rather be lucky than good.

Pixel 3XL Factory Unlocked. Running Android 10 with the April 5, 2020 security patch level and September 1, 2020 Google Play system update (Build No. QQ2A.200405.005).

Magisk 20.4 (20400) with Manager App version 8.0.2 (307)(11). Magisk Hide enabled and com.chase.sig.android & com.chase.sig.android:remote both checked.

Good luck all! I'll be back if things go sideways again.
[Magisk] Spartacus500:
1. Developer Mode

2. USB Debugging Mode

3. Screen Lock

4. Device Encryption

5. Device Rooting :(

I managed to eliminate all security, but Chase still detects root ... Applications left ... I did a test disabling the internet for Chase, effect? None, it scans all installed applications at startup, including system applications, and immediately after clicking "sign up" or "forgotten password?", Informs that root or illegal applications have been detected ... Everything would be fine if Chase didn't say that my system applications such as calendar, telephone (modified phone), system tracking etc. detect as unsafe which is absurd. When you turn on the internet, a special "dangerous app" mode starts and applications are then checked through a special zimperium tunnel ... Also, there is no solution on Chase, like pure stock Rom with Magisk root, but without any external applications downloaded from the Google Play store or any applications modified on the system. Apps like Spotify, Samsung Browser, Opera web, all dangerous ... Hands drop :(
[Magisk] HippoMan:
I am impressed and massively grateful for all of the difficult, complicated, and frustrating work you have been putting into this. Thank you!

And I'm very sad about the absurdity of Chase's attempts at "security" ... as well as being sad about the stupidity (which I ranted about above) of their going to such lengths to "secure" an app on a mobile device app while gladly allowing full access to the Chase web site via the same rooted mobile device's browser ... and via browsers on desktop machines which are all similarly "rooted".

And we trust our money to financial institutions who use such poor judgment about security.

.​
[Magisk] FOREST37:
Very impressive - thank you for trying to defeat the Chase security root detection routines - which the SANTANDER UK banking app appears to be duplicatiing too. Let's hope the other banking apps don't decide to go down the same overzealous checking otherwise I'll be having to have a non-rooted, non-unlocked bootloader etc........
[Magisk] TheKnux:
Chase app works fine for me. Latest Magisk Canary, MagiskHide enabled, Bootloader unlocked, Chase app IS NOT hidden using MagiskHide.
[Magisk] ihavenolifee:
Hmm, they are marking apps like Spotify as dangerous? Thank you for taking such thorough look at this.

---------- Post added at 11:30 PM ---------- Previous post was at 11:25 PM ----------

working fine as in all the features we mentioned as well?
[Magisk] Spartacus500:
I've removed Magisk root and Chase is working fine, "sign up" and "forgot password" are unlocked. After uploading root, Magisk without magisk manager Chase detects root.
[Magisk] ihavenolifee:
Surprising how well their security is that none of us can figure out or pinpoint exactly how they detect it. MagiskHide has worked for almost every other application I use too.
[Magisk] ZMaissi:
And It used to work!! but somehow since today, it let me deposit ONE check, but with the second, it started "finding"my root on my LG V30+ running stock Pie. I tried uninstalling, clearing data, hiding and unhiding rebooting in between, using Island to no avail. Just to let you know, it let me login, send money via Zelle, Pay with Google Pay but if I try to Add a new person to use Zelle OR try to deposit a check, It finds root...
[Magisk] pr0adam:
Stuff like this is probably going to make me switch to iOS . If I cant do everything on my rooted device, cant theme in android 11(as of now) then I don't think I can stay. So stupid I cannot pay friends with Zelle that are new contacts because I want to root my own device
[Magisk] ZMaissi:
But then you will be getting into another world of pain if you have a newer device, AFIK jailbreaking is getting harder on every iOS iteration...
[Magisk] Fry-kun:
For reference: https://github.com/topjohnwu/Magisk/issues/2950
[Magisk] rnadomuc:
Chase no longer allows depositing checks from a rooted phone, so I've been wrestling with this.

My phone passes SafetyNet and I enabled MagiskHide for the Chase app, following the steps here, but to no avail. I ended up making a backup in my recovery and then uninstalling Magisk to deposit a check, then I restored the backup. What a pain in the ass. I hope someone figures out how they're detecting root now soon.
[Magisk] freechris74:
I have rooted pixel 2 on android 11 could not deposit a check. I read the forms long clicked chase app to uninstall and deposit check came up. Clicked deposit check and it worked. A small work around from uninstalling if this helps some
[Magisk] l7777:
This worked for me as well on a Pixel 2, Android 10, Chase version 4.160. Also worked on a Pixel 5, Android 11, and Chase version 4.171.

Force close

Long press icon and select Deposit Checks to launch
[Magisk] hackwerk:
Same with some Thai banking apps (like NEXT by Krung Thai Bank)!

Since updates the phone (Mi A3) doesnt pass CTS anymore.

I dont know if it is coincidence but also the banking app doesnt work anymore and shuts down with rooted message.

Seems all other apps with detection still dont detect when MagiskHide is on them.

Seems to be exact your problem: Zimperium!

Me too can choose a secure operation but within 2 seconds it shuts down with a message.

MagiskHide and also the Didgeridoohan MagiskHideProps module doesnt help in any setting.

If I check the logcat with MatLog I see exact those checks mentioned at the above Zimperium post.

How are we going to fix it?!
[Magisk] rnadomuc:
After applying Magisk 21.2 and MagiskHideProps, as well as enabling MagiskHide for the app, I'm now able to get deposit checks to Chase again.