HTC Amaze 4G (ruby)

Cyanogenmod ROM HTC Amaze 4G (ruby)

Quick Info

Download CyanogenMod

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

Main sections for HTC Amaze 4G (“ruby”)

Information about HTC Amaze 4G (“ruby”)
CyanogenMod install guide for HTC Amaze 4G (“ruby”)
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 jellybean branch of CyanogenMod.

Special boot modes

Recovery: Volume Down & Power

Source code

Device	http://www.github.com/cyanogenmod/android_device_htc_ruby
Kernel	http://www.github.com/cyanogenmod/android_kernel_htc_msm8660

**Amaze 4G Specifications**

Codename:	ruby
Vendor:	HTC
Release date:	2011 October 12
Carrier:	T-Mobile
Type:	phone
GSM freq:	850 900 1700/2100 1800 1900 2100 MHz HSDPA+ (4G) 42.2 Mbit/s, UMTS, EDGE
Platform:	Qualcomm APQ8060
CPU:	1.5 GHz dual-core Scorpion Snapdragon S3
GPU:	Adreno 220
RAM:	1GB
Weight:	173 g (6.10 oz)
Dimensions:	130 mm (5.12 in) (h) 65.6 mm (2.58 in) (w) 11.8 mm (0.46 in) (d)
Screen size:	109 mm (4.3 in)
Resolution:	540×960
Screen density:	256 PPI
Internal storage:	16 GB
SD Card:	microSD, microSDHC up to 32 GB
Bluetooth:	3.0
Wi-Fi:	802.11 a/b/g/n
Main camera:	8MP Dual LED
Secondary camera:	2MP
Power:	1730 mAh removable
Peripherals:	Light sensor, Proximity sensor, Accelerometer, Compass, NFC, MHL, UMA
CM supported:	10
Latest CM version:	jellybean

How to Install CyanogenMod on the HTC Amaze 4G (ruby)

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 Unlocking the bootloader
2 Installing a custom recovery using fastboot
3 Installing CyanogenMod from recovery

Unlocking the bootloader

WARNING:

Unlocking the bootloader will automatically wipe all device data.

Note:

The Amaze 4G can be unlocked officially via the HTC Dev unlock program. This unlock method may have certain restrictions, such as not being able to flash a kernel via recovery (no longer applicable to 2013+ released HTC devices) or no USB access to sdcard in recovery. Some devices, however, have no other method to install custom firmware.

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

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

fastboot oem get_identifier_token
Visit the HTCDev Bootloader Unlock website and follow the instructions there to obtain your unlock key and unlock your bootloader. If your device does not appear in the drop-down list, select All Other Supported Models.
If the device doesn’t automatically reboot, reboot it from the menu. It should now be unlocked.
Since the device resets completely, you will need to re-enable USB debugging on the device to continue.

Installing a custom recovery using fastboot

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

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

Recovery: Download

md5: 93f4a333d22573a3b0bb735887d83163
Connect the Amaze 4G to the computer via USB.
Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
Open a terminal on your PC and reboot the device into fastboot mode by typing

adb reboot bootloader

or by using the hardware key combination for your device while it is powered off.
Once the device is in fastboot mode, verify your PC sees the device by typing

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

fastboot flash recovery your_recovery_image.img

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

Installing CyanogenMod from recovery

Note:

This device, if unlocked with HTCDev Unlock, must have its kernel flashed via fastboot. When you reach the end of the instructions below, do not restart your device to CyanogenMod yet. Instead, restart to the bootloader and put the phone in fastboot mode. Extract boot.img from the CyanogenMod .zip package you just installed and flash it via fastboot: cd to the directory containing boot.img and execute fastboot flash boot boot.img. This needs to be done EVERY time CyanogenMod is updated, thus it is recommended to not use the internal CM updater. The alternative to this burden is to S-OFF your device (recommended), then the boot partition will automatically be updated when CyanogenMod is installed or updated.

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.
Place the CyanogenMod .zip package, as well as any optional .zip packages, on the root of /sdcard:
- Using adb: adb push filename.zip /sdcard/
Note: You can copy the .zip packages to your device using any method you are familiar with. The adb method is used here because it is universal across all devices and works in both Android and recovery mode. If you are in recovery mode, you may need to ensure /sdcard (sometimes called Internal Storage) is mounted by checking its status in the Mounts menu. If you have booted regularly, USB debugging must be enabled.
If you are not already in recovery, boot to recovery mode now.
- Volume Down & Power
In Team Win Recovery Project, select menu choices by tapping on the appropriately labelled button.
Optional (Recommended): Select the Backup button to create a backup.
Select Wipe and then Factory Reset.
Select Install.
Navigate to /sdcard and select the CyanogenMod .zip package.
Follow the on-screen notices to install the package.
Optional: Install any additional packages you wish using the same method (if you are installing multiple packages, install CyanogenMod first and then install any subsequent packages on top of it).
Once installation has finished, return to the main menu and select Reboot, then System. The device will now boot into CyanogenMod.

Helpful Tip

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

How To Build CyanogenMod For HTC Amaze 4G (ruby)

Introduction

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

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

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

What you’ll need

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

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

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 jellybean

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 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 ruby

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

$ source build/envsetup.sh
$ breakfast ruby

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

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

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

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

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 ruby

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

