https://nightly.link/KernelSU-Next/KPatch-Next-Module/workflows/build.yaml/main?previewhttps://nightly.link/KernelSU-Next/KPatch-Next-Module/workflows/build.yaml/main?preview
New ci available!
Module v0.0.1-52 | KPatch v0.13.1
New ci available!
Module v0.0.1-52 | KPatch v0.13.1
👏20❤3😁2
We have identified the issue of bootloops for 6.6 kernel devices with KPatch Next.
Its not an issue with the kpimg patching but an issue on webui for the process of boot.img -> unpacking -> patching -> repacking -> boot.img
We will try to fix it soon.
Its not an issue with the kpimg patching but an issue on webui for the process of boot.img -> unpacking -> patching -> repacking -> boot.img
We will try to fix it soon.
😢14👍9❤5🥰3
If you still want to test kpatch-next then you can patch it manually from cli/termux and enjoy the module that way.
👍12😁2
KernelSU Next
We have identified the issue of bootloops for 6.6 kernel devices with KPatch Next. Its not an issue with the kpimg patching but an issue on webui for the process of boot.img -> unpacking -> patching -> repacking -> boot.img We will try to fix it soon.
The issue is identified and it was magiskboot incompatibility provided by root manger (ksu and forks mostly)
1🔥24😁7😇4❤1🥰1
Bootloop Issue is fixed for 6.6 kernel devices for latest CI
https://nightly.link/KernelSU-Next/KPatch-Next-Module/workflows/build.yaml/main/KPatch-Next-Module-67.zip
https://nightly.link/KernelSU-Next/KPatch-Next-Module/workflows/build.yaml/main/KPatch-Next-Module-67.zip
1🔥34👍12❤4😁2👀2
This media is not supported in your browser
VIEW IN TELEGRAM
3❤54👍21🔥4😢4💘2✍1🥰1👏1
KPach Next has WebUI localization now.
If you want another language, add it and open a PR.
https://github.com/KernelSU-Next/KPatch-Next-Module/
If you want another language, add it and open a PR.
https://github.com/KernelSU-Next/KPatch-Next-Module/
GitHub
GitHub - KernelSU-Next/KPatch-Next-Module: Standalone implementation of KPM support for Magisk/KernelSU
Standalone implementation of KPM support for Magisk/KernelSU - KernelSU-Next/KPatch-Next-Module
❤23👍7❤🔥3😢1
You can now disable and enable
Target Rehooks and Minimal Rehooks
Target Rehooks are enabled by default in kernel, what target Rehooks does is disables targeted syscall for side channel attacks (syscall delay), what Minimal on the other hand is, it disables all unrequired 451 syscalls and only keeping a few set of critical hooks as whitelist for kpnext to be still functioning and operate able which highly squashes side channel attacks in sacrifice for some modules which depends on those blacklisted syscall being unloadable but can be embedded and load early or you load it then enable minimal Rehooks.
Don't worry you don't have to do it in CLI webui toggles will come soon!
Target Rehooks and Minimal Rehooks
Target Rehooks are enabled by default in kernel, what target Rehooks does is disables targeted syscall for side channel attacks (syscall delay), what Minimal on the other hand is, it disables all unrequired 451 syscalls and only keeping a few set of critical hooks as whitelist for kpnext to be still functioning and operate able which highly squashes side channel attacks in sacrifice for some modules which depends on those blacklisted syscall being unloadable but can be embedded and load early or you load it then enable minimal Rehooks.
Don't worry you don't have to do it in CLI webui toggles will come soon!
🔥23❤13👍7
Also btw I will open a kpm modules repo where we can host all kpm modules for easy of findability
3🎉66👍32❤15🔥5
I have removed the need for a superkey (password) for KPatch-Next entirely, no need key for patching neither for verification. Since we are root (uid 0) its really unnecessary and yes no one else can control KPatch-Next unless you are root (uid 0) for security reasons.
👍74🔥18❤9😢9🥰1
The new version v0.13.3 binaries are updated and module ci has auto inherited them, so i suggest to not update or install new ci until webui is updated for the changes
❤26😢9😁2
So i just fixed a very bad crash issue for KPatch-Next with its minimal rehook when enabled it does a very bad kernel panic or syscalls being broken on the entire system, but it gets back in track after a reboot but yes it will happen again if minimal rehook is toggled again, idk why but this thing came to occur when i removed the need of a superkey, weird.
Well anyways after 5 hours of debugging, testing and several refactors i found out it was a massive buffer overflow memory shitting the device up.
Welp anyways its fixed and im dead.
So i suggest if you want to update for next CI please use a fresh boot/kernel non Kpnext patched to repatch.
Well anyways after 5 hours of debugging, testing and several refactors i found out it was a massive buffer overflow memory shitting the device up.
Welp anyways its fixed and im dead.
So i suggest if you want to update for next CI please use a fresh boot/kernel non Kpnext patched to repatch.
2❤43🔥10👍9🥰3
KernelSU Next pinned «KPatch-Next is now open source and available for testing CI builds! https://nightly.link/KernelSU-Next/KPatch-Next-Module/workflows/build.yaml/main?preview»