[OnePlus 3 & 3T Cross Device Development] :
Can we agree on the correct phrases, please?

The boot logo is the still picture at the very beginning of the boot process. It comes out of the bootlogo partion, looks like the Oneplus logo with "powered by android" at the bottom. This is shown while the hardware is powered on and the kernel is booted.

The boot animation is shown during the late boot process. It comes from the system partition (system needs to be mounted in the boot process successfully to be shown) it's the moving "circle".

Though many people think it doesn't matter to use them synonymously (in deed most of the people think so, not just you!), it's very important to use them precisly, because they point to different states in the boot process.

Thanx. The console-ramoops shows a crash of kworker on cpu2.

[ 0.352522] ------------[ cut here ]------------
[ 0.352548] WARNING: CPU: 2 PID: 53 at ../../../../../../kernel/oneplus/msm8996/drivers/clk/msm/clock-local2.c:712 branch_clk_halt_check+0x114/0x124()
[ 0.352560] gcc_mss_q6_bimc_axi_clk: status stuck off
[ 0.352576] CPU: 2 PID: 53 Comm: kworker/u8:1 Not tainted 3.18.120-lineageos-gcbd39cd #1
[ 0.352590] Hardware name: Qualcomm Technologies, Inc. MSM 8996 v3 + PMI8996 MTP (DT)
[ 0.352613] Workqueue: deferwq deferred_probe_work_func
[ 0.352630] Call trace:
[ 0.352650] [<ffffffc00008b00c>] dump_backtrace+0x0/0x290
[ 0.352663] [<ffffffc00008b3a4>] show_stack+0x14/0x1c
[ 0.352677] [<ffffffc00102fa3c>] dump_stack+0x84/0xa8
[ 0.352690] [<ffffffc0000a8ae4>] warn_slowpath_common+0x8c/0xe0
[ 0.352703] [<ffffffc0000a8e08>] warn_slowpath_fmt+0x60/0x80
[ 0.352716] [<ffffffc000cdc7c0>] branch_clk_halt_check+0x114/0x124
[ 0.352729] [<ffffffc000cddba4>] branch_clk_enable+0x88/0xd0
[ 0.352741] [<ffffffc000cd9468>] clk_enable+0xa0/0x1d4
[ 0.352753] [<ffffffc000cda0bc>] __handoff_clk.part.3+0x28c/0x31c
[ 0.352765] [<ffffffc000cda178>] __handoff_clk+0x2c/0x5c
[ 0.352777] [<ffffffc000cda5f8>] msm_clock_register+0x130/0x2c0
[ 0.352790] [<ffffffc000cda7fc>] of_msm_clock_register+0x74/0x9c
[ 0.352805] [<ffffffc000ce7690>] msm_gcc_8996_probe+0x240/0x384
[ 0.352818] [<ffffffc0005fd288>] platform_drv_probe+0x3c/0xbc
[ 0.352830] [<ffffffc0005fb84c>] driver_probe_device+0x90/0x238
[ 0.352842] [<ffffffc0005fbb18>] __device_attach_driver+0x84/0xb0
[ 0.352853] [<ffffffc0005f9e10>] bus_for_each_drv+0x60/0xb0
[ 0.352865] [<ffffffc0005fb6b8>] __device_attach+0xc0/0x104
[ 0.352876] [<ffffffc0005fbb7c>] device_initial_probe+0x10/0x18
[ 0.352887] [<ffffffc0005fa0d4>] bus_probe_device+0x90/0x98
[ 0.352898] [<ffffffc0005fafb8>] deferred_probe_work_func+0x78/0xac
[ 0.352911] [<ffffffc0000c10a8>] process_one_work+0x160/0x480
[ 0.352922] [<ffffffc0000c1508>] worker_thread+0x140/0x478
[ 0.352935] [<ffffffc0000c6ee0>] kthread+0xd8/0xec
[ 0.352963] ---[ end trace 84748c43140aa938 ]---

I've no clue, why this happens - maybe the boot image isn't flashed correctly.

We would really need a log from the auto-rebooting twrp session - but currently I've no idea how to get this. I've seen incomplete flashes in the log, that doesn't show up on the console and twrp reports success.

Since migrating from <16.0 is one of the suspects, I can only ask anybody expiriencing this, to do a backup, followed by a clean flash of yesterday's zip, ota update of today's zip and report back.