Build OS

Build Cyanogenmod

Posted by Kulani Mahadewa on March 11, 2015
Posted in: Build OS. Tagged: . Leave a comment

Guide

  1. Build CyanogenMod: 1. Getting CyanogenMod source code

  2. Build CyanogenMod: 2. Get-prebuilts requires while building

  3. Build CyanogenMod: 3. Getting device-specific code

  4. Build CyanogenMod: 4. Enable ADB on Linux to link your device and LinuxVM

  5. Build CyanogenMod: 5. How to connect your mobile device to LinuxVM

  6. Build CyanogenMod: 6. Extracting proprietary files from the device

  7. Build CyanogenMod: 7. Extracting proprietary files from an already built CyanogenMod ROM

  8. Build CyanogenMod: 8. Start Building OS…

  9. Get Root Access- Root my phone with Root Genius

Build CyanogenMod: 8. Start Building OS…

Posted by Kulani Mahadewa on February 19, 2015
Posted in: Build OS. Tagged: , , , . 5 Comments

Hi ! Let’s start building the OS 🙂 I hope you have collected all required source including pre-built, device specific code and proprietary blobs by now.

*Note: Before starting the build make sure you have enough disk space in your machine. Otherwise the build may stop suddenly with unspecified make errors. It’s good if you have 65-70GB space on your VM or Linux environment to complete a successful build.

*Note: You may need to do some work to overcome make errors which are not relating to memory issues.

At the end of a successful build, it will generate a zip file which you can use for flashing, kernel, recovery.img and etc. at the system/out directory

9zz

Here the steps to proceed for building the source.

Step 1: Turn on caching. Add following at bashrc

Command:$gedit ~/.bashrc

Add following at the end of file.
export USE_CCACHE=1
export CCACHE_DIR=/home/tharaka/android/system/prebuilts/misc/linux-x86/ccache

Step 2:Install following prerequisites required for building

Command:$sudo apt-get install bison build-essential curl flex git gnupg gperf libesd0-dev liblz4-tool libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev

Step 3:Start building with brunch command.

To enable the brunch command first run . build/envsetup.sh (here .<space>build/envetup.sh)

Command:$. build/envsetup.sh
Command:$ brunch <device name>

Command:$ brunch ancora

1

Some instances during building…

2 359a9d9y9z

Done 🙂

Command :$cd $OUT

Command:$ ls

9zz

Yes we got it done !! 🙂 Lets see what we have got

go to system/out directory

@system/out/target/product/<device name> you will find the which contains the cm-11-20150218-UNOFFICIAL-ancora.zip Cyanogenmod.

9zzz 9zzzz

 

 

Cheers ! 🙂

Build CyanogenMod: 7. Extracting proprietary files from an already built CyanogenMod ROM

Posted by Kulani Mahadewa on February 11, 2015
Posted in: Build OS. Tagged: , , , , . Leave a comment

Hi ! 🙂 If you have issues in directly getting proprietary blobs from the the device, for an example while building the source if you often get make errors saying some files are missing, instead pull files from device you can obtain them from a already built CyanogenMod ROM.

4#

Step 1:

First of all find an already build Cyanogenmod ROM zip file for you device model. You can search at http://forum.xda-developers.com

Step 2:

Download the zip file and extract the source in to a directory named original

:$ mkdir -p ~/original

3

Step 3:

Now open a new terminal at the device/samsung/<device model> and execute the extract-files.sh

:$ cd ~/android/system/device/samsung/<device model>

:$ ./extract-files.sh <path to the unzip files folder>

Ex.

:$ cd ~/android/system/device/samsung/ancora

:$ ./extract-files.sh /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora

1

2

Full Log:

