Difference between revisions of "QCDT"

From postmarketOS
Jump to: navigation, search
(Repack procedure)
m (Compare the appended dtb files: bugfixed directory path)
Line 25: Line 25:
 
$ pmbootstrap chroot -r
 
$ pmbootstrap chroot -r
 
# apk add extract-dtb
 
# apk add extract-dtb
# mkdir -p /tmp/extract-dtb
+
# mkdir -p /tmp/extract-dtb-pmOS
 
# ls /boot/
 
# ls /boot/
 
# cp /boot/boot.img-* /tmp/extract-dtb-pmOS/boot.img
 
# cp /boot/boot.img-* /tmp/extract-dtb-pmOS/boot.img

Revision as of 12:15, 29 March 2018

Some Androids only accept boot.img files in the QCDT format, which means the dtb is appended to the end of it (and not at the end of the kernel, as with most other Android devices).

Does my device need a QCDT boot.img file?

Analyze a known working boot.img file with pmbootstrap to find out, if it has the QCDT format or not. You can get such a file from downloading a TWRP image (it is directly in the boot.img format!) or by downloading a full Android ROM for your device and extracting the boot.img file.

$ pmbootstrap bootimg_analyze /path/to/boot.img

If this prints deviceinfo_bootimg_qcdt="true", then you have a QCDT device.

Properly package a QCDT device

The easiest way is using pmbootstrap init to generate a new device, and let it analyze the boot.img file in the process. It will adjust the device and linux package as necessary. But if you want to do it manually:

  • Set deviceinfo_bootimg_qcdt="true" in the deviceinfo
  • Adjust your linux- APKBUILD to generate the /boot/dt.img (look at other QCDT devices to see how it's done, grep for qcdt in aports)

Debugging

  • 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.)

Compare the appended dtb files

$ pmbootstrap install
$ pmbootstrap chroot -r -- mkdir -p /tmp/extract-dtb-known-working
$ sudo cp known_working_boot.img ~/.local/var/pmbootstrap/chroot_rootfs_*/tmp/extract-dtb-known-working/boot.img
$ pmbootstrap chroot -r
# apk add extract-dtb
# mkdir -p /tmp/extract-dtb-pmOS
# ls /boot/
# cp /boot/boot.img-* /tmp/extract-dtb-pmOS/boot.img
# cd /tmp/extract-dtb-pmOS
# extract-dtb boot.img
# cd /tmp/extract-dtb-known-working
# extract-dtb boot.img
Now compare the output in both temp folders.
Is there the same amount of dtb files, and are the files the same?
If not, then the QCDT generation went wrong.

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

abootimg is packaged for postmarketOS as well, which allows to repackage the boot.img files without extracting them.

See also