[tegra / grate] extend automatic kernel updates to work on devices without PARTLABEL available

Currently blocker for tegra devices:

• PARTLABEL isn't available here

So, possibility would be to allow "risky" search through all partitions, where detecting content of each partition and when reaching

Android bootimg, kernel (0x10008000), ramdisk (0x11000000), page size: 2048 with file -b /dev/mmc*

, using THIS if only one of these is found and offsets matches.

This should be final step, when everything else fails.

mentioned in issue #1158 (closed)

By David Heidelberg on 2021-08-02T10:05:58

changed the description

By David Heidelberg on 2021-08-02T10:07:49

I have a bit to say about Asus transformers on Tegra 2 and Tegra 3. To flash using a fastboot they require a packing into blob. This mechanism is already implemented into pmOS via blobtools.

Same time transformers CAN flash kernel without packing into blob (bare boot.img) using dd command and direct partition name (like mmcblk0p9 or mmcblk0p10) and as I know any other labels aren't supported.

By Svyatoslav Ryhel on 2021-08-03T18:18:59

added category::device discussion type::feature labels

Tested on Nexus 7 2013 flo/deb (not the tegra, but this is generic approach which should work everywhere without PARTLABEL available).

#!/bin/sh

for device in $(lsblk -p -n -l -o NAME | xargs)
do
	file -bsZ ${device} | grep "^Android bootimg" && \
		echo ":: Found device $device" && i=$(($i+1))
done

echo ":: Number of partitions with Android bootimg: $i";

if [ $i -eq 1 ]; then
	echo ":: Flashing... $device"
elif [ $i -gt 1 ]; then
	echo ":: Error! Found more than one Android bootimg partition! Don't know what to do!"
else
	echo ":: Didn't found any Android bootimg partition!"
fi

and output

# ./bootimg.sh 
1:Android bootimg, kernel, ramdisk, page size: 2048, cmdline (xxxxxxxxxxxxxxxxxxxxxxxxxxconsole=ttyMSM0,115200,n8 user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 vmalloc=340M)
:: Found device /dev/mmcblk0p14
1:Android bootimg, kernel, ramdisk, page size: 2048, cmdline (console=ttyHSL0,115200,n8 androidboot.hardware=flo user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 vmalloc=340M)
:: Found device /dev/mmcblk0p25
:: Number of partitions with Android bootimg: 2
:: Error! Found more than one Android bootimg partition! Don't know what to do!

First is the BOOT partition, second is the RECOVERY. I need somehow rule out the RECOVERY.

Solution could be to extract kernel and then checkout the build string if it contains postmarketOS, but I feel like it starting to be overcomplicated.

We could fall back to something like this.

By David Heidelberg on 2021-08-19T20:41:34

Maybe you could try appending the string postmarketOS to the end of the boot image and then looking for that string? This could be an added step in boot deploy based on the existence of a deviceinfo flag, the upgrade script would also check for the same flag.

Something like $deviceinfo_tag_boot_image ? Then you don't have to deal with running it through unix tools or doing any complicated extraction / parsing.

EDIT: more simply, just add a $deviceinfo_android_boot variable (is there one already?) with the device node for the boot partition. This does depend on the partition ordering being consistent though.

By Caleb Connolly on 2021-10-10T20:53:11

Closing issue due to inactivity.

By Robert Eckelmann on 2024-08-14T14:18:01

closed