Develop Bugs

[Guide] Android Pay on rooted T-Mobile G5 - UPDATE: Workaround developed!

Android Pay use after rooting has been discussed in a few other threads, here on XDA, notably the 6P and 5X Nexi:
http://forum.xda-developers.com/nexus-6p/general/android-pay-root-t3309072
http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659
With our newly rooted H830s (courtesy of http://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-t3384526), it'd be nice to collect our information here.
I am very interested in how Android Pay may or may not work after our TOT flash. Here's a quick tutorial:
SuperSU must install via a 'systemless' root method due to security changes with Marshmallow. Thus, when SuperSU is flashed in TWRP as described in the TOT root thread, it can only install this way. It should not affect the /system partition.
Android Pay uses the "Safetynet API" to detect for tampering/root. What they classify as tampering is not entirely clear. But they do check /system among other things. It looks like apps that have altered the /system partition in some way are detected via this method.
(more boring info here http://www.howtogeek.com/241012/saf...y-and-other-apps-dont-work-on-rooted-devices/ )
It must also check the permissions of the /su/bin folder, as it should have a 751 permission profile (which is the described fix in the TOT root original post).
That is:
-Run "adb shell"
-From the shell run "su"
-On the # prompt run "chmod 751 /su/bin/"
Or, you can use root explorer to change the permissions octal to 751 for that folder.
It is set to this permission state in the rooted TOT upon first install. Obviously other root alterations you do may change it.
There are apps, such as Safetynet Helper sample (https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample), which can utilize the API to see if the API is tripped.
Right after installing the TOT and getting everything to boot properly, the app shows everything is still kosher. I was able to run Android Pay, add credit cards, and have confirmed with a payment transaction.
I believe any root app that doesn't make permanent changes to /system in and of itself will probably keep Android Pay working. Obviously, for instance, if you have a terminal program app with root, and run some commands that alter your system partition/files, it may trip SafetyNet, though just having the app installed does not.
EDIT1: As of 7/25/16, a change was made to the SafetyNet API and it now detects systemless root. Android Pay no longer works on rooted devices, regardless of method. A new method will need to be developed.
EDIT2: As of 8/22/16, a workaround has been developed and tested!​Developer @topjohnwu has created Magisk (http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382). This is a new way of integrating systemless changes into Android devices. This includes root, xposed, etc. The unique thing with Magisk is that you can instantly un-root your device, run Android Pay, and then reactivate root, all without rebooting. It is pretty seamless.
See the referenced thread for the latest information. It does take some work to install but it's fairly straightforward.
If you want to start from a clean install, @Gungrave223 has detailed the steps here:
http://forum.xda-developers.com/showpost.php?p=68353051&postcount=22
If you want to keep your data, it's just slightly more work. Assuming you are starting with a rooted install, here is a quick summary on how to do this:
0. You may want to first un-register the cards you have in Android Pay. Some banks apparently only allow a set # of installs before they block additional installs, thus requiring you to call the bank directly to have them reset that number. If Android Pay resets (unsure what security changes trigger this), it will forget your cards, thus leaving those cards registered on a phantom install. Un-registering first may prevent this.
1. Get the Magisk flashable zip, the Magisk-altered phh-superuser.zip, and the Magisk manager apk from the referenced thread.
2. Go to SuperSU and select full unroot. DO NOT restore the stock boot.img. DO NOT restore the default recovery. The phone should reboot and your root will be lost.
3. You should now restore the stock boot.img. This can be done without losing your data or re-encrypting your data. There are 2 ways.
Flash autoprime's stock boot.img zip file through TWRP (recommended), OR
Flash the TWRP-ed TOT file through LGUP, using the UPGRADE (not refurbish) setting
Why not just allow SuperSU to restore the stock boot.img in step 2? Because it will reboot instantly into system and start encrypting your data, with no way for you to intervene and boot into TWRP first!
4. You likely did not have data encryption on your initial rooted installation. If you want to keep yourself un-encrypted, you MUST immediately boot into TWRP before the next power on. If you do not, it will re-encrypt your data. This is the default behavior of the stock boot partition, which you just restored in the step above. You can make this easy for yourself by TWRP flashing autoprime's stock boot.zip and then immediately doing the next steps. Note: Magisk can be installed just fine on a phone with an encrypted data partition if you don't care about data encryption.
Flash the magisk.zip from the Magisk thread. This installs Magisk and also disables the forced encryption (just like the dm-verity zip)
Re-establish root by then flashing the special modified phh-superuser.zip
Note: Chainfire's SuperSU is NOT compatible if you want to use Android Pay
5. Reboot into system. You need to then install from the Playstore phh's superuser app. You also need to install the Magisk manager apk. Grant all your usual apps root permission in the superuser app.
6. Run Magisk Manager and grant it superuser access. You'll find a simple toggle to mount/unmount root. Unmount! Check that SafetyNet will pass. If you've done everything right, it will!
7. Run Android Pay. Add your card(s) back. Mount root back and go about your business.
8. When you want to use Android Pay, unmount root and run the app. Here's a tricky part (and currently a work in progress). We do not know how often or when Android Pay checks for root. We DO know that it does this when you initiate adding a new card. So you can try an Android Pay transaction. If it fails (they often do, even if you are unmounted root at that time), pretend to add a card, cancel it, and then do the transaction again. It should work now!

pay was not working after I installed the Fluence patch, uninstalled xposed and Android Pay is working with no issues with root.

fatapia said:
pay was not working after I installed the Fluence patch, uninstalled xposed and Android Pay is working with no issues with root.
Click to expand...
Click to collapse
The Fluence patch has a huge # of system changes. I would totally expect xposed to break the SafetyNet.
So do you have Fluence still installed, with only xposed removed?

waylo said:
The Fluence patch has a huge # of system changes. I would totally expect xposed to break the SafetyNet.
So do you have Fluence still installed, with only xposed removed?
Click to expand...
Click to collapse
Yup you got it, I had been running Xposed off Fluence for a while until I left my wallet at home and didn't feel like starving. So I downloaded the Xposed uninstaller only, ran it in recovery and then let it reboot and Pay was working again.

I followed the instructions for rooting in this thread, http://forum.xda-developers.com/tmo...p-step-guides-rooting-t-mobile-lg-g5-t3388272 and then the instructions here to change the permissions but an still having problems. The only app root app I installed after rooting was an app to export google play music with track names intact.

What problems specifically are you having?
Did you install the safetynet helper app? What happens when you run it?
What root app did you install? Was it this one? http://forum.xda-developers.com/showthread.php?t=2620331 (play music exporter) aka https://www.david-schulte.de/en/play-music-exporter/
Looks like that app doesn't work in MM regardless, per the developer's page.

waylo said:
What problems specifically are you having?
Did you install the safetynet helper app? What happens when you run it?
What root app did you install? Was it this one? http://forum.xda-developers.com/showthread.php?t=2620331 (play music exporter) aka https://www.david-schulte.de/en/play-music-exporter/
Looks like that app doesn't work in MM regardless, per the developer's page.
Click to expand...
Click to collapse
Yes, that is the app. I noticed MM was not supported after I had it installed
I have installed and run the safetynet app and it shows it gets tripped on the CTS profile
---------- Post added at 02:03 PM ---------- Previous post was at 01:40 PM ----------
I just realized I also had Adguard installed. I have uninstalled it and turned off suppersu and restarted but the phone still does not pass the CTS profile check

Wondering if any of those apps made some changes to /system that were not completely reversed.
Doesn't look like that music app does any permanent changes anyway, rather just copies cache not normally accessible into another folder.
Can you check the permission profile of your /su/bin folder?
Briefly looking at the Adguard website I can't make out how its root version works exactly.
What other apps are listed under your SuperSU app list? You're not running xposed, right?

Apps listed in supersu are adb shell, root checker basic, and Titanium backup.
Titanium backup was installed after safetynet app test failed.
I'm not 100% sure what the permissions are but I followed your instructions above to change the permissions and it appeared to run correctly

eremeya said:
Apps listed in supersu are adb shell, root checker basic, and Titanium backup.
Titanium backup was installed after safetynet app test failed.
I'm not 100% sure what the permissions are but I followed your instructions above to change the permissions and it appeared to run correctly
Click to expand...
Click to collapse
SafetyNet still failing after the permissions change?

It was today. I can try changing them again tonight when I'm at my computer and report back.

I have confirmed that the folder permissions are set to 751

eremeya said:
I have confirmed that the folder permissions are set to 751
Click to expand...
Click to collapse
Well if we can't track down the actual changes made, and you're interested in getting Android pay to work, you could try reflashing the system partition.

It looks like from reports on other threads (Nexus mostly), that something has changed with the SafetyNet check. Phones that were working just fine yesterday now fail. Most likely something server-side was patched so now Android Pay will not work with systemless root.
Details updated as I find them.

For those interested in this topic, a pretty major development has occurred at this thread:
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Essentially, this is a brand new way to implement root systemless, which can be toggled via an app, without rebooting. This does allow the SafetyNet api to remain untripped. The steps involved include flashing back to stock kernel/system, flashing the application .zips, and flashing special SuperSU or SuperUser .zips. I have not done any of this yet as it is still very early.
There are some reports, unfortunately, such as this post:
http://forum.xda-developers.com/showpost.php?p=68045722&postcount=121
which reports that despite SafetyNet passing, Android Pay still does not work (user is on Nexus 6P).
I have read of no G5 users doing this yet, but there is a V10 user who has. Stay tuned.

I've been watching the Magisk threads for the past week and decided to take the plunge today. Many Nexus phones seem to have a lot of trouble with Android Pay, but other makes seem to do better. There were confirmations from LG G4 owners. As of this writing Magisk is on v3.
The install steps from the Magisk thread are this:
1. Reflash a stock boot.img to reset your systemless root
2. Flash Magisk.zip
3. Flash modified phh-superuser.zip (not the official one). Chainfire's SuperSU does not currently have as much support, but there is a modified supersu zip as well.
4. Boot and install phh's superuser app from the App store.
5. A 'magisk manager' app is installed via the flashed .zips. This allows you to turn off root for a set # of minutes, without rebooting.
Given the unique way the G5 is rooted, with automatic encryption, I figured it might not be so simple to install this if I wanted to keep my data without a full wipe. It quickly became much more complicated than what I wanted. Here's exactly what happened.
First, I made a full boot+system+data backup.
Then, these were my thoughts/concerns:
I have Adaway installed with the systemless addon zip and SuperSU installed. Magisk installation requests flashing back the stock boot.img. What would this do to the supersu install and Adaway?
The adaway systemless zip makes a script file which is kept in the /su/su.d/ folder. I removed this.
The SuperSU has a complete uninstall feature. As part of this uninstall process, it asks if you want to restore the boot.img (yes--this stock one is backed-up after the initial supersu.zip flash during our initial root/TOT process) and/or the recovery (no, don't do this, but it probably would not have done anything as there is no stock recovery backup). I thought this would accomplish our goal. It does warn you that you may have re-encrypting of the data partition if you go this route.
And unfortunately, after rebooting, it automatically and immediately encrypted the data partition.
Well shoot. Correct me if I'm wrong, but an encrypted data partition cannot be worked on. It booted just fine, but without root.
I started having some doubts at this time so I decided to try to restore back to my initial setup. Through TWRP, I wiped the data partition and flashed the no-verity.zip, to hopefully stop any re-encryption.
Then, after figuring out how to mount system properly (TWRP defaulted to mount system as r/o), I restored my nandroid backup in its entirety.
But upon reboot, it went immediately into bootloader mode. And it continued to do this after every battery pull and power on. I had never heard of this before! Finally, I realized I could still boot into TWRP. I flashed the 10Dcomplete.zip made by autoprime, restoring the boot and system partitions to stock. And then I flashed the magisk v3.zip and the modified phh-superuser zip.
It finally rebooted into Android, with data intact! Oddly, my unlock pattern had changed without my knowledge, but the backup PIN worked. I installed the market phh Superuser. Magisk is installed properly and it passes SafetyNet, and I can add cards to the app. I'll test out Android Pay next opportunity I have.
If I had to do it all again and wanted to keep data intact, this is what I would do.
1. Autoprime did make a 10D boot flashable zip. So this would restore the stock boot.img as intended. There are some files to clean up, such as data/su.img, but that can be dealt with later.
2. I do not know if just flashing the stock boot.img would result in re-encrypting. It probably would. So, immediately after flashing the boot.img in TWRP I would flash magisk and the phh-superuser.
Alternatively, they say you should not dirty flash for things this complex. So consider starting completely new from a 10Dcomplete flash with wiped data.

I've learned that Magisk will work fine with an encrypted data partition, so if you are set on having that, it won't be a problem.

waylo said:
I have a thread here discussing Android Pay while rooted on our G5s:
http://forum.xda-developers.com/tmob...le-g5-t3395036
I thought I was the only one who cared about this kind of stuff!
Which version Magisk did you install?
I just did this 2 days ago but haven't had the opportunity to test AP yet.
What rooted apps are you running? AdAway?
Click to expand...
Click to collapse
To answer your question... I'm using v3 with his v2 of his modified phh superuser.
As for rooted apps...yes AdAways still works perfectly....TB...my one time use of System App Remover etc...
I haven't been able to test Android util tomorrow....but SafetyNet did pass when Magisk was disabled and failed when enabled.
I'll report back tomorrow after I go buy my weekly chicken at my local Fresh Mart.

I'm using the same install as you.
I tried it this AM for the first time and it failed.
On the Magisk-AP thread, someone has posited that maybe the AP app caches any root inquires during that boot. So if you test out AP and it fails while the root is active, it will remember that failure until the next reboot.
That could explain how so many people are getting weird inconsistent results. I'm testing out that theory later today.

Bah, still doesn't work, even if done immediately after a reboot =(

Alternative to SuperSU

As far as I understand it many banking apps simply check for the existance of supersu.apk, and if found denies access. Is it correct that by using another method to getting root, this problem might be solved? And if so, which alternatives are there (can Magisk be used on a OP3)?

snegom said:
As far as I understand it many banking apps simply check for the existance of supersu.apk, and if found denies access. Is it correct that by using another method to getting root, this problem might be solved? And if so, which alternatives are there (can Magisk be used on a OP3)?
Click to expand...
Click to collapse
Yes it can be done (I can use banking apps and Android Pay on my OP3).
1. Disable any in-built root/remove exisiting SuperSU.
2. Flash Magisk
3. Install Magisk Manager
4. Enable Magisk Hide
5. Try app - If it still doens't work go back onto Magisk Hide and enable it on that specific app by pressing the checkbox and it should work. (Try rebooting if it doesn't work)
6. If possible turn off devloper options/ADB options in settings as these can stop banking apps from working.
I hope this helps

I confirm magisk is legit and fantastic!!!
Sent from my OnePlus 3 using XDA Labs

Magisk works perfectly for all the apps which checks for the SAFETYNET......some apps need not be hided using magisk hide ...just bypassing the safetynet is enough for A-pay and banking apps ...

check this thread out:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

byAidan said:
Yes it can be done (I can use banking apps and Android Pay on my OP3).
1. Disable any in-built root/remove exisiting SuperSU.
2. Flash Magisk
3. Install Magisk Manager
4. Enable Magisk Hide
5. Try app - If it still doens't work go back onto Magisk Hide and enable it on that specific app by pressing the checkbox and it should work. (Try rebooting if it doesn't work)
6. If possible turn off devloper options/ADB options in settings as these can stop banking apps from working.
I hope this helps
Click to expand...
Click to collapse
Had this as a small project for this Easter. However for 1) above, is it as simple as just running "Change superuser app" in SuperSU free before proceeding with 2-6) ? Have seen some rather complicated install instructions elsewhere - and can also see that some users have experienced various problems.

