KernelSU Next
0x12b5224b7aca0121c2f003240a901e1d064371c1 [ USDT BEP20 ] TYUVMWGTcnR5svnDoX85DWHyqUAeyQcdjh [ USDT TRC20 ] 0x12b5224b7aca0121c2f003240a901e1d064371c1 [ USDT ERC20 ] 0x12b5224b7aca0121c2f003240a901e1d064371c1 [ ETH ERC20 ] Ld238uYBuRQdZB5YwdbkuU6ektBAAUByoLโฆ
Okay people I never asked for donations and never would've asked lol I could just stop KernelSU Next and go to the next project comes to mind but since y'all wanting me to continue so that's why I put the crypto addresses from your request, so if you are confused or don't want to donate it's up to you man ๐
I never wanted money instead you can donate a old open source kernel device
โค90๐คก35๐21๐ข9๐ฅฐ2๐ฉ2๐1๐
1
KernelSU Next experimental development will be back on track after 12th of February.
๐ฅ60๐27โค5๐ฑ5๐คก5๐ฉ2๐1๐ฆ1
Feature requests now open and will close after 24 hours so please don't spam the section. Also you could just drop ideas in GitHub issues.
https://t.me/ksunext_group/24861
https://t.me/ksunext_group/24861
๐21๐ฉ3โค1๐ฅฐ1
Forwarded from ใตใคใใฏใน
Implement-SUSFS-v1.5.4-for-KernelSU-Next.patch
50.2 KB
This is it! SUSFS v1.5.4 universal patch for KernelSU Next for both GKI and Non-GKI kernels.
if you don't know how to patch just wait for the SUSFS branch of KernelSU Next...
Note: This patch is only for KernelSU Next Submodule side only. you need to do your patches on the kernel side
if you don't know how to patch just wait for the SUSFS branch of KernelSU Next...
Note: This patch is only for KernelSU Next Submodule side only. you need to do your patches on the kernel side
๐ฅ43๐7๐คฏ6๐ฉ4โค2
๐15๐ฅฐ5๐ฉ5โค3
Added next-susfs universal patched branch (NON-GKI/GKI)
๐ฅ80๐16โค11๐ฉ5๐ฅฐ4๐ฟ4๐3
kernel: upstream susfs v1.5.5 (patch by @sidex15 & susfs by @simonpunk)
https://github.com/rifsxd/KernelSU-Next/commit/81dff86d0298da936024c9702f4db01fde1f7200
https://github.com/rifsxd/KernelSU-Next/commit/81dff86d0298da936024c9702f4db01fde1f7200
GitHub
kernel: upstream susfs v1.5.5 (patch by @sidex15 & susfs by @simonpunk) ยท KernelSU-Next/KernelSU-Next@81dff86
An advanced Kernel based root solution for Android - kernel: upstream susfs v1.5.5 (patch by @sidex15 & susfs by @simonpunk) ยท KernelSU-Next/KernelSU-Next@81dff86
๐ฅ34๐15๐ฉ4
Forwarded from user 4626632400
KSU should add a warning to NON-GKI integration:
# Please disable RKP KDP and UH; their drivers cause a kernel panic when the escape to root function is called in fs/namespace.c
โค14๐4๐ฉ4๐ฅ2๐ฅฐ2
Forwarded from user 4626632400
Samsung/exynos specific
๐คฃ30๐ฉ3๐ฟ3๐2
Can you all overlayfs users test the latest CI manager (https://t.me/ksunext_group/24847) and report the results back? Also you need to delete the old modules.img and modules_update.img and install new modules and give feedback about speed or if something goes wrong.
๐15๐ฉ5
KernelSU Next
Can you all overlayfs users test the latest CI manager (https://t.me/ksunext_group/24847) and report the results back? Also you need to delete the old modules.img and modules_update.img and install new modules and give feedback about speed or if somethingโฆ
You have to test instead of me because my device is still bootloader locked ๐
๐ฅ15๐ฉ10๐6๐ฟ6โค1
ksud_overlayfs: fix sparse image journal size being 0 block and cause error to format into ext4 with mke2fs
https://github.com/rifsxd/KernelSU-Next/commit/fcc4f0d206427568f09f7391d707797efa4aaa8d
https://github.com/rifsxd/KernelSU-Next/commit/fcc4f0d206427568f09f7391d707797efa4aaa8d
GitHub
ksud_overlayfs: fix sparse image journal size being 0 block and causeโฆ ยท rifsxd/KernelSU-Next@fcc4f0d
โฆ error to format into ext4 with mke2fs
๐18๐ฉ6โค3
A little but in-depth of the situation with wrong context
๐14๐8๐5๐ค4๐
3๐ฆ2โค1