[Guide][P700] How to build cm10.1 from source - Optimus L3, L5, L7 Android Development

Hey,
Since cm10.1 is comming, I want to share how to build it.
Requirments, Ubuntu and a building environment. There are a lot of threads how to set this up.
open a terminal
Code:
mkdir android
Code:
cd android
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
Code:
repo sync -j*
*= number of jobs, whit a good connection use -j4 for faster download
Code:
cd ~/android/device
Code:
mkdir lge
Code:
cd lge
Code:
git clone https://github.com/TeamHackLG/android_device_lge_p700.git p700
Code:
git clone https://github.com/TeamHackLG/android_device_lge_msm7x27a-common.git -b cm-10.1 msm7x27a-common
Code:
git clone https://github.com/TeamHackLG/proprietary_vendor_lge.git -b cm-10.1
Place the files from the p700 folder in device/lge/p700
Code:
cd ~/android/vendor/cm
Code:
./get-prebuilts
This was for fixing some compiling errors
Code:
cd ~/android
Code:
source build/envsetup.sh
Code:
lunch
In lunch menu type cm_p700-userdebug
Now you can start building
Code:
make -j*
Code:
make -j* otapackage
Speed up builds using ccache (optional, but highly recommended):
Edit your .bashrc and add this line at the bottom:
Code:
Code:
export USE_CCACHE=1
Then issue these commands:
Code:
Code:
$ export USE_CCACHE=1
$ export CCACHE_DIR=~/.ccache
$ prebuilts/misc/linux-x86/ccache/ccache -M 50G
The suggested cache size is 50-100G. (This is size in GB)
otapackage is for a flashable zip
* same again for the number of jobs, if you have a quadcore cpu I would recommend -j8
Good luck!

I also made a TWPR, I'll upload here. I appreciate testers
https://www.dropbox.com/s/bj5ili4ko9kwo1w/recovery.img
For installing/flashing
adb wait-for-device
adb push recovery.img /data/local/tmp/recovery.img
adb shell su -c "dd if=/data/local/tmp/recovery.img of=/dev/block/mmcblk0p17 bs=4096"
adb reboot
adb reboot recovery

For bug fixes check out TeamHackLG github page,
download the repo and replace the existing folder with the folder from github
All credits and big thanks to
TeamHackLG

Why not release a beta version?

When i will finish the exams i try it but i don t promise anything ahahah
Sent from my LG-P700 using xda premium

you must not clone device repos...
Use this:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TeamHackLG/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-10.1" />
<project name="TeamHackLG/android_device_lge_p700" path="device/lge/p700" remote="github" revision="master" />
<project name="TeamHackLG/android_device_lge_msm7x27a-common" path="device/lge/msm7x27a-common" remote="github" revision="cm-10.1" />
<project name="TeamHackLG/lge-kernel-lproj" path="kernel/lge/msm7x27a-common" remote="github" revision="android-msm-3.4-jb42" />
</manifest>
Click to expand...
Click to collapse
save it as local_manifests.xml in .repo
and dont forget to add/replace in default.xml to this:
<project path="hardware/qcom/display-legacy" name="TeamHackLG/android_hardwere_qcom_display-legacy" revision="cm-10.1" />
Click to expand...
Click to collapse
repo sync again and last build

MetaIIica said:
you must not clone device repos...
Use this:
save it as local_manifests.xml in .repo
and dont forget to add/replace in default.xml to this:
repo sync again and last build
Click to expand...
Click to collapse
I'll edit the first post
But cloning worked for me
Sent from my Nexus 7 using XDA Premium HD app

bart452 said:
Hey,
Since cm10.1 is comming, I want to share how to build it.
Requirments, Ubuntu and a building environment. There are a lot of threads how to set this up.
open a terminal
Code:
mkdir android
Code:
cd android
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
Code:
repo sync -j*
*= number of jobs, whit a good connection use -j4 for faster download
Code:
cd ~/android/device
Code:
mkdir lge
Code:
cd lge
Code:
git clone https://github.com/TeamHackLG/android_device_lge_p700.git
Code:
git clone https://github.com/TeamHackLG/android_device_lge_msm7x27a-common.git -b cm10.1
rename the the device folder to p700 and the common files to msm7x27a-common
Code:
git clone https://github.com/TeamHackLG/proprietary_vendor_lge.git p700 -b cm-10.1
Code:
cd ~/android/vendor/cm
Code:
./get-prebuilds
This was for fixing some compiling errors
Code:
cd ~/android
Code:
source build/envsetup.sh
Code:
lunch
In lunch menu type cm_p700-userdebug
Now you can start building
Code:
make -j*
Code:
make -j* otapackage
otapackage is for a flashable zip
* same again for the number of jobs, if you have a quadcore cpu I would recommend -j8
Good luck!
Click to expand...
Click to collapse
why not use
Code:
cd devices/lge
Code:
git clone https://github.com/TeamHackLG/android_device_lge_p700.git [B]p700[/B]
Code:
git clone https://github.com/TeamHackLG/android_device_lge_msm7x27a-common.git -b [B]cm-10.1[/B] [B]msm7x27a-common[/B]
no remaming is required after that.
branch is cm-10.1 not cm10.1
Also, why not use ccache? it speeds up build time ALOT!
Code:
./prebuilts/misc/linux-x86/ccache/ccache -M 50G
export USE_CCACHE=1
You need to have ~50gb free.

Is the ROM based on v20 baseband
And what us baseband