snegom said:
Had this as a small project for this Easter. However for 1) above, is it as simple as just running "Change superuser app" in SuperSU free before proceeding with 2-6) ? Have seen some rather complicated install instructions elsewhere - and can also see that some users have experienced various problems.
Click to expand...
Click to collapse
The only way I could completely remove SuperSU was to dirty flash OOS. Otherwise safety net still detected SuperSU. Rooted with magisk and used magisk hide. Can now play Mario run and used Android pay.

How To Guide EASIEST method to unblock McDonalds app and many more

Hello everyone, after a long time of not being able to figure out on how to make the McDonalds app work on a magisk rooted phone with twrp + custom rom. I finally managed to do it.
I want to share my method with you, hopefully it will work for everyone.
At first, install the McDonalds app (If not already done).
1. Install app manager from play store
2. Force stop + clear cache
3. In magisk, enable magiskhide and follow the steps.
4. In the new magisk app. Select Systemless hosts
5. Also, enable denylist and add McDonalds to it.
6. Install Universal Safetynet Fix by kdrag0n from github.
7. After installing, the apps should work.
Good luck!

which version of magisk?

I don't know exactly, I am using the latest version. Should work on most versions that includes MagiskHide

kyanbarth330 said:
I don't know exactly, I am using the latest version. Should work on most versions that includes MagiskHide
Click to expand...
Click to collapse
Open magisk and it will shiw you what version you have

