Database Users

[GUIDE] Compile CM9 for the Thunderbolt

The purpose of this guide is to show the steps required to compile CM9 specifically for the Thunderbolt. This may be adapted for other ROMs in the future. However, I will not describe how to setup your development environment as that information changes based on distribution versions and has been done many times over. A few good references are here, with an example of mine at the end of this post:
CyanogenMod Wiki - Learning to Build CyanogenMod
CyanogenMod Build Guide for Nexus 7 (Use as an example)
My goal is to aid others in development as the steps to get everything working on the Thunderbolt are not straight-forward unless you know what they are. Even though I had plenty of sources when I started, I still had to spend many hours to get them working. The camera and radio need some extra steps, but those are now streamlined for both my benefit and everyone else's.
I added these steps on gist.github as scripts, although I have not tested them as such. It would be best if you do each line at a time to better understand what you're doing.
Build CM9 Thunderbolt - First Time Only
Build CM9 Thunderbolt - Subsequent Builds
For the first build only:
Code:
mkdir android
cd android/
repo init -u git://github.com/CyanogenMod/android.git -b ics
mkdir -p .repo/local_manifests
wget https://raw.github.com/jblack248/android/ics/local_manifest.xml -O .repo/local_manifests/cm_mecha.xml
repo sync
# Cherry-pick frameworks/base/libs/ui commit from Twisted
cd frameworks/base/ && git fetch http://review.cyanogenmod.com/CyanogenMod/android_frameworks_base refs/changes/85/13285/8 && git cherry-pick FETCH_HEAD && cd ../..
# checkout branch in local trees
repo start ics device/htc/common device/htc/mecha device/htc/msm7x30-common hardware/qcom/camera kernel/htc/mecha-3.0 packages/apps/Camera vendor/htc/mecha vendor/htc/mecha-radio
# download prebuilts
cd vendor/cm/
./get-prebuilts
cd ../..
. build/envsetup.sh
lunch cm_mecha-userdebug
# Make build then rebuild with radio - read script in vendor/htc/mecha-radio if interested
mka bacon && . vendor/htc/mecha-radio/liquid_telephony.sh
For subsequent builds:
Code:
repo sync
# Cherry-pick frameworks/base/libs/ui commit from Twisted
cd frameworks/base/ && git fetch http://review.cyanogenmod.com/CyanogenMod/android_frameworks_base refs/changes/85/13285/8 && git cherry-pick FETCH_HEAD && cd ../..
. build/envsetup.sh
lunch cm_mecha-userdebug
# Make build then rebuild with radio - read script in vendor/htc/mecha-radio if interested
mka bacon && . vendor/htc/mecha-radio/liquid_telephony.sh
How I set up the build environment on Xubuntu 13.04 64-bit - Gist.github:
Code:
echo "Install Android Development Tools and Dependencies"
sudo apt-get install -y android-tools-adb android-tools-fastboot git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.8-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev lib32z1-dev pngcrush schedtool g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline-gplv2-dev gcc-multilib g++-multilib schedtool libc6-dev-i386 ccache
echo "Link zconf.h to fix Android compile issues in 13.04"
ln -s /usr/include/x86_64-linux-gnu/zconf.h /usr/include
echo "Installing Development Tools"
sudo apt-get install -y meld gedit-plugins git gitk gtkhash
echo "Customize .bashrc"
echo "export USE_CCACHE=1" >> ~/.bashrc
echo "ccache -M 20G > /dev/null 2>&1" >> ~/.bashrc
# these locations will be different for you, depending on where you installed the SDK
# echo "export PATH=${PATH}:~/Documents/Development/bin:~/Documents/Development/adt-bundle-linux-x86_64/sdk/tools:~/Documents/Development/adt-bundle-linux-x86_64/sdk/platform-tools"

