yashsingh1/xdaforums huggingface dataset:
[Magisk] TraderJack:
Do you mind sharing what specifically you configured in HideProps?

I just clean wiped to 11 and am still having this issue.

I did some extensive testing on this on 10 using XPrivacyLua and I had mixed results with various hooks in getting it to run without blocking any features. However nothing I did seemed to allow it to consistently run without blocking certain features (Check deposit, Ultimate Rewards, etc).

There is a piece of software (name escapes my know...it may have been mentioned in this thread) that they license to help detect root. It clearly does a lot of scanning of the system for files, apks, etc and I'm not entirely sure what it is they are finding but I expect they aren't only scanning for magisk, root, etc but also any apk associated with being able to bypass any of that.

The good news is that it appears this piece of code runs on the startup of the app each time (from a force close). Additionally it seems to take several seconds (20-30) from the time the app is launched until the restrictions are enforced. This means if you can launch, login, and launch your option quick enough you can get to everything.

Several of the features can be access in other ways. As some have mentioned you can access mobile deposit as a quick task from the launcher. There is also the option in the app from the hamburger menu on the left. Other's don't seem to work from any link (like Ultimate Rewards) unless you launch them quick enough.

I've configured biometric login so usually I can launch the app and be logged in under 10 seconds, giving me plenty of time to launch what I need. I also have a quick force close task setup so that I can easily relaunch to restart the timer.
[Magisk] ahb83:
Thank you for your! I had to add a new contact and timed my taps and it worked!
[Magisk] BuzzW:
Actually, the app thinks EVERYONE is rooted! My wife and I just upgraded to new Samsung, non-rooted (yet) phones with Android 11. The app thinks we are both rooted (or contain some unspecified malware) and blocks some functionality. Some days it seems the hyper-vigilant security witch hunts will be the death of us.
[Magisk] whitedavidp:
Thanks for letting us know about being able to get by using the launcher's quick link to deposit checks! Could not get this done any way else.
[Magisk] Optiongeek:
After applying the Android 11 March security update to my 4a (5G), I can now use features on Chase had previously been alerting due to root. I am running Magisk Hide and have set the integrity check to "basic". Before applying the March update, I could use GPay just fine, but Chase would block on "Bill Pay" and other features complaining about root. I did nothing else than update to the new image and re-patch boot.img file but now Chase seems to let me pay a bill that was previously restricted. Anyone else seeing this?

Edit: OK - Chase must have just changed their app and now allow you to pay a bill using a rooted device. Other features are still off-limits due to root. Never mind.
[Magisk] acidreian:
I am also running a rooted OnePlus 8T and having troubles with rooted device issues on Chase app, I have tried all workarounds listed above. Nothing so far lets me add new billing recipients or go to chase rewards.

Magisk 22.0

Safety Net passes.

Island work work.

Hide prop hide app + hide magisk.

Also something strange I found.

My Telefony process is being listed on VD info as an Emulator and is detected by root.

Has anyone had any success?
[Magisk] mattcoz:
I'm also not rooted and it thinks I am, but my bootloader is unlocked.
[Magisk] Sp1CyPhone:
Worked for me.

Make sure the Chase app has never run before you hide it in MagiskHide.
[Magisk] whitedavidp:
Thankfully, I only use this app to deposit checks. I read somewhere that if you long press the app in the app drawer and choose the option there you can log in and do the deed even if rooted. In the few times I have needed to do this it has worked for me. Good thing I don't need to try and do more!
[Magisk] gfrank227:
Any luck with this app after the September 2021 update?
[Magisk] whitedavidp:
I am on Android 9, rooted with The August 11, 2021 build of this app. I typically do NOT update any app unless I have good reason to do so. In the case of the Chase app, that reason is only when they no longer permit me to use it. All I ever do with this app is deposit checks and I don't need to do that very often any more either. But I just tested the technique I wrote about above and this app still appears to accept sign-in and allows me to engage in the check deposit process without warnings or other issues. I have not updated and, again, will not try to do so until forced. So I cannot speak to your question.

Shameless Plug: to avoid being obviously nagged by Play Store to update those apps I do not really want to update (or even be reminded to update), I wrote an app that is on Play Store called Hide Updates in Play Store. It requires root and is not a perfect solution. But I and others have had good success in avoid such nuisance. Of course, I also turn off all automatic updating by Play Store.

