APatch
APatch copied to clipboard
apd module install fails, but through the App it works
Please check before submitting an issue/在提交 issue 前请检查
- [X] I have searched the issues and haven't found anything relevant/我已经搜索了 issues 列表,没有发现于本问题相关内容
- [X] If patch failed, root failed, or device unable to boot after flashing the new boot.img. Please goto KernelPatch/修复失败或刷入修补后镜像不能启动,请前往 KernelPatch 提问
- [X] 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/版本要求
- [X] I am using latest CI version of APatch/我正在使用最新 CI 版本
Describe the bug/描述 bug
Trying to install a module through command line
apd module install /sdcard/Download/Zygisk-Next-1.1.0-330-a1b0e69-release.zip
it fails
_ ____ _ _
/ \ | _ \ __ _| |_ ___| |__
/ _ \ | |_) / _` | __/ __| '_ \
/ ___ \| __/ (_| | || (__| | | |
/_/ \_\_| \__,_|\__\___|_| |_|
- Preparing image
- Module size: 3.43 MB
e2fsck 1.46.6 (1-Feb-2023)
- Estimated minimum size of the filesystem: 12245
e2fsck 1.46.6 (1-Feb-2023)
- Target image size: 284.41 MB
resize2fs 1.46.6 (1-Feb-2023)
e2fsck 1.46.6 (1-Feb-2023)
- Mounting image
- Error: Invalid argument (os error 22)
Error: Invalid argument (os error 22)
However installing from APatch app it works.
_ ____ _ _
/ \ | _ \ __ _| |_ ___| |__
/ _ \ | |_) / _` | __/ __| '_ \
/ ___ \| __/ (_| | || (__| | | |
/_/ \_\_| \__,_|\__\___|_| |_|
- Preparing image
- Module size: 3.43 MB
e2fsck 1.46.6 (1-Feb-2023)
- Estimated minimum size of the filesystem: 12245
e2fsck 1.46.6 (1-Feb-2023)
- Target image size: 284.41 MB
resize2fs 1.46.6 (1-Feb-2023)
e2fsck 1.46.6 (1-Feb-2023)
- Mounting image
- Current boot slot: _a
- Device is system-as-root
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: module.prop
*********************
Zygisk Next
by Nullptr, 5ec1cff
*********************
*******************
Powered by APatch
*******************
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: customize.sh
- Installing from APatch app
- Installing Zygisk Next 1.1.0 (330-a1b0e69-release)
- Device sdk: 34
- Device platform: arm64
- Extracting verify.sh
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: verify.sh
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
creating: META-INF/com/google/android/
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/update-binary.sha256
inflating: META-INF/com/google/android/updater-script
inflating: META-INF/com/google/android/updater-script.sha256
- Verified META-INF/com/google/android/update-binary
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: customize.sh
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: customize.sh.sha256
- Verified customize.sh
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: verify.sh
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: verify.sh.sha256
- Verified verify.sh
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: sepolicy.rule
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: sepolicy.rule.sha256
- Verified sepolicy.rule
- Extracting module files
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: module.prop
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: module.prop.sha256
- Verified module.prop
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: post-fs-data.sh
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: post-fs-data.sh.sha256
- Verified post-fs-data.sh
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: service.sh
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: service.sh.sha256
- Verified service.sh
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: uninstall.sh
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: uninstall.sh.sha256
- Verified uninstall.sh
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: zygisk-ctl.sh
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: zygisk-ctl.sh.sha256
- Verified zygisk-ctl.sh
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: mazoku
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: mazoku.sha256
- Verified mazoku
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
creating: webroot/
creating: webroot/assets/
inflating: webroot/assets/index-BS7muKoR.js
inflating: webroot/assets/index-php30EZ9.css
inflating: webroot/index.html
- Extracting arm libraries
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: zygiskd
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: zygiskd.sha256
- Verified bin/armeabi-v7a/zygiskd
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: libzygisk.so
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: libzygisk.so.sha256
- Verified lib/armeabi-v7a/libzygisk.so
- Extracting arm64 libraries
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: zygiskd
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: zygiskd.sha256
- Verified bin/arm64-v8a/zygiskd
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: libzygisk.so
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: libzygisk.so.sha256
- Verified lib/arm64-v8a/libzygisk.so
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: libpayload.so
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: libpayload.so.sha256
- Verified lib/arm64-v8a/libpayload.so
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: machikado.arm
Archive: /data/user/0/me.bmax.apatch/cache/module.zip
inflating: machikado.arm.sha256
- Verified machikado.arm
- Setting permissions
- Ensure config dir created
- Clean up unused configure files
- Done
Am I doing something wrong or is there a bug?
Reproduce method/复现方法
- download ZygiskNext
cd /data/adb/apas root- Issue the command:
bin/apd module install /sdcard/Download/Zygisk-Next-1.1.0-330-a1b0e69-release.zip
Expected behavior/预期行为
I expect the module to install the same way it gets installed from the AP
Actual behaviour /实际行为
Fails with error:
Error: Invalid argument (os error 22)
Screenshots/截图
No response
Logs/日志
No response
Device Name/设备名称
Pixel 5
OS Version/系统版本
A14
APatch Version/APatch 版本
0.11.1
Kernel Version/内核版本
Error: Invalid argument (os error 22)
KernelPatch Version/KernelPatch 版本
0.11.1
Additional context/其他信息
0.11.1 is from here.