I have a GS 290 which is the same hardware as Vollaphone and just wonder if it would be possible to install UBports on an SD card?

My phone with all software upgraded to the latest versions always showed the twice error message "Failed to add storage device".
Now I have formatted the remaining part of the sd card to ext 4 and as a result I get the message 4 times :-(.

I just wonder if only a few are annoyed by this problem or if everybody just deletes these messages after each start?

@C0n57an71n Yes I always waited long enough. What image # have you used to flash now?

@C0n57an71n Thank you for the screenshot. Since I had no Ubuntu system ready, I installed gnome-disk-utility
and ran "gnome-disks --restore-disk-image=ubuntu-touch-pinephone.img.xz".
This resulted in the same screen as you showed and installed the image directly to the sd-card.

Obviously gnome-disk did not detect that the backup of GPT table was at the wrong place. I did repair this as usual using gdisk.
I am convinced that this gives the same result as using xz to decompress and dd to write to the sd-card.
And indeed when placing the card in the phone it only shows the pine logo and then the ubuntu boot screen.

This has now happened with #87 to #89. The last 'working' image had been #82.

So there remains the question who else has success using these new images and who does just upgrade from old ones?

@C0n57an71n What do you expect to happen when on Linux a raw file is tried to execute???

@C0n57an71n Sorry, I so not understand.

@C0n57an71n Debian Buster. Many other distros do boot as expected.

@AppLee Sorry, but for quite some time I am no longer able to get a working system with ubports on sd card.
Many other distros do correctly boot, but not ubports!

@C0n57an71n I did write the image on sdcard using dd.
Running fsck after showed that all data has been corectly written. Using a different card makes no difference at all.
I won't try it on eMMC before the system on sd-card is ok.

Now, with #88 the fsck problem does no longer occur.
Anyhow, that card only goes to the animated violet logo screen, no possibility to log in.
Looks to me like some kind of self-stimulation of some computer kid...

I have downloaded #87 (Nov 5, 2020 )
https://ci.ubports.com/job/rootfs/job/rootfs-pinephone-systemimage/, unzipped it and flashed to my 64G sd-card.
When running fsck on sdb10, sdb9 and sdb8 it unexpectedly showed many errors and was not able to repair the fs.
So I was not surprised that this version did not boot at all in the PinePhone.

Exactly the same situation was found with #86, 85 and 84.

Only with #83 fsck on the partitions 10,9 and 8 did not find errors or was able to repair it.
As the original image comes from a smaller card, the backup of gpt data was at the wrong position and I repaired that using gdisk repair mode.
With older versions I had often seen that automatic resizing did not correctly work and therfore I did resize sdb10 to the maximum.
When booting that version I got a b/w Pine logo and then the violet Ubuntu touch screen, but never came to a unlock or login screen.
My questions:
a) How to explain that virgin partitions show file system errors?
b) What must be changed for more success?

Many thanks for your work and help!
LinAdmin