-
Notifications
You must be signed in to change notification settings - Fork 331
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
Zygisk Being detected (Shamiko) #57
Comments
|
install debug version from actions and provide logs |
Logs in kernelsu ? |
I have said install DEBUG version |
Oh sorry my bad, i search the debug version but i didn't found .. |
Oh ok, ... I install the ZygiskOnKernelSU-debug from your link above.. I send new logs from kernelsu right ? |
material terminal is 32 bit and zygisksu now only supports 64 bit processes |
Why don't you read the changelog? 32 bit support is dropped in 0.8.0. it might be added back later, but not now |
Oh i see the changelog before upgrade the module, i think the drop support for 32bit platform not affected for hide method.. my bad to understand it 😑. |
About replace /dev/zygisk to /debug_randisk, is that a feature not updated in the latest release? I use zygisk next on magisk and still find /dev/zygisk. |
Steps to reproduce/复现步骤
latest ZygiskOnKernelSU is being detected just by:
i check with RootXplorer to see inside folder /dev and i see zygisk/ folder in here.
but in previous version everything is work fine.
I Apologize if i report issue in here, i think just shamiko module bugs not support the new ZygiskOnKernelSU. but i can't commit the new issue in Shamiko Module repository..
my setup:
Expected behaviour/预期行为
Shamiko Module fix maybe ?
Actual behaviour/实际行为
Bugs on Shamiko Module ?
KernelSU Module List/KernelSU 模块列表
Zygisk on KernelSU version/Zygisk on KernelSU 版本
ZygiskOnKernelSU v4-0.8.0 (latest)
Android version/Android 版本
13
KernelSU version/KernelSU 版本
KernelSU 11272 (manager 0.6.9) (latest)
Version requirement/版本要求
Logs/日志
i no have logs, but i thing is clear :)
The text was updated successfully, but these errors were encountered: