Home Forum Blog Private Support Courses Archive
Our courses are now on YouTube! Start Watching
Hovatek Forum OPERATING SYSTEMS Android [Please help] TWRP build boots to kernel panic on Realme C51 (RMX3830) — "Attempted to kill init!"

[Please help] TWRP build boots to kernel panic on Realme C51 (RMX3830) — "Attempted to kill init!"

[Please help] TWRP build boots to kernel panic on Realme C51 (RMX3830) — "Attempted to kill init!"

leanmi
leanmi
leanmi
Newbie
2
14-07-2026, 12:46 AM
#1



Device: Realme C51 (RMX3830)
Chipset: Unisoc UMS9230 / Tiger T612 (qogirl6)
Android version: 15
Build fingerprint: ums9230_hulk_Natv_k515-user-gms_QOGIRL6_hulk_SIGN
Build work ID / link: https://tools.hovatek.com/twrpbuildertoo...r_boot.img
Image type used for build: boot.img + vendor_boot.img (stock, extracted from full .pac firmware, Android 15 build)
Resolution entered: 720x1600
I flashed the resulting vendor_boot.img to the inactive slot (slot_b) while keeping the stock vendor_boot on slot_a (active/working). Switching active slot to b and rebooting causes an immediate kernel panic before any recovery UI appears. Pulled the crash log from pstore/ramoops:

[ 0.739470][ T1@C7] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
[ 0.740510][ T1@C7] CPU: 7 PID: 1 Comm: init Tainted: G OE 5.15.178-android13-8-g1e62f652da31-ab1926 #1
[ 0.741827][ T1@C7] Hardware name: Spreadtrum UMS9230 1H10 SoC (DT)
...
[ 0.739470] reason: Attempted to kill init! exitcode=0x00007f00

Device has no separate recovery partition — vendor_boot handles both normal boot and recovery. The panic happens at ~0.7s, before any TWRP UI, suggesting the ramdisk/init binary in the built vendor_boot may be incompatible (wrong ABI/format) with this kernel (5.15.178-android13).

Slot_a (stock, untouched) boots and runs normally — so this is isolated specifically to the TWRP-built vendor_boot.

Happy to provide the stock boot.img/vendor_boot.img used for the build, or any additional logs, if needed.

