Cyanogenmod ROM Motorola Moto X (T-Mobile) (xt1053)

Cyanogenmod ROM Motorola Droid RAZR/RAZR MAXX (CDMA) (spyder)

Quick Info

Check out Motorola Droid RAZR/RAZR MAXX (CDMA) (“spyder”) with newer LineageOS software

Download CyanogenMod

Download (nightly build)
CyanogenMod 13.0 (Android 6.0/6.0.1 (Marshmallow))

Main sections for Motorola Droid RAZR/RAZR MAXX (CDMA) (“spyder”)

1. Information about Motorola Droid RAZR/RAZR MAXX (CDMA) (“spyder”)
2. CyanogenMod install guide for Motorola Droid RAZR/RAZR MAXX (CDMA) (“spyder”)
3. Build CyanogenMod and CyanogenMod Recovery guide

Notes

This is a KEXEC build and must be installed in SafeStrap (builds older than 9/1/2013 must be installed on rom-slot1). CM-12.0 requires at least Safestrap v3.75.

Special boot modes

• Recovery: Power and at SafeStrap splash screen press Menu key within 10 seconds
• Bootloader: Vol Up & Vol Down & Power
• Fastboot: Vol Down & Power

Source code

Device	http://www.github.com/cyanogenmod/android_device_motorola_spyder
Kernel	http://www.github.com/cyanogenmod/android_kernel_motorola_omap4-common

Droid RAZR/RAZR MAXX (CDMA) Specifications

Codename:	spyder
Vendor:	Motorola
Release date:	2011 November 11
Carrier:	Verizon
Type:	phone
GSM freq:	850/900/1800/1900 HSDPA 850/900/1900/2100
CDMA freq:	800/1900 CDMA2000 1xEV-DO
LTE freq:	700 MHz Class 13
Platform:	TI OMAP4430
CPU:	1.2 GHz dual-core Cortex-A9
GPU:	PowerVR SGX540
RAM:	1GB
Weight:	127 g (4.48 oz)
Dimensions:	130.7 x 68.9 x 7.1 mm (5.15 x 2.71 x 0.28 in)
Screen size:	109 mm (4.3 in)
Resolution:	540 x 960
Screen density:	256 ppi
Screen type:	Super AMOLED capacitive touchscreen
Internal storage:	16GB
SD Card:	microSD, up to 32 GB, 16 GB included
Bluetooth:	v4.0 with LE+EDR
Wi-Fi:	Wi-Fi 802.11 b/g/n
Main camera:	8MP, flash: LED
Secondary camera:	2MP
Power:	1780 mAh
Peripherals:	Accelerometer, proximity, compass, GPS
CM supported:	10.1, 10.2, 11, 12, 12.1, 13

How to Install CyanogenMod on the Motorola Droid RAZR/RAZR MAXX (CDMA) (spyder)

Important Notes

This is a KEXEC build and must be installed in SafeStrap (builds older than 9/1/2013 must be installed on rom-slot1). CM-12.0 requires at least Safestrap v3.75.

Gaining Root Access with RazrBlade (Windows Only)

1. Download the following file: (Credit to djrbliss)
   • Razr Blade Windows: Download
2. Download and install the Motorola device drivers.
   • Motorola device drivers
3. Unzip Razr Blade to a folder on your computer.
4. Enable USB debugging on the Droid RAZR/RAZR MAXX (CDMA): Settings > Developer Options and check the USB debugging box.
5. Clear Smart Actions Data: Settings > Apps > Smart Actions and click the Clear data button.
6. Ensure that your data is not encrypted: Settings > Security & Screen Lock > Data Encryption and uncheck both boxes, then press Apply
7. Confirm Droid RAZR/RAZR MAXX (CDMA) is using MTP for USB connection: Settings > Storage > ≡(Menu) Button > USB computer connection > Select Media device (MTP)
8. Connect the Droid RAZR/RAZR MAXX (CDMA) to the computer via USB.
9. On the computer, double click the run.bat file
10. Allow the exploit to finish, the Droid RAZR/RAZR MAXX (CDMA) may reboot several times.
11. When the exploit says “Cleaning up” you may need to look at your phone, unlock the screen if necessary, and press the “Grant” button to grant SuperUser permissions for the exploit to finish.
12. The Droid RAZR/RAZR MAXX (CDMA) is now rooted.

Installing SafeStrap Recovery

1. Download the SafeStrap APK for Droid RAZR/RAZR MAXX (CDMA): Download
   • md5: 896edcc80bc1b670c461508cc7d7af1e
2. Place the downloaded APK alongside adb on your computer.
3. Enable installation from unknown sources on your Droid RAZR/RAZR MAXX (CDMA): Settings > Security and check the Unknown sources box.
4. Open a terminal on your computer and navigate to the adb executable and run the following: adb install YOURAPK.apk
5. If you see [SUCCESS] in the terminal, continue on.

   NOTE: If you see [FAILED], please go back and ensure you’ve followed the instructions above to the letter.

6. Run the SafeStrap app on the Droid RAZR/RAZR MAXX (CDMA).
7. Once requested, permanently grant the application Superuser access.
8. Click the button labeled Install Recovery.
9. Once complete, reboot the device.
10. When the SafeStrap splash screen appears, hit the Menu button on your Droid RAZR/RAZR MAXX (CDMA).
11. Click the button labeled Boot Options.
12. Activate romslot-1 and follow the instructions on the device.
13. We will be updating SafeStrap to use all ROM slots for Kexec soon.
14. Follow the instructions below for installing CyanogenMod from recovery.

Installing CyanogenMod from recovery

1. Make sure your computer has working adb.
2. Download the CyanogenMod build package for your device that you’d like to install to your computer.

   Optional: Download 3rd party applications packages, like Google Apps which are necessary to download apps from Google Play.

3. Place the CyanogenMod .zip package, as well as any optional .zip packages, on the root of /sdcard:
   • Using adb: adb push filename.zip /sdcard/

   Note: You can copy the .zip packages to your device using any method you are familiar with. The adb method is used here because it is universal across all devices and works in both Android and recovery mode. If you are in recovery mode, you may need to ensure /sdcard (sometimes called Internal Storage) is mounted by checking its status in the Mounts menu. If you have booted regularly, USB debugging must be enabled.

4. If you are not already in recovery, boot to recovery mode now.
   • Power and at SafeStrap splash screen press Menu key within 10 seconds
5. In Team Win Recovery Project, select menu choices by tapping on the appropriately labelled button.
6. Optional (Recommended): Select the Backup button to create a backup.
7. Select Wipe and then Factory Reset.
8. Select Install.
9. Navigate to /sdcard and select the CyanogenMod .zip package.
10. Follow the on-screen notices to install the package.
11. Optional: Install any additional packages you wish using the same method (if you are installing multiple packages, install CyanogenMod first and then install any subsequent packages on top of it).
12. Once installation has finished, return to the main menu and select Reboot, then System. The device will now boot into CyanogenMod.

How To Build CyanogenMod For Motorola Droid RAZR/RAZR MAXX (CDMA) (spyder)

Introduction

These instructions will hopefully assist you to start with a stock Droid RAZR/RAZR MAXX (CDMA), unlock the bootloader (if necessary), and then download the required tools as well as the very latest source code for CyanogenMod (based on Google’s Android operating system). Using these, you can build both CyanogenMod and CyanogenMod Recovery image from source code, and then install them both to your device.

It is difficult to say how much experience is necessary to follow these instructions. While this guide is certainly not for the very very very uninitiated, these steps shouldn’t require a PhD in software development either. Some readers will have no difficulty and breeze through the steps easily. Others may struggle over the most basic operation. Because people’s experiences, backgrounds, and intuitions differ, it may be a good idea to read through just to ascertain whether you feel comfortable or are getting over your head.

Remember, you assume all risk of trying this, but you will reap the rewards! It’s pretty satisfying to boot into a fresh operating system you baked at home :) And once you’re an Android-building ninja, there will be no more need to wait for “nightly” builds from anyone. You will have at your fingertips the skills to build a full operating system from code to a running device, whenever you want. Where you go from there– maybe you’ll add a feature, fix a bug, add a translation, or use what you’ve learned to build a new app or port to a new device– or maybe you’ll never build again– it’s all really up to you.

What you’ll need

• A Droid RAZR/RAZR MAXX (CDMA)
• A relatively recent computer (Linux, OS X, or Windows) with a reasonable amount of RAM and about 100 GB of free storage (more if you enable ccache or build for multiple devices). The less RAM you have, the longer the build will take (aim for 8 GB or more). Using SSDs results in considerably faster build times than traditional hard drives.
• A USB cable compatible with the Droid RAZR/RAZR MAXX (CDMA) (typically micro USB, but older devices may use mini USB or have a proprietary cable)
• A decent internet connection & reliable electricity :)
• Some familiarity with basic Android operation and terminology. It would help if you’ve installed custom roms on other devices and are familiar with recovery. It may also be useful to know some basic command line concepts such as cd for “change directory”, the concept of directory hierarchies, that in Linux they are separated by /, etc.

If you are not accustomed to using Linux– this is an excellent chance to learn. It’s free– just download and run a virtual machine (VM) such as Virtualbox, then install a Linux distribution such as Ubuntu (AOSP vets Ubuntu as well). Any recent 64-bit version should work great, but the latest is recommended.

Using a VM allows Linux to run as a guest inside your host computer– a computer in a computer, if you will. If you hate Linux for whatever reason, you can always just uninstall and delete the whole thing. (There are plenty of places to find instructions for setting up Virtualbox with Ubuntu, so I’ll leave it to you to do that.)

So let’s begin!

Build CyanogenMod and CyanogenMod Recovery

Prepare the Build Environment

Install the SDK

If you have not previously installed adb and fastboot, install the Android SDK. “SDK” stands for Software Developer Kit, and it includes useful tools that you can use to flash software, look at the system logs in real time, grab screenshots, and more– all from your computer.

Install the Build Packages

Several “build packages” are needed to build CyanogenMod. You can install these using the package manager of your choice.

For both 32-bit & 64-bit systems, you’ll need:

bc bison build-essential curl flex git gnupg gperf libesd0-dev liblz4-tool libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop maven openjdk-7-jdk pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev

In addition to the above, for 64-bit systems, get these:

g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev

For Ubuntu 15.10 (wily) and newer, substitute:

• lib32readline-gplv2-dev → lib32readline6-dev

For Ubuntu 16.04 (xenial) and newer, substitute (additionally see java notes below):

• libwxgtk2.8-dev → libwxgtk3.0-dev
• openjdk-7-jdk → openjdk-8-jdk

Java versions: Different versions of CyanogenMod require different versions of the JDK (Java Development Kit):

• CyanogenMod 7 – 9: Sun/Oracle Java SE 1.6
• CyanogenMod 10.1: Sun/Oracle Java SE 1.6 or 1.7
• CyanogenMod 10.2 – 11.0: Sun/Oracle Java SE 1.6 or 1.7 (OpenJDK 1.7 works fine, but the build system will display a warning)
• CyanogenMod 12.0 – 13.0: OpenJDK 1.7 (see note about OpenJDK 1.8 below)
• CyanogenMod 14.1: OpenJDK 1.8

Ubuntu 16.04 (Xenial Xerus) or newer and OpenJDK: Since OpenJDK 1.7 was removed from the official Ubuntu repositories, you have a couple options:

1. Obtain OpenJDK 1.7 from the openjdk-r PPA
2. Enable experimental OpenJDK 1.8 support in CyanogenMod 13.0 (not available in earlier version). To enable OpenJDK 1.8 support, add this line to your $HOME/.bashrc file: export EXPERIMENTAL_USE_JAVA8=true.

Also see http://source.android.com/source/initializing.html which lists needed packages.

Create the directories

You will need to set up some directories in your build environment.

To create them:

$ mkdir -p ~/bin
$ mkdir -p ~/android/system

Install the repo command

Enter the following to download the “repo” binary and make it executable (runnable):

$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo

Put the ~/bin directory in your path of execution

In recent versions of Ubuntu, ~/bin should already be in your PATH. You can check this by opening ~/.profile with a text editor and verifying the following code exists (add it if it is missing):

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
fi

Initialize the CyanogenMod source repository

Enter the following to initialize the repository:

Note: Make sure the cm branch entered here is the one you wish to build and is supported on your device.

$ cd ~/android/system/
$ repo init -u https://github.com/CyanogenMod/android.git -b cm-13.0

Download the source code

To start the download of all the source code to your computer:

$ repo sync

The CM manifests include a sensible default configuration for repo, which we strongly suggest you use (i.e. don’t add any options to sync). For reference, our default values are -j 4 and -c. The -j 4 part means that there will be four simultaneous threads/connections. If you experience problems syncing, you can lower this to -j 3 or -j 2. -c will ask repo to pull in only the current branch, instead of the entire CM history.

Prepare to wait a long time while the source code downloads.

Get prebuilt apps (CM11 and below)

Next,

$ cd ~/android/system/vendor/cm

then enter:

$ ./get-prebuilts

You won’t see any confirmation- just another prompt. But this should cause some prebuilt apps to be loaded and installed into the source code. Once completed, this does not need to be done again.

Prepare the device-specific code

After the source downloads, ensure you are in the root of the source code (cd ~/android/system), then type:

$ source build/envsetup.sh
$ breakfast spyder

This will download the device specific configuration and kernel source for your device. An alternative to using the breakfast command is to build your own local manifest. To do this, you will need to locate your device on CyanogenMod’s GitHub and list all of the repositories defined in cm.dependencies in your local manifest.

Extract proprietary blobs

Now ensure that your Droid RAZR/RAZR MAXX (CDMA) is connected to your computer via the USB cable and that you are in the ~/android/system/device/motorola/spyder directory (you can cd ~/android/system/device/motorola/spyder if necessary). Then run the extract-files.sh script:

$ ./extract-files.sh

You should see the proprietary files (aka “blobs”) get pulled from the device and moved to the ~/android/system/vendor/motorola directory. If you see errors about adb being unable to pull the files, adb may not be in the path of execution. If this is the case, see the adb page for suggestions for dealing with “command not found” errors.

Turn on caching to speed up build

You can speed up subsequent builds by adding

export USE_CCACHE=1

to your ~/.bashrc file (what’s a .bashrc file?). Then, specify the amount of disk space to dedicate to ccache by typing this from the top of your Android tree:

prebuilts/misc/linux-x86/ccache/ccache -M 50G

where 50G corresponds to 50GB of cache. This only needs to be run once and the setting will be remembered. Anywhere in the range of 25GB to 100GB will result in very noticeably increased build speeds (for instance, a typical 1hr build time can be reduced to 20min). If you’re only building for one device, 25GB-50GB is fine. If you plan to build for several devices that do not share the same kernel source, aim for 75GB-100GB. This space will be permanently occupied on your drive, so take this into consideration. See more information about ccache on Google’s android build environment initialization page.

Start the build

Time to start building! So now type:

$ croot
$ brunch spyder

The build should begin.

If the build breaks…

• If you experience this not-enough-memory-related error…

ERROR: signapk.jar failed: return code 1make: *** [out/target/product/spyder/cm_spyder-ota-eng.root.zip] Error 1

…you may want to make the following change to ~/android/system/build/tools/releasetools/common.py:

Search for instances of -Xmx2048m (it should appear either under OPTIONS.java_args or near usage of signapk.jar), and replace it with -Xmx1024m or -Xmx512m.

Then start the build again (with brunch).

• If you see a message about things suddenly being “killed” for no reason, your (virtual) machine may have run out of memory or storage space. Assign it more resources and try again.

Install the build

Assuming the build completed without error (it will be obvious when it finishes), type:

$ cd $OUT

in the same terminal window that you did the build. Here you’ll find all the files that were created. The stuff that will go in /system is in a folder called system. The stuff that will become your ramdisk is in a folder called root. And your kernel is called… kernel.

But that’s all just background info. The two files we are interested in are (1) recovery.img, which contains CyanogenMod Recovery, and (2) cm-13.0-20161224-UNOFFICIAL-spyder.zip, which is the CyanogenMod installation package.

Installing SafeStrap Recovery

1. Download the SafeStrap APK for Droid RAZR/RAZR MAXX (CDMA): [{{{install_file}}} Download]
   • md5: {{{install_md5sum}}}
2. Place the downloaded APK alongside adb on your computer.
3. Enable installation from unknown sources on your Droid RAZR/RAZR MAXX (CDMA): Settings > Security and check the Unknown sources box.
4. Open a terminal on your computer and navigate to the adb executable and run the following: adb install YOURAPK.apk
5. If you see [SUCCESS] in the terminal, continue on.

   NOTE: If you see [FAILED], please go back and ensure you’ve followed the instructions above to the letter.

6. Run the SafeStrap app on the Droid RAZR/RAZR MAXX (CDMA).
7. Once requested, permanently grant the application Superuser access.
8. Click the button labeled Install Recovery.
9. Once complete, reboot the device.
10. When the SafeStrap splash screen appears, hit the Menu button on your Droid RAZR/RAZR MAXX (CDMA).
11. Click the button labeled Boot Options.
12. Activate romslot-1 and follow the instructions on the device.
13. We will be updating SafeStrap to use all ROM slots for Kexec soon.
14. Follow the instructions below for installing CyanogenMod from recovery.

Install CyanogenMod

Back to the $OUT directory on your computer– you should see a file that looks something like:

cm-13.0-20161224-UNOFFICIAL-spyder.zip

Now you can flash the cm...zip file above as usual via recovery mode. Before doing so, now is a good time to make a backup of whatever installation is currently running on the device in case something goes wrong with the flash attempt. While CyanogenMod Recovery doesn’t have a backup feature, there are other custom recoveries available that do. You can also use something like Titanium Backup (root required) as an alternative.

Success! So….what’s next?

You’ve done it! Welcome to the elite club of self-builders. You’ve built your operating system from scratch, from the ground up. You are the master/mistress of your domain… and hopefully you’ve learned a bit on the way and had some fun too.

Now that you’ve succeeded in building CyanogenMod for your device, here are some suggestions on what to do next.

Also, be sure to take a glance at the Dev Center on this wiki for all kinds of more detailed information about developer topics ranging from collecting logs, understanding what’s in the source code directories, submitting your own contributions, porting CyanogenMod to new devices, and a lot more.

Congrats again!

Content of this page is based on informations from wiki.cyanogenmod.org, under CC BY-SA 3.0 licence.

Cyanogenmod ROM Motorola Droid Bionic (targa)

Quick Info

Check out Motorola Droid Bionic (“targa”) with newer LineageOS software

Download CyanogenMod

Download (nightly build)
CyanogenMod 13.0 (Android 6.0/6.0.1 (Marshmallow))

Main sections for Motorola Droid Bionic (“targa”)

1. Information about Motorola Droid Bionic (“targa”)
2. CyanogenMod install guide for Motorola Droid Bionic (“targa”)
3. Build CyanogenMod and CyanogenMod Recovery guide

Notes

This is a KEXEC build and must be installed in SafeStrap (builds older than 9/1/2013 must be installed on rom-slot1). CM-12.0 requires at least Safestrap v3.75.

Special boot modes

