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

217 天前
 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         : [<ffffff955ec85a64>] __switch_to+0xa8/0xb4
03-18 18:13:10.311     0     0 I         : [<ffffff955fcfc990>] __schedule+0x578/0x7f4
03-18 18:13:10.311     0     0 I         : [<ffffff955fcfc3f8>] schedule+0x70/0x90
03-18 18:13:10.311     0     0 I         : [<ffffff955fcfff54>] schedule_timeout+0x3c/0x308
03-18 18:13:10.311     0     0 I         : [<ffffff955fcfdbdc>] wait_for_common+0xb0/0x130
03-18 18:13:10.311     0     0 I         : [<ffffff955fcfdb24>] wait_for_completion+0x14/0x1c
03-18 18:13:10.311     0     0 I         : [<ffffff955f192364>] msm_mpm_work_fn+0x50/0xd4
03-18 18:13:10.311     0     0 I         : [<ffffff955ecc9190>] process_one_work+0x1b0/0x478
03-18 18:13:10.311     0     0 I         : [<ffffff955ecc8c68>] worker_thread+0x240/0x484
03-18 18:13:10.311     0     0 I         : [<ffffff955eccdc68>] kthread+0xf4/0x13c
03-18 18:13:10.311     0     0 I         : [<ffffff955ec83310>] 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         : [<ffffff955ec85a64>] __switch_to+0xa8/0xb4
03-18 18:13:10.311     0     0 I         : [<ffffff955fcfc990>] __schedule+0x578/0x7f4
03-18 18:13:10.311     0     0 I         : [<ffffff955fcfc3f8>] schedule+0x70/0x90
03-18 18:13:10.311     0     0 I         : [<ffffff955f09a154>] dsi_event_thread+0xc4/0x3a8
03-18 18:13:10.311     0     0 I         : [<ffffff955eccdc68>] kthread+0xf4/0x13c
03-18 18:13:10.311     0     0 I         : [<ffffff955ec83310>] 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         : [<ffffff955ec85a64>] __switch_to+0xa8/0xb4
03-18 18:13:10.311     0     0 I         : [<ffffff955fcfc990>] __schedule+0x578/0x7f4
03-18 18:13:10.311     0     0 I         : [<ffffff955fcfc3f8>] schedule+0x70/0x90
03-18 18:13:10.311     0     0 I         : [<ffffff955fcfff54>] schedule_timeout+0x3c/0x308
03-18 18:13:10.311     0     0 I         : [<ffffff955fcfdbdc>] wait_for_common+0xb0/0x130
03-18 18:13:10.311     0     0 I         : [<ffffff955fcfdb24>] wait_for_completion+0x14/0x1c
03-18 18:13:10.311     0     0 I         : [<ffffff955fcfa688>] do_sampling+0xbc/0x244
03-18 18:13:10.311     0     0 I         : [<ffffff955eccdc68>] kthread+0xf4/0x13c
03-18 18:13:10.311     0     0 I         : [<ffffff955ec83310>] 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         : [<ffffff955ec85a64>] __switch_to+0xa8/0xb4
03-18 18:13:10.311     0     0 I         : [<ffffff955fcfc990>] __schedule+0x578/0x7f4
03-18 18:13:10.311     0     0 I         : [<ffffff955fcfc3f8>] schedule+0x70/0x90
03-18 18:13:10.311     0     0 I         : [<ffffff955f0d5f18>] __mdss_fb_display_thread+0x154/0x5fc
03-18 18:13:10.311     0     0 I         : [<ffffff955eccdc68>] kthread+0xf4/0x13c
03-18 18:13:10.311     0     0 I         : [<ffffff955ec83310>] 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

5995 次点击
所在节点    Android
23 条回复
amrnxcdt
217 天前
@SGRRYRS 5.20 我已经安装了，一样的问题，keystore2 这里我也没留意到，我去研究下。
SGRRYRS
216 天前
@amrnxcdt 应该是只能格式化 data 了
amrnxcdt
216 天前
@SGRRYRS #22 有进展了，keystore2 的问题解决了，虽然现在还是没能开机。



keystore2 的问题是因为/data/misc/keystore/ 这个目录下的文件所有者变成了 root:root 。改成 keystore:keystore 就可以正常启动了。参考:https://stackoverflow.com/questions/71108966/andoid-12-keystore-user-0-missing-foder



这是修 keystore2 后的 log： https://f.ws59.cn/f/e7cuiqj2ktx


上面这个日志也是会报告
````
01-01 22:11:14.203 760 760 E keystore2: system/security/keystore2/src/error.rs:200 - system/security/keystore2/src/maintenance.rs:177: getting keymint device
01-01 22:11:14.203 760 760 E keystore2:
01-01 22:11:14.203 760 760 E keystore2: Caused by:
01-01 22:11:14.203 760 760 E keystore2: 0: system/security/keystore2/src/globals.rs:339: Cannot connect to Keymint
01-01 22:11:14.203 760 760 E keystore2: 1: system/security/keystore2/src/globals.rs:250: Trying to get Legacy wrapper.
01-01 22:11:14.203 760 760 E keystore2: 2: Error::Km(r#HARDWARE_TYPE_UNAVAILABLE)
01-01 22:11:14.203 736 736 E vold : keystore2 Keystore earlyBootEnded returned service specific error: -68
01-01 22:11:14.203 0 0 E vold : keystore2 Keystore earlyBootEnded returned service specific error: -68
````
我找了之前这个手机正常启动时候的 dmesg 发现里面也会报
````
[ 10.272954] incfs: IncFs_Features: failed to open features dir, assuming v1/none.: No such file or directory
[ 10.307151] vold: keystore2 Keystore earlyBootEnded returned service specific error: -68
[ 10.307938] init: Service 'exec 5 (/system/bin/vdc keymaster earlyBootEnded)' (pid 794) exited with status 0 waiting took 0.043000 seconds
````
keystore2 现在应该是正常的。

这是一个专为移动设备优化的页面（即为了让你能够在 Google 搜索结果里秒开这个页面），如果你希望参与 V2EX 社区的讨论，你可以继续到 V2EX 上打开本讨论主题的完整版本。

https://www.v2ex.com/t/1043832

V2EX 是创意工作者们的社区，是一个分享自己正在做的有趣事物、交流想法，可以遇见新朋友甚至新机会的地方。

V2EX is a community of developers, designers and creative people.

© 2021 V2EX