有熟悉 android 系统启动过程的兄弟吗?有偿请求解决个问题

查看 23|回复 1
作者:amrnxcdt   
如题,lineageos 用 kernelflash 刷入了 anykernel3.zip 的包,刷到一半手机自动重启了,现在重新刷入原本的 boot 也无法启动,也尝试过完整刷入系统。
有开机 log ,看上去都卡在同一个地方。
日志文件较大,节选了下面的信息,如果有熟悉的兄弟请留下联系方式请教一下,薄酬 50 红包,谢谢。
03-18 18:13:08.535     0     0 I init    : starting service 'vendor.ipacm'...
03-18 18:13:08.537     0     0 I init    : ... started service 'vendor.ipacm' has pid 5719
03-18 18:13:08.556     0     0 I init    : Service 'vendor.ipacm' (pid 5719) exited with status 0
03-18 18:13:08.556     0     0 I init    : Sending signal 9 to service 'vendor.ipacm' (pid 5719) process group...
03-18 18:13:08.556     0     0 I libprocessgroup: Successfully killed process cgroup uid 1001 pid 5719 in 0ms
03-18 18:13:08.556     0     0 E init    : process with updatable components 'vendor.ipacm' exited 4 times before boot completed
03-18 18:13:08.557     0     0 I init    : processing action (sys.init.updatable_crashing=1) from (/system/etc/init/flags_health_check.rc:10)
03-18 18:13:08.557     0     0 I init    : starting service 'exec 129 (/system/bin/flags_health_check UPDATABLE_CRASHING)'...
03-18 18:13:08.558     0     0 I init    : ... started service 'exec 129 (/system/bin/flags_health_check UPDATABLE_CRASHING)' has pid 5720
03-18 18:13:08.558     0     0 I init    : SVC_EXEC service 'exec 129 (/system/bin/flags_health_check UPDATABLE_CRASHING)' pid 5720 (uid 1000 gid 1000+0 context default) started; waiting...
03-18 18:13:08.565  5720  5720 I flags_health_check: ServerConfigurableFlagsReset reset_mode value: 1
03-18 18:13:08.565  5720  5720 I flags_health_check: ServerConfigurableFlagsReset updatable crashing detected, resetting flags.
03-18 18:13:08.570     0     0 I init    : Service 'exec 129 (/system/bin/flags_health_check UPDATABLE_CRASHING)' (pid 5720) exited with status 0 waiting took 0.012000 seconds
03-18 18:13:08.570     0     0 I init    : Sending signal 9 to service 'exec 129 (/system/bin/flags_health_check UPDATABLE_CRASHING)' (pid 5720) process group...
03-18 18:13:08.570     0     0 I libprocessgroup: Successfully killed process cgroup uid 1000 pid 5720 in 0ms
03-18 18:13:09.621     0     0 E FG      : fg_psy_get_property: unsupported property 76
03-18 18:13:09.627     0     0 E FG      : fg_psy_get_property: unsupported property 76
03-18 18:13:09.631     0     0 W healthd : battery l=100 v=4369 t=29.2 h=2 st=2 c=78000 fc=2878000 cc=0 chg=u
03-18 18:13:09.636     0     0 E FG      : fg_psy_get_property: unsupported property 76
03-18 18:13:09.773   750  1012 D BootAnimation: Playing files = /product/media/bootanimation.zip/part1, Requested repeat = 0, playUntilComplete = true
03-18 18:13:10.311     0     0 I sysrq   : Show Blocked State
03-18 18:13:10.311     0     0 I         : task                        PC stack   pid father
03-18 18:13:10.311     0     0 I kworker/u16: 1   D ffffff955ec85a64     0    83      2 0x00000010
03-18 18:13:10.311     0     0 I Workqueue: mpm msm_mpm_work_fn
03-18 18:13:10.311     0     0 I Call trace:  
03-18 18:13:10.311     0     0 I         : [] __switch_to+0xa8/0xb4
03-18 18:13:10.311     0     0 I         : [] __schedule+0x578/0x7f4
03-18 18:13:10.311     0     0 I         : [] schedule+0x70/0x90
03-18 18:13:10.311     0     0 I         : [] schedule_timeout+0x3c/0x308
03-18 18:13:10.311     0     0 I         : [] wait_for_common+0xb0/0x130
03-18 18:13:10.311     0     0 I         : [] wait_for_completion+0x14/0x1c
03-18 18:13:10.311     0     0 I         : [] msm_mpm_work_fn+0x50/0xd4
03-18 18:13:10.311     0     0 I         : [] process_one_work+0x1b0/0x478
03-18 18:13:10.311     0     0 I         : [] worker_thread+0x240/0x484
03-18 18:13:10.311     0     0 I         : [] kthread+0xf4/0x13c
03-18 18:13:10.311     0     0 I         : [] ret_from_fork+0x10/0x40
03-18 18:13:10.311     0     0 I         : mdss_dsi_event  D ffffff955ec85a64     0   175      2 0x00000010
03-18 18:13:10.311     0     0 I Call trace:  
03-18 18:13:10.311     0     0 I         : [] __switch_to+0xa8/0xb4
03-18 18:13:10.311     0     0 I         : [] __schedule+0x578/0x7f4
03-18 18:13:10.311     0     0 I         : [] schedule+0x70/0x90
03-18 18:13:10.311     0     0 I         : [] dsi_event_thread+0xc4/0x3a8
03-18 18:13:10.311     0     0 I         : [] kthread+0xf4/0x13c
03-18 18:13:10.311     0     0 I         : [] ret_from_fork+0x10/0x40
03-18 18:13:10.311     0     0 I msm-core: sampli D ffffff955ec85a64     0   541      2 0x00000010
03-18 18:13:10.311     0     0 I Call trace:  
03-18 18:13:10.311     0     0 I         : [] __switch_to+0xa8/0xb4
03-18 18:13:10.311     0     0 I         : [] __schedule+0x578/0x7f4
03-18 18:13:10.311     0     0 I         : [] schedule+0x70/0x90
03-18 18:13:10.311     0     0 I         : [] schedule_timeout+0x3c/0x308
03-18 18:13:10.311     0     0 I         : [] wait_for_common+0xb0/0x130
03-18 18:13:10.311     0     0 I         : [] wait_for_completion+0x14/0x1c
03-18 18:13:10.311     0     0 I         : [] do_sampling+0xbc/0x244
03-18 18:13:10.311     0     0 I         : [] kthread+0xf4/0x13c
03-18 18:13:10.311     0     0 I         : [] ret_from_fork+0x10/0x40
03-18 18:13:10.311     0     0 I         : mdss_fb0        D ffffff955ec85a64     0   785      2 0x00000010
03-18 18:13:10.311     0     0 I Call trace:  
03-18 18:13:10.311     0     0 I         : [] __switch_to+0xa8/0xb4
03-18 18:13:10.311     0     0 I         : [] __schedule+0x578/0x7f4
03-18 18:13:10.311     0     0 I         : [] schedule+0x70/0x90
03-18 18:13:10.311     0     0 I         : [] __mdss_fb_display_thread+0x154/0x5fc
03-18 18:13:10.311     0     0 I         : [] kthread+0xf4/0x13c
03-18 18:13:10.311     0     0 I         : [] ret_from_fork+0x10/0x40
03-18 18:13:10.311     0     0 I sysrq   : Show backtrace of all active CPUs
03-18 18:13:10.311     0     0 I         : Backtrace for cpu 7 (current):
03-18 18:13:10.311     0     0 I         : CPU: 7 PID: 5209 Comm: watchdog Not tainted 4.4.302-perf+ #1
完整 log: https://f.ws59.cn/f/e70xi28hdcm
JayZXu   
是用的什么手机刷的?
感觉这种刷机反复重启,多半还是 vbmeta 的问题吧
虽然 anykernel3 能自动修补 vbmeta ,但是很多手机还会校验 vbmeta 的签名
您需要登录后才可以回帖 登录 | 立即注册

返回顶部