This is a cache of https://discuss.96boards.org/t/hkey960-with-kernel-version-4-14-or-4-19-failed-to-boot-android/9868. It is a snapshot of the page at 2024-09-20T13:04:27.513+0000.
Hkey960 with kernel version 4.14 or 4.19 failed to boot <strong>android</strong> - HiKey 960 - 96Boards Forum

Hkey960 with kernel version 4.14 or 4.19 failed to boot android

I try to flash the newest factory images(kernel version 4.19, hikey960-linaro-2020.02.24-factory-d33c0c48.zip) into Hikey960. But it cannot boot into android as normal as kernel version 4.9.

I can enter the kernel console with adb tools, but the device cannot launch to android.

I found that the kernel was starting service ‘zygote’ again and again.

[ 12.524079] init: processing action (ro.crypto.state=encrypted && ro.crypto.type=file && zygote-start) from (/system/etc/init/hw/init.rc:826)
[ 12.536955] init: Command ‘exec_start update_verifier_nonencrypted’ action=ro.crypto.state=encrypted && ro.crypto.type=file && zygote-start (/system/etc/init/hw/init.rc:828) took 0ms and failed: Service not found
[ 12.556541] init: starting service ‘netd’…
[ 12.561714] init: Created socket ‘/dev/socket/dnsproxyd’, mode 660, user 0, group 3003
[ 12.570259] init: Created socket ‘/dev/socket/mdns’, mode 660, user 0, group 1000
[ 12.578313] init: Created socket ‘/dev/socket/fwmarkd’, mode 660, user 0, group 3003
[ 12.588953] init: starting service ‘zygote’…
[ 12.593931] init: Created socket ‘/dev/socket/zygote’, mode 660, user 0, group 1000
[ 12.601896] init: Created socket ‘/dev/socket/usap_pool_primary’, mode 660, user 0, group 1000
[ 12.613691] init: starting service ‘zygote_secondary’…

And I collected all of fail information as below:

[ 3.035495] hci-ti serial0-0: Direct firmware load for ti-connectivity/TIInit_11.8.32.bts failed with error -2
[ 6.650371] usb 1-1: hub failed to enable device, error -108
[ 6.763164] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 6.799154] wl18xx_driver wl18xx.2.auto: Direct firmware load for ti-connectivity/wl1271-nvs.bin failed with error -2
[ 7.105915] init: [libfs_mgr]ReadFstabFromDt(): failed to read fstab from dt
[ 7.224960] linker: Warning: failed to find generated linker configuration from “/linkerconfig/ld.config.txt”
[ 7.234902] Warning: failed to find generated linker configuration from "
[ 7.592939] init: Do not have permissions to set ‘qemu.hw.mainkeys’ to ‘0’ in property file ‘/vendor/build.prop’: SELinux permission check failed
[ 7.606038] init: Do not have permissions to set ‘wifi.supplicant_scan_interval’ to ‘15’ in property file ‘/vendor/build.prop’: SELinux permission check failed
[ 7.620836] init: Couldn’t load property file ‘/factory/factory.prop’: open() failed: No such file or directory: No such file or directory
[ 7.790813] ueventd: Unable to read config file ‘/odm/ueventd.rc’: open() failed: No such file or directory
[ 7.816116] ueventd: Unable to read config file ‘/ueventd.hikey960.rc’: open() failed: No such file or directory
[ 12.536955] init: Command ‘exec_start update_verifier_nonencrypted’ action=ro.crypto.state=encrypted && ro.crypto.type=file && zygote-start (/system/etc/init/hw/init.rc:828) took 0ms and failed: Service not found
[ 12.711527] cfg80211: failed to load regulatory.db
[ 33.105139] apexd: Revert failed : Revert requested, when there are no active sessions.

Thank you very much for your help! I really want to use hikey960 with kernel version 4.14 or 4.19.

Vendor partition missing or incompatible… Did you flash the vendor partition? Did you update the bootloader to latest build?

Thank you very much for your help! As the picture below, I just downloaded hikey960-linaro-2020.02.24-factory-d33c0c48.zip and decompressed it and executed ./flash-all.sh.

SO do you mean I should flash the vendor.img in the package of verndor-4.14.img.xz?

You would have to make sure that you use a full matching set of images. If you are using the 4.14 boot, you have to also use the 4.14 dts and 4.14 vendor.

Thanks. I’ll try and give you feedback!
Thank you again!