07-30-2016, 10:27 PM
(07-30-2016, 08:31 PM)Hbtr Wrote: Hello all,
I am quite a bit frustrated. Just received my Pine64 and began to study how to put it to work. Got two different MicroSD card (16GB and 64GB) and downloaded the images of Android OS and Remix OS. But when I went to burn the images, the things started to get out of the tracks.
In both cards, and using different OS, I was not able to burn any of the images until now (after two days trying). In all cases the error that occurs is related to the size of the image, that does not match with the size of the card. I searched for help on the web and I found that it is possible to shrink the image file. But I must confess that its not something simple for newbies and for windows users, that it's my case.
Can anyone help me with this issue?
Sincerely
Hbtr
Hbtr, I understand your frustration quite well. I got all the last parts I ordered this week and started looking into which image to use for my 32 GB microSD. I started with the 32 GB image for RemixOS 2.0 using the tools recommended, first PhoenixCard and then Win32DiskImager. Both gave some error but not indicating a 32 GB image file just doesn't fit a 32 GB memory card because it's effective available space is 29 GB and change. Seriously!!! Why do the "image builders" create image files that won't fit the memory cards? I ended up using the 16 GB image file.
I found using Rufus by miles the superior tool on Windows to create boot-able images, and it's faster than the two recommended tools. It also gives you a much better message than either the two aforementioned utilities.
You can find Rufus 2.10 (at present) Rufus.
If you point Rufus to an 'img' file, it already figures you want to use DD instead of the default.
I hope this helps to get the stress levels down to an acceptable range...
Cheers,
John