Develop Bugs

How to build an AOSP Kernel?

So I pretty much would like to start building my own kernels and Roms from AOSP, but not sure where to start. I have downloaded the SDK already, and started downloaded some file with git and these commands:
git clone https://android.googlesource.com/kernel/omap
cd omap
git checkout origin/android-omap-tuna-3.0-mr0
but the guides I've been reading don't offer much more help. And then there is a toolchain of some sort? I can get my way around linux fairly well and have built my own kernels about a year and a half ago for my Vibrant, but took a completely different course.
Was wondering if someone could point me in the right direction, thanks!

You're on the right track. Use Linux ubuntu, install all the packages, the Android tool chain, then just clone the aokp kernel like you showed. But you had the wrong repo link. Go to team kangs github page, go to the nexus kernel, then at the top will be their git link in a box.
Git clone "link"
Then just run the make command in terminal. Make sure you navigated yo the downloaded kernel folder.

RogerPodacter said:
You're on the right track. Use Linux ubuntu, install all the packages, the Android tool chain, then just clone the aokp kernel like you showed. But you had the wrong repo link. Go to team kangs github page, go to the nexus kernel, then at the top will be their git link in a box.
Git clone "link"
Then just run the make command in terminal. Make sure you navigated yo the downloaded kernel folder.
Click to expand...
Click to collapse
Thanks a lot, will try that. The link on their page is AOSP?
Sent from my Galaxy Nexus using XDA

The guy is asking us on how to clone AOSP tuna kernel tree, and you tell him to clone teamKang kernel project?
@op, no, you dont have the incorrect url. Clone from there, then checkout branch android-omap-3.0.
Type:
'make tuna_defconfig'
'make -j4'
You'll then have a zimage in arch/arm/boot, which you'll need to merge with a compatible ramdisk (either by fastboot or manually).
sent from my i9250

bk201doesntexist said:
The guy is asking us on how to clone AOSP tuna kernel tree, and you tell him to clone teamKang kernel project?
@op, no, you dont have the incorrect url. Clone from there, then checkout branch android-omap-3.0.
Type:
'make tuna_defconfig'
'make -j4'
You'll then have a zimage in arch/arm/boot, which you'll need to merge with a compatible ramdisk (either by fastboot or manually).
sent from my i9250
Click to expand...
Click to collapse
Sweet will continue with these steps and look onto the merge
Sent from my Galaxy Nexus using XDA

bk201doesntexist said:
The guy is asking us on how to clone AOSP tuna kernel tree, and you tell him to clone teamKang kernel project?
@op, no, you dont have the incorrect url. Clone from there, then checkout branch android-omap-3.0.
Type:
'make tuna_defconfig'
'make -j4'
You'll then have a zimage in arch/arm/boot, which you'll need to merge with a compatible ramdisk (either by fastboot or manually).
sent from my i9250
Click to expand...
Click to collapse
Oh holy crap haha I completely thought he asked about aokp kernel, my bad I didn't read.

AOSP kernel for HTC Explorer/Pico
Can you tell me how to build aosp kernel for htc explorer?

monishvster said:
Can you tell me how to build aosp kernel for htc explorer?
Click to expand...
Click to collapse
Just do the same thing, but instead sync the htc kernel rather than the nexus. Go search and find out if source code has been released for that phone.
Then just run the make command.

Somebody call 911, we've been hijacked
Note: 'make tuna_defconfig' is for maguro, i dont know what is the name of default config file for the htc, why should we? User should refer to htc explorer subforum @xda or to kernel documentation.
Sent from my i9250

[ROM][AOSPA][DIY][GUIDE] How to build Paranoid Android for Endeavoru

This is DIY
If you are just looking for a well done and stable PA download, you are probably the wrong place. Then go and grab xzzz9097s build, it's good!
If you are impatient and know what to do, just leave and do the init/sync/build.
For anyone wanting to build her/his own PA without any "extras", go ahead and read on.
We already have a very easy full guide to compile CM10 for HOX. I was looking for the same for ParanoidAndroid, but did not find a 100% guide, meaning I had to do it myself.
To be fair, I only needed to do 1% as you will see after the usual disclaimer. I hope this little guide will be enough to make anyone complile their own PA for the HOX.
The usual disclaimer:
I am no developer!
I just happen to be able to read and understand instructions. I am persistent and know how to search for answers.
With luck and patience I ended up with a 184MB zip, that installs and runs just fine on my HOX.
I pass this guide as it is now, no guarantee no returns. I will probably not be able to help much here, time is very limited, so no commitments for support from me.
If it breaks you device, you broke it all by yourself
I am no developer!
gokussjx made the general guide, explaining how to port Paranoid Android 3.xx to different devices.
It works 99% for Endeavoru. The last 1% takes some effort to get right.
For me, not knowing what I am doing, it took a lot of trial and error, but eventually, - I made it and might as well pass it on here.
I'm in debt to all the people helping out in that thread. Huge thanks!
To get started, just follow a few simple steps:
You need a linux setup.
Install as your main system or run it in windows with VirtualBox.
Most guides are expecting Ubuntu. I use Mint Debian 64, which is just perfect for this job (and everything else ).
For VirtualBox you need at least a 50GB virtual-drive. Add 16GB if you will use ccache. I have build PA with a 52GB VBox in Win7.
It was just enough to compile, but had no room for ccache!
Compile time (VBox) on EliteBook 8540w (i7) was 120min. Not too bad, considering my old DeskTop need close to 4 hours on pure Linux.
Expect to download 8GB of source. Add 18GB for building to the "out" folder.
Enough statistics now, let's get started.
Follow gokussjx guide to setup linux for PA compiling.
Follow only these steps:
# Install OpenSSL, for Python
# Install Dependencies
# Configure USB
# JAVA JDK Installation
# Python Installation (just pick option 1)
# Android SDK
Click to expand...
Click to collapse
Exit gokussjx guide and continue here:
Download your favorite arm toolchain:
I found mine here.
Just extract the archive to any folder with user access, later you will point the build system to the /bin folder of the toolchain.
Install CCACHE:
Code:
$ sudo apt-get install ccache
Activate it in .bashrc:
Code:
# use ccache
export USE_CCACHE=1
You can change max-cache size, 16G should be enough for this build.
From terminal:
Code:
$ ccache -M 16G
Install Repo:
Code:
$ mkdir ~/bin
$ PATH=~/bin:$PATH
$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
Download the build manifest:
Code:
$ mkdir -p padroid/system
$ cd padroid/system
$ repo init -u git://github.com/teemodk/manifest.git -b padroid
Get the source!
Code:
$ repo sync -j16
Find this section in "build/envsetup.sh" update with your favorite arm toolchain:
Code:
case $ARCH in
x86) toolchaindir=x86/i686-linux-android-$targetgccversion/bin
;;
arm) toolchaindir=[B]~/toolchain/linaro4.8/bin[/B]
;;
mips) toolchaindir=mips/mipsel-linux-android-$targetgccversion/bin
;;
Go!
Code:
$ ./rom-build.sh endeavoru
Thats all. If it went well, get your new ROM in "out/target/product/endeavoru"
Don't forget the gApps.
Credits go to
PA:molesarecoming, D4rKn3sSyS for the awesome hybrid magic. All PA contributors. gokussjx for the mother of all PA guides. All the helpful people here, that use their time to help.
CM(aosp):thöemy,gorbi16,tbalden,(pabx) and all the unknown soldiers contributing to CM
Everyone I forgot.​

