Unable to differenciate between dtb & blank space when run on boot.img

[chankruze]

When i run the script on a boot.img directly. It's appending all blank space to last dtb.

For example i was extracting dtbs from realme X boot.img. Siz eof boot.img was 67.1 MB. The extracted dtbs are shown below.

size of dtbs when extracted from boot.img:

size of dtbs when extracted from zImage (After unpacking with AIK):

Last dtb has a size of 53.5 MB on boot.img case & 173 Bytes on zImage case.

So what's the issue ?
If the kernel size increased a little, while using dtbs extracted from boot.img having remaining blank space appended, will result in a larger image which will eventually fail to flash with a error that partition is full.

[PabloCastellano]

Hey @chankruze.

Can you upload the mentioned boot.img so I can have a look? Or even better, do you want to provide a patch to fix it?

[chankruze]

@PabloCastellano As per your request i uploaded the boot image here. Let me know the update.

[TwistedPrime]

I got the same issue. Is it necessary to append the dtbdump_!'$'\v''_~\s.dtb back to my kernel image?

[PabloCastellano]

Hey @chankruze, I can't download the image. It always says that I am blocked. Can you use another provider? (e.g. https://send.firefox.com/)

[chankruze]

@thanasxda please mirror this (https://www.androidfilehost.com/?fid=1899786940962599088) here (https://send.firefox.com/). And send url here.

[thanasxda]

@thanasxda please mirror this (https://www.androidfilehost.com/?fid=1899786940962599088) here (https://send.firefox.com/). And send url here.

https://send.firefox.com/download/8f85a1eaa2054966/#keorXRnjuY3EEyxdakgaZg