Database Develop

[DEV] How to build CM10.1 (Android 4.2.1) for the LG-P990 O2x

Build your 'own' CM10.1 ROM (Android 4.2.1) today!
Revision V1.3 2013.01.09 Updates: No more patching needed. local_manifest.xml updated to new branch revision. Text updates.
Revision V1.2 2012.12.13 Updates: Repo sync branch finally changed from mr1-staging to cm-10.1. Thanks HerrKuk.
Revision V1.1 2012.12.11 Updates: New Patch: WiFi shows networks, BT works, audio.h reworked, notification lights are back, USB mass-storage support included. Compatible to V30A Kernel.
Revision V1.0 2012.12.01 Initial release
Thank you note: Thanks to Ricardo Cerqueira for his work on this device.Thanks to marsgod for BT and WiFi patches/tips.
General note: Please keep in mind that CM10.1 is still experimental. This guide is for those who cannot wait...
{
"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"
}
Preparation
What you need:
You need a fully working build environment. If you don't have one running already, you can follow my guide in the other thread to get a fully working environment under Ubuntu 12.10 64bit. Follow the easy steps in the guide. Make a test build with CM10 to see if it is working. Then you will be ready for the next step.
Your build environment is now set? Good, let's start!
Use the terminal to make the steps. A terminal window can be opened by pressing Ctrl+Alt+T. Every single command for the terminal is marked with a $ sign. Just paste every command (without the $ sign) to your terminal window and there shouldn't be any problem.
Get the sources
Start with creating a new working directory for CM10.1:
Code:
$ mkdir ~/cm10.1
$ cd ~/cm10.1
Initialize Repo for Android CM10.1 (Android 4.2.1):
Code:
$ repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
and enter your credentials if needed.
Download the sources:
Code:
$ repo sync
Wait until it's finished (takes a lot of time!).
If the process hangs use Ctrl+C to break out of it and resume the download with another
Code:
$ repo sync
Initialize the environment
Code:
$ . build/envsetup.sh
Obtain the proprietary files:
Create a file with the name local_manifest.xml in the .repo directory to add additional sources. To see the hidden .repo directory, you have to press Ctrl-H in your file manager.
Create the xml-file with
Code:
$ gedit ~/cm10.1/.repo/local_manifest.xml
20130109: Update! New branch revisions!
Paste the following lines to the editor
Code:
<manifest>
<project name="TheMuppets/proprietary_vendor_lge.git" path="vendor/lge" remote="github" revision="cm-10.1"/>
<project name="CyanogenMod/android_device_lge_p990" path="device/lge/p990" remote="github" revision="cm-10.1"/>
<project name="CyanogenMod/android_device_lge_star-common" path="device/lge/star-common" remote="github" revision="cm-10.1"/>
<project name="CyanogenMod/lge-kernel-star" path="kernel/lge/star" remote="github" revision="cm-10.1"/>
</manifest>
Save the file.
Run another
Code:
$ repo sync
Download the necessary prebuilts from cyanogenmod by running
Code:
$ ~/cm10.1/vendor/cm/get-prebuilts
Ok. That's done!
Patching
20130109: Thanks to Ricardo Cerqueira's Update to the CyanogenMod repos there is no more patching needed!
Only for those who have patched the sources before and want to build with the new sources. If you are new to this skip the 'Patching' part and go to 'Build the ROM' directly.
If you have patched/changed the sources and want to get up-to-date, here is what you can do:
change the local.manifest.xml file that it looks like the one you see above
delete all the directories inside your ~/cm10.1/ directory but keep the hidden .repo directory
repo sync now and the missing files will be downloaded and the whole structure will be recreated without redownloading the repos you already have
get the prebuilts with ~/cm10.1/vendor/cm/get-prebuilts
and this is it, just brunch p990 again
Build the ROM
Code:
$ repo sync
$ brunch p990
and flash it via CWM. Make a clean start (if necessary) with format /system, wipe data/factory reset, etc..
Have fun!