Differencies from the official guide.
The official PA manifest is put together in a way, so you can easily build and maintain multiple devices with only one manifest.
It works by adding and removing device specific code with local manifests under the "vendor/pa" folder.
However, I am only compiling for OneX, so I found it easier to add/remove stuff directly in the main manifest.
The downside to this is, that you have to manually maintain the manifest everytime you want to sync with PA. Place for improvement
All changes in STEP 2 of the official guide, is already done if using my guide with padroid manifest.
In vendor/pa these steps are done:
Code:
* Create [URL="https://github.com/teemodk/padroid_vendor_pa/blob/padroid/manifests/endeavoru.adds"]/manifest/<device>.adds[][/URL]
* Create [URL="https://github.com/teemodk/padroid_vendor_pa/blob/padroid/manifests/endeavoru.removes"]/manifest/<device>.removes[/URL]
* Create [URL="https://github.com/teemodk/padroid_vendor_pa/blob/padroid/prebuilt/pa_endeavoru.conf"]/prebuilt/pa_<device>.conf[/URL]
* Create [URL="https://github.com/teemodk/padroid_vendor_pa/blob/padroid/products/pa_endeavoru.mk"]/products/pa_<device>.mk[/URL]
* Add device makefile entry to [URL="https://github.com/teemodk/padroid_vendor_pa/blob/padroid/products/AndroidProducts.mk"]/products/AndroidProducts.mk[/URL]
* Create [URL="https://github.com/teemodk/padroid_vendor_pa/tree/padroid/vendorprops"]/vendorprops/<device>.proprietaries[/URL]
* Add device lunch menu entry to [URL="https://github.com/teemodk/padroid_vendor_pa/blob/padroid/vendorsetup.sh"]/vendorsetup.sh[/URL]
Furthermore, I temporarily moved the CM adds/removes from "vendor/pa/manifests" to .repo/manifest.xml.
I am sure there are better ways to handle git/repo/manifest etc., but this works well for me for now. Open for suggestions though.
Problem Solving
If (when) you run into problems, go to the official guide and find the answer. Most, if not all, errors is already answered there. If not, ask.
But first make a serious effort to find the error yourself. Read some good advice about finding the error.
As a rule of thumb: The build system tells you where to find the error! Something is missing, something is duplicated or somthing is just wrong. It's all in the log, running up your screen when compiling.​

Build 25.Oct.2013
http://d-h.st/XRt

Nice, I'm always eager to learn this stuff .
Thanks!

ROM uploaded to post 3.

teemo said:
ROM uploaded to post 3.
Click to expand...
Click to collapse
Thank you so much Teemo, for providing the guide and the rom.
Just a Q: is this stock ParanoidAndroid rom (stock kernel?) ?
Thanks again for your work :good:

Mat08.cc said:
Thank you so much Teemo, for providing the guide and the rom.
Just a Q: is this stock ParanoidAndroid rom (stock kernel?) ?
Thanks again for your work :good:
Click to expand...
Click to collapse
The ROM is as close to stock as it get for OneX. It is really a mix of CyanogenMod and ParanoidAndroid. I follow the official build guide from PA-team.
The kernel is from same source as CM.
You can see everything in the manifest.

@teemo
your build is running fast and stable, congratulations! maybe you can keep updating this .. I appreciate it and I'm sure many other people would be of the same opinion

Sry,wrong threat....
Gesendet von meinem EndeavorU mit Tapatalk

Hi @teemo I was trying to build my own rom using a different source.
I'm pretty sure I've done things right except that when i start my build it ends up after few seconds saying: "Kernel source found, but no configuration was defined. Please add the TARGET_KERNEL_CONFIG variable to your BoardConfig.mk file"
I checked my BoardConfig.mk file and what I've got is TARGET_KERNEL_CONFIG := cyanogenmod_endeavoru_defconfig
I thought you may know how to help me with this!
Other infos: I'm tryn to build paranoidandroid 4.0 and i'm using cyanogenmod files for the endeavoru since i know aospa is cyanogenmod based right?
Hope you can help me :fingers-crossed:

