-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
kernel su 管理器中显示未激活,但是模块正常使用 #1800
Comments
Need dmesg when boot. |
What should I do? |
kernel su is already working, but shows no activation in the manager。I can use the module and root permissions normally |
可能需要一下打开管理器时,dmesg的输出 |
这个要怎么做呢? |
应该是所有魅族的设备都出现这个问题了。 |
需要把 boot 也回退至 0.94 嘛? |
@youlvlv 需要,问群里人最后能用的版本在11863 |
还需要什么信息嘛? |
啊!?😂 |
魅族在/data/app目录中有一个文件,名叫default_cow,这个文件夹上下文是install_data_file
应该就是系统自带的selinux规则阻止了 |
@Kudryavka03 呃~他应该只能做到发现问题(俺也一样😂) |
我也不懂,等大佬来修() |
@Kudryavka03 你的思路我给截图发tg群里了,不知道有没有动手的😂 |
或许尝试加到这里?:https://github.com/tiann/KernelSU/blob/main/kernel/selinux/rules.c#L124
|
fix tiann/KernelSU#1800 Change-Id: I4661e5fd2258fe4b9719d504bb7f89c1b248709b
fix tiann/KernelSU#1800 Change-Id: I4661e5fd2258fe4b9719d504bb7f89c1b248709b
fix tiann/KernelSU#1800 Change-Id: I89f2ae13e7f9d76a82413d0b7fd60e2de4bed14c Signed-off-by: farizmaul <nickshade88@gmail.com>
fix tiann/KernelSU#1800 Change-Id: I89f2ae13e7f9d76a82413d0b7fd60e2de4bed14c Signed-off-by: farizmaul <nickshade88@gmail.com>
fix tiann/KernelSU#1800 Change-Id: I89f2ae13e7f9d76a82413d0b7fd60e2de4bed14c
fix tiann/KernelSU#1800 Change-Id: Iaecf201f84a141d7b4bba11796a5cded47d43323
fix tiann/KernelSU#1800 Change-Id: I89f2ae13e7f9d76a82413d0b7fd60e2de4bed14c Signed-off-by: Gustavo Mendes <gusttavo.me@outlook.com>
fix tiann/KernelSU#1800 Change-Id: I4661e5fd2258fe4b9719d504bb7f89c1b248709b
fix tiann/KernelSU#1800 Change-Id: I4661e5fd2258fe4b9719d504bb7f89c1b248709b
fix tiann/KernelSU#1800 Change-Id: I4661e5fd2258fe4b9719d504bb7f89c1b248709b Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
fix tiann/KernelSU#1800 Change-Id: I4661e5fd2258fe4b9719d504bb7f89c1b248709b Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
fix tiann/KernelSU#1800 Change-Id: I89f2ae13e7f9d76a82413d0b7fd60e2de4bed14c
fix tiann/KernelSU#1800 Change-Id: I89f2ae13e7f9d76a82413d0b7fd60e2de4bed14c
fix tiann/KernelSU#1800 Change-Id: I4661e5fd2258fe4b9719d504bb7f89c1b248709b Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
fix tiann/KernelSU#1800 Change-Id: I89f2ae13e7f9d76a82413d0b7fd60e2de4bed14c
fix tiann/KernelSU#1800 Change-Id: Iaecf201f84a141d7b4bba11796a5cded47d43323
fix tiann/KernelSU#1800 Change-Id: I89f2ae13e7f9d76a82413d0b7fd60e2de4bed14c Signed-off-by: Gustavo Mendes <gusttavo.me@outlook.com>
fix tiann/KernelSU#1800 Change-Id: I4661e5fd2258fe4b9719d504bb7f89c1b248709b Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
fix tiann/KernelSU#1800 Change-Id: I4661e5fd2258fe4b9719d504bb7f89c1b248709b Signed-off-by: Pranav Vashi <neobuddy89@gmail.com> Signed-off-by: popoASM <pratyayaborborah@gmail.com> Signed-off-by: ihsan <ihsanulrahman@gmail.com>
fix tiann/KernelSU#1800 Change-Id: I4661e5fd2258fe4b9719d504bb7f89c1b248709b Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
fix tiann/KernelSU#1800 Change-Id: I4661e5fd2258fe4b9719d504bb7f89c1b248709b Signed-off-by: Pranav Vashi <neobuddy89@gmail.com> Signed-off-by: popoASM <pratyayaborborah@gmail.com> Signed-off-by: ihsan <ihsanulrahman@gmail.com>
fix tiann/KernelSU#1800 Change-Id: I89f2ae13e7f9d76a82413d0b7fd60e2de4bed14c
fix tiann/KernelSU#1800 Change-Id: I89f2ae13e7f9d76a82413d0b7fd60e2de4bed14c Signed-off-by: Gustavo Mendes <gusttavo.me@outlook.com>
fix tiann/KernelSU#1800 Change-Id: I89f2ae13e7f9d76a82413d0b7fd60e2de4bed14c Signed-off-by: Gustavo Mendes <gusttavo.me@outlook.com>
fix tiann/KernelSU#1800 Change-Id: Iaecf201f84a141d7b4bba11796a5cded47d43323
fix tiann/KernelSU#1800 Change-Id: Iaecf201f84a141d7b4bba11796a5cded47d43323
Please check before submitting an issue
Describe the bug
更新了 1.0 版本的 kernel su 后,重新刷入 kernel su 后重启,kernel su 管理器中提示未激活,但是模块被成功挂载了,root 也正常获取了
To Reproduce
Expected behavior
显示激活
Screenshots
Logs
No response
Device info
5.15.94-android13-8-g6701334c485e-ab17001233086
Additional context
No response
The text was updated successfully, but these errors were encountered: