Database Info

Building From from AOSP Source help

Hi all I have been trying to compile a pure stock from for my phone using someone elces kernel, device, and vendor directories. I synced the master branch of aosp repo and symlinked my sepreatly downloaded device directories to the proper directories. When I go to build, I use the command
Code:
. /build envsetup.sh && brunch ancora_tmo[Code]
I get
[Code]Including devices/samsung/ancora_tmo/vendorsetup.sh
No command 'brunch' found
[Code]
as well as 4 other aosp devices.
I added ancora tmo by symlinking the sources to my system tree.
I tried building with the command lunch and I get
[Code] don't have product specs for: full_ancora_tmo
Do you have right report manifest[Code]
where am I going wrong on building
I followed some custom build instructions and haven't modified much source yet but am simply trying to build pure stock for my phone what am I doing wrong?
Sent from my Galaxy Exhibit running Jocala's CM9

Try these:
Make sure you run the "PATH" command that it says to in SDK setup:
Code:
$ mkdir ~/bin
$ PATH=~/bin:$PATH
Also, if you are making a new device, try to use the mkvendor.sh script in build/tools/device

WhiteHatHacker said:
Try these:
Make sure you run the "PATH" command that it says to in SDK setup:
Code:
$ mkdir ~/bin
$ PATH=~/bin:$PATH
Also, if you are making a new device, try to use the mkvendor.sh script in build/tools/device
Click to expand...
Click to collapse
I did I setup the sdk and edited The .bashrc (or something similar) file
and added the sdk path
Sent from my Galaxy Exhibit running Jocala's CM9

Maybe the '-eng' part was missing
try:
Code:
brunch full_ancora_tmo-eng
or do everything:
Code:
brunch full-eng

WhiteHatHacker said:
Maybe the '-eng' part was missing
try:
Code:
brunch full_ancora_tmo-eng
or do everything:
Code:
brunch full-eng
Click to expand...
Click to collapse
Nope, still says brunch isn't found.
possible the report sync didn't complete right
Sent from my Galaxy Exhibit running Jocala's CM9

Who's kernel are you using?
You did:
Code:
source build/envsetup.sh
correct?

WhiteHatHacker said:
Whose kernel are you using?
Click to expand...
Click to collapse
jocala's custom rooted kernel
Sent from my Galaxy Exhibit running Jocala's CM9

WhiteHatHacker said:
Who's kernel are you using?
You did:
Code:
source build/envsetup.sh
correct?
Click to expand...
Click to collapse
Yes correct
I get this error when I try and build from the lunch menu
Don't have product specs for full_ancora_tmo
Do you have right report manifests.
Sent from my Galaxy Exhibit running Jocala's CM9

Its hard for me to help without browsing your directories, but try this.
Grab your boot.img
do:
Code:
build/tools/device/mkvendor.sh device_manufacturer_name device_name /your/path/to/the/boot.img
once that finishes, do:
Code:
lunch full_device_name-eng
then if you go to devices/product/something or other to your device, you should be able to try and replace your stock kernel with his.
I'm shooting from the hip here, so if i'm f***ed up please let me know, we're all learning ;-)

WhiteHatHacker said:
Its hard for me to help without browsing your directories, but try this.
Grab your boot.img
do:
Code:
build/tools/device/mkvendor.sh device_manufacturer_name device_name /your/path/to/the/boot.img
once that finishes, do:
Code:
lunch full_device_name-eng
[CODE]
then if you go to devices/product/something or other to your device, you should be able to try and replace your stock kernel with his.
I'm shooting from the hip here, so if i'm f***ed up please let me know, we're all learning ;-)[/QUOTE]
Huh? I think my repo sync didn't complete there is no device directory in build/ tools.
my directory is only 5.4gb in size that may be my whole problem
Sent from my Galaxy Exhibit running Jocala's CM9
Click to expand...
Click to collapse

Hmmm, then I'm tapped out.
But, at least this thread has been kept bumped
Whereas mine is back down near the bottom of the page :-(

WhiteHatHacker said:
Hmmm, then I'm tapped out.
But, at least this thread has been kept bumped
Whereas mine is back down near the bottom of the page :-(
Click to expand...
Click to collapse
Yep I think my source tree is jacked up I'll resyncing everything and see how that goes
thanks for helping
Sent from my Galaxy Exhibit running Jocala's CM9

No problem, best I could do was try.

[Guide] How to build CM10.1 (Android 4.2.1) for the Galaxy R I9103

Note:
1. This is extension to the Karthik's Guide with Adam's Repo's...
2. Based on my experience i have created this Guide, I have successfully compiled the Build and sharing this with you so some one can try it...
Preparing the system:
Follow this Link until step 4.4 (i.e. 4.4 - Initialize Repository & Sync)
Start with sources:
Code:
cd ~/android/system/
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 -j4
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 -j4
Initialize the environment
NOTE: If you have trouble syncing due to connection issues, try repo sync -j1. It's slower but some ISPs have issues with -j4/16
Want to make sure you didn't get any connection errors and have the complete repository? Just run the repo sync command again. It can't give you ANY errors.
Wait until it's finished (takes a lot of time!).
VERY IMPORTANT: Now, Lets add the device specific tree..
1) Open your File Browser,
2) Press Ctrl+H (to show hidden files/directories)
3) Navigate to android/system/.repo/manifest.xml
(Right Click & open the XML file in text editor)
4) Add
Code:
<project path="device/samsung/galaxyr" name="Adam77Root/android_device_samsung_galaxyr" remote="github" revision="jellybean"/>
BEFORE the manifest closing tags (</manifest>).
5) Save & Close the File.
Run another
Code:
$ repo sync
Get Device Specific Repos:
Code:
. build/envsetup.sh
Extract files from phone:
NOTE: You need to have cm10 installed on the phone.
Code:
cd ~/android/system/device/samsung/galaxyr/
./extract-files.sh
Code:
~/android/system/vendor/cm/get-prebuilts
Important Things to be taken care before Building ROM:
1. Add these line in Boarconfig.mk
Code:
TARGET_ARCH := arm
BOARD_EGL_NEEDS_LEGACY_FB := true
2. Change the below line.
Code:
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 5242880
to
Code:
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 7242880
3. Delete Overlay folder.
4. Go to build/tools/releasetools and open file "ota_from_target_files" and replace the whole code with this code from this link.
Ok, You are done Now...
Building the ROM:
Code:
brunch cm_galaxyr-eng
it will take around 2 - 3 Hours....
Congrats you are done
Now Go to ~/android/system/out/target/product/galaxyr/cm-10.1-XXXXXXXXX-UNOFFICIAL-galaxyr.zip copy it to mobile and flash it on your mobile..
*********************************************************************************​
Updating the Build:
Code:
cd android/system
repo sync -j1
make installclean
brunch cm_galaxyr-eng
Big Thanks to Adam for his Efforts and Device tree..
Friends if i've missed some things please correct me ...

Gr8 mj! It will be better if u post ur error and how u solved.. By that it help others...
Sent from my GT-I9103 using xda app-developers app

Waiting for cm10.1 ROM now. Using Cm 10 and it is great
Sent from my GT-I9103 using xda app-developers app

I will start building 10.1 today.
Edit: This is my 500th post.
Sent from my CM10-powered GT-I9103

Adam77Root said:
I will start building 10.1 today.
Edit: This is my 500th post.
Sent from my CM10-powered GT-I9103
Click to expand...
Click to collapse
wow that's cool buddy...

Adam77Root said:
I will start building 10.1 today.
Edit: This is my 500th post.
Sent from my CM10-powered GT-I9103
Click to expand...
Click to collapse
adam wat abt cm10 ?? will u abonden it ??
Sent from my GT-I9103 using Tapatalk 2

vipul12389mehta said:
adam wat abt cm10 ?? will u abonden it ??
Sent from my GT-I9103 using Tapatalk 2
Click to expand...
Click to collapse
Not yet. The first builds will be only previews. If 10.1 gets as stable as 10 now is, I'll change to it. But there is work to be done on 10 as well and better to do it on a working build first. But I'm also very excited to see 10.1, so will definitely work on it.

Mj, before running the get-prebuilts command, should I run extract-files.sh first to get the vendor/cm directory as mentioned in karthick's tut for CM10 ?
I'm studying through your's, karthick's, and PA's compiling guides to get to know about compiling roms and trying to understand every step.

sarun_biotech said:
Mj, before running the get-prebuilts command, should I run extract-files.sh first to get the vendor/cm directory as mentioned in karthick's tut for CM10 ?
I'm studying through your's, karthick's, and PA's compiling guides to get to know about compiling roms and trying to understand every step.
Click to expand...
Click to collapse
Yes buddy you need to run it...

Friends updated the Guide with all the details and problems i have faced, so now you can simply follow the steps and build CM 10.1...

Ran in to trouble right in the beginning. My process does not support virtualization (not a n option in BIOS too) and so cannot install 64 bit Ubuntu on VM player.
Do you guys have any alternate suggestions or is it possible to use 32 bit Ubuntu to compile ?

I used wubi... dual boot...

sarun_biotech said:
Ran in to trouble right in the beginning. My process does not support virtualization (not a n option in BIOS too) and so cannot install 64 bit Ubuntu on VM player.
Do you guys have any alternate suggestions or is it possible to use 32 bit Ubuntu to compile ?
Click to expand...
Click to collapse
Even i also faced this problem, so i need to install the Ubuntu through the CD in different partition so that i have both Windows 7 and Ubuntu 12.10 64 Bit...
If you have any problem just PM me...

Cm10 official
Is there a official CM10 for galaxy r. If yes plz snd the link.

akirockstarr said:
Is there a official CM10 for galaxy r. If yes plz snd the link.
Click to expand...
Click to collapse
CM 10 & 10.1 are official for Galaxy R users and Unofficial from CM Team point of view...
1. CM 10 Thread.
2. CM 10.1 Thread.

Guys Check out xda-university.com An answer to all our development questions. :thumbup:
Everything at a single place.

