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!
Related
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
Hey,
i'm just curious about what the title describes. First of all.
What do i really need:
-kernel sources
-binary blobs (extractable)
-recovery / boot.img (extractable)
Let us just talk about the fairphone 2. Additional to the things mentioned we get the full source code of the OS (which i do not need?).
Where do the difficulties lie? For my understanding we just take the kernel sources, the official cyanogenmod (e.g.) source code, the binary blobs and the recovery / boot.img.
How difficult would it be to port Cyanogenmod to the fairphone 2.
Why is it difficult to port a device with existing (again cyanogenmod just as an example) cyanogenmod to a newer Cyanogenmod (Android) version?
I ask this to estimate/evaluate/judge (don't know the right term) the effort needed to do this. I think i'd be able to do that if i put enough work into it (i "speak" c and java), but i just need some answers.
Especially for example why it is more difficult to port Android 6 instead of Android 5 (which is the currently running Android version)
Thanks!
bigCrash
Has nobody an answer? Just one?
Im specifically interested in why it is more difficult to port e.g. cyanogenmod if there is only an older version of stock android and how important the kernel is? Why do we need kernel sources? Can't one just self-compile a kernel.
Where are the limits if i have a device running 4.2. Why can it possibly run 5.1 but not 6? Is the kernel limiting? Or only the effort to realize such a thing.
Thanks!
bigCrash
Hello everybody. I've made XenonHD 6.0 from sources: TeamHorizon, but I'm unfortunately facing issues while booting up. That I can't get past boot animation! ROM was built just fine.Here's the device tree I've used: My device sources branch 6.0, you will find other dependencies in xenonhd.dependencies, same sources work with other ROMs tho. Dunno what's the issue here. I've also made a logcat for the error. (It is too big to be uploaded to pastebin or hastebin, sorry). Someone please help me out!
Thanks.
P.S. It is bootlooping just like lots of other ROMs bootloop, i.e. DARKOBAS, SULTANXDA's, AOSPARADOX. My system is PVS8, updated to CM13 modem. Using TWRP3 (with Firmware backup and restore support)
Looking forward for some good support
Regards
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.
I have an One s with S3 processer(villeC2).
Its specs are similar to sensation(with same cpu and screen resolution),but sensation has Android 7.1 ROM and one s only 4.4......
I would like to port a ROM for it from sensation.
Does anyone know how to do that?
Or if it is possible ?
(sorry for my bad english)
(my first post)
Some info !
Hi,
Actually I'm new in building roms and kernels, too. But i can share some info with you.
For starting this tutorial may be helpful: [Guide] Compile 4.2 & 4.3 & 4.4 Roms for villec2
As you can see, you will need "device", "vendor" and "kernel" source to build a rom.
Usually you can find source code of roms and kernels in xda threads and can start from those.
For example for Android 7.1 you can use RROS vendor and VilleC2 device and kernel sources. (Note: i don't know are these examples compatible or not?!)
And for kernel, maybe you has to upstream the kernel source to be compatible with new version of android that you want to build.
Good luck.
-----------------------------------
Edit:
After Compiling for myself, i figured out Vendor files for choosed rom (Lineage, RR, ..) will be included by their manifest files automatically. so for "Vendor" part in "local_manifest.xml" (or newer "local_manifests/roomservice.xml") we need to assign "proprietary_vendor" files related to our devices. "proprietary_vendor" files can be extracted manully if there isn't any online source.
one more useful guide: [GUIDE]Building any ROM from source for HTC One S aka ville!