Cheers
[Magisk] gfrank227:
My issue has been mostly with the fingerprints. I could not get the latest update to sign in with my fingerprint; it was obviously detecting root; so I downgraded to the prior version and now it works. there's obviously something that it's detecting; and magiskhide, hidemyapplist, and xprivacylua couldn't solve the issue, or at least I haven't figured out how to use them to solve the issue.
[Magisk] vaibhav palande:
@gfrank227 How did you downgrade to the prior version of the chase app?
[Magisk] VD171:
You can backup it using titaniumbackup, uninstall it, install the previous version and then restore backup using titaniumbackup.
[Magisk] vaibhav palande:
Where did you find the previous version of the app?
[Magisk] VD171:
Aptoide - The alternative Android app store

Find, discover and download the best apps and games for Android in the official Aptoide app store

aptoide.com

⚡ APKCombo - #1 APK Downloader

Download APK for Android Game, Android App - Latest Version, Old Versions, Android Tablet, Android Smart TV, Android Wear, armeabi-v7a, arm64-v8a, x86, x86_x64 - Free

apkcombo.com

APKMirror - Free APK Downloads - Free and safe Android APK downloads

Free and safe Android APK downloads

apkmirror.com

Download APK free online downloader | APKPure.com

Download apk for Android with APKPure APK downloader. NoAds, Faster apk downloads and apk file update speed. Best of all, it's free

apkpure.com
[Magisk] gfrank227:
I think from Aptoide but don't remember for sure. Here is the apk
[Magisk] VD171:
The file says "apkeureka.com"
[Magisk] Cares:
What is the latest version of the Chase app that works with root and biometrics? My latest Chase app won't allow me to face unlock anymore.
[Magisk] Cares:
Anyone know how to get Chase to not detect root or unlocked bootloader? I'm passing SafetyNet but somehow Chase still knows and won't let me use biometrics.

Magisk is renamed and hidden. Chase is on DenyList. Google Play Store and Play Protect as well.
[Magisk] gfrank227:
I Know. Don't know why. Use an older version of the app I uploaded above and don't update
[Magisk] String0011:
Confirmed that 4.234 posted by gfrank227 works perfectly on Magisk 23. Hope it could last for months before Chase starts to enforce update.
[Magisk] gfrank227:
I hope so too. After that, there is an option to use a program like Island. Chase won't detect root if installed through Island. But it's a pain in the neck.
[Magisk] TULOA:
Chase works fine for me on LineageOS 18.1 with Magisk Canary plus the universal safetynet fix module.

Strangely since I moved to the magisk alpha with a boot patched magisk version of b6298f86-alpha which is 23001 I can use Samsung Pay again also.