Mat08.cc said:
Hi @teemo I was trying to build my own rom using a different source.
I'm pretty sure I've done things right except that when i start my build it ends up after few seconds saying: "Kernel source found, but no configuration was defined. Please add the TARGET_KERNEL_CONFIG variable to your BoardConfig.mk file"
I checked my BoardConfig.mk file and what I've got is TARGET_KERNEL_CONFIG := cyanogenmod_endeavoru_defconfig
I thought you may know how to help me with this!
Other infos: I'm tryn to build paranoidandroid 4.0 and i'm using cyanogenmod files for the endeavoru since i know aospa is cyanogenmod based right?
Hope you can help me :fingers-crossed:
Click to expand...
Click to collapse
Hi, I don't know what it takes to build ParanoidAndroid 4
But maybe you can ask in the Paranoid guide.
Or you can ask here for all other builds.
EDIT: Btw, to build PA4 or any other KitKat, you need the new sources for OneX (device+vendor+kernel). This guide will not work for KitKat.

teemo said:
Hi, I don't know what it takes to build ParanoidAndroid 4
But maybe you can ask in the Paranoid guide.
Or you can ask here for all other builds.
EDIT: Btw, to build PA4 or any other KitKat, you need the new sources for OneX (device+vendor+kernel). This guide will not work for KitKat.
Click to expand...
Click to collapse
I used the new sources but that was the result! I'll start from zero again to see if I missed something Thanks for the reply always really kind!

Mat08.cc said:
I used the new sources but that was the result! I'll start from zero again to see if I missed something Thanks for the reply always really kind!
Click to expand...
Click to collapse
the aospa dev build the aospa kitkat version...so a few days waiting and it will be there

One-X-master said:
the aospa dev build the aospa kitkat version...so a few days waiting and it will be there
Click to expand...
Click to collapse
Yeah I thought so! But I would love to learn! I have always looked to devs as to extraordinary people, understanding what makes them such would be great

Hey @teemo , sorry to bother you, but could you make an update build of PA? I don't have a stable connection, can't make a build of the new PA.. :/
Thanks man, take care

LuisDias said:
Hey @teemo , sorry to bother you, but could you make an update build of PA? I don't have a stable connection, can't make a build of the new PA.. :/
Thanks man, take care
Click to expand...
Click to collapse
All credits to @audahadi https://drive.google.com/folderview?id=0B-KjFDQ914F4dVdQLU9nT3VkMGc&usp=sharing

bosas200 said:
All credits to @audahadi https://drive.google.com/folderview?id=0B-KjFDQ914F4dVdQLU9nT3VkMGc&usp=sharing
Click to expand...
Click to collapse
Thanks brotha

teemo said:
Build 25.Oct.2013
http://d-h.st/XRt
Click to expand...
Click to collapse
Any chance helping me build AOSB with newer cm 11 base?
As no instructions anywhere on building AOSB from source. Source is
https://github.com/AOSB?page=1
Many thanks

Need Device tree

Hey people ,
Can someone provide a relevant Xiaomi Redmi 1s device tree so I can start building customs ROM's for this device....

hackerzrulez007 said:
Hey people ,
Can someone provide a relevant Xiaomi Redmi 1s device tree so I can start building customs ROM's for this device....
Click to expand...
Click to collapse
Here is The Device tree :
https://github.com/armani-dev/android_device_xiaomi_armani
and here vender tree :
https://github.com/armani-dev/proprietary_vendor_xiaomi

Getting error while compiling AOSP with the armani device tree
I cloned these repos in device/ and vendor/ directories respectively.
I then ran . build/envsetup.sh which ran but gave this.
including device/android_device_xiaomi_armani/vendorsetup.sh
sh: 0: Can't open device/xiaomi/armani/patches/apply.sh
I anyways went ahead and hit lunch and then this happened when i passed cm_armani-userdebug as the selection.
Which would you like? [aosp_arm-eng] cm_armani-userdebug
build/core/product_config.mk:222: *** Can not locate config makefile for product "cm_armani". Stop.
** Don't have a product spec for: 'cm_armani'
** Do you have the right repo manifest?
I am trying to compile android lollipop with this device tree. Will this work? and if it can then where am I doing wrong?