• Recovery: Power and at SafeStrap splash screen press Menu key within 10 seconds
• Bootloader: Vol Up & Vol Down & Power
• Fastboot: Vol Down & Power

Source code

Device	http://www.github.com/cyanogenmod/android_device_motorola_targa
Kernel	http://www.github.com/cyanogenmod/android_kernel_motorola_omap4-common

Droid Bionic Specifications

Codename:	targa
Vendor:	Motorola
Release date:	2011 September 8
Carrier:	Verizon
Type:	phone
CDMA freq:	800/1900 CDMA2000 1xEV-DO
LTE freq:	700 MHz Class 13
Platform:	TI OMAP4430
CPU:	1 GHz dual-core Cortex-A9
GPU:	PowerVR SGX540
RAM:	1GB
Weight:	158.8 g (5.57 oz)
Dimensions:	127.5 x 66.9 x 11 mm (5.02 x 2.63 x 0.43 in)
Screen size:	109 mm (4.3 in)
Resolution:	540 x 960
Screen density:	256 ppi
Screen type:	TFT capacitive touchscreen
Internal storage:	16GB
SD Card:	microSD, up to 32 GB, 16 GB included
Bluetooth:	v2.1 with A2DP, EDR
Wi-Fi:	Wi-Fi 802.11 b/g/n
Main camera:	8MP, flash: LED
Secondary camera:	VGA
Power:	1735 mAh
Peripherals:	Accelerometer, proximity, compass, GPS
CM supported:	10.1, 10.2, 11, 12, 12.1, 13

How to Install CyanogenMod on the Motorola Droid Bionic (targa)

Important Notes

This is a KEXEC build and must be installed in SafeStrap (builds older than 9/1/2013 must be installed on rom-slot1). CM-12.0 requires at least Safestrap v3.75.

Gaining Root Access with Razr’s Edge (Windows Only)

1. Download Razr’s Edge (Credit to djrbliss)
2. Download and install the Motorola device drivers.
   • Motorola device drivers
3. Unzip Razr’s Edge to a folder on your computer.
4. Enable USB debugging on the Droid Bionic: Settings > Developer Options and check the Android debugging box.
5. Connect the Droid Bionic to the computer via USB.
6. On the computer, double click the run.bat file:
7. Allow the exploit to finish, the Droid Bionic may reboot several times.
8. The Droid Bionic is now rooted.

Installing SafeStrap Recovery

1. Download the SafeStrap APK for Droid Bionic: Download
   • md5: a764315b5ffc83847cc1ca282b36f56b
2. Place the downloaded APK alongside adb on your computer.
3. Enable installation from unknown sources on your Droid Bionic: Settings > Security and check the Unknown sources box.
4. Open a terminal on your computer and navigate to the adb executable and run the following: adb install YOURAPK.apk
5. If you see [SUCCESS] in the terminal, continue on.

   NOTE: If you see [FAILED], please go back and ensure you’ve followed the instructions above to the letter.

6. Run the SafeStrap app on the Droid Bionic.
7. Once requested, permanently grant the application Superuser access.
8. Click the button labeled Install Recovery.
9. Once complete, reboot the device.
10. When the SafeStrap splash screen appears, hit the Menu button on your Droid Bionic.
11. Click the button labeled Boot Options.
12. Activate romslot-1 and follow the instructions on the device.
13. We will be updating SafeStrap to use all ROM slots for Kexec soon.
14. Follow the instructions below for installing CyanogenMod from recovery.

Installing CyanogenMod from recovery

1. Make sure your computer has working adb.
2. Download the CyanogenMod build package for your device that you’d like to install to your computer.

   Optional: Download 3rd party applications packages, like Google Apps which are necessary to download apps from Google Play.

3. Place the CyanogenMod .zip package, as well as any optional .zip packages, on the root of /sdcard:
   • Using adb: adb push filename.zip /sdcard/

   Note: You can copy the .zip packages to your device using any method you are familiar with. The adb method is used here because it is universal across all devices and works in both Android and recovery mode. If you are in recovery mode, you may need to ensure /sdcard (sometimes called Internal Storage) is mounted by checking its status in the Mounts menu. If you have booted regularly, USB debugging must be enabled.

4. If you are not already in recovery, boot to recovery mode now.
   • Power and at SafeStrap splash screen press Menu key within 10 seconds
5. In Team Win Recovery Project, select menu choices by tapping on the appropriately labelled button.
6. Optional (Recommended): Select the Backup button to create a backup.
7. Select Wipe and then Factory Reset.
8. Select Install.
9. Navigate to /sdcard and select the CyanogenMod .zip package.
10. Follow the on-screen notices to install the package.
11. Optional: Install any additional packages you wish using the same method (if you are installing multiple packages, install CyanogenMod first and then install any subsequent packages on top of it).
12. Once installation has finished, return to the main menu and select Reboot, then System. The device will now boot into CyanogenMod.

How To Build CyanogenMod For Motorola Droid Bionic (targa)

Introduction

These instructions will hopefully assist you to start with a stock Droid Bionic, unlock the bootloader (if necessary), and then download the required tools as well as the very latest source code for CyanogenMod (based on Google’s Android operating system). Using these, you can build both CyanogenMod and CyanogenMod Recovery image from source code, and then install them both to your device.

It is difficult to say how much experience is necessary to follow these instructions. While this guide is certainly not for the very very very uninitiated, these steps shouldn’t require a PhD in software development either. Some readers will have no difficulty and breeze through the steps easily. Others may struggle over the most basic operation. Because people’s experiences, backgrounds, and intuitions differ, it may be a good idea to read through just to ascertain whether you feel comfortable or are getting over your head.

Remember, you assume all risk of trying this, but you will reap the rewards! It’s pretty satisfying to boot into a fresh operating system you baked at home :) And once you’re an Android-building ninja, there will be no more need to wait for “nightly” builds from anyone. You will have at your fingertips the skills to build a full operating system from code to a running device, whenever you want. Where you go from there– maybe you’ll add a feature, fix a bug, add a translation, or use what you’ve learned to build a new app or port to a new device– or maybe you’ll never build again– it’s all really up to you.

What you’ll need

• A Droid Bionic
• A relatively recent computer (Linux, OS X, or Windows) with a reasonable amount of RAM and about 100 GB of free storage (more if you enable ccache or build for multiple devices). The less RAM you have, the longer the build will take (aim for 8 GB or more). Using SSDs results in considerably faster build times than traditional hard drives.
• A USB cable compatible with the Droid Bionic (typically micro USB, but older devices may use mini USB or have a proprietary cable)
• A decent internet connection & reliable electricity :)
• Some familiarity with basic Android operation and terminology. It would help if you’ve installed custom roms on other devices and are familiar with recovery. It may also be useful to know some basic command line concepts such as cd for “change directory”, the concept of directory hierarchies, that in Linux they are separated by /, etc.

If you are not accustomed to using Linux– this is an excellent chance to learn. It’s free– just download and run a virtual machine (VM) such as Virtualbox, then install a Linux distribution such as Ubuntu (AOSP vets Ubuntu as well). Any recent 64-bit version should work great, but the latest is recommended.

Using a VM allows Linux to run as a guest inside your host computer– a computer in a computer, if you will. If you hate Linux for whatever reason, you can always just uninstall and delete the whole thing. (There are plenty of places to find instructions for setting up Virtualbox with Ubuntu, so I’ll leave it to you to do that.)

So let’s begin!

Build CyanogenMod and CyanogenMod Recovery

Prepare the Build Environment

Install the SDK

If you have not previously installed adb and fastboot, install the Android SDK. “SDK” stands for Software Developer Kit, and it includes useful tools that you can use to flash software, look at the system logs in real time, grab screenshots, and more– all from your computer.

Install the Build Packages

Several “build packages” are needed to build CyanogenMod. You can install these using the package manager of your choice.

For both 32-bit & 64-bit systems, you’ll need:

bc bison build-essential curl flex git gnupg gperf libesd0-dev liblz4-tool libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop maven openjdk-7-jdk pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev

In addition to the above, for 64-bit systems, get these:

g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev

For Ubuntu 15.10 (wily) and newer, substitute:

• lib32readline-gplv2-dev → lib32readline6-dev

For Ubuntu 16.04 (xenial) and newer, substitute (additionally see java notes below):

• libwxgtk2.8-dev → libwxgtk3.0-dev
• openjdk-7-jdk → openjdk-8-jdk

Java versions: Different versions of CyanogenMod require different versions of the JDK (Java Development Kit):

• CyanogenMod 7 – 9: Sun/Oracle Java SE 1.6
• CyanogenMod 10.1: Sun/Oracle Java SE 1.6 or 1.7
• CyanogenMod 10.2 – 11.0: Sun/Oracle Java SE 1.6 or 1.7 (OpenJDK 1.7 works fine, but the build system will display a warning)
• CyanogenMod 12.0 – 13.0: OpenJDK 1.7 (see note about OpenJDK 1.8 below)
• CyanogenMod 14.1: OpenJDK 1.8

Ubuntu 16.04 (Xenial Xerus) or newer and OpenJDK: Since OpenJDK 1.7 was removed from the official Ubuntu repositories, you have a couple options:

1. Obtain OpenJDK 1.7 from the openjdk-r PPA
2. Enable experimental OpenJDK 1.8 support in CyanogenMod 13.0 (not available in earlier version). To enable OpenJDK 1.8 support, add this line to your $HOME/.bashrc file: export EXPERIMENTAL_USE_JAVA8=true.

Also see http://source.android.com/source/initializing.html which lists needed packages.

Create the directories

You will need to set up some directories in your build environment.

To create them:

$ mkdir -p ~/bin
$ mkdir -p ~/android/system

Install the repo command

Enter the following to download the “repo” binary and make it executable (runnable):

$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo

Put the ~/bin directory in your path of execution

In recent versions of Ubuntu, ~/bin should already be in your PATH. You can check this by opening ~/.profile with a text editor and verifying the following code exists (add it if it is missing):

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
fi

Initialize the CyanogenMod source repository

Enter the following to initialize the repository:

Note: Make sure the cm branch entered here is the one you wish to build and is supported on your device.

$ cd ~/android/system/
$ repo init -u https://github.com/CyanogenMod/android.git -b cm-13.0

Download the source code

To start the download of all the source code to your computer:

$ repo sync

The CM manifests include a sensible default configuration for repo, which we strongly suggest you use (i.e. don’t add any options to sync). For reference, our default values are -j 4 and -c. The -j 4 part means that there will be four simultaneous threads/connections. If you experience problems syncing, you can lower this to -j 3 or -j 2. -c will ask repo to pull in only the current branch, instead of the entire CM history.

Prepare to wait a long time while the source code downloads.

Get prebuilt apps (CM11 and below)

Next,

$ cd ~/android/system/vendor/cm

then enter:

$ ./get-prebuilts

You won’t see any confirmation- just another prompt. But this should cause some prebuilt apps to be loaded and installed into the source code. Once completed, this does not need to be done again.

Prepare the device-specific code

After the source downloads, ensure you are in the root of the source code (cd ~/android/system), then type:

$ source build/envsetup.sh
$ breakfast targa

This will download the device specific configuration and kernel source for your device. An alternative to using the breakfast command is to build your own local manifest. To do this, you will need to locate your device on CyanogenMod’s GitHub and list all of the repositories defined in cm.dependencies in your local manifest.

Extract proprietary blobs

Now ensure that your Droid Bionic is connected to your computer via the USB cable and that you are in the ~/android/system/device/motorola/targa directory (you can cd ~/android/system/device/motorola/targa if necessary). Then run the extract-files.sh script:

$ ./extract-files.sh

You should see the proprietary files (aka “blobs”) get pulled from the device and moved to the ~/android/system/vendor/motorola directory. If you see errors about adb being unable to pull the files, adb may not be in the path of execution. If this is the case, see the adb page for suggestions for dealing with “command not found” errors.

Turn on caching to speed up build

You can speed up subsequent builds by adding

export USE_CCACHE=1

to your ~/.bashrc file (what’s a .bashrc file?). Then, specify the amount of disk space to dedicate to ccache by typing this from the top of your Android tree:

prebuilts/misc/linux-x86/ccache/ccache -M 50G

where 50G corresponds to 50GB of cache. This only needs to be run once and the setting will be remembered. Anywhere in the range of 25GB to 100GB will result in very noticeably increased build speeds (for instance, a typical 1hr build time can be reduced to 20min). If you’re only building for one device, 25GB-50GB is fine. If you plan to build for several devices that do not share the same kernel source, aim for 75GB-100GB. This space will be permanently occupied on your drive, so take this into consideration. See more information about ccache on Google’s android build environment initialization page.

Start the build

Time to start building! So now type:

$ croot
$ brunch targa

The build should begin.

If the build breaks…

• If you experience this not-enough-memory-related error…

ERROR: signapk.jar failed: return code 1make: *** [out/target/product/targa/cm_targa-ota-eng.root.zip] Error 1

…you may want to make the following change to ~/android/system/build/tools/releasetools/common.py:

Search for instances of -Xmx2048m (it should appear either under OPTIONS.java_args or near usage of signapk.jar), and replace it with -Xmx1024m or -Xmx512m.

Then start the build again (with brunch).

• If you see a message about things suddenly being “killed” for no reason, your (virtual) machine may have run out of memory or storage space. Assign it more resources and try again.

Install the build

Assuming the build completed without error (it will be obvious when it finishes), type:

$ cd $OUT

in the same terminal window that you did the build. Here you’ll find all the files that were created. The stuff that will go in /system is in a folder called system. The stuff that will become your ramdisk is in a folder called root. And your kernel is called… kernel.

But that’s all just background info. The two files we are interested in are (1) recovery.img, which contains CyanogenMod Recovery, and (2) cm-13.0-20161224-UNOFFICIAL-targa.zip, which is the CyanogenMod installation package.

Installing SafeStrap Recovery

1. Download the SafeStrap APK for Droid Bionic: [{{{install_file}}} Download]
   • md5: {{{install_md5sum}}}
2. Place the downloaded APK alongside adb on your computer.
3. Enable installation from unknown sources on your Droid Bionic: Settings > Security and check the Unknown sources box.
4. Open a terminal on your computer and navigate to the adb executable and run the following: adb install YOURAPK.apk
5. If you see [SUCCESS] in the terminal, continue on.

   NOTE: If you see [FAILED], please go back and ensure you’ve followed the instructions above to the letter.

6. Run the SafeStrap app on the Droid Bionic.
7. Once requested, permanently grant the application Superuser access.
8. Click the button labeled Install Recovery.
9. Once complete, reboot the device.
10. When the SafeStrap splash screen appears, hit the Menu button on your Droid Bionic.
11. Click the button labeled Boot Options.
12. Activate romslot-1 and follow the instructions on the device.
13. We will be updating SafeStrap to use all ROM slots for Kexec soon.
14. Follow the instructions below for installing CyanogenMod from recovery.

Install CyanogenMod

Back to the $OUT directory on your computer– you should see a file that looks something like:

cm-13.0-20161224-UNOFFICIAL-targa.zip

Now you can flash the cm...zip file above as usual via recovery mode. Before doing so, now is a good time to make a backup of whatever installation is currently running on the device in case something goes wrong with the flash attempt. While CyanogenMod Recovery doesn’t have a backup feature, there are other custom recoveries available that do. You can also use something like Titanium Backup (root required) as an alternative.

Success! So….what’s next?

You’ve done it! Welcome to the elite club of self-builders. You’ve built your operating system from scratch, from the ground up. You are the master/mistress of your domain… and hopefully you’ve learned a bit on the way and had some fun too.

Now that you’ve succeeded in building CyanogenMod for your device, here are some suggestions on what to do next.

Also, be sure to take a glance at the Dev Center on this wiki for all kinds of more detailed information about developer topics ranging from collecting logs, understanding what’s in the source code directories, submitting your own contributions, porting CyanogenMod to new devices, and a lot more.

Congrats again!

Content of this page is based on informations from wiki.cyanogenmod.org, under CC BY-SA 3.0 licence.

Cyanogenmod ROM Motorola Droid Mini / Ultra / MAXX (obake)

Quick Info

Download CyanogenMod

Download (nightly build)
CyanogenMod 12.1 (Android 5.1 (Lollipop))

Main sections for Motorola Droid Mini / Ultra / MAXX (“obake”)

1. Information about Motorola Droid Mini / Ultra / MAXX (“obake”)
2. CyanogenMod install guide for Motorola Droid Mini / Ultra / MAXX (“obake”)
3. Build CyanogenMod and CyanogenMod Recovery guide

Notes

This is a unified build for Motorola Droid Mini / Ultra / MAXX

Special boot modes

• Recovery: Hold Volume Down & Power simultaneously.
• Bootloader: Hold Volume Up Volume Down & Power simultaneously. On the next screen use Volume Down to scroll to bootloader and then use Volume Up to select.
• Fastboot: Hold Volume Up Volume Down & Power simultaneously. On the next screen use Volume Down to scroll to bootloader and then use Volume Up to select.

Source code

Device	http://www.github.com/cyanogenmod/android_device_motorola_obake
Kernel	http://www.github.com/cyanogenmod/android_kernel_motorola_ghost

Droid Mini / Ultra / MAXX Specifications

Codename:	obake
Also known as:	XT1030, XT1080, XT1080m
Vendor:	Motorola
Release date:	2013 Aug 23
Carrier:	Verizon
Type:	phone
GSM freq:	850, 900, 1800, 1900 MHz GSM, 850, 900, 1700/2100, 1900, 2100 MHz UMTS
LTE freq:	700 (band 13), 850 (band 5), 1700/2100 (band 4), 1900 (band 2) MHz, LTE, HSDPA+ (4G) 42.2 Mbit/s, HSUPA 5.76 Mbit/s, UMTS, EDGE, GPRS
Platform:	Motorola X8 (Qualcomm Snapdragon S4 Pro MSM8960AB)
CPU:	1.7 GHz dual-core Krait
GPU:	Adreno 320
RAM:	2GB
Weight:	Droid Mini: 130 g (4.59 oz) Droid Ultra: 137 g (4.83 oz) Droid MAXX: 167 g (5.89 oz)
Dimensions:	Droid Mini: 121.3 x 61.3 x 8.9 mm (4.78 x 2.41 x 0.35 in) Droid Ultra: 137.5 x 71.2 x 7.2 mm (5.41 x 2.80 x 0.28 in) Droid MAXX: 137.5 mm (5.41 in) x 71.2 mm (2.80 in) x 8.5 mm (0.33 in)
Screen size:	Droid Mini: 109 mm (4.3 in), Droid Ultra: 127 mm (5.0 in), Droid MAXX: 127 mm (5.0 in)
Resolution:	720 x 1280 pixels
Screen density:	Droid Mini: 342 ppi Droid Ultra: 294 ppi Droid MAXX: 294 ppi
Screen type:	AMOLED
Internal storage:	16 / 32 GB
SD Card:	none
Bluetooth:	4.0, EDR
Wi-Fi:	802.11 a, b, g, n, n 5GHz, ac
Main camera:	10MP, flash: LED
Secondary camera:	2MP
Power:	Droid Mini: 2000 mAh Droid Ultra: 2130 mAh Droid MAXX: 3500 mAh
Peripherals:	Accelerometer, Compass
CM supported:	12, 12.1

