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!
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...
chrisrg last edited by
@LinAdmin Not getting much help here it seems!! And I doubt if I can help much; repairing and resizing partitions is a bit advanced for me. Anyway, I thought I'd offer my latest experience with flashing the pinephone.
I've just fitted an upgraded motherboard and flashed #88 with jumpdrive. All seems good, well until I installed dekko, which immediately crashed the phone ha ha.
Would it make any difference to your experience if you tried flashing sd card with balena etcher? It has to be the simplest way and it carries out the unzipping of the image file so you don't have to.
@LinAdmin How did you write the image? Have you tried with another SD card? Have you tried writing it on the eMMC?
@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.
@LinAdmin On which desktop OS are you doing the image writing?
@C0n57an71n Debian Buster. Many other distros do boot as expected.
@LinAdmin That means that you have Disks app? If yes, could you double-click on the image and see if the Disks app ask you if you want to recover the image and where?
@C0n57an71n Sorry, I so not understand.
@LinAdmin The image file that you have downloaded, double-click on it an see what it does.
@C0n57an71n What do you expect to happen when on Linux a raw file is tried to execute???
This is what happens in Ubuntu 20.04!!!
@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?
@LinAdmin I'll try to write the latest image on my Pinephone (SD card and eMMC) tonight/tomorrow morning and let you know how it went. You could insert the SD-card in the phone, and try writing the image on the card, but with the phone connected to the laptop.
@LinAdmin With the latest image that I have on the phone, I can confirm that it tries like 2 times to boot and then it works. Did you gave it enough time to do its thing?
@C0n57an71n Yes I always waited long enough. What image # have you used to flash now?
@LinAdmin I'm on stable. Latest update was on 29.10.2020. I need to look from a PC because Morph doesn't show me the link to the right image on ci.ubports and the Pinephone doesn't show me in settings.
@LinAdmin That will be 86.
@LinAdmin So I've flashed the latest image on an SD card and boot it from it. After it tried 2 times, it skiped and booted from eMMC instead. So yeah. The latest images might be broken, that could explain why my Pinephone didn't update to them automatically. You can give it a try with version 86, that one works for me.
Hello, I have a short question about this. I have 3 channels in the Pinephone to choose from: dev(298), RC(15) or stable (8). What version is in the link above ? The version (88 or 86) is more stable ? and would the normal OTA updates run here as well ?
I am a bit confused. I hope you can help me with simply clear Words.