tudorsirb said:
why not use
Code:
cd devices/lge
Code:
git clone https://github.com/TeamHackLG/android_device_lge_p700.git [B]p700[/B]
Code:
git clone https://github.com/TeamHackLG/android_device_lge_msm7x27a-common.git -b [B]cm-10.1[/B] [B]msm7x27a-common[/B]
no remaming is required after that.
branch is cm-10.1 not cm10.1
Click to expand...
Click to collapse
Sorry, still a noob, just wrote what I did, I'll edit it when I'm on my pc
Sent from my Nexus 7 using XDA Premium HD app

dr.hafez94 said:
Is the ROM based on v20 baseband
And what us baseband
Click to expand...
Click to collapse
V10 baseband
Sent from my Nexus 7 using XDA Premium HD app

bart452 said:
V10 baseband
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Also there's a bionic patch from gerrit that need to be made in order for ril to work. The link should be on the dev thread.

the patch generate builderror.....

MetaIIica said:
the patch generate builderror.....
Click to expand...
Click to collapse
It worked on clean CM and brought signal

does someone test it TWRP? does it work?

Related

[HOW-TO] Building CM10, AOKP & TeamBaked For The JB Bootloader [Ubuntu 12.04+ 64-bit]

[HOW-TO] Building CM10, AOKP & TeamBaked For The JB Bootloader [Ubuntu 12.04+ 64-bit]
As many of you know, I no longer have my Transformer Prime, and hence cannot continue development for this device. So until the official CM10, AOKP and TeamBaked ROMs are updated to support the new JellyBean bootloader, as a final useful contribution to this device, I decided to provide a how-to guide to help people make their own builds.
This guide assumes that you have some experience building ROMs for Android and that you are comfortable with Linux. It is focused towards building on Ubuntu 12.04+ 64-bit.
1. Prepare the system (common for CM10, AOKP & TeamBaked)
a. Install Java JDK6
Code:
$ wget https://raw.github.com/flexiondotorg/oab-java6/master/oab-java.sh
$ chmod +x oab-java.sh
$ sudo ./oab-java.sh
$ sudo apt-get install sun-java6-jdk
b. Install required applications
Code:
$ sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown \
libxml2-utils xsltproc zlib1g-dev:i386 schedtool pngcrush
$ sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
c. Get the repo binary
Code:
$ mkdir -p ~/bin
$ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
2. Building CM10
a. Get the CM10 source
Code:
$ mkdir -p ~/CM10
$ cd ~/CM10
$ repo init -u git://github.com/CyanogenMod/android.git -b jellybean
$ repo sync -j8
b. Get my JB device, kernel & vendor source trees (You could use any other, just make sure it includes the changes needed for the JB bootloader and has the 3.1 kernel)
Code:
//JB device source to device/asus/tf201
$ mkdir -p ~/CM10/device/asus
$ cd ~/CM10/device/asus
$ git clone git://github.com/craigacgomez/android_device_asus_tf201.git -b cm_jb tf201
//JB kernel source to kernel/asus/tf201
$ mkdir -p ~/CM10/kernel/asus
$ cd ~/CM10/kernel/asus
$ git clone git://github.com/craigacgomez/android_kernel_asus_tf201 -b 10.4.2.15-nvtegra tf201
//JB vendor source to vendor/asus/tf201
$ mkdir -p ~/CM10/vendor/asus
$ cd ~/CM10/vendor/asus
$ git clone git://github.com/craigacgomez/vendor_proprietary_asus_tf201 -b jellybean tf201
c. Comment out CMUpdater since this is not an official build (No harm in leaving it there as long as people are instructed not to use it)
Code:
$ cd ~/CM10/vendor/cm/config/
$ gedit common.mk [comment the line which says CMUpdater \]
d. Resync & build
Code:
$ cd ~/CM10
$ repo sync -j8
$ sh vendor/cm/get-prebuilts
$ . build/envsetup.sh && brunch tf201
3. Building TeamBaked
a. Get the TeamBaked source
Code:
$ mkdir -p ~/BAKED
$ cd ~/BAKED
$ repo init -u https://github.com/TeamBAKED/platform_manifest.git -b jb
$ repo sync -j8
b. Delete the tf201 directories
Code:
$ mkdir -p ~/BAKED/device/asus
$ rm -rf tf201
$ mkdir -p ~/BAKED/kernel/asus
$ rm -rf tf201
$ mkdir -p ~/BAKED/vendor/asus
$ rm -rf tf201
c. Get my JB device, kernel & vendor source trees (You could use any other, just make sure it includes the changes needed for the JB bootloader and has the 3.1 kernel)
Code:
//JB device source to device/asus/tf201
$ mkdir -p ~/BAKED/device/asus
$ cd ~/BAKED/device/asus
$ git clone git://github.com/craigacgomez/android_device_asus_tf201.git -b blackbean_jb tf201
//JB kernel source to kernel/asus/tf201
$ mkdir -p ~/BAKED/kernel/asus
$ cd ~/BAKED/kernel/asus
$ git clone git://github.com/craigacgomez/android_kernel_asus_tf201 -b 10.4.2.15-nvtegra tf201
//JB vendor source to vendor/asus/tf201
$ mkdir -p ~/BAKED/vendor/asus
$ cd ~/BAKED/vendor/asus
$ git clone git://github.com/craigacgomez/vendor_proprietary_asus_tf201 -b jellybean tf201
d. Resync & build
Code:
$ cd ~/BAKED
$ repo sync -j8
$ . build/envsetup.sh && brunch tf201
4. Building AOKP
a. Get the AOKP source
Code:
$ mkdir -p ~/AOKP
$ cd ~/AOKP
$ repo init -u https://github.com/AOKP/platform_manifest.git -b jb
$ repo sync -j8
b. Get my JB device, kernel & vendor source trees (You could use any other, just make sure it includes the changes needed for the JB bootloader and has the 3.1 kernel)
Code:
//JB device source to device/asus/tf201
$ mkdir -p ~/AOKP/device/asus
$ cd ~/AOKP/device/asus
$ git clone git://github.com/craigacgomez/android_device_asus_tf201.git -b aokp_jb tf201
//JB kernel source to kernel/asus/tf201
$ mkdir -p ~/AOKP/kernel/asus
$ cd ~/AOKP/kernel/asus
$ git clone git://github.com/craigacgomez/android_kernel_asus_tf201 -b 10.4.2.15-nvtegra tf201
//JB vendor source to vendor/asus/tf201
$ mkdir -p ~/AOKP/vendor/asus
$ cd ~/AOKP/vendor/asus
$ git clone git://github.com/craigacgomez/vendor_proprietary_asus_tf201 -b jellybean tf201
c. Add tf201 to the vendor & build setup
Code:
$ cd ~/AOKP/vendor/aokp
$ gedit vendorsetup.sh
Add this line vendorsetup.sh below add_lunch_combo aokp_tf101-userdebug
Code:
add_lunch_combo aokp_tf201-userdebug
Code:
$ cd ~/AOKP/vendor/aokp/products
$ gedit AndroidProducts.mk
Add this line vendorsetup.sh below $(LOCAL_DIR)/tf101.mk \
Code:
$(LOCAL_DIR)/tf201.mk \
Code:
$ cd ~/AOKP/vendor/aokp/products
$ touch tf201.mk
$ gedit tf201.mk
Add these line to tf201.mk
Code:
# Inherit device configuration for tf201.
$(call inherit-product, device/asus/tf201/full_tf201.mk)
# Inherit some common AOKP stuff.
$(call inherit-product, vendor/aokp/configs/common_tablet.mk)
$(call inherit-product, vendor/aokp/configs/gsm.mk)
PRODUCT_NAME := aokp_tf201
PRODUCT_DEVICE := tf201
PRODUCT_BRAND := asus
PRODUCT_MODEL := Transformer Prime TF201
PRODUCT_MANUFACTURER := asus
PRODUCT_BUILD_PROP_OVERRIDES += \
PRODUCT_NAME=EeePad \
BUILD_FINGERPRINT="asus/US_epad/EeePad:4.1.1/JRO03C/US_epad-10.4.2.15-20120917:user/release-keys" \
PRIVATE_BUILD_DESC="US_epad-user 4.1.1 JRO03C US_epad-10.4.2.15-20120917 release-keys" \
PRODUCT_COPY_FILES += \
vendor/aokp/prebuilt/bootanimation/bootanimation_1280_800.zip:system/media/bootanimation.zip
d. Resync & build
Code:
$ cd ~/AOKP
$ repo sync -j8
$ . build/envsetup.sh && brunch tf201
Craig, you are so awesome. Thank you so much for all you have done for the community. I hope I can end up with a nexus so I can continue to follow your development, but I'm also glad for the instruction and inspiration to start figuring out how to do more myself. Thanks again.
You're an absolute legend.
I just pressed return to start the build of my first ROM from your previous guide when I saw this..
qubz said:
Your an absolute legend.
Click to expand...
Click to collapse
I'm so sorry if I seem mean... but I just had to do this... I'm a grammar nazi!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
craigacgomez said:
I'm so sorry if I seem mean... but I just had to do this... I'm a grammar nazi!!
Click to expand...
Click to collapse
Ha ha, you got me. It's been a long day. Unfortunately the reply box had no compiler, fix uploaded.
Hey craigacgomez,
thanks for your work.
But I got a problem while trying to build CM10.
Pastebin entry:
http://pastebin.com/st0DfWv4
I'm trying to build it on a server without a gui, what should make no problems. Installed all the requirements you mentioned.
Do you know how to get rid of this error?
Greetz
Chrischdi
chrischdi said:
Hey craigacgomez,
thanks for your work.
But I got a problem while trying to build CM10.
Pastebin entry:
http://pastebin.com/st0DfWv4
I'm trying to build it on a server without a gui, what should make no problems. Installed all the requirements you mentioned.
Do you know how to get rid of this error?
Greetz
Chrischdi
Click to expand...
Click to collapse
libjli.so is a Java binary... somehow it cannot find it... could you try this...
http://serverfault.com/questions/57...ject-file-libjli-so-no-such-file-or-directory
Thanks for this.
I'm hoping to keep your work going , this is a great start
its sad that you no longer have a prime though.
sent from my Prime
Thanks for posting this! You are an absolute legend! It is a massive help as I just started setting up my build environment for compiling my own CM10 and maybe even look at Paranoid :silly:
marko! said:
Thanks for this.
I'm hoping to keep your work going , this is a great start
its sad that you no longer have a prime though.
sent from my Prime
Click to expand...
Click to collapse
gunzy83 said:
Thanks for posting this! You are an absolute legend! It is a massive help as I just started setting up my build environment for compiling my own CM10 and maybe even look at Paranoid :silly:
Click to expand...
Click to collapse
Nice to see people pick up where I left off... to be honest, all I did for this device was the first time for me... I've just been good at modding and I never dug deep into ROM & kernel work before, so I'm pretty sure you guys could do the same or even better!
Hi,
many thanks again Craig for all your work..
I tried to follow your guide for Team Baked, and ended up with::
""build/core/product_config.mk:193: *** _nic.PRODUCTS.[[vendor/baked/products/p5wifi.mk]]: "device/samsung/p5wifi/p5wifi.mk" does not exist. "Stop.
"** Don't have a product spec for: 'baked_tf201'
"** Do you have the right repo manifest?
"
Itried running breakfeast command as suggested but same error.
Anyone has a suggestion ?
Thanks
Striatum_bdr said:
Hi,
many thanks again Craig for all your work..
I tried to follow your guide for Team Baked, and ended up with::
""build/core/product_config.mk:193: *** _nic.PRODUCTS.[[vendor/baked/products/p5wifi.mk]]: "device/samsung/p5wifi/p5wifi.mk" does not exist. "Stop.
"** Don't have a product spec for: 'baked_tf201'
"** Do you have the right repo manifest?
"
Itried running breakfeast command as suggested but same error.
Anyone has a suggestion ?
Thanks
Click to expand...
Click to collapse
Don't run breakfast... just brunch... looks like it has something to do with the p5wifi... try resyncing or comment out that 'add_lunch_combo baked_p5wifi-userdebug' from vendor/baked/vendorsetup.sh
craigacgomez said:
Don't run breakfast... just brunch... looks like it has something to do with the p5wifi... try resyncing or comment out that 'add_lunch_combo baked_p5wifi-userdebug' from vendor/baked/vendorsetup.sh
Click to expand...
Click to collapse
My noob is going to start showing here, but when you say "Comment out" does that simply mean putting brackets around? Does it mean deleting that from the script? I haven't tried to build since your first little guide, but I think I put brackets around what it said to "Comment out."
lortay78 said:
My noob is going to start showing here, but when you say "Comment out" does that simply mean putting brackets around? Does it mean deleting that from the script? I haven't tried to build since your first little guide, but I think I put brackets around what it said to "Comment out."
Click to expand...
Click to collapse
That means out a # at the beginning of the line.
Hi,
Commented out all lines except tf201 in vendorsetup.sh and same error.
Striatum_bdr said:
Hi,
Commented out all lines except tf201 in vendorsetup.sh and same error.
Click to expand...
Click to collapse
Add these lines to the manifest.xml, then repo sync and brunch tf201:
<project path="device/samsung/p4-common" name="device_samsung_p4-common" remote="baked" revision="jb" />
<project path="device/samsung/p5wifi" name="device_samsung_p5wifi" remote="baked" revision="jb" /> :good:
csrabear said:
Add these lines to the manifest.xml, then repo sync and brunch tf201:
<project path="device/samsung/p4-common" name="device_samsung_p4-common" remote="baked" revision="jb" />
<project path="device/samsung/p5wifi" name="device_samsung_p5wifi" remote="baked" revision="jb" /> :good:
Click to expand...
Click to collapse
Great !
It does the trick but... lol
Then error with prebuilts arm toolchain,
/bin/bash: prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc : binary file impossible to execute
Same error endless. Files are there, permission set to executable...
Is there a way to use arm ubuntu toolchain (easily installed by Synaptic)?
Thanks again
Striatum_bdr said:
Great !
It does the trick but... lol
Then error with prebuilts arm toolchain,
/bin/bash: prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc : binary file impossible to execute
Same error endless. Files are there, permission set to executable...
Is there a way to use arm ubuntu toolchain (easily installed by Synaptic)?
Thanks again
Click to expand...
Click to collapse
Hi,
Try this thread for answer---
http://www.google.com/url?sa=t&rct=j&q=%2Fbin%2Fbash%3A%20prebuilts%2Fgcc%2Flinux-x86%2Farm%2Farm-linux-androideabi-4.6%2Fbin%2Farm-linux-androideabi-gcc%20%3A%20binary%20file%20impossible%20to%20execute&source=web&cd=1&cad=rja&ved=0CDAQFjAA&url=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1762641%26page%3D34&ei=T9KsUOnCMIuK8QS0wYHIAQ&usg=AFQjCNEZuCIRoHJX7_h_34dD3tvmeBbVsQ
or maybe this one will help--
http://www.google.com/url?sa=t&rct=j&q=%2Fbin%2Fbash%3A%20prebuilts%2Fgcc%2Flinux-x86%2Farm%2Farm-linux-androideabi-4.6%2Fbin%2Farm-linux-androideabi-gcc%20%3A%20binary%20file%20impossible%20to%20execute&source=web&cd=2&cad=rja&ved=0CDkQFjAB&url=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1807505%26page%3D2&ei=T9KsUOnCMIuK8QS0wYHIAQ&usg=AFQjCNE0FwC2wWy8UE5QHperdU0rI72MKw
csrabear said:
Hi,
Try this thread for answer---
or maybe this one will help--
http://www.google.com/url?sa=t&rct=j&q=%2Fbin%2Fbash%3A%20prebuilts%2Fgcc%2Flinux-x86%2Farm%2Farm-linux-androideabi-4.6%2Fbin%2Farm-linux-androideabi-gcc%20%3A%20binary%20file%20impossible%20to%20execute&source=web&cd=2&cad=rja&ved=0CDkQFjAB&url=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1807505%26page%3D2&ei=T9KsUOnCMIuK8QS0wYHIAQ&usg=AFQjCNE0FwC2wWy8UE5QHperdU0rI72MKw
Click to expand...
Click to collapse
Thanks that's what I suspected, I build on a 32bits machine, found 32 arm binaries in the above post.
Will try later. Thanks.
You really need a 64 bit os. Compilation started fine, but a some point gcc sdk binaries are used and again the default paths lead only to 64 bits ones.
I'll install a 64 version if ubuntu.
Thanks guys for you helps

