APatch on Samsung Galaxy S20 FE 5G with LineageOS 23.2 did not work

[gc-cacher]

Hello,
I tried to patch the boot.img with the current version of APatch and then flash it with Odin. Unfortunately, this did not work. APatch does not recognize the patched boot.img.

I exported the logs and attached them here.

APatch Boot Image Patcher log.txt

APatch_bugreport_2026-02-11_12_24.tar.gz

When patching, the following is displayed:

---

---

APatch Boot Image Patcher

---

• Backing boot.img
• Patching kernel

• ./kptools -p -i kernel.ori -S apatchk3y -k kpimg -o kernel
  [+] kernel image_size: 0x02f76818
  [+] kernel uefi header: false
  [+] kernel load_offset: 0x00080000
  [+] kernel kernel_size: 0x04124000
  [+] kernel page_shift: 12
  [+] new kernel image ...
  [+] linux_banner 1: Linux version 4.19.325-cip128-st12-perf-g0b81c603edde (root@011cf93641cd) (Android (14054515, +pgo, +bolt, +lto, +mlgo, based on r563880c) clang version 21.0.0 (https://android.googlesource.com/toolchain/llvm-project 5e96669f06077099aa41290cdb4c5e6fa0f59349), LLD 21.0.0 (/mnt/disks/build-disk/src/googleplex-android/llvm-r563880-release/out/llvm-project/llvm 5e96669f06077099aa41290cdb4c5e6fa0f59349)) 在编译bootimgtools时候缺少很多依赖 #1 SMP PREEMPT Tue Feb 10 03:24:08 UTC 2026
  [+] linux_banner offset: 0x1980018
  [+] kernel version major: 4, minor: 19, patch: 255
  [+] kallsyms_token_table offset: 0x0238b600
  [+] endian: little
  [+] kallsyms_token_index offset: 0x0238ba00
  [+] arm64 relocation kernel_va: 0xffffffffffffffff
  [?] can't find arm64 relocation table
  [+] kallsyms_markers range: [0x0238a200, 0x0238b510), count: 0x00000261
  [+] approximate kallsyms_offsets range: [0x020ddde0, 0x021763d4) count: 0x0002617d
  [+] kallsyms_names offset: 0x02176600
  [+] kallsyms_num_syms offset: 0x02176500, value: 0x00026175
  [+] names table linux_banner index: 0x000129f8
  [+] linux_banner index: 0
  [+] kallsyms_offsets offset: 0x020dde00
  [+] pid_vnr: type: T, offset: 0x00066b38
  [+] pid_vnr verfied sp_el0, insn: 0xd5384108
  [+] layout kimg: 0x0,0x2f76818, kpimg: 0x2f77000,0x2c100, extra: 0x2fa3100,0x80, end: 0x2fa3180, start: 0x4124000
  [+] kpimg version: c02
  [+] kpimg compile time: 06:48:58 Nov 12 2025
  [+] kpimg config: android, release
  [+] tcp_init_sock: type: T, offset: 0x0166d454
  [+] map_start: 0x166d460, max_size: 0x800
  [+] kallsyms_lookup_name: type: T, offset: 0x0010c634
  [+] printk: type: T, offset: 0x0187d190
  [+] memblock_reserve: type: T, offset: 0x0022a18c
  [+] memblock_free: type: T, offset: 0x0022a0f4
  [+] memblock_mark_nomap: type: T, offset: 0x0022a404
  [?] no symbol: memblock_phys_alloc_try_nid
  [+] memblock_virt_alloc_try_nid: type: T, offset: 0x029a27ec
  [+] memblock_alloc_try_nid: type: T, offset: 0x029a2490
  [+] panic: type: T, offset: 0x0187b954
  [+] rest_init: type: t, offset: 0x0193d38c
  [+] kernel_init: type: t, offset: 0x0193d468
  [?] no symbol: report_cfi_failure
  [?] no symbol: __cfi_slowpath_diag
  [?] no symbol: __cfi_slowpath
  [+] copy_process: type: t, offset: 0x0003cef0
  [+] avc_denied: type: t, offset: 0x004804ec
  [+] slow_avc_audit: type: T, offset: 0x0047f658
  [+] input_handle_event: type: t, offset: 0x00a1993c
  [+] root superkey hash: 6c29a31176bbcb1c36690c30b133cb2e20b4a5d3b506aefb66f3ec3fe2d98656
  [+] paging_init: type: T, offset: 0x029885e4
  [+] patch done: kernel
• patch_rc=0
• set +x

• Repacking boot image
• Successfully Patched!
  Output file is written to
  /storage/emulated/0/Download/apatch_patched_11142_0.12.2_fuki.img

---

Does anyone have an idea where the problem is?