Installing a custom recovery using fastboot

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

Make sure your computer has working fastboot and adb.

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

adb reboot bootloader

or by using the hardware key combination for your device while it is powered off.
Once the device is in fastboot mode, verify your PC sees the device by typing

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

fastboot flash recovery your_recovery_image.img

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

Install CyanogenMod

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

cm-10-20161224-UNOFFICIAL-ruby.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.

Sony Ericsson Xperia X10 Mini (robyn)

Cyanogenmod ROM Sony Ericsson Xperia X10 Mini (robyn)

Quick Info

Download CyanogenMod

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

Main sections for Sony Ericsson Xperia X10 Mini (“robyn”)

Information about Sony Ericsson Xperia X10 Mini (“robyn”)
CyanogenMod install guide for Sony Ericsson Xperia X10 Mini (“robyn”)
Build CyanogenMod and CyanogenMod Recovery guide

Note: Support Status

Notes

The Sony Ericsson Xperia X10 Mini (aka robyn) is a touchscreen smartphone manufactured by Sony Ericsson. Official CyanogenMod support for the Sony Ericsson Xperia X10 Mini was added in CyanogenMod 7.1.

Source code

Device

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

**Xperia X10 Mini Specifications**

Codename:	robyn
Vendor:	Sony Ericsson
Release date:	2010 May
Type:	phone
GSM freq:	Quad-band GSM 850 900 1800 1900 MHz GPRS/EDGE
CDMA freq:	Tri-band 800 1900 2100 MHz HSPA/WCDMA
Platform:	Qualcomm MSM7227
CPU:	600 MHz single-core Qualcomm MSM7227 Processor
GPU:	Qualcomm Adreno 200
RAM:	128MB
Weight:	88 g (3.1 oz)
Dimensions:	83 mm (3.27 in) (h) 50 mm (1.9 in) (w) 16 mm (0.63 in) (d)
Screen size:	65 mm (2.6 in)
Resolution:	320×480 (HVGA)
Screen type:	TFT LCD
SD Card:	supports up to 16 GB
Bluetooth:	Bluetooth 2.0+EDR with A2DP
Wi-Fi:	Wi-Fi (802.11b/g)
Main camera:	5 megapixel with LED Flash
Power:	950 mAh internal rechargeable removable lithium polymer battery
Peripherals:	microUSB, A-GPS, capacitive touchscreen, proximity & ambient light sensors, volume controls, 3-axis accelerometer, digital compass
CM supported:	7
Latest CM version:	gingerbread

How To Build CyanogenMod For Sony Ericsson Xperia X10 Mini (robyn)

Introduction