FAQ
Revision V1.5 20130110 New GAPPS, now without the nasty force closing AOSP keyboard 'bug'
Revision V1.4 20130109 Sections updated: bootloader section, Baseband section, partition size, mass storage mode. Sections removed: building smaller ROMs, mobile data connection, Flight mode, WIFI & BT
Revision V1.3 20121214 Updates: New GAPPS from 20121212
Revision V1.2 20121211 Updates: Bluetooth working, WiFi Networks showing and more. Plus typo fixes.
Revision V1.1 20121206 Updates: Partition size, swapping internal/external memory, USB mass-storage mode.
Revision V1.0 20121201 Initial release
Thanks to key.ita, XXMrHyde, tonyp, Custom40 and marsgod for their contributions to this FAQ.
Where are the Google Applications - GAPPS?
Get the fixed GAPPS here. Fix: The 'bugged' gesture typing is disabled. That's due to Tegra2 which isn't supporting NEON instructions. With the fix you can use the keyboard as usual without force closes.
Or you can get the 'original' GAPPS from 20121212 for 4.2.1 here. Download and flash them via CWM.
The keyboard is force closing all the time. Is there a solution?
Yes. Just flash the fixed GAPPS over your installation via CWM. The gesture typing will be disabled but you can use the AOSP keyboard then as you used it in the previous versions. It's up to you but now you can disable the useless gesture trail, dynamic floating preview etc. under 'Settings>>>Language & input>>>Android keyboard AOSP>>>Enable gesture typing'. Then remove the tick from 'Enable gesture typing' and you are ready to use the AOSP keyboard without any problems.
What bootloader should be used?
You have to use the old bootloader.
Any Baseband recommendations?
I am using the 30B Baseband. You can find it in tonyp's Baseband thread under 'ICS Basebands'. But it is working with other BBs like V20L as well.
[/I]
What about the partition size? Will this ROM (including the GAPPS) fit in the old partition layout?
Yes, it does. Some files get copied to /data so the ROM plus GAPPS fit the old partition size completely.
The 'Developer options' from 'settings' are gone. Where are they?
Touch the 'Build number' seven times in 'about phone'. Then they will appear.
How do I use the external SD-Card as the internal memory (swap SD-Cards)?
Edit the 'vold.fstab' file on your phone under 'system/etc/' and change the lines to:
Code:
dev_mount sdcard /storage/sdcard0 auto /devices/platform/sdhci-tegra.2/mmc_host/mmc1
dev_mount emmc /storage/sdcard1 9 /devices/platform/sdhci-tegra.3/mmc_host/mmc0
If you want to use it permanently on your building system and in every ROM you make then edit '~/CM10.1/device/lge/p990/vold.fstab' and use the both lines above accordingly.
I want to transfer files from/to the phone via USB. How do I turn on the mass-storage mode?
Use the terminal on the phone or use adb shell:
Code:
su
setprop persist.sys.usb.config mass_storage
And reboot. When you use your Computer's USB connection the next time, Android will ask you whether you like to switch on the mass-storage mode.
I want to use the mass-storage mode in my builds. What can I do?
I included it in the ROM building process by editing "~/CM10.1/device/lge/star-common/star.mk'. At the very end of the file you find the line 'persist.sys.usb.config=mtp'. Change it to 'persist.sys.usb.config=mass_storage'. Next time you build a new ROM the mass-storage mode is included. Tip: if you are updating your ROM then sometimes you have to make the switch manually (one time only!) as described above to initiate the change.
Are there any other problems?
I think it is awesome!!! Very fast, nice camera, same energy usage as CM10. I am using it as my daily driver. (well, since Nov 28 now... :fingers-crossed
Please build CM10.1 yourself and test it thoroughly. Maybe we can remove some of the remaining problems together.

Reserved for future use

nice guide :silly:

mivv a lazy one....
Are the sources downloading fast? I didn't try Paranoid... You said few coffees... I think I drank a bucket of coffee and it still wasn't there = went to sleep
I'll try, Although I am busy with my pi... that sdcard corruption bug with OC driwes me crazy, I guess I'll ssh my kitchen PC too do something in parallel...

Does this build has the call bug or it's like Benee's hackfest free of it?
and Raum1807 does HW acceleration work?

Will do this guide next week. Just finished REMICS TOUCHWIZ UX now released for everyone. Then Motorola UI... So next week I'll have time
Sent from my Xoom using XDA Premium HD app

Might give this a go myself, but as you said, it's still in pretty early stages of development.
Thanks for the useful guide though

Shouldn't the file's name be local_manifest.xml?
I.e.
Code:
$ gedit ~/cm10.1/.repo/local.manifest
needs to be changed into
Code:
$ gedit ~/cm10.1/.repo/local_manifest.xml
in order for it to work. Right?

svante38 said:
Shouldn't the file's name be local_manifest.xml?
I.e.
Code:
$ gedit ~/cm10.1/.repo/local.manifest
needs to be changed into
Code:
$ gedit ~/cm10.1/.repo/local_manifest.xml
in order for it to work. Right?
Click to expand...
Click to collapse
Of course. Corrected it. Thanks!

puma99dk| said:
Does this build has the call bug or it's like Benee's hackfest free of it?
and Raum1807 does HW acceleration work?
Click to expand...
Click to collapse
HWA is working. It is basically running like CM10.
The call bug hasn't occurred to me (yet). But I think it is the wrong name anyway: in my opinion it is an microphone/audio bug.
In this ROM the RIL and audio are a bit different. So maybe this bug isn't there. But this is a good reason why I would like to see more people building and testing CM10.1.

Raum1807 said:
Of course. Corrected it. Thanks!
Click to expand...
Click to collapse
Also, looking at your patch, it seems to point to directories on your local machine:
Code:
/home/ac64/cm10.1/...
Shouldn't this be changed to:
Code:
~/cm10.1/...
In order for it to work on all computers?

Can someone upload a build of this?
Sent from my LG-P990 using xda app-developers app

svante38 said:
Also, looking at your patch, it seems to point to directories on your local machine:
Code:
/home/ac64/cm10.1/...
Shouldn't this be changed to:
Code:
~/cm10.1/...
In order for it to work on all computers?
Click to expand...
Click to collapse
By applying the patch with the "-p 4" argument, the first 4 "parts" of the path will be ignored,
by typing:
Code:
cd ~/cm10.1
patch -p4 < CM10.1_building.patch
the path will be "set" correct.
It`s a better to do it this way, so the patch is working also if your path to your repo is different,
e.g. your repo path is CM10.1/android/system/
you have to type:
Code:
cd ~/cm10.1/android/system/
patch -p4 < CM10.1_building.patch
But you can change the path in the CM10.1_building.patch to ~/CM10.1...
but in this case, you have to change the -p4 argument to -p0, or just apply the patch without -p argument

XXMrHyde said:
By applying the patch with the "-p 4" argument, the first 4 "parts" of the path will be ignored,
by typing:
Code:
cd ~/cm10.1
patch -p4 < CM10.1_building.patch
the path will be "set" correct.
It`s a better to do it this way, so the patch is working also if your path to your repo is different,
e.g. your repo path is CM10.1/android/system/
you have to type:
Code:
cd ~/cm10.1/android/system/
patch -p4 < CM10.1_building.patch
But you can change the path in the CM10.1_building.patch to ~/CM10.1...
but in this case, you have to change the -p4 argument to -p0, or just apply the patch without -p argument
Click to expand...
Click to collapse
Oh I see. Thanks for clearing that up.
Thanks OP for the building instructions too, teaching people to fish instead of just providing them one!

Raum1807 said:
HWA is working. It is basically running like CM10.
The call bug hasn't occurred to me (yet). But I think it is the wrong name anyway: in my opinion it is an microphone/audio bug.
In this ROM the RIL and audio are a bit different. So maybe this bug isn't there. But this is a good reason why I would like to see more people building and testing CM10.1.
Click to expand...
Click to collapse
I highly doubt a magic fix
Sent from my Optimus 2X using xda app-developers app

Custom40 said:
Might give this a go myself, but as you said, it's still in pretty early stages of development.
Thanks for the useful guide though
Click to expand...
Click to collapse
if you get it done, please share

last i have test a CM10.1 from EaglesBlood and there work no camera and BB28g has no Signal... would in this CM10.1 all fixed??

See the Screenshots in post #1, signal is working,
just building CM10.1, will report if camera is working

MetaIIica said:
last i have test a CM10.1 from EaglesBlood and there work no camera and BB28g has no Signal... would in this CM10.1 all fixed??
Click to expand...
Click to collapse
EaglesBlood is not CM, its based on AOSP.

[GUIDE] Building CyanogenMod 10.2 for Nexus 4 with Ubuntu 13.04 x64 + NIGHTLIES

If you are looking for my nightly builds, you can find them here.
{
"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"
}
NOTE: Official nightly builds for CM 10.2 are now available! Get them here.
Click to expand...
Click to collapse
So after countless hours of frustration and face-desking, I finally managed to make a working build of CyanogenMod 10.2 (Android 4.3). To make the process slightly less painful for you, I've decided to create this noob-friendly guide. This is my first development guide, so feel free to leave criticism or suggestions through PM.
Prerequisites
You will need:
A relatively recent computer running Ubuntu with a reasonable amount of RAM (I recommend at least 4 GB) and around 35 GB of free hard drive storage
A decent internet connection
Some understanding of basic Android and Linux operation and terminology is helpful
NOTE: This guide is for Ubuntu 13.04 x64, but should work with other relatively recent versions of Ubuntu as well; i.e. 12.04, 12.10.
Click to expand...
Click to collapse
Setting up the build environment
The first thing you need to do is install the correct Java Development Kit/JDK, Oracle Java 6. If you have OpenJDK installed, you have to uninstall it by typing this command into the terminal, which can be brought up by pressing Ctrl+Alt+T or searched for in the dash.
Code:
sudo apt-get purge openjdk*
To install Oracle Java 6, type this into the terminal (one line at a time):
Code:
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java6-installer
y
Android SDK requires the x32 compatability packages, ia32-libs. Install it by entering this:
Code:
sudo apt-get install ia32-libs
y
Now you will need to get the Android SDK/Software Developer Kit, if you haven't already. Go ahead and download it here.
Extract it to a folder of your choice (in this guide, I will refer to it as ~/android/sdk) and from that folder, enter these commands into the terminal:
Code:
cd ~/android/sdk/adt-bundle/sdk/tools
./android sdk
Click Install packages. cd to ~/android/sdk/adt-bundle/sdk/platform-tools and type:
Code:
adb
fastboot
If you've done everything correctly, you should get a big block of text for both (which list all of the adb/fastboot commands).
Next, install the build packages. Copy and paste this command into the terminal:
Code:
sudo apt-get install git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.8-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev pngcrush schedtool libxml2 libxml2-utils xsltproc g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline-gplv2-dev gcc-multilib
y
You will now need to set up the directories for your build environment. Type this into the terminal:
Code:
mkdir -p ~/bin
mkdir -p ~/android/cm-10.2
Set up the repo binary (used for syncing your local repository with the CM source):
Code:
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
NOTE: In order to run the repo command when you're not in ~/bin (the folder where you saved the repo binary), you need to add it to your path of execution. To do this, type:
Code:
gedit ~/.bashrc
And then add the line
Code:
export PATH=${PATH}:~/bin
to the top of the file and click save. You can do the same for the adb and fastboot commands by adding
Code:
export PATH=${PATH}:~/android/sdk/adt-bundle/sdk/tools
export PATH=${PATH}:~/android/sdk/adt-bundle/sdk/platform-tools
to the file.
Click to expand...
Click to collapse
Syncing your local repository with the CM source
The next step is to initialize the repository and download the CM source code to your computer. Type the following lines into the terminal:
Code:
cd ~/android/cm-10.2
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
repo sync
You have now begun downloading all of the CM source code to your build directory. Depending on your internet speed, this can take up to a couple of hours. If the sync interrupts, don't worry. Simply continue the sync (you don't have to restart completely, only the project you were downloading when the interrupt occured, phew) by entering:
Code:
repo sync
Remember, you need to cd into your build directory (~/android/cm-10.2, if you've been following this guide) for the command to work.
Go and get yourself a drink or something, this step takes a long time.
NOTE: If the sync gets stuck at 99%, stop the sync (exit the terminal window), open up a new one, cd to your build directory, and type the following:
Code:
repo sync -j1
This reduces the amount of threads/connections to 1 for the final unsynced project(s). It should work.
Click to expand...
Click to collapse
Now comes the fun part: Building
You're almost to the end! In order to make a working build, you have to get the proprietary files (mainly device build files and drivers) for the Nexus 4. The easiest way to do this is to create a file named "roomservice.xml" in the ~/android/cm-10.2/.repo/local_manifests directory. Now, .repo is a hidden directory, so in order to access that directory you can either 1) show hidden files and folders in Nautilus (the Ubuntu file manager) or 2) access the folder and create the file using terminal commands. Both methods are explained below (2 is probably easier, but does not always work, in my experience).
1) Open up a Nautilus window. Navigate to your build directory (once again, ~/android/cm-10.2) and press Ctrl+H. This allows you to see hidden files and folders. You should see a folder labelled .repo. Enter it and inside, create a directory called "local_manifests", if there isn't already one. Enter that folder and create a blank file called "roomservice.xml". Next, copy the following lines into the file and press save:
Code:
<manifest>
<project name="TheMuppets/proprietary_vendor_lge.git" path="vendor/lge" remote="github" revision="cm-10.2"/>
</manifest>
2) Type this into the terminal:
gedit ~/android/cm-10.2/.repo/local_manifests/roomservice.xml
ext, copy the following lines into the file and press save:
Code:
<manifest>
<project name="TheMuppets/proprietary_vendor_lge.git" path="vendor/lge" remote="github" revision="cm-10.2"/>
</manifest>
If you get an error, try method 1.
Do another repo sync:
Code:
repo sync
After this, you can download the necessary pre-built apps:
Code:
~/android/cm-10.2/vendor/cm/get-prebuilts
Finally, you will build. If you aren't there already, cd to your build directory and run the following commands in the terminal:
Code:
. build/envsetup.sh
brunch mako
Now, just let your computer do the rest. This step is very demanding for your computer, so I recommend you leave it alone while it builds. Go get another drink.
Done? If everything went correctly, cd to ~/android/cm-10.2/out/target/product/mako and you should see your newly built ROM entitled:
cm-10.2-20xxxxxx-UNOFFICIAL-mako.zip
Congratulations! You've successfully built CM 10.2!
For re-builds (i.e. when the source code has been updated and you would like to make a new nightly), just do this:
Code:
cd ~/android/cm-10.2
make clean [I](for incremental builds, you can skip this step. You can also do make clobber; thanks [user=4520802]@obtained[/user])[/I]
repo sync
. build/envsetup.sh
brunch mako
If you ever encounter an error or problem and need help, feel free to post here or send me a PM.
Happy building, everyone!
Sources:
How To Build CyanogenMod Android for Google Nexus 4 ("mako")
http://wiki.cyanogenmod.org/w/Build_for_mako
[GUIDE] How to build CM10.1 (Android 4.2.1) for the Nexus 4 (mako)
http://forum.xda-developers.com/showthread.php?t=2047981
[GUIDE] Building CM10.2 for Nexus 4 with Mac OS X 10.8.X)[UPDATED: 8.8.2013]
http://forum.xda-developers.com/showthread.php?t=2087318
UBUNTU 12.04 - INSTALL ANDROID TOOLS (ADB, FASTBOOT, ...)
http://bernaerts.dyndns.org/linux/245-ubuntu-precise-install-android-sdk

