Invalid ramdisk in boot.img with KernelSU installed as a kernel module

[scarlettekk]

Pixel 8 pro, android QPR Beta (AP21.240216.010)
When using the new kernel module install mode of KernelSU, the app does not load with the given error message

[capntrips]

Can you share dumps of the boot and init_boot partitions?

adb shell
su
cd /data/local/tmp
dd if=/dev/block/by-name/boot_a of=boot_a.img
dd if=/dev/block/by-name/boot_b of=boot_b.img
dd if=/dev/block/by-name/init_boot_a of=init_boot_a.img
dd if=/dev/block/by-name/init_boot_b of=init_boot_b.img
exit
exit
adb pull /data/local/tmp/boot_a.img
adb pull /data/local/tmp/boot_b.img
adb pull /data/local/tmp/init_boot_a.img
adb pull /data/local/tmp/init_boot_b.img

Do you have any details on where the kernel module is installed? If it goes into a separate partition, can you share that dump, as well?

[scarlettekk]

a.zip
b.zip
The module is installed by patching init_boot, other than that I am not sure how it works. The current slot is _a

[capntrips]

A test build, v1.0.0-alpha20+allow-errors, is now available on the releases page. If this does not resolve your issue, feel free to reopen.

[scarlettekk]

It loads now but still shows the warning on slot 1. Will it still work correctly?

[capntrips]

Here are my notes from the XDA support thread:

The allow-errors build will ignore any kernel or ramdisk errors (even on the active slot), which will hopefully allow it to work with KernelSU installed as a kernel module mode. This may have implications in other areas. For example, since it allows a null sha1, it may behave unexpectedly when attempting to make backups when there is a ramdisk error. I'll make an effort to add a settings screen with toggles for sha1 and error handling before I remove the pre-release tag.

Beyond that, I can only speculate, as I don't know any about how KernelSU works. The error message is only informational, and potential quirks with backups aside, there should be nothing that prevents Kernel Flasher from performing its operations. I have no idea if that ramdisk state has any implications for AK3.

Assuming no issues are reported, I may drop the error messages when I remove the pre-release tag.