I'm using 25.2

can you show screen shot of your magisk and the magisk hide function, it is not in mine. i usually use magisk delta which does have magisk hide in it

Or just use the browser when ordering.

It still doesn't work I think they detect an unlocked bootloader even if you don't have root

I saw a module in Lposed that blocks root in the macdonalds app.
Thread '[MOD][XPOSED][4.1+] McRoot (McDonalds Global App)' https://forum.xda-developers.com/t/mod-xposed-4-1-mcroot-mcdonalds-global-app.4265069/

Hey, thanks for the "tutorial"! Kinda surprised that it works even on banking apps or it could be another thing that i tried before.
Edit: I think that you need LSPosed + Hide My Applist for the banking apps

Magisk-in-recovery, unable to reboot to unrooted mode

I've got magisk in recovery installed, but it's quite annoying to reboot to non-rooted mode.
To reboot to recovery mode, I need my headphones plugged in, but the reboot works fine.
When I want to reboot to unrooted mode, I have to reboot to download mode, then cancel out of it for it to work. I've tried shutting down and rebooting, using the magisk app to reboot, but all just reboot to rooted recovery mode instead. Is this intentional or something I'm doing wrong?

See Magisk in Recovery
Why are you trying to reboot to non-rooted mode? If you're having issues with certain apps, simply having an unlocked bootloader may be causing the issue. See this thread.

V0latyle said:
See Magisk in Recovery
Why are you trying to reboot to non-rooted mode? If you're having issues with certain apps, simply having an unlocked bootloader may be causing the issue. See this thread.
Click to expand...
Click to collapse
Nah. The apps that are locked during root work fine in unrooted mode. Kinda weird, but they work fine with an unlocked bootloader. It's mostly government apps and banking apps which are locked when in recovery root mode.
Also, yes I saw the magisk in recovery page, and I tried booting from power off, but it somehow goes into recovery root mode instead of unroot. Which is why I'm so confused.

FreSchDude said:
Nah. The apps that are locked during root work fine in unrooted mode. Kinda weird, but they work fine with an unlocked bootloader. It's mostly government apps and banking apps which are locked when in recovery root mode.
Also, yes I saw the magisk in recovery page, and I tried booting from power off, but it somehow goes into recovery root mode instead of unroot. Which is why I'm so confused.
Click to expand...
Click to collapse
I would still check your Play Integrity verdicts to see if that might be part of the problem. It's also possible that the apps in question are able to detect the SU binary; there are Magisk modules that can help hide this such as Shamiko

V0latyle said:
I would still check your Play Integrity verdicts to see if that might be part of the problem. It's also possible that the apps in question are able to detect the SU binary; there are Magisk modules that can help hide this such as Shamiko
Click to expand...
Click to collapse
Alright. So I should check play integrity for root and non-root, and then what is that other test?

Alright, so, non-root mode only passes basic whilst failing device and strong. Root recovery mode fails all 3 checks.
Is there a magisk module to pass the basic check? Or there might be something else besides that that the apps check for when verifying root...

FreSchDude said:
Alright, so, non-root mode only passes basic whilst failing device and strong. Root recovery mode fails all 3 checks.
Is there a magisk module to pass the basic check? Or there might be something else besides that that the apps check for when verifying root...
Click to expand...
Click to collapse
Read the OP, I linked a Magisk module that should fix BASIC and DEVICE verdicts

V0latyle said:
Read the OP, I linked a Magisk module that should fix BASIC and DEVICE verdicts
View attachment 5890551
Click to expand...
Click to collapse
Shamiko, Universal SafetyNet Fix and zygisk has been enabled. Most apps are working, but some still don't work.
Configuring them was sure a pain, I've got over 30 banking/government apps, and a handful still don't work.
I pass the device and basic now, and Momo doesn't detect SU and magisk anymore. I'm curious how some apps are still able to detect root. Probably has the strongest security because it's a government app.

Sorry about all this trouble, I remember that I once tried back when magiskhide was a thing, but couldn't get some apps to work. I then settled for just booting into non-rooted mode and kinda just stuck with it. As of now, around 5 apps of the 30 still refuse to work and are blocked, detecting root, even with shamiko and the other stuff configured.

Hmmm. Try TB Checker and run the root check.

V0latyle said:
Hmmm. Try TB Checker and run the root check.
Click to expand...
Click to collapse
root management apps, SU binary, 2nd SU Binary, Root via native and Magisk specific checks failed.
After setting up the denylist for Shamiko, it only fails the first test, the Root Management Apps one.

