@C0n57an71n Yes I always waited long enough. What image # have you used to flash now?
Latest posts made by LinAdmin
RE: Problems with PinePhone Builds
@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?
Problems with PinePhone Builds
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.
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!