Cyanogenmod ROM HTC G1 (dream_sapphire)

Quick Info

Download CyanogenMod

It looks like we don’t have any roms for download for this device. 🙁

Main sections for HTC G1 (“dream_sapphire”)

1. Information about HTC G1 (“dream_sapphire”)
2. CyanogenMod install guide for HTC G1 (“dream_sapphire”)
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 froyo branch of CyanogenMod.

Notes

The HTC Dream is a slider touchscreen smartphone manufactured by HTC. The HTC Dream is also marketed as the T-Mobile G1 in multiple markets and the Era G1 in Poland. Official CyanogenMod support for the HTC Dream was added in CyanogenMod 3.1.

The HTC Magic (aka Sapphire) is a touchscreen smartphone manufactured by HTC. It is known as the T-Mobile myTouch 3G in the USA, the Rogers HTC Magic in Canada, and the DoCoMo HT-03A in Japan. Its hardware (RAM, processor, internal storage) are fundamentally identical to the HTC Dream, but the Magic gives up the physical keyboard in favor of a touchscreen version and it has larger storage memory (512 MB). As a result it is somewhat smaller, lighter and sleeker than the Dream. Official CyanogenMod support for the HTC Magic was added in CyanogenMod 3.1.

Source code

Device	http://www.github.com/cyanogenmod/android_device_htc_dream_sapphire
Kernel	http://www.github.com/cyanogenmod/android_kernel_htc_dream_sapphire

G1 Specifications

Codename:	dream_sapphire
Also known as:	Sapphire, MyTouch 3G, Rogers HTC Magic, DoCoMo HT-03A
Vendor:	HTC
Release date:	2008 October 22 (USA) 2009 February 5 (AUS) 2009 February 21 (SINGAPORE) 2009-06-0 (CAN)
Type:	phone
Platform:	Qualcomm MSM7201A
CPU:	528 MHz single-core Qualcomm
RAM:	192MB
Screen size:	81 mm (3.2 in)
Resolution:	480×320
Internal storage:	256MB
SD Card:	up to 16GB
Bluetooth:	2.0+EDR
Wi-Fi:	802.11b/g
Power:	1150 mAh internal rechargeable removable lithium-ion battery
Peripherals:	capacitive touchscreen display, QWERTY keyboard, trackball, volume controls, 3-axis accelerometer
CM supported:	6
Latest CM version:	froyo

How To Build CyanogenMod For HTC G1 (dream_sapphire)

Introduction

These instructions will hopefully assist you to start with a stock G1, 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 G1
• 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 G1 (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 froyo

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 dream_sapphire

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 G1 is connected to your computer via the USB cable and that you are in the ~/android/system/device/htc/dream_sapphire directory (you can cd ~/android/system/device/htc/dream_sapphire 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/htc 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 dream_sapphire

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/dream_sapphire/cm_dream_sapphire-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-6-20161224-UNOFFICIAL-dream_sapphire.zip, which is the CyanogenMod installation package.

Install CyanogenMod

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

cm-6-20161224-UNOFFICIAL-dream_sapphire.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 HTC myTouch 4G Slide (doubleshot)

Quick Info

Download CyanogenMod

It looks like we don’t have any roms for download for this device. 🙁

Main sections for HTC myTouch 4G Slide (“doubleshot”)

1. Information about HTC myTouch 4G Slide (“doubleshot”)
2. CyanogenMod install guide for HTC myTouch 4G Slide (“doubleshot”)
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 ics branch of CyanogenMod.

Special boot modes

• Recovery: Vol Down & Power

Source code

Device	http://www.github.com/cyanogenmod/android_device_htc_doubleshot
Kernel	http://www.github.com/cyanogenmod/htc-kernel-doubleshot

myTouch 4G Slide Specifications

Codename:	doubleshot
Also known as:	myTouch 4G Slide
Vendor:	HTC
Manufacturer:	HTC
Release date:	2011 July 26 (USA)
Carrier:	T-Mobile
Type:	phone (slider)
GSM freq:	850 900 1800 1900 MHz GSM/GPRS/EDGE 1700 2100 MHz UMTS/HSPA+
Platform:	Qualcomm MSM8260
CPU:	1.2 GHz dual-core Qualcomm Snapdragon S3
RAM:	768MB
Weight:	184 g (6.5 oz)
Dimensions:	122 mm (4.8 in) (h) 66 mm (2.6 in) (w) 14 mm (0.54 in) (d)
Screen size:	94 mm (3.7 in)
Resolution:	800×480
Screen density:	252 ppi
Screen type:	S-LCD
Internal storage:	4GB
SD Card:	up to 32GB
Bluetooth:	3.0+EDR w A2DP Stereo
Wi-Fi:	802.11b/g/n
Main camera:	8MP w/ dual LED flash
Secondary camera:	0.3MP
Power:	1520 mAh internal, rechargeable, removable lithium-ion battery
Peripherals:	micro-USB, A-GPS, FM Radio, capacitive touchscreen, proximity and ambient light sensors, volume controls, 3-axis accelerometer, digital compass, gyroscope
CM supported:	9
Latest CM version:	ics

How to Install CyanogenMod on the HTC myTouch 4G Slide (doubleshot)

Obtaining S-OFF and installing a custom recovery on the myTouch 4G Slide

Certain HTC devices can be exploited via a tool called Revolutionary to obtain S-OFF. The status of your device’s support can be checked at their site. Pay close attention to the HBOOT revision as newer updates break the tool’s ability to work properly. The Revolutionary tool will also install ClockworkMod Recovery.

Supported version(s) of HBOOT for the myTouch 4G Slide: 1.44.0007.

1. Windows Only: Download and install HTC USB drivers v3.0.0.007

   md5: f60771a86c4ad69c8c9c1d158e60e850

2. Disable Fast Boot on the myTouch 4G Slide (not to be confused with fastboot):

   Settings » Power » Fast Boot

   (or)

   Settings » Applications » Fast Boot

3. Enable USB debugging:

   Settings » Applications » Development » USB debugging

4. Connect the myTouch 4G Slide to the computer via USB
5. Find your device’s HBOOT version:

   From a command prompt or terminal, type: adb reboot bootloader

   If your HBOOT version is NOT 1.44.0007, you will need to downgrade. To downgrade your myTouch 4G Slide from Gingerbread (Including HBOOT 2.18) to Froyo, so you can root with unrEVOked v3.32 and gain RADIO S-OFF, follow this guide: [[1]]

6. Write down the serial number of the device:

   If at the bootloader: fastboot devices

   If Android is booted: adb devices

   Alternatively, the serial number can usually be found under the battery

7. Download Revolutionary 0.4pre4
8. Fill out the form on the Revolutionary site to get a beta key.
9. Once you have the beta key, launch the Revolutionary beta (you may need to launch it as root or administrator) and enter in the beta key minding that the key contains both upper- and lower-case letters.
10. Revolutionary will now attempt to temp-root your device, set S-OFF, and install a custom recovery image. The device will reboot on its own and the entire process should only take a few minutes. If the process takes longer than 15 minutes, reboot the device and attempt again. Some users have had to attempt S-OFF multiple times before achieving success.

NOTE: If you are unable to S-OFF your device, and it is listed as supported by Revolutionary, join the Revolutionary IRC channel for further assistance.

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.
   • Vol Down & Power
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 HTC myTouch 4G Slide (doubleshot)

Introduction

These instructions will hopefully assist you to start with a stock myTouch 4G Slide, 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 myTouch 4G Slide
• 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 myTouch 4G Slide (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 ics

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 doubleshot

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 myTouch 4G Slide is connected to your computer via the USB cable and that you are in the ~/android/system/device/htc/doubleshot directory (you can cd ~/android/system/device/htc/doubleshot 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/htc 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 doubleshot

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/doubleshot/cm_doubleshot-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-9-20161224-UNOFFICIAL-doubleshot.zip, which is the CyanogenMod installation package.

Install CyanogenMod

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

cm-9-20161224-UNOFFICIAL-doubleshot.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 HTC Eris (desirec)

Quick Info

Download CyanogenMod

It looks like we don’t have any roms for download for this device. 🙁

Main sections for HTC Eris (“desirec”)

1. Information about HTC Eris (“desirec”)
2. CyanogenMod install guide for HTC Eris (“desirec”)
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

• Recovery: Vol Down & Power

Source code

Device

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

Eris Specifications

Codename:	desirec
Vendor:	HTC
Manufacturer:	HTC
Release date:	2009 November 6 (USA)
Type:	phone
CDMA freq:	800 1900 MHz CDMA 2000 MHz 1xEV-DO
Platform:	Qualcomm MSM7600
CPU:	528 MHz single-core Qualcomm
RAM:	288MB
Weight:	120 g (4.2 oz)
Dimensions:	112 mm (4.4 in) (h) 56.2 mm (2.21 in) (w) 14.35 mm (0.565 in) (d)
Screen size:	81 mm (3.2 in)
Resolution:	480×320
Screen density:	180 ppi
Screen type:	TFT LCD
Internal storage:	512MB
SD Card:	yes
Bluetooth:	2.0+EDR w A2DP Stereo
Wi-Fi:	802.11b/g
Main camera:	5MP
Power:	1300 mAh internal, rechargeable, removable lithium-ion battery
Peripherals:	A-GPS, capacitive touchscreen, volume controls, proximity & ambient light sensors, 3-axis accelerometer, digital compass
CM supported:	7
Latest CM version:	gingerbread

How to Install CyanogenMod on the HTC Eris (desirec)

Installing a recovery image using flash_image

Use of the flash_image binary assumes your device already has root. For more detailed instructions on using the tools in this guide, please visit ADB.

1. Download the flash_image binary
   • flash_image: download or download older version (if you get Illegal Instruction)

     md5: bd475f29e0665c702f8eaf57a0423b58

2. Install the binary into /data/local on your phone via adb and set permissions
   • adb push flash_image /data/local/
   • adb shell chmod 777 /data/local/flash_image
3. Download koush’s ClockworkMod Recovery.
   • koush’s ClockworkMod Recovery: download

     md5: 31dae925bc707df266cac86569261e8d

4. Push the file(s) to your device via adb.
   • adb push yourrecoveryimage.img /data/local/
   • adb shell chmod 777 /data/local/yourrecoveryimage.img
   • adb shell rm /data/local/rights/mid.txt
   • adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
   • adb reboot

Wait for device to reboot fully.

Flash the recovery:

1. adb shell /data/local/flash_image recovery /data/local/yourrecoveryimage.img

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.
   • Vol Down & Power
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 HTC Eris (desirec)

Introduction

These instructions will hopefully assist you to start with a stock Eris, 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 Eris
• 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 Eris (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 gingerbread

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 Rom Manager

$ cd ~/android/system/vendor/cyanogen

then enter:

$ ./get-rommanager

You won’t see any confirmation- just another prompt. But this should cause the Rom Manager 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
$ lunch

You should see a list of devices, including something like cm_desirec-userdebug. Select it by typing its number. It is possible that lunch does not display your device. In that case try

$ lunch cm_desirec-userdebug

or

$ lunch full_desirec-userdebug

If all goes well, you should see that desirec-specific directories are downloaded automatically.

Extract proprietary blobs

Now ensure that your Eris is connected to your computer via the USB cable and that you are in the ~/android/system/device/htc/desirec directory (you can cd ~/android/system/device/htc/desirec 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/htc 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:

prebuilt/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 desirec

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/desirec/cm_desirec-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-7-20161224-UNOFFICIAL-desirec.zip, which is the CyanogenMod installation package.

Installing a recovery image using flash_image

Use of the flash_image binary assumes your device already has root. For more detailed instructions on using the tools in this guide, please visit ADB.

1. Download the flash_image binary
   • flash_image: download or download older version (if you get Illegal Instruction)

     md5: bd475f29e0665c702f8eaf57a0423b58

2. Install the binary into /data/local on your phone via adb and set permissions
   • adb push flash_image /data/local/
   • adb shell chmod 777 /data/local/flash_image
3. Download {{{install_devname}}}’s ClockworkMod Recovery.
   • {{{install_devname}}}’s ClockworkMod Recovery: [{{{install_file}}} download]

     md5: {{{install_md5sum}}}

4. Push the file(s) to your device via adb.
   • adb push yourrecoveryimage.img /data/local/
   • adb shell chmod 777 /data/local/yourrecoveryimage.img

Flash the recovery:

1. adb shell /data/local/flash_image recovery /data/local/yourrecoveryimage.img

Install CyanogenMod

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

cm-7-20161224-UNOFFICIAL-desirec.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 HTC Tattoo (click)

Quick Info

Download CyanogenMod

It looks like we don’t have any roms for download for this device. 🙁

Main sections for HTC Tattoo (“click”)

1. Information about HTC Tattoo (“click”)
2. CyanogenMod install guide for HTC Tattoo (“click”)
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

• Recovery: Home & Power

Source code

Device

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

Tattoo Specifications

Codename:	click
Vendor:	HTC
Manufacturer:	HTC
Release date:	2009 October (USA)
Type:	phone
GSM freq:	850 900 1800 1900 MHz GSM/GPRS/EDGE 900 2100 MHz UMTS/HSPA
Platform:	Qualcomm MSM7225
CPU:	528 MHz single-core Qualcomm
RAM:	256MB
Weight:	113 g (4 oz)
Dimensions:	106 mm (4.2 in) (h} 55 mm (2.17 in) (w) 14 mm (0.551 in) (d)
Screen size:	71 mm (2.8 in)
Resolution:	320×240
Screen density:	143 ppi
Screen type:	TFT LCD
Internal storage:	512MB
SD Card:	up to 32GB
Bluetooth:	2.0+EDR and A2DP
Wi-Fi:	802.11b/g
Main camera:	3.2MP
Power:	1100 mAh internal, rechargeable, removable lithium-ion battery
Peripherals:	micro-USB, A-GPS, FM Radio, resistive touchscreen, digital compass, 3-axis accelerometer
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_click-userdebug

$ lunch full_click-userdebug

$ ./extract-files.sh

export USE_CCACHE=1

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

$ croot
$ brunch click

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

$ cd $OUT

cm-7-20161224-UNOFFICIAL-click.zip

Cyanogenmod ROM HTC Desire (CDMA) (bravoc)

Quick Info

Download CyanogenMod

It looks like we don’t have any roms for download for this device. 🙁

Main sections for HTC Desire (CDMA) (“bravoc”)

1. Information about HTC Desire (CDMA) (“bravoc”)
2. CyanogenMod install guide for HTC Desire (CDMA) (“bravoc”)
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

• Recovery: Vol Down & Power then select recovery

Source code

Device

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

Desire (CDMA) Specifications

Codename:	bravoc
Vendor:	HTC
Manufacturer:	HTC
Release date:	2010 September 1 (USA)
Type:	phone
CDMA freq:	800 1900 MHz CDMA 2000 MHz 1xEV-DO
Platform:	Qualcomm QSD8650
CPU:	1 GHz single-core Qualcomm Snapdragon S1
RAM:	576MB
Weight:	135 g (4.8 oz)
Dimensions:	119 mm (4.7 in) (h) 60 mm (2.36 in) (w) 11.9 mm (0.47 in) (d)
Screen size:	94 mm (3.7 in)
Resolution:	800×480
Screen density:	252 ppi
Screen type:	AMOLED
Internal storage:	512MB
SD Card:	yes
Bluetooth:	2.1+EDR w A2DP Stereo
Wi-Fi:	802.11b/g
Main camera:	5MP
Power:	1400 mAh internal, rechargeable, removable lithium-ion battery
Peripherals:	micro-USB, A-GPS, FM Radio, capacitive touchscreen, digital compass, proximity and ambient light sensors, 3-axis accelerometer
CM supported:	7
Latest CM version:	gingerbread

How to Install CyanogenMod on the HTC Desire (CDMA) (bravoc)

Obtaining S-OFF and installing a custom recovery on the Desire (CDMA)

Certain HTC devices can be exploited via a tool called Revolutionary to obtain S-OFF. The status of your device’s support can be checked at their site. Pay close attention to the HBOOT revision as newer updates break the tool’s ability to work properly. The Revolutionary tool will also install ClockworkMod Recovery.

Supported version(s) of HBOOT for the Desire (CDMA): 1.06.0000.

1. Windows Only: Download and install HTC USB drivers v3.0.0.007

   md5: f60771a86c4ad69c8c9c1d158e60e850

2. Disable Fast Boot on the Desire (CDMA) (not to be confused with fastboot):

   Settings » Power » Fast Boot

   (or)

   Settings » Applications » Fast Boot

3. Enable USB debugging:

   Settings » Applications » Development » USB debugging

4. Connect the Desire (CDMA) to the computer via USB
5. Find your device’s HBOOT version:

   From a command prompt or terminal, type: adb reboot bootloader

   If your HBOOT version is NOT 1.06.0000, you will need to downgrade. To downgrade your Desire (CDMA) from Gingerbread (Including HBOOT 2.18) to Froyo, so you can root with unrEVOked v3.32 and gain RADIO S-OFF, follow this guide: [[1]]

6. Write down the serial number of the device:

   If at the bootloader: fastboot devices

   If Android is booted: adb devices

   Alternatively, the serial number can usually be found under the battery

7. Download Revolutionary 0.4pre4
8. Fill out the form on the Revolutionary site to get a beta key.
9. Once you have the beta key, launch the Revolutionary beta (you may need to launch it as root or administrator) and enter in the beta key minding that the key contains both upper- and lower-case letters.
10. Revolutionary will now attempt to temp-root your device, set S-OFF, and install a custom recovery image. The device will reboot on its own and the entire process should only take a few minutes. If the process takes longer than 15 minutes, reboot the device and attempt again. Some users have had to attempt S-OFF multiple times before achieving success.

NOTE: If you are unable to S-OFF your device, and it is listed as supported by Revolutionary, join the Revolutionary IRC channel for further assistance.

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.
   • Vol Down & Power then select recovery
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 HTC Desire (CDMA) (bravoc)

Introduction

These instructions will hopefully assist you to start with a stock Desire (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 Desire (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 Desire (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 gingerbread

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 Rom Manager

$ cd ~/android/system/vendor/cyanogen

then enter:

$ ./get-rommanager

You won’t see any confirmation- just another prompt. But this should cause the Rom Manager 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
$ lunch

You should see a list of devices, including something like cm_bravoc-userdebug. Select it by typing its number. It is possible that lunch does not display your device. In that case try

$ lunch cm_bravoc-userdebug

or

$ lunch full_bravoc-userdebug

If all goes well, you should see that bravoc-specific directories are downloaded automatically.

Extract proprietary blobs

Now ensure that your Desire (CDMA) is connected to your computer via the USB cable and that you are in the ~/android/system/device/htc/bravoc directory (you can cd ~/android/system/device/htc/bravoc 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/htc 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:

prebuilt/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 bravoc

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/bravoc/cm_bravoc-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-7-20161224-UNOFFICIAL-bravoc.zip, which is the CyanogenMod installation package.

Install CyanogenMod

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

cm-7-20161224-UNOFFICIAL-bravoc.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 HTC Desire HD / Inspire 4G (ace)

Quick Info

Download CyanogenMod

It looks like we don’t have any roms for download for this device. 🙁

Main sections for HTC Desire HD / Inspire 4G (“ace”)

1. Information about HTC Desire HD / Inspire 4G (“ace”)
2. CyanogenMod install guide for HTC Desire HD / Inspire 4G (“ace”)
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.

Notes

See the Advanced ACE Hack Kit for information about S-OFF.

Special boot modes

• Recovery: Vol Down & Power

Source code

Device

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

Desire HD / Inspire 4G Specifications

Codename:	ace
Also known as:	Desire HD, Inspire 4G
Vendor:	HTC
Release date:	2010 October 19 (EUR) 2011 February 13 (USA)
Type:	phone
GSM freq:	850 900 1800 1900 MHz GSM/GPRS/EDGE 900 2100 MHz UMTS/HSPA (EUR) 850 1900 MHz UMTS/HSPA+ (USA)
Platform:	Qualcomm MSM8255
CPU:	1 GHz single-core Snapdragon S2
GPU:	Qualcomm Adreno 205
RAM:	768MB
Weight:	164 g (5.8 oz)
Screen size:	109 mm (4.3 in)
Resolution:	800×480
Internal storage:	1.5GB
SD Card:	up to 32GB
Bluetooth:	2.1+EDR and A2DP
Wi-Fi:	802.11b/g/n
Main camera:	8MP w/ dual LED flash
Power:	1230 mAh Internal rechargeable removable lithium-ion battery
Peripherals:	capacitive touchscreen display, proximity and ambient light sensors, volume controls, 3-axis accelerometer, digital compass
CM supported:	7
Latest CM version:	gingerbread

How to Install CyanogenMod on the HTC Desire HD / Inspire 4G (ace)

Important Notes

See the Advanced ACE Hack Kit for information about S-OFF.

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 token:

   fastboot oem get_identifier_token

8. Visit the HTCDev Bootloader Unlock website and follow the instructions there to obtain your unlock key and unlock your bootloader. If your device does not appear in the drop-down list, select All Other Supported Models.
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 — visit twrp.me to obtain the latest version of Team Win Recovery Project for your device.
3. Connect the Desire HD / Inspire 4G 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: Vol 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. Boot to recovery mode, and connect the phone to your computer through USB.
   • Vol Down & Power
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 HTC Desire HD / Inspire 4G (ace)

Introduction

These instructions will hopefully assist you to start with a stock Desire HD / Inspire 4G, 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 Desire HD / Inspire 4G
• 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 Desire HD / Inspire 4G (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 gingerbread

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 Rom Manager

$ cd ~/android/system/vendor/cyanogen

then enter:

$ ./get-rommanager

You won’t see any confirmation- just another prompt. But this should cause the Rom Manager 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
$ lunch

You should see a list of devices, including something like cm_ace-userdebug. Select it by typing its number. It is possible that lunch does not display your device. In that case try

$ lunch cm_ace-userdebug

or

$ lunch full_ace-userdebug

If all goes well, you should see that ace-specific directories are downloaded automatically.

Extract proprietary blobs

Now ensure that your Desire HD / Inspire 4G is connected to your computer via the USB cable and that you are in the ~/android/system/device/htc/ace directory (you can cd ~/android/system/device/htc/ace 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/htc 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:

prebuilt/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 ace

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/ace/cm_ace-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-7-20161224-UNOFFICIAL-ace.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 Desire HD / Inspire 4G 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-7-20161224-UNOFFICIAL-ace.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 HTC One M9 Verizon (himawl)

Quick Info

Check out HTC One M9 (Verizon) (“himawl”) with newer LineageOS software

Download CyanogenMod

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

Main sections for HTC One M9 (Verizon) (“himawl”)

1. Information about HTC One M9 (Verizon) (“himawl”)
2. CyanogenMod install guide for HTC One M9 (Verizon) (“himawl”)
3. Build CyanogenMod and CyanogenMod Recovery guide

Notes

Note: Unlocking the bootloader.

To install CyanogenMod on this device, you must first unlock the bootloader or achieve s-off. The HTCdev.com bootloader unlock does not work on this device. Some alternative options are to use Sunshine or JavaCard.

Special boot modes

• Recovery: With the device powered down, hold the Volume Down and Power buttons until HBOOT appears, then release the buttons. Navigate using the volume keys and select RECOVERY using the Power key.
• Bootloader: With the device powered down, hold the Volume Down and Power buttons until HBOOT appears, then release the buttons.
• Fastboot: With the device powered down, hold the Volume Down and Power buttons until HBOOT appears, then release the buttons. Navigate using the volume keys and select FASTBOOT using the Power key.

Source code

Device	http://www.github.com/cyanogenmod/android_device_htc_himawl
Kernel	http://www.github.com/cyanogenmod/android_kernel_htc_msm8994

One M9 (Verizon) Specifications

Codename:	himawl
Vendor:	HTC
Release date:	2015 March
Type:	phone
GSM freq:	850, 900, 1800, 1900 MHz
CDMA freq:	850, 2100 MHz
Platform:	Qualcomm Snapdragon 810
CPU:	4 x 1.5 Ghz + 4 x 2 Ghz octa-core Cortex A53 & A57
GPU:	Adreno 430
RAM:	3GB
Weight:	157 g (5.54 oz)
Dimensions:	144.6 x 69.7 x 9.6 mm (5.69 x 2.74 x 0.38 in)
Screen size:	127 mm (5.0 in)
Resolution:	1080×1920
Screen density:	~441 ppi
Screen type:	Super LCD3
Internal storage:	32GB
SD Card:	up to 2TB
Bluetooth:	4.1
Wi-Fi:	802.11 a/b/g/n/ac (2.4 & 5 GHz)
Main camera:	20MP, flash: dual-LED
Secondary camera:	4MP
Power:	2840 mAh
CM supported:	13

How to Install CyanogenMod on the HTC One M9 (Verizon) (himawl)

Important Notes

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: ed05e466c549b42a2644aa6aaade46c5

3. Connect the One M9 (Verizon) 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: With the device powered down, hold the Volume Down and Power buttons until HBOOT appears, then release the buttons. Navigate using the volume keys and select RECOVERY using the Power key.
   • 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.
   • With the device powered down, hold the Volume Down and Power buttons until HBOOT appears, then release the buttons. Navigate using the volume keys and select RECOVERY using the Power key.
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 HTC One M9 (Verizon) (himawl)

Introduction

These instructions will hopefully assist you to start with a stock One M9 (Verizon), 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 One M9 (Verizon)
• 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 One M9 (Verizon) (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 himawl

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 One M9 (Verizon) is connected to your computer via the USB cable and that you are in the ~/android/system/device/htc/himawl directory (you can cd ~/android/system/device/htc/himawl 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/htc 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 himawl

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/himawl/cm_himawl-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-himawl.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 One M9 (Verizon) 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-himawl.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 HTC One A9 (GSM International) (hiaeuhl)

Quick Info

Check out HTC One A9 (GSM International) (“hiaeuhl”) with newer LineageOS software

Download CyanogenMod

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

Main sections for HTC One A9 (GSM International) (“hiaeuhl”)

1. Information about HTC One A9 (GSM International) (“hiaeuhl”)
2. CyanogenMod install guide for HTC One A9 (GSM International) (“hiaeuhl”)
3. Build CyanogenMod and CyanogenMod Recovery guide

Special boot modes

• Recovery: With the device powered down, hold the Volume Down and Power buttons until HBOOT appears, then release the buttons. Navigate using the volume keys and select RECOVERY using the Power key.
• Bootloader: With the device powered down, hold the Volume Down and Power buttons until HBOOT appears, then release the buttons.
• Fastboot: With the device powered down, hold the Volume Down and Power buttons until HBOOT appears, then release the buttons. Navigate using the volume keys and select FASTBOOT using the Power key.

Source code

Device	http://www.github.com/cyanogenmod/android_device_htc_hiaeuhl
Kernel	http://www.github.com/cyanogenmod/android_kernel_htc_msm8952

One A9 (GSM International) Specifications

Codename:	hiaeuhl
Vendor:	HTC
Release date:	2015 November
Type:	phone
Platform:	Qualcomm MSM8952 Snapdragon 617
CPU:	4 x 1.5 GHz, 4 x 1.2 GHz octa-core Cortex A53
GPU:	Adreno 405
RAM:	2/3GB
Weight:	143 g (5.04 oz)
Dimensions:	145.8 x 70.8 x 7.3 mm (5.74 x 2.79 x 0.29 in)
Screen size:	127 mm (5.0 in)
Resolution:	1080×1920
Screen density:	441 ppi
Screen type:	AMOLED
Internal storage:	16/32GB
SD Card:	up to 2TB
Bluetooth:	4.1
Wi-Fi:	802.11 a/b/g/n/ac (2.4 & 5 GHz)
Main camera:	13MP, flash: dual-LED
Secondary camera:	4MP
Power:	2150 mAh, Quick Charge 2.0
CM supported:	13, 14.1

How to Install CyanogenMod on the HTC One A9 (GSM International) (hiaeuhl)

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 token:

   fastboot oem get_identifier_token

8. Visit the HTCDev Bootloader Unlock website and follow the instructions there to obtain your unlock key and unlock your bootloader. If your device does not appear in the drop-down list, select All Other Supported Models.
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: beaefd4f6baadfb375ad67001a78c6d8

3. Connect the One A9 (GSM International) 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: With the device powered down, hold the Volume Down and Power buttons until HBOOT appears, then release the buttons. Navigate using the volume keys and select RECOVERY using the Power key.
   • 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.
   • With the device powered down, hold the Volume Down and Power buttons until HBOOT appears, then release the buttons. Navigate using the volume keys and select RECOVERY using the Power key.
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 HTC One A9 (GSM International) (hiaeuhl)

Introduction

These instructions will hopefully assist you to start with a stock One A9 (GSM International), 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 One A9 (GSM International)
• 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 One A9 (GSM International) (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 hiaeuhl

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 One A9 (GSM International) is connected to your computer via the USB cable and that you are in the ~/android/system/device/htc/hiaeuhl directory (you can cd ~/android/system/device/htc/hiaeuhl 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/htc 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 hiaeuhl

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/hiaeuhl/cm_hiaeuhl-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-hiaeuhl.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 One A9 (GSM International) 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-hiaeuhl.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 HTC One A9 (GSM US) (hiaeul)

Quick Info

Check out HTC One A9 (GSM US) (“hiaeul”) with newer LineageOS software

Download CyanogenMod

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

Main sections for HTC One A9 (GSM US) (“hiaeul”)

1. Information about HTC One A9 (GSM US) (“hiaeul”)
2. CyanogenMod install guide for HTC One A9 (GSM US) (“hiaeul”)
3. Build CyanogenMod and CyanogenMod Recovery guide

Special boot modes

• Recovery: With the device powered down, hold the Volume Down and Power buttons until HBOOT appears, then release the buttons. Navigate using the volume keys and select RECOVERY using the Power key.
• Bootloader: With the device powered down, hold the Volume Down and Power buttons until HBOOT appears, then release the buttons.
• Fastboot: With the device powered down, hold the Volume Down and Power buttons until HBOOT appears, then release the buttons. Navigate using the volume keys and select FASTBOOT using the Power key.

Source code

Device	http://www.github.com/cyanogenmod/android_device_htc_hiaeul
Kernel	http://www.github.com/cyanogenmod/android_kernel_htc_msm8952

One A9 (GSM US) Specifications

Codename:	hiaeul
Vendor:	HTC
Release date:	2015 November
Type:	phone
Platform:	Qualcomm MSM8952 Snapdragon 617
CPU:	4 x 1.5 GHz, 4 x 1.2 GHz octa-core Cortex A53
GPU:	Adreno 405
RAM:	2/3GB
Weight:	143 g (5.04 oz)
Dimensions:	145.8 x 70.8 x 7.3 mm (5.74 x 2.79 x 0.29 in)
Screen size:	127 mm (5.0 in)
Resolution:	1080×1920
Screen density:	441 ppi
Screen type:	AMOLED
Internal storage:	16/32GB
SD Card:	up to 2TB
Bluetooth:	4.1
Wi-Fi:	802.11 a/b/g/n/ac (2.4 & 5 GHz)
Main camera:	13MP, flash: dual-LED
Secondary camera:	4MP
Power:	2150 mAh, Quick Charge 2.0
CM supported:	13, 14.1

How to Install CyanogenMod on the HTC One A9 (GSM US) (hiaeul)

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 token:

   fastboot oem get_identifier_token

8. Visit the HTCDev Bootloader Unlock website and follow the instructions there to obtain your unlock key and unlock your bootloader. If your device does not appear in the drop-down list, select All Other Supported Models.
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: beaefd4f6baadfb375ad67001a78c6d8

3. Connect the One A9 (GSM US) 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: With the device powered down, hold the Volume Down and Power buttons until HBOOT appears, then release the buttons. Navigate using the volume keys and select RECOVERY using the Power key.
   • 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.
   • With the device powered down, hold the Volume Down and Power buttons until HBOOT appears, then release the buttons. Navigate using the volume keys and select RECOVERY using the Power key.
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 HTC One A9 (GSM US) (hiaeul)

Introduction

These instructions will hopefully assist you to start with a stock One A9 (GSM US), 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 One A9 (GSM US)
• 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 One A9 (GSM US) (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 hiaeul

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 One A9 (GSM US) is connected to your computer via the USB cable and that you are in the ~/android/system/device/htc/hiaeul directory (you can cd ~/android/system/device/htc/hiaeul 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/htc 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 hiaeul

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/hiaeul/cm_hiaeul-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-hiaeul.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 One A9 (GSM US) 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-hiaeul.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 HTC Desire 816 Dual SIM (a5dwg)

Quick Info

Download CyanogenMod

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

Main sections for HTC Desire 816 Dual SIM (“a5dwg”)

1. Information about HTC Desire 816 Dual SIM (“a5dwg”)
2. CyanogenMod install guide for HTC Desire 816 Dual SIM (“a5dwg”)
3. Build CyanogenMod and CyanogenMod Recovery guide

Special boot modes

• Recovery: With the device powered down, hold the Volume Down and Power buttons until HBOOT appears, then release the buttons. Navigate using the volume keys and select RECOVERY using the Power key.
• Bootloader: With the device powered down, hold the Volume Down and Power buttons until HBOOT appears, then release the buttons.
• Fastboot: With the device powered down, hold the Volume Down and Power buttons until HBOOT appears, then release the buttons. Navigate using the volume keys and select FASTBOOT using the Power key.

Source code

Device	http://www.github.com/cyanogenmod/android_device_htc_a5dwg
Kernel	http://www.github.com/cyanogenmod/android_kernel_htc_msm8974

Desire 816 Dual SIM Specifications

Codename:	a5dwg
Vendor:	HTC
Manufacturer:	HTC
Release date:	2014 April
Type:	phone
GSM freq:	GSM 850 / 900 / 1800 / 1900 HSDPA 850 / 900 / 2100
Platform:	Qualcomm MSM8226 Snapdragon 400
CPU:	1.6 GHz quad-core Cortex A7
GPU:	Adreno 305
RAM:	1.5GB
Weight:	165 g (5.82 oz)
Dimensions:	156.6 mm (6.17 in) x 78.7 mm (3.10 in) x 7.9 mm (0.31 in)
Screen size:	139.7 mm (5.5 in)
Resolution:	1280×720 pixels
Screen density:	~267 ppi
Screen type:	Super LCD2 capacitive touchscreen, 16M colors
Internal storage:	8GB
SD Card:	up to 128GB
Bluetooth:	v4.0 with A2DP, LE
Wi-Fi:	Wi-Fi 802.11 b/g/n, DLNA, Wi-Fi hotspot
Main camera:	13MP, flash: LED
Secondary camera:	5MP
Power:	2600 mAh
Peripherals:	Accelerometer, proximity, compass
CM supported:	13

How to Install CyanogenMod on the HTC Desire 816 Dual SIM (a5dwg)

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 token:

   fastboot oem get_identifier_token

8. Visit the HTCDev Bootloader Unlock website and follow the instructions there to obtain your unlock key and unlock your bootloader. If your device does not appear in the drop-down list, select All Other Supported Models.
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: 98c273cb3f919d5d99de9c6b071e1581

3. Connect the Desire 816 Dual SIM 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: With the device powered down, hold the Volume Down and Power buttons until HBOOT appears, then release the buttons. Navigate using the volume keys and select RECOVERY using the Power key.
   • 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.
   • With the device powered down, hold the Volume Down and Power buttons until HBOOT appears, then release the buttons. Navigate using the volume keys and select RECOVERY using the Power key.
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 HTC Desire 816 Dual SIM (a5dwg)

Introduction

These instructions will hopefully assist you to start with a stock Desire 816 Dual SIM, 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 Desire 816 Dual SIM
• 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 Desire 816 Dual SIM (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 a5dwg

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 Desire 816 Dual SIM is connected to your computer via the USB cable and that you are in the ~/android/system/device/htc/a5dwg directory (you can cd ~/android/system/device/htc/a5dwg 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/htc 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 a5dwg

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/a5dwg/cm_a5dwg-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-a5dwg.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 Desire 816 Dual SIM 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-a5dwg.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.