yashsingh1/xdaforums huggingface dataset:
[Magisk] erOzeOz:
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
[Magisk] KrishvY:
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 :/
[Magisk] Xanth0k1d:
Disabling the existing vkey components should be enough.

Did you spoof the device signature with the magisk hideprops module?
[Magisk] Xanth0k1d:
All my apps are working fine, could you please be clear of your problem? i.e. what's working, what's not etc
[Magisk] KrishvY:
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.
[Magisk] Xanth0k1d:
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.
[Magisk] dearestk:
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?
[Magisk] Xanth0k1d:
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.
[Magisk] inscythe:
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.
[Magisk] inscythe:
@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.
[Magisk] KrishvY:
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?
[Magisk] stevenkyk:
The recent Singpass update requires disabling o.InvalidRegistrarException for root detection to be circumvented.
[Magisk] inscythe:
Thanks! Can confirm that this works!
[Magisk] Lu5ck:
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.
[Magisk] stevenkyk:
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.
[Magisk] auggie246:
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
[Magisk] stevenkyk:
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.
[Magisk] inscythe:
I guess there's another update to Singpass that circumvent this circumvention as well lol
[Magisk] inscythe:
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.
[Magisk] Lu5ck:
Idk about him. Now i am using magisk delta, universal safetynet mod 1.2 and singpass 16.2.1

I also use detach magisk to disable auto update on singpass, while able to auto update other apps
[Magisk] wyt18:
thanks. I'm on 16.2.1 too, along with USNF mod 1.2, but magisk official 25.2. Singpass detects root with this setup and it must be the magisk (though even when I freeze the magisk app it still happens)

can't use delta because I need lsposed/zygisk. do you use xposed at all, or is there a workaround for it on delta?
[Magisk] Lu5ck:
If you use official magisk, then you need install the GitHub latest shamiko.
[Magisk] wyt18:
Yes I already have shamiko v0.6 but still gets detected by Singpass
[Magisk] Lu5ck:
Does your device able to use singpass without magisk?
[Magisk] wyt18:
You mean w/o rooting? I've always been rooted so have not tried recently, but I can imagine there would be no issues running Singpass w/o root

I used to run Singpass v12 without issues alongside Magisk by disabling certain services and providers using App Manager. The same services don't appear in v16. But despite trial and error disabling each service, Singpass still doesn't work
[Magisk] Lu5ck:
Try magisk alpha and the latest shamiko in alpha telegram
[Magisk] wyt18:
Thanks. Does this work with lsposed?
[Magisk] Lu5ck:
Is by the same author
[Magisk] wyt18:
It seems like on Magisk Alpha, one can only choose MagiskHide or Zygisk/Lsposed modes of operation. And it needs a reboot when changing modes

So either Banking apps / Singpass will work, or Google Pay (which relies on SafetyNet) will work, not both at the same time

Any ways to work around this?
[Magisk] Lu5ck:
Idk, I use magisk delta and a older version of singpass.

My past experience with alpha is just zygisk + shamiko (latest from their alpha telegram) + unviersal safetynet fix (modded) and it runs.

Some magisk addons will expose magisk, addons that add extra files via kernelsu, addons like revanced installed via root, some modded camera installed via magisk etc.
[Magisk] wyt18:
Do you use 16.2.1?

12.x used to work for me until two months ago. Now all versions earlier then 16.2.1 force me to update
[Magisk] dogplutoeggavalanche:
Does anyone know how to get around the error? I am running into it recently and have tried Magisk's Deny List but it still doesn't work.
[Magisk] Lu5ck:
Now I use the latest singpass 18.2.1 with latest magisk alpha and latest shamiko.

The dev now seems to be using singpass detection as primary standard to bypass, given their magisk detector they released is based on singpass.
[Magisk] wyt18:
Tried this version too but getting detected (latest shamiko, magisk delta). What sort of detection are they using?
[Magisk] doclucas:
Magisk alpha? Do you mean canary (26103)?
[Magisk] Lu5ck:
Is Alpha, not Delta or canary. Canary is official test version. Alpha is a fork by another devs. Delta dev went back to school thus no longer have time to update

To download alpha, gotta go their telegram. Same for shamiko which is also made by alpha devs. Latest shamiko only works on alpha.

Alpha devs released a Neo Native Detector test, which also available on the same alpha telegram. It is based on Singpass since it has the singpass app ID in it. lol.

Then Real Nullptr, another dev, released an updated version of Native Detector.

t.me/magiskalpha

t.me/nullptr_dev
[Magisk] mrfattyboomz:
Hey bro i tried this magisk Alpha 26103 Shamiko 0.7.3. Added Singpass to denylist. Still doesnt work.

Then i ran the minator detector you posted above it detects injection leh. Does yours show the same?Hey bro i tried this magisk Alpha
[Magisk] doclucas:
Yeah, I am having the same issue. The detector (Native Test, pink icon) says

