[Discussion] The root-and-mod-hiding / fingerprint-spoofing / keybox-stealing cat-and-mouse game

Again (see previous response above) which PI spoofing you use?

PI Fork or PI Fix Inject or something else?

Ok, still you can check PI Attesting directly in PlayStore. Go to Settings, General, About and keep tapping to the Playstore version until you become a developer

Then go a step back, into that new Developer Options and run Check Integrity there

You should pass PI Attest but for the Brand, Device, Model, PlayStore must properly show your actual values, not the spoofed values

Also, check in your custom.pif.prop, your spoof settings should be
spoofBuild=1 spoofProps=1 spoofProvider=0 spoofVendingSdk=0 spoofVendingFinger=0

and in target txt you must have (among others - depending which apps you use):
com.android.vending com.google.android.gms

My custom.pif.prop had so of those but also spoofSignature=1

Target.txt had many items but also those 2 required ones. I went back to tricky store and selected only necessary including those 2, then realized the target file. None of this worked however, i still have no room it claims.

This might be my opportunity to switch from latest Magisk to ksun?

Ok, within the play store integrity, this checks out. It passes and shows my actual values.

My custom.pif.prop had so of those but also spoofSignature=1

Target.txt had many items but also those 2 required ones. I went back to tricky store and selected only necessary including those 2, then realized the target file. None of this worked however, i still have no room it claims.

This might be my opportunity to switch from latest Magisk to ksun?

Fix the Pending Update Loop with ADB

# Clear Play Store and GMS data with shell more thorough than the UI
adb shell pm clear com.android.vending
adb shell pm clear com.google.android.gms

# Reset the Package Mgr temp cache
adb shell rm -rf /data/local/tmp/*

You also might need to address the PI and Device Spoofing issue. Make sure that you haven't enabled Force Basic Attestation with a fingerprint from a device with very little storage because you’ve been messing with PI modules and now the Store thinks it’s living on a 2012 toaster with 8GB of storage.

Check /data/adb/modules/ for any folder related to PI or spoofing.

adb shell getprop | grep -E "model|product|fingerprint"

If these values don't jive with your actual phone, your spoofing module is still active even if disabled in the app.

Since your About tab won't update, the bin might be corrupted. Sideloading a fresh version sometimes fixes the installation directory permissions and remember to reboot in between any changes that you make. ( ͡° ͜ʖ ͡°)

Regulated in Circular 77/2025/TT-NHNN amending Circular 50 on online service security in the banking industry, to be in affect from March 1st:
Clause 2, Article 5: Amend and supplement Clause 4 of Article 8 as follows:

4. Implement solutions to prevent, combat, and detect unauthorized interference with the Mobile Banking application installed on customers' mobile devices. The Mobile Banking application must automatically exit or stop functioning and notify the customer of the reason if any of the following signs are detected:

a) A debugger is attached or the environment has a debugger running; or when the application is running in an emulator/virtual machine/emulator; or operating in a mode that allows the computer to communicate directly with the Android device (Android Debug Bridge);

b) The application software is injected with external code while running, performing actions such as monitoring executed functions, logging data transmitted through functions, APIs, etc. (hooks); or the application software is tampered with or repackaged.

c) The device has been rooted/jailbroken; or its bootloader has been unlocked."

Does it?

PW

But it doesn't say:
4.Implement solutions to prevent, combat, and detect unauthorized interference with the Mobile Banking application installed on customers' mobile devices, including but not limited to deploying a 'device destruct' mechanism, inducing electric shock or otherwise limiting a user's capacity to continue to use the device by any means deemed necessary. The Mobile Banking application must automatically exit or stop functioning and then notify the Police of the reason and specifics of any offending party if any of the following signs are detected:

Does it?

PW

Well it's over. It was fun while it lasted. My country officially banned ADB and bootloader unlocked devices fromm using banking apps. Effective from Mar 1.

We're resilient. We'll find a way around it.

It is already in place at India. None of the banking apps run on rooted devices. Though some works after some workaround, it is still a hassle to bank with rooted device and being a developer with limited devices. Also. some of the apps even check for the presence of VPNs (even local wireguard ones are flagged!) and additional SSL Root Certificates! It is getting crazier by day and I believe it is time to switch (ditch!) Android and requesting the community to create a pure Linux phone that gives full control to the users rather than every feature controlled by the organisations!!

It is already in place at India. None of the banking apps run on rooted devices. Though some works after some workaround, it is still a hassle to bank with rooted device and being a developer with limited devices. Also. some of the apps even check for the presence of VPNs (even local wireguard ones are flagged!) and additional SSL Root Certificates! It is getting crazier by day and I believe it is time to switch (ditch!) Android and requesting the community to create a pure Linux phone that gives full control to the users rather than every feature controlled by the organisations!!

Can you do your "banking" by using a browser to connect to the bank's web site? Maybe "request desktop site" in the browser?

Rooting and modding in general is getting more and more fruitless each day.