WildKernels naming convention changed again

[therealmarv]

Prerequisites

• I have searched existing issues to make sure this bug has not been reported before
• I have searched the XDA Forums to make sure this bug has not been reported before
• I have read the README documentation

Is this issue about reporting a virus or trojan detection?

No

What happened?

Pixelflasher does not find any matching Kernels for WildKernels.

Device state before issue

Pixelflasher did find matching Kernels for WildKernels.

Steps to reproduce

1. Attach Pixel with WildKernels root
2. Process the newest Flash Image from Google
3. Patch with Wild_KSU (not LKM)
4. <- Pixelflasher does not find any WildKernels.

Is your device rooted?

Yes, with another method

If rooted, have you granted shell root access?

Yes

Are you using a custom ROM or kernel?

Yes, I'm using a custom kernel

If using custom ROM/kernel, please confirm

• I have checked the custom ROM/kernel developer's documentation related to this issue
• I have checked if this issue has been reported to the ROM/kernel developer

PixelFlasher Version

8.9.1.0

OS Platform

macOS 26.0.1

Device Model

Pixel 7 Pro

Support File Status

I have attached the encrypted support file generated by PixelFlasher (required naming format: Support_YYYY-MM-DD_hh-mm-ss.zip)

Support File Attachment (REQUIRED)

support_2025-10-31_22-27-34.zip

Additional Notes

see newest naming of WildKernels in https://github.com/WildKernels/GKI_KernelSU_SUSFS/releases
I think you need to edit your RegEx again and allow that it does not start with WKSU

[badabing2005]

This is not a bug, and I will not play yoyo with Wild Kernels developer's whim, every release of wildkernels the developer changes the naming convention, please complain to him.

Eventually I'll add an option to not match anything and list all the assets available, yes all of 348 assets, and let the user select the file they want instead of PixelFlasher automatically selecting it for them, super inconvenient for the user, but that's out of my control.

This is not the first time, see this
#329 (comment)

[therealmarv]

Sounds good. Thanks for even supporting WildKernels. No problem to choose myself (for me).

I keep checking the right Kernel manually (out of extracted boot.img with Magiskboot) with a Hexeditor to be double sure it's the right one. I still do that today 😅

[therealmarv]

Suggestion (a compromise): Maybe allow (pre-)selecting a WildKernel based on pattern matching of the Kernel. E.g. for string 6.1.134 are only two ZIPs in the current assets. And the Linux Kernel version like 6.1.134 needs to be in the filename every time somewhere on Wild's side is my guess.

But I personally would be totally okay to give the (right matching) WildKernel ZIP manually somehow to Pixelflasher if that makes thing easier on your side.

[badabing2005]

you know in the meantime you can download the version that you want, and choose the manual option instead of WildKernels and select that.

[badabing2005]

This is fixed in v8.10.0.0