Running Builds-CSDN博客

来自： http://source.android.com/source/running.html

Running Builds

This page provides details for running builds on specific devices and is designed to complement the information in Building the System.

Building fastboot and adb

If you don't already have fastboot and adb, you can build them with the regular build system. Use the instructions in Building a System and replace the main make command with:

$ make fastboot adb

Booting into fastboot mode

During a cold boot of a device, use the following key combinations to boot into fastboot mode, which is a mode in the bootloader that can be used to flash the device:

Device	Keys
hikey	Link pins 1 - 2 and 5 - 6 of J15
angler	Press and hold Volume Down, then press and hold Power
bullhead	Press and hold Volume Down, then press and hold Power
shamu	Press and hold Volume Down, then press and hold Power
fugu	Press and hold Power
volantis	Press and hold Volume Down, then press and hold Power
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

You can also use the command adb reboot bootloader to reboot from Android directly into the bootloader with no key combinations.

Unlocking the bootloader

It's possible to flash a custom system only if the bootloader allows it, and the bootloader is locked by default. You can unlock the bootloader, but be aware that doing so deletes the user data for privacy reasons (the unlock operation needs to run only once). After unlocking, all data on the device 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 back up any precious files before unlocking the bootloader.

With the device in fastboot mode, unlock the bootloader using:

$ fastboot oem unlock

The procedure must be confirmed on-screen.

On Nexus 10, after unlocking the bootloader, the internal storage remains unformatted. You can format the device using:

$ fastboot format cache
$ fastboot format userdata

To re-lock the bootloader, use:

$ fastboot oem lock

Note: Re-locking the bootloading on a Motoroal Xoom erases user data (including the shared USB data).

Obtaining proprietary binaries

AOSP cannot be used from pure source code only and requires additional hardware-related proprietary libraries to run, specifically for hardware graphics acceleration.

Downloading proprietary binaries

You can download official binaries for the supported devices running tagged AOSP release branches from Google's Nexus driver page. These binaries 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, use the binaries for the most recent numbered release or with the most recent date.

Extracting proprietary binaries

Each set of binaries comes as a self-extracting script in a compressed archive. Uncompress each archive, run the included self-extracting script from the root of the source tree, then confirm that you agree to the terms of the enclosed license agreement. The binaries and their matching makefiles will be installed in the vendor/ hierarchy of the source tree.

Cleaning up

To ensure the newly installed binaries are properly taken into account after being extracted, delete the existing output of any previous build using:

$ make clobber

Selecting a device build

The recommended builds for devices are available from the lunch menu, accessed when running the lunch command with no arguments. You can download factory images and binaries for Nexus devices from:

Device	Code name	Build configuration
HiKey	hikey	hikey-userdebug
Nexus 6P	angler	aosp_angler-userdebug
Nexus 5X	bullhead	aosp_bullhead-userdebug
Nexus 6	shamu	aosp_shamu-userdebug
Nexus Player	fugu	aosp_fugu-userdebug
Nexus 9	volantis (flounder)	aosp_flounder-userdebug
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
PandaBoard (Archived)	panda	aosp_panda-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

Note: Do not use Android 4.1.1 on a Nexus 7 originally sold with Android 4.1.2 or newer.

Flashing a device

You can flash an entire Android system in a single command; doing so verifies the system being flashed is compatible with the installed bootloader and radio, writes the boot, recovery, and system partitions together, and then reboots the system. Flashing also erases all user data, similarly to fastboot oem unlock.

To flash a device, set the device in fastboot mode (if necessary) and run:

$ fastboot -w flashall

Note: Filesystems created via fastboot on Motorola Xoom do not function optimally. We recommend re-creating filesystems through recovery, using: $ adb reboot recovery. While in recovery, open the menu (press Power + Volume Up), wipe the cache partition, then wipe data.

Restoring devices to 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.