Just a note; for the sake of newbs you may want to include instructions on getting the repo script as it doesn't just work OOB.
Code:
remote object '/system/lib/libcamera.so' does not exist
remote object '/system/lib/libcneapiclient.so' does not exist
remote object '/system/lib/libcneqmiutils.so' does not exist
remote object '/system/etc/firmware/a225p5_pm4.fw' does not exist
remote object '/system/etc/firmware/a225_pfp.fw' does not exist
remote object '/system/etc/firmware/a225_pm4.fw' does not exist
remote object '/system/etc/firmware/a300_pfp.fw' does not exist
remote object '/system/etc/firmware/a300_pm4.fw' does not exist
I got this when running ./extract-files.sh although all other files extracted fine, and I'm assuming at the very least libcamera.so is 100% necessary.

You are correct, libcamera.so is especially needed. You can either copy the files manually or modify the extract-files.sh script and extract the ROM zip to a folder to copy the files locally instead of using ADB. Change 'adb pull' to 'cp' and modify the path of the first parameter to the ROM zip folder.
I referenced a couple other guides that help you get the development set up, even the repo bin. That information changes, has been done over many times, and isn't as useful in the long run unless I micro-manage this guide. If I get a chance I might flesh this out a little, but I'm not sure how much of a desire there is for this. I'll help where I can, though.

I updated the OP with fixes to make sure everything works automatically. You no longer have to use the extract-files.sh script (or setup adb) since I made a vendor repo to include all of those files for you. Thanks to santod and others for pointing out a number of problems.
Note: As of 2013-06-29 CM9 is in a broken state as we're getting the kernel and stock OTA blobs to work properly.

repo snapshot

Lets assume we've fetched the source tree
Code:
repo init -u git://github.com/omnirom/android.git -b android-4.4 && repo sync
.. committed some local project changes and then saved a snapshot
Code:
repo manifest -o ~/snapshot.xml -r
Will another 'repo sync' wipe the snapshot from our local tree or can we still revert to that snapshot later on?
Where to find reference to the snapshot in the local tree?

aguaz said:
Lets assume we've fetched the source tree
Code:
repo init -u git://github.com/omnirom/android.git -b android-4.4 && repo sync
.. committed some local project changes and then saved a snapshot
Code:
repo manifest -o ~/snapshot.xml -r
Will another 'repo sync' wipe the snapshot from our local tree or can we still revert to that snapshot later on?
Where to find reference to the snapshot in the local tree?
Click to expand...
Click to collapse
I would have expected that the snapshot build would be reproducible even after a 'repo sync' if:
- the local changes are committed to local topic/feature branches on your local clone(s) of the omnirom git repo(s)
My impression is, if you want to be sure that your manifest snapshot remains relevant, clone the upstream git repo(s) and commit your changes to your clone on a local branch. Use a local_manifest to specify your branch/revision rather than the default branch/revision that sync'ing with upstream will change or reset.
Hopefully someone else will offer a definitive answer.

Meanwhile I'm using btrfs copy-on-write feature to store snapshots:
Before syncing make a reference of the current-tree with
Code:
cp -a --reflink=always old-tree/ new-tree/
This "copy" won't take up disk space other than for the references themselves. You can now sync new-tree/ and always go back to the old one.
I guess it's pretty similar to using btrfs' snapshot feature.

Miui 8

Miui 8 patch rom release, can someone port it for Nexus 4?
https://github.com/MiCode/patchrom/tree/marshmallow

I need it too...

You should contact to miui support forum or XDA devs, I hope they can build miui 8 for nexus 4

