In this document
This page complements the main page about Building and Running with information that is specific to individual devices.
With the current release, it is possible to build for Nexus 4, Nexus 7, and for some variants of Galaxy Nexus. The exact level of functionality for each device depends on the availability of the relevant proprietary hardware-specific binaries.
For Nexus 4 and Nexus 7, all configurations can be used, and all the hardware is functional. Due to hardware differences, do not use 4.1.1 on a Nexus 7 that was originally sold with 4.1.2 or newer.
All configurations of Nexus 10 "manta" can be used with 4.2.2. On those devices, graphics, audio, Wi-Fi, Bluetooth, camera, NFC, GPS and orientation sensors are functional.
The variants of Galaxy Nexus that can be used are the GSM/HSPA+ configuration "maguro" (only if it was originally sold with a "yakju" or "takju" operating system) and the VZW CDMA/LTE configuration "toro". On those devices, graphics and audio are functional, as well as Wi-Fi, Bluetooth, and access to the respective cellular networks. NFC and the orientation sensors are functional.
The Sprint CDMA/LTE configuration "toroplus" of Galaxy Nexus is supported experimentally, in the jb-mr1-dev-plus-aosp branch. On that configuration, the cellular network is not functional, and the other peripherals work like they do on "toro".
The Motorola Xoom can be used in the Wi-Fi configuration "wingray" sold in the USA, with Android 4.1.2. Graphics and audio are functional as well as Wi-Fi and Bluetooth and the orientation sensors.
All configurations of Nexus S and Nexus S 4G can be used with Android 4.1.2. On those devices all the hardware is functional.
In addition, PandaBoard a.k.a. "panda" can be used
in the jb-mr1-dev-plus-aosp branch, but is considered experimental.
The specific details to use a PandaBoard with the Android Open-Source Project
are in the file
device/ti/panda/README in the source tree.
Building fastboot and adb
If you don't already have those tools, fastboot and adb can be built with
the regular build system. Follow the instructions on the page about
Building and Running, and replace the main
make command with
$ make fastboot adb
Booting into fastboot mode
During a cold boot, the following key combinations can be used to boot into fastboot mode, which is a mode in the bootloader that can be used to flash the devices:
|hammerhead||Press and hold both Volume Up and Volume Down, then press and hold Power|
|flo||Press and hold Volume Down, then press and hold Power|
|deb||Press and hold Volume Down, then press and hold Power|
|manta||Press and hold both Volume Up and Volume Down, then press and hold Power|
|mako||Press and hold Volume Down, then press and hold Power|
|grouper||Press and hold Volume Down, then press and hold Power|
|tilapia||Press and hold Volume Down, then press and hold Power|
|phantasm||Power the device, cover it with one hand after the LEDs light up and until they turn red|
|maguro||Press and hold both Volume Up and Volume Down, then press and hold Power|
|toro||Press and hold both Volume Up and Volume Down, then press and hold Power|
|toroplus||Press and hold both Volume Up and Volume Down, then press and hold Power|
|panda||Press and hold Input, then press Power|
|wingray||Press and hold Volume Down, then press and hold Power|
|crespo||Press and hold Volume Up, then press and hold Power|
|crespo4g||Press and hold Volume Up, then press and hold Power|
Also, the command
adb reboot bootloader can be used to reboot from
Android directly into the bootloader with no key combinations.
Unlocking the bootloader
It's only possible to flash a custom system if the bootloader allows it.
The bootloader is locked by default. With the device in fastboot mode, the bootloader is unlocked with
$ fastboot oem unlock
The procedure must be confirmed on-screen, and deletes the user data for privacy reasons. It only needs to be run once.
All data on the phone is erased, i.e. both the applications' private data and the shared data that is accessible over USB, including photos and movies. Be sure to make a backup of any precious files you have before unlocking the bootloader.
On Nexus 10, after unlocking the bootloader, the internal storage is left unformatted and must be formatted with
$ fastboot format cache $ fastboot format userdata
The bootloader can be locked back with
$ fastboot oem lock
Note that this erases user data on Xoom (including the shared USB data).
Obtaining proprietary binaries
The Android Open-Source Project can't be used from pure source code only, and requires additional hardware-related proprietary libraries to run, specifically for hardware graphics acceleration.
Official binaries for the supported devices running tagged AOSP release branches can be downloaded from Google's Nexus driver page. These add access to additional hardware capabilities with non-open-source code. To instead build the AOSP master branch, use the Binaries Preview for Nexus Devices.
When building the master branch for a device, the binaries for the most recent numbered release or with the most recent date are the ones that should be used.
Extracting the proprietary binaries
Each set of binaries comes as a self-extracting script in a compressed archive.
After uncompressing each archive, run the included self-extracting script
from the root of the source tree, confirm that you agree to the terms of the
enclosed license agreement, and the binaries and their matching makefiles
will get installed in the
vendor/ hierarchy of the source tree.
Cleaning up when adding proprietary binaries
In order to make sure that the newly installed binaries are properly taken into account after being extracted, the existing output of any previous build needs to be deleted with
$ make clobber
Picking and building the configuration that matches a device
The steps to configure and build the Android Open Source Project are described in the Building page.
The recommended builds for the various devices are available through
the lunch menu, accessed when running the
lunch command with no arguments. Factory images and binaries for Nexus devices can be downloaded from:
|Device||Code name||Build configuration|
|Nexus 5 (GSM/LTE)||hammerhead||aosp_hammerhead-userdebug|
|Nexus 7 (Wi-Fi)||razor (flo)||aosp_flo-userdebug|
|Nexus 7 (Mobile)||razorg (deb)||aosp_deb-userdebug|
|Nexus 10||mantaray (manta)||full_manta-userdebug|
|Nexus 4||occam (mako)||full_mako-userdebug|
|Nexus 7 (Wi-Fi)||nakasi (grouper)||full_grouper-userdebug|
|Nexus 7 (Mobile)||nakasig (tilapia)||full_tilapia-userdebug|
|Galaxy Nexus (GSM/HSPA+)||yakju (maguro)||full_maguro-userdebug|
|Galaxy Nexus (Verizon)||mysid (toro)||aosp_toro-userdebug|
|Galaxy Nexus (Experimental)||mysidspr (toroplus)||aosp_toroplus-userdebug|
|Motorola Xoom (U.S. Wi-Fi)||wingray||full_wingray-userdebug|
|Nexus S||soju (crespo)||full_crespo-userdebug|
|Nexus S 4G||sojus (crespo4g)||full_crespo4g-userdebug|
Do not use 4.1.1 on a Nexus 7 that was originally sold with 4.1.2 or newer.
Flashing a device
Set the device in fastboot mode if necessary (see above).
An entire Android system can be flashed in a single command: this writes
the boot, recovery and system partitions together after verifying that the
system being flashed is compatible with the installed bootloader and radio,
and reboots the system. This also erases all the user data, similarly to
fastboot oem unlock mentioned earlier.
$ fastboot -w flashall
Note that filesystems created via fastboot on Motorola Xoom aren't working optimally, and it is strongly recommended to re-create them through recovery
$ adb reboot recovery
Once in recovery, open the menu (press Power + Volume Up), wipe the cache partition, then wipe data.
Restoring a device to its original factory state
Factory images for Nexus 5, Nexus 10, Nexus 4, Nexus Q, Nexus 7, Galaxy Nexus (GSM/HSPA+ "yakju" and "takju", and CDMA/LTE "mysid" and "mysidspr"), Nexus S, and Nexus S 4G are available from Google's factory image page.
Factory images for the Motorola Xoom are distributed directly by Motorola.