HTC Desire HD

cd work
mkdir bin
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > bin/repo
chmod a+x bin/repo
mkdir android/system
cd android/system/
repo init -u git://github.com/CyanogenMod/android.git -b ics

Before starting the long first sync, we need to add some extra repositories to the build as presently the Desire HD isn’t included “out of the box”.

Create a file, .repo/local_manifest.xml with the following contents

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <project name="CyanogenMod/android_device_htc_ace"
           path="device/htc/ace" remote="github" />
  <project name="CyanogenMod/android_device_htc_common"
           path="device/htc/common"
           revision="refs/heads/gingerbread"/>
  <project name="CyanogenMod/android_device_htc_msm7x30-common"
           path="device/htc/msm7x30-common" remote="github" />
  <project name="koush/proprietary_vendor_htc"
           path="vendor/htc" />
</manifest>

At this point the codebase will build but will not boot. To fix this, you need to edit the file device/htc/ace/media_profiles.xml as follows.

Insert @ line 77:
< !ATTLIST VideoEditorCap maxPrefetchYUVFrames CDATA #REQUIRED>
Change line 250 from
        maxOutputFrameHeight="720"/>
to
        maxOutputFrameHeight="720" maxPrefetchYUVFrames="10"/>

http://developer.android.com/sdk/index.html

$ cd ~/android/system/vendor/cyanogen
$ ./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.

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.

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 right place in the vendor directory.

Note:

It’s important that these proprietary files are properly extracted and moved to the vendor directory. Without them, CyanogenMod will build without error, but you’ll be missing important functionality, such as the ability to see anything!

If you want to speed up subsequent builds after this one, type:
$ export USE_CCACHE=1

Instead of typing cd ~/android/system every time you want to return back to the root of the source code, here’s a short command that will do it for you: croot . To use this command, as with brunch, you must first do “. build/envsetup.sh” from ~/android/system. Notice there is a period and space (“. ”) in that command.

$ croot
$ brunch ace

Helpful Tip

If the build doesn't start, try lunch and choose your device from the menu. If that doesn't work, try breakfast and choose from the menu. The command make ace should then work.

Helpful Tip

A second, bonus tip! If you get a command not found error for croot or brunch or lunch, be sure you’ve done the “ . build/envsetup.sh” command in this Terminal session from the ~/android/system directory.

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: $ system/build/tools/releasetools/common.py Change: java -Xmx2048m to java -Xmx1024m or java -Xmx512m

Then start the build again (with brunch).

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 ClockworkMod recovery, and (2) cm-[something].zip, which contains CyanogenMod.