"Neo Minotaur (12)

Found Injection

Abnormal Environment

Property Modified"

Using:

Galaxy Note 10+ (N975F)

Magisk Alpha 26103 (hidden)

Shamiko 0.7.3

Universal Safety Net 2.4.0-MOD_1.3 (Displax)

Zygisk-LSPosed

Settings:

Zygisk enabled obviously,

Enforce DenyList disabled,

All relevant apps (including the detector) and all their toggles enabled on the DenyList

Am I doing something wrong?
[Magisk] mrfattyboomz:
Same as me. Not sure if it's the version of alpha. The dude above said latest but his post was jun 29 so he prob using older ver.

I even have hidemyapp but same outcome
[Magisk] Lu5ck:
I using alpha 26104, I didn't hide the alpha app.

The loaded module is Shamiko 0.7.3, I never use USN, doesn't seem to be of any use on my phone, I am using poco x3 pro custom rom crdroid.

I deny singpass and all google related apps and services.

I also naturally deny the banks apps etc.

My current singpass version is 19.0.0

I also got detected on latest neo but no issue running singpass.
[Magisk] mrfattyboomz:
If you could share your denylist it would be great. I'm essentially have everything the same except that i have USN. Not sure if USN is the issue.
[Magisk] mrfattyboomz:
thanks bro..did the same but i guess there is something else it detects. unsure what haha. it usually says unlocked bootloader
[Magisk] Lu5ck:
try

GitHub - Magisk-Modules-Alt-Repo/sensitive_props: Reset sensitive properties to safe state, take from MagiskHide code

Reset sensitive properties to safe state, take from MagiskHide code - Magisk-Modules-Alt-Repo/sensitive_props

github.com

Some phones seems to need this

Just to double check, make sure to disable enforce denylist

Also, if coming from another magisk, make sure to flash the magisk boot image properly, like use the base rom boot image to be patched with
[Magisk] mrfattyboomz:
Hmm actually I think this could be it. I didn't flash new boot image. I came from original magisk n just flashed to alpha via import as zip.

Probably alpha patches the boot img in a special way that prevents singpass detection.
[Magisk] wingatecrescent:
So the consensus at this moment is that Singpass can't be tricked as of now?

I went back to my Galaxy Note 7 FE recently (stock rom rooted with Magisk) and I finally got a German banking app to work again. I'm abit out of my depth here so I spent days looking for a solution and I still don't know if what I'm doing is correct:

Galaxy Note 7 FE (SM-N935F)

Magisk 26100 (Hidden)

Universal Safetynet-fix-v1.1.1-a50mod-v2-rvdekoff

Zygisk is listed as 'no' in the Magisk homepage.

(According to YASNAC Basic Integrity and CTS profile match are both failed)

Settings:

Zygisk enabled

Enforce DenyList enabled

Denylist: Google Play Store, Play Services, the banking app and Singpass.

The thing is, prior to the a50mod, my Universal Safety Net module said "Module is suspended because Zygisk is not enabled" Now it's fine. The German banking app that I couldn't use before (because root was detected) is working. So I don't really understand.

I live in Europe and have to check official gov notices w Singpass from time to time. At the moment I use my husband's non-rooted phone for it. I have an S9 knocking around somewhere (needs a new screen) but it's rooted as well unfortunately. Any help would be appreciated.
[Magisk] doclucas:
Try replacing your Magisk with Magisk Alpha and install Universal Safetynet-fix by Displax (v2.4.0-MOD_2.0 or mod 1.3)

Be sure to clear your Play Store and Play services data. including dual apps play services data, if available.

Also make sure you do not have Lucky Patcher installed and no traces/patches of it, otherwise you may need to wipe your phone and reinstall everything and start installing your root stuff and trial and error until it fails, so you know what causes it.

Edit: Of course enable Zygisk and install the latest Shamiko and hide any relevant apps in Magisk Alpha (no enforce enabled when using Shamiko)
[Magisk] Lu5ck:
You can use delta as well with zygisk disabled, basically in magiskhide mode which also means you don't need shamiko. It seems to hide root better than zygisk.
[Magisk] EmpressIn5:
Hey everyone, I'm relatively new to all the terminologies used in the entire thread and am still not sure as to what to do. I am running a Samsung S22, and the version of Magisk I am running is 26.1.

I can't seem to get UOB TMRW (with the latest update) or Singpass to work. Could someone guide me with a step-by-step? Also, is there an all-in-one method for all apps? I'm scared that future apps may detect root as well. Thanks in advance!
[Magisk] doclucas:
I got uob tmrw sg working fine here. Follow my post above regarding magisk alpha.
[Magisk] EmpressIn5:
Could you link the post? I'm unable to find it
[Magisk] doclucas:
Come on, a bit of effort...August 22nd, a few posts before this.
[Magisk] mrfattyboomz:
Ok so magisk alpha method so far works for all Apps except SingPass for me. This could be because i did not flash boot.img using magisk alpha but instead just installed it via Zip method over the original magisk.

