Repository navigation
docs(profiles): add Xiaomi 15 to the 6.6.118 gc44b714366cc row - #653
Merged
Merged
Conversation
Verified on-device: Xiaomi 15 (dada, 24129PN74C), HyperOS 3.0.307.0.WOCCNXM, kernel 6.6.118-android15-8-gc44b714366cc-abogki519650608-4k. The shipped profile reaches uid 0 and loads the KernelSU module via the Shizuku flow.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds Xiaomi 15 to the existing row for
6.6.118-android15-8-gc44b714366cc-abogki519650608-4kin bothSUPPORTED_DEVICES.mdandSUPPORTED_DEVICES_ZH.md.No profile change: the kernel string matches a shipped profile exactly, so it is the same image the REDMI K80 Pro / Turbo 5 Max, POCO X8 Pro Max and Xiaomi Pad 7 Ultra already run. Only the device list was missing it.
Device
uname -r6.6.118-android15-8-gc44b714366cc-abogki519650608-4k/proc/cmdline)dada:15/OS3.0.307.0.WOCCNXM:userVerification
Route resolved from the built-in profile (
select_stack,waiter_shift = -2), CPU pair main 6 / consumer 7.[+] SELinux permissive/ later runs start with[+] SELinux already permissive.child uid = 0→[+] child is root!.uid=2000 Seccomp=0),[+] no app seccomp filter (adb/shell flow); skipping W3.uid=0 euid=0 seccomp=0,ksudresolved fromme.weishu.kernelsu, module late-loaded (policyload before=0 after=2), native exitedcode=0. Root confirmed on-device afterwards.Debug logs are available on request (
.log.txt,profile.conf,profile.bin,ksu.logper attempt).Two observations, for your call
Shizuku was required in practice on this build. Direct (non-Shizuku) runs reached
child is root!but then died in W3: the 4leaf dirprobes all returnedret=4(comm untouched) and the process was eventually SIGKILLed. I did not touch the profile —recommend_shizukuis shared with the other devices on this row, so I left it at0and turned the switch on manually. If you would rather advertise it, tell me how you want it expressed (a parenthetical in the device cell, or a separate profile for the Xiaomi 15) and I will rework the patch.Landing rate on this build looks like ~1 in 12
selectcalls.pselect post-select … ret=8always coincides with the write landing (SELinux permissive/child uid = 0), whileret=4returnsstatus=0 success=1without changing the target. W2 needed 12 attempts to land; W3's probe budget is 4, which is why the shell flow is the practical path here. This is a native/attack-path observation, so I am not proposing changes for it — just flagging it in case it matches other reports on this kernel.Chinese summary: 小米 15（dada，HyperOS 3.0.307.0.WOCCNXM，内核
6.6.118-android15-8-gc44b714366cc-abogki519650608-4k）实测可用，已加入支持列表；未改动 profile。实测需通过 Shizuku 运行（直连模式在 W3 阶段失败）。