bmax121
Redmi12c 刷入成功，无限重启，不能启动
机器：redmi12c 系统：Global HyperOS 1.0.3.0.UCVMIXM 安卓版本：14 现象：apatch app修补和命令行修改刷入都成功，无法启动，卡开机redmi图标页，然后循环重启。falsh 原始 boot 后正常恢复。
D:\Android\apatch\bin>magiskboot.exe unpack boot.img Parsing image: [boot.img] HEADER_VER [2] KERNEL_SZ [12629877] RAMDISK_SZ [16214206] SECOND_SZ [0] RECOV_DTBO_SZ [0] DTB_SZ [147873] OS_VERSION [12.0.0] OS_PATCH_LEVEL [2024-02] PAGESIZE [2048] NAME [] CMDLINE [bootopt=64S3,32N2,64N2 buildvariant=user] CHECKSUM [b9dc94633e5012aaebfb1664b8fcd57988391a26000000000000000000000000] KERNEL_FMT [gzip] RAMDISK_FMT [gzip] VBMETA
D:\Android\apatch\bin>kptools-msys2.exe -p --image kernel-b --skey "everyday123" --kpimg kpimg-android --out kernel [-] common.c:43/read_file_align(); open file kernel-b
- No such file or directory
D:\Android\apatch\bin>kptools-msys2.exe -p --image kernel-b --skey "everyday123" --kpimg kpimg-android --out kernel [+] kernel image_size: 0x01b70000 [+] kernel uefi header: false [+] kernel load_offset: 0x00080000 [+] kernel kernel_size: 0x01fda000 [+] kernel page_shift: 12 [+] new kernel image ... [+] linux_banner 1: Linux version 4.19.191-perf-g75e060e5bed0 (builder@pangu-build-component-vendor-235584-kg0px-b2979-5qhmc) (Android (6443078 based on r383902) clang version 11.0.1 (https://android.googlesource.com/toolchain/llvm-project b397f81060ce6d701042b782172ed13bee898b79), LLD 11.0.1 (/buildbot/tmp/tmp6_m7QH b397f81060ce6d701042b782172ed13bee898b79)) #1 SMP PREEMPT Fri Feb 2 12:24:53 UTC 2024 [+] linux_banner offset: 0x1040018 [+] kernel version major: 4, minor: 19, patch: 191 [+] kallsyms_token_table offset: 0x012ef700 [+] endian: little [+] kallsyms_token_index offset: 0x012efb00 [+] find arm64 relocation kernel_va: 0xffffffffffffffff [?] can't find arm64 relocation table [+] kallsyms_markers range: [0x012eef00, 0x012ef638), count: 0x000000e7 [?] find approximate kallsyms_offsets error [+] approximate kallsyms_addresses range: [0x011c0a00, 0x01233b08) count: 0x0000e621 [+] kallsyms_names offset: 0x01233d00 [+] kallsyms_num_syms offset: 0x01233c00, value: 0x0000e621 [?] no linux_banner? maybe CONFIG_KALLSYMS_ALL=n? [+] names table vector index: 0x00000012, pid_vnr index: 0x00000553 [+] pid_vnr verfied succeed, sp, insn: 0x910003fd [+] vectors offset: 0x00003800 [+] pid_vnr offset: 0x0005ea14 [+] kallsyms_addresses offset: 0x011c0b60 [+] layout kimg: 0x0-0x1b70000, kpimg: 0x1b70000,0x27f50, extra: 0x1b97f50,0x80, end: 0x1b97fd0, start: 0x1fda000 [+] kpimg version: a05 [+] kpimg compile time: 05:31:46 Apr 8 2024 [+] kpimg config: android, release [+] tcp_init_sock: type: T, offset: 0x00e707f4 [+] map_start: 0xe70800, max_size: 0x800 [+] kallsyms_lookup_name: type: T, offset: 0x000f3ad0 [+] printk: type: T, offset: 0x000ab898 [+] memblock_reserve: type: T, offset: 0x001d2b18 [+] memblock_free: type: T, offset: 0x001d297c [+] memblock_mark_nomap: type: T, offset: 0x001d3180 [?] no symbol: memblock_phys_alloc_try_nid [+] memblock_virt_alloc_try_nid: type: T, offset: 0x015bb844 [+] memblock_alloc_try_nid: type: T, offset: 0x015bb494 [+] panic: type: T, offset: 0x00034170 [+] rest_init: type: t, offset: 0x01027b38 [+] kernel_init: type: t, offset: 0x01027b8c [?] no symbol: report_cfi_failure [?] no symbol: __cfi_slowpath_diag [?] no symbol: __cfi_slowpath [+] copy_process: type: t, offset: 0x00033010 [+] avc_denied: type: t, offset: 0x003f4cd0 [+] slow_avc_audit: type: T, offset: 0x003f4068 [+] input_handle_event: type: t, offset: 0x00b11df0 [+] superkey: everyday123 [+] paging_init: type: T, offset: 0x015a5f44 [+] patch done: kernel
D:\Android\apatch\bin>magiskboot.exe repack boot.img Parsing image: [boot.img] HEADER_VER [2] KERNEL_SZ [12629877] RAMDISK_SZ [16214206] SECOND_SZ [0] RECOV_DTBO_SZ [0] DTB_SZ [147873] OS_VERSION [12.0.0] OS_PATCH_LEVEL [2024-02] PAGESIZE [2048] NAME [] CMDLINE [bootopt=64S3,32N2,64N2 buildvariant=user] CHECKSUM [b9dc94633e5012aaebfb1664b8fcd57988391a26000000000000000000000000] KERNEL_FMT [gzip] RAMDISK_FMT [gzip] VBMETA Repack to image: [new-boot.img] HEADER_VER [2] KERNEL_SZ [12679937] RAMDISK_SZ [16164647] SECOND_SZ [0] RECOV_DTBO_SZ [0] DTB_SZ [147873] OS_VERSION [12.0.0] OS_PATCH_LEVEL [2024-02] PAGESIZE [2048] NAME [] CMDLINE [bootopt=64S3,32N2,64N2 buildvariant=user] CHECKSUM [efeb82178c589928e37d9db7b348e513358855f0000000000000000000000000]
D:\Android\apatch\bin>ls boot.img kernel kpimg-android magiskboot.exe new-boot.img dtb kernel-b kptools-msys2.exe msys-2.0.dll ramdisk.cpio
D:\Android\apatch\bin>adb reboot bootloader
can you get the panic logs, in the floder: /data/adb/ap/log and /sys/fs/pstore
can you get the panic logs, in the floder: /data/adb/ap/log and /sys/fs/pstore
I try to get the panic logs, in the floder: /data/adb/ap/log and /sys/fs/pstore, but Permission denied.
Then I install magisk and pull log. /data/adb/ap/log： not exist.
/sys/fs/pstore: pstore.zip