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

Issues or not with .bind_mount_enable ? #763

Open
5 tasks done
VisionR1 opened this issue Nov 3, 2024 · 8 comments
Open
5 tasks done

Issues or not with .bind_mount_enable ? #763

VisionR1 opened this issue Nov 3, 2024 · 8 comments
Labels
bug Something isn't working

Comments

@VisionR1
Copy link
Contributor

VisionR1 commented Nov 3, 2024

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

In case someone have the same.
Latest nightly build with feature .bind_mount_enable, have some issues, the modules not update, example, the PIFork when I create the script-only-mode and install it again from APatch, instead of script-only-mode, install the full version again.
And module who remove or replace system apps, when install it the integrity failed, even the basic not pass, with PIF, even with TrickyStore.
If disabled my module for remove&replace files system, the integrity work again.
In Kitsune Mask I don't have problems with this specific feature.

Reproduce method/复现方法

  1. Update a module. example from PIFork full mode to script-only-mode.

  2. Install a module, who remove&replace system files.

Expected behavior/预期行为

  1. Install a module actually update.

  2. Not failed the integrity, even the basic.

Actual behaviour /实际行为

All the above.

Screenshots/截图

IMG_20241103_173923
cp: '/data/adb/modules/playintegrityfix/module.prop' and '/data/adb/modules/playintegrityfix/module.prop' are the same file.

This feature, is from Kitsune Mask.
IMG_20241103_170806

Logs/日志

No response

Device Name/设备名称

Xiaomi Poco X3 NFC

OS Version/系统版本

11

APatch Version/APatch 版本

APatch_10763-236-g9b935ac/10999

Kernel Version/内核版本

4.14.180-perf-gae096ac9215c

KernelPatch Version/KernelPatch 版本

0.11.1

Additional context/其他信息

Nothing more.

@VisionR1 VisionR1 added the bug Something isn't working label Nov 3, 2024
@VisionR1
Copy link
Contributor Author

I found when I replace hosts in system/etc and remove apps from system/pri-apps the integrity failed, even the basic, but if I replace the bootanimation from system/media, the integrity all good.

@shedowe19
Copy link

shedowe19 commented Nov 23, 2024

APatch_install_APM_log_2024-11-23-16-50-10.log
APatch_bugreport_2024-11-23_16_50.tar.gz
I have read only Filesystem, can you check the Logs?

@VisionR1
Copy link
Contributor Author

VisionR1 commented Nov 23, 2024

APatch_install_APM_log_2024-11-23-16-50-10.log Uploading APatch_bugreport_2024-11-23_16_50.tar.gz… I have read only Filesystem, can you check the Logs?

Oh, now I have again the overlayfs mode.
What logs exactly?

@shedowe19
Copy link

APatch_install_APM_log_2024-11-23-16-50-10.log Uploading APatch_bugreport_2024-11-23_16_50.tar.gz… I have read only Filesystem, can you check the Logs?

Oh, now I have again the overlayfs mode. What logs exactly?

Now the Logs are there

@shedowe19
Copy link

I have only write acess after Boot 5 minutes and then are in Read Only Mode

@VisionR1
Copy link
Contributor Author

I have only write acess after Boot 5 minutes and then are in Read Only Mode

I'm little confused, how your issue, is relative with mine? You have this issue after bind_mount_enable ?

@shedowe19
Copy link

Screenshot_20241123-171426
With the Module Magisk_overlayfs its worked, but not without

@VisionR1
Copy link
Contributor Author

VisionR1 commented Nov 23, 2024

Oh, unfortunately I don't know, maybe your kernel somehow reject the internal overlayfs, and with this module can bypass.
In my device the internal overlayfs work, for me not work the bind_mount_enable. like issue title.
Have you write about that, in the telegram Group?

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