02-17-2019, 06:35 PM
(This post was last modified: 02-18-2019, 07:58 PM by daidokoro.
Edit Reason: fix the prose so it makes more sense
)
I’m having the same problems booting Android as described above.
I'm able to load Armbian to either media (SD or eMMC) and boot it successfully complete
with a working desktop.
Android is another story. I've tried burning several images to media on both
Linux and W10 just to make sure. It's a similar story in both OSes. All attempts failed.
Under Linux I am using the DD method. I download an image and unzip it. Next I DD it to the media.
When I look at it with fdisk I have a wierd looking partition table.
Under W10 I use Etcher and it complains that the unzipped image doesn't have a valid partition table.
and wants to know if I want to go ahead.
What am I doing wrong?
I'm able to load Armbian to either media (SD or eMMC) and boot it successfully complete
with a working desktop.
Android is another story. I've tried burning several images to media on both
Linux and W10 just to make sure. It's a similar story in both OSes. All attempts failed.
Under Linux I am using the DD method. I download an image and unzip it. Next I DD it to the media.
When I look at it with fdisk I have a wierd looking partition table.
Under W10 I use Etcher and it complains that the unzipped image doesn't have a valid partition table.
and wants to know if I want to go ahead.
What am I doing wrong?