QCDT
Appearance
The mozilla-flame
and other devices have the dtb appended to the boot.img.
To find out if your device boots qcdt
boot.img
files, run extract-dtb
(packaged for pmOS) on a known-working boot.img
(e.g. from TWRP or LineageOS).
Check PR #356 for example usage of how it is implemented right now, and #323 for the related discussion. In case you are implementing this for another device, please edit this article and put it more in a step-by-step format.
Some approaches that can help debug appended DTB issues:
- Hook up the serial UART and see what kind of debug output the bootloader provides
- Repack the boot image with a working
dt.img
from another distribution (stock, Lineage, recovery, etc.)
Repack Procedure
You need mkbootimg
and unpackbootimg
tools which are already packaged in pmbootstrap.
$ ./pmbootstrap build mkbootimg unpackbootimg $ ./unpackbootimg -i $SOMEDIR/boot.img-$vendor-$name -o pmos $ ./unpackbootimg -i $OTHERDIR/boot.img -o other $ cp other/boot.img-dt pmos/boot.img-$vendor-$name-dt $ ./mkbootimg -o boot.repack.img -r pmos/boot.img-$vendor-$name-
You can also get these from https://github.com/efidroid/build/tree/master/tools