These instructions will hopefully assist you to start with a stock Xperia X10 Mini, 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 Xperia X10 Mini
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 Xperia X10 Mini (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_robyn-userdebug. Select it by typing its number. It is possible that lunch does not display your device. In that case try

$ lunch cm_robyn-userdebug

$ lunch full_robyn-userdebug

If all goes well, you should see that robyn-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 Xperia X10 Mini is connected to your computer via the USB cable and that you are in the ~/android/system/device/semc/robyn directory (you can cd ~/android/system/device/semc/robyn 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/semc 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/semc 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 robyn

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 robyn 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/robyn/cm_robyn-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-robyn.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-robyn.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 Thrill 4G (p925)

Cyanogenmod ROM LG Thrill 4G (p925)

Quick Info

Download CyanogenMod

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

Main sections for LG Thrill 4G (“p925”)

Information about LG Thrill 4G (“p925”)
CyanogenMod install guide for LG Thrill 4G (“p925”)
Build CyanogenMod and CyanogenMod Recovery guide

Note: Support Status

Notes

The LG Thrill 4G is the US version of the LG Optimus 3D. Both phones share the same hardware, and as a result, CM10 Optimus 3D ROMs may be installed. Please see the LG Optimus 3D page for information on installation.

Source code

Device

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

**Thrill 4G Specifications**

Codename:	p925
Vendor:	LG
Type:	phone
Platform:	TI OMAP4430
CPU:	1 GHz dual-core Cortex A9
RAM:	512MB
Screen size:	109 mm (4.3 in)
Resolution:	480×800
Screen density:	217 ppi
Screen type:	TFT LCD
CM supported:	7
Latest CM version:	gingerbread

How to Install CyanogenMod on the LG Thrill 4G (p925)

Note: DISCLAIMER

1 Important Notes
2 Installing CyanogenMod from recovery

Important Notes

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

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/

Helpful Tip

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

How To Build CyanogenMod For LG Thrill 4G (p925)

Introduction

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

What you’ll need

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

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

$ lunch cm_p925-userdebug

$ lunch full_p925-userdebug

If all goes well, you should see that p925-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 Thrill 4G is connected to your computer via the USB cable and that you are in the ~/android/system/device/lge/p925 directory (you can cd ~/android/system/device/lge/p925 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:

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

Helpful Tip

Start the build

Time to start building! So now type:

$ croot
$ brunch p925

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 p925 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/p925/cm_p925-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-p925.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-p925.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 One (p500)

Cyanogenmod ROM LG Optimus One (p500)

Quick Info

Download CyanogenMod

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

Main sections for LG Optimus One (“p500”)

Information about LG Optimus One (“p500”)
CyanogenMod install guide for LG Optimus One (“p500”)
Build CyanogenMod and CyanogenMod Recovery guide

Note: Support Status

Special boot modes

Recovery: Volume Down + Power + Home
Fastboot: Power + Home

Source code

Device

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

**Optimus One Specifications**

Codename:	p500
Also known as:	LG-P500/LG Optimus One
Vendor:	LG
Manufacturer:	LG
Release date:	October 2010
Carrier:	Vodafone
Type:	phone
GSM freq:	850 900 1800 1900 2100 MHz UMTS/HSPA+
Platform:	Qualcomm MSM7227
CPU:	600 MHz single-core Snapdragon (ARMv6)
GPU:	Qualcomm Adreno 200
RAM:	512MB
Weight:	129 g (4.55 oz)
Dimensions:	113.5 mm (4.47 in) (h) 59 mm (2.32 in) (w) 13.3 mm (0.52 in) (d)
Screen size:	81 mm (3.2 in)
Resolution:	320×480
Screen density:	160 PPI
Internal storage:	190MB
SD Card:	up to 32GB
Bluetooth:	2.1
Wi-Fi:	802.11 b/g
Main camera:	3.2MP
Power:	1500 mAh
Peripherals:	accelerometer, proximity, compass
CM supported:	7
Latest CM version:	gingerbread

How to Install CyanogenMod on the LG Optimus One (p500)

Note: DISCLAIMER

1 Installing CyanogenMod from recovery
2 Before you start
3 Installing Recovery Mode
4 Accessing Recovery Mode
5 Troubleshooting

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.
- Volume Down + Power + Home
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.

Before you start

Backup all your data as this will wipe everything on your phone
Make sure your battery is fully charged
This can take as little as 30 minutes and as long as 3 hours

Installing Recovery Mode

On a rooted device

Go to Google Play Store
Install “ClockworkMod ROM Manager”
Follow instructions when you open it
Confirm your model and select Clockwork Recovery mode
Wait for download to complete
It’ll flash your device with the ROM manager

Rooting

It is easy to root this device, so root the device before trying to install cyanogenmod.

Use SuperOneClick :
http://forum.xda-developers.com/showthread.php?t=803682

First:

Settings > SD Card and Storage: make sure “Mass Storage” in unchecked
Settings > Applications > Developers Tools: check USB Debugging
You will need to have the LG USB driver installed on your computer

More on Recovery Mode Install

In some cases (encountered at least with LG P500 with Android 2.2.1 and 2.3.3), the current (2014) ROM Manager does not install the ClockworkMod Recovery image correctly. The manager does not report any error, however, on attempt to boot ClockworkMod Recovery, stock recovery is displayed and factory reset takes place afterwards (behavior described e.g. here http://androidforums.com/optimus-one-all-things-root/465761-clockwork-mod-reboot-into-recovery-factory-resets-phone.html). This issue can be fixed using the LGMDP tool (process described here http://forum.xda-developers.com/showthread.php?t=1318750), it might also be necessary to try multiple versions of the ClockworkMod Recovery images. (Note: use the MENU button (on the left) to select in this recovery.)

Another issue to pay attention to is the phone baseband version (especially if the installed CyanogenMod image does not connect to the mobile network at all).

Accessing Recovery Mode

Power off phone
Press and hold VOLUME DOWN + HOME + Power until you see LG Logo

Troubleshooting

VOLUME DOWN + HOME + POWER just resets the phone

If you enter the key combination and you see a white box, yellow arrow and a green droid, this means that you have not installed ClockworkMod Recovery mode. Install ClockworkMod Recovery mode and try again

Backup failed ‘error while making a backup image of /sdcard/.android_secure

If you see an error running a backup of your phone and it says ‘error while making a backup image of [ insert folder name here ]’, you do not have enough free space on your sd card. Free up space on your SD card and try again

Here is a page that talks about => .android_secure

My phone boots but freezes on the blue android skateboard logo

Go back into recovery mode
Wipe/factory reset your phone
Reinstall the Cyanogenmod image

I don’t have Android Market/Google Play Store anymore

To get Google Play Store, you must install Google Apps. Download the ZIP file to your sd card, reboot into Recovery Mode and install the ZIP. It’ll add Google Play Store to your install. This also installs GMail and some other basic Google apps.

How To Build CyanogenMod For LG Optimus One (p500)

Introduction

These instructions will hopefully assist you to start with a stock Optimus One, 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 One
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 One (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_p500-userdebug. Select it by typing its number. It is possible that lunch does not display your device. In that case try

$ lunch cm_p500-userdebug

$ lunch full_p500-userdebug

If all goes well, you should see that p500-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 One is connected to your computer via the USB cable and that you are in the ~/android/system/device/lge/p500 directory (you can cd ~/android/system/device/lge/p500 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 p500

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 p500 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/p500/cm_p500-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-p500.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-p500.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.

Samsung Galaxy Tab 10.1 (Verizon) (p4vzw)

Cyanogenmod ROM Samsung Galaxy Tab 10.1 (Verizon) (p4vzw)

Quick Info

Download CyanogenMod

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

Main sections for Samsung Galaxy Tab 10.1 (Verizon) (“p4vzw”)

Information about Samsung Galaxy Tab 10.1 (Verizon) (“p4vzw”)
CyanogenMod install guide for Samsung Galaxy Tab 10.1 (Verizon) (“p4vzw”)
Build CyanogenMod and CyanogenMod Recovery guide

Notes

This guide assumes the tablet is running stock ICS.

Special boot modes

Download: Volume Down

Source code

Device	http://www.github.com/cyanogenmod/android_device_samsung_p4vzw
Kernel	http://www.github.com/cyanogenmod/android_kernel_samsung_p4

**Galaxy Tab 10.1 (Verizon) Specifications**

Codename:	p4vzw
Also known as:	SCH-I905
Vendor:	Samsung
Manufacturer:	samsung
Type:	tablet
CDMA freq:	Dual-band CDMA 800 1900 MHz EVDO Rev. A
LTE freq:	700MHz
Platform:	NVIDIA Tegra 2
CPU:	1 GHz dual-core T2 250
GPU:	ULP Geforce
RAM:	1GB
Weight:	565 g (19.9 oz)
Dimensions:	256 mm (10.1 in) (h) 175 mm (6.8 in) (w) 9.7 mm (0.38 in) (d)
Screen size:	257 mm (10.1 in)
Resolution:	1280×800
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:	7000 mAh (Non-removable)
Peripherals:	capacitive touchscreen, proximity & light sensors, 3-axis accelerometer, additional 3-axis gyroscope, digital compass
CM supported:	9, 10, 10.1

Note: DISCLAIMER

1 Installing a custom recovery on Samsung Galaxy Tab 10.1 (Verizon)
2 Installing CyanogenMod from recovery

Installing a custom recovery on Samsung Galaxy Tab 10.1 (Verizon)

Samsung devices come with a unique boot mode called Download Mode which is very similar to Fastboot Mode on some devices with unlocked bootloaders. P3/P4 family tablets need to use Odin3-v1.85 to interface with the device while in Download Mode. The preferred method of installing a custom recovery is through this boot mode. Rooting the stock firmware is neither recommended nor necessary.

Windows Only (pending heimdall testing)

Download pershoot’s ClockworkMod Recovery package, and Odin3-v1.85:
- pershoot’s ClockworkMod Recovery: download
  
  md5: 3f800d0638ef867c2c93067d16ace9db
- Odin3-v1.85: download
- Samsung USB Drivers with Escape: download
  - 64 bit only Escape: download
Open Odin3-v1.85.
Power off the Samsung Galaxy Tab 10.1 (Verizon) and connect the USB adapter to the computer but not to the Samsung Galaxy Tab 10.1 (Verizon).
Boot the Samsung Galaxy Tab 10.1 (Verizon) into download mode by holding down Vol Up & Power buttons while connecting via USB. After the Samsung logo appears and disappears, release both buttons promptly when you see the download icon. The download icon will stay fixed if you time the button release properly (just keep trying if your hand-eye coordination sucks). Press Vol Down to select enter Download Mode and Vol Up one more time to adhere to the warning page to connect to Odin.
- NOTE: To confirm the device is connected and working, look in Odin for a yellow COM box with the word 0:[COMn] inside, with n being a number.
Uncheck the box labeled Auto Reboot.
Press the dialog box labeled PDA and select the recovery package.
Press Start.
A blue transfer bar will appear on the device showing the recovery being transferred. The Samsung Galaxy Tab 10.1 (Verizon) now has ClockworkMod Recovery installed.
Assuming you unchecked the Auto Reboot box, the device won’t reboot automatically. If you already copied CM to the device, reboot directly into CWM by holding down the Vol Up & Power buttons again. Otherwise, hold down the Power button for a standard reboot (you will have to reload CWM again after you copy the CM files to the device).
Continue to the next section.

Helpful Tip

The stock ROM may overwrite your custom recovery on boot. To prevent this, boot immediately into ClockworkMod 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.
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.

Installing CyanogenMod from recovery

Note:

Some devices do not have removable SD cards. There may be a partition on the device named “/sdcard” that can be used for flashing purposes, even though the contents of /sdcard may actually be in internal storage. If the device has no removable SD card nor the “/sdcard” folder, then just use the “/root” folder in the following directions.

Download the prebuilt release of CyanogenMod you wish to install. (Or if you’ve built CM yourself, look in the $OUT directory for the .zip.)

Optional: Download any supplemental 3rd-party applications packages for the device you wish to use.
Place the CyanogenMod rom .zip file on the root of the SD card:
- If using Windows, you may be able to simply copy the files to your device with Windows Explorer.
- Else, from a terminal run adb push ROMZIP.zip /sdcard/
See adb documentation for additional help with this step.

Optional: Place any supplemental packages (eg Google Apps or kernels) .zip file(s) on the root of the SD card.

Note: This device needs to use Google Apps sourced from here for CyanogenMod 10.1.
Boot to recovery mode on the Samsung Galaxy Tab 10.1 (Verizon) by holding Vol Up & Power.
Once the device boots into the ClockworkMod Recovery, use the physical volume buttons to move up and down. On most devices, the power button is used to confirm your selection, although for some devices the power button is used as a “back” button to go up one level, in which case the home button is used to confirm the selection.

Optional/Recommended: Select backup and restore to create a backup of the current installation on the Samsung Galaxy Tab 10.1 (Verizon).
Select the option to wipe data/factory reset.
Select install zip from sdcard.
Select choose zip from sdcard.
Select the CyanogenMod file you placed on the sdcard. You will then need to then confirm that you do wish to flash this file.

Optional: Install any additional packages you wish using the same method.
Once the installation has finished, return back to the main menu, and select the reboot system now option. The Samsung Galaxy Tab 10.1 (Verizon) should now boot into CyanogenMod.

How To Build CyanogenMod For Samsung Galaxy Tab 10.1 (Verizon) (p4vzw)

Introduction

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

What you’ll need

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

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 p4vzw

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

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 p4vzw 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/p4vzw/cm_p4vzw-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-p4vzw.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-p4vzw.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.

Samsung Galaxy Tab 10.1 (TMO) (p4tmo)

Cyanogenmod ROM Samsung Galaxy Tab 10.1 (TMO) (p4tmo)

Quick Info

Download CyanogenMod

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

Main sections for Samsung Galaxy Tab 10.1 (TMO) (“p4tmo”)

Information about Samsung Galaxy Tab 10.1 (TMO) (“p4tmo”)
CyanogenMod install guide for Samsung Galaxy Tab 10.1 (TMO) (“p4tmo”)
Build CyanogenMod and CyanogenMod Recovery guide

Special boot modes

Download: Volume Down

Source code

Device	http://www.github.com/cyanogenmod/android_device_samsung_p4tmo
Kernel	http://www.github.com/cyanogenmod/android_kernel_samsung_p4

**Galaxy Tab 10.1 (TMO) Specifications**

Codename:	p4tmo
Also known as:	SGH-T859
Vendor:	Samsung
Manufacturer:	samsung
Type:	tablet
GSM freq:	Quad-band 850 900 1800 1900 MHz HSDPA 850 1700 1900 2100 MHz
LTE freq:	700MHz
Platform:	NVIDIA Tegra 2
CPU:	1 GHz dual-core T2 250
GPU:	ULP Geforce
RAM:	1GB
Weight:	565 g (19.9 oz)
Dimensions:	256 mm (10.1 in) (h) 175 mm (6.8 in) (w) 9.7 mm (0.38 in) (d)
Screen size:	257 mm (10.1 in)
Resolution:	1280×800
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:	7000 mAh (Non-removable)
Peripherals:	capacitive touchscreen, proximity & light sensors, 3-axis accelerometer, additional 3-axis gyroscope, digital compass
CM supported:	9, 10, 10.1

Note: DISCLAIMER

1 Installing a custom recovery on Samsung Galaxy Tab 10.1 (TMO)
2 Installing CyanogenMod from recovery

Installing a custom recovery on Samsung Galaxy Tab 10.1 (TMO)

Windows Only (pending heimdall testing)

Download pershoot’s ClockworkMod Recovery package, and Odin3-v1.85:
- pershoot’s ClockworkMod Recovery: download
  
  md5: 814ac9b7e51de62500c51433aa10c32b
- Bootloader: download
  
  md5: aa6e706240c8a6858dc1979421ad8d29
- Modem: download
  
  md5: 9b8d7f44ef2c5dc5ae577f4b6012f395
- Odin3-v1.85: download
- Samsung USB Drivers with Escape: download
  - 64 bit only Escape: download
Open Odin3-v1.85.
Power off the Samsung Galaxy Tab 10.1 (TMO) and connect the USB adapter to the computer but not to the Samsung Galaxy Tab 10.1.
Boot the Samsung Galaxy Tab 10.1 (TMO) into download mode by holding down Vol Down & Power while connecting via USB.
- NOTE: To confirm the device is connected and working, look for the blue COM box with the word Added!! inside.
Uncheck the box labeled Auto Reboot.
Press the dialog box labeled PDA and select the bootloader package.
Press Start.
A blue transfer bar will appear on the device showing the file being transferred. Once completed, the device will reboot automatically.
Repeat Steps 2-7 using the recovery and modem files the exact same way as the bootloader.
The Samsung Galaxy Tab 10.1 (TMO) now has ClockworkMod Recovery installed. Continue to the next section.

Helpful Tip

The stock ROM may overwrite your custom recovery on boot. To prevent this, boot immediately into ClockworkMod 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.
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.

Installing CyanogenMod from recovery

Note:

Some devices do not have removable SD cards. Regardless, there should still be a partition on the device named “/sdcard” that can be used for flashing purposes, even though the contents of /sdcard may actually be in internal storage.

Download the prebuilt release of CyanogenMod you wish to install. (Or if you’ve built CM yourself, look in the $OUT directory for the .zip.)

Optional: Download any supplemental 3rd-party applications packages for the device you wish to use.
Place the CyanogenMod rom .zip file on the root of the SD card:
- From a terminal run adb push ROMZIP.zip /sdcard/
See adb documentation for additional help with this step.

Optional: Place any supplemental packages (eg Google Apps or kernels) .zip file(s) on the root of the SD card.

Note: This device needs to use Google Apps sourced from here for CyanogenMod 10.1.
Boot to recovery mode on the Samsung Galaxy Tab 10.1 (TMO) by holding Vol Up & Power.
Once the device boots into the ClockworkMod Recovery, use the physical volume buttons to move up and down. On most devices, the power button is used to confirm your selection, although for some devices the power button is used as a “back” button to go up one level, in which case the home button is used to confirm the selection.

Optional/Recommended: Select backup and restore to create a backup of the current installation on the Samsung Galaxy Tab 10.1 (TMO).
Select the option to wipe data/factory reset.
Select install zip from sdcard.
Select choose zip from sdcard.
Select the CyanogenMod file you placed on the sdcard. You will then need to then confirm that you do wish to flash this file.

Optional: Install any additional packages you wish using the same method.
Once the installation has finished, return back to the main menu, and select the reboot system now option. The Samsung Galaxy Tab 10.1 (TMO) should now boot into CyanogenMod.

How To Build CyanogenMod For Samsung Galaxy Tab 10.1 (TMO) (p4tmo)

Introduction

These instructions will hopefully assist you to start with a stock Galaxy Tab 10.1 (TMO), 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 10.1 (TMO)
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 10.1 (TMO) (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 p4tmo

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 10.1 (TMO) is connected to your computer via the USB cable and that you are in the ~/android/system/device/samsung/p4tmo directory (you can cd ~/android/system/device/samsung/p4tmo 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 p4tmo

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 p4tmo 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/p4tmo/cm_p4tmo-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-p4tmo.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-p4tmo.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.

Samsung Galaxy Tab 2 7.0 (GSM) (p3100)

Cyanogenmod ROM Samsung Galaxy Tab 2 7.0 (GSM) (p3100)

Quick Info

Download CyanogenMod

Download (nightly build)
CyanogenMod 11 (Android 4.4-4.4.4 (KitKat))

Main sections for Samsung Galaxy Tab 2 7.0 (GSM) (“p3100”)

Information about Samsung Galaxy Tab 2 7.0 (GSM) (“p3100”)
CyanogenMod install guide for Samsung Galaxy Tab 2 7.0 (GSM) (“p3100”)
Build CyanogenMod and CyanogenMod Recovery guide

Notes

WARNING: Device specific builds are discontinued!

Please use “espresso3g” builds in future.

Special boot modes

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

Source code

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

**Galaxy Tab 2 7.0 (GSM) Specifications**

Codename:	p3100
Vendor:	Samsung
Manufacturer:	samsung
Type:	tablet
GSM freq:	Quad-band 850 900 1800 1900 MHz Tri-band 900 1900 2100 MHz HSPA+
Platform:	TI OMAP4430
CPU:	1 GHz dual-core OMAP4
GPU:	PowerVR SGX540
RAM:	1GB
Weight:	344 g (12.1 oz)
Dimensions:	194 mm (7.6 in) (h) 122 mm (4.8 in) (w) 10.5 mm (0.41 in) (d)
Screen size:	178 mm (7.0 in)
Resolution:	1024×600
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 (Non-removable)
Peripherals:	capacitive touchscreen, proximity & light sensors, 3-axis accelerometer, additional 3-axis gyroscope, digital compass
CM supported:	9, 10, 10.1, 10.2, 11

How to Install CyanogenMod on the Samsung Galaxy Tab 2 7.0 (GSM) (p3100)

Note: DISCLAIMER

1 Important Notes
2 Installing a custom recovery
3 Installing CyanogenMod from recovery

Important Notes

WARNING: Device specific builds are discontinued!

Please use “espresso3g” builds in future.

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: 9bf4e927ddeb55a98bc57cb81bbb6366
Power off the Galaxy Tab 2 7.0 (GSM) and connect the USB adapter to the computer but not to the Galaxy Tab 2 7.0 (GSM), yet.
Boot the Galaxy Tab 2 7.0 (GSM) into download mode. Hold Volume Down & Power. 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 Vol Up & Power.
The Galaxy Tab 2 7.0 (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.
Place the CyanogenMod .zip package, as well as any optional .zip packages, on the root of /sdcard:
- Using adb: adb push filename.zip /sdcard/
Note: You can copy the .zip packages to your device using any method you are familiar with. The adb method is used here because it is universal across all devices and works in both Android and recovery mode. If you are in recovery mode, you may need to ensure /sdcard (sometimes called Internal Storage) is mounted by checking its status in the Mounts menu. If you have booted regularly, USB debugging must be enabled.
If you are not already in recovery, boot to recovery mode now.
- Hold Vol Up & Power.
In Team Win Recovery Project, select menu choices by tapping on the appropriately labelled button.
Optional (Recommended): Select the Backup button to create a backup.
Select Wipe and then Factory Reset.
Select Install.
Navigate to /sdcard and select the CyanogenMod .zip package.
Follow the on-screen notices to install the package.
Optional: Install any additional packages you wish using the same method (if you are installing multiple packages, install CyanogenMod first and then install any subsequent packages on top of it).
Once installation has finished, return to the main menu and select Reboot, then System. The device will now boot into CyanogenMod.

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 (GSM) (p3100)

Introduction

These instructions will hopefully assist you to start with a stock Galaxy Tab 2 7.0 (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 (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 (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

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

$ source build/envsetup.sh
$ breakfast p3100

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

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 p3100 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/p3100/cm_p3100-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-p3100.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-p3100.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.

Samsung Galaxy Tab (P1000L) (p1l)

Cyanogenmod ROM Samsung Galaxy Tab (P1000L) (p1l)

Quick Info

Download CyanogenMod

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

Main sections for Samsung Galaxy Tab (P1000L) (“p1l”)

Information about Samsung Galaxy Tab (P1000L) (“p1l”)
CyanogenMod install guide for Samsung Galaxy Tab (P1000L) (“p1l”)
Build CyanogenMod and CyanogenMod Recovery guide

Note: Support Status

Notes

This guide applies to a Samsung Galaxy Tab (P1000L) on the stock 2.3 release.

Special boot modes

Download: Volume Down

Source code

Device	http://www.github.com/cyanogenmod/android_device_samsung_p1l
Kernel	http://www.github.com/cyanogenmod/android_kernel_samsung_p1

**Galaxy Tab (P1000L) Specifications**

Codename:	p1l
Vendor:	Samsung
Manufacturer:	samsung
Type:	tablet
GSM freq:	850 900 1800 1900 MHz GSM/GPRS/EDGE 900 1900 2100 MHz UMTS/HSPA
Platform:	Samsung S5PC110
CPU:	1 GHz single-core Hummingbird
GPU:	PowerVR SGX540
RAM:	512MB
Weight:	380 g (13.4 oz)
Dimensions:	190 mm (7.48 in) (h) 121 mm (4.76 in) (w) 12 mm (0.47 in) (d)
Screen size:	178 mm (7.0 in)
Resolution:	1024×600
Screen density:	169 PPI
Internal storage:	16/32GB
SD Card:	up to 32GB
Bluetooth:	3.0
Wi-Fi:	802.11 b/g/n
Main camera:	3.15MP w/ LED flash
Secondary camera:	1.3MP
Power:	4000 mAh (Non-removable)
CM supported:	9, 10
Latest CM version:	jellybean

How to Install CyanogenMod on the Samsung Galaxy Tab (P1000L) (p1l)

Note: DISCLAIMER

1 Important Notes
2 Installing a custom recovery
3 Installing CyanogenMod from recovery

Important Notes

This guide applies to a Samsung Galaxy Tab (P1000L) on the stock 2.3 release.

Installing a custom recovery

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: 8d7fa1f49fdc3e678e746ad64e37a9cc
Power off the Galaxy Tab (P1000L) and connect the USB adapter to the computer but not to the Galaxy Tab (P1000L), yet.
Boot the Galaxy Tab (P1000L) into download mode. Volume Down 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 --kernel zImage --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.

Note: this device has an initramfs recovery, meaning recovery is actually packaged inside a kernel image. Substitute the filename of the kernel/recovery combo that you downloaded in place of zImage above.
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.
The Galaxy Tab (P1000L) 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.

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 (P1000L) (p1l)

Introduction

These instructions will hopefully assist you to start with a stock Galaxy Tab (P1000L), 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 (P1000L)
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 (P1000L) (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 jellybean

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 p1l

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

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 p1l 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/p1l/cm_p1l-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-10-20161224-UNOFFICIAL-p1l.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-10-20161224-UNOFFICIAL-p1l.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.

Samsung Galaxy Tab (P1000N) (p1n)

Cyanogenmod ROM Samsung Galaxy Tab (P1000N) (p1n)

Quick Info

Download CyanogenMod

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

Main sections for Samsung Galaxy Tab (P1000N) (“p1n”)

Information about Samsung Galaxy Tab (P1000N) (“p1n”)
CyanogenMod install guide for Samsung Galaxy Tab (P1000N) (“p1n”)
Build CyanogenMod and CyanogenMod Recovery guide

Note: Support Status

Notes

This guide applies to a Samsung Galaxy Tab (P1000N) on the stock 2.3 release.

Special boot modes

Download: Volume Down

Source code

Device	http://www.github.com/cyanogenmod/android_device_samsung_p1n
Kernel	http://www.github.com/cyanogenmod/android_kernel_samsung_p1

**Galaxy Tab (P1000N) Specifications**

Codename:	p1n
Vendor:	Samsung
Manufacturer:	samsung
Type:	tablet
GSM freq:	850 900 1800 1900 MHz GSM/GPRS/EDGE 900 1900 2100 MHz UMTS/HSPA
Platform:	Samsung S5PC110
CPU:	1 GHz single-core Hummingbird
GPU:	PowerVR SGX540
RAM:	512MB
Weight:	380 g (13.4 oz)
Dimensions:	190 mm (7.48 in) (h) 121 mm (4.76 in) (w) 12 mm (0.47 in) (d)
Screen size:	178 mm (7.0 in)
Resolution:	1024×600
Screen density:	169 PPI
Internal storage:	16/32GB
SD Card:	up to 32GB
Bluetooth:	3.0
Wi-Fi:	802.11 b/g/n
Main camera:	3.15MP w/ LED flash
Secondary camera:	1.3MP
Power:	4000 mAh (Non-removable)
CM supported:	9, 10
Latest CM version:	jellybean

How to Install CyanogenMod on the Samsung Galaxy Tab (P1000N) (p1n)

Note: DISCLAIMER

1 Important Notes
2 Installing a custom recovery
3 Installing CyanogenMod from recovery

Important Notes

This guide applies to a Samsung Galaxy Tab (P1000N) on the stock 2.3 release.

Installing a custom recovery

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: 44288023d96f6f91a1d85c5880dd3d3e
Power off the Galaxy Tab (P1000N) and connect the USB adapter to the computer but not to the Galaxy Tab (P1000N), yet.
Boot the Galaxy Tab (P1000N) into download mode. Volume Down 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 --kernel zImage --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.

Note: this device has an initramfs recovery, meaning recovery is actually packaged inside a kernel image. Substitute the filename of the kernel/recovery combo that you downloaded in place of zImage above.
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.
The Galaxy Tab (P1000N) 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.

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 (P1000N) (p1n)

Introduction

These instructions will hopefully assist you to start with a stock Galaxy Tab (P1000N), 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 (P1000N)
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 (P1000N) (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 jellybean

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 p1n

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

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 p1n 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/p1n/cm_p1n-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-10-20161224-UNOFFICIAL-p1n.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-10-20161224-UNOFFICIAL-p1n.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.

Samsung Galaxy Tab (CDMA) (p1c)

Cyanogenmod ROM Samsung Galaxy Tab (CDMA) (p1c)

Quick Info

Download CyanogenMod

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

Main sections for Samsung Galaxy Tab (CDMA) (“p1c”)

Information about Samsung Galaxy Tab (CDMA) (“p1c”)
CyanogenMod install guide for Samsung Galaxy Tab (CDMA) (“p1c”)
Build CyanogenMod and CyanogenMod Recovery guide

Note: Support Status

Notes

This guide applies to a Samsung Galaxy Tab (CDMA) on the stock 2.3 release. https://goo.im/devs/cmwiki has files for p1c. Search in /p1/p1c for the CDMA Tab radio files, etc

Special boot modes

Download: Volume Down

Source code

Device	http://www.github.com/cyanogenmod/android_device_samsung_p1c
Kernel	http://www.github.com/cyanogenmod/android_kernel_samsung_galaxytab-cdma

**Galaxy Tab (CDMA) Specifications**

Codename:	p1c
Also known as:	SCH-I800, SPH-P100
Vendor:	Samsung
Manufacturer:	samsung
Release date:	2010 November 11 (USA – Verizon) 2010 November 14 (USA – Sprint)
Carrier:	Verizon Sprint
Type:	tablet
CDMA freq:	800 1900 MHz CDMA 2000 MHz 1xEV-DO
Platform:	Samsung Exynos 3
CPU:	1 GHz single-core Cortex A8
GPU:	PowerVR SGX540
RAM:	512MB
Weight:	380 g (13.4 oz)
Dimensions:	190 mm (7.48 in) (h) 121 mm (4.76 in) (w) 12 mm (0.47 in) (d)
Screen size:	178 mm (7.0 in)
Resolution:	1024×600
Screen density:	169 PPI
Internal storage:	16/32GB
SD Card:	up to 32GB
Bluetooth:	3.0
Wi-Fi:	802.11 a/b/g/n
Main camera:	3.15MP w/ LED flash
Secondary camera:	1.3MP
Power:	4000 mAh (Non-removable)
CM supported:	9, 10
Latest CM version:	jellybean

How to Install CyanogenMod on the Samsung Galaxy Tab (CDMA) (p1c)

Note: DISCLAIMER

1 Important Notes
2 Installing a custom recovery
3 Installing CyanogenMod from recovery

Important Notes

This guide applies to a Samsung Galaxy Tab (CDMA) on the stock 2.3 release. https://goo.im/devs/cmwiki has files for p1c. Search in /p1/p1c for the CDMA Tab radio files, etc

Installing a custom recovery

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: da99fab9969ce90402313f72206577cd
Power off the Galaxy Tab (CDMA) and connect the USB adapter to the computer but not to the Galaxy Tab (CDMA), yet.
Boot the Galaxy Tab (CDMA) into download mode. Volume Down 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 --kernel zImage --recovery recovery.bin --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.
The Galaxy Tab (CDMA) 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.

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 (CDMA) (p1c)

Introduction

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

What you’ll need

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

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 jellybean

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 p1c

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

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 p1c 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/p1c/cm_p1c-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-10-20161224-UNOFFICIAL-p1c.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-10-20161224-UNOFFICIAL-p1c.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 Amaze 4G (ruby)

Quick Info

Main sections for HTC Amaze 4G (“ruby”)

Special boot modes

Source code

How to Install CyanogenMod on the HTC Amaze 4G (ruby)

Contents

Unlocking the bootloader

Installing a custom recovery using fastboot

Installing CyanogenMod from recovery

How To Build CyanogenMod For HTC Amaze 4G (ruby)

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

Installing a custom recovery using fastboot

Install CyanogenMod

Success! So….what’s next?

Cyanogenmod ROM Sony Ericsson Xperia X10 Mini (robyn)

Quick Info

Main sections for Sony Ericsson Xperia X10 Mini (“robyn”)

Notes

Source code

How To Build CyanogenMod For Sony Ericsson Xperia X10 Mini (robyn)

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 LG Thrill 4G (p925)

Quick Info

Main sections for LG Thrill 4G (“p925”)

Notes

Source code

How to Install CyanogenMod on the LG Thrill 4G (p925)

Contents

Important Notes

Installing CyanogenMod from recovery

How To Build CyanogenMod For LG Thrill 4G (p925)

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

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