I have a Google Pixel 4a 5g.
[Magisk] String0011:
It forces me to update today. Sad.
[Magisk] gfrank227:
Does this include fingerprint sign-in?
[Magisk] gfrank227:
:-( I hope someone figures this out soon. I've tried everything i know. All the privacy settings on xprivacylua; all of the root apps hidden on hidemyapplist....nothing helps with that damn fingerprint sign-in. Perhaps when kdragon finally gets around to putting out the zygisk module on github for safetynet fix; but i'm not optimistic. Luckily it still works, so i guess it could be worse; but still, i'm a perfectionist...
[Magisk] eg1122:
I believe that what it's actually detecting is the Magisk app itself. I got sign in to work by hiding magisk app, rename it to something other than settings. And then make sure chase is in the deny list. After that wipe data/cache for Chase and reboot. After that open chase and sign in. Sign out and sign in again but this time press the biometrics option. It will prompt you to sign in via password and then it should allow you to enable biometrics.

After this, I was able to sign in multiple times into Chase via FP. I then restored the magisk app and am still able to use FP to sign in.

I'm using the latest Canary Magisk and the Safetynet fix v2.2 module
[Magisk] gfrank227:
This did not work with version 1.1 (which I downgraded to after I updated to new magisk canary.) After 2.2 hits github, I will try again and report back.
[Magisk] EthanG_1988:
I am also on the latest Canary Magisk (23013) and Safetynet fix v2.2.

I followed your instructions:

1. Make sure chase app is on denylist (I am on V4.255 of chase app)

2. Hide magisk app with different name ("settings" in my case)

3. I used island to freeze Magisk (now called "settings")

4. Wipe cache/data on chase app

5. Reboot

6. Sign into chase app

7. Sign out of chase app, and then sign back in, but hit biometric option

8. After inputting password, it immediately jumped to the FP screen, and gave the "it looks like this isn't working right now" error

There must be something different between our two setups.

EDIT: I missed the part where you said name Magisk something other than "settings"....testing now with different name

EDIT 2: Changing the Magisk app name to "value" didn't change anything...I also tried naming it "anypine" (Just being random)

I also tested enabling every single system and OS app under denylist (this was a pain to select them all). That didn't change anything. I also disabled every magisk module except for safetynet (just had substratum and systemless hosts).

I don't see a way around this unless there is a way to fully disable magisk and root temporarily.

Hopefully someone smarter than me can fix this or find a workaround.
[Magisk] gfrank227:
I wonder if BusyBox could be the culprit. ?
[Magisk] EthanG_1988:
I have made some progress on this, and can now use Chase biometrics in the latest Chase app (V4.255)

It did require downgrading from Magisk Canary with UNSF 2.2.0 to a fork of Magisk and UNSF v2.1.1 (I even had paid for the beta preview of the new UNSF, but I am happy to support the developer).

All the steps I took can be found in this post on Github where some people helped me.

Word of warning: I might have way more steps, and things installed than are actually needed, but I wanted to be as thorough as possible.

com.starfinanz.mobile.android.pushtan detects root with enabled Magisk Hide · Issue #1084 · topjohnwu/Magisk

The mentioned app (https://play.google.com/store/apps/details?id=com.starfinanz.mobile.android.pushtan) here is able to detect root on your device while Magisk Hide is enabled. It immediatly stop a...

github.com
[Magisk] gfrank227:
Fascinating regarding the fork of magisk. Problem is we really need to figure out a way to make it work with zygisk. Riru's days may be numbered.
[Magisk] EthanG_1988:
I 100% agree. I felt bad using a fork of Magisk, but this was one of those things that I couldn't give up on until I got it working.

If Riru worked with Zygisk, then LSPosed could maybe work, and this might all work on the latest canary build....but I failed to get it working today.
[Magisk] gfrank227:
Lsposed is working with magisk. It's that momo program that isn't.
[Magisk] EthanG_1988:
If someone on here wants to test that LSposed Zygisk preview build works with Magisk Canary, then that could save a lot of time. I spent about an hour trying to get it to work to no avail. Someone on GitHub was working on testing it a few hours ago.
[Magisk] gfrank227:
Yes it works. I am running gravitybox and hidemyapplist and xprivacylua. But it doesn't help with chase
[Magisk] EthanG_1988:
Sorry to hear that. Momo must be doing a decent job hiding Magisk. What does magisk detector say?
[Magisk] gfrank227:
Lsposed working. Momo won't install bc no riru
[Magisk] EthanG_1988:
Hopefully momo gets updated to support something other than Riru...momo confused me even when reading the git. Telegram is a crapshoot as well....most of the threads are loaded with untranslated Chinese.
[Magisk] gfrank227:
what is it supposed to do anyway?
[Magisk] EthanG_1988:
On the git, it says that MagiskHide works to hide a lot of things, but it still leaves some traces behind. I honestly don't understand exactly what Momo is doing, but I know when I created the four blank files that were named appropriately in the correct folder, Magisk Detector all of a sudden couldn't detect the Magisk Manager (this is the goal to making Chase work with biometrics).
[Magisk] EthanG_1988:
On the subject of gravitybox....I remember using that app years ago (I couldn't root my last phone that I had since 2017). Looking around, it looks like gravitybox only works up to android 11. Are you aware of a build that works with android 12?
[Magisk] gfrank227:
No. I am on 10 so I haven't researched. But 12 is new so perhaps give it time.
[Magisk] TULOA:
Yes it does. I am kind of wondering if my particular setup though is responsible for the Settings app crashing on me so I am investigating that but I can use fingerprint logon and even still I can use Samsung Pay.

Edit: It is confirmed to be my exact setup that causes Settings crashes. But I can get to the proper pages I need to do what I want without app info for now. I will play around with different magisk versions and see what allows both and report back here later.

Edit 2:

My setup:

Magisk App Version: 7717f0a6-lite

Magisk Boot Image: b6298f86-alpha

Modules:

App Systemizer (I cant get it to work for what I need so it might as well not be installed)

Busybox 1.33.1

Call Recorder - SKVALEX 2.1.0 (3.4.9)

Riru 26.1.2.r505.c20529bced

Riru-MomoHider 0.0.7

Smali Patcher 0.0.7.4

Tulsadiver NavBar Swap v1 (Switches my back and app switch buttons)

Universal SafetyNet Fix v1.2.0

I had MagiskHide on with chase and all its activities hidden.

Along with others from samsung pay and mcdonalds.

All this back when I was using the latest canary before they killed off MagiskHide.

Which once I get my new watch I will go back to because I am removing samsung pay.
[Magisk] gfrank227:
Here's a crazy idea. What if you deleted magisk manager entirely without uninstalling it from the boot.img. set up chase and then reinstall. ?
[Magisk] desertcat:
The Chase app is working for me and Busybox being a culprit in detecting root is a strong possibility. I uninstalled Busybox after I uninstalled Titanium Backup. To the best of my knowledge, Titanium Backup is the only app that requires Busybox.

Here is what I have:

Pixel 3a running Android 12

Magisk 23.0

Magisk modules:

Universal SafetyNet Fix (2.1.0)

Riru

Riru - Enhanced Mode for MagiskHide

When I installed the Chase app I did not open it until I hide the app using MagiskHide.
[Magisk] eg1122:
So earlier today I realized I didn't enable the account balance preview when I got fingerprint to work. I took the following steps and was able to enable it.

Pixel 6 Pro

Latest Magisk Canary

USNF 2.2.0

I made sure chase app was on deny list.

Reboot.

Uninstall Magisk app

Sign into Chase

Force close chase and wipe app cache

Sign back in and was able to toggle account balance preview.

Reinstall Magisk app

Everything still working.
[Magisk] gfrank227:
I still can't get biometrics to work no matter what I do.
[Magisk] KHANrad_SIN:
So I managed to get biometrics working but other things like accessing your rewards and adding new recipient to zelle still doesn't work and will show the "you are rooted" prompt.

EDIT: I MANAGED TO GET OTHER FEATURES LIKE REDEEMING REWARDS POINTS AND ADDING RECIPIENT IN ZELLE TEMPORARILY WORKING. PLEASE READ LAST PARAGRAPH AT END OF POST.

Pixel 6 Pro, Magisk Canary (23014), USNF 2.2.0

My steps to get biometrics working was:

1. make sure you hide magisk manager and name it something else besides "settings", I named mine "foo" for example.

2. Enable chase in DenyList, makes sure both options are checked underneath it. (Tap on an app in the DenyList to see the options for that app).

3. wipe cache and data for chase app

4. Reboot

5. Sign in to chase app and DO NOT tap the biometrics option, just sign in.

6. Now, Sign out of chase

7. Go back to the DenyList and uncheck the second option under chase that says "com.chase.sig.android:remote"

8. Go clear the cache (NOT DATA ONLY CACHE) for the chase app and then force stop the app.

9. Go back to chase app and sign in but this time tap the biometrics option and it will tell you to sign in using your password first. After that it should take you to the fingerprint option page and it should enable fingerprint sign in for you, if not then just tap the switch yourself.

Now of course YMMV so do this at your own risk.

EDIT: I've also discovered that after step 9 as described above, you will temporarily be able to access your rewards points and redeem them and you will also be able to add recipients in zelle. The catch is that once you sign out and sign back in you won't be able to redeem rewards points anymore or add recipients in zelle (fingerprint sign in will still stick though).

To remedy this as a temporary work around, anytime you need those features, just clear the cache for the chase app (ONLY CACHE NOT DATA) and then force close the app as well. Now go back and sign in and those features should work for that current login session. Once you log out though it won't work anymore. So any time you want to use those feature you have to clear cache and force close before signing in. Not ideal but at least it's something.

To remedy this simply close the app by going into multitasking and swiping the app away. Reopen chase and login, those features should be working now. Anytime you want to use those features just close/quit the app completely in multitasking and log back in.
[Magisk] Exel:
This unfortunately didn't work for me, no matter what I did with the latest chase app, it just wouldn't work.

I did however find a workaround that worked for me.

Big thanks to Bad Bimr for figuring out the data off / wifi off part.

Here's how to get the Chase app working:

1. Uninstall any previous chase app from your phone.

2. Download this Chase apk: https://apkeureka.com/apk/com.chase.sig.android/link/2/ (chase-mobile_v4.234_apkeureka.com.apk)

3. Use a file explorer or the one that comes stock with your phone to install the apk.

4. DO NOT open the Chase app.

5. Go to Magisk > DenyList and check everything on the Chase app.

5a. Not sure if this is required but I also spoofed my Magisk and named it "Matrix" (Settings > Hide Magisk app)

6. Turn off both your Wifi and Data so you have no internet connection.

7. Open the Chase app and enter your login username and password (make sure to click on the fingerprint sensor so it takes you straight to that setting to enable)

8. It will prompt you that you have no data when you click the sign in button.

9. You can now enable data and it will sign you in and take you to the fingerprint authentication page where you can enable it.

10. The next time you sign it, it will prompt you to update the app. Go ahead and do that. Your fingerprint will still work once you update.

11. PROFIT!
[Magisk] Lw00d:
yes this work for me on pixel 6 Pro
[Magisk] String0011:
Update: I realized that it refuses to work when I use HMA to blacklist it from play store (in order not to accidentally touch the update button). When I remove it from HMA, I could log in normally again.
[Magisk] eg1122:
Do you or anyone else have this version of the app, apkeureka seems to be down. I had to redo my fingerprints and now I cant get my method to work anymore.
[Magisk] Exel:
Here you go:

Dropbox

www.dropbox.com
[Magisk] bigknowz:
Got fingerprint working again flashing December update and then registering print before flashing magisk again. Have no interest installing Bank apk that is not from the Play Store.
[Magisk] roirraW "edor" ehT:
I think I'll be taking that route the next time I'm doing flashing on the phone. :)
[Magisk] Cares:
For some reason my fingerprint stopped working yesterday. I had to roll back and follow these steps to enable fingerprint again. It forced me to update the app to continue using it and upon updating it wouldn't let me use fingerprint again.
[Magisk] cognitivedissonance:
I'm still rocking a Pixel 2 XL running stock rooted 9.0.0. I've got Magisk 23.0 Stable installed and the following modules installed:

Busybox for Android NDK 1.34.1

Systemless Hosts 1.0

Riru 26.1.4.r552(etc)

Universal SafetyNet Fix 2.1.3

If it matters, I do still have TWRP installed as well.

When I run the SafetyNet check I get the following:

SafetyNet API Error
basicIntegrity (-)
ctsProfile (-)
evalType N/A

I believe this is a Magisk issue, b/c when I check SafetyNet using the app "SafetyNet Test" from the Play Store, it does pass.

While I can still log into the Chase app, I cannot access the Rewards section due to the pop-up that everyone is familiar with by now, notifying that root has been detected. Is there still a reliable method to get past this check, or am I screwed?
[Magisk] Xx-Ness-xX:
I can confirm fingerprint is working as for now.

Just flashed January update and set up fingerprint before rooting.

Tested on Pixel 5 Android 12
[Magisk] ChocoboX:
Thanks!! worked for me. Running Android 11 on a Pixel 4 XL. I didn't reboot on step 4 and still worked. I disabled the Magisk modules. I was able to get Citi to work as well.
[Magisk] Cares:
As of today with the latest Chase version my fingerprint login stopped working. Anyone else?

The app forces me to update so I have no choice.
[Magisk] gfrank227:
Mine hasn't worked for approximately six months. No matter what I do, it has been detecting root. I'm curious to know how you hid it for as long as you did. Their root detection is unbelievable, and maddening. If I can access their website from an admin account on a PC, then I should be able to access it from the root of a phone. It's no different.

Only thing that works is to install a program called Island. It uses the work profile built into Android. you can install Chase through the Island app, and then it won't detect root. If you then set up a fingerprint for work mode in settings, the fingerprint works too. But people shouldn't have to do this!
[Magisk] Cares:
I don't know how I hid it for so long. I just used the methods in this thread and it worked. But looks like it stopped working as of this latest update.

I use Island another app environment that I don't want my Chase app to be in it.
[Magisk] VD171:
I've tried the app today.

Before:

After:

About how hiding root actually?

I've installed Magisk v24.2, LSPosed v1.7.2, Shamiko v0.4.4, XPrivacyLua v1.30, Universal SafetyNet Fix v2.2.1 and everything is working perfectly.

I can hide root/xposed/lsposed/zygisk and fix safetynet, using it, please read my reply:

https://xdaforums.com/t/app-v1-10-vd-infos-package-com-vitaodoidao-vdinfos.4097379/post-86427499
[Magisk] cognitivedissonance:
My guess is that it's Shamiko that is doing the trick. I tend to believe that the way Chase is detecting root is by finding Magisk. As I understand it, that's what Shamiko does - hide Magisk.
[Magisk] Nekromantik:
So anyone got Chase UK app working?

Do you need Shamiko?

Edit: Using Shamiko and latest Magisk stable on Pixel 6 Pro works fine on Chase UK app.