[bug]: Flashing the 6.6.30 kernel onto a OnePlus 13-PJZ110(ColorOS15.0.0.831) caused a bootloop.

[wahowes2]

Prerequisites

• I have searched existing issues and this is not a duplicate.
• I am running a Stock ROM (OOS or ColorOS).
• (Non-OnePlus devices only) I have read the compatibility list and confirmed my device is listed or uses a OnePlus kernel with a matching KMI.

Device Type

OnePlus device

Device Name & Model

OnePlus 13 — PJZ110

(Non-OnePlus only) OnePlus kernel used

No response

OOS / COS Version

ColorOS 15.0.0.831

Android Version

Android 15

Manager Type

KernelSU-Next

Manager Version

v3.3.0-25-g234f6e04 (33239-2)

Kernel Driver Version

33239

Kernel Installation Source

GitHub Release

Kernel Release Tag or Actions Run Link

https://github.com/WildKernels/OnePlus_KernelSU_SUSFS/releases/download/v2.2.0-r4/AK3_OP13_A15_android15-6.6.30_KSUN_33239_SuSFS_v2.2.0.zip

Bug Description

Bootloop.

lsmod_output.txt

Steps to Reproduce

1.Use magiskboot to unpack the original boot.img file.
2.Rename the Image file in Anykernel3.zip to kernel, replace the original kernel file, and repackage it into a new boot.img file.
3.After flashing the new boot.img to the device, the first screen appears and then quickly goes black, repeating this cycle.

Expected vs Actual Behavior

Expected: Normal startup
Actual: bootloop

Regression?

Unknown / first install

(Regression only) Last working kernel version

No response

Boot.img stock

Yes

Manager Log (name_log.tar.gz)

KernelSU_Next_bugreport_2026-08-12_19_58.tar.gz

SYSTEM_LAST_KMSG (OnePlus devices only)

No response

Additional Context

https://github.com/WildKernels/OnePlus_KernelSU_SUSFS/releases/download/v2.2.0-r4/AK3_OP13-PJZ_A15_android15-6.6.66_KSUN_33239_SuSFS_v2.2.0.zip
Although the original kernel was 6.6.30, flashing a 6.6.66 kernel allowed the device to boot and function normally. To prevent misleading information from the exported lsmod file, I flashed back to the original boot.img, patched and flashed init_boot.img to boot in LKM mode, and then obtained the lsmod file. Therefore, the Susfs module is not working in the image.

[fatalcoder524]

1. Try with 2.2.0-r3 and 2.2.0-r2
2. I would suggest flashing AK3 zip instead of manual boot.img patching.
3. If boot.img patch is required, Then try with this boot.img : https://huggingface.co/datasets/offici5l/fcetool/resolve/main/gauss-componentotacostmanual-cn.allawnfs.com/remove-7d2ca65bd7e500c3623549c6f467b777/component-ota/25/06/13/5878414eb5a042c6aed39dc29ff7c590/boot.img

Issue is I cant find any boot failure logs. So Its an early boot failure!