Don't use APatch with 6.1.124-android14-11-g8d713f9e8e7b-ab13202960 if you don't want bootloop

[albotroz]

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

• I searched the issues and didn't found anything relevant | 我已经搜索了 Issues 列表，没有发现于本问题相关内容
• If the patch fails or the image cannot be booted after flashing the new boot.img, visit KernelPatch to clarify your doubts | 修复失败或刷入修补后镜像不能启动，请前往 KernelPatch 提问
• I will upload the bug report file in APatch Manager > Settings > Send logs | 我会上传 Bug Report 文件从 APatch 管理器 > 设置 > 发送日志
• I know how to reproduce the issue, which might not be specific to my device | 我知道如何重新复现这个问题

Version requirements | 版本要求

• I'm using the latest CI version of APatch Manager | 我正在使用最新 CI 版本

Bug description | 描述 Bug

APatch causes bootloop, even after repatching to boot.img from ROM

Reproduce method | 复现方法

Try 11142 and latest CI build

Expected behavior | 预期行为

Should start without bootloop, should start without bootloop after repatching to ROM-boot.img

Actual behavior | 实际行为

BOOTLOOP

Screenshots | 截图

No response

Logs | 日志

No response

Device name | 设备名称

Google Pixel 6a "bluejay"

OS version | 系统版本

LineageOS 23 (Android 16)

APatch version | APatch 版本

11142 and latest CI

Kernel version | 内核版本

6.1.124-android14-11-g8d713f9e8e7b-ab13202960

KernelPatch version | KernelPatch 版本

BOOTLOOP

[NikunjK8]

I also got bootloop on 6.6.56-android15-8-g6f1fb56fa84d-ab13470876-4k
Using Infinity X 3.5 Android 16

I tried both patching boot.img method and renaming apk to zip and flashing through recovery. Same results even though APatch requirements are met.

[hayvan96]

If it's a bluejay (pixel 6a), the ramdisk is in vendor_boot, not boot. Have you tried to patch vendor_boot.img instead of boot.img?

[NikunjK8]

Mine is rodin (poco x7 pro)

[albotroz]

If it's a bluejay (pixel 6a), the ramdisk is in vendor_boot, not boot. Have you tried to patch vendor_boot.img instead of boot.img?

Was that the recommendation from the start?
With earlier Android versions on Pixel 6a (bluejay), I always patched boot.img and it worked - Magisk and APatch.

Newer Android/kernel versions then caused APatch to restart.

The last time I tried APatch with Pixel 6a (LineageOS), it caused reboots, and I tried patching boot.img, vendor_boot.img, etc. again, but this time I took them from Lineage to fix the reboots. That didn't help, and I had to reflash LineageOS.

[hayvan96]

If it's a bluejay (pixel 6a), the ramdisk is in vendor_boot, not boot. Have you tried to patch vendor_boot.img instead of boot.img?

Was that the recommendation from the start? With earlier Android versions on Pixel 6a (bluejay), I always patched boot.img and it worked - Magisk and APatch.

Newer Android/kernel versions then caused APatch to restart.

The last time I tried APatch with Pixel 6a (LineageOS), it caused reboots, and I tried patching boot.img, vendor_boot.img, etc. again, but this time I took them from Lineage to fix the reboots. That didn't help, and I had to reflash LineageOS.

Well I don't know, I was suggesting that because I originally tried apatch to replace magisk on my bluejay (LOS22), but it resulted in some reboots. I switched to kernelsu next, patched boot.img and after a while, I realized the ramdisk was containted in vendor_boot. Since then, I'm flashing the (LOS) vendor boot img via fastboot and I had no problem (on KSUN). I was just wondering if it could fix the problems with apatch, since for that specific device, vendor_boot seems to be the image to be patched.