full crash_log
[ 0.517690][T124@C3] [Native Hang Detect] hang_detect info thread starts.
[ 0.564747][ T8@C1] yanbin: uart 1 eb
[ 0.565853][ T8@C1] yanbin: uart 2 eb
[ 0.566318][ T8@C1] yanbin: uart 2 disable
[ 0.739470][ T1@C7] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
[ 0.740510][ T1@C7] CPU: 7 PID: 1 Comm: init Tainted: G OE 5.15.178-android13-8-g1e62f652da31-ab1926 #1
[ 0.741827][ T1@C7] Hardware name: Spreadtrum UMS9230 1H10 SoC (DT)
[ 0.742603][ T1@C7] Call trace:
[ 0.742989][ T1@C7] dump_backtrace.cfi_jt+0x0/0x8
[ 0.743588][ T1@C7] dump_stack_lvl+0x80/0xb8
[ 0.744129][ T1@C7] panic+0x190/0x4b4
[ 0.744594][ T1@C7] do_exit+0xb94/0x1054
[ 0.745090][ T1@C7] do_group_exit+0x144/0x174
[ 0.745641][ T1@C7] do_group_exit+0x0/0x174
[ 0.746166][ T1@C7] invoke_syscall+0x60/0x150
[ 0.746719][ T1@C7] el0_svc_common+0xb8/0xf8
[ 0.747258][ T1@C7] do_el0_svc+0x28/0x98
[ 0.747750][ T1@C7] el0_svc+0x24/0x84
[ 0.748217][ T1@C7] el0t_64_sync_handler+0x88/0xec
[ 0.748821][ T1@C7] el0t_64_sync+0x1b8/0x1bc
[ 0.749360][ T1@C7] SMP: stopping secondary CPUs
[ 0.750247][ T1@C7] trusty-log: trusty-log panic notifier - trusty version Unisoc TEE v2.1.1, qogirl6, Built: 16:42:01 Jun 5 2025, b1a0a691 (builder@0e199bbf44e2)
[ 0.750255][ T1@C7] sysdump: (sysdump_panic_event) ------ in (7)
[ 0.752808][ T1@C7] sysdump:
[ 0.752808][ T1@C7] reg_esr_el1 = 0000000056000000
[ 0.752808][ T1@C7] reg_far_el1 = 0000007fb18b1000
[ 0.752808][ T1@C7] reg_elr_el1 = 000000000035b618
[ 0.755140][ T1@C7] unisoc-mailbox smsg_senddie mailbox send die smsg
[ 0.755952][ T1@C7] unisoc-mailbox smsg_senddie mailbox send die smsg
[ 3.756869][ T1@C7] sysdump:
[ 3.757236][ T1@C7] sysdump: *****************************************************
[ 3.758173][ T1@C7] sysdump: * *
[ 3.759110][ T1@C7] sysdump: * Sysdump enter, preparing debug info to dump ... *
[ 3.760046][ T1@C7] sysdump: * *
[ 3.760984][ T1@C7] sysdump: *****************************************************
[ 3.761920][ T1@C7] sysdump:
[ 3.762288][ T1@C7] sysdump: reason: Attempted to kill init! exitcode=0x00007f00, sprd_sysdump_info->crash_key: 0
[ 3.763645][ T1@C7] sysdump:
[ 3.764011][ T1@C7] sysdump: *****************************************************
[ 3.764948][ T1@C7] sysdump: * *
[ 3.765884][ T1@C7] sysdump: * Preparing debug info done ... *
[ 3.766821][ T1@C7] sysdump: * *
[ 3.767758][ T1@C7] sysdump: *****************************************************
[ 3.768695][ T1@C7] sysdump:
[ 4.769275][ T1@C7] Dumping ftrace buffer:
[ 4.769792][ T1@C7] (ftrace buffer empty)
[ 4.770322][ T1@C7] Kernel Offset: 0x80000 from 0xffffffc008000000
[ 4.771087][ T1@C7] PHYS_OFFSET: 0x80000000
[ 4.771603][ T1@C7] CPU features: 0x3,00000181,23300e46
[ 4.772252][ T1@C7] Memory Limit: none
[ 4.779805][ T1@C7] sprd-adi 64200000.spi: psci reboot enable
leanmi
leanmi
leanmi
Newbie
2
14-07-2026, 12:59 AM
#2
Device: Realme C51 (RMX3830)
Chipset: Unisoc UMS9230 / Tiger T612 (qogirl6)
Android version: 15
Build fingerprint: ums9230_hulk_Natv_k515-user-gms_QOGIRL6_hulk_SIGN
Build work ID / link: https://tools.hovatek.com/twrpbuildertoo...r_boot.img
Image type used for build: boot.img + vendor_boot.img (stock, extracted from full .pac firmware, Android 15 build)
Resolution entered: 720x1600
I flashed the resulting vendor_boot.img to the inactive slot (slot_b) while keeping the stock vendor_boot on slot_a (active/working). Switching active slot to b and rebooting causes an immediate kernel panic before any recovery UI appears. Pulled the crash log from pstore/ramoops:

[ 0.739470][ T1@C7] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
[ 0.740510][ T1@C7] CPU: 7 PID: 1 Comm: init Tainted: G OE 5.15.178-android13-8-g1e62f652da31-ab1926 #1
[ 0.741827][ T1@C7] Hardware name: Spreadtrum UMS9230 1H10 SoC (DT)
...
[ 0.739470] reason: Attempted to kill init! exitcode=0x00007f00

Device has no separate recovery partition — vendor_boot handles both normal boot and recovery. The panic happens at ~0.7s, before any TWRP UI, suggesting the ramdisk/init binary in the built vendor_boot may be incompatible (wrong ABI/format) with this kernel (5.15.178-android13).

Slot_a (stock, untouched) boots and runs normally — so this is isolated specifically to the TWRP-built vendor_boot.

Happy to provide the stock boot.img/vendor_boot.img used for the build, or any additional logs, if needed.


full crash_log
[ 0.517690][T124@C3] [Native Hang Detect] hang_detect info thread starts.
[ 0.564747][ T8@C1] yanbin: uart 1 eb
[ 0.565853][ T8@C1] yanbin: uart 2 eb
[ 0.566318][ T8@C1] yanbin: uart 2 disable
[ 0.739470][ T1@C7] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
[ 0.740510][ T1@C7] CPU: 7 PID: 1 Comm: init Tainted: G OE 5.15.178-android13-8-g1e62f652da31-ab1926 #1
[ 0.741827][ T1@C7] Hardware name: Spreadtrum UMS9230 1H10 SoC (DT)
[ 0.742603][ T1@C7] Call trace:
[ 0.742989][ T1@C7] dump_backtrace.cfi_jt+0x0/0x8
[ 0.743588][ T1@C7] dump_stack_lvl+0x80/0xb8
[ 0.744129][ T1@C7] panic+0x190/0x4b4
[ 0.744594][ T1@C7] do_exit+0xb94/0x1054
[ 0.745090][ T1@C7] do_group_exit+0x144/0x174
[ 0.745641][ T1@C7] do_group_exit+0x0/0x174
[ 0.746166][ T1@C7] invoke_syscall+0x60/0x150
[ 0.746719][ T1@C7] el0_svc_common+0xb8/0xf8
[ 0.747258][ T1@C7] do_el0_svc+0x28/0x98
[ 0.747750][ T1@C7] el0_svc+0x24/0x84
[ 0.748217][ T1@C7] el0t_64_sync_handler+0x88/0xec
[ 0.748821][ T1@C7] el0t_64_sync+0x1b8/0x1bc
[ 0.749360][ T1@C7] SMP: stopping secondary CPUs
[ 0.750247][ T1@C7] trusty-log: trusty-log panic notifier - trusty version Unisoc TEE v2.1.1, qogirl6, Built: 16:42:01 Jun 5 2025, b1a0a691 (builder@0e199bbf44e2)
[ 0.750255][ T1@C7] sysdump: (sysdump_panic_event) ------ in (7)
[ 0.752808][ T1@C7] sysdump:
[ 0.752808][ T1@C7] reg_esr_el1 = 0000000056000000
[ 0.752808][ T1@C7] reg_far_el1 = 0000007fb18b1000
[ 0.752808][ T1@C7] reg_elr_el1 = 000000000035b618
[ 0.755140][ T1@C7] unisoc-mailbox smsg_senddie mailbox send die smsg
[ 0.755952][ T1@C7] unisoc-mailbox smsg_senddie mailbox send die smsg
[ 3.756869][ T1@C7] sysdump:
[ 3.757236][ T1@C7] sysdump: *****************************************************
[ 3.758173][ T1@C7] sysdump: * *
[ 3.759110][ T1@C7] sysdump: * Sysdump enter, preparing debug info to dump ... *
[ 3.760046][ T1@C7] sysdump: * *
[ 3.760984][ T1@C7] sysdump: *****************************************************
[ 3.761920][ T1@C7] sysdump:
[ 3.762288][ T1@C7] sysdump: reason: Attempted to kill init! exitcode=0x00007f00, sprd_sysdump_info->crash_key: 0
[ 3.763645][ T1@C7] sysdump:
[ 3.764011][ T1@C7] sysdump: *****************************************************
[ 3.764948][ T1@C7] sysdump: * *
[ 3.765884][ T1@C7] sysdump: * Preparing debug info done ... *
[ 3.766821][ T1@C7] sysdump: * *
[ 3.767758][ T1@C7] sysdump: *****************************************************
[ 3.768695][ T1@C7] sysdump:
[ 4.769275][ T1@C7] Dumping ftrace buffer:
[ 4.769792][ T1@C7] (ftrace buffer empty)
[ 4.770322][ T1@C7] Kernel Offset: 0x80000 from 0xffffffc008000000
[ 4.771087][ T1@C7] PHYS_OFFSET: 0x80000000
[ 4.771603][ T1@C7] CPU features: 0x3,00000181,23300e46
[ 4.772252][ T1@C7] Memory Limit: none
[ 4.779805][ T1@C7] sprd-adi 64200000.spi: psci reboot enable
hovatek
hovatek
hovatek
Administrator
51,035
14-07-2026, 03:43 PM
#3
(14-07-2026, 12:59 AM)leanmi Device: Realme C51 (RMX3830)
Chipset: Unisoc UMS9230 / Tiger T612 (qogirl6)
Android version: 15
..

Android 15 support is experimental, but drop a link to your boot and vendor_boot images so we take a look.

Learn MediaTek, Unisoc / Spreadtrum (SPD) and Qualcomm Software Repairs @ https://www.hovatek.com/training
Note!
We have a reply schedule for Forum Support. Please try Private Support if you can't wait.
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)