Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Singpass 19.2 detected KSU #991

Closed
Lu5ck opened this issue Sep 27, 2023 · 17 comments
Closed

Singpass 19.2 detected KSU #991

Lu5ck opened this issue Sep 27, 2023 · 17 comments

Comments

@Lu5ck
Copy link

Lu5ck commented Sep 27, 2023

Describe the bug
Singpass 19.2 detected KSU

To Reproduce
Steps to reproduce the behavior:

  1. https://play.google.com/store/apps/details?id=sg.ndi.sp
  2. Run the app
  3. Got detected

Expected behavior
Not detected

Smartphone (please complete the following information):

Additional context

  • I have no other module installed, just KSU and it got detected.
  • Uninstalling KSU manager and Lucky Patcher doesn't help so I assume is not detecting app list.
  • Uninstall KSU aka flashing back to stock kernel will allow the app to launch. I have manager installed at this point so I assume is not about app list.

PS: I cannot join the KernelSU telegram group too! The bot does not respond to /start!! Please fix.

@tiann
Copy link
Owner

tiann commented Sep 27, 2023

How about flash a custom kernel without KernelSU?

@Lu5ck
Copy link
Author

Lu5ck commented Sep 27, 2023

I flash this NetHunter Kernel which does not have KernelSU, can run singpass 19.2

I flash this No Gravity Kernel which has KSU 11210, singpass 19.2 detected root too.

My self compiled is KSU 11238

@Ardjlon
Copy link

Ardjlon commented Sep 27, 2023

Any screenshot? I already have my kernel with KSU, and when open the app I can login, but i dont have account, idk if happen after login...

@Lu5ck
Copy link
Author

Lu5ck commented Sep 27, 2023

Any screenshot? I already have my kernel with KSU, and when open the app I can login, but i dont have account, idk if happen after login...

No, no need for an account, just tried it by clearing data and cache.

Screenshot_20230928-014148_crDroid Home.png

Are you running any modules? I tried with zero modules.

I am using non-gki, integrated manually with hooks, following the instructions at here. Maybe missing some hooks?

Screenshot_20230928-021406_crDroid Home.png

@Ardjlon
Copy link

Ardjlon commented Sep 27, 2023

Any screenshot? I already have my kernel with KSU, and when open the app I can login, but i dont have account, idk if happen after login...

No, no need for an account, just tried it by clearing data and cache.

Screenshot_20230928-014148_crDroid Home.png

Are you running any modules? I tried with zero modules.

I am using non-gki, integrated manually with hooks, following the instructions at here. Maybe missing some hooks?

Screenshot_20230928-021406_crDroid Home.png

Not here, I dont use modules, I can see the login options and I have not had any blocks, maybe an app on your list? I have problems with a banking app that closes when it detects MT explorer or ApkMod, among others.

Although I don't understand how it detected root for you from the browser

@Lu5ck
Copy link
Author

Lu5ck commented Sep 27, 2023

The app opens a website for the deny page while the app closes, that's how it works.

I have tried uninstall root related apps but still detected root.
When I uninstall KSU by flashing back to stock kernel, even with those root apps installed, singpass will run so I doubt is detecting apps.

Are you using kprobe ksu or manual ksu? And what kernel version?

@belinux
Copy link

belinux commented Sep 27, 2023

I can confirm, I tested the app on a Pixel 7 Pro and it's detecting root..

@Ardjlon
Copy link

Ardjlon commented Sep 27, 2023

Right now I getting warning...
photo_2023-09-27_16-43-59

But

photo_2023-09-27_16-44-00

Manual KSU

@tiann
Copy link
Owner

tiann commented Sep 28, 2023

I have identified the cause. Before I commit the fix, you can temporarily solve it like this:

rm /data/adb/ksu/modules*.img

And then reboot.

@Lu5ck
Copy link
Author

Lu5ck commented Sep 28, 2023

I have identified the cause. Before I commit the fix, you can temporarily solve it like this:

rm /data/adb/ksu/modules*.img

And then reboot.

That works. Thank you!

@ljlVink

This comment was marked as off-topic.

@HuskyDG
Copy link
Contributor

HuskyDG commented Sep 30, 2023

It detects the mountpoint of /data/adb/modules because kernelsu will not unmount it for kernel lower than 5.10

@backslashxx
Copy link
Contributor

It detects the mountpoint of /data/adb/modules because kernelsu will not unmount it for kernel lower than 5.10

So what youre saying is that we can unmount it after boot? so, doable with a module? @HuskyDG

@Bot-wxt1221
Copy link
Contributor

Bot-wxt1221 commented Oct 1, 2023

I try to run zygisk for kernelsu and shamiko. It works

Screenshot_20231001-082753_KernelSU.png

Screenshot_20231001-082748_Termux.png

Screenshot_20231001-082929_KernelSU.png

@Lu5ck
Copy link
Author

Lu5ck commented Oct 3, 2023

Could you show us the output of the following files in an app with no detections?

  • /proc/self/mounts
  • /proc/self/mountinfo
  • /proc/self/mountstats

KSU kernel, with /data/adb/modules.img not deleted
ksu_mounts.txt
ksu_mountstats.txt
ksu_mountinfo.txt

Stock kernel
stock_mounts.txt
stock_mountstats.txt
stock_mountinfo.txt

@belinux
Copy link

belinux commented Oct 4, 2023

I have identified the cause. Before I commit the fix, you can temporarily solve it like this:

rm /data/adb/ksu/modules*.img

And then reboot.

I've tried this, but after rebooting my revanced modules stopped working.. :(

@Ardjlon
Copy link

Ardjlon commented Oct 4, 2023

I have identified the cause. Before I commit the fix, you can temporarily solve it like this:

rm /data/adb/ksu/modules*.img

And then reboot.

I've tried this, but after rebooting my revanced modules stopped working.. :(

It's because the modules are there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants