07-25-2020, 04:16 PM
(07-25-2020, 02:03 PM)devrtz Wrote:(07-25-2020, 12:48 PM)Luke Wrote:Thanks for letting me know. I do not yet know what the problem is :\(07-25-2020, 10:45 AM)devrtz Wrote: I've updated the OP with new images as debian packages. I have yet to find out how to get the binaries I provided earlier from the debian packages (the resulting binary from before consists of multiple parts).
If you want to build it manually: You can grab it from here. If you are not building on a debian based system
you should look at the patch under "debian/patches/pinephone".
To manually build (from the Makefiles and such) you also need the ARM trusted firmware (ATF). Once you have ATF you need to EXPORT BL31=path-to-atf.bin and then I believe make pinephone_defconfig and make. This will give you the binaries in the form they were before (which you can dd)
Thanks! the one issue I currently have is that apt attempts to overwrite the custom uboot every time I run an upgrade now :/
And curiously it tries grabbing u-boot from upstream bullseye repo (2020.07+dfsg-1), not from the mobian repo (2020.04+dfsg-2pinephone5).
I strongly suggest not upgrading it (or reinstalling u-boot afterwards and rerunning u-boot-install-pinephone) as I believe the u-boot from debian does not support the pinephone. At least it's not listed as a supported device in the package information)
Mine attempts to fetch u-boot-sunxi-xxx, but it still broke portions of the installation and I had to reflash. For now I just decided to apt-mark hold the package.
Thanks!