How to Install CyanogenMod on the Motorola Droid Mini / Ultra / MAXX (obake)

Important Notes

This is a unified build for Motorola Droid Mini / Ultra / MAXX

Unlocking the bootloader

1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging on the device.
3. Enable OEM unlock in the Developer options settings on the device. (Note: Not all devices have this setting, so continue with next step if yours does not.)
4. Connect the device to the computer through USB.
5. From a terminal on a computer, type the following to boot the device into fastboot mode:

   adb reboot bootloader

6. Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
   • If you don’t see your device serial number, and instead see “<waiting for device>”, fastboot is not configured properly on your machine. See fastboot documentation for more info.
   • If you see “no permissions fastboot”, try running fastboot as root.
7. From the same terminal, type the following command to obtain your bootloader unlock code:

   fastboot oem get_unlock_data

8. Visit the Motorola Bootloader Unlock website and follow the instructions there to obtain your unlock key and unlock your bootloader.
9. If the device doesn’t automatically reboot, reboot it from the menu. It should now be unlocked.
10. Since the device resets completely, you will need to re-enable USB debugging on the device to continue.

Installing a custom recovery using fastboot

See All About Recovery Images for more information about custom recoveries and their capabilities.

1. Make sure your computer has working fastboot and adb.
2. Download recovery — you can directly download a recovery image using the link below, or visit twrp.me to obtain the latest version of Team Win Recovery Project for your device.

   Recovery: Download

   md5: aadfe53423e4301364a03a2458b2536d

3. Connect the Droid Mini / Ultra / MAXX to the computer via USB.
4. Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
5. Open a terminal on your PC and reboot the device into fastboot mode by typing

   adb reboot bootloader

   or by using the hardware key combination for your device while it is powered off.

6. Once the device is in fastboot mode, verify your PC sees the device by typing

   fastboot devices

   • If you don’t see your device serial number, and instead see “<waiting for device>”, fastboot is not configured properly on your machine. See fastboot documentation for more info.
   • If you see “no permissionsfastboot”, make sure your UDEV rules are setup correctly.
7. Flash recovery onto your device by entering the following command:

   fastboot flash recovery your_recovery_image.img

   where the latter part is the filename of the recovery image.

8. Once the flash completes successfully, reboot the device into recovery to verify the installation. Boot to recovery instructions: Hold Volume Down & Power simultaneously.
   • Note: Some ROMs overwrite recovery at boot time so if you do not plan to immediately boot into recovery to install CyanogenMod, please be aware that this may overwrite your custom recovery with the stock one.

Installing CyanogenMod from recovery

1. Make sure your computer has working adb.
2. Download the CyanogenMod build package for your device that you’d like to install to your computer.

   Optional: Download 3rd party applications packages, like Google Apps which are necessary to download apps from Google Play.

3. Place the CyanogenMod .zip package, as well as any optional .zip packages, on the root of /sdcard:
   • Using adb: adb push filename.zip /sdcard/

   Note: You can copy the .zip packages to your device using any method you are familiar with. The adb method is used here because it is universal across all devices and works in both Android and recovery mode. If you are in recovery mode, you may need to ensure /sdcard (sometimes called Internal Storage) is mounted by checking its status in the Mounts menu. If you have booted regularly, USB debugging must be enabled.

4. If you are not already in recovery, boot to recovery mode now.
   • Hold Volume Down & Power simultaneously.
5. In Team Win Recovery Project, select menu choices by tapping on the appropriately labelled button.
6. Optional (Recommended): Select the Backup button to create a backup.
7. Select Wipe and then Factory Reset.
8. Select Install.
9. Navigate to /sdcard and select the CyanogenMod .zip package.
10. Follow the on-screen notices to install the package.
11. Optional: Install any additional packages you wish using the same method (if you are installing multiple packages, install CyanogenMod first and then install any subsequent packages on top of it).
12. Once installation has finished, return to the main menu and select Reboot, then System. The device will now boot into CyanogenMod.

How To Build CyanogenMod For Motorola Droid Mini / Ultra / MAXX (obake)

Introduction

These instructions will hopefully assist you to start with a stock Droid Mini / Ultra / MAXX, unlock the bootloader (if necessary), and then download the required tools as well as the very latest source code for CyanogenMod (based on Google’s Android operating system). Using these, you can build both CyanogenMod and CyanogenMod Recovery image from source code, and then install them both to your device.

It is difficult to say how much experience is necessary to follow these instructions. While this guide is certainly not for the very very very uninitiated, these steps shouldn’t require a PhD in software development either. Some readers will have no difficulty and breeze through the steps easily. Others may struggle over the most basic operation. Because people’s experiences, backgrounds, and intuitions differ, it may be a good idea to read through just to ascertain whether you feel comfortable or are getting over your head.

Remember, you assume all risk of trying this, but you will reap the rewards! It’s pretty satisfying to boot into a fresh operating system you baked at home :) And once you’re an Android-building ninja, there will be no more need to wait for “nightly” builds from anyone. You will have at your fingertips the skills to build a full operating system from code to a running device, whenever you want. Where you go from there– maybe you’ll add a feature, fix a bug, add a translation, or use what you’ve learned to build a new app or port to a new device– or maybe you’ll never build again– it’s all really up to you.

What you’ll need

• A Droid Mini / Ultra / MAXX
• A relatively recent computer (Linux, OS X, or Windows) with a reasonable amount of RAM and about 100 GB of free storage (more if you enable ccache or build for multiple devices). The less RAM you have, the longer the build will take (aim for 8 GB or more). Using SSDs results in considerably faster build times than traditional hard drives.
• A USB cable compatible with the Droid Mini / Ultra / MAXX (typically micro USB, but older devices may use mini USB or have a proprietary cable)
• A decent internet connection & reliable electricity :)
• Some familiarity with basic Android operation and terminology. It would help if you’ve installed custom roms on other devices and are familiar with recovery. It may also be useful to know some basic command line concepts such as cd for “change directory”, the concept of directory hierarchies, that in Linux they are separated by /, etc.

If you are not accustomed to using Linux– this is an excellent chance to learn. It’s free– just download and run a virtual machine (VM) such as Virtualbox, then install a Linux distribution such as Ubuntu (AOSP vets Ubuntu as well). Any recent 64-bit version should work great, but the latest is recommended.

Using a VM allows Linux to run as a guest inside your host computer– a computer in a computer, if you will. If you hate Linux for whatever reason, you can always just uninstall and delete the whole thing. (There are plenty of places to find instructions for setting up Virtualbox with Ubuntu, so I’ll leave it to you to do that.)

So let’s begin!

Unlocking your Droid Mini / Ultra / MAXX

What does “unlocking” mean?

The first step in putting any custom operating system on your Droid Mini / Ultra / MAXX is to unlock the bootloader. A bootloader is the very first program that runs when you turn on your device. The bootloader initializes some hardware and then loads the kernel and ramdisk, and gets the boot process going. If the bootloader is in locked mode, it will ensure that only the stock operating system can run. Since you will be installing your own operating system, you need to turn this off. Luckily, Google and motorola make it easy.

Okay. I’m in. What do I need to do this?

To unlock your bootloader, you’ll first need a program on your computer called fastboot. One way to get fastboot is to download and install the Android SDK (Software Developer Kit) from Google. The SDK is used by app developers when they’re writing programs for Android, and who knows, you may want to write apps someday. But the SDK also contains two great tools that are useful even to non-developers. They are:

• adb – Android Debug Bridge – this is a program that lets your computer “talk” to your Droid Mini / Ultra / MAXX while the device is running. Among the many things you can do with adb– you can push files from your computer to the device or pull files from the device to your computer, you can get a running real-time log of Android activity (which is very useful for debugging or having others help you debug), you can create an interactive “shell” session (similar to Linux or OS X) to type commands to your device, and much more.

• fastboot – fastboot works a little bit like adb, except it’s often used at a much earlier point in the boot process, even before Android or any operating system loads. You can put your Droid Mini / Ultra / MAXX into a “fastboot” mode, whereby, if you are connected via USB cable, you can copy entire partitions from your computer (usually in the form of an image file, such as boot.img or recovery.img) over to the device, wiping over whatever happened to be there. Fastboot is able to do more than that, however. It’s also used to send special commands to the device to do things such as unlock your bootloader.

How do I do the actual unlocking?

So this should be a one time thing…

Install the Android SDK

To unlock your Droid Mini / Ultra / MAXX, you will need fastboot installed. Go ahead and download the SDK, per the steps on Google’s web page. Then install it by following the specific instructions for your computer.

Unlocking the bootloader

1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging on the device.
3. Enable OEM unlock in the Developer options settings on the device. (Note: Not all devices have this setting, so continue with next step if yours does not.)
4. Connect the device to the computer through USB.
5. From a terminal on a computer, type the following to boot the device into fastboot mode:

   adb reboot bootloader

6. Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
   • If you don’t see your device serial number, and instead see “<waiting for device>”, fastboot is not configured properly on your machine. See fastboot documentation for more info.
   • If you see “no permissions fastboot”, try running fastboot as root.
7. From the same terminal, type the following command to unlock the bootloader:

   fastboot oem get_unlock_data

8. If the device doesn’t automatically reboot, reboot it from the menu. It should now be unlocked.
9. Since the device resets completely, you will need to re-enable USB debugging on the device to continue.

Troubleshooting

If you have issues with fastboot or adb not being found, make sure that the Android SDK folder /platform-tools, which contains the adb and fastboot files, are in the path of execution for commands typed at the terminal. Usually typing something like

# PATH=$PATH:/your/specific/path/to/android/sdk/platform-tools/

will work for that terminal session.

$ sudo apt-get install ia32-libs

You’ll be using fastboot again to install a custom recovery.

Build CyanogenMod and CyanogenMod Recovery

Prepare the Build Environment

Install the SDK

If you have not previously installed adb and fastboot, install the Android SDK. “SDK” stands for Software Developer Kit, and it includes useful tools that you can use to flash software, look at the system logs in real time, grab screenshots, and more– all from your computer.

Install the Build Packages

Several “build packages” are needed to build CyanogenMod. You can install these using the package manager of your choice.

For both 32-bit & 64-bit systems, you’ll need:

bc bison build-essential curl flex git gnupg gperf libesd0-dev liblz4-tool libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop maven openjdk-7-jdk pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev

In addition to the above, for 64-bit systems, get these:

g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev

For Ubuntu 15.10 (wily) and newer, substitute:

• lib32readline-gplv2-dev → lib32readline6-dev

For Ubuntu 16.04 (xenial) and newer, substitute (additionally see java notes below):

• libwxgtk2.8-dev → libwxgtk3.0-dev
• openjdk-7-jdk → openjdk-8-jdk

Java versions: Different versions of CyanogenMod require different versions of the JDK (Java Development Kit):

• CyanogenMod 7 – 9: Sun/Oracle Java SE 1.6
• CyanogenMod 10.1: Sun/Oracle Java SE 1.6 or 1.7
• CyanogenMod 10.2 – 11.0: Sun/Oracle Java SE 1.6 or 1.7 (OpenJDK 1.7 works fine, but the build system will display a warning)
• CyanogenMod 12.0 – 13.0: OpenJDK 1.7 (see note about OpenJDK 1.8 below)
• CyanogenMod 14.1: OpenJDK 1.8

Ubuntu 16.04 (Xenial Xerus) or newer and OpenJDK: Since OpenJDK 1.7 was removed from the official Ubuntu repositories, you have a couple options:

1. Obtain OpenJDK 1.7 from the openjdk-r PPA
2. Enable experimental OpenJDK 1.8 support in CyanogenMod 13.0 (not available in earlier version). To enable OpenJDK 1.8 support, add this line to your $HOME/.bashrc file: export EXPERIMENTAL_USE_JAVA8=true.

Also see http://source.android.com/source/initializing.html which lists needed packages.

Create the directories

You will need to set up some directories in your build environment.

To create them:

$ mkdir -p ~/bin
$ mkdir -p ~/android/system

Install the repo command

Enter the following to download the “repo” binary and make it executable (runnable):

$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo

Put the ~/bin directory in your path of execution

In recent versions of Ubuntu, ~/bin should already be in your PATH. You can check this by opening ~/.profile with a text editor and verifying the following code exists (add it if it is missing):

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
fi

Initialize the CyanogenMod source repository

Enter the following to initialize the repository:

Note: Make sure the cm branch entered here is the one you wish to build and is supported on your device.

$ cd ~/android/system/
$ repo init -u https://github.com/CyanogenMod/android.git -b cm-13.0

Download the source code

To start the download of all the source code to your computer:

$ repo sync

The CM manifests include a sensible default configuration for repo, which we strongly suggest you use (i.e. don’t add any options to sync). For reference, our default values are -j 4 and -c. The -j 4 part means that there will be four simultaneous threads/connections. If you experience problems syncing, you can lower this to -j 3 or -j 2. -c will ask repo to pull in only the current branch, instead of the entire CM history.

Prepare to wait a long time while the source code downloads.

Get prebuilt apps (CM11 and below)

Next,

$ cd ~/android/system/vendor/cm

then enter:

$ ./get-prebuilts

You won’t see any confirmation- just another prompt. But this should cause some prebuilt apps to be loaded and installed into the source code. Once completed, this does not need to be done again.

Prepare the device-specific code

After the source downloads, ensure you are in the root of the source code (cd ~/android/system), then type:

$ source build/envsetup.sh
$ breakfast obake

This will download the device specific configuration and kernel source for your device. An alternative to using the breakfast command is to build your own local manifest. To do this, you will need to locate your device on CyanogenMod’s GitHub and list all of the repositories defined in cm.dependencies in your local manifest.

Extract proprietary blobs

Now ensure that your Droid Mini / Ultra / MAXX is connected to your computer via the USB cable and that you are in the ~/android/system/device/motorola/obake directory (you can cd ~/android/system/device/motorola/obake if necessary). Then run the extract-files.sh script:

$ ./extract-files.sh

You should see the proprietary files (aka “blobs”) get pulled from the device and moved to the ~/android/system/vendor/motorola directory. If you see errors about adb being unable to pull the files, adb may not be in the path of execution. If this is the case, see the adb page for suggestions for dealing with “command not found” errors.

Turn on caching to speed up build

You can speed up subsequent builds by adding

export USE_CCACHE=1

to your ~/.bashrc file (what’s a .bashrc file?). Then, specify the amount of disk space to dedicate to ccache by typing this from the top of your Android tree:

prebuilts/misc/linux-x86/ccache/ccache -M 50G

where 50G corresponds to 50GB of cache. This only needs to be run once and the setting will be remembered. Anywhere in the range of 25GB to 100GB will result in very noticeably increased build speeds (for instance, a typical 1hr build time can be reduced to 20min). If you’re only building for one device, 25GB-50GB is fine. If you plan to build for several devices that do not share the same kernel source, aim for 75GB-100GB. This space will be permanently occupied on your drive, so take this into consideration. See more information about ccache on Google’s android build environment initialization page.

Start the build

Time to start building! So now type:

$ croot
$ brunch obake

The build should begin.

If the build breaks…

• If you experience this not-enough-memory-related error…

ERROR: signapk.jar failed: return code 1make: *** [out/target/product/obake/cm_obake-ota-eng.root.zip] Error 1

…you may want to make the following change to ~/android/system/build/tools/releasetools/common.py:

Search for instances of -Xmx2048m (it should appear either under OPTIONS.java_args or near usage of signapk.jar), and replace it with -Xmx1024m or -Xmx512m.

Then start the build again (with brunch).

• If you see a message about things suddenly being “killed” for no reason, your (virtual) machine may have run out of memory or storage space. Assign it more resources and try again.

Install the build

Assuming the build completed without error (it will be obvious when it finishes), type:

$ cd $OUT

in the same terminal window that you did the build. Here you’ll find all the files that were created. The stuff that will go in /system is in a folder called system. The stuff that will become your ramdisk is in a folder called root. And your kernel is called… kernel.

But that’s all just background info. The two files we are interested in are (1) recovery.img, which contains CyanogenMod Recovery, and (2) cm-13.0-20161224-UNOFFICIAL-obake.zip, which is the CyanogenMod installation package.

Installing a custom recovery using fastboot

See All About Recovery Images for more information about custom recoveries and their capabilities.

1. Make sure your computer has working fastboot and adb.

1. Connect the Droid Mini / Ultra / MAXX to the computer via USB.
2. Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
3. Open a terminal on your PC and reboot the device into fastboot mode by typing

   adb reboot bootloader

   or by using the hardware key combination for your device while it is powered off.

4. Once the device is in fastboot mode, verify your PC sees the device by typing

   fastboot devices

   • If you don’t see your device serial number, and instead see “<waiting for device>”, fastboot is not configured properly on your machine. See fastboot documentation for more info.
   • If you see “no permissionsfastboot”, make sure your UDEV rules are setup correctly.
5. Flash recovery onto your device by entering the following command:

   fastboot flash recovery your_recovery_image.img

   where the latter part is the filename of the recovery image.

6. Once the flash completes successfully, reboot the device into recovery to verify the installation.
   • Note: Some ROMs overwrite recovery at boot time so if you do not plan to immediately boot into recovery to install CyanogenMod, please be aware that this may overwrite your custom recovery with the stock one.

Install CyanogenMod

Back to the $OUT directory on your computer– you should see a file that looks something like:

cm-13.0-20161224-UNOFFICIAL-obake.zip

Now you can flash the cm...zip file above as usual via recovery mode. Before doing so, now is a good time to make a backup of whatever installation is currently running on the device in case something goes wrong with the flash attempt. While CyanogenMod Recovery doesn’t have a backup feature, there are other custom recoveries available that do. You can also use something like Titanium Backup (root required) as an alternative.

Success! So….what’s next?

You’ve done it! Welcome to the elite club of self-builders. You’ve built your operating system from scratch, from the ground up. You are the master/mistress of your domain… and hopefully you’ve learned a bit on the way and had some fun too.

Now that you’ve succeeded in building CyanogenMod for your device, here are some suggestions on what to do next.

Also, be sure to take a glance at the Dev Center on this wiki for all kinds of more detailed information about developer topics ranging from collecting logs, understanding what’s in the source code directories, submitting your own contributions, porting CyanogenMod to new devices, and a lot more.

Congrats again!

Content of this page is based on informations from wiki.cyanogenmod.org, under CC BY-SA 3.0 licence.

Cyanogenmod ROM Motorola Moto E (condor)

Quick Info

Check out Motorola Moto E (“condor”) with newer LineageOS software

Download CyanogenMod

Download (nightly build)
CyanogenMod 14.1 (Android 7.1 (Nougat))

Main sections for Motorola Moto E (“condor”)

1. Information about Motorola Moto E (“condor”)
2. CyanogenMod install guide for Motorola Moto E (“condor”)
3. Build CyanogenMod and CyanogenMod Recovery guide

Special boot modes

• Recovery: Hold Volume Down & Power simultaneously. On the next screen use Volume Down to scroll to recovery and then use Volume Up to select.
• Bootloader: Hold Volume Down & Power simultaneously. On the next screen use Volume Down to scroll and Volume Up to select.
• Fastboot: Hold Volume Down & Power simultaneously.