praveenpuglia said:
I cloned these repos in device/ and vendor/ directories respectively.
I then ran . build/envsetup.sh which ran but gave this.
including device/android_device_xiaomi_armani/vendorsetup.sh
sh: 0: Can't open device/xiaomi/armani/patches/apply.sh
I anyways went ahead and hit lunch and then this happened when i passed cm_armani-userdebug as the selection.
Which would you like? [aosp_arm-eng] cm_armani-userdebug
build/core/product_config.mk:222: *** Can not locate config makefile for product "cm_armani". Stop.
** Don't have a product spec for: 'cm_armani'
** Do you have the right repo manifest?
I am trying to compile android lollipop with this device tree. Will this work? and if it can then where am I doing wrong?
Click to expand...
Click to collapse
these device tree won't work for cm12 ie lolipop
there are patch, which should be done before compiling rom

Can you tell me more ? I am not trying to build cm lollipop..i am trying to build AOSP stock rom. I just want to know if the cm 11 device tree can be used to conpile AOSP rom!

praveenpuglia said:
Can you tell me more ? I am not trying to build cm lollipop..i am trying to build AOSP stock rom. I just want to know if the cm 11 device tree can be used to conpile AOSP rom!
Click to expand...
Click to collapse
Won't work. Will need heck loads of patches and dirty hacks and display and media repos should be taken from armani-dev.

kD said:
Won't work. Will need heck loads of patches and dirty hacks and display and media repos should be taken from armani-dev.
Click to expand...
Click to collapse
What about using those device trees for cm12?

praveenpuglia said:
What about using those device trees for cm12?
Click to expand...
Click to collapse
As said earlier won't work

Actually OP need 1st step guide with current repo .... I think

delete

Delete this thread

Well, i suddenly visited Mipad sub-forum on XDA and i saw this...
What? You just rename repository from android_device_nvidia_shieldtablet to android_device_xiaomi_mocha...
And it is ALL what you did ???? OMG. No comments. Facepalm.
So i spent 1 hour of my life to make a mocha bring up.
https://github.com/vickdu31/android_device_xiaomi_mocha/pull/1/files
Also you should merge commits which will update selinux to kernel sources.
+ Do not forget about upstream patches.
Cherry-pick it from
https://github.com/CyanogenMod/android_kernel_nvidia_shieldtablet
If YOU continue do nothing, you will receive no result.

tank0412 said:
Well, i suddenly visited Mipad sub-forum on XDA and i saw this...
What? You just rename repository from android_device_nvidia_shieldtablet to android_device_xiaomi_mocha...
And it is ALL what you did ???? OMG. No comments. Facepalm.
So i spent 1 hour of my life to make a mocha bring up.
https://github.com/vickdu31/android_device_xiaomi_mocha/pull/1/files
Also you should merge commits which will update selinux to kernel sources.
+ Do not forget about upstream patches.
Cherry-pick it from
https://github.com/CyanogenMod/android_kernel_nvidia_shieldtablet
If YOU continue do nothing, you will receive no result.
Click to expand...
Click to collapse
Don't blame him. There is a will and intention of him to cook a rom. Everybody needs help and everybody was a beginner.

Yeah I have been pretty busy at school and other stuff so I don't have time, and still I have to learn couple things, I pulled the request, thanks.
I did this in this time : http://gbatemp.net/threads/release-haxchi-installer-1-1-noob-friendly.448890/
I think there is no big hurry and I am really busy at the moment, my point is to get more people working and ofcourse I have to start working on it asap !

There are people working
They just don't open a thread without having done anything because that's not really development

