HTC myTouch 3G Slide (espresso)

Cyanogenmod ROM HTC myTouch 3G Slide (espresso)

Quick Info

Download CyanogenMod

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

Main sections for HTC myTouch 3G Slide (“espresso”)

Information about HTC myTouch 3G Slide (“espresso”)
CyanogenMod install guide for HTC myTouch 3G Slide (“espresso”)
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_espresso

**myTouch 3G Slide Specifications**

Codename:	espresso
Vendor:	HTC
Manufacturer:	HTC
Release date:	2010 June 2 (USA)
Type:	phone (slider)
GSM freq:	850 900 1800 1900 MHz GSM/GPRS/EDGE 900 1700 2100 MHz UMTS/HSPA
Platform:	Qualcomm MSM7227
CPU:	600 MHz single-core Qualcomm
RAM:	512MB
Weight:	167 g (5.9 oz)
Dimensions:	114 mm (4.5 in) (h} 58 in (2.3 in) (w) 15 mm (0.6 in)
Screen size:	86 mm (3.4 in)
Resolution:	480×320
Screen density:	170 ppi
Screen type:	TFT LCD
Internal storage:	512MB
SD Card:	up to 32GB
Bluetooth:	2.1+EDR
Wi-Fi:	802.11b/g
Main camera:	5MP w/ LED flash
Power:	1300 mAh internal, rechargeable, removable lithium-ion battery
Peripherals:	A-GPS, capacitive touchscreen, volume controls, proximity and ambient light sensors, 3-axis accelerometer, physical keyboard
CM supported:	7
Latest CM version:	gingerbread

Note: DISCLAIMER

Modifying or replacing your device’s software may void your device’s warranty, lead to data loss, hair loss, financial loss, privacy loss, security breaches, or other damage, and therefore must be done entirely at your own risk. No one affiliated with the CyanogenMod project is responsible for your actions. Good luck.

1 Rooting & Installing a Custom Recovery on the myTouch Slide
2 Installing CyanogenMod from recovery

Rooting & Installing a Custom Recovery on the myTouch Slide

If the TMobile myTouch Slide is already rooted and has a custom recovery image skip this section.

In order to go through this process, you will need to create a goldcard.
You will need ADB on the computer to root the TMobile myTouch Slide. Follow the Android SDK guide, to get the ADB shell on the computer.
Download rageagainstthecage-arm5, flash_image, Engineering Recovery image, the ClockworkMod Recovery 2.5.0.7 update.zip & the 1.27.531.1 firmware:
- rageagainstthecage-arm5: Download
  
  md5: bfa28d457b54508326ab55d11399c586
- flash_image: Download
  
  md5: bd475f29e0665c702f8eaf57a0423b58
- Engineering Recovery image: Download
  
  md5: 14d4b30fb47225d7baabe7fe95386927
- the ClockworkMod Recovery 2.5.0.7 update.zip: Download
  
  md5: f18d1de25c35a3d50dd578a46c3f633d
- 1.27.531.1 firmware: Download
  
  md5: 9e80d53b4afa73ecf0d58f703831ac82
Unzip rageagainstthecage-arm5, flash_image, & the Engineering Recovery image to the same folder as ADB (the /platform-tools folder within the Android SDK folder).
With the Goldcard inserted in the TMobile myTouch Slide, rename the ClockworkMod Recovery update.zip to simply “update.zip” and copy it with the 1.27.531.1 firmware to the root of the SD card (NOT in any folders).
On the TMobile myTouch Slide we have to set several settings for this process to go smooth;
Connect the TMobile myTouch Slide to the computer via USB.
On the computer, open terminal and run the following commands:

adb push rageagainstthecage-arm5.bin /data/local/tmp/

adb shell

chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin

/data/local/tmp/rageagainstthecage-arm5.bin
Once the exploit finishes, in terminal, run the following commands:

exit

adb kill-server

adb start-server

adb push flash_image /data/local/

adb push recovery-engineering-espresso.img /data/local/mtd0.img

adb shell

cd /data/local

chmod 04755 *

/data/local/flash_image misc /data/local/mtd0.img
Once complete, power off the TMobile myTouch Slide.
Hold the Volume Down button while powering on until the device is in bootloader mode.
After a minute or so, the device will prompt to see if you want to run the update. Press the Volume Up button to accept & apply the update.

NOTE: The update will take a while to apply, just wait.

NOTE: If you get an error stating the update is older than version on the phone, there is an issue with the Goldcard you created.
Once the device is finished applying the update, it will ask you to reboot. DON’T reboot the device & press the Volume Down button to tell the device not to.
Back at the bootloader menu, use Volume Down to highlight Recovery and press the Power button to boot into the recovery.
Once in the recovery, you will see a device with a triangle. Press Volume Up & the Power button.
Use the Volume Down button to highlight Apply update.zip & press the Power button to select this.
After a moment, the TMobile myTouch Slide will boot into the ClockworkMod Recovery.

Installing CyanogenMod from recovery

Make sure your computer has working adb.
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.
Boot to recovery mode, and connect the phone to your computer through USB.
- Vol Down & Power
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.
Optional (Recommended): Select backup and restore to create a backup.
Select wipe data/factory reset.
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.
Once installation has finished, return to the main menu and select reboot system now. The device will now boot into CyanogenMod.

Helpful Tip – SD card folders

CyanogenMod 10.1 and newer have multi-user support (introduced in Android 4.2). If your device has storage on the /data partition, then Android actually looks in /data/media/0/ for the first user’s /sdcard/ storage. ClockworkMod recovery symlinks /sdcard/ to /data/media/ though. So, if you are pushing files to internal storage in recovery and want them to be visible in Android, you should push them to /sdcard/0/ or /data/media/0/. Here’s the most frequent scenarios:

If you’re coming from a ROM with Android 4.1 or older to CyanogenMod 10 or older: adb push update.zip /sdcard/
If you’re coming from a ROM with Android 4.1 or older to CyanogenMod 10.1 or newer: adb shell "mkdir /sdcard/0/" followed by adb push update.zip /sdcard/0/
If you’re coming from a ROM with Android 4.2 or newer to CyanogenMod 10.1 or newer: adb push update.zip /sdcard/0/

How To Build CyanogenMod For HTC myTouch 3G Slide (espresso)

Introduction

These instructions will hopefully assist you to start with a stock myTouch 3G 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 3G 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 3G 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.

Note:

You want to use a 64-bit version of Linux. A 32-bit Linux environment will only work if you are building CyanogenMod 6 and older. For CyanogenMod 10.1, if you encounter issues with 64bit host binaries, you can set BUILD_HOST_32bit=1 in your environment. This is generally not needed, though, especially with CyanogenMod 10.2 and newer.

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

Note:

You only need to do these steps the first time you build. If you previously prepared your build environment and have downloaded the CyanogenMod source code for another device, skip to Prepare the device-specific code.

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.

Helpful Tip

While the SDK contains lots of different things– the two tools you are most interested in for building Android are adb and fastboot, located in the /platform-tools directory.

Install the Build Packages

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

Helpful Tip

A package manager in Linux is a system used to install or remove software (usually originating from the Internet) on your computer. With Ubuntu, you can use the Ubuntu Software Center. Even better, you may also use the apt-get install command directly in the Terminal. (Learn more about the apt packaging tool system from Wikipedia.)

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:

Obtain OpenJDK 1.7 from the openjdk-r PPA
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.

Helpful Tip

The repo sync command is used to update the latest source code from CyanogenMod and Google. Remember it, as you can do it every few days to keep your code base fresh and up-to-date.

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_espresso-userdebug. Select it by typing its number. It is possible that lunch does not display your device. In that case try

$ lunch cm_espresso-userdebug

$ lunch full_espresso-userdebug

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

Helpful Tip

If you want to know more about what source build/envsetup.sh does or simply want to know more about the breakfast, brunch and lunch commands, you can head over to the Envsetup help page.

Helpful Tip

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, you must first run source build/envsetup.sh from ~/android/system.

Extract proprietary blobs

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

Note:

Your device should already be running a build of CyanogenMod for the branch you wish to build for the extract-files.sh script to function properly.

Note:

It’s important that these proprietary files are extracted to the ~/android/system/vendor/htc directory by using the extract-files.sh script. Makefiles are generated at the same time to make sure the blobs are eventually copied to the device. Without these blobs, CyanogenMod may build without error, but you’ll be missing important functionality, such as graphics libraries that enable you to see anything!

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.

Helpful Tip

If you are a very active developer, working on many other projects than just Android, you might prefer to keep your Android ccache independent (because it’s huge and can slow down the efficiency of ccache in your other projects). Beginning with CyanogenMod 12.1, you can specify environment variables for the location and size of CyanogenMod’s ccache. Some syntax examples: export ANDROID_CCACHE_DIR="$HOME/android/.ccache" and export ANDROID_CCACHE_SIZE="50G".

Start the build

Time to start building! So now type:

$ croot
$ brunch espresso

The build should begin.

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 espresso should then work.

Helpful Tip

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

Helpful Tip

A third tip! If the build to fails while downloading Gello, you’ll need to import a missing certificate into Maven’s truststore. Detailed instructions on how to do that can be found here

If the build breaks…

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

