Build for devices

Build for devices

This page complements the Home Page's personal device building details.

The currently released devices are Galaxy Nexus, Motorola xoom, Nexus S, and Nexus S 4G.

Galaxy Nexus supports only the GSM/HSPA + configuration of "maguro" and only the "yakju" or "takju" operating system originally sold.

Motorola xoom supports the Wi-Fi configuration "wingray" sold in USA ".

Nexus S supports all configurations. The Nexus S 4G is supported.

In addition, pandaboard a.k. A. "Panda" only supports the primary branch, but it is currently considered as an experiment. Detailed Description: Use a pandaboard to use the android open source project in the source tree file
device/ti/panda/README.

Nexus One a.k. A. "passion" is outdated. It is an experiment in gingerbread and is not supported. It cannot use a new version of the android open-source project.

Android developer phone (adp1 and adp2, a.k. a. "Dream" and "sapphire") are outdated, labs and not supported in froyo, and new versions of Android open-source projects cannot be used.

In the open-source Android project, no CDMA devices are supported.

Build fastboot and ADB

If you do not already have these tools, fastboot and ADB can be built with qualified build systems. This page describes how to build and replace a master.
makeCommand

$ make fastboot adb

Boot to fastboot Mode

During a cold boot, the following key combinations can be used to boot to fastboot mode, and one bootloader mode can be used to burn the device:

Device	Key
Maguro	Press and hold bothVolume upAndVolume downAnd then press and holdPower Supply
Panda	Press and holdInput, And then pressPower Supply
Wingray	Press and holdVolume downAnd then press and holdPower Supply
Crespo	Press and holdVolume upAnd then press and holdPower Supply
Passion	Press and hold the trackball, and then pressPower Supply
Sapphire	Press and holdReturn, And then pressPower Supply
Dream	Press and holdReturn, And then pressPower Supply

Also, when the device runs froyo or later, ADB is enabled.adb reboot bootloaderIt can be used to restart directly from Android to bootloader without a key combination.

Unlock the boot program

It is only possible to burn a custom system, if the boot program permits it.

This is set in adp1 and adp2 by default.

On Nexus One, Nexus S, Nexus S 4G, xoom, and Galaxy Nexus, the Bootstrap program is locked by default. The device enters fastboot mode and is used to unlock the boot program.

$ fastboot oem unlock

The process must be confirmed on the screen and the user data must be deleted for privacy reasons. It only needs to be run once.

Note that data on all phones is erased on Nexus S, Nexus S 4G, Motorola xoom, and Galaxy Nexus. This includes private data of applications and shared data that has accessed USB, including photos and videos. Make sure to make a backup of any precious file before you unlock the bootloader.

On Nexus One, this behavior invalidates the warranty and is irreversible.

On Nexus S, Nexus S 4G, xoom, and Galaxy Nexus, the boot program can be locked for reuse.

$ fastboot oem lock

Note that this is to erase user data on the xoom (including shared USB data ).

Obtain a proprietary binary file

At the beginning of icecreamsandwich, the android open-source project cannot be used to run libraries only from pure source code, and requires additional hardware-related ownership, especially hardware graphics acceleration.

Official binary files of Nexus S, Nexus S 4G, Galaxy Nexus and pandaboard can be downloaded from Google's nexus driver page to add non-open source code for accessing additional hardware capabilities.

When a device is supported in the master branch, most of the latest binary file numbers are published once in the master branch.

Nexus One, adp2, or adp1 do not have official binary files.

Extract private binary files

Each group of binary files is compressed and archived as a self-extracting script. After extracting each archive, run the include self-extraction script from the root of the source tree to confirm that you agree to the terms of the license agreement and that the binary files match them with makefileswill to obtain the vendor installed on the source tree/Class.

When a private binary file is added for cleanup

To ensure that the newly installed binary file is correct, considering the extracted account, the existing output of any existing build needs to be deleted

$ make clobber

Select the configuration that matches the device with the build

This step configures and builds the android open source project description on this page about the build.

It is recommended that the building for each device is effective through the lunch menu, when runninglunchWhen the command does not have parameters, access:

Device	Branch	Build configurations
Maguro	Android-4.0.4_r2.1 or master	Full_maguro-userdebug
Panda	Master	Full_panda-userdebug
Wingray	Android-4.0.4_r2.1 or master	Full_wingray-userdebug
Crespo	Android-4.0.4_r2.1 or master	Full_crespo-userdebug
Passion	Android-2.3.7_r1	Full_passion-userdebug
Sapphire	Android-2.2.3_r1	Full_sapphire-userdebug
Dream	Android-2.2.3_r1	Full_dream-userdebug

Burn a device

Set the device to fastboot mode, if required (see above ).

Because user data is usually incompatible with Android, it is usually better to delete a new system when it is burned.

$ fastboot erase cache$ fastboot erase userdata

A single command is used to enable the startup of an entire android system. After the system partition is verified together with the system partition, the system is installed with compatible boot guide and radio, and restart the system.

$ fastboot flashall

Except for partitions on all devices, the preceding command can be replaced with a single command.

$ fastboot -w flashall

Note that creating a file system through fastboot on Motorola xoom is not optimal, and it is strongly recommended that you recreate them through restoration

$ adb reboot recovery

Once restored, open the menu (by power + volume), erase the cache partition, and then erase the data.

Nexus S, Nexus S 4G and Galaxy Nexus boot guide and Cell Station compatibility

On Nexus S, Nexus S 4g, and Galaxy Nexus, each version of Android has only a specific version of the boot loader and cell radio software that is tested. However, incompatibility is expected. When running the new system with the old boot program and radio station image according to the following table.

Nexus S (Worldwide "XX", i9020t and i9023 ):

Android version	First boot the program	Preferred radio station	It is also possible
2.3 (grh55)	I9020xxjk1	I9020xxjk8
2.3.1 (grh78)	I9020xxjk1	I9020xxjk8
2.3.2 (grh78c)	I9020xxjk1	I9020xxjk8
2.3.3 (gri40)	I9020xxka3	I9020xxkb1	All previous versions
2.3.4 (grj22)	I9020xxka3	I9020xxkd1	All previous versions
2.3.5 (grj90)	I9020xxka3	I9020xxkf1	All previous versions
2.3.6 (grk39f)	I9020xxka3	I9020xxkf1	All previous versions
4.0.3 (iml74k)	I9020xxkl1	I9020xxki1	All previous versions
4.0.4 (imm76d)	I9020xxkl1	I9020xxki1
4.0.4 (imm76i)	I9020xxkl1	I9020xxki1
4.0.4 (imm76k)	I9020xxkl1	I9020xxki1
4.0.4 (imm76l)	I9020xxkl1	I9020xxki1

Nexus S (850 MHz version "UC", i9020a ):

Android version	Preferred Bootstrap program	Preferred radio station	It is also possible
2.3.3 (gri54)	I9020xxka3	I9020uckb2
2.3.4 (grj22)	I9020xxka3	I9020uckd1	All previous versions
2.3.5 (grj90)	I9020xxka3	I9020uckf1	All previous versions
2.3.6 (grk39c)	I9020xxka3	I9020uckf1	All previous versions
2.3.6 (grk39f)	I9020xxka3	I9020uckf1	All previous versions
4.0.3 (iml74k)	I9020xxkl1	I9020uckf1	All previous versions
4.0.4 (imm76d)	I9020xxkl1	I9020uckj1
4.0.4 (imm76i)	I9020xxkl1	I9020uckj1
4.0.4 (imm76k)	I9020xxkl1	I9020uckj1
4.0.4 (imm76l)	I9020xxkl1	I9020uckj1

Nexus S (Korean version "KR", m200 ):

Android version	Preferred Bootstrap program	Preferred radio station	It is also possible
2.3.3 (gri54)	I9020xxka3	I9020krkb3
2.3.4 (grj22)	I9020xxka3	M200krkc1	All previous versions
2.3.5 (grj90)	I9020xxka3	M200krkc1	All previous versions
2.3.6 (grk39f)	I9020xxka3	M200krkc1	All previous versions
4.0.3 (iml74k)	I9020xxkl1	M200krkc1	All previous versions
4.0.4 (imm76d)	I9020xxkl1	M200krkc1
4.0.4 (imm76i)	I9020xxkl1	M200krkc1
4.0.4 (imm76k)	I9020xxkl1	M200krkc1
4.0.4 (imm76l)	I9020xxkl1	M200krkc1

Nexus S 4G (CDMA/WiMAX version, d720 ):

Android version	Preferred Bootstrap program	Preferred radio station	It is also possible
4.0.4 (imm76l)	D720sprke1	D720sprlc1

Galaxy Nexus (GSM/HSPA + ):

Android version	Preferred Bootstrap program	Preferred radio station	It is also possible
4.0.1 (itl41d)	Primekj10	I9250xxkk1
4.0.2 (icl53f)	Primekk15	I9250xxkk6	All previous versions
4.0.3 (iml74k)	Primekl01	I9250xxkk6	All previous versions
4.0.4 (imm76d)	Primela03	I9250xxla02
4.0.4 (imm76i)	Primela03	I9250xxla02
4.0.4 (imm76k)	Primela03	I9250xxla02
4.0.4 (imm76l)	Primela03	I9250xxla02

Assume that you are building an Android app. Assume that your Nexus S, Nexus S 4g, or Galaxy Nexus has an old boot program and a radio image, which is marked as a possible table above, but fastboot is not recognized. You can delete it locally.
version-bootloaderAndversion-basebandRow in device/samsung/crespo/board-info.txtOr
device/samsung/maguro/board-info.txt

Restores a device to its original factory status.

Factory images and Nexus S (and all variants) of Galaxy Nexus (GSM/HSPA + "yakju" and "takju", and CDMA/LTE "mysid) is available from Google's factory image page.

The factory image of Motorola xoom is directly released by Motorola.

Nexus One does not have a valid Factory image.