Repository navigation
Kernel Panic when using 6.6 kernel android 15 .ko module #319
Description
Soo 1r of all, an issue, the .ko module was tested on a Pixel 10 Pro XL running Android 17, which i expected to be out of scope as for now.
The reason for me uploading this issue is in the scenario that the issue was not expected, or may be related to issues with other devices, and ill upload any findings i have here or solutions.
reset message: KP: Oops: Fatal exception: comm:finit_loader PC:kp_patch_text+0x30/0x188 [kernelpatch] LR:0x86a1d54865208aa8
Activity
david568303 commentedon Oct 1, 2026
As more data im running GrapheneOS, and tought i had to manipulate selinux, disable kernel modules signature by applying some patches to the kernel, this is what i came up with that loads, im working into getting it to work smoothly/properly on grapheneos right now.
kernelpatch-native64-graphene-vm.zip
xeropresence commentedon Oct 1, 2026
What commit are you working off of?
With a308d88 merged, 6.1 kernels on graphene are working for me.
xeropresence commentedon Oct 1, 2026
so with grapheneos, the kernel is compiled with RANDSTRUCT_FULL, i think thats going to pose a problem for using the ko module.
david568303 commentedon Oct 1, 2026
Im working with the 6.6 kernel android 15 .ko kernel module, and out of the box its not working for me on Android 17.
david568303 commentedon Oct 1, 2026
IDK, i have been able to get around some issues now, to the point where Apatch detects it and allows it to install tought it never installs because su is not working yet with the modifications i currently have, im working on trying to solve that.
xeropresence commentedon Oct 1, 2026
Try using kptools to patch boot.img instead of using the module.
david568303 commentedon Oct 1, 2026
Ok, will do in less than 1h, i was still working on getting the .ko module to work and i really want to give it a shot.
david568303 commentedon Oct 2, 2026
Well, i think ill close the issue, i got to a point where i wasn't getting su for some reason, it was working to a point but it couldn't adquire su, i decided to go for a project that covers the os i wanted which i think will be easyer for me, i ended up just nuking all the files, also, part of the reason was that when updating there would be a brick risk because of the .ko module, while by using something tested and maintained by multiple members of the community, ill have a lower risk.
And to add, i know i could just have tested kptools or kpimg-android and if it worked i just had to sign the images, but i have spent a good time trying to get it to work and i only have this device currently.
david568303 commentedon Oct 3, 2026
Hey, soo i ended up trying it out, but it didn't work.
Also, i made a fork where claude fixed the issues and i was able to boot.
My Fork
On a Pixel 10 Pro XL with kernel 6.6
Soo i asked claude to help me fix the issue and he was able to identify 2 issues.