Source code

Device	http://www.github.com/cyanogenmod/android_device_motorola_condor
Kernel	http://www.github.com/cyanogenmod/android_kernel_motorola_msm8610

Moto E Specifications

Codename:	condor
Also known as:	XT1021, XT1022, XT1023
Vendor:	Motorola
Release date:	2014 May 13
Type:	phone
GSM freq:	GSM 850/900/1800/1900 MHz, HSDPA 850/900/1900/2100 MHz
Platform:	Qualcomm Snapdragon 200
CPU:	1.2 GHz dual-core Cortex A7
GPU:	Adreno 302
RAM:	1GB
Weight:	142 g (5.04 oz)
Dimensions:	124.8 mm (4.91 in) x 64.8 mm (2.55 in) x 12.3 mm (0.48 in)
Screen size:	109 mm (4.3 in)
Resolution:	540 x 960 pixels
Screen density:	~256 ppi
Screen type:	IPS LCD
Internal storage:	4GB
SD Card:	up to 32GB
Bluetooth:	v4.0
Wi-Fi:	Wi-Fi 802.11 b/g/n
Main camera:	5MP, flash: none
Secondary camera:	none
Power:	1980 mAh
Peripherals:	Accelerometer, proximity, compass
CM supported:	12, 12.1, 13, 14.1

How to Install CyanogenMod on the Motorola Moto E (condor)

Unlocking the bootloader

1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging on the device.
3. Enable OEM unlock in the Developer options settings on the device. (Note: Not all devices have this setting, so continue with next step if yours does not.)
4. Connect the device to the computer through USB.
5. From a terminal on a computer, type the following to boot the device into fastboot mode:

   adb reboot bootloader

6. Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
   • If you don’t see your device serial number, and instead see “<waiting for device>”, fastboot is not configured properly on your machine. See fastboot documentation for more info.
   • If you see “no permissions fastboot”, try running fastboot as root.
7. From the same terminal, type the following command to obtain your bootloader unlock code:

   fastboot oem get_unlock_data

8. Visit the Motorola Bootloader Unlock website and follow the instructions there to obtain your unlock key and unlock your bootloader.
9. If the device doesn’t automatically reboot, reboot it from the menu. It should now be unlocked.
10. Since the device resets completely, you will need to re-enable USB debugging on the device to continue.

Installing a custom recovery using fastboot

See All About Recovery Images for more information about custom recoveries and their capabilities.

1. Make sure your computer has working fastboot and adb.
2. Download recovery — you can directly download a recovery image using the link below, or visit twrp.me to obtain the latest version of Team Win Recovery Project for your device.

   Recovery: Download

   md5: 11084b7b3d3db34d1e44c9e95db04705

3. Connect the Moto E to the computer via USB.
4. Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
5. Open a terminal on your PC and reboot the device into fastboot mode by typing

   adb reboot bootloader

   or by using the hardware key combination for your device while it is powered off.

6. Once the device is in fastboot mode, verify your PC sees the device by typing

   fastboot devices

   • If you don’t see your device serial number, and instead see “<waiting for device>”, fastboot is not configured properly on your machine. See fastboot documentation for more info.
   • If you see “no permissionsfastboot”, make sure your UDEV rules are setup correctly.
7. Flash recovery onto your device by entering the following command:

   fastboot flash recovery your_recovery_image.img

   where the latter part is the filename of the recovery image.

8. Once the flash completes successfully, reboot the device into recovery to verify the installation. Boot to recovery instructions: Hold Volume Down & Power simultaneously. On the next screen use Volume Down to scroll to recovery and then use Volume Up to select.
   • Note: Some ROMs overwrite recovery at boot time so if you do not plan to immediately boot into recovery to install CyanogenMod, please be aware that this may overwrite your custom recovery with the stock one.

Installing CyanogenMod from recovery

1. Make sure your computer has working adb.
2. Download the CyanogenMod build package for your device that you’d like to install to your computer.

   Optional: Download 3rd party applications packages, like Google Apps which are necessary to download apps from Google Play.

3. Place the CyanogenMod .zip package, as well as any optional .zip packages, on the root of /sdcard:
   • Using adb: adb push filename.zip /sdcard/

   Note: You can copy the .zip packages to your device using any method you are familiar with. The adb method is used here because it is universal across all devices and works in both Android and recovery mode. If you are in recovery mode, you may need to ensure /sdcard (sometimes called Internal Storage) is mounted by checking its status in the Mounts menu. If you have booted regularly, USB debugging must be enabled.

4. If you are not already in recovery, boot to recovery mode now.
   • Hold Volume Down & Power simultaneously. On the next screen use Volume Down to scroll to recovery and then use Volume Up to select.
5. In Team Win Recovery Project, select menu choices by tapping on the appropriately labelled button.
6. Optional (Recommended): Select the Backup button to create a backup.
7. Select Wipe and then Factory Reset.
8. Select Install.
9. Navigate to /sdcard and select the CyanogenMod .zip package.
10. Follow the on-screen notices to install the package.
11. Optional: Install any additional packages you wish using the same method (if you are installing multiple packages, install CyanogenMod first and then install any subsequent packages on top of it).
12. Once installation has finished, return to the main menu and select Reboot, then System. The device will now boot into CyanogenMod.

How To Build CyanogenMod For Motorola Moto E (condor)

Introduction

These instructions will hopefully assist you to start with a stock Moto E, unlock the bootloader (if necessary), and then download the required tools as well as the very latest source code for CyanogenMod (based on Google’s Android operating system). Using these, you can build both CyanogenMod and CyanogenMod Recovery image from source code, and then install them both to your device.

It is difficult to say how much experience is necessary to follow these instructions. While this guide is certainly not for the very very very uninitiated, these steps shouldn’t require a PhD in software development either. Some readers will have no difficulty and breeze through the steps easily. Others may struggle over the most basic operation. Because people’s experiences, backgrounds, and intuitions differ, it may be a good idea to read through just to ascertain whether you feel comfortable or are getting over your head.

Remember, you assume all risk of trying this, but you will reap the rewards! It’s pretty satisfying to boot into a fresh operating system you baked at home :) And once you’re an Android-building ninja, there will be no more need to wait for “nightly” builds from anyone. You will have at your fingertips the skills to build a full operating system from code to a running device, whenever you want. Where you go from there– maybe you’ll add a feature, fix a bug, add a translation, or use what you’ve learned to build a new app or port to a new device– or maybe you’ll never build again– it’s all really up to you.

What you’ll need

• A Moto E
• A relatively recent computer (Linux, OS X, or Windows) with a reasonable amount of RAM and about 100 GB of free storage (more if you enable ccache or build for multiple devices). The less RAM you have, the longer the build will take (aim for 8 GB or more). Using SSDs results in considerably faster build times than traditional hard drives.
• A USB cable compatible with the Moto E (typically micro USB, but older devices may use mini USB or have a proprietary cable)
• A decent internet connection & reliable electricity :)
• Some familiarity with basic Android operation and terminology. It would help if you’ve installed custom roms on other devices and are familiar with recovery. It may also be useful to know some basic command line concepts such as cd for “change directory”, the concept of directory hierarchies, that in Linux they are separated by /, etc.

If you are not accustomed to using Linux– this is an excellent chance to learn. It’s free– just download and run a virtual machine (VM) such as Virtualbox, then install a Linux distribution such as Ubuntu (AOSP vets Ubuntu as well). Any recent 64-bit version should work great, but the latest is recommended.

Using a VM allows Linux to run as a guest inside your host computer– a computer in a computer, if you will. If you hate Linux for whatever reason, you can always just uninstall and delete the whole thing. (There are plenty of places to find instructions for setting up Virtualbox with Ubuntu, so I’ll leave it to you to do that.)

So let’s begin!

Unlocking your Moto E

What does “unlocking” mean?

The first step in putting any custom operating system on your Moto E is to unlock the bootloader. A bootloader is the very first program that runs when you turn on your device. The bootloader initializes some hardware and then loads the kernel and ramdisk, and gets the boot process going. If the bootloader is in locked mode, it will ensure that only the stock operating system can run. Since you will be installing your own operating system, you need to turn this off. Luckily, Google and motorola make it easy.

Okay. I’m in. What do I need to do this?

To unlock your bootloader, you’ll first need a program on your computer called fastboot. One way to get fastboot is to download and install the Android SDK (Software Developer Kit) from Google. The SDK is used by app developers when they’re writing programs for Android, and who knows, you may want to write apps someday. But the SDK also contains two great tools that are useful even to non-developers. They are:

• adb – Android Debug Bridge – this is a program that lets your computer “talk” to your Moto E while the device is running. Among the many things you can do with adb– you can push files from your computer to the device or pull files from the device to your computer, you can get a running real-time log of Android activity (which is very useful for debugging or having others help you debug), you can create an interactive “shell” session (similar to Linux or OS X) to type commands to your device, and much more.

• fastboot – fastboot works a little bit like adb, except it’s often used at a much earlier point in the boot process, even before Android or any operating system loads. You can put your Moto E into a “fastboot” mode, whereby, if you are connected via USB cable, you can copy entire partitions from your computer (usually in the form of an image file, such as boot.img or recovery.img) over to the device, wiping over whatever happened to be there. Fastboot is able to do more than that, however. It’s also used to send special commands to the device to do things such as unlock your bootloader.

How do I do the actual unlocking?

So this should be a one time thing…

Install the Android SDK

To unlock your Moto E, you will need fastboot installed. Go ahead and download the SDK, per the steps on Google’s web page. Then install it by following the specific instructions for your computer.

Unlocking the bootloader

1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging on the device.
3. Enable OEM unlock in the Developer options settings on the device. (Note: Not all devices have this setting, so continue with next step if yours does not.)
4. Connect the device to the computer through USB.
5. From a terminal on a computer, type the following to boot the device into fastboot mode:

   adb reboot bootloader

6. Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
   • If you don’t see your device serial number, and instead see “<waiting for device>”, fastboot is not configured properly on your machine. See fastboot documentation for more info.
   • If you see “no permissions fastboot”, try running fastboot as root.
7. From the same terminal, type the following command to unlock the bootloader:

   fastboot oem get_unlock_data

8. If the device doesn’t automatically reboot, reboot it from the menu. It should now be unlocked.
9. Since the device resets completely, you will need to re-enable USB debugging on the device to continue.

Troubleshooting

If you have issues with fastboot or adb not being found, make sure that the Android SDK folder /platform-tools, which contains the adb and fastboot files, are in the path of execution for commands typed at the terminal. Usually typing something like

# PATH=$PATH:/your/specific/path/to/android/sdk/platform-tools/

will work for that terminal session.

$ sudo apt-get install ia32-libs

You’ll be using fastboot again to install a custom recovery.

Build CyanogenMod and CyanogenMod Recovery

Prepare the Build Environment

Install the SDK

If you have not previously installed adb and fastboot, install the Android SDK. “SDK” stands for Software Developer Kit, and it includes useful tools that you can use to flash software, look at the system logs in real time, grab screenshots, and more– all from your computer.

Install the Build Packages

Several “build packages” are needed to build CyanogenMod. You can install these using the package manager of your choice.

For both 32-bit & 64-bit systems, you’ll need:

bc bison build-essential curl flex git gnupg gperf libesd0-dev liblz4-tool libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop maven openjdk-7-jdk pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev

In addition to the above, for 64-bit systems, get these:

g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev

For Ubuntu 15.10 (wily) and newer, substitute:

• lib32readline-gplv2-dev → lib32readline6-dev

For Ubuntu 16.04 (xenial) and newer, substitute (additionally see java notes below):

• libwxgtk2.8-dev → libwxgtk3.0-dev
• openjdk-7-jdk → openjdk-8-jdk

Java versions: Different versions of CyanogenMod require different versions of the JDK (Java Development Kit):

• CyanogenMod 7 – 9: Sun/Oracle Java SE 1.6
• CyanogenMod 10.1: Sun/Oracle Java SE 1.6 or 1.7
• CyanogenMod 10.2 – 11.0: Sun/Oracle Java SE 1.6 or 1.7 (OpenJDK 1.7 works fine, but the build system will display a warning)
• CyanogenMod 12.0 – 13.0: OpenJDK 1.7 (see note about OpenJDK 1.8 below)
• CyanogenMod 14.1: OpenJDK 1.8

Ubuntu 16.04 (Xenial Xerus) or newer and OpenJDK: Since OpenJDK 1.7 was removed from the official Ubuntu repositories, you have a couple options:

1. Obtain OpenJDK 1.7 from the openjdk-r PPA
2. Enable experimental OpenJDK 1.8 support in CyanogenMod 13.0 (not available in earlier version). To enable OpenJDK 1.8 support, add this line to your $HOME/.bashrc file: export EXPERIMENTAL_USE_JAVA8=true.

Also see http://source.android.com/source/initializing.html which lists needed packages.

Create the directories

You will need to set up some directories in your build environment.

To create them:

$ mkdir -p ~/bin
$ mkdir -p ~/android/system

Install the repo command

Enter the following to download the “repo” binary and make it executable (runnable):

$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo

Put the ~/bin directory in your path of execution

In recent versions of Ubuntu, ~/bin should already be in your PATH. You can check this by opening ~/.profile with a text editor and verifying the following code exists (add it if it is missing):

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
fi

Initialize the CyanogenMod source repository

Enter the following to initialize the repository:

Note: Make sure the cm branch entered here is the one you wish to build and is supported on your device.

$ cd ~/android/system/
$ repo init -u https://github.com/CyanogenMod/android.git -b cm-13.0

Download the source code

To start the download of all the source code to your computer:

$ repo sync

The CM manifests include a sensible default configuration for repo, which we strongly suggest you use (i.e. don’t add any options to sync). For reference, our default values are -j 4 and -c. The -j 4 part means that there will be four simultaneous threads/connections. If you experience problems syncing, you can lower this to -j 3 or -j 2. -c will ask repo to pull in only the current branch, instead of the entire CM history.

Prepare to wait a long time while the source code downloads.

Get prebuilt apps (CM11 and below)

Next,

$ cd ~/android/system/vendor/cm

then enter:

$ ./get-prebuilts

You won’t see any confirmation- just another prompt. But this should cause some prebuilt apps to be loaded and installed into the source code. Once completed, this does not need to be done again.

Prepare the device-specific code

After the source downloads, ensure you are in the root of the source code (cd ~/android/system), then type:

$ source build/envsetup.sh
$ breakfast condor

This will download the device specific configuration and kernel source for your device. An alternative to using the breakfast command is to build your own local manifest. To do this, you will need to locate your device on CyanogenMod’s GitHub and list all of the repositories defined in cm.dependencies in your local manifest.

Extract proprietary blobs

Now ensure that your Moto E is connected to your computer via the USB cable and that you are in the ~/android/system/device/motorola/condor directory (you can cd ~/android/system/device/motorola/condor if necessary). Then run the extract-files.sh script:

$ ./extract-files.sh

You should see the proprietary files (aka “blobs”) get pulled from the device and moved to the ~/android/system/vendor/motorola directory. If you see errors about adb being unable to pull the files, adb may not be in the path of execution. If this is the case, see the adb page for suggestions for dealing with “command not found” errors.

Turn on caching to speed up build

You can speed up subsequent builds by adding

export USE_CCACHE=1

to your ~/.bashrc file (what’s a .bashrc file?). Then, specify the amount of disk space to dedicate to ccache by typing this from the top of your Android tree:

prebuilts/misc/linux-x86/ccache/ccache -M 50G

where 50G corresponds to 50GB of cache. This only needs to be run once and the setting will be remembered. Anywhere in the range of 25GB to 100GB will result in very noticeably increased build speeds (for instance, a typical 1hr build time can be reduced to 20min). If you’re only building for one device, 25GB-50GB is fine. If you plan to build for several devices that do not share the same kernel source, aim for 75GB-100GB. This space will be permanently occupied on your drive, so take this into consideration. See more information about ccache on Google’s android build environment initialization page.

Start the build

Time to start building! So now type:

$ croot
$ brunch condor

The build should begin.

If the build breaks…

• If you experience this not-enough-memory-related error…

ERROR: signapk.jar failed: return code 1make: *** [out/target/product/condor/cm_condor-ota-eng.root.zip] Error 1

…you may want to make the following change to ~/android/system/build/tools/releasetools/common.py:

Search for instances of -Xmx2048m (it should appear either under OPTIONS.java_args or near usage of signapk.jar), and replace it with -Xmx1024m or -Xmx512m.

Then start the build again (with brunch).

• If you see a message about things suddenly being “killed” for no reason, your (virtual) machine may have run out of memory or storage space. Assign it more resources and try again.

Install the build

Assuming the build completed without error (it will be obvious when it finishes), type:

$ cd $OUT

in the same terminal window that you did the build. Here you’ll find all the files that were created. The stuff that will go in /system is in a folder called system. The stuff that will become your ramdisk is in a folder called root. And your kernel is called… kernel.

But that’s all just background info. The two files we are interested in are (1) recovery.img, which contains CyanogenMod Recovery, and (2) cm-13.0-20161224-UNOFFICIAL-condor.zip, which is the CyanogenMod installation package.

Installing a custom recovery using fastboot

See All About Recovery Images for more information about custom recoveries and their capabilities.

1. Make sure your computer has working fastboot and adb.

1. Connect the Moto E to the computer via USB.
2. Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
3. Open a terminal on your PC and reboot the device into fastboot mode by typing

   adb reboot bootloader

   or by using the hardware key combination for your device while it is powered off.

4. Once the device is in fastboot mode, verify your PC sees the device by typing

   fastboot devices

   • If you don’t see your device serial number, and instead see “<waiting for device>”, fastboot is not configured properly on your machine. See fastboot documentation for more info.
   • If you see “no permissionsfastboot”, make sure your UDEV rules are setup correctly.
5. Flash recovery onto your device by entering the following command:

   fastboot flash recovery your_recovery_image.img

   where the latter part is the filename of the recovery image.

6. Once the flash completes successfully, reboot the device into recovery to verify the installation.
   • Note: Some ROMs overwrite recovery at boot time so if you do not plan to immediately boot into recovery to install CyanogenMod, please be aware that this may overwrite your custom recovery with the stock one.

Install CyanogenMod

Back to the $OUT directory on your computer– you should see a file that looks something like:

cm-13.0-20161224-UNOFFICIAL-condor.zip

Now you can flash the cm...zip file above as usual via recovery mode. Before doing so, now is a good time to make a backup of whatever installation is currently running on the device in case something goes wrong with the flash attempt. While CyanogenMod Recovery doesn’t have a backup feature, there are other custom recoveries available that do. You can also use something like Titanium Backup (root required) as an alternative.

Success! So….what’s next?

You’ve done it! Welcome to the elite club of self-builders. You’ve built your operating system from scratch, from the ground up. You are the master/mistress of your domain… and hopefully you’ve learned a bit on the way and had some fun too.

Now that you’ve succeeded in building CyanogenMod for your device, here are some suggestions on what to do next.

Also, be sure to take a glance at the Dev Center on this wiki for all kinds of more detailed information about developer topics ranging from collecting logs, understanding what’s in the source code directories, submitting your own contributions, porting CyanogenMod to new devices, and a lot more.