Harrynowl said:
There are people working
They just don't open a thread without having done anything because that's not really development
Click to expand...
Click to collapse
Can't find anyone working on it.. Is there any thread, forum or group or anything where people work ? Even on github I didnt find anything

vickdu31 said:
Can't find anyone working on it.. Is there any thread, forum or group or anything where people work ? Even on github I didnt find anything
Click to expand...
Click to collapse
Yes, it could be great to join your effort to not repeat same work.
Regards.

vickdu31 said:
Can't find anyone working on it.. Is there any thread, forum or group or anything where people work ? Even on github I didnt find anything
Click to expand...
Click to collapse
@Harrynowl is working as far as I know. I'm too but very busy lately.

Status !!?
vickdu31 said:
I create this thread to gather all potential developpers to join me and try to build a CM13.0 (at least a build that boot) for our Mi Pad.
I don't have much experience or knowledge yet but who knows, maybe we can get bootable build soon or later.
To all users : Do not expect anything from this thread in a while.
Current situation :
Just created the device tree from Nexus and Xiaomi sources.
To do right now :
- Totally modify the Device Tree (this is from nexus 9)
- Modify kernel to be able to try to even build something
Here are the device tree :
Device Tree (from cm13 Nexus 9) : https://github.com/vickdu31/android_device_xioami_mocha
Kernel Tree (from Xiaomi KK) : https://github.com/vickdu31/android_kernel_xiaomi_mocha
Vendor Tree (old Xiaomi KK) : https://github.com/vickdu31/android_vendor_xiaomi_mocha
I think I cannot do everything all by myself within 6+ month so any help is very welcome just as pull requests.
XDA:DevDB Information
working on Mi Pad, ROM for the Xiaomi Mi Pad
Contributors
vickdu31
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-11-21
Last Updated 2016-11-26
Click to expand...
Click to collapse
Any progress to look forward to ?

Required help
Can some one guide me through the process of building the rom i already downloaded the cm 13 source. Searched many forums but not able to understand the process how to build for mocha @tank0412 @vickdu31 @Harrynowl

Rohit99 said:
Can some one guide me through the process of building the rom i already downloaded the cm 13 source. Searched many forums but not able to understand the process how to build for mocha @tank0412 @vickdu31 @Harrynowl
Click to expand...
Click to collapse
OMG.
Are you seriously?
. build/envsetup.sh
lunch
*enter number of mochas lunch combo"

You cannot build with these device sources because they are broken

Error while building
tank0412 said:
OMG.
Are you seriously?
. build/envsetup.sh
lunch
*enter number of mochas lunch combo"
Click to expand...
Click to collapse
Got this error while building using command
Code:
brunch mocha
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:234: *** Can not locate config makefile for product "cm_mocha". Stop.
Device mocha not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for mocha not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:234: *** Can not locate config makefile for product "cm_mocha". Stop.
** Don't have a product spec for: 'cm_mocha'
** Do you have the right repo manifest?
Click to expand...
Click to collapse
added repos in local_manifest.xml and roomservice.xml
Update :
i was able to brunch but stuck at this error
make: *** No rule to make target 'kernel/xiaomi/mocha/arch/arm/configs/cyanogenmod_mocha_defconfig', needed by '/home/uttara/rom/script/out/target/product/mocha/obj/KERNEL_OBJ/.config'. Stop.
make: *** Waiting for unfinished jobs....
Click to expand...
Click to collapse
@tank0412 please help

Rohit99 said:
Got this error while building using command
Code:
brunch mocha
added repos in local_manifest.xml and roomservice.xml
Update :
i was able to brunch but stuck at this error
@tank0412 please help
Click to expand...
Click to collapse
OMG. Are you seriously?
Put kernel sources to 'kernel/xiaomi/mocha/
It was writtent in the error!
No comments....
And rename defconfig of mocha to cyanogenmod_mocha_defconfig