@Trickster22
Install Ubuntu.
Install Java
Guide to configure android SDK
Guide to configure repository:
Open terminal
Code:
mkdir -p ~/bin
Code:
PATH=~/bin:$PATH
Code:
cd ~/bin
Code:
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
Code:
chmod a+x ~/bin/repo
Code:
mkdir ~/patchrom
Code:
cd ~/patchrom
Code:
repo init -u git://github.com/MiCode/patchrom.git -b marshmallow
Now you'll have to configure git. Run following commands in terminal
Code:
git config --global user.email ENTER_YOUR_EMAIL_ID_HERE
Code:
git config --global user.name ENTER_YOUR_REAL_NAME_HERE
Code:
repo init -u git://github.com/MiCode/patchrom.git -b marshmallow
Code:
repo sync
Wait......
after, Install the latest version of Fake nexus (marshmallow), reboot to device in mode recovery (TWRP).
PS.: After you finish generating the stockrom.zip of fake nexus, do the same for cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J5-mako.zip
Reboot your device for recovery, use this comand to gerate stockrom.zip and metadata folder:
Code:
/home/"YOUR-USER-NAME-UBUNTU"/patchrom/tools/releasetools/ota_target_from_phone -r
Sende me stockrom.zip and metadata folder
Source: http://forum.xda-developers.com/android/software/guide-build-port-miui-rom-to-device-t3250984

Dio_S said:
@Trickster22
Install Ubuntu.
Install Java
Guide to configure android SDK
Guide to configure repository:
Open terminal
Code:
mkdir -p ~/bin
Code:
PATH=~/bin:$PATH
Code:
cd ~/bin
Code:
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
Code:
chmod a+x ~/bin/repo
Code:
mkdir ~/patchrom
Code:
cd ~/patchrom
Code:
repo init -u git://github.com/MiCode/patchrom.git -b marshmallow
Now you'll have to configure git. Run following commands in terminal
Code:
git config --global user.email ENTER_YOUR_EMAIL_ID_HERE
Code:
git config --global user.name ENTER_YOUR_REAL_NAME_HERE
Code:
repo init -u git://github.com/MiCode/patchrom.git -b marshmallow
Code:
repo sync
Wait......
after, Install the latest version of Fake nexus (marshmallow), reboot to device in mode recovery (TWRP).
PS.: After you finish generating the stockrom.zip of fake nexus, do the same for cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J5-mako.zip
use this comand to gerate stockrom.zip and metadata folder:
Code:
/home/"YOUR-USER-NAME-UBUNTU"/patchrom/tools/releasetools/ota_target_from_phone -r
Sende me stockrom.zip and metadata folder
Source: http://forum.xda-developers.com/android/software/guide-build-port-miui-rom-to-device-t3250984
Click to expand...
Click to collapse
Thank you sir for this valuable info/guide but I have a weak machine for Ubuntu like only 2 GB ram. This is why I was requesting others to build miui.

Trickster22 said:
Thank you sir for this valuable info/guide but I have a weak machine for Ubuntu like only 2 GB ram. This is why I was requesting others to build miui.
Click to expand...
Click to collapse
You should just generate the stockrom.zip + metadata and send me, I can do it, because I do not have the device

what ıs thıs ?

hasanben35 said:
what ıs thıs ?
Click to expand...
Click to collapse
For me to compile miui, I need the stockrom.zip plus the metadata folder generated by the patchrom, this guide shows how.
Sorry mt english

hım how long does it take

hasanben35 said:
hım how long does it take
Click to expand...
Click to collapse
This process should take around 1 hour if you already have Ubuntu installed and configured

multı rom nıtrogen os 7.1.1 and flyme ınstalled flyme remove ubuntu ınstall after _?

hasanben35 said:
mult? rom n?trogen os 7.1.1 and flyme ?nstalled flyme remove ubuntu ?nstall after _?
Click to expand...
Click to collapse
Ubuntu in PC "Desktop"

oh my god no no no waıtıng rom sorry ubuntu ınstall pc no

Okay, I'll make those files. Where should I send it?

[Guide] Build MoKee Rom 7.1.2 For Samsung T700/T705/T800/T805

