Me too. I finally got the ubuntu-touch-pinephone.img.gz downloaded to an RPI. After gunzip I have a file that appears to be 4000000000 in size. I run dd if=ubuntu-touch-pinephone.img of=/dev/sdb. I put the EVO Plus 32 gb microsd to which the file was written in the pinephone and get a black screen but a green led. When I tried cfdisk /dev/sdb after the dd completed to see if the microsd was flagged bootable, cfdisk couldn't handle it.
Then I tried writing the same file to an 8GB microsd. The write stopped after 5mb and now the card is dead. Not liking the fragility of the microsd cards and failing .img on the 32gb failing to do anything but sit with a black screen. This is suppose to be linux.
And why are there two .img files on the download page? Only one .img would be written to a disk or is it something else than a disk image?
soyrunner
On the RPI, I can run fdisk -lu ./*.img and get ./ubuntu-touch-pinephone.img: 3.7GB, 4000000000 bytes, 7512500 sectors; Units: 1 * 512 = 512 bytes; Sector size 512/512; I/O size 512/512; Disklabel type: dos; Disk identifier: 0xcaef1991; Device: ./ubuntu-touch-pinephone.img; Boot: *; Start: 1953; End: 7810547; Size: 3.7GB; id: 83; Type: linux
Then mount -t auto -o loop,offset999936 ./ubuntu-touch-pinephone.img /mnt/
And in /mnt/ I find all the directories one typically finds in a linux boot directory. But putting the microsd card in the pinephone only gets a black screen and a green LED.
I don't know why I can't put the sd card in an adapter and mount it on the RPI.
soyrunner.
Retrying while following these excellent instructions:
https://www.youtube.com/watch?v=Z0FMW72_OYc