Database Info

custom kernel in otapackage

I appologize for what seems to be an elementary question, but I simply cant find an answer.
When I compile my custom android kernel under the '~/android/kernel' tree
'~/kernel/arch/arm/zImage'
How do I place this in the '~/android/system' tree and generate an 'otapackage' with my new kernel?
Up until now I have separatly booted the custom kernel using 'fastboot boot' and 'fastboot flash'
Thank you for any help and/or pointers
I am curently using the default android gingerbrread branch and the default android msm_kernel branch.

SOLVED
I copied my new zImage as ~/android/system/device/htc/passion/kernel
then re-ran make -j2 otapackage

[Q] How to compile android bootable recovery from sources?

From the title it is clear what I want to achieve so I would just get down to business here, I found the android bootable recovery sources from here [For JB] View Sources { https://android.googlesource.com/platform/bootable/recovery/+/jb-release }
There are so many file in there, and I know that to get the recovery files I need to compile the recovery.c but I think that's quit not all of it? I want to know that how should I compile this recovery, no matter how simple it is, I just want to create my own open source recovery. That's why I need to know how to compile the recovery from the sources like this.
Thanks in Advance!

How to now that i had successfully compiled rom with source

I JUST STARTED COMPILING A ROM WITH SOURCE FOR VILLE C2. I GOT MANY WARNINGS DURING THE PROCESS BUT AT THE END I DIDN'T GOT ANY ERROR. BUT WHEN I CHECK FOR ROM.ZIP IN OUT FOLDER I FOUND NOTHING. CAN ANYONE HELP ME ABOUT THIS:crying::crying:

Can not locate config file for product "full_BLU_LIFE_ONE-eng". Stop.

So I have been at my wits end the last couple days trying to figure out exactly what's going on. I have a BLU Life One 2015, (X011Q) which is unsupported on basically every custom ROM/recovery/whatever. There is no repo for it on github, (except my own, which I'm having trouble with, and is the point of this post) no released device tree (if I'm using the right word), the only source code released for it is for the kernel on Android 4.4.4.
This far, I've extracted the required files from the boot.img (I also have the recovery.img and build.prop) using a guide I found on XDA University to build CWM out of the cyanogenmod source code. (I can't post the link to this guide, unfortunately, because I'm too new a user)
Everything in that tutorial goes fine (though it might be worth noting i have to use obbtool instead of otatools) until I get to the point where I have to run "lunch full_’device_name-eng" (For me, this is: lunch full_BLU_LIFE_ONE-eng). When I do, I run into this:
Code:
build/core/product_config.mk:245: *** Can not locate config makefile for product "full_BLU_LIFE_ONE". Stop.
Device BLU_LIFE_ONE not found. Attempting to retrieve device repository from CyanogenMod Github (http //github.com/CyanogenMod).
Repository for BLU_LIFE_ONE 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:245: *** Can not locate config makefile for product "full_BLU_LIFE_ONE". Stop.
build/core/product_config.mk:245: *** Can not locate config makefile for product "full_BLU_LIFE_ONE". Stop.
** Don't have a product spec for: 'full_BLU_LIFE_ONE'
** Do you have the right repo manifest?
In case this is helpful:
From build.prop
Code:
ro.product.brand=BLU
ro.product.device=BLU_LIFE_ONE
Files that were extracted with mkvendor.sh:
Code:
AndroidBoard.mk
AndroidProducts.mk
BoardConfig.mk
cm.mk
device_BLU_LIFE_ONE.mk
kernel
recovery.fstab
system.prop
My main thought is that I'm lacking a device tree, but after searching for others, I wonder what else would be in one, and if the files I've got don't constitute some part of the device tree.
TL;DR
Do I need to create a device tree myself for a device that has no support yet whatsoever for any kind of custom ROM/Recovery? And if so, how?
Any and all help is greatly appreciated.

How do i find out board_offsets for my devices

Hi,
i am building a new kernel for my device and have issues booting it.
i guess it is related to the offsets defined in my mkbootimage description
Code:
pagesize=2048
base=0x10000000
kernel_offset=0x00008000
ramdisk_offset=0x01000000
second_offset=0x00f00000
tags_offset=0x00000100
how can i find out how the offsets changed? i mean for a normal kernel, it is fine to just reuse those values but if you build a KASAN kernel, those need to be different.
should i unpack and load the zimage and look for symbols?