tharaka@tharaka-ubuntu14:~/android/system$ cd ~/android/system/device/samsung/ancoratharaka@tharaka-ubuntu14:~/android/system/device/samsung/ancora$ ./extract-files.sh /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora
./extract-files.sh: line 1: #!/bin/sh: No such file or directory
Found DEVICE=ancora VENDOR=samsung
have argument /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora
test path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora
test path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora found
Function to perform the extraction from either adb or paths
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system/vendor/bin/bcm4329.hcd
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system/vendor/bin/bcm4329.hcd
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//bin/rmt_storage
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//bin/rmt_storage
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//bin/rild
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//bin/rild
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//bin/radish
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//bin/radish
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//etc/firmware/vidc_720p_command_control.fw
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//etc/firmware/vidc_720p_command_control.fw
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//etc/firmware/vidc_720p_h263_dec_mc.fw
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//etc/firmware/vidc_720p_h263_dec_mc.fw
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//etc/firmware/vidc_720p_h264_dec_mc.fw
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//etc/firmware/vidc_720p_h264_dec_mc.fw
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//etc/firmware/vidc_720p_h264_enc_mc.fw
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//etc/firmware/vidc_720p_h264_enc_mc.fw
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//etc/firmware/vidc_720p_mp4_dec_mc.fw
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//etc/firmware/vidc_720p_mp4_dec_mc.fw
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//etc/firmware/vidc_720p_mp4_enc_mc.fw
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//etc/firmware/vidc_720p_mp4_enc_mc.fw
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//etc/firmware/vidc_720p_vc1_dec_mc.fw
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//etc/firmware/vidc_720p_vc1_dec_mc.fw
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//etc/firmware/yamato_pfp.fw
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//etc/firmware/yamato_pfp.fw
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//etc/firmware/yamato_pm4.fw
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//etc/firmware/yamato_pm4.fw
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system/vendor/lib/egl/libEGL_adreno.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system/vendor/lib/egl/libEGL_adreno.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system/vendor/lib/egl/libGLESv1_CM_adreno.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system/vendor/lib/egl/libGLESv1_CM_adreno.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system/vendor/lib/egl/libGLESv2_adreno.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system/vendor/lib/egl/libGLESv2_adreno.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system/vendor/lib/egl/libq3dtools_adreno.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system/vendor/lib/egl/libq3dtools_adreno.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system/vendor/lib/egl/eglsubAndroid.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system/vendor/lib/egl/eglsubAndroid.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system/vendor/lib/egl/libGLESv2S3D_adreno.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system/vendor/lib/egl/libGLESv2S3D_adreno.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//lib/libActionShot.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//lib/libActionShot.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//lib/libakm.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//lib/libakm.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//lib/libarccamera.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//lib/libarccamera.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//lib/libaudioalsa.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//lib/libaudioalsa.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system/vendor/lib/libC2D2.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system/vendor/lib/libC2D2.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system/vendor/lib/libCB.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system/vendor/lib/libCB.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system/vendor/lib/libsc-a2xx.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system/vendor/lib/libsc-a2xx.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system/vendor/lib/libOpenVG.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system/vendor/lib/libOpenVG.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system/vendor/lib/libOpenCL.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system/vendor/lib/libOpenCL.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system/vendor/lib/libgsl.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system/vendor/lib/libgsl.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system/vendor/lib/libbt-vendor.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system/vendor/lib/libbt-vendor.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system/vendor/lib/libc2d2_z180.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system/vendor/lib/libc2d2_z180.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system/vendor/lib/libadreno_utils.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system/vendor/lib/libadreno_utils.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//lib/libcamera.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//lib/libcamera.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//lib/libcaps.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//lib/libcaps.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//lib/libgemini.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//lib/libgemini.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//lib/libmmipl.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//lib/libmmipl.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//lib/libmmjpeg.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//lib/libmmjpeg.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//lib/libmmosal.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//lib/libmmosal.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//lib/libmmparser.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//lib/libmmparser.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//lib/libOmxMp3Dec.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//lib/libOmxMp3Dec.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//lib/liboemcamera.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//lib/liboemcamera.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//lib/libPanoraMax3.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//lib/libPanoraMax3.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//lib/libs3cjpeg.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//lib/libs3cjpeg.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//lib/libseccameraadaptor.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//lib/libseccameraadaptor.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//lib/libsecjpegarcsoft.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//lib/libsecjpegarcsoft.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//lib/libsecjpegboard.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//lib/libsecjpegboard.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//lib/libsecjpeginterface.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//lib/libsecjpeginterface.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//lib/libsecril-client.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//lib/libsecril-client.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//lib/libsec-ril.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//lib/libsec-ril.so
full path /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora/system//lib/libril.so
Copying from cm-11-20141223-UNOFFICIAL-ancora: /system//lib/libril.so
Function to perform the extraction from either adb or paths
egrep: ../samsung/ancora/proprietary-files.txt: No such file or directory
Generating ../../../vendor/samsung/ancora/ancora-vendor-blobs.mk …
Generating ../../../vendor/samsung/ancora/ancora-vendor.mk …
Generating ../../../vendor/samsung/ancora/BoardConfigVendor.mk …
tharaka@tharaka-ubuntu14:~/android/system/device/samsung/ancora$ /home/tharaka/original/cm-11-20141223-UNOFFICIAL-ancora

 

Cheers ! 🙂

Build CyanogenMod: 6. Extracting proprietary files from the device

Posted by Kulani Mahadewa on January 27, 2015
Posted in: Build OS. Tagged: , , , . 1 Comment

Hi ! 🙂 I hope you have followed the 5th and 6th posts of Build CyanogenMod and ready with your device connected to the Linux VM.  Because in order to successfully extract proprietary files from the device you need to connect your device via USB cable and enable ADB on Linux.

Step 1:

Open a new terminal –> Goto device/samsung/<your device> –> Execute the extract-files.sh file

Command:$cd ~/android/system/device/samsung/ancora

Command:$ ./extract-files.sh

2

1

Step 2:

Check the new files at android/system/vendor/ancora

4

 

Yesss ! we have got new proprietary blobs extracted from the device. 🙂 🙂

Cheers ! 🙂

Build CyanogenMod: 5. How to connect your mobile device to LinuxVM

Posted by Kulani Mahadewa on January 27, 2015
Posted in: Build OS. Tagged: , , , , . Leave a comment

Hi ! 🙂 Once you have enabled ADB on Linux VM, then check whether adb detects your mobile device. If not then you have to explicitly change settings through Oracle VM Manager. I have state here the steps to proceed.

Step 1:

First plug your device to the machine. Then;
Goto -> Oracle VM VirtualBox Manager–>Select UbuntuVM (Your Linux VM) –> Settings—>USB –> Select Add filters from device at the left side panel –> Select your device from the suggestions.

0

0#
Step 2:

Restart your Linux VM (UbuntuVM)

This will install required device drivers and enable the connection between your mobile device and Linux VM.

1

2

Step 3:

Open a new terminal -> Execute adb devices command
This result on terminal will show your mobile device as a connected android device.

3
Cheers ! 🙂

Build CyanogenMod: 4. Enable ADB on Linux to link your device and LinuxVM

Posted by Kulani Mahadewa on January 26, 2015
Posted in: Build OS. Tagged: , , , , , . 1 Comment

Hi ! 🙂 I guess you have collected all required source codes by now. (If not please refer the Buidl OS guide) In order to proceed further you need to communicate with your device through ADB (Android Debug Bridge). So let’s go ahead and download Android SDK to our Linux VM and enable adb.

Step 1. Download Android SDK

  • We have a Linux environment. So get the android-sdk-r24.0.2-linux.tgz from android developer site here. Extract the files.

1

  • Goto android–>sdk—>android-sdk-linux –> tools.

You will see the android executable file. This is the Andorid SDK Manager. Execute the file.

2

  • Select Android SDK platform-tools, Build-tools and Install them. In order to get adb tool, fastboot tool these two should be installed on your machine.

3#

Step 2. Update PATH variables

  • Add path to platform-tools and tools to PATH

4

Command: $ gedit ~/.bashrc

a~

Command: $ adb

a

Note: Some required build packages are missing.

Step 3. Get required build packages

Command: $ sudo apt-get install g++-multilib

This will suggest you to add some additional packages. Install them as well.

d

New packages installed: g++-multilib gcc-multilib lib32ncurses5-dev  lib32readline-gplv2-dev  lib32z1-dev

e

Step 4. Run adb command

Now the adb is enabled 🙂 Yesss

f

Command: $ adb devices

This will check for running android devices. Seems like we have no devices currently.

g

Never mind Lets check with some android virtual devices (emulators) 🙂

Step 5. Create an emulator and run the device.

  • Create emulator using avd

Command: $ android create avd -n <given name> -t <target ID> –abi <specify CPU>

Ex: $android create avd -n TestAVD -t 1 –abi armeabi-v7a

  • Run the emulator

Command: $ emulator -avd TestAVD

i

Running Emulator……

k

Step 6. Check for running devices through ADB

Command : $ adb devices

You can see the emulator is listed under the running android devices. 🙂

l

 

Cheers ! 🙂

 

Build CyanogenMod: 3. Getting device-specific code

Posted by Kulani Mahadewa on January 25, 2015
Posted in: Build OS. Tagged: , , , , . 2 Comments