Reserved

Nice thanks for the guide muchly appreciated!
Sent from my Nexus 4 using Tapatalk 4

Other phones
Very nice guide, but i was wondering if this is working for other phones too? Which i think it does but i was kind of wondering about this part "Now comes the fun part: Building", i want to do this on samsung galaxy s2 (gt-i9100), will i write the same things (execpt from bunch mako)?

You missed the "repo sync" command after creating roomservice.xml file, it is necessary to download the device specific files. (sorry my english)

Cheerpipe said:
You missed the "repo sync" command after creating roomservice.xml file, it is necessary to download the device specific files. (sorry my english)
Click to expand...
Click to collapse
You are absolutely correct. Thanks for that
Sent by carrier pigeon

Chekhn said:
Very nice guide, but i was wondering if this is working for other phones too? Which i think it does but i was kind of wondering about this part "Now comes the fun part: Building", i want to do this on samsung galaxy s2 (gt-i9100), will i write the same things (execpt from bunch mako)?
Click to expand...
Click to collapse
You'd also need the correct proprietary (device-specific) files. I'm not sure that TheMuppets has the files for the i9100. You may need to extract them from a working build of CM yourself.
You can check out CM's guide for your device here: http://wiki.cyanogenmod.org/w/Build_for_i9100
Sent by carrier pigeon

klvnhng said:
You'd also need the correct proprietary (device-specific) files. I'm not sure that TheMuppets has the files for the i9100. You may need to extract them from a working build of CM yourself.
You can check out CM's guide for your device here: http://wiki.cyanogenmod.org/w/Build_for_i9100
Sent by carrier pigeon
Click to expand...
Click to collapse
I have checked the CM build guide, but i don't get the zip file when i do cd $OUT, have been searching but no answer and I can't find any threads or posts with this problem.

Chekhn said:
I have checked the CM build guide, but i don't get the zip file when i do cd $OUT, have been searching but no answer and I can't find any threads or posts with this problem.
Click to expand...
Click to collapse
You probably didn't get the device blobs correctly. I did a search for the i9100 and it turns out that TheMuppets repo does have it.
So for roomservice.xml:
Code:
<manifest>
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.2" />
</manifest>
And when building:
Code:
brunch i9100

klvnhng said:
You'd also need the correct proprietary (device-specific) files. I'm not sure that TheMuppets has the files for the i9100. You may need to extract them from a working build of CM yourself.
You can check out CM's guide for your device here: http://wiki.cyanogenmod.org/w/Build_for_i9100
Sent by carrier pigeon
Click to expand...
Click to collapse
TheMuppets does have i9100 proprietary files.
Edit: looks like I'm 1 minute late.
Also: make clobber and make clean are the same for cm. "make clobber" actually does a "make clean".
Sent from my Nexus 4 using xda premium

@klvnhng
Are you sure we can make this with Java 7?. I tried some days ago to build AOSP and some other ROM´s, and I had so much problems becasue of the Java version when building. I had Java 7, but specifically the build asked for Java 6, so I had to downgrade.
Another question would be if it is necessary to download the code for all the devices, instead of downloading the code just for Mako.
Thanks.

