I've had the most consistent results using the below in bash shell
To usb mmc adapter:
gunzip -c android-7.1-rock-64-rock64_atv-v0.3.13-r115-raw.img.gz | sudo dd of=/dev/sdX
To sdcard
gunzip -c android-7.1-rock-64-rock64_atv-v0.3.12-r115-raw.img.gz | sudo dd of=/dev/mmcblkX
same again in xz
to mmc
xzcat rock64_20171204_stock_android_7.1.2_rooted_emmc.img.xz | sudo dd of=/dev/sdX
or to sdcard
xzcat rock64_20171204_stock_android_7.1.2_rooted_sd2emmc.img.xz | sudo dd of=/dev/mmcblkX
I don't trust etcher, or anything dd'ing w/o telling me what it's doing
For me it's /dev/sdb and /dev/mmbblk0 btw, if in doubt plug or unplug the device and do
sudo dmesg
youl'll see it activated/deactivated and what it's name is
Prob work in MacOS, and should work in win10 with Windows Subsystem for Linux
I've only done myself in Debian.
To usb mmc adapter:
gunzip -c android-7.1-rock-64-rock64_atv-v0.3.13-r115-raw.img.gz | sudo dd of=/dev/sdX
To sdcard
gunzip -c android-7.1-rock-64-rock64_atv-v0.3.12-r115-raw.img.gz | sudo dd of=/dev/mmcblkX
same again in xz
to mmc
xzcat rock64_20171204_stock_android_7.1.2_rooted_emmc.img.xz | sudo dd of=/dev/sdX
or to sdcard
xzcat rock64_20171204_stock_android_7.1.2_rooted_sd2emmc.img.xz | sudo dd of=/dev/mmcblkX
I don't trust etcher, or anything dd'ing w/o telling me what it's doing
For me it's /dev/sdb and /dev/mmbblk0 btw, if in doubt plug or unplug the device and do
sudo dmesg
youl'll see it activated/deactivated and what it's name is
Prob work in MacOS, and should work in win10 with Windows Subsystem for Linux
I've only done myself in Debian.