Hey guys,
I just started compiling the first rom from source, and everything went great, but I have a question. I want to build it now but pointing to a custom kernel. In the ROM , I created the local_manifest but I dont know how to make it point to the custom Kernel (Specifically UBER-L) in order to build successfully. I cloned the repository onto my source directory but now I am stuck. Any help would be great
Related
Hey guys, I want to install a custom kernel, razrqcom-dev-team kernel, on my XT925 - Carbon ROM(0614) but I dont find any information about how to procede.
I downloaded the repository android_kernel_motorola_msm8960-common(razrqcom-dev-team). Someone has a good instruction or know a good tutorial to share?
My apologies about my poor english
Cheers,
Just to clarify: Are you looking for the pre-compiled kernel or do you want to learn how to build android from source?
If you only want a precompiled kernel, then you shouldn't worry, as the right one is already built in line with the rom you chose.
Hello,
I recently downloaded the official AOSP source code into my machine and I want to compile it for my GT-I9300,
but before that where do I get the device blobs and properitary drivers from? Can I use CM's device tree? Are there any other device trees?
And in an addition to that how do I get the Kernel to work properly? Do I need to use the CM kernel?
A hint / tip or a link to a guide would be appreciated.
Thanks in advance
I can suggest you to go to xda university
I'm sure that you will find all you need for cooking your own build
Good luck
Hello there,
I am currently having a One Plus One. I have multi-rom utlity which allows me to have multiple android OS installed.
Currently the cyanogenmod based custom Marshmallow Rom I use (http://forum.xda-developers.com/one...m-kernel-unofficial-cyanogenmod-13-0-t3242700) has switched over to using stable CM branch as their rom base. So this requires using Super SU for root access. Unfortunately Super Su is not compatible with Multirom implementation for OPO.
One suggestion provided was to try building the custom rom from source with user-debug flag. Meanwhile I came across two build.prop values (ro.build.type=userdebug ; persist.sys.root_access=1) which I hoped would enable inbuilt superuser without rebuilding the rom from source but they did not work.
So for now, there seems to be no other way around building from source ( I wanted to avoid this as much as possible because I have a very slow Internet access downloading 30 GB or so for the ROM alone will take a month for me).
So here are my 2 questions:
1> The rom developer in the thread mentioned in 2nd para, talks about 2 source (Kernel and the rest). When I looked at the manifest, they talk about replacing something. So does this mean I need to download the cyanogenmod sources as well or does repo sync take care of that automatically ?
2> I assume the kernel and rom need to be built separately. Can the "userdebug" mode be enabled only by rebuilding the kernel and then placing it with rest of the rom build zip provided by the developer to avoid rebuilding the whole rom ? or better yet flash the my userdebug kernel again after the normal rom installation ?
Thanks In Advance
crazydude10 said:
Hello there,
I am currently having a One Plus One. I have multi-rom utlity which allows me to have multiple android OS installed.
Currently the cyanogenmod based custom Marshmallow Rom I use (http://forum.xda-developers.com/one...m-kernel-unofficial-cyanogenmod-13-0-t3242700) has switched over to using stable CM branch as their rom base. So this requires using Super SU for root access. Unfortunately Super Su is not compatible with Multirom implementation for OPO.
One suggestion provided was to try building the custom rom from source with user-debug flag. Meanwhile I came across two build.prop values (ro.build.type=userdebug ; persist.sys.root_access=1) which I hoped would enable inbuilt superuser without rebuilding the rom from source but they did not work.
So for now, there seems to be no other way around building from source ( I wanted to avoid this as much as possible because I have a very slow Internet access downloading 30 GB or so for the ROM alone will take a month for me).
So here are my 2 questions:
1> The rom developer in the thread mentioned in 2nd para, talks about 2 source (Kernel and the rest). When I looked at the manifest, they talk about replacing something. So does this mean I need to download the cyanogenmod sources as well or does repo sync take care of that automatically ?
2> I assume the kernel and rom need to be built separately. Can the "userdebug" mode be enabled only by rebuilding the kernel and then placing it with rest of the rom build zip provided by the developer to avoid rebuilding the whole rom ? or better yet flash the my userdebug kernel again after the normal rom installation ?
Thanks In Advance
Click to expand...
Click to collapse
Greetings,
Please read the Sticky threads for XDA Assist. This is not a help desk. XDA Assist is for helping new members or visitors navigate this site. You are a Senior Member and therefore you should know how to use the search feature and find the correct thread to ask your questions.
Thanks for understanding.
Thread closed.
Hello All,
I am new in the android world, but am fairly experienced on the Linux side of things. I would like to build a loadable kernel module for a specific version of JB (4.2.2_r1) and have some general questions.
As I understand it, the process should be as follows:
Get kernel source for JB, compile kernel, then compile kernel module. Please correct me if I am wrong
I can't seem to find the kernel source for this, can anyone point me to exactly where it is?
Thanks
Hi guys,
I want to present my port of M-Kernel, which was originally made by Metallice. This port has exactly the same functionality as the latest release from Metallice (a77), but was ported from Android 5.1 to Android 6.0.
Since this is a testing build only, it is currently provided as zImage only. You have to manually concatenate my kernel with the ramdisk of the ROM of your choice to be able to flash and use my kernel. For concatenating, you can use mkbootimg (click here), which is provided in my Github account.
You can get the source code and the kernel binary from Github (click here).
WARNING!!! This software is provided without any warranty. You use it at your own risk, although it is very unlikely for your device to get damaged due to my kernel.
I hope you enjoy my kernel! Feel free to ask questions about it, but please read the original M-Kernel thread before!
Best regards,
Oebbler
Thank you so much!
Something I didn't have the time or the skills to do!
I created an anykernel script for myself.
here
Hello,
If you are using Omnirom 6.0.1 by daniel_hk, you can flash the attached boot.img either with fastboot or with the TWRP image flasher. This boot.img contains my port of M-Kernel and the ramdisk files for Omnirom 6.0.1.
If you are not using Omnirom 6.0.1, you can try this image as well, but it may not work as expected. Please make sure you have a recent backup before modifying your device!