[GUIDE][PA 3.xx][4.3] Building Paranoid Android from source

AOSPA+ Building from sources
Pre reuirments :
A 64 bit PC
Some knowlegde About Git
A brain
This is unofficial. This thread is intended for devs & advanced users only.
For the first time you try to build AOSPA
Follow this guide up to "Initialize the CyanogenMod source repository" step (don't execute this step).
http://wiki.cyanogenmod.org/w/Build_for_smultron
Download & compile lz4 compression tool
Code:
sudo apt-get install subversion
cd ~/Downloads
svn checkout -r 91 http://lz4.googlecode.com/svn/trunk/ lz4
cd lz4 && make && cp lz4demo ~/bin/lz4demo
Initialize the AOSPA source repository
Enter the following to initialize the repository:
Code:
cd ~/android/system/
repo init -u git://github.com/ParanoidAndroid/manifest.git -b jb43-legacy
Get the required local manifest
Code:
mkdir -p ~/android/system/.repo/local_manifests
curl https://raw.github.com/LegacyXperia/local_manifests/cm-10.2/semc.xml > ~/android/system/.repo/local_manifests/semc.xml
Download the source code
Code:
repo sync
Download some commits from CyanogenMod gerrit which are not accepted yet
Code:
curl https://raw.github.com/LegacyXperia/local_manifests/cm-10.2/updates.sh > ~/android/system/updates.sh
chmod a+x updates.sh
./updates.sh
Get the prebuilts
Code:
cd ~/android/system/vendor/cm
./get-prebuilts
Setup the environment & prepare the device-specific code.
Code:
cd ~/android/system
. build/envsetup.sh
breakfast smultron
Build the ROM (takes long time)
Code:
brunch smultron
If the build finishes successfully, you will find the build here (change DATE into the date):
~/android/system/out/target/product/smultron/cm-10.2-DATE-UNOFFICIAL-smultron.zip
The next times you want to build, you only need to do the following:
Sync the repositories & make sure you are using the latest local_manifest.
Code:
cd ~/android/system/
curl https://raw.github.com/LegacyXperia/local_manifests/cm-10.2/semc.xml > ~/android/system/.repo/local_manifests/semc.xml
repo sync
Download some commits from CyanogenMod gerrit which are not accepted yet
Code:
curl https://raw.github.com/LegacyXperia/local_manifests/cm-10.2/updates.sh > ~/android/system/updates.sh
chmod a+x updates.sh
./updates.sh
Setup the environment
Code:
. build/envsetup.sh
Build the ROM
Code:
brunch smultron
If the build finishes successfully, you will find the build here (change DATE into the date):
~/android/system/out/target/product/smultron/PA-3.9-DATE-UNOFFICIAL-smultron.zip
Steps to build only the kernel:
Sync the repositories.
Code:
cd ~/android/system/
repo sync
Setup the environment
Code:
. build/envsetup.sh
Build the kernel
Code:
breakfast smultron
make -j4 bootimage
If the build finishes successfully, you will find the boot image here:
~/android/system/out/target/product/smultron/boot.img
Credits: Thanks to hnl_dk , mikeioannia for the initial CM9 & CM10 , 10.1 , 10.2 guides.
And you built successfully with that method? Because as far as I know it's impossible... You didn't define anything about the device in the vendor/pa folders so it can't even find your device while trying to ./rom-build.sh
Sent from my Nexus 4 running Android 4.2.2
As reported by mihahn this thread seems a blatant copy of another guide without any actual research. I've maintained AOSPA for several devices for some time and see at least 2 mistakes when quickly scanning through it.
Thread closed for now, if it's solved I'll reopen, otherwise it will be deleted.

Setup Script for Build Android with Ubuntu 12.04 - 14.04

I have made a sample Bash-Scripts for all usable Ubuntu Versions (12.04 -14.04) to setup for building Android-Roms such as CyanogenMod, AOSP, PAC, PA, Omni-Rom, AOKP or what ever you want build. This is the first Startup for all
How to use:
Download Attachment and decompress to your Useraccount in Ubuntu.
Pick your needed Bashscript for your Ubuntu and give the files
Code:
chmod +x *.sh
now start it with (when you use Ubuntu 12.04)
Code:
./ 12.04.sh
This download and install all needed packages.
When ready you can now setup for your favourite Rom what you want.
eg. CyanogenMod 11:
Code:
mkdir cm11 && cd cm11
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
(now put here your DEVICE Repos here)
Code:
mkdir .repo/local_manifests
vi ~/cm11/.repo/local_manifests/roomservice.xml
Code:
repo sync -jXX -q #XX=needed Cores
. build/envsetup.sh
~/cm11/vendor/cm/get-prebuilts
#brunch -jXX DEVICE #DEVICE=Codename for your device
this is a very useful thread . thanx for sharing
Thanks

[ROMS][GITHUB] List with Repo initialization commands.

Hi there! I am new here! So decided to start off with this!
Here's a list of the OpenSource ROMs, with the links to their github repos and the commands used for initializing their respective repos, to the working directories
For syncing the full repo,
After you initialize certain repo in the working folder, you have to give the following command :
Code:
repo sync -jX -c -f
Note : X = no. of threads. If you are not working on certain things in the background, you can add as many threads as the CPU supports.
ROMs with Github links. This will be useful for source builders, as they would find all the Github links are one place!
1. CyanogenMod
Link to Github sources :
Code:
[URL="https://github.com/CyanogenMod"]https://github.com/CyanogenMod[/URL]
Command for initializing the repo in the working folder :
Code:
repo init -u git://github.com/CyanogenMod/android.git -b <branch>
2. OmniROM
Link to github sources :
Code:
[URL="https://github.com/omnirom"]https://github.com/omnirom[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/omnirom/android.git -b android-4.4
3. Carbon ROM
Link to github sources :
Code:
[URL="https://github.com/CarbonDev"]https://github.com/CarbonDev[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/CarbonDev/android.git -b <branch>
4. PAC-man
Link to github sources :
Code:
[URL="https://github.com/PAC-man"]https://github.com/PAC-man[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u git://github.com/PAC-man/pacman.git -b <branch>
5. Paranoid Android
Link to github sources :
Code:
[URL="https://github.com/ParanoidAndroid"]https://github.com/ParanoidAndroid[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u [email protected]:ParanoidAndroid/manifest.git -b <branch>
6. Root Box
Link to github sources :
Code:
[URL="https://github.com/Root-Box"]https://github.com/Root-Box[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/Root-Box/platform_manifest.git -b <branch>
7. AOKP
Link to github sources :
Code:
[URL="https://github.com/AOKP"]https://github.com/AOKP[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/AOKP/platform_manifest.git -b <branch>
8. AOSP
Link to github sources :
Code:
[URL="https://github.com/android"]https://github.com/android[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://android.googlesource.com/platform/manifest.git -b <branch>
9. CyanMobile
Link to github sources :
Code:
[URL="https://github.com/CyanMobile"]https://github.com/CyanMobile[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u git://github.com/CyanMobile/android_cyanmobile.git -b <branch>
10. MiCode
Link to github sources :
Code:
[URL="https://github.com/MiCode"]https://github.com/MiCode[/URL]
Command for initializing the repo in the working folder:
Code:
I couldn't find the manifest git! Some one help me out! :P
11. AOSB
Link to github sources :
Code:
[URL="https://github.com/AOSB"]https://github.com/AOSB[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/AOSB/android.git <branch>
12. Liquid Smooth
Link to github sources :
Code:
[URL="https://github.com/LiquidSmooth"]https://github.com/LiquidSmooth[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u git://github.com/LiquidSmooth/android.git -b <branch>
13. Slim ROMs
Link to github sources :
Code:
[URL="https://github.com/SlimRoms"]https://github.com/SlimRoms[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u git://github.com/SlimRoms/platform_manifest.git -b <branch>
14. CyanFox
Link to github sources :
Code:
[URL="https://github.com/CyanFox"]https://github.com/CyanFox[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u git://github.com/CyanFox/android.git -b <branch>
15. Lewa OS
Link to github sources :
Code:
[URL="https://github.com/LeWaCode"]https://github.com/LeWaCode[/URL]
Command for initializing the repo in the working folder:
Code:
I couldn't find the manifest git! Some one help me out! :P
16. Mokee
Link to github sources :
Code:
[URL="https://github.com/MoKee"]https://github.com/MoKee[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/MoKee/android.git -b <branch>
17. ResurrectionRemix
Link to github sources :
Code:
[URL="https://github.com/resurrectionremix"]https://github.com/resurrectionremix[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/ResurrectionRemix/platform_manifest.git -b <branch>
I am new here, so I am sure, I might have missed out some ROM. Please care to inform that through posting the Github link in the thread! Thanks
I'm really sorry if I'm posting in the wrong thread, but I'm new to the dev forums so I didn't want to make a whole new thread for this simple question. I'm currrently syncing the CM-11.0 branch from the cyanogenmod github. And most packages are donwloaded correctly, but 4 are making problems. Here's the log of my terminal:
Code:
Fetching projects: 99% (433/437) fatal: Not a git repository: '/home/pavle/android/system/.repo/projects/packages/apps/QuickSearchBox.git'
fatal: Not a git repository: '/home/pavle/android/system/.repo/projects/external/safe-iop.git'
fatal: Not a git repository: '/home/pavle/android/system/.repo/projects/system/security.git'
fatal: Not a git repository: '/home/pavle/android/system/.repo/projects/external/chromium_org/third_party/leveldatabase/src.git'
error: Cannot fetch CyanogenMod/android_packages_apps_QuickSearchBox
warn: --force-broken, continuing to sync
error: Cannot fetch CyanogenMod/android_system_security
warn: --force-broken, continuing to sync
error: Cannot fetch platform/external/chromium_org/third_party/leveldatabase/src
warn: --force-broken, continuing to sync
error: Cannot fetch CyanogenMod/android_external_safe-iop
warn: --force-broken, continuing to sync
I ran the repo sync command with the -f flag as you can see, so it would download everything else execpt the ones it can't. I'm running ubuntu 13.10 x64. Also I should mention that I haven't added any device specific trees yet, only pure CM without kernel, device or vendor repos
Why the -c and -f arguments with repo sync? Doesn't it run fine without them?
Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu
paxy97 said:
I'm really sorry if I'm posting in the wrong thread, but I'm new to the dev forums so I didn't want to make a whole new thread for this simple question. I'm currrently syncing the CM-11.0 branch from the cyanogenmod github. And most packages are donwloaded correctly, but 4 are making problems. Here's the log of my terminal:
Code:
Fetching projects: 99% (433/437) fatal: Not a git repository: '/home/pavle/android/system/.repo/projects/packages/apps/QuickSearchBox.git'
fatal: Not a git repository: '/home/pavle/android/system/.repo/projects/external/safe-iop.git'
fatal: Not a git repository: '/home/pavle/android/system/.repo/projects/system/security.git'
fatal: Not a git repository: '/home/pavle/android/system/.repo/projects/external/chromium_org/third_party/leveldatabase/src.git'
error: Cannot fetch CyanogenMod/android_packages_apps_QuickSearchBox
warn: --force-broken, continuing to sync
error: Cannot fetch CyanogenMod/android_system_security
warn: --force-broken, continuing to sync
error: Cannot fetch platform/external/chromium_org/third_party/leveldatabase/src
warn: --force-broken, continuing to sync
error: Cannot fetch CyanogenMod/android_external_safe-iop
warn: --force-broken, continuing to sync
I ran the repo sync command with the -f flag as you can see, so it would download everything else execpt the ones it can't. I'm running ubuntu 13.10 x64. Also I should mention that I haven't added any device specific trees yet, only pure CM without kernel, device or vendor repos
Click to expand...
Click to collapse
Try to sync again.. this time, don't use the -f arguments.
SMillerNL said:
Why the -c and -f arguments with repo sync? Doesn't it run fine without them?
Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu
Click to expand...
Click to collapse
Ya, It will run without -c and -f arguments. But -f will force the sync. It is good for people who have a slow internet, as the download won't break in between(that doesn't matter much though, but it saves time, if suppose the dev is syncing overnight).
PixCM said:
Try to sync again.. this time, don't use the -f arguments.
Ya, It will run without -c and -f arguments. But -f will force the sync. It is good for people who have a slow internet, as the download won't break in between(that doesn't matter much though, but it saves time, if suppose the dev is syncing overnight).
Click to expand...
Click to collapse
So what will -c do then?
Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu
SMillerNL said:
So what will -c do then?
Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu
Click to expand...
Click to collapse
-c: command and arguments to execute. The command is evaluated through /bin/sh and any arguments after it are passed through as shell positional parameters.
PixCM said:
Hi there! I am new here! So decided to start off with this!
Here's a list of the OpenSource ROMs, with the links to their github repos and the commands used for initializing their respective repos, to the working directories
For syncing the full repo,
After you initialize certain repo in the working folder, you have to give the following command :
Code:
repo sync -jX -c -f
Note : X = no. of threads. If you are not working on certain things in the background, you can add as many threads as the CPU supports.
ROMs with Github links. This will be useful for source builders, as they would find all the Github links are one place!
1. CyanogenMod
Link to Github sources :
Code:
[URL="https://github.com/CyanogenMod"]https://github.com/CyanogenMod[/URL]
Command for initializing the repo in the working folder :
Code:
repo init -u git://github.com/CyanogenMod/android.git -b <branch>
2. OmniROM
Link to github sources :
Code:
[URL="https://github.com/omnirom"]https://github.com/omnirom[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/omnirom/android.git -b android-4.4
3. Carbon ROM
Link to github sources :
Code:
[URL="https://github.com/CarbonDev"]https://github.com/CarbonDev[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/CarbonDev/android.git -b <branch>
4. PAC-man
Link to github sources :
Code:
[URL="https://github.com/PAC-man"]https://github.com/PAC-man[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u git://github.com/PAC-man/pacman.git -b <branch>
5. Paranoid Android
Link to github sources :
Code:
[URL="https://github.com/ParanoidAndroid"]https://github.com/ParanoidAndroid[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u [email protected]:ParanoidAndroid/manifest.git -b <branch>
6. Root Box
Link to github sources :
Code:
[URL="https://github.com/Root-Box"]https://github.com/Root-Box[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/Root-Box/platform_manifest.git -b <branch>
7. AOKP
Link to github sources :
Code:
[URL="https://github.com/AOKP"]https://github.com/AOKP[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/AOKP/platform_manifest.git -b <branch>
8. AOSP
Link to github sources :
Code:
[URL="https://github.com/android"]https://github.com/android[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://android.googlesource.com/platform/manifest.git -b <branch>
9. CyanMobile
Link to github sources :
Code:
[URL="https://github.com/CyanMobile"]https://github.com/CyanMobile[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u git://github.com/CyanMobile/android_cyanmobile.git -b <branch>
10. MiCode
Link to github sources :
Code:
[URL="https://github.com/MiCode"]https://github.com/MiCode[/URL]
Command for initializing the repo in the working folder:
Code:
I couldn't find the manifest git! Some one help me out! :P
11. AOSB
Link to github sources :
Code:
[URL="https://github.com/AOSB"]https://github.com/AOSB[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/AOSB/android.git <branch>
12. Liquid Smooth
Link to github sources :
Code:
[URL="https://github.com/LiquidSmooth"]https://github.com/LiquidSmooth[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u git://github.com/LiquidSmooth/android.git -b <branch>
13. Slim ROMs
Link to github sources :
Code:
[URL="https://github.com/SlimRoms"]https://github.com/SlimRoms[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u git://github.com/SlimRoms/platform_manifest.git -b <branch>
14. CyanFox
Link to github sources :
Code:
[URL="https://github.com/CyanFox"]https://github.com/CyanFox[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u git://github.com/CyanFox/android.git -b <branch>
15. Lewa OS
Link to github sources :
Code:
[URL="https://github.com/LeWaCode"]https://github.com/LeWaCode[/URL]
Command for initializing the repo in the working folder:
Code:
I couldn't find the manifest git! Some one help me out! :P
16. Mokee
Link to github sources :
Code:
[URL="https://github.com/MoKee"]https://github.com/MoKee[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/MoKee/android.git -b <branch>
17. ResurrectionRemix
Link to github sources :
Code:
[URL="https://github.com/resurrectionremix"]https://github.com/resurrectionremix[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/ResurrectionRemix/platform_manifest.git -b <branch>
I am new here, so I am sure, I might have missed out some ROM. Please care to inform that through posting the Github link in the thread! Thanks
Click to expand...
Click to collapse
The ParanoidAndroid repo is actually
https://github.com/AOSPA for Nexus devices
or
https://github.com/AOSPA-legacy for non-Nexus
I'm getting excited repo sync error... When I do "repo sync" command ...
And when I do a "./build-pac.sh p3100" command..
It gets stuck at lunching device thing... It's unable to download dependencies from cyanogenmod...
I had edited the room_service.xml a while back.. The error started after that... But now I deleted the room service file but the error still fails... Any solutions...?
Thanks for including CyanFox....... ....
Sent from my GT-I9100 using Tapatalk
zeetherocker said:
I'm getting excited repo sync error... When I do "repo sync" command ...
And when I do a "./build-pac.sh p3100" command..
It gets stuck at lunching device thing... It's unable to download dependencies from cyanogenmod...
I had edited the room_service.xml a while back.. The error started after that... But now I deleted the room service file but the error still fails... Any solutions...?
Click to expand...
Click to collapse
Hmm, The lunch process doesn't use the room service. It uses the dependencies of the ROM and syncs, whats there in the dependencies file!
Check dependencies for errors, or manually put the files in place. The vendor in /vendor/manufacturer/device, the device tree in /device/manufacturer/device and kernel in /kernel/manufacturer/device (check in the boardconfig.mk, for exact location of kernel source).
I suppose that its a exiting repo error and not a exciting repo sync error . for that, use the flag "-f" , for example. repo sync -f
Check if this works :highfive:
PixCM said:
Hmm, The lunch process doesn't use the room service. It uses the dependencies of the ROM and syncs, whats there in the dependencies file!
Check dependencies for errors, or manually put the files in place. The vendor in /vendor/manufacturer/device, the device tree in /device/manufacturer/device and kernel in /kernel/manufacturer/device (check in the boardconfig.mk, for exact location of kernel source).
I suppose that its a exiting repo error and not a exciting repo sync error . for that, use the flag "-f" , for example. repo sync -f
Check if this works :highfive:
Click to expand...
Click to collapse
I'm sure it's excited repo sync error... I'll post a Screenshot later... For now I've deleted a few folders... I'll try syncing repos again in the morning... And I'll do whatever u said and report back if I get errors..
Replicant OS
Nice list, I did not know there where so many, here is another one at http://www.replicant.us/
@PixCM Nice thread
maybe add VanirAOSP
https://github.com/VanirAOSP/platform_manifest
add Hellkat
https://github.com/Hellybean/android
add BeanStalk
https://github.com/scotthartbti/android
Cheers
MiCode builds funny.
sync command:
repo init -u git://github.com/MiCode/patchrom.git -b jellybean42
---------- Post added at 05:49 PM ---------- Previous post was at 05:47 PM ----------
and Dirty Unicorn
https://github.com/DirtyUnicorns-KitKat
sync:
repo init -u https://github.com/DirtyUnicorns-KitKat/manifest.git -b du44
Here you go, this should about cover it
https://github.com/LowEndGeek/General_Android_Documents/blob/master/CustomRoms.md
more...
broodROM
https://github.com/broodROM/platform_manifest
AOSP-S4 4.4.2 KitKat
https://github.com/AOSP-S4-KK/platform_manifest
ValidusAOSP
https://github.com/ValidusAOSP/platform_manifest
MWisBest
https://github.com/MWisBest/android_manifest
AnimeROM
https://github.com/AnimeROM/android
TheSchismROM
https://github.com/TheSchismROM/platform_manifest
Mahdi-Rom
https://github.com/Mahdi-Rom/platform_manifest
and one more guys
https://github.com/PureKat/android
Www.github.com/SOKP/platform_manifest
Sent from my GT-I9500 using XDA Premium 4 mobile app
another one=AICP rom
Android Ice Cold Project
https://github.com/AICP/platform_manifest
repo init -u https://github.com/AICP/platform_manifest.git -b kitkat
if someone got some new rom link to add... please do!
one more
will test it soon... today if iam lucky...
https://github.com/CyanHacker/android
repo init -u git://github.com/CyanHacker/android.git -b kitkat