Galaxo60 said:
@klvnhng
Are you sure we can make this with Java 7?. I tried some days ago to build AOSP and some other ROM´s, and I had so much problems becasue of the Java version when building. I had Java 7, but specifically the build asked for Java 6, so I had to downgrade.
Another question would be if it is necessary to download the code for all the devices, instead of downloading the code just for Mako.
Thanks.
Click to expand...
Click to collapse
Hmm...you may be correct. I have both 6 and 7 installed, so it could be that I'm actually using 6.
Edit: JDK 6 is required (http://source.android.com/source/initializing.html). I have a mixed environment.
And yes, in order to build CM, you need to have the entire source repo synced. Sorry

Thank you for the help guys!

Excellent!
Great guide... Very thorough and informative. Getting ready to build my first 10.2 shortly... Thanks again

VoiD_Dweller said:
Great guide... Very thorough and informative. Getting ready to build my first 10.2 shortly... Thanks again
Click to expand...
Click to collapse
Let me know how it goes!

wow i needed this thread since 1 month i am trying but not able to build properly now u r here to help thnkx.

I will try ! Thx
Sent from my Nexus 4 using xda app-developers app

Noob's question ; what are the differences between a home compiled rom and the rom you can download on the CM website ?

klvnhng said:
Let me know how it goes!
Click to expand...
Click to collapse
Got the build done.. flashed it, flashed gapps, everything works excellent!
One thing though, I noticed the build size of the zip is 9 mb larger than the official nightly for yesterday. Whats up with that?
Also what are the perks of building on ubuntu 13.04 vs the recommended 12.04 I always see in the other guides? are the tools more optimized or something? I'm a linux newb so excuse me if it's a lame question
---------- Post added at 08:06 AM ---------- Previous post was at 08:05 AM ----------
french-anonymous said:
Noob's question ; what are the differences between a home compiled rom and the rom you can download on the CM website ?
Click to expand...
Click to collapse
You built it, and you don't have to wait for their build server. Also after you learn more about it, you can customize and add things of your own.. basically.

VoiD_Dweller said:
Got the build done.. flashed it, flashed gapps, everything works excellent!
One thing though, I noticed the build size of the zip is 9 mb larger than the official nightly for yesterday. Whats up with that?
Click to expand...
Click to collapse
To be honest, I'm not quite sure. My builds average 206 MB.
VoiD_Dweller said:
Also what are the perks of building on ubuntu 13.04 vs the recommended 12.04 I always see in the other guides? are the tools more optimized or something? I'm a linux newb so excuse me if it's a lame question
Click to expand...
Click to collapse
Apparently, the 3.8 kernel included in 13.04 handles tasks more efficiently. There are other optimizations as well, I'm sure. Most people recommend 12.04 because it is a LTS version and therefore will have bug fix and security updates for for 5 years, as opposed to 9 months. But I like to keep up-to-date :good:

[GUIDE] Understanding and using Gerrit [Easy+Explained]

So, what happened to me in the past few days was that, I had to submit few patches to gerrit, and I had no idea what to do, where to start, and everything that runs in the mind of a person who first uses gerrit. One simply doesn't gets the whole knowledge he needs to use gerrit at one place, so I decided to make it, so it could be easier for the new users. ​
Click to expand...
Click to collapse
So firstly, I'll explain few terms that are important for you to learn before going towards a bit tricky side. ​
Git - To be precise, git is a code-sharing website/software that allows you to share your project resources you can 'Make Software, better, together'(That's what the tag line says )!
Now, before I go to gerrit, read this: Major Open Source Projects, like, CyanogenMod, AOKP, OmniROM etc. don't directly accept pull requests and in case you want to make a change in their source for a fix/feature or anything, you need to send them patches over gerrit which are then reviewed by the trusted members of the community and if they find it valuable enough, gets merged into the git repository!
Gerrit(Copying the definition from Wiki) - Gerrit is a free, web-based team software code review tool. Software developers in a team can review each other's modifications on their source code using a Web browser and approve or reject those changes. It integrates closely with Git, a distributed version control system.
So, now, git and gerrit are so closely related, that a patch verified over gerrit can directly be merged on git without much hassel, also please note that your gerrit and git username must be same.
Pull Requests - Pull requests are sent over Git after you fork a repository, make some changes into it and then want the owner to merge those changes into his repository, and that's how community development and Open Source works.
Patches - In simple terms, any changes you make to repos of Open Source Projects like CM or AOKP and send them over gerrit for code review are called Patches.
How GERRIT works?! ​
Now, Gerrit is deployed in place of this central repository and adds an additional concept, a store of pending changes. Everyone still fetches from the authoritative repository but instead of pushing back to it, they push to this pending changes location. A change can only be submitted into the authoritative repository and become an accepted part of the project once the change has been reviewed and approved.
I found a nice diagram explaining this over the internet that will clear your doubts(if any ) -
{
"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"
}
Now few important stuff needs to be setup before proceeding-​
Setting up Git:
Debian/Ubuntu:
Code:
sudo apt-get install git
Fedora:
Code:
yum install git
ArchLinux:
Code:
pacman -S git
openSUSE:
Code:
zypper install git
Configuring git:
Code:
git config --global user.email "[email protected]"
Code:
git config --global user.name "your-username"
Setting up SSH Keys(Skip this if you have already set them up) -
Code:
cd .ssh
ssh-keygen -t rsa -C "[email protected]"
Now this will create 2 files in ~/.ssh directory as follows:
~/.ssh/id_rsa //identification (private) key
~/.ssh/id_rsa.pub //public key
Click to expand...
Click to collapse
Adding SSH Keys to your Account -
Code:
cat /home/username_on_pc/.ssh/id_rsa.pub
This will show up few lines over terminal, copy those and add them into your git profile(I won't explain that, there are many guides for the same)
Now install few packages -
Code:
sudo apt-get install python-pip
sudo pip install git-review
Now comes setting up the Gerrit part -​
In case of CyanogenMod,
Code:
git config --global review.review.cyanogenmod.org.username "gerrit username"
git config --global review.review.cyanogenmod.org.email "email you registered with"
In case of AOKP,
Code:
git config --global review.gerrit.aokp.co.username <gerrit username>
git config --global review.gerrit.aokp.co.email <email you registered with>
Making Changes and Submitting Patches -​
I'd firstly recommend you to repo sync to grab the full latest source.
Next(Don't make changes before this step) -
Code:
repo start <branch> <path to make changes
Example(You need to be in the source directory) -
Code:
repo start kitkat packages/apps/Settings
Now after this, go into the folders, make your changes and save them but only the changes in the specified directories(Packages/apps/Settings in this case)!
then
Code:
cd packages/apps/Settings
After making changes, for satisfaction, run,
Code:
git status
It tells you what files you modified(In Red color ) and shows on which branch you're currently on.
Now, the committing part,
Run:
Code:
git add -A
Run git status again, and it'll show the files in green color, telling you that the changes have been added.
Now:
Code:
git commit -s
This will commit the changes and open up a Text Editor called NANO. Here you need to edit the commit message that appears at the side of the gerrit window to describe what the patch does.
After writing the commit message, press Ctrl+O and then Enter key to save the commit message and then Ctrl+X to exit the editor. This is the committing part done. :good:
Now submitting the patch -
Code:
repo upload .
After this, it will ask you Yes/No twice(For the first time) and once(Everytime next) and you obviously have to hit Y!
Guess what?! Done!
Congratulations, you just learned gerrit and know how you use it. I hope you'll send some nice patches and respect the Open Source. :victory:
But, wait, what if there is a merge conflict :crying::crying:
Don't worry, there is a nic doc over the internet to help you with this - http://www.mediawiki.org/wiki/Gerrit/resolve_conflict
If you still have doubts, see few examples here or ask on the thread. I'll be happy to hrlp! :victory:
Credits -
> Firstly, My Parents :angel:
> @galaxyfreak @championswimmer @crossfire77 to introducing me to gerrit.
> AOKP/CM team for hosting useful docs.

Ok, so you have changes to make to the gerrit commit you just sent? Read on ​
Ok, it goes easy,
repo start like earlier, make changes, go to the directory where the changes were made(Settings in this case). Now, make sure you go to the patch URL now and copy up the Change ID, which can be done by clicking over it.
Now, git status to spot the changes.
The,
Code:
git add -A
and
Code:
git commit --amend
^This will tell git that you need to amend an existing commit. Cool, isn't it?
Now, make changes(if any) to the commit message. and then
Code:
repo upload .
YES, That's it! The new change will now be at the same URL under Patch Set 2! And will got 3, 4 so on as you make changes.

Reserved!

Really a Great work !

Great work !
git config --global review.gerrit.omnirom.org.username "gerrit username"
git config --global review.gerrit.omnirom.org.email "email you registered with"
Here are the configs required for omnirom.

Unable to patch
#Superuser said:
Ok, so you have changes to make to the gerrit commit you just sent? Read on ​
Ok, it goes easy,
repo start like earlier, make changes, go to the directory where the changes were made(Settings in this case). Now, make sure you go to the patch URL now and copy up the Change ID, which can be done by clicking over it.
Now, git status to spot the changes.
The,
Code:
git add -A
and
Code:
git commit --amend
^This will tell git that you need to amend an existing commit. Cool, isn't it?
Now, make changes(if any) to the commit message. and then
Code:
repo upload .
YES, That's it! The new change will now be at the same URL under Patch Set 2! And will got 3, 4 so on as you make changes.
Click to expand...
Click to collapse
When I do the above commands to provide a patch to CyanogenMod gerrit it gives a new Change-ID and got committed as a new 'Merge Commit'. Can you tell me where I am going wrong? :crying:

solomonsunder said:
When I do the above commands to provide a patch to CyanogenMod gerrit it gives a new Change-ID and got committed as a new 'Merge Commit'. Can you tell me where I am going wrong? :crying:
Click to expand...
Click to collapse
You sure that you ran git commit --amend ?

patchset
#Superuser said:
You sure that you ran git commit --amend ?
Click to expand...
Click to collapse
Yes. I tried to follow your post and this one wiki.cyanogenmod.org/w/Doc:_using_gerrit. I did a change earlier here. review.cyanogenmod.org/#/c/59083/ for a new translation. Since there were whitespace errors and a file strings.xml~ got added, I changed my local file, deleted the strings.xml~, did a git add strings.xml. Then I did a git commit --amend which gave me a new Change-ID which said Merge commit 'refs/changes/83/59083/1' of review.cyanogenmod.org/CyanogenMod/android_frameworks_base into SystemUITamil. Then I did a repo upload. This got uploaded as review.cyanogenmod.org/#/c/59286/ :crying:
I tried to manually change the Change-ID to I52f02ea81fa7e20334e7ac7f26d37ced6fe54489 and then do a repo upload. But it didn't allow me and gave a message ! [remote rejected] SystemUITamil -> refs/for/cm-11.0 (squash commits first)
Where am I going wrong?

Rebase worked
#Superuser said:
You sure that you ran git commit --amend ?
Click to expand...
Click to collapse
I did a rebase on frameworks/base and then followed your steps. Now it is working fine. :good: I used to do a repo start branchname projectpath even for patches. Could that have been a reason it was creating new changes?

solomonsunder said:
I did a rebase on frameworks/base and then followed your steps. Now it is working fine. :good: I used to do a repo start branchname projectpath even for patches. Could that have been a reason it was creating new changes?
Click to expand...
Click to collapse
I never actually close the Terminal after submitting a patch and verifying it, so not sure, maybe it lost track of the changes you made and the change that got uploaded. Rebase is actually useful in this. :good: Glad that you figured it out.

Hi @v_superuser,
Thanks for the guide. I reached upto "repo upload ." step but after that it returns upload failed.
Can you please help me out with this? I registered on aicp gerrit and also added publickey on gerrit.
Link to screenshot.

Says "Make sure you have correct rights" could be some rom specific stuff they have done for repo or seeing the rest, it could be something with your ssh keys.
You sure you're using same email id and username on git and gerrit?

v_superuser said:
Says "Make sure you have correct rights" could be some rom specific stuff they have done for repo or seeing the rest, it could be something with your ssh keys.
You sure you're using same email id and username on git and gerrit?
Click to expand...
Click to collapse
No, username is different. Email id is same.
I cannot change either of them now.
I was able to connect via ssh using [email protected] (Nikhil is username in gerrit)
nikhilmenghani is my username in github.
Any thoughts?

Nikhil said:
No, username is different. Email id is same.
I cannot change either of them now.
I was able to connect via ssh using [email protected] (Nikhil is username in gerrit)
nikhilmenghani is my username in github.
Any thoughts?
Click to expand...
Click to collapse
Use same git and gerrit username.

@v_superuser
I tried again and facing the same error
Code:
Upload project frameworks/native/ to remote branch kitkat:
branch kitkat ( 1 commit, Sat Oct 4 22:55:31 2014 +0530):
8dd591e7 DisplayDevice: Backwards compatibility with old EGL
to gerrit.aicp-rom.com (y/N)? y
The authenticity of host '[gerrit.aicp-rom.com]:29418 ([195.154.174.249]:29418)' can't be established.
RSA key fingerprint is 8c:9c:82:a7:4e:4f:8c:c6:c3:21:3d:c0:38:5d:25:58.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '[gerrit.aicp-rom.com]:29418,[195.154.174.249]:29418' (RSA) to the list of known hosts.
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Any thoughts?
I added public key to gerrit.aicp-rom.com from id_rsa.pub file too.

Nikhil said:
@v_superuser
I tried again and facing the same error
Code:
Upload project frameworks/native/ to remote branch kitkat:
branch kitkat ( 1 commit, Sat Oct 4 22:55:31 2014 +0530):
8dd591e7 DisplayDevice: Backwards compatibility with old EGL
to gerrit.aicp-rom.com (y/N)? y
The authenticity of host '[gerrit.aicp-rom.com]:29418 ([195.154.174.249]:29418)' can't be established.
RSA key fingerprint is 8c:9c:82:a7:4e:4f:8c:c6:c3:21:3d:c0:38:5d:25:58.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '[gerrit.aicp-rom.com]:29418,[195.154.174.249]:29418' (RSA) to the list of known hosts.
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Any thoughts?
I added public key to gerrit.aicp-rom.com from id_rsa.pub file too.
Click to expand...
Click to collapse
No idea. You registered on gerrit too, right?

v_superuser said:
No idea. You registered on gerrit too, right?
Click to expand...
Click to collapse
Yes I did.
Anyway, busy with other things so not trying much as of now.
Thanks for help!

Thank you OP for explainations. I see these termes (git, gerrit...) in lots of threats but never tried to understand. Now it's more clear in my head
Sent from my GT-I9305 using XDA Free mobile app

ok so i am starting to come along in my cm port for my phone, now i want to be able to upload the changes it gerrit for review,,
its for the i9305 s3,, now i have all the i9305 device tree setup for cm12.1 and its working pretty much 80% bugless..
if i go repo start it says error: project device/samsung/i9305 not found do i have to repo init the project before i can repo start
and as the s3 is officially supported up until kitkat syncing the cm12.1 source does not sync the device repos needed, would i need to repo clone the cm11 device tree and start a new branch for lollipop

I want to upload a commit for a device kernel (for example Oneplus 3) to lineage . How to do it ? I have to download lineage source code ?

[DEV] Building a Marshmallow Kernel for Zenfone 5/6

Development: Building a Marshmallow Kernel for Zenfone 5/6​
Prerequisites:
Ubuntu 16.10 (Installation Guide)
~5 GiB of Available Disk Space
Establishing a Build Environment
Open a Terminal Emulator (Ctrl+Alt+T)
Install the latest Ubuntu updates:
Code:
sudo apt-get update
sudo apt-get dist-upgrade
Add the OpenJDK 7 Repository:
Code:
sudo add-apt-repository ppa:openjdk-r/ppa
sudo apt-get update
Install the Required packages by Android:
Code:
sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z-dev ccache libgl1-mesa-dev libxml2-utils xsltproc unzip maven yasm optipng openjdk-7-jdk
Install Repo:
Code:
sudo wget https://storage.googleapis.com/git-repo-downloads/repo -O/usr/bin/repo
sudo chmod +x /usr/bin/repo
Install Wine (you'll need it for AndImgTool):
Code:
sudo dpkg --add-architecture i386
sudo add-apt-repository ppa:wine/wine-builds
sudo apt-get update
sudo apt-get install --install-recommends winehq-devel
Setup Wine (don't modify the settings, just press OK):
Code:
WINEARCH=win32 winecfg
Setup Git:
Code:
git config --global user.name "Your Name"
git config --global user.email "[email protected]"
Recommended: Reboot.
Downloading the Source:
Create a Working Directory:
Code:
mkdir -p ~/Kernel
cd ~/Kernel
Initialize the Repository:
Code:
repo init -u git://github.com/intel-ctp/android.git -b zf5/kernel
Download the Code:
Code:
repo sync -c -j4
Important: Remove a Conflicting Directory: (you may face build errors if you don't run that)
Code:
rm -Rf bionic/tests
Building the Kernel:
Prepare the build environment:
Code:
. build/envsetup.sh
lunch mini_T00F-user
Build minigzip:
Code:
make -j4 minigzip
Build the Kernel:
Code:
make -f KernelMakefile -j4 build_kernel
make -f KernelMakefile -j4 modules_install
make -f KernelMakefile -j4 copy_modules_to_root
Generating the Boot Image:
Download the Ramdisk to a Working Directory:
Code:
cd ~
git clone https://github.com/zf5/Kernel.git Boot -b cm-13.1
Enter Working Directory:
Code:
cd Boot
Download AndImgTool:
Code:
wget https://basketbuild.com/uploads/devs/dgadelha/ASUS_T00F/Tools/AndImgTool.exe
Remove my prebuilt files:
Code:
rm -v PARTS/BZIMAGE
rm -Rv ramdisk/lib/modules/*
Copy your just-built kernel files:
Code:
cp -v ~/Kernel/out/target/product/T00F/kernel PARTS/BZIMAGE
cp -Rv ~/Kernel/out/target/product/T00F/root/lib/modules/* ramdisk/lib/modules/
Generate your Boot Image:
Code:
wine AndImgTool.exe . boot.img
Enjoy your Kernel!
Also check out: Development: Building CyanogenMod 13 for Zenfone 5/6

Great,
Thank you!

i dont think its a good idea by using wine for building

ccxex29 said:
i dont think its a good idea by using wine for building
Click to expand...
Click to collapse
You'll just use Wine to generate the boot.img. It works and I tested it. All my Boot images were generated using it.

@dgadelha Hey, thanks for the good work there. How would you suggest me to edit kernel default config with menuconfig? I tried to copy and use defconfig but it was problematic. I wanted to hear your opinions on this. Thanks.
Sent from my ASUS_T00F using Tapatalk

smgdev said:
@dgadelha Hey, thanks for the good work there. How would you suggest me to edit kernel default config with menuconfig? I tried to copy and use defconfig but it was problematic. I wanted to hear your opinions on this. Thanks.
Sent from my ASUS_T00F using Tapatalk
Click to expand...
Click to collapse
Hi @smgdev
I already played a lot with menuconfig, but if you want to try out, that's how I recommend you to do:
Cleanup your build environment, delete the out/target/product and kernel/asus directories
Run a repo sync
Play with menuconfig:
Code:
make -f KernelMakefile TARGET_DEVICE=hd menuconfig
When you finish, press Save and save it as "defconfig", your file will be now at out/target/product/asusctp_hd/kernel/linux/defconfig
Copy your new defconfig to Desktop and cleanup the environment again (delete out/target/product/asusctp_hd and kernel/asus)
Run another repo sync
Copy your defconfig to kernel/asus/T00F, replacing mine
Build it.
That's my recommended way to use menuconfig, keeping the environment cleanest as possible.
Thanks.

dgadelha said:
Hi @smgdev
I already played a lot with menuconfig, but if you want to try out, that's how I recommend you to do:
Cleanup your build environment, delete the out/target/product and kernel/asus directories
Run a repo sync
Play with menuconfig:
Code:
make -f KernelMakefile TARGET_DEVICE=hd menuconfig
When you finish, press Save and save it as "defconfig", your file will be now at out/target/product/asusctp_hd/kernel/linux/defconfig
Copy your new defconfig to Desktop and cleanup the environment again (delete out/target/product/asusctp_hd and kernel/asus)
Run another repo sync
Copy your defconfig to kernel/asus/T00F, replacing mine
Build it.
That's my recommended way to use menuconfig, keeping the environment cleanest as possible.
Thanks.
Click to expand...
Click to collapse
Oh, and i was wondering why I was getting compilation errors. Thank you so much! Never thought a repo sync. But I have a 2-3 line mac802.11 patch. Can I apply it as soon as I repo sync? I do not experience problems with that patch.
Thank you so much again!
Sent from my ASUS_T00F using Tapatalk

smgdev said:
Oh, and i was wondering why I was getting compilation errors. Thank you so much! Never thought a repo sync. But I have a 2-3 line mac802.11 patch. Can I apply it as soon as I repo sync? I do not experience problems with that patch.
Thank you so much again!
Click to expand...
Click to collapse
Hi @smgdev
Yes, you can do it.
But also you could submit the patch directly to the GitHub repository to be available to everyone.
Thanks.

@dgadelha hey, its me again and sorry for bothering you again.
I am porting nethunter kernel, its a tx injection patch but I can submit it if you want.
Anyways, can you see the problem?
{
"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"
}
Sent from my ASUS_T00F using Tapatalk

smgdev said:
@dgadelha hey, its me again and sorry for bothering you again.
I am porting nethunter kernel, its a tx injection patch but I can submit it if you want.
Anyways, can you see the problem?
Sent from my ASUS_T00F using Tapatalk
Click to expand...
Click to collapse
Edit cpiostatfile.txt and remove the mentioned missing file.
Thanks.

dgadelha said:
Edit cpiostatfile.txt and remove the mentioned missing file.
Thanks.
Click to expand...
Click to collapse
Fixed one line and moved modules to lib/modules from lib root. That might be an issue of Makefile. Suggest you to check it. Anyway, I built the image and its working. Thank you for dealing with my ignorance.
By the way, do you have communication with BORETS24? I have to get into touch with him/her for his/her HID keyboard patch.

smgdev said:
Fixed one line and moved modules to lib/modules from lib root. That might be an issue of Makefile. Suggest you to check it. Anyway, I built the image and its working. Thank you for dealing with my ignorance.
By the way, do you have communication with BORETS24? I have to get into touch with him/her for his/her HID keyboard patch.
Click to expand...
Click to collapse
Hi @smgdev
Your issue was because you modified your defconfig and disabled (or changed to built-in) the module t4k35_180 and then it was not generated, not fault of Makefile or etc.
Then, AndImgTool threw an error because it could not find the file (which was mentioned at cpiostatfile.txt).
So basically it is, for every file that you add or remove from the ramdisk, you need to update cpiostatfile.txt.
Thanks.

dgadelha said:
Hi @smgdev
Your issue was because you modified your defconfig and disabled (or changed to built-in) the module t4k35_180 and then it was not generated, not fault of Makefile or etc.
Then, AndImgTool threw an error because it could not find the file (which was mentioned at cpiostatfile.txt).
So basically it is, for every file that you add or remove from the ramdisk, you need to update cpiostatfile.txt.
Thanks.
Click to expand...
Click to collapse
I found out the error wasn't t4k35_180.ko generating. Modules were copied to a wrong directory. boot/lib instead of boot/lib/modules which was declared in the cpiostatfile. I was talking about that. Anyway,
You are the best, thanks for everything.
Sent from my ASUS_T00F using Tapatalk

smgdev said:
I found out the error wasn't t4k35_180.ko generating. Modules were copied to a wrong directory. boot/lib instead of boot/lib/modules which was declared in the cpiostatfile. I was talking about that. Anyway,
You are the best, thanks for everything.
Sent from my ASUS_T00F using Tapatalk
Click to expand...
Click to collapse
Ah, thanks. I'll fix that.

Hey, probably a silly question but;
What should I change to port a stock-rom booting kernel to run CM-based rom kernel?
I have both sources of two kernels and I need to make stock-booting kernel to CM-booting kernel (for an experiment).

ozank said:
Hey, probably a silly question but;
What should I change to port a stock-rom booting kernel to run CM-based rom kernel?
I have both sources of two kernels and I need to make stock-booting kernel to CM-booting kernel (for an experiment).
Click to expand...
Click to collapse
By "stock-rom booting kernel" you mean the kernel-only (bzImage) or full boot image (bzImage+Ramdisk)?

dgadelha said:
By "stock-rom booting kernel" you mean the kernel-only (bzImage) or full boot image (bzImage+Ramdisk)?
Click to expand...
Click to collapse
Actually I need to port Borets24 to CM13 again for some experiments and I think the both of source codes has bz+RDisk.

ozank said:
Actually I need to port Borets24 to CM13 again for some experiments and I think the both of source codes has bz+RDisk.
Click to expand...
Click to collapse
Build his bzImage, normally, and use my Ramdisk.
I built his kernel before and it had many issues (drain, lag, etc) and then I got back into stock. Unfortunately, I don't keep history of my builds.
And remember: disable SELinux

dgadelha said:
Build his bzImage, normally, and use my Ramdisk.
I built his kernel before and it had many issues (drain, lag, etc) and then I got back into stock. Unfortunately, I don't keep history of my builds.
And remember: disable SELinux
Click to expand...
Click to collapse
Thank you; yes, I saw that you were using in the earlier builds, I wanted to try with latest freeze-reboot things (some people were saying the freeze is not happening and I thought what if I recompile again for CM13 based roms and try it for 2-3 days).
Thanks again and have a good day.

Hey @dgadelha , so sorry to bother you again but as far as I know this devices boot.img structure is different. If so, can you explain it?
Thanks
Sent from my ASUS_T00F using XDA-Developers mobile app

LazyFlasher - make and install your own custom kernels!

INTRODUCTION
Hello Pixel C users and developers! I saw your device forum is a little lonely, so I offer you this in the hopes it may become slightly more eventful and 2017 becomes the year of the Pixel C development!
I expect that before you start, you have a Linux installation in either a virtual machine or on a physical PC.
Debian Jessie, Kali Linux, Mint, or Ubuntu are excellent choices and what I'm familiar with, so if you get stuck it'll be easier for me to help you if you use these.
NEED LINUX? I'VE GOT YOU COVERED
If you don't have a Linux installation, consider installing the latest version of Oracle VM VirtualBox.
You can download a minimal Debian VM from my site: https://build.nethunter.com/possibly-the-coolest-things/Debian.ova (SHA1SUM)
It should be fairly simple to "Import Appliance..." from VirtualBox and set up the Shared Folders properly, everything else is set up for you!
Username: root
Password: xda
Once logged in, create your own user account from LXTerminal:
Code:
adduser [b]yourname[/b]
# answer the questions, you can leave it all blank except the password if you want>
echo "[b]yourname[/b] ALL=(root) NOPASSWD: /bin/su" > /etc/sudoers.d/me
The second command will allow you to type "su" to become root whenever you need.
You should then log out and log in to your new account instead.
PREREQUISITES
First off, you'll want to download some tools necessary for building and downloading kernel sources:
bc - a tool needed by the kernel build system
git-core - you'll want git for downloading and maintaining your sources
build-essential - native gcc & tools for building (needed for build commands)
libncurses5-dev - needed to build menuconfig
diffutils - used to compare config changes
colordiff - used by diff to provide colorful human readable diff output
Code:
apt-get install bc git-core build-essential libncurses5-dev diffutils colordiff
PREPARING YOUR ENVIRONMENT
Once you've got that out of the way, you should create an organized environment for working. I like to use ~/build.
Code:
mkdir -p ~/build/toolchain ~/build/kernel
DOWNLOADING & INSTALLING A TOOLCHAIN
You'll want to download a toolchain for kernel building. I recommend using Linaro's optimized ARM64 (aarch64) toolchains.
GCC 4.9: https://releases.linaro.org/components/toolchain/binaries/4.9-2016.02/aarch64-linux-gnu/
GCC 5.X: https://releases.linaro.org/components/toolchain/binaries/latest-5/aarch64-linux-gnu/
The actual file that you want ends in -x86_64_aarch64-linux-gnu.tar.xz (assuming you have a 64-bit Linux install, seriously, 32-bit needs to go! )
We'll use the GCC 5.3.1 2016.5 toolchain in this example.
Let's download and extract it now:
Code:
cd ~/build/toolchain
wget "https://releases.linaro.org/components/toolchain/binaries/latest-5/aarch64-linux-gnu/gcc-linaro-5.3.1-2016.05-x86_64_aarch64-linux-gnu.tar.xz"
tar xf ./*linux-gnu.tar.xz
rm ./*linux-gnu.tar.xz
That's it for installing the toolchain, easy right?
DOWNLOADING THE KERNEL
First, you'll want to create a GitHub account if you don't have one already.
This will allow you to upload your changes and share your kernel with other interested users and developers.
Once you've got your account, and you're logged in, browse to:
https://github.com/jcadduono/android_kernel_google_chromeos
You want to fork the sources to your own account, to do this simply click the [Fork | ] button near the top right of the page:
{
"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"
}
Now you've got your own copy of the Google ChromeOS (dragon / ryu) 3.18 kernel sources on your GitHub!
The next step is to use git to download it to your PC.
Replace "your_username" with your actual GitHub username. Using [email protected] you can avoid being asked for your username each time you push new changes.
Code:
cd ~/build/kernel
git clone https://yo[email protected]/your_username/android_kernel_google_chromeos
cd android_kernel_google_chromeos
The default branch is android-7.1. This is what most users will want. I've added build and menuconfig scripts to assist in building for you.
There may be some additional branches available to choose from.
You can use git log <branch> to view commits, and git cherry-pick <commit id> to copy commits from those branches into yours if you like.
CONFIGURING GIT
Before you start working on your kernel, you will need to set up your git profile.
The user values show up in commit messages to tell people who authored them.
Code:
git config --global user.name "Your Name"
git config --global user.email "[email protected]"
git config --global push.default simple
YOUR FIRST COMMIT
We'll want to check out a new branch, and give it your own cool name. I suggest adding a -7.1 suffix to it because you'll probably want to start a new branch for each time a new version of Android releases.
We're going to use "coolname" as our example, so be sure to replace that with what you really want it to be called in the next steps.
Code:
git checkout -B coolname-7.1
Next we'll need to modify the build scripts to fit our setup.
Open build.sh and menuconfig.sh.
You'll want to set the TOOLCHAIN= path in both scripts. If you're following this guide, then it's already correct!
You will also want to set your default target config name.
See the line:
Code:
[ "$TARGET" ] || TARGET=google
You'll want it to look like this:
Code:
[ "$TARGET" ] || TARGET=coolname
Now you want to copy the default Google kernel configuration so you have your own to work with:
Code:
cp arch/arm64/configs/google_dragon_defconfig arch/arm64/configs/coolname_dragon_defconfig
Now you'll have prepared your kernel source for starting work on your own custom kernel!
Let's turn that into a commit, but first look at the changes you've made using:
Code:
git diff
Does that look good? If not, fix what's broken before proceeding.
Next you'll want to add files that will be part of your commit.
For simplicity's sake, let's just add all of the changed files into the commit.
Code:
git add .
Now to make your commit:
Code:
git commit -m "My first commit, setting up my coolname kernel!"
You've done it!
CONFIGURING YOUR KERNEL
We'll use the menuconfig.sh script to launch the kernel menuconfig.
Code:
./menuconfig.sh
Change whatever options you're interested in, but don't change a lot all at once, otherwise when or if you run into issues, you won't know which option caused it.
Once you're done playing in the menuconfig, exit and save.
You'll be shown a colorful difference between your old configuration and your new one.
It will ask you if you want to save it, and you just have to type "y" and press enter for it to be saved.
At this point it's a good idea to make another commit to save your configuration changes.
If you need to edit the commit, you can easily use git commit --amend to fix it up.
BUILDING YOUR NEW KERNEL
Let's take your new config for a test drive.
To build your kernel, simply run:
Code:
./build.sh dragon
Once your kernel is finished building, the resulting files will be located at:
Code:
build/arch/arm64/boot/Image.fit
build/lib/modules/ (if modules are enabled)
INSTALLING YOUR NEW KERNEL
The LazyFlasher project comes to the rescue here. It's the swiss army knife of kernel flashing in TWRP.
To download it (feel free to fork it so you can have a copy on your GitHub to modify instead!):
Code:
cd ~/build
git clone -b kernel-flasher https://github.com/jcadduono/lazyflasher.git
cd lazyflasher
To use LazyFlasher, you'll probably want to take a look at the Makefile, config.sh, and META-INF/com/google/android/update-binary (a shell script).
There's a few things you can change there to personalize it to your needs.
(make another git commit to save your setup!)
Once the installer is set up to your liking, all you have to do to build it is copy the Image.fit from your build output into the lazyflasher folder.
If you have built with kernel modules, copy build/lib/modules -> lazyflasher/modules.
Now simply run:
Code:
make
A TWRP flashable zip and sha1sum is created!
Transfer it to TWRP and flash away, you've just lost your custom kernel development virginity.
Go have a few beers to celebrate, or to drown your sorrows in the case of a boot loop.
UPDATING THE KERNEL SOURCES
Of course my repository will become out of date after a while. In this situation, you want to add a remote that is more updated.
We'll use Google's official Pixel C kernel repository here.
Inside your kernel source directory, run the command:
Code:
git remote add google -t chromeos-3.18 https://chromium.googlesource.com/chromiumos/third_party/kernel
Every time you want to fetch updates from Google's branch, run the command:
Code:
git fetch google --tags
After fetching updates, you have to apply them. You can choose between a rebase strategy or a merge strategy.
In most cases you'll want to use the merge strategy.
The merge strategy will merge Google's updates into your branch.
The rebase strategy will move your work on top of Google's latest instead.
Code:
# the merge strategy (pick one, recommended)
git merge google/chromeos-3.18
# the rebase strategy (will require a force push and rewrite history, not recommended)
git rebase google/chromeos-3.18
JUST WANT TO DISABLE VERITY/ENCRYPTION?
You can build lazyflasher by itself, empty, without a kernel Image.fit or modules and flash it!
It's already set up to automatically disable verity and make encryption optional.
Alternatively, there's a branch already set up called no-verity-opt-encrypt. You can find prebuilt official zips at: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
It should work on any and all kernels!
PROBLEMS?
Post a reply here and I'll try to find a solution and add it to this post.
RESOURCES
Need a text editor for coding? I use gedit. It's pretty, light, and you can get some decent plugins for it.
It's a minimal editor, so don't expect anything really fancy. Configure it and enable plugins before you decide to trash it.
Code:
apt-get install gedit gedit-plugins
Here's an awesome git starter guide: http://rogerdudler.github.io/git-guide/

Lazy flasher worked great for me, on Linux.

OMFG this is a wonderfu TUT maybe it requires more knowledge than I have but I take a look this weekend (I use and love Ubuntu a lot).
Also I know you from OP 3T forums and your development is amazing, is nice to see good developers and development here.
Thanks!!!

I've followed your instructions, but I'm not finding a dtbgen.sh in the kernel/android_kernel_google_chromeos/ folder. Am I missing something? I have the build.sh and the menuconfig.sh...

michaave said:
I've followed your instructions, but I'm not finding a dtbgen.sh in the kernel/android_kernel_google_chromeos/ folder. Am I missing something? I have the build.sh and the menuconfig.sh...
Click to expand...
Click to collapse
Fixed the guide, I combined it into build.sh for simplicity at some point. It has been some time since the repository was updated, but you should be able to simply add google as a remote and fetch & rebase to be up-to-date. (I think I mentioned this already)

this looks pretty cool! :good:
Q: are the pre-built no-verity zips Pixel-C specific, or can they be used on any device?

... doesnt work for me - the compiled kernel always ends up in a boot loop

hagbardceline23 said:
... doesnt work for me - the compiled kernel always ends up in a boot loop
Click to expand...
Click to collapse
Pls try to use the sources from here ..
https://android.googlesource.com/kernel/tegra/
If you use chromeos 3.18 you need to know what to exclude
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/chromeos-3.18
Its the full 3.18 with changes for all relevant devices.
Have a try with tegra sources and start with dragon_defconfig.
It will boot
Cheers

thanks !!! works like a charm with the tegra sources

I expect that before you start, you have a Linux installation in either a virtual machine or on a physical PC.
Debian Jessie, Kali Linux, Mint, or Ubuntu are excellent choices and what I'm familiar with, so if you get stuck it'll be easier for me to help you if you use these.
Click to expand...
Click to collapse
For what it's worth, I've successfully rebuild the kernel on the Ubuntu Userspace on Windows: https://insights.ubuntu.com/2016/03...-the-ubuntu-userspace-for-windows-developers/
And then flashed it with LazyFlasher.
Thanks for your work!

I have an idea to customize the kernel, but at the moment I can't open the kernel, these are farther away for me, but I want to make it my first device developed.

Panokiaran said:
I have an idea to customize the kernel, but at the moment I can't open the kernel, these are farther away for me, but I want to make it my first device developed.
Click to expand...
Click to collapse
thank you