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

在安卓14上KSU无法正常修补内核 #1573

Closed
3 tasks done
AMWss opened this issue Apr 1, 2024 · 3 comments
Closed
3 tasks done

在安卓14上KSU无法正常修补内核 #1573

AMWss opened this issue Apr 1, 2024 · 3 comments

Comments

@AMWss
Copy link

AMWss commented Apr 1, 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

机型:Redmi K50 Ultra
安卓14
HyperOS
KSU状态:给予了所有请求的权限
问题:报错Not Match Found
Screenshot_2024-04-01-16-09-06-438_me weishu kernelsu
该问题在以下图选择右上角图标选择目标img后解决,但处理后的img并没有生效,刷入后无法获得root
Screenshot_2024-04-01-16-15-56-773_me weishu kernelsu
但是我通过在rec里修改/sdcard/Download/boot.img的权限为0777后开机正常修补,并且修补后的img是有效的,刷入后成功获得权限
而且似乎这也会影响在root环境下直接安装的功能
Screenshot_2024-04-01-16-18-47-960_me weishu kernelsu
我会尝试上传ksu日志至123网盘或者通过邮件,但是其他网盘我可能不行,其中123网盘若是无法网页下载,注册一个账号登录即可直接网页下载,若是需要邮件发送,请备注一下,然后发一下邮箱,我发给您

To Reproduce

Expected behavior

加入申请完全访问并管理所有文件权限以保证修补内核正常运行

Screenshots

No response

Logs

No response

Device info

  • Device:红米K50至尊
  • OS Version:14
  • KernelSU Version:0.9.2
  • Kernel Version:LKM working on 5.10.198

Additional context

No response

@tiann
Copy link
Owner

tiann commented Apr 1, 2024

你应该是使用了自定义内核,它的内核名字不符合 GKI 规范,你需要手动修补;请先查阅文档。

@tiann tiann closed this as completed Apr 1, 2024
@AMWss
Copy link
Author

AMWss commented Apr 1, 2024

你应该是使用了自定义内核,它的内核名字不符合 GKI 规范,你需要手动修补;请先查阅文档。

emm其实不是,因为我在测试过程中也用了原厂的内核,小米官方boot,也是报同样的错,所以排除内核名字的问题

@AMWss
Copy link
Author

AMWss commented Apr 1, 2024

你应该是使用了自定义内核,它的内核名字不符合 GKI 规范,你需要手动修补;请先查阅文档。

并且我通过在rec里修改了目标文件的权限到777后,虽然不清楚它如何工作的但是它的确成功修补了

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

2 participants