Hi ! 🙂 Once you have completed downloading cyangenmod mainline source code, next you should get the device specific configuration and kernel source. You are a lucky chap if your device is listed under the available github repositories of cyanogenmod at GitHub (https://github.com/CyanogenMod) . Then you can simply use following commands.

Run the envsetup.sh script at android/system/build folder

Command:$ source build/envsetup.sh
Command:$ breakfast [device_name]

For an example if your device is a Samsung Galaxy S3;

Command:$ source build/envsetup.sh
Command:$ breakfast i9300

In my case things became little bit different. My device here is a Samsung Galaxy W (GT-I8150). Currently CyangenMod GitHub does not contain any repository for this device. So I had to look a different way to proceed from here. With reference to the wiki page of cynaogenmod ( http://wiki.cyanogenmod.org/ ) an alternative to the breakfast command is to build an own local_manifest.xml.

Here at https://github.com/arco I found some git repositories holding device,vendor and kernel files for GT-I8150.

10

Step 1: Create the local_manifest.xml file inside .repo/localmanifests

  • Goto  android/system –> Press (Ctrl + H) to view hidden files —> .repo folder will appear

5 (ctrl +h)

  • Go inside the .repo –>  you will see two folders called mainfests and local_manifests.

6manifests folder—> contains the default.xml

default.xml : “The master list of all the git repositories that together comprise the CyanogenMod source code are defined in CyanogenMod’s default.xml manifest.” Do not change this file.

7

  • Create a new xml file called local_mainfest.xml inside local manifests folder

local_manifest.xml: Add all the new device specific dependencies to this file. This local manifest allows you to customize the list of repositories used in the copy of the source code by overriding or supplementing the default manifest. Thereby you can extend or change the repository without editing the default.xml.

9

Step 2: Add the new dependencies to the local_manifest.xml file

11


<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<remote name="arco" fetch="https://github.com/arco" />

<project path="device/samsung/ancora" name="android_device_samsung_ancora" remote="arco" revision="cm-10.1"/>
<project path="vendor/samsung/ancora" name="android_vendor_samsung_ancora" remote="arco" revision="cm-10.1"/>
<project path="kernel/samsung/samsung-kernel-msm7x30" name="samsung-kernel-msm7x30" remote="arco" revision="cm-10.1"/>
</manifest>

Step 3: Execute repo sync

Command: $ repo sync -j4

a1

  • Fetching each new repository included in the local_manifest.xml

Fetching android_device_samsung_ancora

a2

Fetching android_vendor_samsung_ancora

a3

Fetching samsung-kernel-msm7x30

a3~

  • Completed fetching and syncing repository

a5

a6

Completed syncing… See what you have got ! 🙂

Now lets have a look on what we have got new 🙂

system/device/samsung/ancora

b1

b3

 system/vendor/samsung/ancora

d1

system/kernel/samsung

c1

c2

 

Note: (Possible Errors)

When you run the envsetup.sh script at build folder and follow up breakfast command, if your device does not present in the cyanogenmod github repository you will get an error like following;

1

2

4

So,,,,,,,,,,,,,,,,,,,,

Go ahead create your own local_mainfest.xml file (Y)

Cheers !! 🙂

Build CyanogenMod: 2. Get-prebuilts requires while building

Posted by Kulani Mahadewa on January 24, 2015
Posted in: Build OS. Tagged: . Leave a comment

Hi ! 🙂 When you are done with downloading CyanogenMod source code, (Refer: Getting CyanogenMod source code ) next recommended step is to run the get-prebuilts script located at the vendor/cm directory This will install some new files under the vendor directory, which will be useful while building the source code.

1

Command: $ cd ~/android/system/vendor/cm

Command: $ ./get-prebuilts

4

 

Installing new source to vendor/cm directory –> proprietary directory

1~

 

proprietary directory contains Term.apk plus several files inside lib folder.

1~a

Inside lib folder

1~b

Cheers ! 🙂

Build CyanogenMod: 1. Getting CyanogenMod source code

Posted by Kulani Mahadewa on January 23, 2015
Posted in: Build Android, Build OS. Tagged: , , , . 1 Comment

Hi ! 🙂 If you are interested in building a fresh operating system for your Android device from CyanogenMod source code, lets start from here… First of all you need to get the required source code which will take some extra hours from your time to sync. So be patient.

Prerequisites:

  • Linux environment
  • Repo – repository management tool built on top of Git

What is CyanogenMod?

Why are we using CyanogenMod ? that because we are interested in what CyanogenMod offers which does not present in other official firmware. 🙂

I extracted the following description from CyanogenMod official web site

“CyanogenMod (pronounced sigh-AN-oh-jen-mod), is a customized, aftermarket firmware distribution for several Android devices. Based on the Android Open Source Project, CyanogenMod is designed to increase performance and reliability over Android-based ROMs released by vendors and carriers such as Google, T-Mobile, HTC, etc. CyanogenMod also offers a variety of features & enhancements that are not currently found in these versions of Android…”

Step 1: Install Repo

Repo is making the job easy for Android developers to collect the source code , since it enables downloading files from several git repositories.

  • Create a folder name bin inside home directory.

Command: mkdir -p ~/bin

0

  • Download repo

Command: curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo

8

2

  • Make it executable

Command: chmod a+x ~/bin/repo

7

  • Add ~/bin to PATH

Command: gedit ~/.bashrc

Open the ~/.bashrc add following

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

d

Step 2: Initialize CyanogenMod source repository

  • Create directory structure ~/android/system

Command: mkdir -p ~/android/system

  • Change directory

Command: cd ~/android/system/

  • Initialize repo

Command: repo init -u https://github.com/CyanogenMod/android.git -b cm-11.0

With this command it initializes the repository in the android/systems directory.

9

Step 3: Downloading the source code with sync

Next step is to sync the source of CyanogenMod. Fetching and cloning will take several hours. Until the fetching is completed you will not see source files in the directory.

Command: repo sync -j4 -c

  • Start fetching…….

aaa

  • Fetching completed –> Start checking out source

aaaaaaa

  • Completed checking out all source

b

Complete source: ~/android/system

c

 

Cheers! 🙂