xiaomi-scorpio dtb not found

I'm not sure if this is related to #559 (closed) or #63 (closed) so I'm opening a new issue.

I get this trying to pmbootstrap flasher boot:

(815214) [14:50:22] (native) boot xiaomi-scorpio kernel
(815214) [14:50:22] (native) calculate depends of android-tools, avbtool (pmbootstrap -v for details)
(815214) [14:50:22] (native) % fastboot --cmdline androidboot.hardware=qcom ehci-hcd.park=3 lpm_levels.sleep_disabled=1 cma=32M@0-0xffffffff loop.max_part=7 buildvariant=userdebug boot /mnt/rootfs_xiaomi-scorpio/boot/boot.img-xiaomi-scorpio
Sending 'boot.img' (57216 KB)                      OKAY [  2.108s]
Booting                                            FAILED (remote: 'dtb not found')
fastboot: error: Command failed

I'm using this kernel, and have tried those commits:

• 95f789c577af310133bcebffe3228affd6fe9cf8
• 2933054d2488e3d40ae6f4745f93d657e4f96b96

Both give the same result.

Here's bootimg-analyze for a boot.img I extracted from the build of LineageOS that is currently installed and running on the phone:

deviceinfo_kernel_cmdline="androidboot.hardware=qcom ehci-hcd.park=3 lpm_levels.sleep_disabled=1 cma=32M@0-0xffffffff loop.max_part=7 buildvariant=userdebug"
deviceinfo_generate_bootimg="true"
deviceinfo_bootimg_qcdt="false"
deviceinfo_bootimg_dtb_second="false"
deviceinfo_flash_offset_base="0x80000000"
deviceinfo_flash_offset_kernel="0x00008000"
deviceinfo_flash_offset_ramdisk="0x01000000"
deviceinfo_flash_offset_second="0x00f00000"
deviceinfo_flash_offset_tags="0x00000100"
deviceinfo_flash_pagesize="4096"

I was recommended to use deviceinfo_append_dtb="true", but that made pmbootstrap install fail:

==> initramfs: creating boot.img
error: could not load kernel '/boot/vmlinuz-xiaomi-scorpio-dtb'

I ported Halium with this kernel successfully, so I don't think it is entirely missing the device tree.

If you're using this defconfig https://github.com/LineageOS/android_kernel_xiaomi_msm8996/blob/lineage-17.1/arch/arm64/configs/scorpio_defconfig#L68 with this CONFIG_BUILD_ARM64_APPENDED_DTB_IMAGE=y then build process should produce kernel image with already appended dtb (this only works in downstream kernels; deviceinfo_append_dtb="true" is needed for mainline kernels where this feature is not present).

Then you just make sure that downstreamkernel_package packages correct kernel.

You can also use bootimg_analyse on produced boot.img to compare output to stock just in case

By Alexey Min on 2020-06-26T14:11:32

I found CONFIG_BUILD_ARM64_APPENDED_DTB_IMAGE enabled. I rebuilt the kernel package and reinstalled just to be sure, yet it is still happening.

By Yassine Oudjana on 2020-06-26T15:12:35

added category::device label

I downloaded the TWRP for this device and ran extract-dtb and it yielded 6 different device trees. The most likely scenario is that your device's msm-id, pmic-id or board-id didn't match the one that's used in this kernel (as per my guess only one is being built in). This is normal for different versions/revisions of the phone.

By Konrad Dybcio on 2020-06-27T08:52:17

wouldn't Halium not boot with this kernel then?

By Yassine Oudjana on 2020-06-27T08:52:17

extract-dtb dumps 124 dtbs from the boot image generated by pmbootstrap

By Yassine Oudjana on 2020-06-28T08:45:16

After checking /sys/firmware/devicetree/base in a running install of LineageOS, I think the device tree source of this specific unit is either this, with qcom,board-id = <34 0>, or this, with qcom,board-id = <33 0>.

From the 124 dtbs I got from the boot image generated by pmbootstrap, the ones for 8996pro + PMI8996 MTP all have qcom,board-id = <8 0>.

What am I missing here?

By Yassine Oudjana on 2020-07-11T13:25:21

This stopped happening at some point and I'm not sure how or why. I'll close now and reopen if it happens again.

By Yassine Oudjana on 2020-09-12T09:48:43

closed

mentioned in issue #559 (closed)

By Yassine Oudjana on 2021-04-16T17:52:28