I am trying to build CM 10.1 by your instructions and while extracting files from phone (cm10.1 beta 2.2) few "not found" & chmod errors occur. Logs (only error lines) following. Sorry I could'nt attach as file.Is it fine?
Code:
[email protected]:~/mydev/cm10.1/device/samsung/galaxyr$ ./extract-files.sh
remote object '/system/etc/wifi/bcm4330_mfg.bin' does not exist
remote object '/system/etc/wifi/nvram_mfg.txt' does not exist
remote object '/system/bin/wlandutservice' does not exist
remote object '/system/bin/macloader' does not exist
remote object '/system/bin/mfgloader' does not exist
remote object '/system/bin/nv_hciattach' does not exist
chmod: cannot access `../../../vendor/samsung/galaxyr/proprietary/wlandutservice': No such file or directory
chmod: cannot access `../../../vendor/samsung/galaxyr/proprietary/macloader': No such file or directory
chmod: cannot access `../../../vendor/samsung/galaxyr/proprietary/mfgloader': No such file or directory
chmod: cannot access `../../../vendor/samsung/galaxyr/proprietary/nv_hciattach': No such file or directory
remote object '/system/bin/brcm_patchram_plus' does not exist
chmod: cannot access `../../../vendor/samsung/galaxyr/proprietary/brcm_patchram_plus': No such file or directory
remote object '/system/bin/drexe' does not exist
remote object '/system/bin/npsmobex' does not exist
chmod: cannot access `../../../vendor/samsung/galaxyr/proprietary/drexe': No such file or directory
chmod: cannot access `../../../vendor/samsung/galaxyr/proprietary/npsmobex': No such file or directory
Why are we extracting files from phone? The device tree should be holding them right?

kishoreinme said:
I am trying to build CM 10.1 by your instructions and while extracting files from phone (cm10.1 beta 2.2) few "not found" & chmod errors occur. Logs (only error lines) following. Sorry I could'nt attach as file.Is it fine?
Click to expand...
Click to collapse
Not an issue you can proceed with next command, it will take care of these files.....

No ZIP file after ROM build build

Hi
So I went for final build command->
Code:
mka bacon -j8
(my virtual machine is 4 cored).
It gives following output->
http://pastebin.com/CcNXpbSR
But there is no build file (that .zip file) in out/target/product/DeviceName/
Any help please.
PS->
I used these commands->
Code:
phablet-dev-bootstrap [target_directory]
repo sync -j3
. build/envsetup.sh
lunch cm_DeviceCodename-userdebug
mka bacon -j8
I basically didn't see any errors in outputs except "fatal: Invalid git file format: ...repo/repo/.git/clone.bundle" but thats network problem. Right? And btw the sync went fine after that. Even when I ran repo sync again (without deleting repo folder), it successfully fetched everything from existing files. There was no error then.
I also did run make clean command before building it, but still.....
Please help.

Building Android on MAC OS

Hi
I am trying to build Android on MAC OS X Yosemite(v10.10.1) machine.I have installed all the requirements as specified in source.android.com for setting up a MAC build environment(JDK,Python,Git etc.)
I have created a case sensitive file system in MAC and downloaded AOSP Master Branch to the working directory.
using these commands
repo init -u <link>
repo sync
Now to build this I've set up the environment using
$ . build/envsetup.sh
selected a target using
$ lunch aosp_arm-eng
Now when trying to make the Master branch in MAC build environment using 'make -B' the system hangs and restarts ( after about 30 minutes ). I have also tried 'make -B -j4' hoping to speed things up.
the Make process hangs at this step
minibp out/soong/.bootstrap/primary.ninja.in
Am i missing anything here?
Can anyone please guide me to build my Android in MAC environment?I am new to all these and any help will be much appreciated.

Need help for kernel Compile

I need some help of the developer to compile the kernel of the letv 1s. I tried to compile with the instruction provided on the letv 1s source code. I successfully compiled it with some warnings, although when I flash it, the phone failed to boot.
This is what I used to compile
------------------------------------------------------------------------------------------------------------------------
Le 1S Kernel Build mini-Howto
===============================
1. Build
--------
- get toolchain
From android git server, codesourcery etc.
- aarch64-linux-android-4.9
- Unpack kernel source
Suppose kernel source has been unpacked to <kernel> dir.
- make output folder
$ mkdir <kernel>/out
- export env variables
export correct "CROSS_COMPILE" to use the toolchain path you have downloaded.
$ export CROSS_COMPILE=<Your cross compilee dir>/aarch64-linux-android-4.9/bin/aarch64-linux-android-
$ export JOBS=16 # Can be CPU core # x 2
- build kernel
$ cd <kernel>
$ make -C $PWD O=$PWD/out ARCH=arm64 x500_defconfig
$ make -j$JOBS -C $PWD O=$PWD/out ARCH=arm64 KCFLAGS=-mno-android
2. Output files
---------------
- Kernel: out/arch/arm64/boot/Image
--------------------------------------------------------------------------------------------------------------------------
Expect help from @DroidThug & other developers

superac11 said:
I need some help of the developer to compile the kernel of the letv 1s. I tried to compile with the instruction provided on the letv 1s source code. I successfully compiled it with some warnings, although when I flash it, the phone failed to boot.
This is what I used to compile
------------------------------------------------------------------------------------------------------------------------
Le 1S Kernel Build mini-Howto
===============================
1. Build
--------
- get toolchain
From android git server, codesourcery etc.
- aarch64-linux-android-4.9
- Unpack kernel source
Suppose kernel source has been unpacked to <kernel> dir.
- make output folder
$ mkdir <kernel>/out
- export env variables
export correct "CROSS_COMPILE" to use the toolchain path you have downloaded.
$ export CROSS_COMPILE=<Your cross compilee dir>/aarch64-linux-android-4.9/bin/aarch64-linux-android-
$ export JOBS=16 # Can be CPU core # x 2
- build kernel
$ cd <kernel>
$ make -C $PWD O=$PWD/out ARCH=arm64 x500_defconfig
$ make -j$JOBS -C $PWD O=$PWD/out ARCH=arm64 KCFLAGS=-mno-android
2. Output files
---------------
- Kernel: out/arch/arm64/boot/Image
--------------------------------------------------------------------------------------------------------------------------
Expect help from @DroidThug & other developers
Click to expand...
Click to collapse
Hello.
Sorry for the late reply, but have Exams going on.
You can try using https://github.com/DroidThug/android_kernel_leeco_MT6795 as the source
I have fixed up stuff here and there. You may try compiling from here
Also, if you would like, you may use UBERTC from
https://github.com/DroidThug/aarch64-linux-android-gcc-4.9
You may also use the script from https://raw.githubusercontent.com/D...8bc37a9f01b6ddc77971754bdadd0e476/infernus.sh

DroidThug said:
Hello.
Sorry for the late reply, but have Exams going on.
You can try using https://github.com/DroidThug/android_kernel_leeco_MT6795 as the source
I have fixed up stuff here and there. You may try compiling from here
Also, if you would like, you may use UBERTC from
https://github.com/DroidThug/aarch64-linux-android-gcc-4.9
You may also use the script from https://raw.githubusercontent.com/D...8bc37a9f01b6ddc77971754bdadd0e476/infernus.sh
Click to expand...
Click to collapse
Thank you , Although i had already coompiled kernel and started to build the cm 13, everything gone good except brunch command,
----------------------------------------------------------------------------------------------------
[email protected]:/mnt/new/minimal$ lunch
You're building on Linux
Lunch menu... pick a combo:
1. cm_x500-eng 5. minimal_hammerhead-userdebug
2. cm_x500-user 6. minimal_mako-userdebug
3. cm_x500-userdebug 7. minimal_shamu-userdebug
4. minimal_angler-userdebug
Which would you like? [aosp_arm-eng] 1
build/core/product_config.mk:222: *** Can not locate config makefile for product "cm_x500". Stop.
WARNING: Trying to fetch a device that's already there
WARNING: device/LeTV/x500/minimal.dependencies file not found
build/core/product_config.mk:222: *** Can not locate config makefile for product "cm_x500". Stop.
** Don't have a product spec for: 'cm_x500'
** Do you have the right repo manifest?
[email protected]:/mnt/new/minimal$

superac11 said:
Thank you , Although i had already coompiled kernel and started to build the cm 13, everything gone good except brunch command,
----------------------------------------------------------------------------------------------------
[email protected]:/mnt/new/minimal$ lunch
You're building on Linux
Lunch menu... pick a combo:
1. cm_x500-eng 5. minimal_hammerhead-userdebug
2. cm_x500-user 6. minimal_mako-userdebug
3. cm_x500-userdebug 7. minimal_shamu-userdebug
4. minimal_angler-userdebug
Which would you like? [aosp_arm-eng] 1
build/core/product_config.mk:222: *** Can not locate config makefile for product "cm_x500". Stop.
WARNING: Trying to fetch a device that's already there
WARNING: device/LeTV/x500/minimal.dependencies file not found
build/core/product_config.mk:222: *** Can not locate config makefile for product "cm_x500". Stop.
** Don't have a product spec for: 'cm_x500'
** Do you have the right repo manifest?
[email protected]:/mnt/new/minimal$
Click to expand...
Click to collapse
You are building Minimal OS eh?
Minimal is based off AOSP, and the tree you use is of CyanogenMod.
You might have to edit stuff here and there