+- PINE64 (https://forum.pine64.org)
+-- Forum: PinePhone (https://forum.pine64.org/forumdisplay.php?fid=120)
+--- Forum: PinePhone Software (https://forum.pine64.org/forumdisplay.php?fid=121)
+---- Forum: UBPorts on PinePhone (https://forum.pine64.org/forumdisplay.php?fid=125)
+---- Thread: Ubports OTA won't work on my braveheart (/showthread.php?tid=9928)
Pages:
1
2
Ubports OTA won't work on my braveheart - none - 05-22-2020
I've tried for a week now. I've followed the ubports install instructions on multiple sd cards and on the emmc using jumpdrive. Nothing works.
I get a ubuntu logo, some non working progress dots, a flickering screen. Sometimes I get to the setup app, it crashes before I can finish.
I had ubports running well on the emmc before the ota img was available, what's gone wrong?
RE: Ubports OTA won't work on my braveheart - pawlinski - 05-22-2020
I have the exact same situation.
RE: Ubports OTA won't work on my braveheart - davidbe - 05-22-2020
Same here... I feel like it is more unstable now. I managed to update to #29, but that didn't make any difference. You might try https://forum.pine64.org/showthread.php?tid=9901
RE: Ubports OTA won't work on my braveheart - falkensmaze - 05-22-2020
Unfortunately, I have also been having this same issue since flashing OTA-12. I still have some of the older UT images from April on my machine, and I have no problems at all running them. I tried again last night with a fresh re-flash of one of the newer builds and while it did take awhile to boot into the OS through bootloops and black screens, I was eventually update to #29, but alas, I wasn't even able to boot into the operating system again after that.
At the moment, the newer UT builds are the only images with this issue on my end, sadly (it is the OS I hope to be able to daily drive eventually). I've also tested KDE neon mobile, deb+phosh, and pmOS all with no problems.
RE: Ubports OTA won't work on my braveheart - somken - 05-22-2020
... Odd, I have no problems. Outside of the GPS bits being lost in the latest build. I have no issues. Been using Etcher to burn the image to my SD card and the phone boots no problem.
RE: Ubports OTA won't work on my braveheart - kugiigi - 05-22-2020
I don't have these problems as well. So far OTA works fine on my PinePhone. Although, it seems that UT is more prone to partition/file system corruption now. It could happen after an OTA or in my case a hard shutdown. In these cases, you will be stuck in a blank screen after the pine64 screen. This is fixable by running fsck on the corrupted partition though.
Also, just to clear to everyone that OTA-12 isn't relevant to the pinephone because its development is separate from the other UT supported devices for now. So basciallyicthere's no OTA-12 for the pinephone.
RE: Ubports OTA won't work on my braveheart - Nooblife - 05-23-2020
First time my userdata was corrupted, and this time it was the cache. fsck fixed it for me.
RE: Ubports OTA won't work on my braveheart - none - 05-24-2020
(05-22-2020, 11:20 PM)kugiigi Wrote: I don't have these problems as well. So far OTA works fine on my PinePhone. Although, it seems that UT is more prone to partition/file system corruption now. It could happen after an OTA or in my case a hard shutdown. In these cases, you will be stuck in a blank screen after the pine64 screen. This is fixable by running fsck on the corrupted partition though.
Also, just to clear to everyone that OTA-12 isn't relevant to the pinephone because its development is separate from the other UT supported devices for now. So basciallyicthere's no OTA-12 for the pinephone.
I read the post about using fsck. none of my partitions are corrupted. the problem still persists.
RE: Ubports OTA won't work on my braveheart - falkensmaze - 05-26-2020
(05-24-2020, 07:45 AM)none Wrote:(05-22-2020, 11:20 PM)kugiigi Wrote: I don't have these problems as well. So far OTA works fine on my PinePhone. Although, it seems that UT is more prone to partition/file system corruption now. It could happen after an OTA or in my case a hard shutdown. In these cases, you will be stuck in a blank screen after the pine64 screen. This is fixable by running fsck on the corrupted partition though.
Also, just to clear to everyone that OTA-12 isn't relevant to the pinephone because its development is separate from the other UT supported devices for now. So basciallyicthere's no OTA-12 for the pinephone.
I read the post about using fsck. none of my partitions are corrupted. the problem still persists.
I've tried with fsck as well, each time with different, freshly formatted sd cards and fresh installs of UT.
It's always the same three partitions that can't mount, and I get errors with superblocks each time, always like this:
Code:
$ sudo fsck /dev/sdb1
fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb1
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>I've tried e2fsck as well, to no avail. I'm only having these issues with builds of UT since May 12 on my Pinephone. All other images (postmarketOS, deb+phosh, etc) that I have tested so far (a few on the same sd cards) do just fine.
I might go out and purchase a few more sd cards just to make sure that I haven't corrupted these beyond repair somehow, but it is odd that I'm not having issues with any other images, and older builds of UT that I still have on my machine are able to boot just fine with no crashes/black screens/etc.
RE: Ubports OTA won't work on my braveheart - Mangled - 05-29-2020
I too am having issues flashing the images. I tried an image as far back as #7 and does not boot. I do not have these issues with mobian nor sailfish or any other distro. Seems to be a ub-port issue.