KernelSU-Next v1.0.8 is Released!
Key Changes :-
- Full manager UI overhaul
- Flash zip by opening it with manager
- Module banners
- Better mount system persistence
- Amoled mode
- Better throne tracker
- LKM mode is restored
- Superuser list improvements
- Fixed module flash rotation bug
- Output full logs on actions, lkm install and module flash with developer options on
- module card indicators for usefull info
- update count indicator in status card
- sucompat disabled indicator in status card && disable module/superuser screens if no sucompat
- And much more...
https://github.com/KernelSU-Next/KernelSU-Next/releases/tag/v1.0.8
Key Changes :-
- Full manager UI overhaul
- Flash zip by opening it with manager
- Module banners
- Better mount system persistence
- Amoled mode
- Better throne tracker
- LKM mode is restored
- Superuser list improvements
- Fixed module flash rotation bug
- Output full logs on actions, lkm install and module flash with developer options on
- module card indicators for usefull info
- update count indicator in status card
- sucompat disabled indicator in status card && disable module/superuser screens if no sucompat
- And much more...
https://github.com/KernelSU-Next/KernelSU-Next/releases/tag/v1.0.8
GitHub
Release v1.0.8 Β· KernelSU-Next/KernelSU-Next
Key Changes
Full manager UI overhaul
Flash zip by opening it with manager
Module banners
Better mount system persistence
Amoled mode
Better throne tracker
LKM mode is restored
Superuser list impro...
Full manager UI overhaul
Flash zip by opening it with manager
Module banners
Better mount system persistence
Amoled mode
Better throne tracker
LKM mode is restored
Superuser list impro...
π₯79β€22π11π2π1
Hello.
I got something to announce that I will stop maintaining next-susfs and next-susfs-dev branches since it's really tiring to maintain those branches without errors and having to support both non-gki gki universal support, since susfs has dropped non-gki it's tough to maintain and backport, so I would want the users to patch it themselves for their devices on top of next branch, I wouldn't suggest you using next branch directly for your workflows to patch so you should use the stable tags instead for example 1.0.8 since they are still code and won't be having any changes constantly like in next branches which will break your cloud build workflow.
And I would just suggest non gki susfs users to use their specific patches instead of trying to backport from susfs gki branches since it's not really meant for non gki.
I got something to announce that I will stop maintaining next-susfs and next-susfs-dev branches since it's really tiring to maintain those branches without errors and having to support both non-gki gki universal support, since susfs has dropped non-gki it's tough to maintain and backport, so I would want the users to patch it themselves for their devices on top of next branch, I wouldn't suggest you using next branch directly for your workflows to patch so you should use the stable tags instead for example 1.0.8 since they are still code and won't be having any changes constantly like in next branches which will break your cloud build workflow.
And I would just suggest non gki susfs users to use their specific patches instead of trying to backport from susfs gki branches since it's not really meant for non gki.
β€62π’37π14π2πΏ2
What do you rate the new v1.0.8 update on the scale of 1 to 10
Anonymous Poll
60%
10
11%
9
7%
8
5%
7
2%
6
3%
5
1%
4
1%
3
0%
2
10%
1
β€54π5π―4π₯2π2π2π2
If you like the new update and found it useful with the new improvements and features then feel free to donate to the project to show love. π
https://github.com/KernelSU-Next/KernelSU-Next/tree/v1.0.8?tab=readme-ov-file#donations
or if wanna use binance then use the QR Code.
Thanks for your support and showing love. β₯οΈ
https://github.com/KernelSU-Next/KernelSU-Next/tree/v1.0.8?tab=readme-ov-file#donations
or if wanna use binance then use the QR Code.
Thanks for your support and showing love. β₯οΈ
GitHub
GitHub - KernelSU-Next/KernelSU-Next at v1.0.8
An advanced Kernel based root solution for Android - GitHub - KernelSU-Next/KernelSU-Next at v1.0.8
β€40πΏ5π₯2π2
Now imma enjoy my vacation see ya all next month
π56β€20π15π4π€3π2π₯°1π1
A bit of info for susfs users,
You are highly encouraged to not use kprobes + sus_su along with v1.0.8, sus_su will conflict with sucompat
Post version v1.0.8 ksunext will provide manual hooks for its kernels directly so I suggest you use manual hooks too plus its much better and more hidden
You are highly encouraged to not use kprobes + sus_su along with v1.0.8, sus_su will conflict with sucompat
Post version v1.0.8 ksunext will provide manual hooks for its kernels directly so I suggest you use manual hooks too plus its much better and more hidden
π54β€21πΏ7π2π2
Forwarded from KernelSU Next CI
I accidentally nuked all of the ci messages
πΏ66π9π4π4π2
Anyways the ci can still be found with https://nightly.link/KernelSU-Next/KernelSU-Next/workflows/build-manager-ci/next/Manager
πΏ27β€2
Media is too big
VIEW IN TELEGRAM
Now the available module update count will be shown as badge
π₯°39πΏ7π6
Forwarded from Modulπ
ΎοΈs #AntiRetardModules
BREAKING: Integrity Box is gone from face of GitHub, for good
GitHub is NOT playing around when it comes to its TOS, determined that module author rename from
All source code and releases included in the repo have been deleted forever.
π§βπ» @modulosdec
GitHub is NOT playing around when it comes to its TOS, determined that module author rename from
Meowna to Rifsxd's mother is violating TOS.All source code and releases included in the repo have been deleted forever.
π§βπ» @modulosdec
π₯79π21π12β€5
Anyways enough trolling since dirt is off of github now i reverted back the commit,
the whole purpose of the commit was to troll and ragebait, why? i was bored af :D
please give real and useful feature ideas, only in github issues tab
the whole purpose of the commit was to troll and ragebait, why? i was bored af :D
please give real and useful feature ideas, only in github issues tab
π37π16πΏ9β€3π3π₯1π«‘1
Added the ability to patch lkm to newer xiaomi vendor_boot which came with kernel 6.6
Do test LKM for both init_boot and vendor_boot for devices which doesnt come with init_boot
https://github.com/KernelSU-Next/KernelSU-Next/commit/0beea57ab7817ef2088a34fc9ae7ad6755492a79
Do test LKM for both init_boot and vendor_boot for devices which doesnt come with init_boot
https://github.com/KernelSU-Next/KernelSU-Next/commit/0beea57ab7817ef2088a34fc9ae7ad6755492a79
GitHub
ksud: test vendor_boot patching for some newer devices Β· KernelSU-Next/KernelSU-Next@0beea57
An advanced Kernel based root solution for Android - ksud: test vendor_boot patching for some newer devices Β· KernelSU-Next/KernelSU-Next@0beea57
π₯28π6β€5