ERROR: signapk.jar failed: return code 1make: *** [out/target/product/espresso/cm_espresso-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-espresso.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-espresso.zip

Note:

The above file name may vary depending on the version of CM you are building. Your build may not include a version number or may identify itself as a “KANG” rather than UNOFFICIAL version. Regardless, the file name will end in .zip and should be titled similarly to official builds.

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.

Samsung Galaxy Tab 2 7.0 / Tab 2 10.1 (unified, GSM) (espresso3g)

Cyanogenmod ROM Samsung Galaxy Tab 2 7.0 / Tab 2 10.1 (unified, GSM) (espresso3g)

Quick Info

Check out Samsung Galaxy Tab 2 7.0 / Tab 2 10.1 (unified, GSM) (“espresso3g”) with newer LineageOS software

Download CyanogenMod

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

Main sections for Samsung Galaxy Tab 2 7.0 / Tab 2 10.1 (unified, GSM) (“espresso3g”)

Information about Samsung Galaxy Tab 2 7.0 / Tab 2 10.1 (unified, GSM) (“espresso3g”)
CyanogenMod install guide for Samsung Galaxy Tab 2 7.0 / Tab 2 10.1 (unified, GSM) (“espresso3g”)
Build CyanogenMod and CyanogenMod Recovery guide

Special boot modes

Recovery: Hold Power & Volume Down.
Download: Hold Power & Volume Up.

Source code

Device	http://www.github.com/cyanogenmod/android_device_samsung_espresso3g
Kernel	http://www.github.com/cyanogenmod/android_kernel_samsung_espresso10

**Galaxy Tab 2 7.0 / Tab 2 10.1 (unified, GSM) Specifications**

Codename:	espresso3g
Also known as:	P3100, P5100
Vendor:	Samsung
Manufacturer:	samsung
Type:	tablet
GSM freq:	Quad-band 850 900 1800 1900 MHz Quad-band 850 900 1900 2100 MHz HSPA+
Platform:	TI OMAP4430
CPU:	1 GHz dual-core OMAP4
GPU:	PowerVR SGX540
RAM:	1GB
Screen size:	178 mm (7.0 in) / 257 mm (10.1 in)
Resolution:	1024×600 (7.0 in) / 1280×800 (10.1 in)
Screen density:	169 PPI
Internal storage:	8/16/32GB
SD Card:	up to 32GB
Bluetooth:	3.0
Wi-Fi:	802.11 b/g/n
Main camera:	3.1MP
Secondary camera:	1.3MP
Power:	4000 mAh (7.0 in) / 7000 mAh (10.1 in) (Non-removable)
Peripherals:	capacitive touchscreen, proximity & light sensors, 3-axis accelerometer, additional 3-axis gyroscope, digital compass
CM supported:	13

How to Install CyanogenMod on the Samsung Galaxy Tab 2 7.0 / Tab 2 10.1 (unified, GSM) (espresso3g)

Note: DISCLAIMER

1 Installing a custom recovery
2 Installing CyanogenMod from recovery

Installing a custom recovery

Samsung devices come with a unique boot mode called Download Mode which is very similar to Fastboot Mode on some devices with unlocked bootloaders. Heimdall is a cross-platform, open source tool for interfacing with Download Mode on Samsung devices. The preferred method of installing a custom recovery is through this boot mode. Rooting the stock firmware is neither recommended nor necessary.

Download and install the Heimdall Suite
- Windows: Extract the Heimdall suite and take note of the directory holding heimdall.exe. You can verify Heimdall is working by opening a command prompt in this directory and typing heimdall version. If you receive an error, be sure that you have the Microsoft Visual C++ 2012 Redistributable Package (x86/32bit) installed on your computer.
- Linux: Pick the appropriate installation package based on your distribution. The -frontend packages are not required for this guide. After installation, heimdall should be available from the terminal; type heimdall version to verify installation succeeded.
- Mac: Install the dmg package. After installation, heimdall should be available from the terminal; type heimdall version to verify installation succeeded.
- Building from source: The source code for the Heimdall Suite is available on Github. For more details about how to compile the Heimdall Suite, please refer to the README file on Github under the relevant operating system directory. You can also refer to the Install and compile Heimdall instructions on this wiki.
Download recovery — you can directly download a recovery image using the link below, or visit TWRP site to check for the latest version of recovery for your device (if your device can be found there). For general info about recoveries click here.

Recovery: Download

md5: 341c4e467bcd65c9b9ad9339e7cac18d
Power off the Galaxy Tab 2 7.0 / Tab 2 10.1 (unified, GSM) and connect the USB adapter to the computer but not to the Galaxy Tab 2 7.0 / Tab 2 10.1 (unified, GSM), yet.
Boot the Galaxy Tab 2 7.0 / Tab 2 10.1 (unified, GSM) into download mode. Hold Power & Volume Up. Accept the disclaimer on the device. Then, insert the USB cable into the device.
Windows (only) driver installation – Skip this step if you are using Linux or Mac

A more complete set of the following instructions can be found in the Zadig User Guide.
1. Run zadig.exe from the Drivers folder of the Heimdall Suite.
2. Choose Options » List All Devices from the menu.
3. Select Samsung USB Composite Device or MSM8x60 or Gadget Serial or Device Name from the drop down menu. (If nothing relevant appears, try uninstalling any Samsung related Windows software, like Samsung Windows drivers and/or Kies).
4. Click Replace Driver (having selecting “Install Driver” from the drop down list built into the button).
5. If you are prompted with a warning that the installer is unable to verify the publisher of the driver, select Install this driver anyway. You may receive two more prompts about security. Select the options that allow you to carry on.
At this point, familiarize yourself with the Flashing with heimdall notes below so that you are prepared for any strange behaviour if it occurs.
On the computer, open a terminal (or Command Prompt on Windows) in the directory where the recovery image is located and type:

heimdall flash --RECOVERY recovery.img --no-reboot

Tip: The file may not be named identically to what’s in this command. If the file is wrapped in a zip or tar file, extract the file first, because heimdall isn’t going to do it for you.
A blue transfer bar will appear on the device showing the recovery being transferred.
Unplug the USB cable from your device.
- NOTE: Be sure to reboot into recovery immediately after having installed the custom recovery. Otherwise the custom recovery will be overwritten and the device will reboot (appearing as though your custom recovery failed to install).
Manually reboot the phone into recovery mode by performing the following. Hold Power & Volume Down.
The Galaxy Tab 2 7.0 / Tab 2 10.1 (unified, GSM) now has a custom recovery installed. Continue to the next section.

Note: Flashing with heimdall

In Windows 7 UAC (User Account Control) may need switching off. Once Heimdall is finished it can be re-enabled.
Protocol initialization can fail if the device is connected via a USB hub – connect the USB cable directly to the PC
It may be necessary to run the heimdall flash command as root in Linux or Mac OS X: sudo heimdall flash [...]. Typical symptoms of this are:
- a blue bar doesn’t show up after the process has finished
- Failed to confirm end of file transfer sequence!
It may be necessary to capitalize the name of the partition on some devices. Try --KERNEL instead of --kernel and/or --recovery instead of --RECOVERY.
If on Linux 64bit you get “unable to execute ./heimdall: No such file or directory”, try the 32bit version and make sure to run it with sudo: reference.
On Mac OS X you may see this message: “ERROR: Claiming interface failed!”. If so, you need to disable the default USB drivers with the following commands:
sudo kextunload -b com.apple.driver.AppleUSBCDC;
sudo kextunload -b com.apple.driver.AppleUSBCDCACMControl;
sudo kextunload -b com.apple.driver.AppleUSBCDCACMData;
If you have installed Samsung Kies, you may further need to unload those USB drivers with the following commands:
sudo kextunload -b com.devguru.driver.SamsungComposite;
sudo kextunload -b com.devguru.driver.SamsungACMData
sudo kextunload -b com.devguru.driver.SamsungACMControl
Using Heimdall version 1.4.0 (the latest version available for download on the Glass Echidna website) you may see this message or one similar to it:
Error: Failed to confirm end of PIT file transfer!
If you experience this error, follow the instructions for compiling Heimdall from source to get the latest version on GitHub with the issue patched.

Helpful Tip

The stock ROM may overwrite your custom recovery on boot. To prevent this, boot immediately into recovery after leaving Download Mode instead of letting the ROM boot up normally. If your recovery is overwritten, simply redo the steps you followed above and catch it before it boots next time.
Note for upgrades from gingerbread to jellybean remember the recovery is changed. This means once you install do NOT restore to old-gingerbread-stock ROM from cwm-recovery.
To upgrade from stock/CM7/CM9/CM10.1.2/CM10.1.3 to CM10.2, you must first boot into recovery and wipe data, cache, and dalvik cache (factory reset). Due to the new partition layout in CM10.2, failing to perform these steps will result in a bootloop. See here for details; more about repartitioning here. If you missed this step before installing, boot to recovery and factory reset, then reinstall CM10.2.
Some users have reported connection errors if the device is connected to a USB hub. If you experience such errors it is recommended that you try connecting your device to a USB port on the motherboard.
Antivirus software may prevent Heimdall from connecting properly. Disable your antivirus before proceeding.
When Heimdall fails to connect, the Download mode may get stuck, making all further attempts fail too. To retry, you may need to restart the Download mode: turn off the phone by holding Power for 5-10 seconds (or by pulling out the battery), then boot into Download mode and run Heimdall again.
If Heimdall fails to connect (errors related to initializing the protocol, or transferring data):

if you just installed the driver, try rebooting your computer and trying again.

if you still have troubles after reboot, in Zadig try installing the libusbK driver rather than the WinUSB driver.

Installing CyanogenMod from recovery

Make sure your computer has working adb.
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.
Boot to recovery mode, and connect the phone to your computer through USB.
- Hold Power & Volume Down.
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.
Optional (Recommended): Select backup and restore to create a backup.
Select wipe data/factory reset.
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.
Once installation has finished, return to the main menu and select reboot system now. The device will now boot into CyanogenMod.

Helpful Tip – SD card folders

If you’re coming from a ROM with Android 4.1 or older to CyanogenMod 10 or older: adb push update.zip /sdcard/
If you’re coming from a ROM with Android 4.1 or older to CyanogenMod 10.1 or newer: adb shell "mkdir /sdcard/0/" followed by adb push update.zip /sdcard/0/
If you’re coming from a ROM with Android 4.2 or newer to CyanogenMod 10.1 or newer: adb push update.zip /sdcard/0/

Helpful Tip

See something wrong on this page? Click here: Report a Site Problem.

How To Build CyanogenMod For Samsung Galaxy Tab 2 7.0 / Tab 2 10.1 (unified, GSM) (espresso3g)

Introduction

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

What you’ll need

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

Note:

So let’s begin!

Build CyanogenMod and CyanogenMod Recovery

Prepare the Build Environment

Note:

Install the SDK

Helpful Tip

While the SDK contains lots of different things– the two tools you are most interested in for building Android are adb and fastboot, located in the /platform-tools directory.

Install the Build Packages

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

Helpful Tip

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:

Obtain OpenJDK 1.7 from the openjdk-r PPA
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

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

Helpful Tip

The repo sync command is used to update the latest source code from CyanogenMod and Google. Remember it, as you can do it every few days to keep your code base fresh and up-to-date.

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

Helpful Tip – Errors during breakfast

Different maintainers setup their device inheritance rules differently. Some require a vendor directory to be populated before breakfast will even succeed. If you receive an error here about vendor makefiles, then jump down to the next section Extract proprietary blobs. The first portion of breakfast should have succeeded at pulling in the device tree and the extract blobs script should be available. After completing that section, you can rerun breakfast espresso3g

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

$ source build/envsetup.sh
$ breakfast espresso3g

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.

Helpful Tip

If you want to know more about what source build/envsetup.sh does or simply want to know more about the breakfast, brunch and lunch commands, you can head over to the Envsetup help page.

Helpful Tip

Extract proprietary blobs

Now ensure that your Galaxy Tab 2 7.0 / Tab 2 10.1 (unified, GSM) is connected to your computer via the USB cable and that you are in the ~/android/system/device/samsung/espresso3g directory (you can cd ~/android/system/device/samsung/espresso3g 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/samsung 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.

Note:

Your device should already be running a build of CyanogenMod for the branch you wish to build for the extract-files.sh script to function properly.

Note:

It’s important that these proprietary files are extracted to the ~/android/system/vendor/samsung directory by using the extract-files.sh script. Makefiles are generated at the same time to make sure the blobs are eventually copied to the device. Without these blobs, CyanogenMod may build without error, but you’ll be missing important functionality, such as graphics libraries that enable you to see anything!

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

Helpful Tip

Start the build

Time to start building! So now type:

$ croot
$ brunch espresso3g

The build should begin.

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 espresso3g should then work.

Helpful Tip

A third tip! If the build to fails while downloading Gello, you’ll need to import a missing certificate into Maven’s truststore. Detailed instructions on how to do that can be found here

If the build breaks…

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

ERROR: signapk.jar failed: return code 1make: *** [out/target/product/espresso3g/cm_espresso3g-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

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-espresso3g.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-13.0-20161224-UNOFFICIAL-espresso3g.zip

Note:

Success! So….what’s next?

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

Congrats again!

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

Barnes & Noble Nook Color (encore)

Cyanogenmod ROM Barnes & Noble Nook Color (encore)

Quick Info

Download CyanogenMod

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

Main sections for Barnes & Noble Nook Color (“encore”)

Information about Barnes & Noble Nook Color (“encore”)
CyanogenMod install guide for Barnes & Noble Nook Color (“encore”)
Build CyanogenMod and CyanogenMod Recovery guide

Notes

The Barnes & Noble Nook Color (aka encore) is a touchscreen tablet manufactured by Barnes & Noble. Official CyanogenMod support for the Barnes & Noble Nook Color was added in CyanogenMod 7.

Source code

Device	http://www.github.com/cyanogenmod/android_device_bn_encore
Kernel	http://www.github.com/cyanogenmod/android_kernel_bn_encore

**Nook Color Specifications**

Codename:	encore
Vendor:	Barnes & Noble
Type:	tablet
Platform:	TI OMAP3621
CPU:	800 MHz single-core Cortex-A8
GPU:	Imagination Technology PowerVR SGX530
RAM:	512MB
Weight:	448 g (15.8 oz)
Dimensions:	206 mm (8.1 in) (h) 127 mm (5 in) (w) 12 mm (0.48 in) (d)
Screen size:	178 mm (7.0 in)
Resolution:	1024×600 (WSVGA)
Screen type:	IPS LCD
Internal storage:	8GB
SD Card:	up to 32GB
Wi-Fi:	802.11b/g/n
Power:	4000 mAh internal rechargeable non-removable lithium-ion polymer battery
Peripherals:	capacitive touchscreen display, 3-axis accelerometer
CM supported:	7, 10, 10.1, 10.2, 11

How to Install CyanogenMod on the Barnes & Noble Nook Color (encore)

Note: DISCLAIMER

1 Important Notes
- 1.1 Setting up uNooter
- 1.2 Gaining Root Access
2 Install a Custom Recovery Image
3 Installing CyanogenMod from recovery
4 Alternative ClockworkMod Recovery installation

Important Notes

The Barnes & Noble Nook Color (aka encore) is a touchscreen tablet manufactured by Barnes & Noble. Official CyanogenMod support for the Barnes & Noble Nook Color was added in CyanogenMod 7.

Setting up uNooter

In order to properly flash an uNooter image to a SD card, you will need to use an USB card adapter or have an internal SD card slot on the computer. Writing the uNooter image to the SD card will wipe it, backup anything of value and/or importance elsewhere.

Download the uNooter image:
- uNooter: Download
  
  md5: 4e1e7be9939aaef43d3a1d04cb17b2cd
Unzip the uNooter zipfile.
Write the uNooter image to the SD card:

Windows

Due to Windows not having the ability to write images to drives, you will need win32DiskImager to accomplish this. Latest version should be fine.
Insert the SD card you are going to use to write the uNooter image to.
Open win32DiskImager.
Select the downloaded & extracted uNooter image with the folder button.
Select the drive letter for the SD card.
Write the uNooter image.

Linux

Insert the SD card you are going to use to write the uNooter image to.
On the computer, open up terminal and navigate the directory where the extracted uNooter image is located.
Once in the same directory as the uNooter image, type the following commands:

umount /dev/<sdcard>

NOTE: <sdcard> is the device file associated with the SD card, e.g., sdc or mmcblk0, and NOT the mount point, e.g., sdc1 or mmcblk0p1.

dd if=uNooter.img of=/dev/<sdcard> bs=1M

Mac OS X

Insert the SD card you are going to use to write the uNooter image to.
On the computer, open up terminal and navigate the directory where the extracted uNooter image is located.
Once in the same directory as the uNooter image, type the following commands:

diskutil list

NOTE: This will help you identify the SD card. Make sure it is the SD card & not one of the hard drives of the computer.

diskutil unmountDisk /dev/<sdcard>

NOTE: <sdcard> is the device file associated with the SD card, e.g. disk2.

dd if=uNooter.img of=/dev/<sdcard> bs=1m

The uNooter image is now setup on the SD card. Continue to the next section.

Gaining Root Access

Power off the Barnes & Noble Nook Color. Also if the device is connected to a computer, disconnect it.
Insert the newly setup uNooter SD card into the Barnes & Noble Nook Color.
Connect the Barnes & Noble Nook Color to the computer. This will trigger the Barnes & Noble Nook Color to power on (the screen will remain off) and allow uNooter to root the device. This screen is black for up to ten minutes.
The computer will see a new USB device.
- Windows: The computer may complain about missing drivers. Simply cancel through them at this time.
- Linux: The Barnes & Noble Nook Color will show up the computer as a RNDIS ethernet device. You may ignore this.
- Mac OS X: The Barnes & Noble Nook Color will show up as an additional Ethernet device. Just cancel when you see the dialog box pop up.
Once this occurs, disconnect the Barnes & Noble Nook Color from the computer. The Barnes & Noble Nook Color may restart itself. If it restarts normal, continue to the next step. If it does not, power it off, remove the SD card & power it back on normal.
At this point the Barnes & Noble Nook Color is rooted. Continue to the next section.

Install a Custom Recovery Image

If the Nook Color already has the ClockworkMod Recovery installed, you may skip this section.

In the Extras menu on the Barnes & Noble Nook Color, launch ROM Manager.
Select Flash ClockworkMod Recovery.
Click on Barnes & Noble Nook Color and then give ROM Manager root permission, if it prompts you.
If it hangs after that and freezes up, just allow the app to Force Close. Then open it back up and repeat steps 2-4.
Once the flash was successful, you should see a dialog box that says “Successfully flashed ClockworkMod recovery!”.
Press OK.
The ClockworkMod Recovery should now be installed on the Barnes & Noble Nook Color.

Installing CyanogenMod from recovery

Make sure your computer has working adb.
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.
Boot to recovery mode, and connect the phone to your computer through USB.

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.
Optional (Recommended): Select backup and restore to create a backup.
Select wipe data/factory reset.
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.
Once installation has finished, return to the main menu and select reboot system now. The device will now boot into CyanogenMod.

Helpful Tip – SD card folders

If you’re coming from a ROM with Android 4.1 or older to CyanogenMod 10 or older: adb push update.zip /sdcard/
If you’re coming from a ROM with Android 4.1 or older to CyanogenMod 10.1 or newer: adb shell "mkdir /sdcard/0/" followed by adb push update.zip /sdcard/0/
If you’re coming from a ROM with Android 4.2 or newer to CyanogenMod 10.1 or newer: adb push update.zip /sdcard/0/

Helpful Tip

See something wrong on this page? Click here: Report a Site Problem.

Alternative ClockworkMod Recovery installation

ClockworkMod Recovery installation on Nook Color (encore) does not work through ROM Manager.
Last version of Rom Manager and ClockworkMod does not support Nook. It could be checked by observing ROM manager page.

The working solution to the September, 2014 is to download image of ClockworkMod and write it to SD card as described in Setting up uNooter section. Setting up uNoter is not required. Note: this will destroy all information on SD card!!! CWM-6.0.1.2 SD image could be found on xda-developers on the post bottom download

After this step you should install CyanogenMod, as it will install “Universal” bootloader, which can boot to CM or CWM recovery. Stock bootloader ignore any keys combination. It boot from SD card if bootable one available, or from internal memory.

The latest version of ClockworkMod is 6.0.4.8 and is found in this post. link. This one is not a SD image!
It could be downloaded to SD card (as a zip file) and installed throw available CWM recovery. Boot to the recovery by pressing nook n key. Than choose “install zip from sd card”.

CyanogenMod should be installed through the same “install zip from sd card” method. Download suitable CyanogenMod package and [Google_Apps Google apps] package to the SD card. For CM 11 use 20140105 version, only this one have a “Google Play” service in my case. Alternatively, you can download minimalistic GApps

If your Nook shows SystemUI failed message, boot to the CWM recovery and make a date/factory reset wipe.

How To Build CyanogenMod For Barnes & Noble Nook Color (encore)

Introduction

These instructions will hopefully assist you to start with a stock Nook Color, 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.

What you’ll need

A Nook Color
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 Nook Color (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.

Note:

So let’s begin!

Build CyanogenMod and CyanogenMod Recovery

Prepare the Build Environment

Note:

Install the SDK

Helpful Tip

While the SDK contains lots of different things– the two tools you are most interested in for building Android are adb and fastboot, located in the /platform-tools directory.

Install the Build Packages

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

Helpful Tip

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:

Obtain OpenJDK 1.7 from the openjdk-r PPA
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

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

Helpful Tip

The repo sync command is used to update the latest source code from CyanogenMod and Google. Remember it, as you can do it every few days to keep your code base fresh and up-to-date.

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

Helpful Tip – Errors during breakfast

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

$ source build/envsetup.sh
$ breakfast encore

Helpful Tip

If you want to know more about what source build/envsetup.sh does or simply want to know more about the breakfast, brunch and lunch commands, you can head over to the Envsetup help page.

Helpful Tip

Extract proprietary blobs

Now ensure that your Nook Color is connected to your computer via the USB cable and that you are in the ~/android/system/device/bn/encore directory (you can cd ~/android/system/device/bn/encore 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/bn 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.

Note:

Your device should already be running a build of CyanogenMod for the branch you wish to build for the extract-files.sh script to function properly.

Note:

It’s important that these proprietary files are extracted to the ~/android/system/vendor/bn directory by using the extract-files.sh script. Makefiles are generated at the same time to make sure the blobs are eventually copied to the device. Without these blobs, CyanogenMod may build without error, but you’ll be missing important functionality, such as graphics libraries that enable you to see anything!

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

Helpful Tip

Start the build

Time to start building! So now type:

$ croot
$ brunch encore

The build should begin.

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 encore should then work.

Helpful Tip

A third tip! If the build to fails while downloading Gello, you’ll need to import a missing certificate into Maven’s truststore. Detailed instructions on how to do that can be found here

If the build breaks…

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

ERROR: signapk.jar failed: return code 1make: *** [out/target/product/encore/cm_encore-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

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-encore.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-13.0-20161224-UNOFFICIAL-encore.zip

Note:

Success! So….what’s next?

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

Congrats again!

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

LG Optimus Sol (e730)

Cyanogenmod ROM LG Optimus Sol (e730)

Quick Info

Download CyanogenMod

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

Main sections for LG Optimus Sol (“e730”)

Information about LG Optimus Sol (“e730”)
CyanogenMod install guide for LG Optimus Sol (“e730”)
Build CyanogenMod and CyanogenMod Recovery guide

Note: Support Status

Source code

Device	http://www.github.com/cyanogenmod/android_device_lge_e730
Kernel	http://www.github.com/cyanogenmod/android_kernel_lge_e730

**Optimus Sol Specifications**

Codename:	e730
Vendor:	LG
Manufacturer:	LG
Type:	phone
GSM freq:	GSM 850 / 900 / 1800 / 1900 HSDPA 900 / 2100
Platform:	Qualcomm MSM8255
CPU:	1 GHz single-core Scorpion Snapdragon
GPU:	Adreno 205
RAM:	512MB
Weight:	110 g (3.88 oz)
Dimensions:	122.5 x 62.5 x 9.8 mm (4.82 x 2.46 x 0.39 in)
Screen size:	97 mm (3.8 in)
Resolution:	480×800
Screen density:	246 ppi
Internal storage:	1GB
SD Card:	up to 32GB
Bluetooth:	3.0
Wi-Fi:	802.11 b/g/n
Main camera:	5MP
Secondary camera:	VGA
Power:	Li-Ion 1500 mAh battery
Peripherals:	Accelerometer, proximity, compass
CM supported:	7, 9
Latest CM version:	ics

How to Install CyanogenMod on the LG Optimus Sol (e730)

Note: DISCLAIMER

1 Installing CyanogenMod from recovery
2 How to root your phone
3 How to install ClockWorkMod-Recovery
4 How to start in CWM-Recovery
5 How to install Cyanogenmod

Installing CyanogenMod from recovery

Make sure your computer has working adb.
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.
Boot to recovery mode, and connect the phone to your computer through USB.

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.
Optional (Recommended): Select backup and restore to create a backup.
Select wipe data/factory reset.
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.
Once installation has finished, return to the main menu and select reboot system now. The device will now boot into CyanogenMod.

Helpful Tip – SD card folders

If you’re coming from a ROM with Android 4.1 or older to CyanogenMod 10 or older: adb push update.zip /sdcard/
If you’re coming from a ROM with Android 4.1 or older to CyanogenMod 10.1 or newer: adb shell "mkdir /sdcard/0/" followed by adb push update.zip /sdcard/0/
If you’re coming from a ROM with Android 4.2 or newer to CyanogenMod 10.1 or newer: adb push update.zip /sdcard/0/

Helpful Tip

See something wrong on this page? Click here: Report a Site Problem.

How to root your phone

Required software:

– LG USB-driver (you can get the driver for your e730 on the lg website)

– SuperOneClick (Software for rooting your device. This instruction has been tested with version 2.3.3)

1. Download the required software

2. Install LG USB-driver on your pc

3. You have to enable following settings in your phone

Settings >> Applications >> Unknown sources

Settings >> Applications >> Development >> USB-Debugging

4. Connect your phone via USB to your pc. Your pc should start the driver installation automatically. Wait until the installation is finished.

5. Start “SuperOneClick.exe”. If you have downloaded a zip.-file, unzip it in a new folder first.

6. Important: If you use a firewall on your pc, your firewall has to accept the access from “adb.exe”.

7. Accept the disclaimer and choose “root” (it is the upper left button).

8. Root-process starts. Wait until it is finished. When finished, your phone should restart and you will find the app “super-user” on your phone.

Origin of this instruction (it is in german language)

How to install ClockWorkMod-Recovery

Important: You need internet access on your phone. Some data will be downloaded during installation.

1. Install the App “RomManager” (free version is sufficient) on your phone.

2. Start the app and jump the registration and advertisement until you get to the main page.

3. Click “Install ClockWorkMod Recovery”

4. Look for your phone (Optimus Sol) in the next menu and click “OK”. Follow the installation instructions. During this process there will be a super-user request by the RomManager. You have to allow this request.

5. After successful installation you will find on the main page of this app (RomManager) the current installed version of CWM-Recovery.

Origin of this instruction (it is in german language)

How to start in CWM-Recovery

You can choose between these two possibilities:

Variant 1:

Start the app “RomManager” and choose the entry “Restart into recovery”.

Variant 2:

Switch off your phone and start by pressing the Volume-down AND Power-button. Keep them pressed until you see the CWM-Recovery.

To navigate in recovery-menu:

Down: Volume down (-)

Up: Volume up (+)

Confirm/Select: Power-button

How to install Cyanogenmod

Important: Your phone should be fully charged!

Installing CM for the first time:

1. Download CyanogenMod and copy the zip.file to the sd-card of your phone (/sdcard).

2. Execute the following steps consecutively:

Start the optimus sol in CWM-recovery-mode

Select Backup and restore > Backup (safe your system)

Select wipe data/factory reset (confirm with Yes)

Select wipe cache partition (confirm with Yes)

Select advanced

Select Wipe Dalvik Cache (confirm with Yes)

Select Wipe Battery Stats (confirm with Yes)

Select ++++Go Back+++++++

Select install zip from sdcard

Select choose zip frome sdcard

Select your downloaded version of cyanogenmod and confirm your choice with “***YES***”. The installation starts.

Select +++++Go Back+++++

Select reboot system now

3. Finished

Update-Installation:

With an update-installation all user data and apps are kept.

1. Download CyanogenMod and copy the zip.file to the sd-card of your phone (/sdcard).

2. Execute the following steps consecutively:

Start the optimus sol in CWM-recovery-mode

Select Backup and restore > Backup (safe your system)

Select advanced

Select Wipe Dalvik Cache (confirm with Yes)

Select Wipe Battery Stats (confirm with Yes)

Select ++++Go Back+++++++

Select install zip from sdcard

Select choose zip frome sdcard

Select your downloaded version of cyanogenmod and confirm your choice with “***YES***”. The installation starts.

Select +++++Go Back+++++

Select reboot system now

3. Finished

Origin of this instruction (it is in german language)

How To Build CyanogenMod For LG Optimus Sol (e730)

Introduction

These instructions will hopefully assist you to start with a stock Optimus Sol, 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.

What you’ll need

A Optimus Sol
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 Optimus Sol (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.

Note:

So let’s begin!

Build CyanogenMod and CyanogenMod Recovery

Prepare the Build Environment

Note:

Install the SDK

Helpful Tip

While the SDK contains lots of different things– the two tools you are most interested in for building Android are adb and fastboot, located in the /platform-tools directory.

Install the Build Packages

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

Helpful Tip

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:

Obtain OpenJDK 1.7 from the openjdk-r PPA
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

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

Helpful Tip

The repo sync command is used to update the latest source code from CyanogenMod and Google. Remember it, as you can do it every few days to keep your code base fresh and up-to-date.

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

Helpful Tip – Errors during breakfast

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

$ source build/envsetup.sh
$ breakfast e730

Helpful Tip

If you want to know more about what source build/envsetup.sh does or simply want to know more about the breakfast, brunch and lunch commands, you can head over to the Envsetup help page.

Helpful Tip

Extract proprietary blobs

Now ensure that your Optimus Sol is connected to your computer via the USB cable and that you are in the ~/android/system/device/lge/e730 directory (you can cd ~/android/system/device/lge/e730 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/lge 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.

Note:

Your device should already be running a build of CyanogenMod for the branch you wish to build for the extract-files.sh script to function properly.

Note:

It’s important that these proprietary files are extracted to the ~/android/system/vendor/lge directory by using the extract-files.sh script. Makefiles are generated at the same time to make sure the blobs are eventually copied to the device. Without these blobs, CyanogenMod may build without error, but you’ll be missing important functionality, such as graphics libraries that enable you to see anything!

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

Helpful Tip

Start the build

Time to start building! So now type:

$ croot
$ brunch e730

The build should begin.

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 e730 should then work.

Helpful Tip

A third tip! If the build to fails while downloading Gello, you’ll need to import a missing certificate into Maven’s truststore. Detailed instructions on how to do that can be found here

If the build breaks…

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

ERROR: signapk.jar failed: return code 1make: *** [out/target/product/e730/cm_e730-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

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-e730.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-e730.zip

Note:

Success! So….what’s next?

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

Congrats again!

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

LG Optimus Hub (e510)

Cyanogenmod ROM LG Optimus Hub (e510)

Quick Info

Download CyanogenMod

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

Main sections for LG Optimus Hub (“e510”)

Information about LG Optimus Hub (“e510”)
CyanogenMod install guide for LG Optimus Hub (“e510”)
Build CyanogenMod and CyanogenMod Recovery guide

Note: Support Status

Source code

Device

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

**Optimus Hub Specifications**

Codename:	e510
Vendor:	LG
Manufacturer:	LG
Type:	phone
GSM freq:	GSM 850 / 900 / 1800 / 1900 HSDPA 900 / 2100
Platform:	Qualcomm MSM7227T
CPU:	800 MHz single-core ARM v6
GPU:	Adreno 200
RAM:	512MB
Weight:	123 g (4.34 oz)
Dimensions:	113.4 x 60.8 x 11.9 mm (4.46 x 2.39 x 0.47 in)
Screen size:	89 mm (3.5 in)
Resolution:	320×480
Screen density:	165 ppi
Internal storage:	150MB
SD Card:	up to 32GB
Bluetooth:	3.0
Wi-Fi:	802.11 b/g/n
Main camera:	5MP
Power:	Li-Ion 1500 mAh battery
CM supported:	7
Latest CM version:	gingerbread

How to Install CyanogenMod on the LG Optimus Hub (e510)

Note: DISCLAIMER

1 Installing CyanogenMod from recovery

Installing CyanogenMod from recovery

Make sure your computer has working adb.
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.
Boot to recovery mode, and connect the phone to your computer through USB.

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.
Optional (Recommended): Select backup and restore to create a backup.
Select wipe data/factory reset.
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.
Once installation has finished, return to the main menu and select reboot system now. The device will now boot into CyanogenMod.

Helpful Tip – SD card folders

If you’re coming from a ROM with Android 4.1 or older to CyanogenMod 10 or older: adb push update.zip /sdcard/
If you’re coming from a ROM with Android 4.1 or older to CyanogenMod 10.1 or newer: adb shell "mkdir /sdcard/0/" followed by adb push update.zip /sdcard/0/
If you’re coming from a ROM with Android 4.2 or newer to CyanogenMod 10.1 or newer: adb push update.zip /sdcard/0/

Helpful Tip

See something wrong on this page? Click here: Report a Site Problem.

How To Build CyanogenMod For LG Optimus Hub (e510)

Introduction

These instructions will hopefully assist you to start with a stock Optimus Hub, 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.

What you’ll need

A Optimus Hub
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 Optimus Hub (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.

Note:

So let’s begin!

Build CyanogenMod and CyanogenMod Recovery

Prepare the Build Environment

Note:

Install the SDK

Helpful Tip

While the SDK contains lots of different things– the two tools you are most interested in for building Android are adb and fastboot, located in the /platform-tools directory.

Install the Build Packages

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

Helpful Tip

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:

Obtain OpenJDK 1.7 from the openjdk-r PPA
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

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

Helpful Tip

The repo sync command is used to update the latest source code from CyanogenMod and Google. Remember it, as you can do it every few days to keep your code base fresh and up-to-date.

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_e510-userdebug. Select it by typing its number. It is possible that lunch does not display your device. In that case try

$ lunch cm_e510-userdebug

$ lunch full_e510-userdebug

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

Helpful Tip

If you want to know more about what source build/envsetup.sh does or simply want to know more about the breakfast, brunch and lunch commands, you can head over to the Envsetup help page.

Helpful Tip

Extract proprietary blobs

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

$ ./extract-files.sh

Note:

Your device should already be running a build of CyanogenMod for the branch you wish to build for the extract-files.sh script to function properly.

Note:

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

Helpful Tip

Start the build

Time to start building! So now type:

$ croot
$ brunch e510

The build should begin.

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 e510 should then work.

Helpful Tip

A third tip! If the build to fails while downloading Gello, you’ll need to import a missing certificate into Maven’s truststore. Detailed instructions on how to do that can be found here

If the build breaks…

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

ERROR: signapk.jar failed: return code 1make: *** [out/target/product/e510/cm_e510-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

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-e510.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-e510.zip

Note:

Success! So….what’s next?

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

Congrats again!

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

Motorola Droid 2 Global (droid2we)

Cyanogenmod ROM Motorola Droid 2 Global (droid2we)

Quick Info

Download CyanogenMod

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

Main sections for Motorola Droid 2 Global (“droid2we”)

Information about Motorola Droid 2 Global (“droid2we”)
CyanogenMod install guide for Motorola Droid 2 Global (“droid2we”)
Build CyanogenMod and CyanogenMod Recovery guide

Note: Support Status

Notes

This guide is likely out of date, please consult XDA or other sources or fix up this guide if you can.

Source code

Device

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

**Droid 2 Global Specifications**

Codename:	droid2we
Vendor:	Motorola
Release date:	2010 November 11 (USA)
Type:	phone (slider)
GSM freq:	850 900 1800 1900 MHz GSM/GPRS/EDGE 850 1900 2100 MHz UMTS/HSPA
CDMA freq:	800 1900 MHz CDMA 2000 MHz 1xEV-DO
Platform:	TI OMAP3640
CPU:	1.2 GHz single-core Texas Instruments
GPU:	Imagination Technology PowerVR SGX530
RAM:	512MB
Weight:	169 g (6 oz)
Dimensions:	116 mm (4.7 in) (h) 61 mm (2.4 in) (w) 14 mm (0.551 in) (d)
Screen size:	94 mm (3.7 in)
Resolution:	854×480
Internal storage:	8GB
SD Card:	up to 32GB
Bluetooth:	2.1 + EDR
Wi-Fi:	802.11b/g/n
Main camera:	5MP
Power:	1400 mAh internal rechargeable removable lithium-ion polymer battery
Peripherals:	capacitive touchscreen, proximity and ambient light sensors, volume controls, 3-axis accelerometer, digital compass, QWERTY keyboard
CM supported:	7
Latest CM version:	gingerbread

Note: DISCLAIMER

1 Latest Cyanogen That Works
2 Downgrade to the 2.4.330 Firmware
- 2.1 Downgrading the Firmware with RSD Lite (Windows)
- 2.2 Downgrading the Firmware with sbf_flash (Linux & OS X)
3 Gain Root with Framaroot
4 Gaining Root Access with rageagainstthecage
5 Install Bootstrap
6 Installing CyanogenMod from recovery

Latest Cyanogen That Works

Unfortunately, none of the offical ROMs will work for Droid 2 Global. Neither the latest nightly (2013-03-01) nor the stable version 7.2.0. The only version which appears to work is an unofficial version 9, which is unstable. http://rootzwiki.com/topic/17976-cyanogenmod-9-unofficial-for-droid-2-global-ics403-update-31512/page-153#entry1117799

Downgrade to the 2.4.330 Firmware

If the Motorola Droid 2 Global is running firmware newer (higher) than 2.4.330 (Settings » About Phone) you need to downgrade the device first in order to root.

Downgrading the Firmware with RSD Lite (Windows)

Download the Motorola Drivers, RSD Lite & the 2.4.330 firmware:
- RSD Lite 5.7: Download
  
  md5: feb9a71470ee539e074bf420a2e4d8bd
- Motorola 5.5.0 device drivers: Download
- ~~2.4.330 firmware: Download~~
  
  ~~md5: 49cc34d07666c92c1a2a5779e2c74243~~ This firmware creates a bootloader error: Bootloader D0.11 Err:A5,70,70,00,1F. Do not install! If you accidentally install, VRZ_A956_4.5.608_1FF_01.sbf AND flash this after full 608 sbf.rar will get your phone working again. You have to flash both in succession.
Unzip the firmware and place it somewhere easy to access.
Install RSD Lite.
Once RSD Lite is installed, install the Motorola device drivers.
Power off the Motorola Droid 2 Global.
Boot into bootloader mode by holding down the Up Arrow on the keyboard & Power button.
Connect the Motorola Droid 2 Global to the computer via USB.
Open RSD Lite.
Click on the “…” button next to the filename box and select the 2.4.330 firmware .sbf file.
Once it is selected, hit Start and wait for it to finish flashing the device.
It should take about 20 minutes to flash the 2.4.330 firmware. Once it’s finished, the Motorola Droid 2 Global will reboot itself and it will go into a bootloader. Pull the battery and power back while holding the X button. Once you see an Android with the triangle & exclamation point, ~~press the Search button on the keyboard~~ press the ‘Volume Up’ and ‘Volume Down’ buttons at the same time.
The Motorola Droid 2 Global is now in the factory recovery image, use the arrow keys on the keyboard to move around and the Camera button (ClockworkMod Recovery only) or Enter on the keyboard to select.
Select the option to Wipe data/factory reset.
Once the wipe is finished, select Reboot system now.
The Motorola Droid 2 Global is now downgraded to the needed firmware.
Skip the activation of the phone by pressing once in the top left black corner, top right black corner, lower right black corner, and finally lower left black corner.
Turn on “Install Applications From Unknown Source” and “USB Debugging”.

Downgrading the Firmware with sbf_flash (Linux & OS X)

Download sbf_flash & the 2.4.330 firmware:
- sbf_flash: Download
  
  md5: c0eedecde76f82b120161729428b59f7
- 2.4.330 firmware: Download
  
  md5: 49cc34d07666c92c1a2a5779e2c74243
Unzip the sbf_flash zipfile.
Unzip the 2.4.330 firmware and place it somewhere easy to access.
Power off the Motorola Droid 2 Global.
Boot into bootloader mode by holding down the Up Arrow on the keyboard & the Power button.
Connect the Motorola Droid 2 Global to the computer via USB.
On the computer, open terminal and run the following commands:

chmod +x sbf_flash

./sbf_flash VRZ_A956_2.4.33_1FF_01.sbf
It should take about 20 minutes to flash the 2.4.330 firmware. Once it’s finished, the Motorola Droid 2 Global will reboot itself and it will go into a bootloader. Pull the battery and power back while holding the X button. Once you see an Android with the triangle & exclamation point, press the Search button on the keyboard.
The Motorola Droid 2 Global is now in the factory recovery image, use the arrow keys on the keyboard to move around and the Camera button or OK on the keyboard to select.
Select the option to Wipe data/factory reset.
Once the wipe is finished, select Reboot system now.
The Motorola Droid 2 Global is now downgraded to the needed firmware.

Gain Root with Framaroot

Install Framaroot for one click root. http://forum.xda-developers.com/showthread.php?t=2130276 (Select Gimli.)
Run adb push Framaroot_9.9.9.apk /sdcard/
Open Files app, navigate to SDCard, select Framaroot, install, open, root, reboot.

Gaining Root Access with rageagainstthecage

You will need ADB on the computer to root the Droid 2 Global.
Download the following files:
- rageagainstthecage-arm5: Download
  
  md5: bfa28d457b54508326ab55d11399c586
  
  (Note: Antivirus software may delete this because “it could be used by malware to root Android phones”. Either turn off your antivirus, or flag this as “allowed” while you are gaining root access, and un”allow” it when done.)
- Superuser package: Download
  
  md5: 43d9a40b63e916635d5ad7ca32433fab

Unzip rageinthecage-arm5 & the Superuser package to the same folder as adb (the /platform-tools folder within the Android SDK folder).
Connect the Droid 2 Global to the computer via USB.
Allow “USB debug” on the device: Settings > Applications > Development and check USB debugging box.
On the computer, open terminal and run the following commands:

adb push rageagainstthecage-arm5.bin /data/local/tmp/

adb shell

chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin

/data/local/tmp/rageagainstthecage-arm5.bin
Once the exploit finishes, in terminal, run the following commands:

exit

adb kill-server

adb start-server

adb shell

NOTE: You should see a “#”. If you see a “$”, then the exploit didn’t work, please repeat steps 4 & 5.

mount -o rw,remount /dev/block/mmcblk1p21 /system

exit

adb push su /system/xbin/

adb shell chmod 4755 /system/xbin/su

adb push Superuser.apk /system/app/
The Droid 2 Global is now rooted, please continue to the next section.

Install Bootstrap

NEVER install or run Droid 2 Recovery Bootstrap when CyanogenMOD is already installed! It will brick your phone and you must re-flash stock SBF files with RSDLite. You will not even be able to enter recovery mode. Droid 2 Recovery Bootstrap is only for stock ROMs.

Download the Droid 2 Recovery Bootstrap:
- Droid 2 Recovery Bootstrap 1.0.0.5: Download
  
  md5: c67a11b41f52b617d3656ba80016f003
Copy the Droid 2 Recovery Bootstrap to the same folder as adb (the /platform-tools folder within the Android SDK folder).
Connect the Motorola Droid 2 to the computer via USB.
On the computer, open terminal and run the following command:

adb push bootstrap-1.0.0.5-droid2.apk /system/app/
The Droid 2 Recovery Bootstrap with the ClockworkMod Recovery should now be installed on the Motorola Droid 2.

Installing CyanogenMod from recovery

Make sure your computer has working adb.
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.
Boot to recovery mode, and connect the phone to your computer through USB.
- X Key & Power
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.
Optional (Recommended): Select backup and restore to create a backup.
Select wipe data/factory reset.
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.
Once installation has finished, return to the main menu and select reboot system now. The device will now boot into CyanogenMod.

Helpful Tip – SD card folders

If you’re coming from a ROM with Android 4.1 or older to CyanogenMod 10 or older: adb push update.zip /sdcard/
If you’re coming from a ROM with Android 4.1 or older to CyanogenMod 10.1 or newer: adb shell "mkdir /sdcard/0/" followed by adb push update.zip /sdcard/0/
If you’re coming from a ROM with Android 4.2 or newer to CyanogenMod 10.1 or newer: adb push update.zip /sdcard/0/

How To Build CyanogenMod For Motorola Droid 2 Global (droid2we)

Introduction

These instructions will hopefully assist you to start with a stock Droid 2 Global, 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.

What you’ll need

A Droid 2 Global
A relatively recent computer (Linux, OS X, or Windows) with a reasonable amount of RAM and about 100 GB of free storage (more if you enable ccache or build for multiple devices). The less RAM you have, the longer the build will take (aim for 8 GB or more). Using SSDs results in considerably faster build times than traditional hard drives.
A USB cable compatible with the Droid 2 Global (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.

Note:

So let’s begin!

Build CyanogenMod and CyanogenMod Recovery

Prepare the Build Environment

Note:

Install the SDK

Helpful Tip

While the SDK contains lots of different things– the two tools you are most interested in for building Android are adb and fastboot, located in the /platform-tools directory.

Install the Build Packages

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

Helpful Tip

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:

Obtain OpenJDK 1.7 from the openjdk-r PPA
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

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

Helpful Tip

The repo sync command is used to update the latest source code from CyanogenMod and Google. Remember it, as you can do it every few days to keep your code base fresh and up-to-date.

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_droid2we-userdebug. Select it by typing its number. It is possible that lunch does not display your device. In that case try

$ lunch cm_droid2we-userdebug

$ lunch full_droid2we-userdebug

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

Helpful Tip

If you want to know more about what source build/envsetup.sh does or simply want to know more about the breakfast, brunch and lunch commands, you can head over to the Envsetup help page.

Helpful Tip

Extract proprietary blobs

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

$ ./extract-files.sh

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

Note:

Your device should already be running a build of CyanogenMod for the branch you wish to build for the extract-files.sh script to function properly.

Note:

It’s important that these proprietary files are extracted to the ~/android/system/vendor/motorola directory by using the extract-files.sh script. Makefiles are generated at the same time to make sure the blobs are eventually copied to the device. Without these blobs, CyanogenMod may build without error, but you’ll be missing important functionality, such as graphics libraries that enable you to see anything!

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

Helpful Tip

Start the build

Time to start building! So now type:

$ croot
$ brunch droid2we

The build should begin.

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 droid2we should then work.

Helpful Tip

A third tip! If the build to fails while downloading Gello, you’ll need to import a missing certificate into Maven’s truststore. Detailed instructions on how to do that can be found here

If the build breaks…

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

ERROR: signapk.jar failed: return code 1make: *** [out/target/product/droid2we/cm_droid2we-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

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-droid2we.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-droid2we.zip

Note:

Success! So….what’s next?

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

Congrats again!

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

Motorola Droid 2 (droid2)

Cyanogenmod ROM Motorola Droid 2 (droid2)

Quick Info

Download CyanogenMod

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

Main sections for Motorola Droid 2 (“droid2”)

Information about Motorola Droid 2 (“droid2”)
CyanogenMod install guide for Motorola Droid 2 (“droid2”)
Build CyanogenMod and CyanogenMod Recovery guide

Note: Support Status

Special boot modes

Bootloader: Hold down the Up Arrow on the keyboard & Power button.

Source code

Device

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

**Droid 2 Specifications**

Codename:	droid2
Vendor:	Motorola
Manufacturer:	motorola
Release date:	2010 August 12
Type:	phone (slider)
Platform:	TI OMAP3630
CPU:	1 GHz single-core Texas Instruments OMAP3620
GPU:	Imagination Technology PowerVR SGX530
RAM:	512MB
Weight:	169 g (6 oz)
Dimensions:	116 mm (4.7 in) (h) 61 mm (2.4 in) (w) 14 mm (0.551 in) (d)
Screen size:	94 mm (3.7 in)
Resolution:	854×480
Screen density:	265 ppi
Screen type:	TFT LCD
Internal storage:	8GB
SD Card:	up to 32GB
Bluetooth:	2.1
Wi-Fi:	802.11b/g/n
Main camera:	5MP w/ LED flash
Power:	1400 mAh internal rechargeable removable lithium-ion polymer battery
CM supported:	7
Latest CM version:	gingerbread

Note: DISCLAIMER

1 Downgrade to the 2.3.20 Firmware
- 1.1 Downgrading the Firmware with RSD Lite (Windows)
- 1.2 Downgrading the Firmware with sbf_flash (Linux & OS X)
2 Gain Root with Framaroot
3 Gaining Root Access with rageagainstthecage
4 Install Bootstrap
5 Installing CyanogenMod from recovery

Downgrade to the 2.3.20 Firmware

If the Motorola Droid 2 is running firmware newer (higher) than 2.3.20 (Settings » About Phone) you need to downgrade the device first in order to root. If the Motorola Droid 2 is already running 2.3.20 or lower you can skip to the Gaining Root Access section.

Note: If you recently (Spring 2012) accepted the Verizon OTA update to Android version 2.3.4 (firmware version 4.5.621 or 4.5.629) DO NOT DOWNGRADE AT ALL. You will end up bricking your phone due to the new bootloader. It can be unbricked via methods described in the Droid 2 area on http://forums.xda-developers.com/. ~~There is currently (as of May 2012) no way to root a Droid 2 with this system version.~~

Newer Note: A new (July 2012) method for rooting the Droid 2 with the 2.3.4 update. Several people on this page have confirmed that it worked for them. http://rootzwiki.com/topic/29930-new-root-method-for-stock-234-621622-found-droid2-r2d2/

Downgrading the Firmware with RSD Lite (Windows)

Download the Motorola Drivers, RSD Lite & the 2.3.20 firmware:
- RSD Lite 5.7: Download
  
  md5: feb9a71470ee539e074bf420a2e4d8bd
- Motorola 5.5.0 device drivers: Download
- 2.3.20 firmware: Download
  
  md5: 35f8667698e7081f5c8753613abd37f2
Unzip the 2.3.20 firmware and place it somewhere easy to access.
Install RSD Lite.
Once RSD Lite is installed, install the Motorola device drivers.
Power off the Motorola Droid 2.
Boot into bootloader mode by holding down the Up Arrow on the keyboard & Power button.
Connect the Motorola Droid 2 to the computer via USB.
Open RSD Lite.
Click on the “…” button next to the filename box and select the 2.3.20 firmware .sbf file.
Once it is selected, hit Start and wait for it to finish flashing the device.
It should take about 20 minutes to flash the 2.3.20 firmware. Once it’s finished, the Motorola Droid 2 will reboot itself and it will go into a bootloader. Pull the battery and power back while holding the X button. Once you see an Android with the triangle & exclamation point, press the Search button on the keyboard.
The Motorola Droid 2 is now in the factory recovery image, use the arrow keys on the keyboard to move around and the Camera button or OK on the keyboard to select.
Select the option to Wipe data/factory reset.
Once the wipe is finished, select Reboot system now.
The Motorola Droid 2 is now downgraded to the needed firmware.

Downgrading the Firmware with sbf_flash (Linux & OS X)

Download sbf_flash & the 2.3.20 firmware:
- sbf_flash: Download
- 2.3.20 firmware: Download
  
  md5: 35f8667698e7081f5c8753613abd37f2
Unzip the sbf_flash zipfile.
Unzip the 2.3.20 firmware and place it somewhere easy to access.
Power off the Motorola Droid 2.
Boot into bootloader mode by holding down the Up Arrow on the keyboard & the Power button.
Connect the Motorola Droid 2 to the computer via USB.
On the computer, open terminal and run the following commands:

chmod +x sbf_flash

./sbf_flash VRZ_A955_2.3.20_1FF_01.sbf
It should take about 20 minutes to flash the 2.3.20 firmware. Once it’s finished, the Motorola Droid 2 will reboot itself and it will go into a bootloader. Pull the battery and power back on while holding the X keyboard key. Once you see an Android with the triangle & exclamation point, press the Search keyboard key.
The Motorola Droid 2 is now in the factory recovery image, use the arrow keys on the keyboard to move around and the Camera button or OK on the keyboard to select.
Select the option to Wipe data/factory reset.
Once the wipe is finished, select Reboot system now.
The Motorola Droid 2 is now downgraded to the needed firmware.

Gain Root with Framaroot

Install Framaroot for one click root. http://forum.xda-developers.com/showthread.php?t=2130276 (Select Gimli.)
Run adb push Framaroot_9.9.9.apk /sdcard/
Open Files app, navigate to SDCard, select Framaroot, install, open, root, reboot.

Gaining Root Access with rageagainstthecage

You will need ADB on the computer to root the Droid 2.
Download the following files:
- rageagainstthecage-arm5: Download
  
  md5: bfa28d457b54508326ab55d11399c586
  
  (Note: Antivirus software may delete this because “it could be used by malware to root Android phones”. Either turn off your antivirus, or flag this as “allowed” while you are gaining root access, and un”allow” it when done.)
- Superuser package: Download
  
  md5: 43d9a40b63e916635d5ad7ca32433fab

Unzip rageinthecage-arm5 & the Superuser package to the same folder as adb (the /platform-tools folder within the Android SDK folder).
Connect the Droid 2 to the computer via USB.
Allow “USB debug” on the device: Settings > Applications > Development and check USB debugging box.
On the computer, open terminal and run the following commands:

adb push rageagainstthecage-arm5.bin /data/local/tmp/

adb shell

chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin

/data/local/tmp/rageagainstthecage-arm5.bin
Once the exploit finishes, in terminal, run the following commands:

exit

adb kill-server

adb start-server

adb shell

NOTE: You should see a “#”. If you see a “$”, then the exploit didn’t work, please repeat steps 4 & 5.

mount -o rw,remount /dev/block/mmcblk1p21 /system

exit

adb push su /system/xbin/

adb shell chmod 4755 /system/xbin/su

adb push Superuser.apk /system/app/
The Droid 2 is now rooted, please continue to the next section.

Install Bootstrap

Download the Droid 2 Recovery Bootstrap:
- Droid 2 Recovery Bootstrap 1.0.0.5: Download
  
  md5: c67a11b41f52b617d3656ba80016f003
Copy the Droid 2 Recovery Bootstrap to the same folder as adb (the /platform-tools folder within the Android SDK folder).
Connect the Motorola Droid 2 to the computer via USB.
On the computer, open terminal and run the following command:

adb push bootstrap-1.0.0.5-droid2.apk /system/app/
On the Droid 2, open the Recovery Bootstrap app
- select “Bootstrap Recovery” and grant superuser access
The Droid 2 Recovery Bootstrap with the ClockworkMod Recovery should now be installed on the Motorola Droid 2.

Installing CyanogenMod from recovery

Make sure your computer has working adb.
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.
Boot to recovery mode, and connect the phone to your computer through USB.
- X Key & Power
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.
Optional (Recommended): Select backup and restore to create a backup.
Select wipe data/factory reset.
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.
Once installation has finished, return to the main menu and select reboot system now. The device will now boot into CyanogenMod.

Helpful Tip – SD card folders

If you’re coming from a ROM with Android 4.1 or older to CyanogenMod 10 or older: adb push update.zip /sdcard/
If you’re coming from a ROM with Android 4.1 or older to CyanogenMod 10.1 or newer: adb shell "mkdir /sdcard/0/" followed by adb push update.zip /sdcard/0/
If you’re coming from a ROM with Android 4.2 or newer to CyanogenMod 10.1 or newer: adb push update.zip /sdcard/0/

How To Build CyanogenMod For Motorola Droid 2 (droid2)

Introduction

These instructions will hopefully assist you to start with a stock Droid 2, 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.

What you’ll need

A Droid 2
A relatively recent computer (Linux, OS X, or Windows) with a reasonable amount of RAM and about 100 GB of free storage (more if you enable ccache or build for multiple devices). The less RAM you have, the longer the build will take (aim for 8 GB or more). Using SSDs results in considerably faster build times than traditional hard drives.
A USB cable compatible with the Droid 2 (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.

Note:

So let’s begin!

Build CyanogenMod and CyanogenMod Recovery

Prepare the Build Environment

Note:

Install the SDK

Helpful Tip

While the SDK contains lots of different things– the two tools you are most interested in for building Android are adb and fastboot, located in the /platform-tools directory.

Install the Build Packages

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

Helpful Tip

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:

Obtain OpenJDK 1.7 from the openjdk-r PPA
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

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

Helpful Tip

The repo sync command is used to update the latest source code from CyanogenMod and Google. Remember it, as you can do it every few days to keep your code base fresh and up-to-date.

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_droid2-userdebug. Select it by typing its number. It is possible that lunch does not display your device. In that case try

$ lunch cm_droid2-userdebug

$ lunch full_droid2-userdebug

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

Helpful Tip

If you want to know more about what source build/envsetup.sh does or simply want to know more about the breakfast, brunch and lunch commands, you can head over to the Envsetup help page.

Helpful Tip

Extract proprietary blobs

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

$ ./extract-files.sh

Note:

Your device should already be running a build of CyanogenMod for the branch you wish to build for the extract-files.sh script to function properly.

Note:

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

Helpful Tip

Start the build

Time to start building! So now type:

$ croot
$ brunch droid2

The build should begin.

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 droid2 should then work.

Helpful Tip

A third tip! If the build to fails while downloading Gello, you’ll need to import a missing certificate into Maven’s truststore. Detailed instructions on how to do that can be found here

If the build breaks…

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

ERROR: signapk.jar failed: return code 1make: *** [out/target/product/droid2/cm_droid2-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

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-droid2.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-droid2.zip

Note:

Success! So….what’s next?

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

Congrats again!

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

HTC G1 (dream_sapphire)

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”)

Information about HTC G1 (“dream_sapphire”)
CyanogenMod install guide for HTC G1 (“dream_sapphire”)
Build CyanogenMod and CyanogenMod Recovery guide

Note: Support Status

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.

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.

Note:

So let’s begin!

Build CyanogenMod and CyanogenMod Recovery

Prepare the Build Environment

Note:

Install the SDK

Helpful Tip

While the SDK contains lots of different things– the two tools you are most interested in for building Android are adb and fastboot, located in the /platform-tools directory.

Install the Build Packages

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

Helpful Tip

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:

Obtain OpenJDK 1.7 from the openjdk-r PPA
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

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

Helpful Tip

The repo sync command is used to update the latest source code from CyanogenMod and Google. Remember it, as you can do it every few days to keep your code base fresh and up-to-date.

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

Helpful Tip – Errors during breakfast

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

Helpful Tip

If you want to know more about what source build/envsetup.sh does or simply want to know more about the breakfast, brunch and lunch commands, you can head over to the Envsetup help page.

Helpful Tip

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

Note:

Your device should already be running a build of CyanogenMod for the branch you wish to build for the extract-files.sh script to function properly.

Note:

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

Helpful Tip

Start the build

Time to start building! So now type:

$ croot
$ brunch dream_sapphire

The build should begin.

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 dream_sapphire should then work.

Helpful Tip

A third tip! If the build to fails while downloading Gello, you’ll need to import a missing certificate into Maven’s truststore. Detailed instructions on how to do that can be found here

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

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

Note:

Success! So….what’s next?

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

Congrats again!

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

HTC myTouch 4G Slide (doubleshot)

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”)

Information about HTC myTouch 4G Slide (“doubleshot”)
CyanogenMod install guide for HTC myTouch 4G Slide (“doubleshot”)
Build CyanogenMod and CyanogenMod Recovery guide

Note: Support Status

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)

Note: DISCLAIMER

1 Obtaining S-OFF and installing a custom recovery on the myTouch 4G Slide
2 Installing CyanogenMod from recovery

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.

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

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

Settings » Power » Fast Boot

(or)

Settings » Applications » Fast Boot
Enable USB debugging:

Settings » Applications » Development » USB debugging
Connect the myTouch 4G Slide to the computer via USB
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]]
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
Download Revolutionary 0.4pre4
Fill out the form on the Revolutionary site to get a beta key.
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.
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

Make sure your computer has working adb.
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.
Boot to recovery mode, and connect the phone to your computer through USB.
- Vol Down & Power
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.
Optional (Recommended): Select backup and restore to create a backup.
Select wipe data/factory reset.
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.
Once installation has finished, return to the main menu and select reboot system now. The device will now boot into CyanogenMod.

Helpful Tip – SD card folders

If you’re coming from a ROM with Android 4.1 or older to CyanogenMod 10 or older: adb push update.zip /sdcard/
If you’re coming from a ROM with Android 4.1 or older to CyanogenMod 10.1 or newer: adb shell "mkdir /sdcard/0/" followed by adb push update.zip /sdcard/0/
If you’re coming from a ROM with Android 4.2 or newer to CyanogenMod 10.1 or newer: adb push update.zip /sdcard/0/

Helpful Tip

See something wrong on this page? Click here: Report a Site Problem.

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.

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.

Note:

So let’s begin!

Build CyanogenMod and CyanogenMod Recovery

Prepare the Build Environment

Note:

Install the SDK

Helpful Tip

While the SDK contains lots of different things– the two tools you are most interested in for building Android are adb and fastboot, located in the /platform-tools directory.

Install the Build Packages

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

Helpful Tip

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:

Obtain OpenJDK 1.7 from the openjdk-r PPA
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

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

Helpful Tip

The repo sync command is used to update the latest source code from CyanogenMod and Google. Remember it, as you can do it every few days to keep your code base fresh and up-to-date.

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

Helpful Tip – Errors during breakfast

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

Helpful Tip

If you want to know more about what source build/envsetup.sh does or simply want to know more about the breakfast, brunch and lunch commands, you can head over to the Envsetup help page.

Helpful Tip

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

Note:

Your device should already be running a build of CyanogenMod for the branch you wish to build for the extract-files.sh script to function properly.

Note:

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

Helpful Tip

Start the build

Time to start building! So now type:

$ croot
$ brunch doubleshot

The build should begin.

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 doubleshot should then work.

Helpful Tip

A third tip! If the build to fails while downloading Gello, you’ll need to import a missing certificate into Maven’s truststore. Detailed instructions on how to do that can be found here

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

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

Note:

Success! So….what’s next?

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

Congrats again!

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

HTC Eris (desirec)

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”)

Information about HTC Eris (“desirec”)
CyanogenMod install guide for HTC Eris (“desirec”)
Build CyanogenMod and CyanogenMod Recovery guide

Note: Support Status

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)

Note: DISCLAIMER

1 Installing a recovery image using flash_image
2 Installing CyanogenMod from recovery

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.

Download the flash_image binary
- flash_image: download or download older version (if you get Illegal Instruction)
  
  md5: bd475f29e0665c702f8eaf57a0423b58
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
Download koush’s ClockworkMod Recovery.
- koush’s ClockworkMod Recovery: download
  
  md5: 31dae925bc707df266cac86569261e8d
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:

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

Installing CyanogenMod from recovery

Make sure your computer has working adb.
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.
Boot to recovery mode, and connect the phone to your computer through USB.
- Vol Down & Power
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.
Optional (Recommended): Select backup and restore to create a backup.
Select wipe data/factory reset.
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.
Once installation has finished, return to the main menu and select reboot system now. The device will now boot into CyanogenMod.

Helpful Tip – SD card folders

If you’re coming from a ROM with Android 4.1 or older to CyanogenMod 10 or older: adb push update.zip /sdcard/
If you’re coming from a ROM with Android 4.1 or older to CyanogenMod 10.1 or newer: adb shell "mkdir /sdcard/0/" followed by adb push update.zip /sdcard/0/
If you’re coming from a ROM with Android 4.2 or newer to CyanogenMod 10.1 or newer: adb push update.zip /sdcard/0/

Helpful Tip

See something wrong on this page? Click here: Report a Site Problem.

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.

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.

Note:

So let’s begin!

Build CyanogenMod and CyanogenMod Recovery

Prepare the Build Environment

Note:

Install the SDK

Helpful Tip

While the SDK contains lots of different things– the two tools you are most interested in for building Android are adb and fastboot, located in the /platform-tools directory.

Install the Build Packages

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

Helpful Tip

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:

Obtain OpenJDK 1.7 from the openjdk-r PPA
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

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

Helpful Tip

The repo sync command is used to update the latest source code from CyanogenMod and Google. Remember it, as you can do it every few days to keep your code base fresh and up-to-date.

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

$ lunch full_desirec-userdebug

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

Helpful Tip

If you want to know more about what source build/envsetup.sh does or simply want to know more about the breakfast, brunch and lunch commands, you can head over to the Envsetup help page.

Helpful Tip

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

Note:

Your device should already be running a build of CyanogenMod for the branch you wish to build for the extract-files.sh script to function properly.

Note:

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

Helpful Tip

Start the build

Time to start building! So now type:

$ croot
$ brunch desirec

The build should begin.

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 desirec should then work.

Helpful Tip

A third tip! If the build to fails while downloading Gello, you’ll need to import a missing certificate into Maven’s truststore. Detailed instructions on how to do that can be found here

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

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.

Download the flash_image binary
- flash_image: download or download older version (if you get Illegal Instruction)
  
  md5: bd475f29e0665c702f8eaf57a0423b58
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
Download {{{install_devname}}}’s ClockworkMod Recovery.
- {{{install_devname}}}’s ClockworkMod Recovery: [{{{install_file}}} download]
  
  md5: {{{install_md5sum}}}
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:

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

Note:

Success! So….what’s next?

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

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 3G Slide (espresso)

Quick Info

Main sections for HTC myTouch 3G Slide (“espresso”)

Special boot modes

Source code

Contents

Rooting & Installing a Custom Recovery on the myTouch Slide

Installing CyanogenMod from recovery

How To Build CyanogenMod For HTC myTouch 3G Slide (espresso)

Contents

Introduction

What you’ll need

Build CyanogenMod and CyanogenMod Recovery

Prepare the Build Environment

Install the SDK

Install the Build Packages

Create the directories

Install the repo command

Put the ~/bin directory in your path of execution

Initialize the CyanogenMod source repository

Download the source code

Get prebuilt Rom Manager

Prepare the device-specific code

Extract proprietary blobs

Turn on caching to speed up build

Start the build

If the build breaks…

Install the build

Install CyanogenMod

Success! So….what’s next?

Cyanogenmod ROM Samsung Galaxy Tab 2 7.0 / Tab 2 10.1 (unified, GSM) (espresso3g)

Quick Info

Check out Samsung Galaxy Tab 2 7.0 / Tab 2 10.1 (unified, GSM) (“espresso3g”) with newer LineageOS software

Main sections for Samsung Galaxy Tab 2 7.0 / Tab 2 10.1 (unified, GSM) (“espresso3g”)

Special boot modes

Source code

How to Install CyanogenMod on the Samsung Galaxy Tab 2 7.0 / Tab 2 10.1 (unified, GSM) (espresso3g)

Contents

Installing a custom recovery

Installing CyanogenMod from recovery

How To Build CyanogenMod For Samsung Galaxy Tab 2 7.0 / Tab 2 10.1 (unified, GSM) (espresso3g)

Contents

Introduction

What you’ll need

Build CyanogenMod and CyanogenMod Recovery

Prepare the Build Environment

Install the SDK

Install the Build Packages

Create the directories

Install the repo command

Put the ~/bin directory in your path of execution

Initialize the CyanogenMod source repository

Download the source code

Get prebuilt apps (CM11 and below)

Prepare the device-specific code

Extract proprietary blobs

Turn on caching to speed up build

Start the build

If the build breaks…

Install the build

Install CyanogenMod

Success! So….what’s next?

Cyanogenmod ROM Barnes & Noble Nook Color (encore)

Quick Info

Main sections for Barnes & Noble Nook Color (“encore”)

Notes

Source code

How to Install CyanogenMod on the Barnes & Noble Nook Color (encore)

Contents

Important Notes

Setting up uNooter

Windows

Linux

Mac OS X

Gaining Root Access

Install a Custom Recovery Image

Installing CyanogenMod from recovery

Alternative ClockworkMod Recovery installation

How To Build CyanogenMod For Barnes & Noble Nook Color (encore)

Contents

Install the `repo` command

Put the `~/bin` directory in your path of execution

Install the `repo` command

Put the `~/bin` directory in your path of execution

Install the `repo` command

Put the `~/bin` directory in your path of execution

Install the `repo` command

Put the `~/bin` directory in your path of execution