Congrats again!

Content of this page is based on informations from wiki.cyanogenmod.org, under CC BY-SA 3.0 licence.

Cyanogenmod ROM Motorola Droid 4 (maserati)

Quick Info

Check out Motorola Droid 4 (“maserati”) with newer LineageOS software

Download CyanogenMod

Download (nightly build)
CyanogenMod 13.0 (Android 6.0/6.0.1 (Marshmallow))

Main sections for Motorola Droid 4 (“maserati”)

1. Information about Motorola Droid 4 (“maserati”)
2. CyanogenMod install guide for Motorola Droid 4 (“maserati”)
3. Build CyanogenMod and CyanogenMod Recovery guide

Notes

This is a KEXEC build and must be installed in SafeStrap (builds older than 9/1/2013 must be installed on rom-slot1). CM-12.0 requires at least Safestrap v3.75.

Special boot modes

• Recovery: Power and at SafeStrap splash screen press Menu key within 10 seconds
• Bootloader: Vol Up & Vol Down & Power
• Fastboot: Vol Down & Power

Source code

Device	http://www.github.com/cyanogenmod/android_device_motorola_maserati
Kernel	http://www.github.com/cyanogenmod/android_kernel_motorola_omap4-common

Droid 4 Specifications

Codename:	maserati
Vendor:	Motorola
Release date:	2012 February 10
Carrier:	Verizon
Type:	phone (slider)
GSM freq:	850/900/1800/1900 HSDPA 850/900/1900/2100
CDMA freq:	800/1900 CDMA2000 1xEV-DO
LTE freq:	700 MHz Class 13
Platform:	TI OMAP4430
CPU:	1.2 GHz dual-core Cortex-A9
GPU:	PowerVR SGX540
RAM:	1GB
Weight:	178.9 g (6.28 oz)
Dimensions:	127 x 67.3 x 12.7 mm (5.0 x 2.65 x 0.5 in)
Screen size:	102 mm (4.0 in)
Resolution:	540 x 960
Screen density:	275 ppi
Screen type:	TFT capacitive touchscreen
Internal storage:	16GB
SD Card:	microSD, up to 32 GB
Bluetooth:	v4.0 with LE+EDR
Wi-Fi:	Wi-Fi 802.11 b/g/n
Main camera:	8MP, flash: LED
Secondary camera:	1.3MP
Power:	1785 mAh
Peripherals:	Accelerometer, proximity, compass, GPS, HDMI, FM Radio (Not officialy supported)
CM supported:	10.1, 10.2, 11, 12, 12.1, 13

How to Install CyanogenMod on the Motorola Droid 4 (maserati)

Important Notes

This is a KEXEC build and must be installed in SafeStrap (builds older than 9/1/2013 must be installed on rom-slot1). CM-12.0 requires at least Safestrap v3.75.

Gaining Root Access with RazrBlade (Windows Only)

1. Download the following file: (Credit to djrbliss)
   • Razr Blade Windows: Download
2. Download and install the Motorola device drivers.
   • Motorola device drivers
3. Unzip Razr Blade to a folder on your computer.
4. Enable USB debugging on the Droid 4: Settings > Developer Options and check the USB debugging box.
5. Clear Smart Actions Data: Settings > Apps > Smart Actions and click the Clear data button.
6. Ensure that your data is not encrypted: Settings > Security & Screen Lock > Data Encryption and uncheck both boxes, then press Apply
7. Confirm Droid 4 is using MTP for USB connection: Settings > Storage > ≡(Menu) Button > USB computer connection > Select Media device (MTP)
8. Connect the Droid 4 to the computer via USB.
9. On the computer, double click the run.bat file
10. Allow the exploit to finish, the Droid 4 may reboot several times.
11. When the exploit says “Cleaning up” you may need to look at your phone, unlock the screen if necessary, and press the “Grant” button to grant SuperUser permissions for the exploit to finish.
12. The Droid 4 is now rooted.

Installing SafeStrap Recovery

1. Download the SafeStrap APK for Droid 4: Download
   • md5: af6112a1d1a42ddc79dbad3624fe11c3
2. Place the downloaded APK alongside adb on your computer.
3. Enable installation from unknown sources on your Droid 4: Settings > Security and check the Unknown sources box.
4. Open a terminal on your computer and navigate to the adb executable and run the following: adb install YOURAPK.apk
5. If you see [SUCCESS] in the terminal, continue on.

   NOTE: If you see [FAILED], please go back and ensure you’ve followed the instructions above to the letter.

6. Run the SafeStrap app on the Droid 4.
7. Once requested, permanently grant the application Superuser access.
8. Click the button labeled Install Recovery.
9. Once complete, reboot the device.
10. When the SafeStrap splash screen appears, hit the Menu button on your Droid 4.
11. Click the button labeled Boot Options.
12. Activate romslot-1 and follow the instructions on the device.
13. We will be updating SafeStrap to use all ROM slots for Kexec soon.
14. Follow the instructions below for installing CyanogenMod from recovery.

Installing CyanogenMod from recovery

1. Make sure your computer has working adb.
2. Download the CyanogenMod build package for your device that you’d like to install to your computer.

   Optional: Download 3rd party applications packages, like Google Apps which are necessary to download apps from Google Play.

3. Place the CyanogenMod .zip package, as well as any optional .zip packages, on the root of /sdcard:
   • Using adb: adb push filename.zip /sdcard/

   Note: You can copy the .zip packages to your device using any method you are familiar with. The adb method is used here because it is universal across all devices and works in both Android and recovery mode. If you are in recovery mode, you may need to ensure /sdcard (sometimes called Internal Storage) is mounted by checking its status in the Mounts menu. If you have booted regularly, USB debugging must be enabled.

4. If you are not already in recovery, boot to recovery mode now.
   • Power and at SafeStrap splash screen press Menu key within 10 seconds
5. In Team Win Recovery Project, select menu choices by tapping on the appropriately labelled button.
6. Optional (Recommended): Select the Backup button to create a backup.
7. Select Wipe and then Factory Reset.
8. Select Install.
9. Navigate to /sdcard and select the CyanogenMod .zip package.
10. Follow the on-screen notices to install the package.
11. Optional: Install any additional packages you wish using the same method (if you are installing multiple packages, install CyanogenMod first and then install any subsequent packages on top of it).
12. Once installation has finished, return to the main menu and select Reboot, then System. The device will now boot into CyanogenMod.

How To Build CyanogenMod For Motorola Droid 4 (maserati)

Introduction

These instructions will hopefully assist you to start with a stock Droid 4, unlock the bootloader (if necessary), and then download the required tools as well as the very latest source code for CyanogenMod (based on Google’s Android operating system). Using these, you can build both CyanogenMod and CyanogenMod Recovery image from source code, and then install them both to your device.

It is difficult to say how much experience is necessary to follow these instructions. While this guide is certainly not for the very very very uninitiated, these steps shouldn’t require a PhD in software development either. Some readers will have no difficulty and breeze through the steps easily. Others may struggle over the most basic operation. Because people’s experiences, backgrounds, and intuitions differ, it may be a good idea to read through just to ascertain whether you feel comfortable or are getting over your head.

Remember, you assume all risk of trying this, but you will reap the rewards! It’s pretty satisfying to boot into a fresh operating system you baked at home :) And once you’re an Android-building ninja, there will be no more need to wait for “nightly” builds from anyone. You will have at your fingertips the skills to build a full operating system from code to a running device, whenever you want. Where you go from there– maybe you’ll add a feature, fix a bug, add a translation, or use what you’ve learned to build a new app or port to a new device– or maybe you’ll never build again– it’s all really up to you.

What you’ll need

• A Droid 4
• A relatively recent computer (Linux, OS X, or Windows) with a reasonable amount of RAM and about 100 GB of free storage (more if you enable ccache or build for multiple devices). The less RAM you have, the longer the build will take (aim for 8 GB or more). Using SSDs results in considerably faster build times than traditional hard drives.
• A USB cable compatible with the Droid 4 (typically micro USB, but older devices may use mini USB or have a proprietary cable)
• A decent internet connection & reliable electricity :)
• Some familiarity with basic Android operation and terminology. It would help if you’ve installed custom roms on other devices and are familiar with recovery. It may also be useful to know some basic command line concepts such as cd for “change directory”, the concept of directory hierarchies, that in Linux they are separated by /, etc.

If you are not accustomed to using Linux– this is an excellent chance to learn. It’s free– just download and run a virtual machine (VM) such as Virtualbox, then install a Linux distribution such as Ubuntu (AOSP vets Ubuntu as well). Any recent 64-bit version should work great, but the latest is recommended.

Using a VM allows Linux to run as a guest inside your host computer– a computer in a computer, if you will. If you hate Linux for whatever reason, you can always just uninstall and delete the whole thing. (There are plenty of places to find instructions for setting up Virtualbox with Ubuntu, so I’ll leave it to you to do that.)

So let’s begin!

Build CyanogenMod and CyanogenMod Recovery

Prepare the Build Environment

Install the SDK

If you have not previously installed adb and fastboot, install the Android SDK. “SDK” stands for Software Developer Kit, and it includes useful tools that you can use to flash software, look at the system logs in real time, grab screenshots, and more– all from your computer.

Install the Build Packages

Several “build packages” are needed to build CyanogenMod. You can install these using the package manager of your choice.

For both 32-bit & 64-bit systems, you’ll need:

bc bison build-essential curl flex git gnupg gperf libesd0-dev liblz4-tool libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop maven openjdk-7-jdk pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev

In addition to the above, for 64-bit systems, get these:

g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev

For Ubuntu 15.10 (wily) and newer, substitute:

• lib32readline-gplv2-dev → lib32readline6-dev

For Ubuntu 16.04 (xenial) and newer, substitute (additionally see java notes below):

• libwxgtk2.8-dev → libwxgtk3.0-dev
• openjdk-7-jdk → openjdk-8-jdk

Java versions: Different versions of CyanogenMod require different versions of the JDK (Java Development Kit):

• CyanogenMod 7 – 9: Sun/Oracle Java SE 1.6
• CyanogenMod 10.1: Sun/Oracle Java SE 1.6 or 1.7
• CyanogenMod 10.2 – 11.0: Sun/Oracle Java SE 1.6 or 1.7 (OpenJDK 1.7 works fine, but the build system will display a warning)
• CyanogenMod 12.0 – 13.0: OpenJDK 1.7 (see note about OpenJDK 1.8 below)
• CyanogenMod 14.1: OpenJDK 1.8

Ubuntu 16.04 (Xenial Xerus) or newer and OpenJDK: Since OpenJDK 1.7 was removed from the official Ubuntu repositories, you have a couple options:

1. Obtain OpenJDK 1.7 from the openjdk-r PPA
2. Enable experimental OpenJDK 1.8 support in CyanogenMod 13.0 (not available in earlier version). To enable OpenJDK 1.8 support, add this line to your $HOME/.bashrc file: export EXPERIMENTAL_USE_JAVA8=true.

Also see http://source.android.com/source/initializing.html which lists needed packages.

Create the directories

You will need to set up some directories in your build environment.

To create them:

$ mkdir -p ~/bin
$ mkdir -p ~/android/system

Install the repo command

Enter the following to download the “repo” binary and make it executable (runnable):

$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo

Put the ~/bin directory in your path of execution

In recent versions of Ubuntu, ~/bin should already be in your PATH. You can check this by opening ~/.profile with a text editor and verifying the following code exists (add it if it is missing):

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
fi

Initialize the CyanogenMod source repository

Enter the following to initialize the repository:

Note: Make sure the cm branch entered here is the one you wish to build and is supported on your device.

$ cd ~/android/system/
$ repo init -u https://github.com/CyanogenMod/android.git -b cm-13.0

Download the source code

To start the download of all the source code to your computer:

$ repo sync

The CM manifests include a sensible default configuration for repo, which we strongly suggest you use (i.e. don’t add any options to sync). For reference, our default values are -j 4 and -c. The -j 4 part means that there will be four simultaneous threads/connections. If you experience problems syncing, you can lower this to -j 3 or -j 2. -c will ask repo to pull in only the current branch, instead of the entire CM history.

Prepare to wait a long time while the source code downloads.

Get prebuilt apps (CM11 and below)

Next,

$ cd ~/android/system/vendor/cm

then enter:

$ ./get-prebuilts

You won’t see any confirmation- just another prompt. But this should cause some prebuilt apps to be loaded and installed into the source code. Once completed, this does not need to be done again.

Prepare the device-specific code

After the source downloads, ensure you are in the root of the source code (cd ~/android/system), then type:

$ source build/envsetup.sh
$ breakfast maserati

This will download the device specific configuration and kernel source for your device. An alternative to using the breakfast command is to build your own local manifest. To do this, you will need to locate your device on CyanogenMod’s GitHub and list all of the repositories defined in cm.dependencies in your local manifest.

Extract proprietary blobs

Now ensure that your Droid 4 is connected to your computer via the USB cable and that you are in the ~/android/system/device/motorola/maserati directory (you can cd ~/android/system/device/motorola/maserati if necessary). Then run the extract-files.sh script:

$ ./extract-files.sh

You should see the proprietary files (aka “blobs”) get pulled from the device and moved to the ~/android/system/vendor/motorola directory. If you see errors about adb being unable to pull the files, adb may not be in the path of execution. If this is the case, see the adb page for suggestions for dealing with “command not found” errors.

Turn on caching to speed up build

You can speed up subsequent builds by adding

export USE_CCACHE=1

to your ~/.bashrc file (what’s a .bashrc file?). Then, specify the amount of disk space to dedicate to ccache by typing this from the top of your Android tree:

prebuilts/misc/linux-x86/ccache/ccache -M 50G

where 50G corresponds to 50GB of cache. This only needs to be run once and the setting will be remembered. Anywhere in the range of 25GB to 100GB will result in very noticeably increased build speeds (for instance, a typical 1hr build time can be reduced to 20min). If you’re only building for one device, 25GB-50GB is fine. If you plan to build for several devices that do not share the same kernel source, aim for 75GB-100GB. This space will be permanently occupied on your drive, so take this into consideration. See more information about ccache on Google’s android build environment initialization page.

Start the build

Time to start building! So now type:

$ croot
$ brunch maserati

The build should begin.

If the build breaks…

• If you experience this not-enough-memory-related error…

ERROR: signapk.jar failed: return code 1make: *** [out/target/product/maserati/cm_maserati-ota-eng.root.zip] Error 1

…you may want to make the following change to ~/android/system/build/tools/releasetools/common.py:

Search for instances of -Xmx2048m (it should appear either under OPTIONS.java_args or near usage of signapk.jar), and replace it with -Xmx1024m or -Xmx512m.

Then start the build again (with brunch).

• If you see a message about things suddenly being “killed” for no reason, your (virtual) machine may have run out of memory or storage space. Assign it more resources and try again.

Install the build

Assuming the build completed without error (it will be obvious when it finishes), type:

$ cd $OUT

in the same terminal window that you did the build. Here you’ll find all the files that were created. The stuff that will go in /system is in a folder called system. The stuff that will become your ramdisk is in a folder called root. And your kernel is called… kernel.

But that’s all just background info. The two files we are interested in are (1) recovery.img, which contains CyanogenMod Recovery, and (2) cm-13.0-20161224-UNOFFICIAL-maserati.zip, which is the CyanogenMod installation package.

Installing SafeStrap Recovery

1. Download the SafeStrap APK for Droid 4: [{{{install_file}}} Download]
   • md5: {{{install_md5sum}}}
2. Place the downloaded APK alongside adb on your computer.
3. Enable installation from unknown sources on your Droid 4: Settings > Security and check the Unknown sources box.
4. Open a terminal on your computer and navigate to the adb executable and run the following: adb install YOURAPK.apk
5. If you see [SUCCESS] in the terminal, continue on.

   NOTE: If you see [FAILED], please go back and ensure you’ve followed the instructions above to the letter.

6. Run the SafeStrap app on the Droid 4.
7. Once requested, permanently grant the application Superuser access.
8. Click the button labeled Install Recovery.
9. Once complete, reboot the device.
10. When the SafeStrap splash screen appears, hit the Menu button on your Droid 4.
11. Click the button labeled Boot Options.
12. Activate romslot-1 and follow the instructions on the device.
13. We will be updating SafeStrap to use all ROM slots for Kexec soon.
14. Follow the instructions below for installing CyanogenMod from recovery.

Install CyanogenMod

Back to the $OUT directory on your computer– you should see a file that looks something like:

cm-13.0-20161224-UNOFFICIAL-maserati.zip

Now you can flash the cm...zip file above as usual via recovery mode. Before doing so, now is a good time to make a backup of whatever installation is currently running on the device in case something goes wrong with the flash attempt. While CyanogenMod Recovery doesn’t have a backup feature, there are other custom recoveries available that do. You can also use something like Titanium Backup (root required) as an alternative.

Success! So….what’s next?

You’ve done it! Welcome to the elite club of self-builders. You’ve built your operating system from scratch, from the ground up. You are the master/mistress of your domain… and hopefully you’ve learned a bit on the way and had some fun too.

Now that you’ve succeeded in building CyanogenMod for your device, here are some suggestions on what to do next.

Also, be sure to take a glance at the Dev Center on this wiki for all kinds of more detailed information about developer topics ranging from collecting logs, understanding what’s in the source code directories, submitting your own contributions, porting CyanogenMod to new devices, and a lot more.

Congrats again!

Content of this page is based on informations from wiki.cyanogenmod.org, under CC BY-SA 3.0 licence.

Cyanogenmod ROM Motorola Droid RAZR M (scorpion_mini) (xt907)

Quick Info

Download CyanogenMod

Download (nightly build)
CyanogenMod 12.1 (Android 5.1 (Lollipop))

Main sections for Motorola Droid RAZR M (“xt907”)

1. Information about Motorola Droid RAZR M (“xt907”)
2. CyanogenMod install guide for Motorola Droid RAZR M (“xt907”)
3. Build CyanogenMod and CyanogenMod Recovery guide

Notes

Note:

Your device must be bootloader unlocked.
For CM 11.0, the device builds have been unified. Get the latest CM 11.0 build for KitKat bootloader updated devices here and for devices still on JellyBean bootloader here.
For CM 12.0 and newer, KitKat bootloader is required and builds were de-unified again. Get them under the usual xt907 builds.

Special boot modes

• Recovery: Hold Volume Down & Power simultaneously.
• Bootloader: Hold Volume Up Volume Down & Power simultaneously. On the next screen use Volume Down to scroll to bootloader and then use Volume Up to select.
• Fastboot: Hold Volume Up Volume Down & Power simultaneously. On the next screen use Volume Down to scroll to bootloader and then use Volume Up to select.

Source code

Device	http://www.github.com/cyanogenmod/android_device_motorola_xt907
Kernel	http://www.github.com/cyanogenmod/android_kernel_motorola_msm8960-common

Droid RAZR M Specifications

