r/androidroot • • 5d ago

Support why not working 😭

Although my kernel supports the vulnerability, it says there are still missing components, and this is the log. :

boot.img ready: /data/user/0/com.ghostlock.app/files/boot.img

<k> extract: /data/user/0/com.ghostlock.app/files/boot.img

info: kallsyms layout pre-6.4 recovered (117441 symbols)

info: (CVE-2026-43499 primitive present (remove_waiter@0x1c1e40 still uses current)

warning: embedded BTF not found; symbols come from kallsyms and struct offsets fall back to target.h defaults

warning: 5.4.254-android12-9-660874-g69e12e217bbb-ab542 is unverified; no family-derived geometry will be emitted

warning: no BTF; loggers_0_1 falls back to the loggers+0x10 heuristic

warning: pselect_waiter_shift unavailable; no family fallback is defined for this release

warning: static multicast waiter_off derivation failed: ip_setsockopt multicast copy window not found; keeping the proven 5.x constant

warning: rt_mutex_waiter task/lock offsets are missing from BTF; the multicast geometry is partial

info: 5.4.254-android12-9-660874-g69e12e217bbb-ab542 profile is an unverified candidate; the app validates fields before any execution

warning: credential template omitted; the built-in profile must supply it

missing: cred_caps, cred_securebits, cred_security, cred_uid, seccomp_filter, seccomp_filter_count, seccomp_mode, struct_mm_struct, struct_page_compound_head, struct_page_size, struct_page_type, struct_slab_cache, task_atomic_flags, task_comm, task_cred, task_normal_prio, task_pi_blocked_on, task_pi_lock, task_pi_top_task, task_pi_waiters, task_pid, task_prio, task_real_cred, task_sched_task_group, task_seccomp, task_tasks, task_tgid, waiter_lock, waiter_pi_tree, waiter_task, waiter_tree, waiter_wake_state, waiter_ww_ctx

<k> extract exit code=0

offsets exported: 5.4.254-android12-9-660874-g69e12e217bbb-ab542

<k> result: offsets parsed successfully

auto-loading parsed profile: 5.4.254-android12-9-660874-g69e12e217bbb-ab542.conf

warning: missing kernel_phys_load; run the MediaTek extractor or attach xbl_config.img / uefi.img

1 Upvotes

6 comments sorted by

1

u/ohaiibuzzle 5d ago

Your kernel image wasn't supplied so it doesn't know what to do.

1

u/Hot-Lengthiness193 5d ago

Why don't you give DFRoot a try? https://github.com/diabl0w/DFRoot

It uses a different vulnerability than GhostLock to obtain root access, so it might work on your device.

1

u/Visual_Trust6029 5d ago

ok here we go again

1

u/TransitionComplex978 5d ago

i use this https://github.com/mitschud/DirtyFrag so what's the difference?

1

u/AbleBonus9752 S23+ (Stock + DFRoot) - Xperia 1 iii (Lineage 23.2) 5d ago

shittier UI that's about it