tank0412 said:
OMG. Are you seriously?
Put kernel sources to 'kernel/xiaomi/mocha/
It was writtent in the error!
No comments....
And rename defconfig of mocha to cyanogenmod_mocha_defconfig
Click to expand...
Click to collapse
@tank0412 I'm very sorry for disturbing you this is my first build so please help, should i rename tegra_defconfig bcoz there is no file named defconfig

Rohit99 said:
@tank0412 I'm very sorry for disturbing you this is my first build so please help, should i rename tegra_defconfig bcoz there is no file named defconfig
Click to expand...
Click to collapse
Oh, GOD.
Check this:
https://github.com/vickdu31/android_kernel_xiaomi_mocha/pull/1/files
And turn on logic

Im working on other projects now, I don't have time at all, I can pull commits, I was thinking about closing this thread but since we can talk I can keep it open, but a discusion thread would be more apropriate

vickdu31 said:
Im working on other projects now, I don't have time at all, I can pull commits, I was thinking about closing this thread but since we can talk I can keep it open, but a discusion thread would be more apropriate
Click to expand...
Click to collapse
@vickdu31 you can close the thread i have created a new thread CM13

General Manifest FIle

Hello Fellow developer and programmer, I'm building a custom by using Ressurection Remix as a base, While I'm initializing the repo an error occurred, How to solve that. The Error is repo is not reccoginzsed as an internal or external command, I have installed the repo, thanks for the reading the post

LMGTFY - Let Me Google That For You
For all those people who find it more convenient to bother you with their question rather than to Google it for themselves.
bfy.tw

Deadshot0x7 said:
Hello Fellow developer and programmer, I'm building a custom by using Ressurection Remix as a base, While I'm initializing the repo an error occurred, How to solve that. The Error is repo is not reccoginzsed as an internal or external command, I have installed the repo, thanks for the reading the post
Click to expand...
Click to collapse
Download repo and make executable. Basic stuff man. Google as suggested above.

William.trem said:
Download repo and make executable. Basic stuff man. Google as suggested above.
Click to expand...
Click to collapse
thanks btw I'm new to custom rom

Deadshot0x7 said:
thanks btw I'm new to custom rom
Click to expand...
Click to collapse
I'm working on porting one myself. Repo is available within the Ubuntu apt-get repository. That can be a simpler way to install. However I'd suggest the curl & chmod method method for the latest binary as well as getting good experience.

Source control tools | Android Open Source Project
source.android.com
Downloading the Source | Android Open Source Project
source.android.com
2 sec to google

Follow the instructions to add the repository, then do an initial repo sync, I hope you have plenty of drive space cos some roms can take up many GB
The manifest instructions even link you to the guide for setting up git and repo
Ubuntu is usually the best platform for this, it might work in Windows subsystem for Linux but I've never tried so couldn't tell you.
Haven't built a rom for a while but you used to add device tree urls in .repo/local_manifests/roomservice.xml, it's probably still done the same way. (.repo is a hidden folder by default so, in Ubuntu, you would press CTRL+H to get it to show up)
If you don't know how to install repo then you will likely need to do a LOT of reading before you can even think of firing off a build.

djsubterrain said:
Follow the instructions to add the repository, then do an initial repo sync, I hope you have plenty of drive space cos some roms can take up many GB
The manifest instructions even link you to the guide for setting up git and repo
Ubuntu is usually the best platform for this, it might work in Windows subsystem for Linux but I've never tried so couldn't tell you.
Haven't built a rom for a while but you used to add device tree urls in .repo/local_manifests/roomservice.xml, it's probably still done the same way. (.repo is a hidden folder by default so, in Ubuntu, you would press CTRL+H to get it to show up)
If you don't know how to install repo then you will likely need to do a LOT of reading before you can even think of firing off a build.
Click to expand...
Click to collapse
Currently having success within WSL v1 Ubuntu.