Unable to boot

Luksus

The problem seems to stem from the fact that GSI ports overlay device-specific changes to the rootfs in a horrible way compared to traditional ports. GSIs do that at install-time of the update, meaning the rootfs-tarball can trump the device-tarball's contents.

But for me, that doesn't explain, why it works with the ubports-installer. It is actually doing the same. Except of, if the OTA was an incremental update, then something may be corrupted during the setup.
And there were no issues for the FP3, in this regard. So I doubt, that the GSI method was the root cause here.

I believe the X605 is very sensitive about touching the system-partition/rootfs.
For example, if you make the rootfs writable for changing some overlays or installing something through apt and you forget to mount it read-only again before rebooting, it will be stuck at bootlogo too, in most cases. No idea, whats happening there.

Lakotaubp

@luksus Maybe updates are landing on top of the existing system and not merging correctly, where as the installer reinstalls everything not just the updated files so all works. Just a thought.

Luksus

@lakotaubp Yes, that is what I meant by "incremental".
But I don't believe that this is the case for the first RC update for about a month.

arubislander

@luksus said in Unable to boot:

@lakotaubp Yes, that is what I meant by "incremental".
But I don't believe that this is the case for the first RC update for about a month.

It could well be incremental still, since it is only next one in number since the previous one.

I don't think the amount of time between updates matters, only the amount of updates skipped.

Luksus

@arubislander I think it matters, how much packages have changed.

arubislander

@luksus that is another possibility