RKSU Updates – Telegram
RKSU Updates
2.31K subscribers
100 photos
696 files
813 links
Streamlined with upstream, but with Non-GKI support.

Supported Kernel: 4.4 ~ 6.18+

Update channel for rsuntk's KernelSU fork.
Managed by: @RissuDesu @lptxda_bot
Download Telegram
KernelSU_v3.0.0-10-legacy-45-gebe59fc1_32329-release.apk
8.9 MB
Manager
#ci_2329
kernel, ksud: Update KSU_UMOUNT_GETLIST (#235)

Proper update, since we merged stale pr.

* ksu toolkit (for ksud ref):
https://github.com/backslashxx/ksu_toolkit/blob/bdf37bca24d912f1d13d6af7b613ca80dc7a74bb/src/toolkit.c#L188
* up (typedef changes):
https://github.com/backslashxx/KernelSU/commit/e234346c10ed9619b3084da18a90e49fad15ebf4

Signed-off-by: backslashxx <118538522+backslashxx@users.noreply.github.com>
Signed-off-by: rsuntk <rissu.ntk@gmail.com>
Co-authored-by: backslashxx <118538522+backslashxx@users.noreply.github.com>

Commit
Workflow run
KernelSU_v3.0.0-10-legacy-45-gebe59fc1-spoofed_32329-release.apk
8.9 MB
Spoofed Manager
#ci_2329
kernel, ksud: Update KSU_UMOUNT_GETLIST (#235)

Proper update, since we merged stale pr.

* ksu toolkit (for ksud ref):
https://github.com/backslashxx/ksu_toolkit/blob/bdf37bca24d912f1d13d6af7b613ca80dc7a74bb/src/toolkit.c#L188
* up (typedef changes):
https://github.com/backslashxx/KernelSU/commit/e234346c10ed9619b3084da18a90e49fad15ebf4

Signed-off-by: backslashxx <118538522+backslashxx@users.noreply.github.com>
Signed-off-by: rsuntk <rissu.ntk@gmail.com>
Co-authored-by: backslashxx <118538522+backslashxx@users.noreply.github.com>

Commit
Workflow run
KernelSU_v3.0.0-10-legacy-46-g2d745415_32330-release.apk
8.9 MB
Manager
#ci_2330
ksud: Remove 8MB total_size  assert

Reason:
"nah, the reason is that alloca allocations happen on stack
and stack space is constant on linux

if youre using heap (mmap, brk) then theres no need, heap memory is practically unlimited"

Co-authored-by: backslashxx <118538522+backslashxx@users.noreply.github.com>
Signed-off-by: rsuntk <rissu.ntk@gmail.com>

Commit
Workflow run
KernelSU_v3.0.0-10-legacy-46-g2d745415-spoofed_32330-release.apk
8.9 MB
Spoofed Manager
#ci_2330
ksud: Remove 8MB total_size  assert

Reason:
"nah, the reason is that alloca allocations happen on stack
and stack space is constant on linux

if youre using heap (mmap, brk) then theres no need, heap memory is practically unlimited"

Co-authored-by: backslashxx <118538522+backslashxx@users.noreply.github.com>
Signed-off-by: rsuntk <rissu.ntk@gmail.com>

Commit
Workflow run
2
Mr bindhost
KernelSU_v3.0.0-10-legacy-47-g0482abcb-spoofed_32331-release.apk
8.9 MB
Spoofed Manager
#ci_2331
manager: build(deps): Bump miuix to 0.7.2

Signed-off-by: rsuntk <rissu.ntk@gmail.com>

Commit
Workflow run
KernelSU_v3.0.0-10-legacy-47-g0482abcb_32331-release.apk
8.9 MB
Manager
#ci_2331
manager: build(deps): Bump miuix to 0.7.2

Signed-off-by: rsuntk <rissu.ntk@gmail.com>

Commit
Workflow run
KernelSU_v3.0.0-10-legacy-49-g44d9142a-spoofed_32333-release.apk
8.9 MB
Spoofed Manager
#ci_2333
kernel: fix compilation error

* Yeah, forgot to check that

Signed-off-by: rsuntk <rissu.ntk@gmail.com>

Commit
Workflow run
KernelSU_v3.0.0-10-legacy-49-g44d9142a_32333-release.apk
8.9 MB
Manager
#ci_2333
kernel: fix compilation error

* Yeah, forgot to check that

Signed-off-by: rsuntk <rissu.ntk@gmail.com>

Commit
Workflow run
KernelSU_v3.0.0-30-legacy-spoofed_32334-release.apk
8.9 MB
Spoofed Manager
#ci_2334
kernel: CRIT: fix kernel safe_mode (#236)

* Apparently it just a borked logic. We shouldn't check already_post_fs_data on ksu_is_safe_mode..

Signed-off-by: rsuntk <rissu.ntk@gmail.com>

Commit
Workflow run
KernelSU_v3.0.0-30-legacy-spoofed_32334-release.apk
8.9 MB
Spoofed Manager
#ci_2334
kernel: CRIT: fix kernel safe_mode (#236)

* Apparently it just a borked logic. We shouldn't check already_post_fs_data on ksu_is_safe_mode..

Signed-off-by: rsuntk <rissu.ntk@gmail.com>

Commit
Workflow run
KernelSU_v3.0.0-30-legacy_32334-release.apk
8.9 MB
Manager
#ci_2334
kernel: CRIT: fix kernel safe_mode (#236)

* Apparently it just a borked logic. We shouldn't check already_post_fs_data on ksu_is_safe_mode..

Signed-off-by: rsuntk <rissu.ntk@gmail.com>

Commit
Workflow run
KernelSU_v3.0.0-30-legacy_32334-release.apk
8.9 MB
Manager
#ci_2334
kernel: CRIT: fix kernel safe_mode (#236)

* Apparently it just a borked logic. We shouldn't check already_post_fs_data on ksu_is_safe_mode..

Signed-off-by: rsuntk <rissu.ntk@gmail.com>

Commit
Workflow run
[Mode aman] = Safe Mode

Yeah, it works now.. I just lose my last brain cell trying to figuring out what's wrong.
susfs-rksu-master has been synced with main branch (32334)
Some tags has been removed because of this fatal bug. Advised to update your kernel build immedietly.
KernelSU_v3.0.0-30-legacy-2-g08aab497_32336-release.apk
8.9 MB
Manager
#ci_2336
kernel, ci: Add format check for kernel

* This commit is squashed

Co-authored-by: dabao1955 <dabao1955@163.com>
Co-authored-by: 5ec1cff <56485584+5ec1cff@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Signed-off-by: rsuntk <rissu.ntk@gmail.com>

Commit
Workflow run
KernelSU_v3.0.0-30-legacy-2-g08aab497-spoofed_32336-release.apk
8.9 MB
Spoofed Manager
#ci_2336
kernel, ci: Add format check for kernel

* This commit is squashed

Co-authored-by: dabao1955 <dabao1955@163.com>
Co-authored-by: 5ec1cff <56485584+5ec1cff@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Signed-off-by: rsuntk <rissu.ntk@gmail.com>

Commit
Workflow run
KernelSU_v3.0.0-30-legacy-3-g48299d84_32337-release.apk
8.9 MB
Manager
#ci_2337
kernel: allow sys_read hook

Signed-off-by: rsuntk <rissu.ntk@gmail.com>

Commit
Workflow run
1
KernelSU_v3.0.0-30-legacy-3-g48299d84-spoofed_32337-release.apk
8.9 MB
Spoofed Manager
#ci_2337
kernel: allow sys_read hook

Signed-off-by: rsuntk <rissu.ntk@gmail.com>

Commit
Workflow run