Bootable OS images

= GNU/Linux =

When the image you download is made for a different type of device (eg. Cubieboard vs MK802) but using the same CPU (eg. A10) you should be able to use it after updating u-boot and script.bin from your particular hwpack.

Some images that use very little hardware like the headless server images might work without changes on many devices.

Arch

 * ArchLinuxARM Official
 * ArchLinuxARM

Berryboot
keep in mind berryboot is not a recommended boot image for A10 devices


 * Berryboot

Kali

 * Kali Linux on Cubieboard

Linaro

 * Ubuntu and Linaro images by Martin Wild
 * CUBIUNTU 12.11 with 3.4 kernel for A10/A20 Cubieboard by isaac chavarria
 * Linaro desktop with 3.4 kernel for A20 EOMA68 by jm

Mer

 * mer-test images
 * Mer images for Improv

Tiny Core

 * ARMv7 Allwinner A10 official port

Ubuntu

 * Mele: Ubuntu 12.10 armhf base with nand install
 * Minimal Ubuntu 12.04.2 LTS with 3.4.29 kernel image for A13-OLinuXino
 * Ubuntu 12.04 desktop with 3.4 kernel image for A10-Cubieboard(nand install)
 * Ubuntu 13.03 server with 3.4 kernel image for A10-Cubieboard(nand install)
 * Ubuntu 12.04 desktop with 3.3 kernel image for A20-Cubieboard(nand install)
 * MK802 Ubuntu Images by Miniand
 * Ubuntu and Linaro images by Martin Wild
 * Ubuntu 13.04 Desktop Linux with 3.4 kernel for A20 EOMA68 and Cubieboard2 by jm
 * Ubuntu 13.04 Desktop Linux with 3D acceleration with stage 3.4 kernel for A20 EOMA68 and Cubieboard2 by jm

= Android =

Android is typically installed to the internal nand flash using LiveSuit or PhoenixCard.

It is not easily possible to update the script.bin in LiveSuit images so you need an image for your particular device. Old android images would let the bootloader present on the nand set up memory controller so there is better chance of compatibility.

Cubieboard

 * Cubieboard download page Android TV box and testing images for LiveSuit (bottom of page) - HDMI TV output