[HELP!] Lineageos 15.1 build fails with "ninja failed with: exit status 1"

Hi everyone!
I'm trying to build LineageOS 15.1 for my Samsung Galaxy S5 - klte. Everything is good until I start compiling and then the build fails with an error "ninja failed with: exit status 1".
I've gone through the output from the build, but I can't find anything that sticks out. I also have tried Googling the problem, but I can't find anything that matches my problem. Here are my build steps:
## Create the directories
mkdir -p ~/bin
mkdir -p ~/android/lineage
## Install the repo
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
## Put the ~/bin directory in my path
nano ~/.profile
# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
PATH="$HOME/bin:$PATH"
fi
source ~/.profile
## Initialize the source repository
cd ~/android/lineage
repo init -u https://github.com/LineageOS/android.git -b lineage-15.1
## Download the source code
repo sync -f --force-sync -j8 -c
source build/envsetup.sh
breakfast klte
cd ~/android/lineage/device/samsung/klte
./extract-files.sh
cd ~/android/lineage
export USE_CCACHE=1
./prebuilts/sdk/tools/jack-admin kill-server
export JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx15g"
./prebuilts/sdk/tools/jack-admin start-server
## Prepare the device-specific code
source build/envsetup.sh
breakfast klte
## Start the build
croot
brunch klte
Here is a link for the output from the build:
http://www.ohsmeg.com/bill/projects/android/lineageos/ninja_error.html
My build machine is an i7-950 with 16gb of memory, running Ubuntu 16.04 headless.
Any suggestions?
Thanks!
zog

Categories

Resources