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

Manager and system patches are not working properly in RedMagicOS 9.0.33 / Android 14. #926

Open
5 tasks done
Hetols opened this issue Feb 14, 2025 · 5 comments
Open
5 tasks done
Labels
bug Something isn't working

Comments

@Hetols
Copy link

Hetols commented Feb 14, 2025

Please check before submitting an issue/在提交 issue 前请检查

  • I have searched the issues and haven't found anything relevant/我已经搜索了 issues 列表,没有发现于本问题相关内容
  • If patch failed, root failed, or device unable to boot after flashing the new boot.img. Please goto KernelPatch/修复失败或刷入修补后镜像不能启动,请前往 KernelPatch 提问
  • I will upload bugreport file in APatch Manager - Settings - Report log/我会上传 bureport 文件从 APatch 管理器 - 设置 - 发送日志
  • I know how to reproduce the issue which may not be specific to my device/我知道如何重新复现这个问题

Version requirement/版本要求

  • I am using latest CI version of APatch/我正在使用最新 CI 版本

Describe the bug/描述 bug

由10763版本更新到11039版本之后,管理器无法正确的处理超级用户授权以及模块安装。
After updating from version 10763 to 11039, the manager cannot correctly handle superuser authorization and module installation.

Reproduce method/复现方法

    1. 更新管理器至11039版本 / Update Manager to version 11039
    1. 更新内核模块至0.11.2版本 / Update kernel module to version 0.11.2
    1. 更新系统补丁 / Update system patche
    1. 安装系统模块更新 / Install system module update
    1. 重新启动设备 / Reboot device

Expected behavior/预期行为

重新启动之后,之前已经授予权限的软件能够正常使用超级用户权限,系统模块的更新被正确的安装。
After rebooting, previously authorized software can use superuser permissions normally, and system module updates are installed correctly.

Actual behaviour /实际行为

在重新启动之后,超级用户的授权列表仅剩下shell,系统模块的更新仍然显示为等待系统重新启动。此时即使再次对应用授予超级用户权限,应用也无法正常使用该权限。
After rebooting, the superuser authorization list only contains the shell, and system module updates still show as pending a system reboot. Even after granting superuser permissions to the app again, the app cannot use the permissions properly.

Screenshots/截图

No response

Logs/日志

No response

Device Name/设备名称

RedMagic 9 Pro (NX769J)

OS Version/系统版本

14

APatch Version/APatch 版本

11039

Kernel Version/内核版本

6.1.68-android14-11-g716498f88d0f-ab11695701

KernelPatch Version/KernelPatch 版本

0.11.2

Additional context/其他信息

经过反复测试,该问题可以通过卸载系统补丁并立刻重新安装来临时解决,并会在重新启动设备之后重新出现。
After repeated testing, the issue can be temporarily resolved by uninstalling and immediately reinstalling the system patch, and will reappear after rebooting the device.

该问题无法通过重新修补内核解决。
This issue cannot be resolved by patching the kernel.

该问题在 10763 的 Release 版本之后所有的CI版本均有出现。
This issue has appeared in all CI builds after the 10763 Release version.

@Hetols Hetols added the bug Something isn't working label Feb 14, 2025
@VisionR1
Copy link
Contributor

Have you try clean install? Or delete /data/adb all inside and reboot?

@Hetols
Copy link
Author

Hetols commented Feb 14, 2025

Have you try clean install? Or delete /data/adb all inside and reboot?

@VisionR1

I have tried the following solutions but none of them worked:

  • Clearing the userdata partition, reinstalling the system, and patching boot.img again.
  • Deleting /data/adb after the issue appeared, performing a "full uninstall" of the patch, and then patching and installing again.

我尝试过以下方案但都未能解决该问题:

  • 清除userdata分区后重新安装系统并在修补boot.img之后进行相同的操作
  • 在已经出现该问题的情况下删除/data/adb并对补丁进行“完整卸载”,再重新进行修补和安装操作

@VisionR1
Copy link
Contributor

Understand.
So, maybe your device is not complete compatible, with APatch.

@Hetols
Copy link
Author

Hetols commented Feb 14, 2025

@VisionR1
I'd like to know if this issue will be resolved in future versions?
If you need to conduct related tests later, please contact me, and I will do my best to help.

@VisionR1
Copy link
Contributor

@VisionR1 I'd like to know if this issue will be resolved in future versions? If you need to conduct related tests later, please contact me, and I will do my best to help.

Really, i don't know.
For my device (A11) never had this problem before, and if have any other problems, i clean install or delete all inside in /data/adb

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants