NameLast modifiedSizeLicense

Parent Directory Parent Directory
other MANIFEST 13-Jan-2018 10:57 308 open
other MD5SUMS 13-Jan-2018 10:57 381 open
text R-LCR.xml 13-Jan-2018 10:57 52.7K open
application/x-tar boot.tar.bz2 27-Feb-2018 01:41 10.1M open
text changelog.txt 13-Jan-2018 10:58 937 open
application/x-sh 13-Jan-2018 10:58 394 open
text installed-files.txt 13-Jan-2018 10:58 211.7K open
other juno.img.bz2 27-Feb-2018 01:41 359.1M open
other kernel_config 13-Jan-2018 10:59 97.8K open
application/x-sh 13-Jan-2018 10:59 7.7K open
application/x-sh 13-Jan-2018 10:59 130 open
text pinned-manifest.xml 13-Jan-2018 10:59 92.3K open
other ramdisk.img 13-Jan-2018 10:59 1.4M open
text source-manifest.xml 13-Jan-2018 10:59 49.7K open
other system.img 27-Feb-2018 01:41 930.0M open
application/x-tar system.tar.bz2 27-Feb-2018 01:41 353.4M open
other userdata.img 27-Feb-2018 01:42 550.0M open
application/x-tar userdata.tar.bz2 13-Jan-2018 11:01 6.3M open
application/x-tar vendor.tar.bz2 13-Jan-2018 11:01 4.4M open

Get artifacts

Click on each link to download:

  • boot.tar.bz2
  • system.tar.bz2
  • userdata.tar.bz2

Get linaro image tools

Run following commands to install the linaro-image-tools package and dependencies:

  $ wget -O -|sudo apt-key add -
  $ sudo echo "deb trusty main" >>/etc/apt/sources.list
  $ sudo echo "deb-src trusty main" >>/etc/apt/sources.list
  $ sudo apt-get update
  $ sudo apt-get install linaro-image-tools

Change ‘trusty’ in the instructions to whichever distro release you want packages for.
For details you can reference the “Linaro Repositories” page here

If you’re using a “tip” build then we suggest you use the tip of linaro-image-tools:

  $ git clone

Flash Linaro tarball images on USB drive

Please make sure you specified the right USB drive path you see from the dmesg log for following steps,
or you could erase your hard drive with the wrong parameter.

Insert USB drive into your PC, and flash the image files with the linaro-android-media-create command:

$ linaro-android-media-create --mmc /dev/sdX --image_size 2000M --dev vexpress --system system.tar.bz2 --userdata userdata.tar.bz2 --boot boot.tar.bz2

If you’re using tip of linaro image tools

$ ./linaro-image-tools/linaro-android-media-create --mmc /dev/sdX --image_size 2000M --dev vexpress --system system.tar.bz2 --userdata userdata.tar.bz2 --boot boot.tar.bz2

Configure Juno boot time UEFI configuration

Stop at UEFI prompt and select the Shell item, it will boot up directly for you.

Accessing Source Code

Linaro Android Source Code

Download the Android building script for this build
from the list of artifacts listed above, and run it.
This script will help to download the entire source code for both Android and
the kernel and attempt to build it.

Most commonly used options for

$ ./ -h #To print the script usage
$ ./ -t #To build from the tip of the branch without overlay
$ ./ -t -o <overlay> #To build from the tip of the branch with provided overlay
$ ./ -m <pinned_manifest> -o <overlay> #To reproduce an exact build from pinned manifest
$ ./ -t -u <url-aosp-mirror-manifest> #Provide the url to your AOSP mirror manifest

The pinned manifest(pinned-manifest.xml(?) and source manifest(source-manifest.xml) can be found from the list of artifacts

Compiling Linaro Android RootFS+Kernel

The following simple steps download, install and compile a complete Linaro Android distribution

  • Download and install Ubuntu 14.04 64 bit or newer (download)
  • Download the Android building script for this build from the list of artifacts listed above
  • Run the script

Build from the tip of the source:

chmod a+x
./ -t  or  ./ -t -u <url-aosp-mirror-manifest>

Or reproduce the exactly the same as this buid:

chmod a+x
./ -m pinned-manifest.xml or ./ -m pinned-manifest.xml -u <url-aosp-mirror-manifest>

Installing Android on your board

cd android/out/target/product/juno
sudo linaro-android-media-create --mmc /dev/sdX --dev vexpress --boot boot.tar.bz2 --system system.tar.bz2 --userdata userdata.tar.bz2

Insert the USB drive into your board and reboot it. You must configure UEFI each time you create a new disk image.