[ROM][CM] KitKang Rom CM11 Kangs (**Building Guide Now Included!!)

1. Make sure you are unlocked and running the latest version of ClockworkMod Recovery (Either Touch or Non-Touch is fine). If you do not know how to unlock your bootloader or install recovery, follow these steps.
2. Make sure you are running the latest firmware version. If you do not know what firmware version you are running, you can check in Settings in the "About Phone" tab. Currently, the latest firmware is VRBMF1, and a recovery flashable of the firmware can be found here. To install, simply reboot to ClockworkMod and flash the zip file.
3. Backup everything you need. All of your files will be deleted! To backup your apps, I recommend using Helium. It is very easy and straightforward.
4. Download the ROM and G-Apps from the links provided and copy them over to your phone via USB cable.
5. Reboot to recovery. To do so, either use the built in reboot option to recovery in ROMs such as CyanogenMod, or power down and hold Power + Home + Vol Up and you should be in recovery.
6. Wipe the data, system, cache, and dalvik cache partitions in recovery. (Dalvik wipe is located in Advanced Settings)
7. Install the ROM and G-Apps files
8. Reboot and setup your phone!

Click to expand...

Click to collapse

1. Download the ROM and G-Apps from the links provided and copy them over to your phone via USB cable.
2. Reboot to recovery. To do so, either use the built in reboot option to recovery in ROMs such as CyanogenMod, or power down and hold Power + Home + Vol Up and you should be in recovery.
3. Wipe the cache and dalvik cache partitions in recovery. (Dalvik wipe is located in Advanced Settings)
4. Install the ROM and G-Apps files
5. Reboot!

Click to expand...

Click to collapse

This is a guide demonstrating how to build KitKang for yourself on Mac. I am not responsible for anything you do to your computer or your phone as a result of following this guide. Before building, I would recommend that you have at least a little knowledge of Terminal, and a powerful computer. AOSP takes up a lot of resources, and even my i7 Ivy Bridge build with 16GB RAM and an SSD takes almost an hour to build. The AOSP code takes up a lot of space, so I recommend AT LEAST 150GB free space, just to be safe. This guide involves installing specific packages to build AOSP. To install these packages, we will use Homebrew. You will also need XCode to build. If you do not have these installed, refer to the beginning of the guide. If you already have these installed for some reason, skip the first section for installing XCode and Homebrew.

Click to expand...

Click to collapse

Installing XCode/Homebrew

• Download and install XCode from the Mac App Store. You will need an Apple account to do this.
• After downloading and installing XCode, you will need the Command Line Tools. These can be installed by opening a Terminal window and entering:
  Code:

  xcode-select --install

• After entering this, hit return and a box should pop up asking you if you want to install Command Line Tools. Click yes, and wait for it to install.
• Now, make sure you have the latest Java Runtime. You do this in Terminal by entering a command and going through an installation process. Enter the command
  Code:

  java

• With the Command Line Tools and Java installed, we can now install Homebrew. To do so, open Terminal again and enter the following:
  Code:

  ruby -e "$(curl -fsSL https://raw.github.com/mxcl/homebrew/go/install)"

• Make sure Homebrew is installed and works correctly by running
  Code:

  brew doctor

• If you got errors in the previous command, try googling to see if there is something else you need. If you can run the command without errors, you are good to go!
• We must now move the SDK so the build recognizes what to use. To do this, run the following commands in Terminal
  
  Code:

  sudo mkdir /Developer

  Code:

  sudo mkdir /Developer/SDKs

  Code:

  sudo cp -r /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk /Developer/SDKs/MacOSX.sdk

• NOTE: You need superuser permissions to run the previous 3 commands.
• Now, in Terminal, type
  
  Code:

  nano ~/.bash_profile

• If you get a no file found error, then run
  Code:

  nano -w ~/.bash_profile

• You should get a screen with some text. Scroll to the bottom using the arrow keys until there's just blank spaces, and paste the following code
  
  Code:

  export BUILD_MAC_SDK_EXPERIMENTAL=1

• Save the file using ctrl-x and clicking yes and enter
• Restart Terminal to make the changes take effect
• With Homebrew now installed, we can continue to downloading required build packages!

Click to expand...

Click to collapse

Click to expand...

Click to collapse

Installing Required Packages

• Now we will install packages required to build the AOSP source. This can be done with the Terminal command
  Code:

  brew install git coreutils findutils gnu-sed gnupg pngcrush repo

• With these packages installed, we need to make some symlinks so that OSX knows which files to use, and doesn't mess up the build. To do this, enter
  Code:

  ln -s /usr/local/bin/gfind /usr/local/bin/find && ln -s /usr/local/bin/gsed /usr/local/bin/sed

• With these packages installed, we are now ready to create a build environment and download the AOSP source.

Click to expand...

Click to collapse

Click to expand...

Click to collapse

Preparing the Build Environment and Downloading the Source

