小米8SE升级到安卓10后进TWRP时卡在TWRP启动界面的问题

小米8SE升级到安卓10后进TWRP时卡在TWRP启动界面的问题
0

小米8SE通过魔趣中心刷入增量包时卡在TWRP启动界面

问题描述: 小米8SE通过魔趣中心刷入增量包时在重启到TWRP后就卡在TWRP启动界面了,重启也会直接进行TWRP卡住
当前版本: MK100.0-sirius-202006101608-NIGHTLY

崩溃log:

11-18 15:56:10.649 560 560 F [email protected]: Configure failed
--------- beginning of crash
11-18 15:56:10.649 560 560 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 560 (android.hardwar), pid 560 (android.hardwar)
11-18 15:56:10.651 560 560 F libc : crash_dump helper failed to exec
11-18 15:56:10.651 560 560 F libc : failed to wait for crash_dump helper: No child processes
11-18 15:56:10.652 561 561 I ServiceManagement: Removing namespace from process name [email protected] to [email protected]
11-18 15:56:10.653 530 530 E SELinux : avc: denied { add } for interface=android.hardware.gatekeeper::IGatekeeper pid=561 scontext=u:r:recovery:s0 tcontext=u:object_r:hal_gatekeeper_hwservice:s0 tclass=hwservice_manager permissive=1
11-18 15:56:10.653 561 561 I [email protected]: Registration complete for [email protected]::IGatekeeper/default.
11-18 15:56:10.659 535 535 I ArmToArm64Assembler: generated scanline__00000077:03010101_00008001_00000000 [195 ipp] (241 ins) at [0x7e156503c0:0x7e15650784] in 100156 ns
11-18 15:56:10.721 535 535 I ArmToArm64Assembler: generated scanline__00000077:03545401_00000A01_00000000 [ 69 ipp] (113 ins) at [0x7e15650790:0x7e15650954] in 88958 ns
11-18 15:56:10.740 535 535 I ArmToArm64Assembler: generated scanline__00000077:03545401_00000A08_00000000 [ 69 ipp] (116 ins) at [0x7e15650960:0x7e15650b30] in 89375 ns
11-18 15:56:10.749 535 535 I recovery: type=1400 audit(0.0:74): avc: denied { write } for name=“etc” dev=“rootfs” ino=12962 scontext=u:r:recovery:s0 tcontext=u:object_r:rootfs:s0 tclass=dir permissive=1
11-18 15:56:10.749 535 535 I recovery: type=1400 audit(0.0:75): avc: denied { add_name } for name=“mtab” scontext=u:r:recovery:s0 tcontext=u:object_r:rootfs:s0 tclass=dir permissive=1
11-18 15:56:10.749 535 535 I recovery: type=1400 audit(0.0:76): avc: denied { create } for name=“mtab” scontext=u:r:recovery:s0 tcontext=u:object_r:rootfs:s0 tclass=lnk_file permissive=1
11-18 15:56:10.749 535 535 I recovery: type=1400 audit(0.0:77): avc: denied { create } for name=“firmware” scontext=u:r:recovery:s0 tcontext=u:object_r:rootfs:s0 tclass=dir permissive=1
11-18 15:56:10.786 549 550 I adbd : functionfs successfully initialized
11-18 15:56:10.787 549 550 I adbd : registering usb transport
11-18 15:56:10.788 549 564 E cutils-trace: Error opening trace file: No such file or directory (2)
11-18 15:56:10.789 535 535 I recovery: type=1400 audit(0.0:78): avc: denied { sys_time } for capability=25 scontext=u:r:recovery:s0 tcontext=u:r:recovery:s0 tclass=capability permissive=1
10-04 23:52:15.460 535 535 I recovery: type=1400 audit(0.0:82): avc: denied { open } for path="/persist/time/ats_2" dev=“mmcblk0p68” ino=180 scontext=u:r:recovery:s0 tcontext=u:object_r:persist_time_file:s0 tclass=file permissive=1
06-13 10:07:42.377 535 535 E cutils-trace: Error opening trace file: No such file or directory (2)
06-13 10:07:42.378 530 530 W /sbin/hwservicemanager: Cannot open /system/manifest.xml
06-13 10:07:43.380 535 535 W /sbin/recovery: Waited one second for [email protected]::IKeymasterDevice/default. Waiting another…
06-13 10:07:45.381 535 535 I chatty : uid=0(root) /sbin/recovery identical 2 lines
06-13 10:07:46.382 535 535 W /sbin/recovery: Waited one second for [email protected]::IKeymasterDevice/default. Waiting another…
06-13 10:07:47.046 580 580 E cutils-trace: Error opening trace file: No such file or directory (2)
06-13 10:07:47.046 530 530 W /sbin/hwservicemanager: Cannot open /system/manifest.xml
06-13 10:07:47.046 580 580 D vndksupport: Loading /usr/lib64/hw/[email protected] from current namespace instead of sphal namespace.
06-13 10:07:47.049 580 580 D QSEECOMAPI: QSEECom_get_handle sb_length = 0xa000
06-13 10:07:47.049 580 580 D QSEECOMAPI: App is already loaded QSEE and app id = 1
06-13 10:07:47.055 580 580 E KeymasterUtils: TA API Major Verion: 3
06-13 10:07:47.055 580 580 E KeymasterUtils: TA API Minor Verion: 0
06-13 10:07:47.055 580 580 E KeymasterUtils: TA Major Verion: 3
06-13 10:07:47.055 580 580 E KeymasterUtils: TA Minor Verion: 124
06-13 10:07:47.063 580 580 E KeyMasterHalDevice: configure
06-13 10:07:47.063 580 580 E KeyMasterHalDevice: ret: 0
06-13 10:07:47.063 580 580 E KeyMasterHalDevice: resp->status: -38
06-13 10:07:47.063 580 580 F [email protected]: Configure failed
06-13 10:07:47.063 580 580 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 580 (android.hardwar), pid 580 (android.hardwar)
06-13 10:07:47.066 580 580 F libc : crash_dump helper failed to exec
06-13 10:07:47.067 580 580 F libc : failed to wait for crash_dump helper: No child processes
06-13 10:07:47.382 535 535 W /sbin/recovery: Waited one second for [email protected]::IKeymasterDevice/default. Waiting another…
06-13 10:07:50.384 535 535 I chatty : uid=0(root) /sbin/recovery identical 3 lines
06-13 10:07:51.384 535 535 W /sbin/recovery: Waited one second for [email protected]::IKeymasterDevice/default. Waiting another…
06-13 10:07:52.046 586 586 E cutils-trace: Error opening trace file: No such file or directory (2)
06-13 10:07:52.047 530 530 W /sbin/hwservicemanager: Cannot open /system/manifest.xml
06-13 10:07:52.048 586 586 D vndksupport: Loading /usr/lib64/hw/[email protected] from current namespace instead of sphal namespace.
…后面重复/sbin/recovery: Waited one second for [email protected]::IKeymasterDevice/default. Waiting another…

我现在就想解决启动的问题,应该删掉启动时的刷机脚本就可以了,所以刷机脚本是放在什么地方

1 Like

我通过刷入原生的recovery绕过了更新脚本(因为它不支持脚本)得以正常开机,估计是当前TWRP的问题

问题应该解决了,我用的是wzsx150的TWRP,小米8SE安卓9升安卓10后TWRP要更新到安卓10的版本