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

kernel su 管理器中显示未激活,但是模块正常使用 #1800

Closed
2 of 3 tasks
youlvlv opened this issue Jun 3, 2024 · 20 comments · Fixed by #1832
Closed
2 of 3 tasks

kernel su 管理器中显示未激活,但是模块正常使用 #1800

youlvlv opened this issue Jun 3, 2024 · 20 comments · Fixed by #1832

Comments

@youlvlv
Copy link

youlvlv commented Jun 3, 2024

Please check before submitting an issue

  • I have searched the issues and haven't found anything relevant
  • I will upload bugreport file in KernelSU Manager - Settings - Report log
  • I know how to reproduce the issue which may not be specific to my device

Describe the bug

更新了 1.0 版本的 kernel su 后,重新刷入 kernel su 后重启,kernel su 管理器中提示未激活,但是模块被成功挂载了,root 也正常获取了

To Reproduce

  1. 从 0.94 更新到 1.0 版本管理器
  2. 刷入 kernel su
  3. 重启提示未激活

Expected behavior

显示激活

Screenshots

S40603-20292763_me weishu kernelsu
S40603-20291989_org lsposed manager

Logs

No response

Device info

  • Device: meizu 20 pro
  • OS Version:flyme 10.5.5.1
  • KernelSU Version: 1.0
  • Kernel Version:
    5.15.94-android13-8-g6701334c485e-ab17001233086

Additional context

No response

@aviraxp
Copy link
Contributor

aviraxp commented Jun 3, 2024

Need dmesg when boot.

@youlvlv
Copy link
Author

youlvlv commented Jun 5, 2024

Need dmesg when boot.

What should I do?

@youlvlv
Copy link
Author

youlvlv commented Jun 5, 2024

Need dmesg when boot.

kernel su is already working, but shows no activation in the manager。I can use the module and root permissions normally

@aviraxp
Copy link
Contributor

aviraxp commented Jun 5, 2024

https://t.me/hwrtools/10

@youlvlv
Copy link
Author

youlvlv commented Jun 6, 2024

@aviraxp
Copy link
Contributor

aviraxp commented Jun 7, 2024

可能需要一下打开管理器时,dmesg的输出

@youlvlv
Copy link
Author

youlvlv commented Jun 8, 2024

可能需要一下打开管理器时,dmesg的输出

这个要怎么做呢?

@Kudryavka03
Copy link

应该是所有魅族的设备都出现这个问题了。
退回Ver0.9.4正常,0.9.5起管理器显示未激活了,但Root权限,模块,一切正常工作

@youlvlv
Copy link
Author

youlvlv commented Jun 11, 2024

应该是所有魅族的设备都出现这个问题了。
退回Ver0.9.4正常,0.9.5起管理器显示未激活了,但Root权限,模块,一切正常工作

需要把 boot 也回退至 0.94 嘛?

@HHH3366
Copy link

HHH3366 commented Jun 11, 2024

@youlvlv 需要,问群里人最后能用的版本在11863

@youlvlv
Copy link
Author

youlvlv commented Jun 17, 2024

可能需要一下打开管理器时,dmesg的输出

还需要什么信息嘛?

@Kudryavka03
Copy link

宽容SELinux后开两次管理器就能正常识别到工作中
de4fb77e5c5e3a1d0567e54619083017
再次改为严格后,管理器依然工作
8ac9297745c57f3429250af2704751e2_720

@HHH3366
Copy link

HHH3366 commented Jun 18, 2024

啊!?😂

@youlvlv
Copy link
Author

youlvlv commented Jun 18, 2024

宽容SELinux后开两次管理器就能正常识别到工作中 de4fb77e5c5e3a1d0567e54619083017 再次改为严格后,管理器依然工作 8ac9297745c57f3429250af2704751e2_720

我尝试了一下,还是没有成功,修改后需要重启么?

@Kudryavka03
Copy link

宽容SELinux后开两次管理器就能正常识别到工作中 de4fb77e5c5e3a1d0567e54619083017 再次改为严格后,管理器依然工作 8ac9297745c57f3429250af2704751e2_720

我尝试了一下,还是没有成功,修改后需要重启么?

