Database Develop

Bypass DBS banking App

Resently BDS banking app(India) is updated.is there any modules to make that work...

Aniruddhlr said:
Resently BDS banking app(India) is updated.is there any modules to make that work...
Click to expand...
Click to collapse
This isn't xposed, so probably not. As long as your passing safetynet and enabled magisk hide for that and rebooted, in theory you should be fine. The next thing you can try is force closing the app and in Magisk manager, tapping "hide magisk manager" but that's only a temporary fix, some apps now check to see if magisk is installed at all. This will fix that

manor7777 said:
This isn't xposed, so probably not. As long as your passing safetynet and enabled magisk hide for that and rebooted, in theory you should be fine. The next thing you can try is force closing the app and in Magisk manager, tapping "hide magisk manager" but that's only a temporary fix, some apps now check to see if magisk is installed at all. This will fix that
Click to expand...
Click to collapse
Magisk is installed and passes safety net.
Still many banking apps detected root like BHIM.
And is there any way to hide custom ROM?

Aniruddhlr said:
Magisk is installed and passes safety net.
Still many banking apps detected root like BHIM.
And is there any way to hide custom ROM?
Click to expand...
Click to collapse
You can make a script to change the build information in the rom to release-keys instead of test-keys, some apps detect that. Also make sure you tick your banking app in Magisk hide settings. I believe there is a module so ewhere on the forum to do this, I will link it if I see it. Also you can try universal safetynet bypass module

manor7777 said:
You can make a script to change the build information in the rom to release-keys instead of test-keys, some apps detect that. Also make sure you tick your banking app in Magisk hide settings. I believe there is a module so ewhere on the forum to do this, I will link it if I see it. Also you can try universal safetynet bypass module
Click to expand...
Click to collapse
Thank you.ill try and tell you results.

Aniruddhlr said:
Magisk is installed and passes safety net.
Still many banking apps detected root like BHIM.
And is there any way to hide custom ROM?
Click to expand...
Click to collapse
manor7777 said:
You can make a script to change the build information in the rom to release-keys instead of test-keys, some apps detect that. Also make sure you tick your banking app in Magisk hide settings. I believe there is a module so ewhere on the forum to do this, I will link it if I see it. Also you can try universal safetynet bypass module
Click to expand...
Click to collapse
MagiskHide already changes the prop to release-keys (and some other props). And since SafetyNet already passes there's no need for the Universal SafetyNet Fix module.
Only thing to do is to add the app to the Hide list (no module needed for that) and also hide the Magisk Manager (there's an option for that in the Manager settings). Also make sure to use the latest release (currently v14.6 beta) since there's often improvements being done.
It's also possible that the app detects things like Developer options and USB Debugging being enabled. That can't be hidden by Magisk, so try disabling those if they're enabled.

Didgeridoohan said:
MagiskHide already changes the prop to release-keys (and some other props). And since SafetyNet already passes there's no need for the Universal SafetyNet Fix module.
Only thing to do is to add the app to the Hide list (no module needed for that) and also hide the Magisk Manager (there's an option for that in the Manager settings). Also make sure to use the latest release (currently v14.6 beta) since there's often improvements being done.
It's also possible that the app detects things like Developer options and USB Debugging being enabled. That can't be hidden by Magisk, so try disabling those if they're enabled.
Click to expand...
Click to collapse
Yeah just now I saw that release keys in build prop.
I'm not on beta is it safe to install beta(magisk).
I'll try those debugging things.

It's saying runtime tampering.what does it mean?

Aniruddhlr said:
Yeah just now I saw that release keys in build prop.
I'm not on beta is it safe to install beta(magisk).
I'll try those debugging things.
Click to expand...
Click to collapse
Beta is safe... The worst that can happen (that I've seen so far) is a bootloop that can be fixed by flashing a clean boot image or an earlier release (v14.5).
There might also be problems with the su database, but that should be fixed by uninstalling the app (from within the Manager, press Uninstall and choose Uninstall App) and reinstalling it.
It's worth it, since the Hide feature is much improved in v14.6.
---------- Post added at 12:21 ---------- Previous post was at 12:21 ----------
Aniruddhlr said:
It's saying runtime tampering.what does it mean?
Click to expand...
Click to collapse
What is saying that?

https://i.imgur.com/e2rAlNI.png

Didgeridoohan said:
Beta is safe... The worst that can happen (that I've seen so far) is a bootloop that can be fixed by flashing a clean boot image or an earlier release (v14.5).
There might also be problems with the su database, but that should be fixed by uninstalling the app (from within the Manager, press Uninstall and choose Uninstall App) and reinstalling it.
It's worth it, since the Hide feature is much improved in v14.6.
---------- Post added at 12:21 ---------- Previous post was at 12:21 ----------
What is saying that?
Click to expand...
Click to collapse
I added a image.see

Aniruddhlr said:
I added a image.see
Click to expand...
Click to collapse
Hello again.
Yes, I saw the image... But, the only thing you could try is to update Magisk and use the improved hiding features.
There are a few issues with the latest stable v15.0. Many Samsung and Huawei users are experiencing bootloops and some users have had forced encryption issues. Don't think I've seen any issues mentioned for Xiaomi devices though... Just make sure to have a backup and the latest Magisk uninstaller zip available and you should be good to go.
If you're feeling unsure about updating, wait... The issues are under investigation.

Didgeridoohan said:
Hello again.
Yes, I saw the image... But, the only thing you could try is to update Magisk and use the improved hiding features.
There are a few issues with the latest stable v15.0. Many Samsung and Huawei users are experiencing bootloops and some users have had forced encryption issues. Don't think I've seen any issues mentioned for Xiaomi devices though... Just make sure to have a backup and the latest Magisk uninstaller zip available and you should be good to go.
If you're feeling unsure about updating, wait... The issues are under investigation.
Click to expand...
Click to collapse
Thanks for that warning.
I already updated to 15v and found forced encryption issue.
Does runtime tampering have anything to do with this root?

Aniruddhlr said:
Thanks for that warning.
I already updated to 15v and found forced encryption issue.
Does runtime tampering have anything to do with this root?
Click to expand...
Click to collapse
Have you gotten v15.0 up and running? If not you could try again and uncheck "Preserve forced encryption" in the Manager before updating, or if you're flashing from recovery you could run the following code in the recovery terminal first:
Code:
echo KEEPFORCEENCRYPT=false>>/data/.magisk
Runtime tampering is probably just DBS's way of saying your device is rooted.
After getting v15.0 running, add the app to the Hide list and hide the Manager (option in settings). You might also have to clear data for the DBS app.
Also make sure that MagiskHide is working by checking SafetyNet. If at least basic integrity passes we know it does. If it doesn't, toggle MagiskHide off and on in the Manager settings and try again.

Hi, I am also facing same issue. My device is Zuk Z2 and am on Dot-OS rom. Magisk passes SafetyNet, have enabled Magisk Hide but still this DBS bank app detects root.
I also tried after disabling Developer options. Same error. What extra can be done?

+1
I need access to this app too whilst rooted with Magisk

tomdot said:
+1
I need access to this app too whilst rooted with Magisk
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417

DBS banking app finally works with Magisk 16.0 (with Magiskhide)

Mine can't work.. there no error code appearing when opening the app but the app hangs at "log in " and "register" page.. anyone can help please
I'm using ressurectiin remix on redmi note 5

tomdot said:
DBS banking app finally works with Magisk 16.0 (with Magiskhide)
Click to expand...
Click to collapse
yes it's work for me,
1st i check it in my hide list
and then i hide my magisk
if only i did my 1st choice it still give some warning and force close the app
thanks

Root detected by GO MOBILE banking app

I've been scratching my head for weeks now this app keeps on detecting root on my device. I've previously tried canary build, but currently on 20.1 and it still detects it. App is MagiskHided, Magisk Manager repackaged, both SafetyNet basicIntegrity and ctsProfile is passed. My other banking app that also checks for root works, even the rootbeerFresh is showing all green and this app still detects root. I don't know what else to try.
Device Info:
OnePlus 6T running Evolution X rom (Android 10), I also tried on OOS pie, doesn't work as well.
Magisk 20.1
This app used to work just by MagiskHide and repackaging Magisk Manager, since the update, I think they changed something. Any help is appreciated.

I tested it right now and had no issues starting the app once added to the Hide list. OnePlus 3T, Android 9 (ArrowOS), Canary build 20302 with hidden Manager build 269.
That means Magisk can hide from the app just fine and there might be something about your specific setup that's being detected. Could be an app, could be a directory on your storage, could be the ROM itself (this is the second time lately that I've seen a user having issues with root detection on Evolution X, on a Poco F1 though. May be unrelated.).
As always, there are a lot of hiding tips available here:
https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

Didgeridoohan said:
I tested it right now and had no issues starting the app once added to the Hide list. OnePlus 3T, Android 9 (ArrowOS), Canary build 20302 with hidden Manager build 269.
That means Magisk can hide from the app just fine and there might be something about your specific setup that's being detected. Could be an app, could be a directory on your storage, could be the ROM itself (this is the second time lately that I've seen a user having issues with root detection on Evolution X, on a Poco F1 though. May be unrelated.).
As always, there are a lot of hiding tips available here:
https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Click to expand...
Click to collapse
DId you MagiskHide it beforehand or did you try without MagiskHide first? I want to make sure that the app doesn't "remember" that it has detected root previously

terraflops said:
DId you MagiskHide it beforehand or did you try without MagiskHide first? I want to make sure that the app doesn't "remember" that it has detected root previously
Click to expand...
Click to collapse
I made sure that it could detect root first, so I opened it once without adding it to MagiskHide (got the same screen you showed above). And, I did not have to clear any data for the app after adding it to the list, it just started up without issue.

terraflops said:
DId you MagiskHide it beforehand or did you try without MagiskHide first? I want to make sure that the app doesn't "remember" that it has detected root previously
Click to expand...
Click to collapse
any luck for this problem?

I also have this issue. Any luck?!

I have the same issue and finally found a solution for it ! Change the folder twrp name on internal storage was a trick but don't forget to hide the aplication go mobile from magisk hide then boom I can use the banking aplication on my root devices .
I'm not using any xposed so if you are on xposed try rename the folder of it usually it store on folder download on the internal if that doesn't work try to uninstal the xposed application on your mobile menu(you can instal it again after you're done with banking)
Another trick that I found latelly was I change the recovery ....any recovery besides the twrp (orangefox,pitchblack,batik etc)

Aldino21 said:
I have the same issue and finally found a solution for it ! Change the folder twrp name on internal storage was a trick but don't forget to hide the aplication go mobile from magisk hide then boom I can use the banking aplication on my root devices .
I'm not using any xposed so if you are on xposed try rename the folder of it usually it store on folder download on the internal if that doesn't work try to uninstal the xposed application on your mobile menu(you can instal it again after you're done with banking)
Another trick that I found latelly was I change the recovery ....any recovery besides the twrp (orangefox,pitchblack,batik etc)
Click to expand...
Click to collapse
Awsome maaan, like that simple trick could be solve the pricky app

LSPosed Xposed Framework [8.1-13.0]. Simple Magisk Module

Developers: LSPosed Developers
Homepage: GitHub
✱ Requirements:
• Magisk 21+
• Android 8.1-13
• Riru(NOT NEEDED) USE ZYGISK
Description: Riru module providing ART interception framework (natively for Android Pie) that provides consistent API -interfaces with OG Xposed, using YAHFA (or SandHook) interception environment, supports Android 8.1 ~ 11.
& Installation:
• Install Riru 23+
• Install Riru - LSPosed via Magisk Manager
• Install LSPosed Manager app (Note: No Saparate App and Zip, App Will be Installed Automatically)
• Reboot your device.
Download:
For stable release, please go to Github Release page For canary build use telegram.
Go to second post for latest version Download
Notes:I'm just sharing this from github, I'm not responsible if you bricked your device.
GPay and other banking apps working fine without any issue so this xposed alternative is worth trying and safer.
Note: If anyone facing bootloop issue, don't panic, hard reboot again and it will work.
Screenshot:

Download:
Flash zip file through magisk and then install LSPosed Manager app
Update 1 March 2021
V1.2.0
V1.3.7 Updated 15.May.2021
(Note: No Saparate App and Zip, App Will be Installed Automatically)
For Newer Version Changelogs and Downloads:
LsPosed Github
Changelog
Spoiler: See
Fix manager white screen
[*]Support split-apk modules (LSPosed will choose only one apk with xposed_init to load)
[*]Fix manager crash when launching an uninstalled module from notification
[*]Load modules with SharedMemory (it can speedup app cold launch) 2
[*]New manager icon
[*]Fix incorrect update notification in the first installation
[*]Fix some apps not showing in the scope list in some rare cases
[*]Show notification of module uninstallation
[*]Prevent modules from hooking inner methods (methods from XposedBridge's classloader)
Note:
Previously LSPosed only recognize modules from the primary user. However, this strategy is not good and leads to some problems: some modules require getting installed app lists for configuration but they cannot do so across users; some require reading themselves from the hooked apps but they cannot do so from non-primary users; some users want to configure modules differently on different users which is not feasible previously. Thus LSPosed now requires every module to be installed to the user on which the apps they want to hook are installed. Some devices restrict modules from installing onto some users. In such a case, you can install them from the manager (but it's recommended).
1: For some weird devices that prevent installing apps from the root user, please install the manager from /data/adb/lspd/manager.apk or manager.apk from the zip file manually.
2: Some modules get modules' apk path using reflection of its classloader, it's not recommended and unstable since the apk path from classloader no longer exists when using SharedMemory to load modules. Please use the documented way (from IXposedHookZygoteInit.StartupParam.modulePath) instead.

Reserved 2

Why it's safer than EdXposed?

QkiZMR said:
Why it's safer than EdXposed?
Click to expand...
Click to collapse
I didn't say it's safer than edxposed. I meant xposed alternatives like taichi etc.
All banking apps works, no system slowdown, i got more free ram etc.
In edxposed the hooked apps take time to open, no such issue with LSPosed.
That's why i thought it's worth trying and safer.

And +1 is safetynet passes all the time with LSPosed but, with edxposed safetynet works for some time after every reboot even with blacklisting google framework and services.

This slowdown is caused by YAHFA hook in EdXposed. On Sandhook is much better. Which hook method you use in LSposed?
And +1 is safetynet passes all the time with LSPosed but, with edxposed safetynet works for some time after every reboot even with blacklisting google framework and services
Click to expand...
Click to collapse
SafetyNet works till google patched it no matter which xposed clone you use. Before last patch SN was working fine with EdXposed. I don't needed blacklisting framework and services because EdXposed manager is doing automatically, with special option enabled. So don't say lies about EdXposed but tell us about technical differences between LSposed and EdXposed. What you change after forking EdXposed repo?

looks working good u,till now, just its annoying sometimes to have to choos which app has the module applies. a "select all" option would be welcome in a next release

How do I pass safety net? I have universal safety fix module is installed too.

Antho02 said:
looks working good u,till now, just its annoying sometimes to have to choos which app has the module applies. a "select all" option would be welcome in a next release
Click to expand...
Click to collapse
This is what i was confused about? ive never chosen before. I dont know which ones i need things like HiddenCoreModule to apply to? Everything?

It looks like this xposed clone works only in whitelist mode...

I'm quite amazed that this edxposed alternative is running much better than edxposed itself on my android 11, aosp rom, redmi k30 pro zoom. Really glad that I came across this!
Thanks for the great and awesome work devs!

Preparedtobereckless said:
This is what i was confused about? ive never chosen before. I dont know which ones i need things like HiddenCoreModule to apply to? Everything?
Click to expand...
Click to collapse
Apply to System Framework.
Hidden core module do nothing, try no device check module. BTW safetynet passes for me by default.
darashikoh said:
How do I pass safety net? I have universal safety fix module is installed too.
Click to expand...
Click to collapse

What are LSposed module we can use in A11

Im trying to ask the scope list of my modules. Firefds minminguard hiddencore and hide mock location. Anybody can help for the whitelist ??

what does mean: "select other app for each module" ?
for example for "GravitiyBox" module, which app should be enable and why?!

mrhamed said:
what does mean: "select other app for each module" ?
for example for "GravitiyBox" module, which app should be enable and why?!
Click to expand...
Click to collapse
Android System - android
Call - com.samsung.android.incallui
Camera - com.sec.android.app.camera
Contacts - com.samsung.android.contacts
Email - com.samsung.android.email.provider
Firefds Kit - sb.firefds.r.firefdskit
Messaging - com.samsung.android.messaging
MTP Application - com.samsung.android.MtpApplication
NFC - com.android.nfc
One UI Home - com.sec.android.app.launcher
Settings - com.android.settings
Smart Capture - com.samsung.android.app.smartcapture
Software Update - com.wssyncmldm
System UI - com.android.systemui
It also depends on what firmware you are using amd what features you've enabled in gravity box. Enable these according.
What I've enabled in miui are shown in image below.

a module based selection, what to hook seems a good approach of doing what you want and at the same time saving resources. a more advanced selectiin UI would be good. filter based on words and then select in the filtered list, select deselect all. in addition I have no idea what some modules are hooking like gravity box...this is just an example...I know I can find out however maybe the manager app can support to find out or tick what is recommended

I am trying LSposed on my OnePlus 7 Pro (GM-1917), OOS 10.3.8, Magisk 21.4, xXx 12.4.
I followed these instructions from the OP ...
• Install Riru 23+
• Install Riru - LSPosed via Magisk Manager
• Install LSPosed Manager app
• Reboot your device.
Click to expand...
Click to collapse
I got into what seems to be an infinite boot loop. I waited 3-5 minutes, but the boot loop continued.
Has anyone seen this behavior? If so, is there a workaround?
Thank you in advance.
UPDATE: I must have messed up one or more of the installation steps the first time around. I retried installing, and now LSPosed works for me with no boot loop.
OnePlus 7 Pro (GM-1917)
OOS 10.3.8
Magisk 21.4
Magisk Manager 8.0.7
xXx 12.4
Riru 23.4
LSPosed-v0.5.4.0-5135-release.zip (YAHFA)
LSPosedManager-v0.5.4.0-5175-release-signed.apk
Good work!
Onward!

HippoMan said:
I am trying LSposed on my OnePlus 7 Pro (GM-1917), OOS 10.3.8, Magisk 21.4, xXx 12.4.
I followed these instructions from the OP ...
I got into what seems to be an infinite boot loop. I waited 3-5 minutes, but the boot loop continued.
Has anyone seen this behavior? If so, is there a workaround?
Thank you in advance.
Click to expand...
Click to collapse
Working fine with OnePlus 7t latest beta. There might be some other issue. LSPosed doesn't seem to cause bootloop. Share logcat.

Using Software with V-key Components

UPDATE!​NO MORE COMPLICATED SCRIPTS, JUST USE MAGISK 24.1 WITH DENY LIST!
1. Enable Zygisk, add the apps to the deny list
2. Hide Magisk App
3. Install SafetyNet Fix by kdrag0n (Might still need Magisk Hide Props if your device is a little older)
Working on: Poco X3 Pro + Lineage 18.1 (Android 11)
Aurora Store | F-Droid - Free and Open Source Android App Repository
A Google Playstore Client
f-droid.org
^Use aurora store to get the older version of Singapass that's likely to work, I'm using build 100.
V-Key Pte Ltd is basically a IT security technology based in Singapore I suppose.
Some softwares in Singapore, i.e. OCBC Banking, SingPass and maybe some other SEA banking softwares have v-key components which detects magisk.
This is a guide on how to use such softwares with Magisk, because I firmly believe that I get to choose what features I wish to have for my phone, and it is not fair for these banking companies to deny their services just because my device is rooted, I mean, if my banking stuff gets compromised because my phone is rooted and exploited, I'm willing to take the risk.
This guide aims to help mostly Singaporean users or anyone using such softwares with v-key components.
To make things work, the following things must be done:
1. Make sure Magisk manager is hidden
2. Make sure device fingerprint is certified by google (Check out the MagiskHide Props Config module) Please contribute fingerprints to this module for the benefit of everyone, checkout the GitHub page for more details.
3. Add the apps to Magisk Hide list.
4. Use package manager (pm) to disable the following v-key components in terminal (Using POSB Banking App as an example:
pm disable com.dbs.sg.posbmbanking/vkey.android.vos.MgService
pm disable com.dbs.sg.posbmbanking/com.vkey.android.support.permission.VGuardPermissionActivity
pm disable com.dbs.sg.posbmbanking/com.vkey.android.vguard.VGDialogActivity
pm disable com.dbs.sg.posbmbanking/com.vkey.android.internal.vguard.cache.ProcessHttpRequestIntentService
*Some apps may not have one or two v-key components listed above (i.e. SingPass), so getting an error on one or two components being not found should not be a big issue. If things works out you should see out puts on new states being disabled
*Attached a script that deals with OCBC, POSB and SingPass, if you have some weird errors make sure the encoding or format (Not sure of the jargon for it) is Unix or sth and not Windows
Credits:
Reddit User u/Inscythe for giving me a vague idea on the existence of v-key components
Muntashir Akon for his App Manager, allowed me to search for v-key components of apps(tried the disabling features of this app but didn't work, hence the script with pm command)
@Didgeridoohan for MagiskHide Props Config
@vurtomatic for giving me the idea of creating a guide on this.

Hi @Xanth0k1d , thanks for the guide.
I have a rooted LOS 18.1 (OnePlus 3), with magisk 22.1, magisk hide on and magisk manager hidden. All my bank apps work correctly excepts K-PLUS app, the retail bank app from Kasikorn Bank in Thailand.
I can see in the logs of magisk that some vkey components are linked to the app. I followed you guide and was able to disable 2/4 components you listed (2 didn't exist).
Unfortunately this didn't fix the issue.
Do you know how I can search in my phone if other vkey components exist that I might need to disable?
Thanks

Hey @Xanth0k1d, does this still work for you? I noticed that VGuard services are visible with App Manager for DBS but not Government apps. I could disable those services via ADB Root without the use of Magisk just fine.
Seems like GovTech has caught up to this trick :/

erOzeOz said:
Hi @Xanth0k1d , thanks for the guide.
I have a rooted LOS 18.1 (OnePlus 3), with magisk 22.1, magisk hide on and magisk manager hidden. All my bank apps work correctly excepts K-PLUS app, the retail bank app from Kasikorn Bank in Thailand.
I can see in the logs of magisk that some vkey components are linked to the app. I followed you guide and was able to disable 2/4 components you listed (2 didn't exist).
Unfortunately this didn't fix the issue.
Do you know how I can search in my phone if other vkey components exist that I might need to disable?
Thanks
Click to expand...
Click to collapse
Disabling the existing vkey components should be enough.
Did you spoof the device signature with the magisk hideprops module?

KrishvY said:
Hey @Xanth0k1d, does this still work for you? I noticed that VGuard services are visible with App Manager for DBS but not Government apps. I could disable those services via ADB Root without the use of Magisk just fine.
Seems like GovTech has caught up to this trick :/
Click to expand...
Click to collapse
All my apps are working fine, could you please be clear of your problem? i.e. what's working, what's not etc

Xanth0k1d said:
All my apps are working fine, could you please be clear of your problem? i.e. what's working, what's not etc
Click to expand...
Click to collapse
I'm using a OP6, LineageOS 17.1, latest nightly build. I can't use SingPass and Standard Chartered but I can use DBS just fine. I did not root my phone and I don't have Magisk installed either.
I just can't find V-key components in SingPass with App Manager.

KrishvY said:
I'm using a OP6, LineageOS 17.1, latest nightly build. I can't use SingPass and Standard Chartered but I can use DBS just fine. I did not root my phone and I don't have Magisk installed either.
I just can't find V-key components in SingPass with App Manager.
Click to expand...
Click to collapse
The App Mananger by Muntashir Akon?
I think I need to explain this properly, SIngapass and some apps may not work in the following situations:
You installed a custom rom without a Google approved device ID
You rooted your phone
You have Magisk
etc​
For your case, Singpass does not work because you installed Lineage - a custom rom, which should not have a Google approved device prop by default. It doesn't matter if you are rooted or you have install Magisk at this point.
My suggestion to you is to install Magisk and follow my guide-hide magisk and spoof you device fingerprint so it looks like you are running a stock rom.

hi @Xanth0k1d. Have been using your method to hide singpass in the past. But the app just recently was able to detect root. As someone mentioned above, the updated app has no v-key components listed in the service. Any idea how to circumvent the situation and what services to disable?

Holy ****, I just saw the update.
Probably some dude saw this post...
I have yet updated so I can't test, if anyone's finding any solutions to this pls update as well.

Xanth0k1d said:
V-Key Pte Ltd is basically a IT security technology based in Singapore I suppose.
Some softwares in Singapore, i.e. OCBC Banking, SingPass and maybe some other SEA banking softwares have v-key components which detects magisk.
This is a guide on how to use such softwares with Magisk, because I firmly believe that I get to choose what features I wish to have for my phone, and it is not fair for these banking companies to deny their services just because my device is rooted, I mean, if my banking stuff gets compromised because my phone is rooted and exploited, I'm willing to take the risk.
This guide aims to help mostly Singaporean users or anyone using such softwares with v-key components.
To make things work, the following things must be done:
1. Make sure Magisk manager is hidden
2. Make sure device fingerprint is certified by google (Check out the MagiskHide Props Config module) Please contribute fingerprints to this module for the benefit of everyone, checkout the GitHub page for more details.
3. Add the apps to Magisk Hide list.
4. Use package manager (pm) to disable the following v-key components in terminal (Using POSB Banking App as an example:
pm disable com.dbs.sg.posbmbanking/vkey.android.vos.MgService
pm disable com.dbs.sg.posbmbanking/com.vkey.android.support.permission.VGuardPermissionActivity
pm disable com.dbs.sg.posbmbanking/com.vkey.android.vguard.VGDialogActivity
pm disable com.dbs.sg.posbmbanking/com.vkey.android.internal.vguard.cache.ProcessHttpRequestIntentService
*Some apps may not have one or two v-key components listed above (i.e. SingPass), so getting an error on one or two components being not found should not be a big issue. If things works out you should see out puts on new states being disabled
*Attached a script that deals with OCBC, POSB and SingPass, if you have some weird errors make sure the encoding or format (Not sure of the jargon for it) is Unix or sth and not Windows
Credits:
Reddit User u/Inscythe for giving me a vague idea on the existence of v-key components
Muntashir Akon for his App Manager, allowed me to search for v-key components of apps(tried the disabling features of this app but didn't work, hence the script with pm command)
@Didgeridoohan for MagiskHide Props Config
@vurtomatic for giving me the idea of creating a guide on this.
Click to expand...
Click to collapse
heya, I'm the reddit user... I had updated the app, but so far has no luck finding where the detection is hiding now... I might just try turning off services one-by-one with servicely, but I'll keep you all updated if I get any success.

@Xanth0k1d since you haven't updated your singpass, can you check what are the available services and listeners currently your version is using? I want to compare the difference with the latest version.

I managed to get Singapore's GPay app to work by blocking this `com.google.android.gms.gmscompliance.ui.UncertifiedDeviceActivity`. Do your devices pass SafetyNet?

The recent Singpass update requires disabling o.InvalidRegistrarException for root detection to be circumvented.

stevenkyk said:
The recent Singpass update requires disabling o.InvalidRegistrarException for root detection to be circumvented.
Click to expand...
Click to collapse
Thanks! Can confirm that this works!

Singpass is a really weird app.
Recently google nuke the api so magisk stopped working, can't pass the safetynet. Magisk released a canary release that fix that.
Yet, singpass continue to stop working so I thought maybe I need do more? Then I coincidently force stop the app to run it again, it magically working again! That is after I reboot twice before that. So now I learn the rebooting and force stop do different things.
I didn't apply anything from this thread, it is really a weird app.

Lu5ck said:
Singpass is a really weird app.
Recently google nuke the api so magisk stopped working, can't pass the safetynet. Magisk released a canary release that fix that.
Yet, singpass continue to stop working so I thought maybe I need do more? Then I coincidently force stop the app to run it again, it magically working again! That is after I reboot twice before that. So now I learn the rebooting and force stop do different things.
I didn't apply anything from this thread, it is really a weird app.
Click to expand...
Click to collapse
The safetynet api did not get nuked, the api changed so code that use the old api won't work, even on the latest stable build safetynet will still pass when using another checker app. While I won't go into the technical details, singpass spawns a new isolated process to check for root, exploiting the fact that isolated processes are treated differently and is difficult for magisk to hide itself. So the solution is to disable the offending process and not let it spawn. There are several other requirements necessary for singpass to run, which are largely beyond the scope of discussion in this thread.

Any idea how to bypass Citibank sg root detection? I am able to use vkey method for posb and ocbc but Citibank doesn't have a vkey service

auggie246 said:
Any idea how to bypass Citibank sg root detection? I am able to use vkey method for posb and ocbc but Citibank doesn't have a vkey service
Click to expand...
Click to collapse
The trick here is to decompile the APK using apktool and inspect the Androidmanifest.xml manually. Search for "ISOLATED" and in the same line you should be able to find the name of the service to be disabled. Of course this assumes that citibank's app used a similar tactic as the other apps.
Edit: I tried the citibank sg app, magisk hide + rename package is sufficient for me to launch the app, don't have an account so I can't test any further.

stevenkyk said:
The recent Singpass update requires disabling o.InvalidRegistrarException for root detection to be circumvented.
Click to expand...
Click to collapse
I guess there's another update to Singpass that circumvent this circumvention as well lol

Apparently it's now using a service called o.ImmutableSetMultimap for checking root (confirmed by magiskhide entry) and it works for a few seconds after loading Singpass before failing again with different error message. I think it checks for both whether the service is active and found a root (gives error T0), or whether the service is running at all (gives error T-1). I think we need something else to block this.

What is the go-to replacement for MagiskHide & the central module repo?

I just realized there was a new public Magisk release yesterday, v24, and reading through the changes I see there are two that kind of impact me: MagiskHide and the central module repository removals.
So far I had been using MagiskHide because of its ease of use, list apps, tick box, and that's it (I haven't encountered apps that detected Magisk or root status, although I know it's insufficient for some). For modules, for example, the one that moves user certs to the system store, I just searched directly from the Magisk app and it was all good as well.
But things change from now on with those things being deprecated and removed and because there isn't much to go about in the release notes I was wondering if someone could direct me to the way of doing things now.
- What's the most apt, prevalent, or recommended replacement for MagiskHide? From the release notes I gather its a module, but I'm clueless as to which one or whether there are more than one option.
- If searching for mods and directly installing them is not available through the app, is there anything like it? Or is it all manual now? I.e. look for a module around the net, download it, copy it / decompress it somewhere in the device and install it.
Thanks for everything!

KaoDome said:
I just realized there was a new public Magisk release yesterday, v24, and reading through the changes I see there are two that kind of impact me: MagiskHide and the central module repository removals.
So far I had been using MagiskHide because of its ease of use, list apps, tick box, and that's it (I haven't encountered apps that detected Magisk or root status, although I know it's insufficient for some). For modules, for example, the one that moves user certs to the system store, I just searched directly from the Magisk app and it was all good as well.
But things change from now on with those things being deprecated and removed and because there isn't much to go about in the release notes I was wondering if someone could direct me to the way of doing things now.
- What's the most apt, prevalent, or recommended replacement for MagiskHide? From the release notes I gather its a module, but I'm clueless as to which one or whether there are more than one option.
- If searching for mods and directly installing them is not available through the app, is there anything like it? Or is it all manual now? I.e. look for a module around the net, download it, copy it / decompress it somewhere in the device and install it.
Thanks for everything!
Click to expand...
Click to collapse
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Here. First 5 post and you should know all you need

So, I read through that thread. It certainly solved a few issues for me. Like getting safety net, getting a repository, etc.
But it didn't have anything I see to replace magisk hide, even in the Fox Magisk Module Manager.
Do I just need to know other terminology now? Or is there something else I'm missing?

Quantumrabbit said:
So, I read through that thread. It certainly solved a few issues for me. Like getting safety net, getting a repository, etc.
But it didn't have anything I see to replace magisk hide, even in the Fox Magisk Module Manager.
Do I just need to know other terminology now? Or is there something else I'm missing?
Click to expand...
Click to collapse
I don't get it, Magisk Hide is good for passing SafetyNet and you said you got it. Anyway, for SafetyNet you can use the Universal SafetyNet Fix module.
If you meant the hide list, there's now the Deny list. To quote:
The Deny list is similar but instead of hiding Magisk from the process, Magisk is unloaded so there is nothing to hide.
Click to expand...
Click to collapse

Porpet said:
I don't get it, Magisk Hide is good for passing SafetyNet and you said you got it. Anyway, for SafetyNet you can use the Universal SafetyNet Fix module.
If you meant the hide list, there's now the Deny list. To quote:
Click to expand...
Click to collapse
Yes, it's for some banking apps, Concur, and others, none of which have any business checking for root, but all check for Magisk and such in other ways, and prevent usage.
If the deny list is how to do that now, I'll give that a go. Thank you

Quantumrabbit said:
Yes, it's for some banking apps, Concur, and others, none of which have any business checking for root, but all check for Magisk and such in other ways, and prevent usage.
If the deny list is how to do that now, I'll give that a go. Thank you
Click to expand...
Click to collapse
And where did you find the deny list?

fusk said:
And where did you find the deny list?
Click to expand...
Click to collapse
Settings enforce deny list. You need to enable zygisk and reboot prior also in settings.
Also there is an add on module shamiko that has more hide features after you configure denylist

H
toolhas4degrees said:
Settings enforce deny list. You need to enable zygisk and reboot prior also in settings.
Also there is an add on module shamiko that has more hide features after you configure denylist
Click to expand...
Click to collapse
How to add modules shamiko & how to more hide features

Spartacus500 said:
H
How to add modules shamiko & how to more hide features
Click to expand...
Click to collapse
Shamiko is a flashable only need to slash magisk module. You can find it in the magisk alpha thread on telegram. You need to configure denylist first and reboot then turn off the enforce denylist toggle and flash the shamiko module.
If you are using lsposed download hide my applist xposed module and search how to use it if you want more coverage
Pm me if you want links

I'm having a lot of trouble. Duo Mobile (a 2FA app) is still able to detect that I'm rooted. Here's what I've done:
1) Installed Magisk & Manager app version 24.1 (24100)
2) Enabled Zygisk (and rebooted of course)
3) Enabled Enforce DenyList
4) Added com.duosecurity.duomobile and ALL Google Play Services submodules to the DenyList
5) Installed Universal SafetyNet Fix v2.2.1 from https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.2.1
6) Hidden the Magisk app
7) Completely uninstalled & reinstalled Duo Mobile (and verified that it's still on the DenyList
This is incredibly annoying, is there anything I'm doing wrong? Is there a way to verify that the SafetyNet Fix is working as expected? Magisk doesn't have a "Check SafetyNet" option on the app anymore.

Drakinite said:
I'm having a lot of trouble. Duo Mobile (a 2FA app) is still able to detect that I'm rooted. Here's what I've done:
1) Installed Magisk & Manager app version 24.1 (24100)
2) Enabled Zygisk (and rebooted of course)
3) Enabled Enforce DenyList
4) Added com.duosecurity.duomobile and ALL Google Play Services submodules to the DenyList
5) Installed Universal SafetyNet Fix v2.2.1 from https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.2.1
6) Hidden the Magisk app
7) Completely uninstalled & reinstalled Duo Mobile (and verified that it's still on the DenyList
This is incredibly annoying, is there anything I'm doing wrong? Is there a way to verify that the SafetyNet Fix is working as expected? Magisk doesn't have a "Check SafetyNet" option on the app anymore.
Click to expand...
Click to collapse
This is quite weird and definitely shows how different devices handle root detection. I a Samsung S10+ and just installed Magisk 24 with enforce DenyList earlier this week. Today I just installed Duo Mobile and it works fine. I do not have it in the DenyList, and Magisk is not hidden. I use a custom SafetyNet fix that was installed when I originally installed an AIO TWRP/Magisk/SafetyNet fix after unlocking my bootloader. I also fail SafetyNet checks.
Have you tried Shamiko? It didn't help me pass SafetyNet so I removed it.
Unfortunately I don't have any other fixes for you but you can check SafetyNet with apps from the play store, I use YASNAC and SafetyNet 'attest'.
What phone are you using?

Drakinite said:
This is incredibly annoying, is there anything I'm doing wrong? Is there a way to verify that the SafetyNet Fix is working as expected? Magisk doesn't have a "Check SafetyNet" option on the app anymore.
Click to expand...
Click to collapse
There are SafetyNet checker apps you can download from the Play Store or F-Droid such as YASNAC.

danbest82 said:
Have you tried Shamiko? It didn't help me pass SafetyNet so I removed it.
Unfortunately I don't have any other fixes for you but you can check SafetyNet with apps from the play store, I use YASNAC and SafetyNet 'attest'.
What phone are you using?
Click to expand...
Click to collapse
I'm using a Oneplus 6. At your suggestion, I tried Shamiko, but so far it hasn't worked.
anonymous-bot said:
There are SafetyNet checker apps you can download from the Play Store or F-Droid such as YASNAC.
Click to expand...
Click to collapse
I tried Momo from the Magisk alpha telegram channel, and it's been helpful so far, but it's detecting Magisk/TWRP files and I don't know where they are located. Is there a way to find where these files it's detecting are? This might be what Duo is detecting.
When I run YASNAC, it passes the SafetyNet check.

Drakinite said:
I'm using a Oneplus 6. At your suggestion, I tried Shamiko, but so far it hasn't worked.
I tried Momo from the Magisk alpha telegram channel, and it's been helpful so far, but it's detecting Magisk/TWRP files and I don't know where they are located. Is there a way to find where these files it's detecting are? This might be what Duo is detecting.
When I run YASNAC, it passes the SafetyNet check.
Click to expand...
Click to collapse
Get VD Infos and use it to scan your files. You can find it on XDA.

Drakinite said:
I'm using a Oneplus 6. At your suggestion, I tried Shamiko, but so far it hasn't worked.
Click to expand...
Click to collapse
Hmm ok. Like I said shimako didn't work for me either. I'm not sure why Duo is still detecting root. For reference this is what is on my DenyList:
Drakinite said:
I tried Momo from the Magisk alpha telegram channel, and it's been helpful so far, but it's detecting Magisk/TWRP files and I don't know where they are located. Is there a way to find where these files it's detecting are? This might be what Duo is detecting.
When I run YASNAC, it passes the SafetyNet check.
Click to expand...
Click to collapse
YASNAC is the replacement for Momo it looks like since Momo is Riru based (https://github.com/canyie/Riru-MomoHider)

simplydat said:
Get VD Infos and use use to scan your files. You can find it in XDA
Click to expand...
Click to collapse
Ok so this one is more helpful, but I'm not sure how to hide these that appeared. Any idea what ro.kernel.qemu.gles is? I looked through my list of installed apps and nothing like that showed up.
Should we switch to private messages to not spam the thread? Or perhaps staying in here can be helpful for those with the same problem?

Drakinite said:
Ok so this one is more helpful, but I'm not sure how to hide these that appeared. Any idea what ro.kernel.qemu.gles is? I looked through my list of installed apps and nothing like that showed up.
Should we switch to private messages to not spam the thread? Or perhaps staying in here can be helpful for those with the same problem?
Click to expand...
Click to collapse
OMG WAIT, it finally worked! I don't know what changed, but Duo is now no longer detecting root. Gotta love when things magically start working when you don't know what changed.

Drakinite said:
OMG WAIT, it finally worked! I don't know what changed, but Duo is now no longer detecting root. Gotta love when things magically start working when you don't know what changed.
Click to expand...
Click to collapse
Awesome. Hope it stays that way!

Hi,
I've switched to the new method with the DenyList & Shamiko (v0.5.0) on OnePlus 6 recently - Magisk (v24.3), however it doesn't seem to hide root from Google Pay. Can it still be a bug with Magisk, when it can't hide system apps? In the changelog of Shamiko it mentioned that it was fixed in Magisk "24102+", I'm not sure what version is this, but I imagine it's not released yet. If so, is there a way of installing this version early?
Thank you!

antivirtel said:
Hi,
I've switched to the new method with the DenyList & Shamiko (v0.5.0) on OnePlus 6 recently - Magisk (v24.3), however it doesn't seem to hide root from Google Pay. Can it still be a bug with Magisk, when it can't hide system apps? In the changelog of Shamiko it mentioned that it was fixed in Magisk "24102+", I'm not sure what version is this, but I imagine it's not released yet. If so, is there a way of installing this version early?
Thank you!
Click to expand...
Click to collapse
Version 24102 would be v24.102. So your Magisk 24.300 is newer.