FreSchDude said:
root management apps, SU binary, 2nd SU Binary, Root via native and Magisk specific checks failed.
After setting up the denylist for Shamiko, it only fails the first test, the Root Management Apps one.
Click to expand...
Click to collapse
Update: I activated magisk hide and now all checks pass.
I'll be goin off to bed now, I'll be back in the morning.
Thanks for all the help so far mate

No problem.
I'd suggest bringing this up in the Magisk General Support/Discussion thread as the wizards over there might be able to help. Make sure you mention the specific app you're having trouble with.

Question How do you hide your root-state?

Hello!
I have a Realme GT Master Edition, running Android 13 under RUI4.0
I rooted the stock rom with a patched boot.img by Magisk and without TWRP. (stock recovery)
So far so good...
My question is now how i can hide that my phone is rooted? There are some apps (for example banking apps or netflix app) that doesn't work because my device can't be trusted if it is rooted.
Magisk hide is not existing for newer devices. I googled it and can't find a working solution that i can trust.
Do you have a suggestion or if your phone is rooted how do you hide it from these apps?
What are Modules in Magisk? Maybe there is an option for this or a sort of expansion to install?
The most apps that look up the root state just warn me that my device is rooted but work as normal. (So it is no problem if there is no solution, I just don't want to see that warning everytime i start an app)

Robro86 said:
Hello!
I have a Realme GT Master Edition, running Android 13 under RUI4.0
I rooted the stock rom with a patched boot.img by Magisk and without TWRP. (stock recovery)
So far so good...
My question is now how i can hide that my phone is rooted? There are some apps (for example banking apps or netflix app) that doesn't work because my device can't be trusted if it is rooted.
Magisk hide is not existing for newer devices. I googled it and can't find a working solution that i can trust.
Do you have a suggestion or if your phone is rooted how do you hide it from these apps?
What are Modules in Magisk? Maybe there is an option for this or a sort of expansion to install?
The most apps that look up the root state just warn me that my device is rooted but work as normal. (So it is no problem if there is no solution, I just don't want to see that warning everytime i start an app)
Click to expand...
Click to collapse
Magisk definitely works. Download the latest version
Download Magisk Manager Latest Version 26.1 For Android 2023
Magisk Manager is an app which helps users to root their phone. With the help of Magisk you can run banking apps and also pass SafetyNet tests.
magiskmanager.com

Robro86 said:
Hello!
I have a Realme GT Master Edition, running Android 13 under RUI4.0
I rooted the stock rom with a patched boot.img by Magisk and without TWRP. (stock recovery)
So far so good...
My question is now how i can hide that my phone is rooted? There are some apps (for example banking apps or netflix app) that doesn't work because my device can't be trusted if it is rooted.
Magisk hide is not existing for newer devices. I googled it and can't find a working solution that i can trust.
Do you have a suggestion or if your phone is rooted how do you hide it from these apps?
What are Modules in Magisk? Maybe there is an option for this or a sort of expansion to install?
The most apps that look up the root state just warn me that my device is rooted but work as normal. (So it is no problem if there is no solution, I just don't want to see that warning everytime i start an app)
Click to expand...
Click to collapse
USE BANKING APPS on ROOTED DEVICES
1. Download and FLASH SHAMIKO MODULE 2. HIDE the MAGISK APP with any other name other than SETTINGS 3. Enable ZYGISK 4. Configure DENYLIST - Tap on the UPI app in the DENYLIST and then SELECT THE CHECK MARK - Make sure the PROGRESS BAR over the...
forum.xda-developers.com

Stano36 said:
USE BANKING APPS on ROOTED DEVICES
1. Download and FLASH SHAMIKO MODULE 2. HIDE the MAGISK APP with any other name other than SETTINGS 3. Enable ZYGISK 4. Configure DENYLIST - Tap on the UPI app in the DENYLIST and then SELECT THE CHECK MARK - Make sure the PROGRESS BAR over the...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks, this is working for me. Not in every App, but the annoying warning in the Banking app is gone.
Other apps seem to have problems connecting to a server. - But I don't really need that apps.

Robro86 said:
Thanks, this is working for me. Not in every App, but the annoying warning in the Banking app is gone.
Other apps seem to have problems connecting to a server. - But I don't really need that apps.
Click to expand...
Click to collapse
Magisk's exclusion list works perfectly for me (GDPR firmware), no need extra app.