不要重启,多开几次也许就好了()
kmsg中会有KernelSU的日志,提示找到了管理器的
感觉是有不明的SELinux策略阻止了Manager对tmpfs的访问?

@Kudryavka03
Copy link

Kudryavka03 commented Jun 18, 2024

魅族在/data/app目录中有一个文件,名叫default_cow,这个文件夹上下文是install_data_file
然后ksu_filp_open_compat打开这个目录的时候,会被SELinux阻止,然后就不再继续搜寻下去了

avc: denied { read } for comm="PackageManager" name="default_cow" dev="dm-55" ino=276 scontext=u:r:system_server:s0 tcontext=u:object_r:install_data_file:s0 tclass=dir permissive=0

应该就是系统自带的selinux规则阻止了
通过ksud给selinux打补丁 ksud sepolicy patch "allow system_server install_data_file dir {read open}" 后顺利找到manager。
所以search_manager在搜索管理器的时候,遇到错误的时候是不是应该不要返回而是继续搜索下去呢?
@youlvlv 试试看用ksud给SELinux规则打一下补丁
然后随便安装或卸载一个app,再看看manager有没有问题(

@HHH3366
Copy link

HHH3366 commented Jun 18, 2024

@Kudryavka03 呃~他应该只能做到发现问题(俺也一样😂)

@Kudryavka03
Copy link

@Kudryavka03 呃~他应该只能做到发现问题(俺也一样😂)

我也不懂,等大佬来修()

@HHH3366
Copy link

HHH3366 commented Jun 18, 2024

@Kudryavka03 你的思路我给截图发tg群里了,不知道有没有动手的😂

@pomelohan
Copy link

pomelohan commented Jun 18, 2024

或许尝试加到这里?:https://github.com/tiann/KernelSU/blob/main/kernel/selinux/rules.c#L124

ksu_allow(db, "system_server", "install_data_file", "dir", "open");
ksu_allow(db, "system_server", "install_data_file", "dir", "read");

Jprimero15 pushed a commit to Jprimero15/KernelSU that referenced this issue Jun 19, 2024
diphons pushed a commit to diphons/sdm845-419 that referenced this issue Jun 19, 2024
diphons pushed a commit to diphons/kernel_xiaomi_sdm845 that referenced this issue Jun 19, 2024
rcmiku pushed a commit to rcmiku/KernelSU that referenced this issue Jun 23, 2024
Huexxx pushed a commit to Huexxx/kernel_xiaomi_msm8998 that referenced this issue Jun 24, 2024
diphons pushed a commit to diphons/kernel_xiaomi_sdm845 that referenced this issue Jun 25, 2024
diphons pushed a commit to diphons/kernel_xiaomi_sdm845 that referenced this issue Jun 25, 2024
diphons pushed a commit to diphons/kernel_xiaomi_sdm845 that referenced this issue Jun 25, 2024
diphons pushed a commit to diphons/kernel_xiaomi_sdm845 that referenced this issue Jun 25, 2024
diphons pushed a commit to diphons/kernel_xiaomi_sdm845 that referenced this issue Jun 25, 2024
diphons pushed a commit to diphons/kernel_xiaomi_sdm845 that referenced this issue Jun 25, 2024
diphons pushed a commit to diphons/kernel_xiaomi_sdm845 that referenced this issue Jun 25, 2024
diphons pushed a commit to diphons/kernel_xiaomi_sdm845 that referenced this issue Jun 25, 2024
ryxpace pushed a commit to ryxpace/KernelSU that referenced this issue Jun 25, 2024
Danda420 pushed a commit to Danda420/kernel_xiaomi_sm8250 that referenced this issue Jun 26, 2024
Huexxx pushed a commit to Huexxx/kernel_xiaomi_msm8998 that referenced this issue Jun 27, 2024
Huexxx pushed a commit to Huexxx/kernel_xiaomi_msm8998 that referenced this issue Jun 27, 2024
Huexxx pushed a commit to Huexxx/kernel_xiaomi_msm8998 that referenced this issue Jun 28, 2024
Huexxx pushed a commit to Huexxx/kernel_xiaomi_msm8998 that referenced this issue Jun 28, 2024
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

Successfully merging a pull request may close this issue.

5 participants