(10-06-2016, 06:57 PM)Ghost Wrote: The actual capacity of a MicroSD card varies between brands. Sounds like the image you are trying is so slightly bigger than the card you are burning onto, thus the process cannot complete.
Try burning the 8GB image, just to confirm as working.
Or as dkryder says, there's always the Android 7 build, which auto-resizes to fill out the microSD on first boot.
Well, I just dd-ed the Android 7 build (android-7.0-pine-a64-v1.4-r51.img, 4 099 932 160 bytes), but no luck. Just the red LED, and the projector where HDMI output is connected to, says no signal. The creators of Pine64 could at least have made some error screen to tell whats wrong.
I have two of these Pine64 2GB boards, and both behave the same, so, unless I got very unlucky, the problem lies within the SD card and/or the way how the image is burned on.
Previously I used this same card for Raspberry Pi 2, with no issues.
Afer dd-ing the image, the card would not normally mount on my Ubuntu, am I wrong to assume that it should mount and I'd be able to see the contents?
EDIT:
Ok, dammit, when I burned the image with the Gnome Disks utility, the result looked much better - properly partitioned drive, and it now boots, too, hooray! Pherhaps I had to dd the image to /dev/mmcblk0, instead of /dev/mmcblk0p1? Got to test that later.