Codename:	xt907
Also known as:	scorpion_mini
Vendor:	Motorola
Release date:	2012 September
Carrier:	Verizon
Type:	phone
GSM freq:	GSM 850/900/1800/1900 HSDPA 850/900/1900/2100
CDMA freq:	CDMA 800/1900 CDMA2000 1xEV-DO
LTE freq:	LTE 700 MHz Class 13
Platform:	Qualcomm MSM8960
CPU:	1.5 GHz dual-core Krait
GPU:	Adreno 225
RAM:	1GB
Weight:	126 g (4.44 oz)
Dimensions:	122.5 mm (4.82 in) (h) 60.9 mm (2.40 in) (w) 8.3 mm (0.33 in) (d)
Screen size:	109 mm (4.3 in)
Resolution:	540 x 960
Screen density:	~256 ppi
Screen type:	Super AMOLED
Internal storage:	8 GB (4 GB user available)
SD Card:	microSD, up to 32 GB
Bluetooth:	v4.0 with LE+EDR
Wi-Fi:	802.11 a/b/g/n, dual-band, Wi-Fi hotspot, DLNA
Main camera:	8MP, flash: LED
Secondary camera:	VGA
Power:	Non-removable Li-Ion 2000 mAh battery
Peripherals:	Accelerometer, proximity, compass
CM supported:	10.1, 10.2, 11, 12, 12.1

How to Install CyanogenMod on the Motorola Droid RAZR M (xt907)

Important Notes

Unlocking the bootloader on the Droid RAZR M

1. This unlock requires your device to be rooted. Do not proceed without a working su.
2. Download motopocalypse (credit to djrbliss).
3. Extract all files in the zip.
   • Windows only: install the latest Motorola USB drivers.
4. Enable USB debugging on the device and connect device to PC.
   • Windows: run the run.bat file.
   • Linux/OSX: ./run.sh
5. Your bootloader should now be unlocked, proceed to next section.

Installing a custom recovery using fastboot

See All About Recovery Images for more information about custom recoveries and their capabilities.

1. Make sure your computer has working fastboot and adb.
2. Download recovery — you can directly download a recovery image using the link below, or visit twrp.me to obtain the latest version of Team Win Recovery Project for your device.

   Recovery: Download

   md5: ec2177f9d1c3a3d4671e99522d9b6315

3. Connect the Droid RAZR M to the computer via USB.
4. Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
5. Open a terminal on your PC and reboot the device into fastboot mode by typing

   adb reboot bootloader

   or by using the hardware key combination for your device while it is powered off.

6. Once the device is in fastboot mode, verify your PC sees the device by typing

   fastboot devices

   • If you don’t see your device serial number, and instead see “<waiting for device>”, fastboot is not configured properly on your machine. See fastboot documentation for more info.
   • If you see “no permissionsfastboot”, make sure your UDEV rules are setup correctly.
7. Flash recovery onto your device by entering the following command:

   fastboot flash recovery your_recovery_image.img

   where the latter part is the filename of the recovery image.

8. Once the flash completes successfully, reboot the device into recovery to verify the installation. Boot to recovery instructions: Hold Volume Down & Power simultaneously.
   • Note: Some ROMs overwrite recovery at boot time so if you do not plan to immediately boot into recovery to install CyanogenMod, please be aware that this may overwrite your custom recovery with the stock one.

Installing CyanogenMod from recovery

1. Make sure your computer has working adb.
2. Download the CyanogenMod build package for your device that you’d like to install to your computer.

   Optional: Download 3rd party applications packages, like Google Apps which are necessary to download apps from Google Play.

3. Place the CyanogenMod .zip package, as well as any optional .zip packages, on the root of /sdcard:
   • Using adb: adb push filename.zip /sdcard/

   Note: You can copy the .zip packages to your device using any method you are familiar with. The adb method is used here because it is universal across all devices and works in both Android and recovery mode. If you are in recovery mode, you may need to ensure /sdcard (sometimes called Internal Storage) is mounted by checking its status in the Mounts menu. If you have booted regularly, USB debugging must be enabled.

4. If you are not already in recovery, boot to recovery mode now.
   • Hold Volume Down & Power simultaneously.
5. In Team Win Recovery Project, select menu choices by tapping on the appropriately labelled button.
6. Optional (Recommended): Select the Backup button to create a backup.
7. Select Wipe and then Factory Reset.
8. Select Install.
9. Navigate to /sdcard and select the CyanogenMod .zip package.
10. Follow the on-screen notices to install the package.
11. Optional: Install any additional packages you wish using the same method (if you are installing multiple packages, install CyanogenMod first and then install any subsequent packages on top of it).
12. Once installation has finished, return to the main menu and select Reboot, then System. The device will now boot into CyanogenMod.

Devices with System Version “182.46.15.XT907.Verizon.en.US” or “183.46.15.XT907.Verizon.en.US” (Check under Settings -> About Phone) as installed by an Over-The-Air update can not have their boot loader unlocked unless it was unlocked prior to the update. As of mid 2015, there are no known ways of unlocking the boot loader with those system versions, regardless of if you have root access or not.

How To Build CyanogenMod For Motorola Droid RAZR M (xt907)

Introduction

These instructions will hopefully assist you to start with a stock Droid RAZR M, unlock the bootloader (if necessary), and then download the required tools as well as the very latest source code for CyanogenMod (based on Google’s Android operating system). Using these, you can build both CyanogenMod and CyanogenMod Recovery image from source code, and then install them both to your device.

It is difficult to say how much experience is necessary to follow these instructions. While this guide is certainly not for the very very very uninitiated, these steps shouldn’t require a PhD in software development either. Some readers will have no difficulty and breeze through the steps easily. Others may struggle over the most basic operation. Because people’s experiences, backgrounds, and intuitions differ, it may be a good idea to read through just to ascertain whether you feel comfortable or are getting over your head.

Remember, you assume all risk of trying this, but you will reap the rewards! It’s pretty satisfying to boot into a fresh operating system you baked at home :) And once you’re an Android-building ninja, there will be no more need to wait for “nightly” builds from anyone. You will have at your fingertips the skills to build a full operating system from code to a running device, whenever you want. Where you go from there– maybe you’ll add a feature, fix a bug, add a translation, or use what you’ve learned to build a new app or port to a new device– or maybe you’ll never build again– it’s all really up to you.

What you’ll need

• A Droid RAZR M
• A relatively recent computer (Linux, OS X, or Windows) with a reasonable amount of RAM and about 100 GB of free storage (more if you enable ccache or build for multiple devices). The less RAM you have, the longer the build will take (aim for 8 GB or more). Using SSDs results in considerably faster build times than traditional hard drives.
• A USB cable compatible with the Droid RAZR M (typically micro USB, but older devices may use mini USB or have a proprietary cable)
• A decent internet connection & reliable electricity :)
• Some familiarity with basic Android operation and terminology. It would help if you’ve installed custom roms on other devices and are familiar with recovery. It may also be useful to know some basic command line concepts such as cd for “change directory”, the concept of directory hierarchies, that in Linux they are separated by /, etc.

If you are not accustomed to using Linux– this is an excellent chance to learn. It’s free– just download and run a virtual machine (VM) such as Virtualbox, then install a Linux distribution such as Ubuntu (AOSP vets Ubuntu as well). Any recent 64-bit version should work great, but the latest is recommended.

Using a VM allows Linux to run as a guest inside your host computer– a computer in a computer, if you will. If you hate Linux for whatever reason, you can always just uninstall and delete the whole thing. (There are plenty of places to find instructions for setting up Virtualbox with Ubuntu, so I’ll leave it to you to do that.)

So let’s begin!

Build CyanogenMod and CyanogenMod Recovery

Prepare the Build Environment

Install the SDK

If you have not previously installed adb and fastboot, install the Android SDK. “SDK” stands for Software Developer Kit, and it includes useful tools that you can use to flash software, look at the system logs in real time, grab screenshots, and more– all from your computer.

Install the Build Packages

Several “build packages” are needed to build CyanogenMod. You can install these using the package manager of your choice.

For both 32-bit & 64-bit systems, you’ll need:

bc bison build-essential curl flex git gnupg gperf libesd0-dev liblz4-tool libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop maven openjdk-7-jdk pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev

In addition to the above, for 64-bit systems, get these:

g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev

For Ubuntu 15.10 (wily) and newer, substitute:

• lib32readline-gplv2-dev → lib32readline6-dev

For Ubuntu 16.04 (xenial) and newer, substitute (additionally see java notes below):

• libwxgtk2.8-dev → libwxgtk3.0-dev
• openjdk-7-jdk → openjdk-8-jdk

Java versions: Different versions of CyanogenMod require different versions of the JDK (Java Development Kit):

• CyanogenMod 7 – 9: Sun/Oracle Java SE 1.6
• CyanogenMod 10.1: Sun/Oracle Java SE 1.6 or 1.7
• CyanogenMod 10.2 – 11.0: Sun/Oracle Java SE 1.6 or 1.7 (OpenJDK 1.7 works fine, but the build system will display a warning)
• CyanogenMod 12.0 – 13.0: OpenJDK 1.7 (see note about OpenJDK 1.8 below)
• CyanogenMod 14.1: OpenJDK 1.8

Ubuntu 16.04 (Xenial Xerus) or newer and OpenJDK: Since OpenJDK 1.7 was removed from the official Ubuntu repositories, you have a couple options:

1. Obtain OpenJDK 1.7 from the openjdk-r PPA
2. Enable experimental OpenJDK 1.8 support in CyanogenMod 13.0 (not available in earlier version). To enable OpenJDK 1.8 support, add this line to your $HOME/.bashrc file: export EXPERIMENTAL_USE_JAVA8=true.

Also see http://source.android.com/source/initializing.html which lists needed packages.

Create the directories

You will need to set up some directories in your build environment.

To create them:

$ mkdir -p ~/bin
$ mkdir -p ~/android/system

Install the repo command

Enter the following to download the “repo” binary and make it executable (runnable):

$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo

Put the ~/bin directory in your path of execution

In recent versions of Ubuntu, ~/bin should already be in your PATH. You can check this by opening ~/.profile with a text editor and verifying the following code exists (add it if it is missing):

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
fi

Initialize the CyanogenMod source repository

Enter the following to initialize the repository:

Note: Make sure the cm branch entered here is the one you wish to build and is supported on your device.

$ cd ~/android/system/
$ repo init -u https://github.com/CyanogenMod/android.git -b cm-13.0

Download the source code

To start the download of all the source code to your computer:

$ repo sync

The CM manifests include a sensible default configuration for repo, which we strongly suggest you use (i.e. don’t add any options to sync). For reference, our default values are -j 4 and -c. The -j 4 part means that there will be four simultaneous threads/connections. If you experience problems syncing, you can lower this to -j 3 or -j 2. -c will ask repo to pull in only the current branch, instead of the entire CM history.

Prepare to wait a long time while the source code downloads.

Get prebuilt apps (CM11 and below)

Next,

$ cd ~/android/system/vendor/cm

then enter:

$ ./get-prebuilts

You won’t see any confirmation- just another prompt. But this should cause some prebuilt apps to be loaded and installed into the source code. Once completed, this does not need to be done again.

Prepare the device-specific code

After the source downloads, ensure you are in the root of the source code (cd ~/android/system), then type:

$ source build/envsetup.sh
$ breakfast xt907

This will download the device specific configuration and kernel source for your device. An alternative to using the breakfast command is to build your own local manifest. To do this, you will need to locate your device on CyanogenMod’s GitHub and list all of the repositories defined in cm.dependencies in your local manifest.

Extract proprietary blobs

Now ensure that your Droid RAZR M is connected to your computer via the USB cable and that you are in the ~/android/system/device/motorola/xt907 directory (you can cd ~/android/system/device/motorola/xt907 if necessary). Then run the extract-files.sh script:

$ ./extract-files.sh

You should see the proprietary files (aka “blobs”) get pulled from the device and moved to the ~/android/system/vendor/motorola directory. If you see errors about adb being unable to pull the files, adb may not be in the path of execution. If this is the case, see the adb page for suggestions for dealing with “command not found” errors.

Turn on caching to speed up build

You can speed up subsequent builds by adding

export USE_CCACHE=1

to your ~/.bashrc file (what’s a .bashrc file?). Then, specify the amount of disk space to dedicate to ccache by typing this from the top of your Android tree:

prebuilts/misc/linux-x86/ccache/ccache -M 50G

where 50G corresponds to 50GB of cache. This only needs to be run once and the setting will be remembered. Anywhere in the range of 25GB to 100GB will result in very noticeably increased build speeds (for instance, a typical 1hr build time can be reduced to 20min). If you’re only building for one device, 25GB-50GB is fine. If you plan to build for several devices that do not share the same kernel source, aim for 75GB-100GB. This space will be permanently occupied on your drive, so take this into consideration. See more information about ccache on Google’s android build environment initialization page.

Start the build

Time to start building! So now type:

$ croot
$ brunch xt907

The build should begin.

If the build breaks…

• If you experience this not-enough-memory-related error…

ERROR: signapk.jar failed: return code 1make: *** [out/target/product/xt907/cm_xt907-ota-eng.root.zip] Error 1

…you may want to make the following change to ~/android/system/build/tools/releasetools/common.py:

Search for instances of -Xmx2048m (it should appear either under OPTIONS.java_args or near usage of signapk.jar), and replace it with -Xmx1024m or -Xmx512m.

Then start the build again (with brunch).

• If you see a message about things suddenly being “killed” for no reason, your (virtual) machine may have run out of memory or storage space. Assign it more resources and try again.

Install the build

Assuming the build completed without error (it will be obvious when it finishes), type:

$ cd $OUT

in the same terminal window that you did the build. Here you’ll find all the files that were created. The stuff that will go in /system is in a folder called system. The stuff that will become your ramdisk is in a folder called root. And your kernel is called… kernel.

But that’s all just background info. The two files we are interested in are (1) recovery.img, which contains CyanogenMod Recovery, and (2) cm-13.0-20161224-UNOFFICIAL-xt907.zip, which is the CyanogenMod installation package.

Installing a custom recovery using fastboot

See All About Recovery Images for more information about custom recoveries and their capabilities.

1. Make sure your computer has working fastboot and adb.

1. Connect the Droid RAZR M to the computer via USB.
2. Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
3. Open a terminal on your PC and reboot the device into fastboot mode by typing

   adb reboot bootloader

   or by using the hardware key combination for your device while it is powered off.

4. Once the device is in fastboot mode, verify your PC sees the device by typing

   fastboot devices

   • If you don’t see your device serial number, and instead see “<waiting for device>”, fastboot is not configured properly on your machine. See fastboot documentation for more info.
   • If you see “no permissionsfastboot”, make sure your UDEV rules are setup correctly.
5. Flash recovery onto your device by entering the following command:

   fastboot flash recovery your_recovery_image.img

   where the latter part is the filename of the recovery image.

6. Once the flash completes successfully, reboot the device into recovery to verify the installation.
   • Note: Some ROMs overwrite recovery at boot time so if you do not plan to immediately boot into recovery to install CyanogenMod, please be aware that this may overwrite your custom recovery with the stock one.

Install CyanogenMod

Back to the $OUT directory on your computer– you should see a file that looks something like:

cm-13.0-20161224-UNOFFICIAL-xt907.zip

Now you can flash the cm...zip file above as usual via recovery mode. Before doing so, now is a good time to make a backup of whatever installation is currently running on the device in case something goes wrong with the flash attempt. While CyanogenMod Recovery doesn’t have a backup feature, there are other custom recoveries available that do. You can also use something like Titanium Backup (root required) as an alternative.

Success! So….what’s next?

You’ve done it! Welcome to the elite club of self-builders. You’ve built your operating system from scratch, from the ground up. You are the master/mistress of your domain… and hopefully you’ve learned a bit on the way and had some fun too.

Now that you’ve succeeded in building CyanogenMod for your device, here are some suggestions on what to do next.

Also, be sure to take a glance at the Dev Center on this wiki for all kinds of more detailed information about developer topics ranging from collecting logs, understanding what’s in the source code directories, submitting your own contributions, porting CyanogenMod to new devices, and a lot more.

Congrats again!

Content of this page is based on informations from wiki.cyanogenmod.org, under CC BY-SA 3.0 licence.

Cyanogenmod ROM Motorola Atrix HD (mb886) (qinara)

Quick Info

Download CyanogenMod

Download (nightly build)
CyanogenMod 12.1 (Android 5.1 (Lollipop))

Main sections for Motorola Atrix HD (“mb886”)

1. Information about Motorola Atrix HD (“mb886”)
2. CyanogenMod install guide for Motorola Atrix HD (“mb886”)
3. Build CyanogenMod and CyanogenMod Recovery guide

Notes

Note:

For CM 11.0, the builds have been unified. Get the latest CM 11.0 builds for mb886 here.
For CM 12.0 and newer, builds were de-unified again and can be found under the usual mb886 device builds.

Note:

Your device must be bootloader unlocked to run CyanogenMod. This can only be accomplished on stock firmware versions prior to 9.20.1

Special boot modes

• Recovery: Hold Volume Down & Power simultaneously.
• Bootloader: Hold Volume Up Volume Down & Power simultaneously. On the next screen use Volume Down to scroll to bootloader and then use Volume Up to select.
• Fastboot: Hold Volume Up Volume Down & Power simultaneously. On the next screen use Volume Down to scroll to bootloader and then use Volume Up to select.

Source code

Device	http://www.github.com/cyanogenmod/android_device_motorola_mb886
Kernel	http://www.github.com/cyanogenmod/android_kernel_motorola_msm8960-common

Atrix HD Specifications

Codename:	mb886
Also known as:	qinara
Vendor:	Motorola
Release date:	2012 July
Carrier:	AT&T
Type:	phone
GSM freq:	GSM 850/900/1800/1900 HSDPA 850/1700/1900/2100
LTE freq:	LTE 700 MHz Class 17/2100
Platform:	Qualcomm MSM8960
CPU:	1.5 GHz dual-core Krait
GPU:	Adreno 225
RAM:	1GB
Weight:	140 g (4.94 oz)
Dimensions:	133.5 mm (5.26 in) (h) 69.9 mm (2.75in) (w) 8.4 mm (0.33 in) (d)
Screen size:	114 mm (4.5 in)
Resolution:	720 x 1280
Screen density:	~326 ppi
Screen type:	TFT
Internal storage:	8 GB (4 GB user available)
SD Card:	microSD, up to 32 GB
Bluetooth:	v4.0 with A2DP, LE, EDR
Wi-Fi:	802.11 a/b/g/n, dual-band, Wi-Fi Direct
Main camera:	8MP, flash: LED
Secondary camera:	1.3MP
Power:	Non-removable Li-Ion 1780 mAh battery
Peripherals:	Accelerometer, proximity, compass
CM supported:	10.1, 10.2, 11, 12, 12.1

How to Install CyanogenMod on the Motorola Atrix HD (mb886)

Important Notes

Unlocking the bootloader on the Atrix HD

1. This unlock requires your device to be rooted. Do not proceed without a working su.
2. Download motopocalypse (credit to djrbliss).
3. Extract all files in the zip.
   • Windows only: install the latest Motorola USB drivers.
4. Enable USB debugging on the device and connect device to PC.
   • Windows: run the run.bat file.
   • Linux/OSX: ./run.sh
5. Your bootloader should now be unlocked, proceed to next section.

Installing a custom recovery using fastboot

See All About Recovery Images for more information about custom recoveries and their capabilities.

1. Make sure your computer has working fastboot and adb.
2. Download recovery — you can directly download a recovery image using the link below, or visit download.cyanogenmod.org to obtain the latest version of CyanogenMod Recovery for your device.

   Recovery: Download

   md5:

3. Connect the Atrix HD to the computer via USB.
4. Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
5. Open a terminal on your PC and reboot the device into fastboot mode by typing

   adb reboot bootloader

   or by using the hardware key combination for your device while it is powered off.

6. Once the device is in fastboot mode, verify your PC sees the device by typing

   fastboot devices

   • If you don’t see your device serial number, and instead see “<waiting for device>”, fastboot is not configured properly on your machine. See fastboot documentation for more info.
   • If you see “no permissionsfastboot”, make sure your UDEV rules are setup correctly.
7. Flash recovery onto your device by entering the following command:

   fastboot flash recovery your_recovery_image.img

   where the latter part is the filename of the recovery image.

8. Once the flash completes successfully, reboot the device into recovery to verify the installation. Boot to recovery instructions: Hold Volume Down & Power simultaneously.
   • Note: Some ROMs overwrite recovery at boot time so if you do not plan to immediately boot into recovery to install CyanogenMod, please be aware that this may overwrite your custom recovery with the stock one.

Installing CyanogenMod from recovery

1. Make sure your computer has working adb.
2. Download the CyanogenMod build package for your device that you’d like to install to your computer.

   Optional: Download 3rd party applications packages, like Google Apps which are necessary to download apps from Google Play.

3. Boot to recovery mode, and connect the phone to your computer through USB.
   • Hold Volume Down & Power simultaneously.
4. In ClockworkMod Recovery, use the physical volume buttons to move up and down. On most devices, the power button is used to confirm a menu selection, but for some devices a physical home key acts as a selector. Some devices have touch enabled ClockworkMod Recovery, in which case you may be able to swipe to, or touch, menu selections.
5. Optional (Recommended): Select backup and restore to create a backup.
6. Select wipe data/factory reset.
7. You have two options for transferring and installing the installation packages. The sideload method is more universal across devices, whereas the push and install method is more commonly used:
   • Sideload method: select install zip > install zip from sideload. Follow the on-screen notices to install the package. The installer does not necessarily display an “Install complete.” message. You can tell the install is complete if there were no fatal error messages and you have regained control over the menu.
   • Push and install method: Open a command prompt (or Terminal on Mac and Linux) and navigate to the directory holding the package(s) you would like to install. On the device, navigate to the mounts and storage menu. If you see /storage/sdcard0 or /sdcard as a mountable volume, go ahead and mount it. If you do not see one of these partitions, then instead mount the /data partition. Take note of which volume you mounted. Now, push the package(s) to your device (also, see tip below):

   – If you mounted /storage/sdcard0, then: adb push update.zip /storage/sdcard0/

   – If you mounted /sdcard or /data, then: adb push update.zip /sdcard/

   where update.zip should be replaced with the package filename. Go back to the main menu and select install zip. Choose to install from the same directory where you pushed the package(s). If you are installing multiple packages, install CyanogenMod first and then install any subsequent packages on top of it.

8. Once installation has finished, return to the main menu and select reboot system now. The device will now boot into CyanogenMod.

How To Build CyanogenMod For Motorola Atrix HD (mb886)

Introduction

These instructions will hopefully assist you to start with a stock Atrix HD, unlock the bootloader (if necessary), and then download the required tools as well as the very latest source code for CyanogenMod (based on Google’s Android operating system). Using these, you can build both CyanogenMod and CyanogenMod Recovery image from source code, and then install them both to your device.

It is difficult to say how much experience is necessary to follow these instructions. While this guide is certainly not for the very very very uninitiated, these steps shouldn’t require a PhD in software development either. Some readers will have no difficulty and breeze through the steps easily. Others may struggle over the most basic operation. Because people’s experiences, backgrounds, and intuitions differ, it may be a good idea to read through just to ascertain whether you feel comfortable or are getting over your head.

Remember, you assume all risk of trying this, but you will reap the rewards! It’s pretty satisfying to boot into a fresh operating system you baked at home :) And once you’re an Android-building ninja, there will be no more need to wait for “nightly” builds from anyone. You will have at your fingertips the skills to build a full operating system from code to a running device, whenever you want. Where you go from there– maybe you’ll add a feature, fix a bug, add a translation, or use what you’ve learned to build a new app or port to a new device– or maybe you’ll never build again– it’s all really up to you.

What you’ll need

• A Atrix HD
• A relatively recent computer (Linux, OS X, or Windows) with a reasonable amount of RAM and about 100 GB of free storage (more if you enable ccache or build for multiple devices). The less RAM you have, the longer the build will take (aim for 8 GB or more). Using SSDs results in considerably faster build times than traditional hard drives.
• A USB cable compatible with the Atrix HD (typically micro USB, but older devices may use mini USB or have a proprietary cable)
• A decent internet connection & reliable electricity :)
• Some familiarity with basic Android operation and terminology. It would help if you’ve installed custom roms on other devices and are familiar with recovery. It may also be useful to know some basic command line concepts such as cd for “change directory”, the concept of directory hierarchies, that in Linux they are separated by /, etc.

If you are not accustomed to using Linux– this is an excellent chance to learn. It’s free– just download and run a virtual machine (VM) such as Virtualbox, then install a Linux distribution such as Ubuntu (AOSP vets Ubuntu as well). Any recent 64-bit version should work great, but the latest is recommended.

Using a VM allows Linux to run as a guest inside your host computer– a computer in a computer, if you will. If you hate Linux for whatever reason, you can always just uninstall and delete the whole thing. (There are plenty of places to find instructions for setting up Virtualbox with Ubuntu, so I’ll leave it to you to do that.)

So let’s begin!

Build CyanogenMod and CyanogenMod Recovery

Prepare the Build Environment

Install the SDK

If you have not previously installed adb and fastboot, install the Android SDK. “SDK” stands for Software Developer Kit, and it includes useful tools that you can use to flash software, look at the system logs in real time, grab screenshots, and more– all from your computer.

Install the Build Packages

Several “build packages” are needed to build CyanogenMod. You can install these using the package manager of your choice.

For both 32-bit & 64-bit systems, you’ll need:

bc bison build-essential curl flex git gnupg gperf libesd0-dev liblz4-tool libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop maven openjdk-7-jdk pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev

In addition to the above, for 64-bit systems, get these:

g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev

For Ubuntu 15.10 (wily) and newer, substitute:

• lib32readline-gplv2-dev → lib32readline6-dev

For Ubuntu 16.04 (xenial) and newer, substitute (additionally see java notes below):

• libwxgtk2.8-dev → libwxgtk3.0-dev
• openjdk-7-jdk → openjdk-8-jdk

Java versions: Different versions of CyanogenMod require different versions of the JDK (Java Development Kit):

• CyanogenMod 7 – 9: Sun/Oracle Java SE 1.6
• CyanogenMod 10.1: Sun/Oracle Java SE 1.6 or 1.7
• CyanogenMod 10.2 – 11.0: Sun/Oracle Java SE 1.6 or 1.7 (OpenJDK 1.7 works fine, but the build system will display a warning)
• CyanogenMod 12.0 – 13.0: OpenJDK 1.7 (see note about OpenJDK 1.8 below)
• CyanogenMod 14.1: OpenJDK 1.8

Ubuntu 16.04 (Xenial Xerus) or newer and OpenJDK: Since OpenJDK 1.7 was removed from the official Ubuntu repositories, you have a couple options:

1. Obtain OpenJDK 1.7 from the openjdk-r PPA
2. Enable experimental OpenJDK 1.8 support in CyanogenMod 13.0 (not available in earlier version). To enable OpenJDK 1.8 support, add this line to your $HOME/.bashrc file: export EXPERIMENTAL_USE_JAVA8=true.

Also see http://source.android.com/source/initializing.html which lists needed packages.

Create the directories

You will need to set up some directories in your build environment.

To create them:

$ mkdir -p ~/bin
$ mkdir -p ~/android/system

Install the repo command

Enter the following to download the “repo” binary and make it executable (runnable):

$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo

Put the ~/bin directory in your path of execution

In recent versions of Ubuntu, ~/bin should already be in your PATH. You can check this by opening ~/.profile with a text editor and verifying the following code exists (add it if it is missing):

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
fi

Initialize the CyanogenMod source repository

Enter the following to initialize the repository:

Note: Make sure the cm branch entered here is the one you wish to build and is supported on your device.

$ cd ~/android/system/
$ repo init -u https://github.com/CyanogenMod/android.git -b cm-13.0

Download the source code

To start the download of all the source code to your computer:

$ repo sync

The CM manifests include a sensible default configuration for repo, which we strongly suggest you use (i.e. don’t add any options to sync). For reference, our default values are -j 4 and -c. The -j 4 part means that there will be four simultaneous threads/connections. If you experience problems syncing, you can lower this to -j 3 or -j 2. -c will ask repo to pull in only the current branch, instead of the entire CM history.

Prepare to wait a long time while the source code downloads.

Get prebuilt apps (CM11 and below)

Next,

$ cd ~/android/system/vendor/cm

then enter:

$ ./get-prebuilts

You won’t see any confirmation- just another prompt. But this should cause some prebuilt apps to be loaded and installed into the source code. Once completed, this does not need to be done again.

Prepare the device-specific code

After the source downloads, ensure you are in the root of the source code (cd ~/android/system), then type:

$ source build/envsetup.sh
$ breakfast mb886

This will download the device specific configuration and kernel source for your device. An alternative to using the breakfast command is to build your own local manifest. To do this, you will need to locate your device on CyanogenMod’s GitHub and list all of the repositories defined in cm.dependencies in your local manifest.

Extract proprietary blobs

Now ensure that your Atrix HD is connected to your computer via the USB cable and that you are in the ~/android/system/device/motorola/mb886 directory (you can cd ~/android/system/device/motorola/mb886 if necessary). Then run the extract-files.sh script:

$ ./extract-files.sh

You should see the proprietary files (aka “blobs”) get pulled from the device and moved to the ~/android/system/vendor/motorola directory. If you see errors about adb being unable to pull the files, adb may not be in the path of execution. If this is the case, see the adb page for suggestions for dealing with “command not found” errors.

Turn on caching to speed up build

You can speed up subsequent builds by adding

export USE_CCACHE=1

to your ~/.bashrc file (what’s a .bashrc file?). Then, specify the amount of disk space to dedicate to ccache by typing this from the top of your Android tree:

prebuilts/misc/linux-x86/ccache/ccache -M 50G

where 50G corresponds to 50GB of cache. This only needs to be run once and the setting will be remembered. Anywhere in the range of 25GB to 100GB will result in very noticeably increased build speeds (for instance, a typical 1hr build time can be reduced to 20min). If you’re only building for one device, 25GB-50GB is fine. If you plan to build for several devices that do not share the same kernel source, aim for 75GB-100GB. This space will be permanently occupied on your drive, so take this into consideration. See more information about ccache on Google’s android build environment initialization page.

Start the build

Time to start building! So now type:

$ croot
$ brunch mb886

The build should begin.

If the build breaks…

• If you experience this not-enough-memory-related error…

ERROR: signapk.jar failed: return code 1make: *** [out/target/product/mb886/cm_mb886-ota-eng.root.zip] Error 1

…you may want to make the following change to ~/android/system/build/tools/releasetools/common.py:

Search for instances of -Xmx2048m (it should appear either under OPTIONS.java_args or near usage of signapk.jar), and replace it with -Xmx1024m or -Xmx512m.

Then start the build again (with brunch).

• If you see a message about things suddenly being “killed” for no reason, your (virtual) machine may have run out of memory or storage space. Assign it more resources and try again.

Install the build

Assuming the build completed without error (it will be obvious when it finishes), type:

$ cd $OUT

in the same terminal window that you did the build. Here you’ll find all the files that were created. The stuff that will go in /system is in a folder called system. The stuff that will become your ramdisk is in a folder called root. And your kernel is called… kernel.

But that’s all just background info. The two files we are interested in are (1) recovery.img, which contains CyanogenMod Recovery, and (2) cm-13.0-20161224-UNOFFICIAL-mb886.zip, which is the CyanogenMod installation package.

Installing a custom recovery using fastboot

See All About Recovery Images for more information about custom recoveries and their capabilities.

1. Make sure your computer has working fastboot and adb.

1. Connect the Atrix HD to the computer via USB.
2. Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
3. Open a terminal on your PC and reboot the device into fastboot mode by typing

   adb reboot bootloader

   or by using the hardware key combination for your device while it is powered off.

4. Once the device is in fastboot mode, verify your PC sees the device by typing

   fastboot devices

   • If you don’t see your device serial number, and instead see “<waiting for device>”, fastboot is not configured properly on your machine. See fastboot documentation for more info.
   • If you see “no permissionsfastboot”, make sure your UDEV rules are setup correctly.
5. Flash recovery onto your device by entering the following command:

   fastboot flash recovery your_recovery_image.img

   where the latter part is the filename of the recovery image.

6. Once the flash completes successfully, reboot the device into recovery to verify the installation.
   • Note: Some ROMs overwrite recovery at boot time so if you do not plan to immediately boot into recovery to install CyanogenMod, please be aware that this may overwrite your custom recovery with the stock one.

Install CyanogenMod

Back to the $OUT directory on your computer– you should see a file that looks something like:

cm-13.0-20161224-UNOFFICIAL-mb886.zip

Now you can flash the cm...zip file above as usual via recovery mode. Before doing so, now is a good time to make a backup of whatever installation is currently running on the device in case something goes wrong with the flash attempt. While CyanogenMod Recovery doesn’t have a backup feature, there are other custom recoveries available that do. You can also use something like Titanium Backup (root required) as an alternative.

Success! So….what’s next?

You’ve done it! Welcome to the elite club of self-builders. You’ve built your operating system from scratch, from the ground up. You are the master/mistress of your domain… and hopefully you’ve learned a bit on the way and had some fun too.

Now that you’ve succeeded in building CyanogenMod for your device, here are some suggestions on what to do next.

Also, be sure to take a glance at the Dev Center on this wiki for all kinds of more detailed information about developer topics ranging from collecting logs, understanding what’s in the source code directories, submitting your own contributions, porting CyanogenMod to new devices, and a lot more.

Congrats again!

Content of this page is based on informations from wiki.cyanogenmod.org, under CC BY-SA 3.0 licence.

Cyanogenmod ROM Motorola Atrix 4G (olympus)

Quick Info

Download CyanogenMod

Download (nightly build)
CyanogenMod 7 (Android 2.3 (Gingerbread))

Main sections for Motorola Atrix 4G (“olympus”)

1. Information about Motorola Atrix 4G (“olympus”)
2. CyanogenMod install guide for Motorola Atrix 4G (“olympus”)
3. Build CyanogenMod and CyanogenMod Recovery guide

Note: Support Status

This device does not support the latest official release of CyanogenMod. This may be due to hardware limitations or simply because development is ongoing. The most recent version supported is based on the gingerbread branch of CyanogenMod.

Special boot modes

• Bootloader: Hold down the Volume Down & Power buttons

Source code

Device

http://www.github.com/cyanogenmod/android_device_motorola_olympus

Atrix 4G Specifications

Codename:	olympus
Vendor:	Motorola
Manufacturer:	motorola
Release date:	2011 August 5
Carrier:	Verizon
Type:	phone
GSM freq:	850 900 1800 1900 MHz
CDMA freq:	850 1900 2100 MHz
LTE freq:	700MHz
Platform:	NVIDIA Tegra 2
CPU:	1 GHz dual-core Nvidia Tegra 2
GPU:	GeForce ULP
RAM:	1GB
Weight:	158 g (5.6 oz)
Dimensions:	127 mm (5 in) (h) 67 mm (2.6 in) (w) 12 mm (0.472 in) (d)
Screen size:	109 mm (4.3 in)
Resolution:	960 x 540 px
Internal storage:	16GB
SD Card:	up to 32 GB
Bluetooth:	2.1
Wi-Fi:	802.11 b/g/n
Main camera:	8MP w/ Dual LED flash
Secondary camera:	1.3MP
Power:	1700 mAh internal rechargeable removable lithium-ion polymer battery
CM supported:	7
Latest CM version:	gingerbread

bc bison build-essential curl flex git gnupg gperf libesd0-dev liblz4-tool libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop maven openjdk-7-jdk pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev

g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev

$ mkdir -p ~/bin
$ mkdir -p ~/android/system

$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
fi

$ cd ~/android/system/
$ repo init -u https://github.com/CyanogenMod/android.git -b gingerbread

$ repo sync

$ cd ~/android/system/vendor/cyanogen

$ ./get-rommanager

After the source downloads, ensure you are in the root of the source code (cd ~/android/system), then type:

$ source build/envsetup.sh
$ lunch

$ lunch cm_olympus-userdebug

$ lunch full_olympus-userdebug

$ ./extract-files.sh

export USE_CCACHE=1

prebuilt/linux-x86/ccache/ccache -M 50G

$ croot
$ brunch olympus

ERROR: signapk.jar failed: return code 1make: *** [out/target/product/olympus/cm_olympus-ota-eng.root.zip] Error 1

$ cd $OUT

cm-7-20161224-UNOFFICIAL-olympus.zip

Cyanogenmod ROM Motorola RAZR HD (GSM) (vanquish_u) (xt925)

Quick Info

Download CyanogenMod

Download (nightly build)
CyanogenMod 12.1 (Android 5.1 (Lollipop))

Main sections for Motorola RAZR HD (GSM) (“xt925”)

1. Information about Motorola RAZR HD (GSM) (“xt925”)
2. CyanogenMod install guide for Motorola RAZR HD (GSM) (“xt925”)
3. Build CyanogenMod and CyanogenMod Recovery guide

Notes

Note:

Your device must be bootloader unlocked.
For CM 11.0, the device builds have been unified. Get the latest CM 11.0 build for KitKat bootloader updated xt925 here and for xt925 still on JellyBean bootloader here.
For CM 12.0 and newer, the builds were de-unified again. The builds for KitKat updated bootloader xt925 are under the usual xt925 builds. The builds for xt925 that is still on JellyBean bootloader are here.

Special boot modes

• Recovery: Volume Down & Power.
• Bootloader: Volume Up & Volume Down & Power. Use Volume Down to scroll and Volume Up to select.
• Fastboot: Volume Up & Volume Down & Power. Use Volume Down to scroll and Volume Up to select.

Source code

Device	http://www.github.com/cyanogenmod/android_device_motorola_xt925
Kernel	http://www.github.com/cyanogenmod/android_kernel_motorola_msm8960-common

RAZR HD (GSM) Specifications

