Skip to content

common: add snapuserd to vendor ramdisk

Mattijs Korpershoek requested to merge mkorpershoek/fix-ota-update-engine into ti-android-14

When applying an OTA via SystemUpdaterSample, after booting to _b slot, we have the following error:

[    4.217496][    T1] init: Created socket '/dev/socket/snapuserd', mode 660, user 1000, group 1000
[    4.229481][  T115] init: Cannot launch snapuserd; execv failed: No such file or directory
[   14.239621][    T1] init: Timed out connecting to snapuserd socket: snapuserd
[   14.247006][    T1] init: Could not connect to first-stage snapuserd
[   14.255756][    T1] init: InitFatalReboot: signal 6

Because of this, we cannot do any OTA updates.

According to [1], the vendor_boot ramdisk is loaded during the first-stage init. However, the vendor_boot ramdisk does not have snapuserd installed.

Add snapuserd to the vendor_boot ramdisk to solve the OTA problem.

Another option would be to move to a dedicated A/B recovery partition [2], but that has not been investigated.

[1] https://source.android.com/docs/core/architecture/partitions/generic-boot#figure-T-1 [2] https://source.android.com/docs/core/architecture/partitions/generic-boot#figure-T-2 Signed-off-by: Mattijs Korpershoek mkorpershoek@baylibre.com

Merge request reports