For magisk delta i read their thread alot of people has issues here and there in regards to other stuff. Not sure if i want to try or switch to it. Wish i had a spare phone to test out :(
[Magisk] EmpressIn5:
I found the post.

I uninstalled the main Magisk app and downloaded Magisk Alpha. However, it doesn't seem to recognize that my device is rooted.

I have to "Select and Patch a File" but I'm not sure what to do next
[Magisk] doclucas:
I have no idea about Galaxy S22, but if it's the same as my Galaxy Note 10+, then you must not root your phone this way, but use a patched kernel to root it (in my case I personally compiled a kernel with magisk alpha and flashed it).

You may want to research what's the way to properly root it with magisk alpha.
[Magisk] EmpressIn5:
I'm unable to find any guides with the S22, so I'm assuming its going to be the same method. How do you go about patching the kernel, then compiling it, and then flashing it?

After that, will all my data be lost?
[Magisk] Lu5ck:
The latest singpass 19.1 is able to detect root, at least for me. I recommend using 19.02 which you can download from apkpure and disable auto update.

Some bank app also start using zimperium which also detect root. ATM, I am using magisk delta with zygisk disabled and able to hide root from zimperium well.

I haven't try using KernelSU which is alternative of Magisk.
[Magisk] EmpressIn5:
How do I use Magisk Delta? Could you provide a step-by-step guide? (Would this also be the same method to use for Magisk Alpha?) I'm lost on where to start and all. Thanks in advance!
[Magisk] Lu5ck:
Install Magisk Delta

Get boot.img from your rom

Patch the boot.img in magisk delta app

Flash the patched boot.img in recovery

Disable Zygisk in magik delta

Enable unmount

Enable unmount globally if you want to do whitelist style aka select which app to have root access instead of typical deny root access

Clear cache / data of magisk delta (there seems to be a boot loop bug if don't do that)

Reboot

Now check if unmount is enabled

Add your rooted or deny root apps into it

Reboot

If there's an delta update, you need to do 3 then do 8 then do 4.
[Magisk] doclucas:
Seems to be working fine with magisk alpha. Zygisk and shamiko. I'm not sg so can't login but it loads fine and I can pass all the set up pages until reaching the website.
[Magisk] Lu5ck:
I have compiled KernelSU based off my custom rom kernel source. Latest singpass simply crash when trying to run it, I guess it is trying to access more permissions than typical apps, maybe using some kind of exploits to do so. I haven't test what permissions it trying to access, KernelSU just has so much permissions you can fine tune for each individual app.
[Magisk] doclucas:
Again, you may wanna check magisk Alpha out...
[Magisk] mrfattyboomz:
bro u not sian keep flash your phone? AHAH coz when u switch from alpha to delta gota flash. then if we switch to kernelSU also needa flash.

Also i heard kernelSU would be the best option to totaly solve any sort of detection. Not too sure of the mechanics tbh
[Magisk] Lu5ck:
Bo bian, some apps works some apps don't

I like Delta because of the whitelist

This cat and mouse game very jialat

KernelSU need to flash custom kernel that support it, I compiled my own kernel based on my rom kernel with github action compiler. I can't use other custom kernel because my rom has integrated miui camera app via some kernel hacks

But latest singpass also crash on KernelSU, I suspect singpass is doing shady things like malwares or my compiled kernelsu got problem as I didn't compile it with kprobe. /shrug

Got time then test, for now sticking to 19.02
[Magisk] EmpressIn5:
Looks like the latest DBS PayLah update is detecting root...
[Magisk] doclucas:
True.

DBS is now using zimperium... Hopefully someone can find a way around it.
[Magisk] edjocute:
Did some testing on my spare phone with KernelSU.

Singpass 19.1 works somewhat with KernelSU (Zygisk, Shamiko and LSPosed installed). However, it detects the systemless hosts module for adaway so an alternative module is needed.

Paylah detects Shamiko, but not Zygisk or LSPosed.

HSBC detects LSposed (6990), but not Zygisk.

All three work with plain KernelSU (no Zygisk, Shamiko and LSPosed).
[Magisk] doclucas:
I've tested DBS on my rooted xiaomi and it works fine there with Alpha, but fails on my Samsung. Had a look with app manager and found zimperium got something called Knox license receiver (Knox is exclusive to samsung), which I guess failed, as Knox fuse gets tripped when unlocking the bl, that's irreversible.
[Magisk] Lu5ck:
My singpass 9.1 for kernelsu got this error

09-23 02:23:52.685 28684 28684 D AndroidRuntime: Shutting down VM
09-23 02:23:52.685 28684 28684 E AndroidRuntime: FATAL EXCEPTION: main
09-23 02:23:52.685 28684 28684 E AndroidRuntime: Process: sg.ndi.sp, PID: 28684
09-23 02:23:52.685 28684 28684 E AndroidRuntime: java.lang.SecurityException: Not allowed to bind to service Intent { cmp=sg.ndi.sp/o.btX }
09-23 02:23:52.685 28684 28684 E AndroidRuntime: at android.app.ContextImpl.bindServiceCommon(ContextImpl.java:2040)
09-23 02:23:52.685 28684 28684 E AndroidRuntime: at android.app.ContextImpl.bindService(ContextImpl.java:1951)
09-23 02:23:52.685 28684 28684 E AndroidRuntime: at android.content.ContextWrapper.bindService(ContextWrapper.java:853)
09-23 02:23:52.685 28684 28684 E AndroidRuntime: at android.content.ContextWrapper.bindService(ContextWrapper.java:853)
09-23 02:23:52.685 28684 28684 E AndroidRuntime: at o.bpY.onStart(SourceFile:124)
09-23 02:23:52.685 28684 28684 E AndroidRuntime: at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1549)
09-23 02:23:52.685 28684 28684 E AndroidRuntime: at android.app.Activity.performStart(Activity.java:8385)
09-23 02:23:52.685 28684 28684 E AndroidRuntime: at android.app.ActivityThread.handleStartActivity(ActivityThread.java:3680)
09-23 02:23:52.685 28684 28684 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.performLifecycleSequence(TransactionExecutor.java:224)
09-23 02:23:52.685 28684 28684 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.cycleToPath(TransactionExecutor.java:204)
09-23 02:23:52.685 28684 28684 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
09-23 02:23:52.685 28684 28684 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
09-23 02:23:52.685 28684 28684 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2308)
09-23 02:23:52.685 28684 28684 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
09-23 02:23:52.685 28684 28684 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201)
09-23 02:23:52.685 28684 28684 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
09-23 02:23:52.685 28684 28684 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7936)
09-23 02:23:52.685 28684 28684 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
09-23 02:23:52.685 28684 28684 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
09-23 02:23:52.685 28684 28684 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:854)

EDIT: Nvm,, 19.1 simply bugged for my rom. No root also got this error. Apparently o.btX (remote process) didn't declare its intent thus blocked. Only singpass can fix this I think.
[Magisk] mrfattyboomz:
Seems like kernelSU is the way to go but we' sacrificing everything else not being able to use lsposed and zygisk esp.

Tbh at this junction, having a seperate phone just for banking apps makes more sense and less headache.

Also! It's safer with the amnt of scams and **** happening
[Magisk] Lu5ck:
For KernelSU systemless host, there was a older method where it uses "mount --bind" which works where bank apps won't detect but break safetynet, lol.

⁧ Sebi in KernelSU Group

t.me
[Magisk] doclucas:
Regarding Knox devices (Samsung) and the new Zimperium root detection.

There is a github issue with more details in the KnoxPatch repo:

[Feature request] Extend support to banking apps using Zimperium · Issue #52 · salvogiangri/KnoxPatch

Device name: Galaxy Note 10 Plus Device model number: SM-N975F OS version: Android 12 Software info: Any Magisk/KernelSU version: 26301 (Magisk Alpha) Hook framework app: LSPosed 1.9.1 (6990) KnoxP...

github.com
[Magisk] Lu5ck:
Zimperium also detect on my Poco X3 Pro the last I have checked. Running without Zygisk aka MagiskHide mode works though, I am not sure about Singpass. Have you tried shamiko-alpha yet?
[Magisk] kutysam:
For paylah, just disable developer options
[Magisk] iceddeath:
am using magisk alpha +shamiko + lsposed + hma.

can finally hide from DBS Paylah.

but CPF still having issue
[Magisk] Warrenator:
Dear Guru, Recently I have purchase latest Oneplus 12 from China store flashed to Oxygen OS instead of China Colour OS.

I have 0 issues with all local bank application , but when come to authenticate Singapass (version 21) on my phone, after face verification, I always stuck with Error Code 82-T991.

I am totally helpless, as I cannot login to Singpass, I cannot login to all my digibank such as Trust Bank & GXS.

Calling to helpdesk and email to support is completely useless as they dont even know what is going on.

Appreciate there are some guru here able to advice and resolve my issue

Thank you
[Magisk] wyt18:
First time using Singpass in a few weeks, and today upon startup, it redirected me to a webpage that says my device is rooted, then force closes

Am on Magisk 27.0 + Shamiko + Lsposed + HMA + PIF. Anyone able to get around the latest restrictions?