Codename:	xt925
Also known as:	vanquish_u
Vendor:	Motorola
Release date:	2012 September
Type:	phone
GSM freq:	GSM 850 / 900 / 1800 / 1900 HSDPA 850 / 900 / 1900 / 2100
LTE freq:	LTE 800 / 1800 / 2600 LTE 700 / 800 / 1700 / 1800 / 2600
Platform:	Qualcomm MSM8960
CPU:	1.5 GHz dual-core Cortex A9 (Krait)
GPU:	Adreno 225
RAM:	1GB
Weight:	146 g (5.15 oz)
Dimensions:	131.9 x 67.9 x 8.4 mm (5.19 x 2.67 x 0.33 in)
Screen size:	119 mm (4.7 in)
Resolution:	720 x 1280 pixels
Screen density:	~312 ppi
Screen type:	Super AMOLED capacitive touchscreen
Internal storage:	16 GB (12 GB user available)
SD Card:	microSD, up to 32 GB
Bluetooth:	Yes, v4.0 with A2DP, LE, EDR
Wi-Fi:	Wi-Fi 802.11 a/b/g/n, dual-band, DLNA, Wi-Fi hotspot
Main camera:	8 MP, 3264×2448 pixels, autofocus, 1080p@30fps, flash: LED flash
Secondary camera:	Yes, 1.3 MP
Power:	Non-removable Li-Po 2500/2530 mAh battery (Up to 16h-2G / Up to 22h-3G)
Peripherals:	Accelerometer, proximity, compass
CM supported:	10.1, 10.2, 11, 12, 12.1

How to Install CyanogenMod on the Motorola RAZR HD (GSM) (xt925)

Important Notes

Unlocking the bootloader

1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging on the device.
3. Enable OEM unlock in the Developer options settings on the device. (Note: Not all devices have this setting, so continue with next step if yours does not.)
4. Connect the device to the computer through USB.
5. From a terminal on a computer, type the following to boot the device into fastboot mode:

   adb reboot bootloader

6. Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
   • If you don’t see your device serial number, and instead see “<waiting for device>”, fastboot is not configured properly on your machine. See fastboot documentation for more info.
   • If you see “no permissions fastboot”, try running fastboot as root.
7. From the same terminal, type the following command to obtain your bootloader unlock code:

   fastboot oem get_unlock_data

8. Visit the Motorola Bootloader Unlock website and follow the instructions there to obtain your unlock key and unlock your bootloader.
9. If the device doesn’t automatically reboot, reboot it from the menu. It should now be unlocked.
10. Since the device resets completely, you will need to re-enable USB debugging on the device to continue.

Installing a custom recovery using fastboot

See All About Recovery Images for more information about custom recoveries and their capabilities.

1. Make sure your computer has working fastboot and adb.
2. Download recovery — you can directly download a recovery image using the link below, or visit twrp.me to obtain the latest version of Team Win Recovery Project for your device.

   Recovery: Download

   md5: 047f9294e72d813526437e9464372c46

3. Connect the RAZR HD (GSM) to the computer via USB.
4. Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
5. Open a terminal on your PC and reboot the device into fastboot mode by typing

   adb reboot bootloader

   or by using the hardware key combination for your device while it is powered off.

6. Once the device is in fastboot mode, verify your PC sees the device by typing

   fastboot devices

   • If you don’t see your device serial number, and instead see “<waiting for device>”, fastboot is not configured properly on your machine. See fastboot documentation for more info.
   • If you see “no permissionsfastboot”, make sure your UDEV rules are setup correctly.
7. Flash recovery onto your device by entering the following command:

   fastboot flash recovery your_recovery_image.img

   where the latter part is the filename of the recovery image.

8. Once the flash completes successfully, reboot the device into recovery to verify the installation. Boot to recovery instructions: Volume Down & Power.
   • Note: Some ROMs overwrite recovery at boot time so if you do not plan to immediately boot into recovery to install CyanogenMod, please be aware that this may overwrite your custom recovery with the stock one.

Installing CyanogenMod from recovery

1. Make sure your computer has working adb.
2. Download the CyanogenMod build package for your device that you’d like to install to your computer.

   Optional: Download 3rd party applications packages, like Google Apps which are necessary to download apps from Google Play.

3. Place the CyanogenMod .zip package, as well as any optional .zip packages, on the root of /sdcard:
   • Using adb: adb push filename.zip /sdcard/

   Note: You can copy the .zip packages to your device using any method you are familiar with. The adb method is used here because it is universal across all devices and works in both Android and recovery mode. If you are in recovery mode, you may need to ensure /sdcard (sometimes called Internal Storage) is mounted by checking its status in the Mounts menu. If you have booted regularly, USB debugging must be enabled.

4. If you are not already in recovery, boot to recovery mode now.
   • Volume Down & Power.
5. In Team Win Recovery Project, select menu choices by tapping on the appropriately labelled button.
6. Optional (Recommended): Select the Backup button to create a backup.
7. Select Wipe and then Factory Reset.
8. Select Install.
9. Navigate to /sdcard and select the CyanogenMod .zip package.
10. Follow the on-screen notices to install the package.
11. Optional: Install any additional packages you wish using the same method (if you are installing multiple packages, install CyanogenMod first and then install any subsequent packages on top of it).
12. Once installation has finished, return to the main menu and select Reboot, then System. The device will now boot into CyanogenMod.

How To Build CyanogenMod For Motorola RAZR HD (GSM) (xt925)

Introduction

These instructions will hopefully assist you to start with a stock RAZR HD (GSM), unlock the bootloader (if necessary), and then download the required tools as well as the very latest source code for CyanogenMod (based on Google’s Android operating system). Using these, you can build both CyanogenMod and CyanogenMod Recovery image from source code, and then install them both to your device.

It is difficult to say how much experience is necessary to follow these instructions. While this guide is certainly not for the very very very uninitiated, these steps shouldn’t require a PhD in software development either. Some readers will have no difficulty and breeze through the steps easily. Others may struggle over the most basic operation. Because people’s experiences, backgrounds, and intuitions differ, it may be a good idea to read through just to ascertain whether you feel comfortable or are getting over your head.

Remember, you assume all risk of trying this, but you will reap the rewards! It’s pretty satisfying to boot into a fresh operating system you baked at home :) And once you’re an Android-building ninja, there will be no more need to wait for “nightly” builds from anyone. You will have at your fingertips the skills to build a full operating system from code to a running device, whenever you want. Where you go from there– maybe you’ll add a feature, fix a bug, add a translation, or use what you’ve learned to build a new app or port to a new device– or maybe you’ll never build again– it’s all really up to you.

What you’ll need

• A RAZR HD (GSM)
• A relatively recent computer (Linux, OS X, or Windows) with a reasonable amount of RAM and about 100 GB of free storage (more if you enable ccache or build for multiple devices). The less RAM you have, the longer the build will take (aim for 8 GB or more). Using SSDs results in considerably faster build times than traditional hard drives.
• A USB cable compatible with the RAZR HD (GSM) (typically micro USB, but older devices may use mini USB or have a proprietary cable)
• A decent internet connection & reliable electricity :)
• Some familiarity with basic Android operation and terminology. It would help if you’ve installed custom roms on other devices and are familiar with recovery. It may also be useful to know some basic command line concepts such as cd for “change directory”, the concept of directory hierarchies, that in Linux they are separated by /, etc.

If you are not accustomed to using Linux– this is an excellent chance to learn. It’s free– just download and run a virtual machine (VM) such as Virtualbox, then install a Linux distribution such as Ubuntu (AOSP vets Ubuntu as well). Any recent 64-bit version should work great, but the latest is recommended.

Using a VM allows Linux to run as a guest inside your host computer– a computer in a computer, if you will. If you hate Linux for whatever reason, you can always just uninstall and delete the whole thing. (There are plenty of places to find instructions for setting up Virtualbox with Ubuntu, so I’ll leave it to you to do that.)

So let’s begin!

Unlocking your RAZR HD (GSM)

What does “unlocking” mean?

The first step in putting any custom operating system on your RAZR HD (GSM) is to unlock the bootloader. A bootloader is the very first program that runs when you turn on your device. The bootloader initializes some hardware and then loads the kernel and ramdisk, and gets the boot process going. If the bootloader is in locked mode, it will ensure that only the stock operating system can run. Since you will be installing your own operating system, you need to turn this off. Luckily, Google and motorola make it easy.

Okay. I’m in. What do I need to do this?

To unlock your bootloader, you’ll first need a program on your computer called fastboot. One way to get fastboot is to download and install the Android SDK (Software Developer Kit) from Google. The SDK is used by app developers when they’re writing programs for Android, and who knows, you may want to write apps someday. But the SDK also contains two great tools that are useful even to non-developers. They are:

• adb – Android Debug Bridge – this is a program that lets your computer “talk” to your RAZR HD (GSM) while the device is running. Among the many things you can do with adb– you can push files from your computer to the device or pull files from the device to your computer, you can get a running real-time log of Android activity (which is very useful for debugging or having others help you debug), you can create an interactive “shell” session (similar to Linux or OS X) to type commands to your device, and much more.

• fastboot – fastboot works a little bit like adb, except it’s often used at a much earlier point in the boot process, even before Android or any operating system loads. You can put your RAZR HD (GSM) into a “fastboot” mode, whereby, if you are connected via USB cable, you can copy entire partitions from your computer (usually in the form of an image file, such as boot.img or recovery.img) over to the device, wiping over whatever happened to be there. Fastboot is able to do more than that, however. It’s also used to send special commands to the device to do things such as unlock your bootloader.

How do I do the actual unlocking?

So this should be a one time thing…

Install the Android SDK

To unlock your RAZR HD (GSM), you will need fastboot installed. Go ahead and download the SDK, per the steps on Google’s web page. Then install it by following the specific instructions for your computer.

Unlocking the bootloader

1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging on the device.
3. Enable OEM unlock in the Developer options settings on the device. (Note: Not all devices have this setting, so continue with next step if yours does not.)
4. Connect the device to the computer through USB.
5. From a terminal on a computer, type the following to boot the device into fastboot mode:

   adb reboot bootloader

6. Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
   • If you don’t see your device serial number, and instead see “<waiting for device>”, fastboot is not configured properly on your machine. See fastboot documentation for more info.
   • If you see “no permissions fastboot”, try running fastboot as root.
7. From the same terminal, type the following command to unlock the bootloader:

   fastboot oem get_unlock_data

8. If the device doesn’t automatically reboot, reboot it from the menu. It should now be unlocked.
9. Since the device resets completely, you will need to re-enable USB debugging on the device to continue.

Troubleshooting

If you have issues with fastboot or adb not being found, make sure that the Android SDK folder /platform-tools, which contains the adb and fastboot files, are in the path of execution for commands typed at the terminal. Usually typing something like

# PATH=$PATH:/your/specific/path/to/android/sdk/platform-tools/

will work for that terminal session.

$ sudo apt-get install ia32-libs

You’ll be using fastboot again to install a custom recovery.

Build CyanogenMod and CyanogenMod Recovery

Prepare the Build Environment

Install the SDK

If you have not previously installed adb and fastboot, install the Android SDK. “SDK” stands for Software Developer Kit, and it includes useful tools that you can use to flash software, look at the system logs in real time, grab screenshots, and more– all from your computer.

Install the Build Packages

Several “build packages” are needed to build CyanogenMod. You can install these using the package manager of your choice.

For both 32-bit & 64-bit systems, you’ll need:

bc bison build-essential curl flex git gnupg gperf libesd0-dev liblz4-tool libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop maven openjdk-7-jdk pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev

In addition to the above, for 64-bit systems, get these:

g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev

For Ubuntu 15.10 (wily) and newer, substitute:

• lib32readline-gplv2-dev → lib32readline6-dev

For Ubuntu 16.04 (xenial) and newer, substitute (additionally see java notes below):

• libwxgtk2.8-dev → libwxgtk3.0-dev
• openjdk-7-jdk → openjdk-8-jdk

Java versions: Different versions of CyanogenMod require different versions of the JDK (Java Development Kit):

• CyanogenMod 7 – 9: Sun/Oracle Java SE 1.6
• CyanogenMod 10.1: Sun/Oracle Java SE 1.6 or 1.7
• CyanogenMod 10.2 – 11.0: Sun/Oracle Java SE 1.6 or 1.7 (OpenJDK 1.7 works fine, but the build system will display a warning)
• CyanogenMod 12.0 – 13.0: OpenJDK 1.7 (see note about OpenJDK 1.8 below)
• CyanogenMod 14.1: OpenJDK 1.8

Ubuntu 16.04 (Xenial Xerus) or newer and OpenJDK: Since OpenJDK 1.7 was removed from the official Ubuntu repositories, you have a couple options:

1. Obtain OpenJDK 1.7 from the openjdk-r PPA
2. Enable experimental OpenJDK 1.8 support in CyanogenMod 13.0 (not available in earlier version). To enable OpenJDK 1.8 support, add this line to your $HOME/.bashrc file: export EXPERIMENTAL_USE_JAVA8=true.

Also see http://source.android.com/source/initializing.html which lists needed packages.

Create the directories

You will need to set up some directories in your build environment.

To create them:

$ mkdir -p ~/bin
$ mkdir -p ~/android/system

Install the repo command

Enter the following to download the “repo” binary and make it executable (runnable):

$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo

Put the ~/bin directory in your path of execution

In recent versions of Ubuntu, ~/bin should already be in your PATH. You can check this by opening ~/.profile with a text editor and verifying the following code exists (add it if it is missing):

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
fi

Initialize the CyanogenMod source repository

Enter the following to initialize the repository:

Note: Make sure the cm branch entered here is the one you wish to build and is supported on your device.

$ cd ~/android/system/
$ repo init -u https://github.com/CyanogenMod/android.git -b cm-13.0

Download the source code

To start the download of all the source code to your computer:

$ repo sync

The CM manifests include a sensible default configuration for repo, which we strongly suggest you use (i.e. don’t add any options to sync). For reference, our default values are -j 4 and -c. The -j 4 part means that there will be four simultaneous threads/connections. If you experience problems syncing, you can lower this to -j 3 or -j 2. -c will ask repo to pull in only the current branch, instead of the entire CM history.

Prepare to wait a long time while the source code downloads.

Get prebuilt apps (CM11 and below)

Next,

$ cd ~/android/system/vendor/cm

then enter:

$ ./get-prebuilts

You won’t see any confirmation- just another prompt. But this should cause some prebuilt apps to be loaded and installed into the source code. Once completed, this does not need to be done again.

Prepare the device-specific code

After the source downloads, ensure you are in the root of the source code (cd ~/android/system), then type:

$ source build/envsetup.sh
$ breakfast xt925

This will download the device specific configuration and kernel source for your device. An alternative to using the breakfast command is to build your own local manifest. To do this, you will need to locate your device on CyanogenMod’s GitHub and list all of the repositories defined in cm.dependencies in your local manifest.

Extract proprietary blobs

Now ensure that your RAZR HD (GSM) is connected to your computer via the USB cable and that you are in the ~/android/system/device/motorola/xt925 directory (you can cd ~/android/system/device/motorola/xt925 if necessary). Then run the extract-files.sh script:

$ ./extract-files.sh

You should see the proprietary files (aka “blobs”) get pulled from the device and moved to the ~/android/system/vendor/motorola directory. If you see errors about adb being unable to pull the files, adb may not be in the path of execution. If this is the case, see the adb page for suggestions for dealing with “command not found” errors.

Turn on caching to speed up build

You can speed up subsequent builds by adding

export USE_CCACHE=1

to your ~/.bashrc file (what’s a .bashrc file?). Then, specify the amount of disk space to dedicate to ccache by typing this from the top of your Android tree:

prebuilts/misc/linux-x86/ccache/ccache -M 50G

where 50G corresponds to 50GB of cache. This only needs to be run once and the setting will be remembered. Anywhere in the range of 25GB to 100GB will result in very noticeably increased build speeds (for instance, a typical 1hr build time can be reduced to 20min). If you’re only building for one device, 25GB-50GB is fine. If you plan to build for several devices that do not share the same kernel source, aim for 75GB-100GB. This space will be permanently occupied on your drive, so take this into consideration. See more information about ccache on Google’s android build environment initialization page.

Start the build

Time to start building! So now type:

$ croot
$ brunch xt925

The build should begin.

If the build breaks…

• If you experience this not-enough-memory-related error…

ERROR: signapk.jar failed: return code 1make: *** [out/target/product/xt925/cm_xt925-ota-eng.root.zip] Error 1

…you may want to make the following change to ~/android/system/build/tools/releasetools/common.py:

Search for instances of -Xmx2048m (it should appear either under OPTIONS.java_args or near usage of signapk.jar), and replace it with -Xmx1024m or -Xmx512m.

Then start the build again (with brunch).

• If you see a message about things suddenly being “killed” for no reason, your (virtual) machine may have run out of memory or storage space. Assign it more resources and try again.

Install the build

Assuming the build completed without error (it will be obvious when it finishes), type:

$ cd $OUT

in the same terminal window that you did the build. Here you’ll find all the files that were created. The stuff that will go in /system is in a folder called system. The stuff that will become your ramdisk is in a folder called root. And your kernel is called… kernel.

But that’s all just background info. The two files we are interested in are (1) recovery.img, which contains CyanogenMod Recovery, and (2) cm-13.0-20161224-UNOFFICIAL-xt925.zip, which is the CyanogenMod installation package.

Installing a custom recovery using fastboot

See All About Recovery Images for more information about custom recoveries and their capabilities.

1. Make sure your computer has working fastboot and adb.

1. Connect the RAZR HD (GSM) to the computer via USB.
2. Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
3. Open a terminal on your PC and reboot the device into fastboot mode by typing

   adb reboot bootloader

   or by using the hardware key combination for your device while it is powered off.

4. Once the device is in fastboot mode, verify your PC sees the device by typing

   fastboot devices

   • If you don’t see your device serial number, and instead see “<waiting for device>”, fastboot is not configured properly on your machine. See fastboot documentation for more info.
   • If you see “no permissionsfastboot”, make sure your UDEV rules are setup correctly.
5. Flash recovery onto your device by entering the following command:

   fastboot flash recovery your_recovery_image.img

   where the latter part is the filename of the recovery image.

6. Once the flash completes successfully, reboot the device into recovery to verify the installation.
   • Note: Some ROMs overwrite recovery at boot time so if you do not plan to immediately boot into recovery to install CyanogenMod, please be aware that this may overwrite your custom recovery with the stock one.

Install CyanogenMod

Back to the $OUT directory on your computer– you should see a file that looks something like:

cm-13.0-20161224-UNOFFICIAL-xt925.zip

Now you can flash the cm...zip file above as usual via recovery mode. Before doing so, now is a good time to make a backup of whatever installation is currently running on the device in case something goes wrong with the flash attempt. While CyanogenMod Recovery doesn’t have a backup feature, there are other custom recoveries available that do. You can also use something like Titanium Backup (root required) as an alternative.

Success! So….what’s next?

You’ve done it! Welcome to the elite club of self-builders. You’ve built your operating system from scratch, from the ground up. You are the master/mistress of your domain… and hopefully you’ve learned a bit on the way and had some fun too.

Now that you’ve succeeded in building CyanogenMod for your device, here are some suggestions on what to do next.

Also, be sure to take a glance at the Dev Center on this wiki for all kinds of more detailed information about developer topics ranging from collecting logs, understanding what’s in the source code directories, submitting your own contributions, porting CyanogenMod to new devices, and a lot more.

Congrats again!

Content of this page is based on informations from wiki.cyanogenmod.org, under CC BY-SA 3.0 licence.