• First, we need to create a dedicated workspace for our AOSP code. This can be done in Terminal by entering
  Code:

  hdiutil create -type SPARSE -fs "Case-sensitive Journaled HFS+" -size 120g -volname "android" -attach ~/Desktop/Android

• This will create the workspace image on our desktop. To move it, simply drag and drop in Finder to the location you want.
• Now, locate the workspace in Finder and double click it to mount it
• NOTE: If you moved your workspace to a different directory, you will have to use the path to that directory in the previous step.
• Next, from within Terminal, locate the directory by typing
  Code:

  cd /Volumes/android

• Now that we are in the working directory, it is time to download the Android Source. This is done by entering the following command
  Code:

  repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0 && repo sync && say 'finished'

• Wait for the download to finish. Depending on your connection, it can take a long time, so get comfortable.
• When the download finishes and you can see all of the source folders in your directory, it is time to download the S3 specific files. To do this, we need to edit the roomservice.xml. However, this file is hidden. We can access it by entering the following in Terminal
  Code:

  open -a TextEdit .repo/local_manifests/roomservice.xml

• You should get a blank file in TextEdit. Enter the following code as is here
  Code:

  <?xml version="1.0" encoding="UTF-8"?>
  <manifest>
    <project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" revision="cm-11.0" />
    <project name="CyanogenMod/android_device_samsung_d2vzw" path="device/samsung/d2vzw" remote="github" />
    <project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
    <project name="CyanogenMod/android_device_samsung_msm8960-common" path="device/samsung/msm8960-common" revision="cm-10.2" />
    <project name="CyanogenMod/android_device_samsung_d2-common" path="device/samsung/d2-common" remote="github" />
    <project name="CyanogenMod/android_kernel_samsung_d2" path="kernel/samsung/d2" remote="github" />
    <project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
  </manifest>

• Save and close the file, and again run
  Code:

  repo sync

• With the S3 specific files downloaded, we need to download the CyanogenMod specific app files. This can be done by running
  Code:

  ./vendor/cm/get-prebuilts

• With this done, we need to download the cherrypicks specific to the S3. Eventually, these will not be needed, but as CyanogenMod 11 is still in beta, it is needed for now. Because the cherrypicks are often being merged, and new ones created, the kind folks at CyanogenMod have created a Google Document with a list of the latest commits. This is located here. NOTE: This document does not include any cherrypicks that I may include for features. By using these cherrypicks, you are installing everything needed to make the ROM as stable as possible. I may occasionally include other cherrypicks that I find enhance features. Inside the document, scroll down to the '# repopicks' section and continue scrolling past the commit messages. At the bottom, you will see a section titled 'Combined'. This will have a command such as
  Code:

  repopick -s s <List of commit hashes>

• You could simply copy this command and paste it into a Terminal window, but that would put the cherrypicks on new branches of the source, which could cause problems with resyncing the source. I would recommend copying only the commit numbers.
• In Terminal, run the command
  Code:

  . build/envsetup.sh

• Run the repopick command, adding the commit numbers to the end. Here is an example
  Code:

  repopick 53075 53131 53302 53309 53356 53445 53528 53595 53603 53604 53637 53964 54197 54198 54219 53468 54251 54274 54277

• If the commits do not all merge correctly, you will get what is called a merge conflict. This is because one or more of the commits does not play nice with the CyanogenMod code. Make sure you have the latest code by resyncing, and also make sure you have the latest cherrypicks. If the command still fails, wait a few hours because the document probably just hasn't been updated.
• Once you get all of the commits merged correctly, it is time to build!

Click to expand...

Click to collapse

Click to expand...

Click to collapse

Building the Source

• Before building, if you have extra space on your hard drive, you can optionally use CCache to speed up your build a bit. Enable this from inside the working directory by using
  Code:

  export USE_CCACHE=1 && prebuilt/darwin-x86/ccache/ccache -M 20G

• You may also need to change the ulimit to support building. On OSX 10.9, I experienced errors stating that I had too many files open, and I had to change the ulimit amount. NOTE: If you have issues, you will need to do this every time you build! Change the ulimit amount by running
  Code:

  ulimit -Hn 8192

  and
  Code:

  ulimit -Sn 8192

• Make sure your working directory is clean by running
  Code:

  make clean

• Next, initiate the build by running
  Code:

  brunch d2vzw

• If all goes well you should have a flashable zip in the out/target/product/d2vzw/ folder. Enjoy!

Click to expand...

Click to collapse

Click to expand...

Click to collapse

Updating the Source

• Later on, you may decide to build another file to see with new changes to the CyanogenMod code. Think of this as a ROM update. To do this, you will need to follow some steps. All of these steps have been completed already in this guide, so I will just be outlining them, and will not be listing everything. If you forget how to do something, consult the guide.
• Repo sync
• Apply cherrypicks
• Enable CCache (Optional)
• Set the ulimits
• Clean your working directory using
  Code:

  make clean

• Build the code using
  Code:

  brunch d2vzw

Click to expand...

Click to collapse

Click to expand...

Click to collapse