How To Build MoKee Rom For Exynos5420 Device (7.1.2)​Support Device :
HTML:
klimtwifi # Samsung T700
klimtlte # Samsung T705
chagallwifi # Samsung T800
chagalllte # Samsung T805
chagallltetmo # Samsung T807T
ha3g # Samsung Note3 (N900)
Step 1: Setting Up A Compile Environment
You must have a 64-bit environment.
A Linux computer should have 8 GB RAM or more, otherwise build errors may occur.
Ubuntu 16.04
These instructions should work for other version of Ubuntu and most other Debian-based systems.
Install build packages
Open a terminal (ctrl + alt + t). First install the necessary packages; copy paste the code below and hit enter.
HTML:
sudo apt-get update
sudo apt-get install git ccache automake lzop bison gperf build-essential zip curl zlib1g-dev zlib1g-dev:i386 g++-multilib python-networkx libxml2-utils bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev squashfs-tools pngcrush schedtool dpkg-dev liblz4-tool make optipng maven bc pngquant imagemagick yasm libssl-dev
sudo apt-get install openjdk-8-jdk
HTML:
mkdir -p ~/bin
mkdir -p ~/mokee
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
Add bin to PATH
HTML:
echo "export PATH=~/bin:$PATH" >> ~/.bashrc
Configure git:
HTML:
git config --global user.email "[email protected]"
git config --global user.name "Your Name"
Move to build directory and sync the source code:
HTML:
cd ~/mokee
repo init -u https://github.com/Cyborg2017/android_mokee.git -b mokee-7.1.2
repo sync -j8 -f --no-clone-bundle
Let's configure ccache too. It will reduce the build time to 40% after first build
HTML:
echo "export USE_CCACHE=1" >> ~/.bashrc
~/mokee/prebuilts/misc/linux-x86/ccache/ccache -M 25G
25G means it will use upto 25 gb of disk space for ccaching. Atleast 10 gb is recommended. But if you want to compile for more devices, use more space for ccache.
Step 2: Compiling For Your Device
# MoKee Rom For Samsung Exynos5420 Chips Device
============================================================
To initialize your local repository using the MoKee trees, use a command like this:
HTML:
repo init -u https://github.com/Cyborg2017/android_mokee.git -b mokee-7.1.2
Then to sync up:
HTML:
repo sync
Start Work
-------------------------------------------------------------
To work faster, we introduced a new build script to help you start compiling.
First, go to the root path of your project. We assume that your source is under
(/mokee):
HTML:
cd /mokee
then feel free to use the build script:
HTML:
. build/envsetup.sh
lunch mk_klimtwifi # T700
lunch mk_klimtlte # T705
lunch mk_chagallwifi # T800
lunch mk_chagalllte # T805
lunch mk_chagallltetmo # T807T
lunch mk_ha3g # N900
mka bacon -j8
The script is interactive so everything else is self-explanatory.
Source:
https://github.com/Cyborg2017/android_mokee
https://github.com/Cyborg2017/android_device_samsung_exynos5420-common
https://github.com/Cyborg2017/android_device_samsung_chagalllte
https://github.com/Cyborg2017/android_device_samsung_chagallwifi
https://github.com/Cyborg2017/android_device_samsung_klimtlte
https://github.com/Cyborg2017/android_device_samsung_klimtwifi
https://github.com/Cyborg2017/android_device_samsung_chagallltetmo
https://github.com/Cyborg2017/android_device_samsung_ha3g
https://github.com/Cyborg2017/android_kernel_samsung_exynos5420
Thanks:
MoKee Rom Team: https://github.com/MoKee
Exynos5420 Team: https://github.com/exynos5420
LineageOs Team: https://github.com/LineageOS

Building LOS 15.0

Before starting, yes, I know there is a project already.
Hello everyone. I've been following this step by step:
https://wiki.lineageos.org/devices/harpia/build
Only I have replaced this line:
Code:
repo init -u https://github.com/LineageOS/android.git -b cm-14.1
For this one:
Code:
repo init -u git://github.com/LineageOS/android.git -b lineage-15.0
The problem is, I get loads of fatal errors when running:
Code:
repo sync
What am I doing wrong?
Thank you.-

Seems the error was due to a bad internet connection.

Hope it works out for you now. Good luck.

i tried too few weeks ago. can you post your roomservice.xml?