Successful patch with questionable "no symbol", not booting. Awaiting untested builds

[TheK0tYaRa]

Currently, there is no immediate solution. You need to troubleshoot it yourself or provide the device to me for further investigation.

As i am aware, i feel like getting my phone experimented on. While i can't send it to you or finance it's ownership, i can instead test on it for you.

The following is the output of kptools:

> ../kptools-linux -p --image kernel-b --skey 'test' --kpimg ../kpimg-android --out kernel
[+] kernel image_size: 0x02433010
[+] kernel uefi header: false
[+] kernel load_offset: 0x00080000
[+] kernel kernel_size: 0x02a48000
[+] kernel page_shift: 12
[+] new kernel image ...
[+] linux_banner 1: Linux version 4.14.355-SN-1.7.2-LB (thek0tyara@sus) (Neutron clang version 19.0.0git (https://github.com/llvm/llvm-project.git fd3eaf76ba3392a4406247d996e757ef49f7a8b2), Neutron LLD 19.0.0) #1 SMP PREEMPT Thu Jan 23 20:30:59 EET 2025
[+] linux_banner offset: 0xe5000f
[+] kernel version major: 4, minor: 14, patch: 255
[+] kallsyms_token_table offset: 0x012b2720
[+] endian: little
[+] kallsyms_token_index offset: 0x012b2a98
[+] find arm64 relocation kernel_va: 0xffffff8008080000
[+] find arm64 relocation table range: [0x01f64b18, 0x02256910), count: 0x0001f695
[+] apply 0x0001f694 relocation entries
[+] kallsyms_markers range: [0x012b1ab8, 0x012b2720), count: 0x0000018d
[+] approximate kallsyms_offsets range: [0x01100048, 0x011632b4) count: 0x00018c9b
[+] kallsyms_names offset: 0x011632c0
[+] kallsyms_num_syms offset: 0x011632b8, value: 0x00018c9a
[+] names table linux_banner index: 0x0000bc10
[+] linux_banner index: 0
[+] kallsyms_offsets offset: 0x01100048
[+] layout kimg: 0x0,0x2433010, kpimg: 0x2434000,0x27f80, extra: 0x245bf80,0x80, end: 0x245c000, start: 0x2a48000
[+] kpimg version: a07
[+] kpimg compile time: 12:16:35 May  1 2024
[+] kpimg config: android, release
[+] tcp_init_sock: type: T, offset: 0x00ce8ef0
[+] map_start: 0xce8ef0, max_size: 0x800
[+] kallsyms_lookup_name: type: T, offset: 0x000f7d8c
[+] printk: type: T, offset: 0x000afab8
[+] memblock_reserve: type: T, offset: 0x001e373c
[+] memblock_free: type: T, offset: 0x001e36a8
[+] memblock_mark_nomap: type: T, offset: 0x001e39c0
[?] no symbol: memblock_phys_alloc_try_nid
[+] memblock_virt_alloc_try_nid: type: T, offset: 0x014f0204
[+] memblock_alloc_try_nid: type: T, offset: 0x014efde0
[+] panic: type: T, offset: 0x0002ed50
[+] rest_init: type: t, offset: 0x00e3a768
[+] kernel_init: type: t, offset: 0x00e3a83c
[?] no symbol: report_cfi_failure
[?] no symbol: __cfi_slowpath_diag
[?] no symbol: __cfi_slowpath
[+] copy_process: type: t, offset: 0x0002bd98
[+] do_execveat_common: type: t, offset: 0x002195b4
[?] no symbol: __do_execve_file
[?] no symbol: do_execve_common
[?] no symbol: do_faccessat
[?] no symbol: __arm64_sys_faccessat
[+] sys_faccessat: type: T, offset: 0x0020afac
[?] no symbol: __arm64_sys_faccessat2
[?] no symbol: sys_faccessat2
[?] no symbol: __arm64_sys_newfstatat
[+] sys_newfstatat: type: T, offset: 0x002161d4
[+] vfs_statx: type: T, offset: 0x00215fc4
[?] no symbol: vfs_fstatat
[+] avc_denied: type: t, offset: 0x0042179c
[+] slow_avc_audit: type: T, offset: 0x00420704
[+] input_handle_event: type: t, offset: 0x0089421c
[+] superkey: test
[+] paging_init: type: T, offset: 0x014d6e88
[+] patch done: kernel

The end result is device stuck on logo (not bootlooping). The same happens on attempt to boot to recovery. Also, the powered off charging animation gets frozen after appearing before it shows battery percentage. I have built the kernel locally and it works before the patching process. Feel free to guide me to patch kernel sources or change kernel config in some way as i can do that good enough for it to boot.

[TheK0tYaRa]

APatch/issues/873 seems to be the closest case match i have found so far