Related
༼ つ ◕_◕ ༽つIn the name of our great lord Helix!༼ つ ◕_◕ ༽つ
Kerneller, a flashable Zip template for ramdisk modifications
Google what a kerneller is
Many of you have no doubt heard of osm0sis' Anykernel2 and previously koush's Anykernel. Kerneller is an alternative designed solely around Sony's Xperia lineup, taking into account the 'recovery-inside-ramdisk' situation we've found ourselves in. However, the script should also support other devices such as Nexus. (I say should because I can only test on the Xperia devices I own -- if anyone could help test, I would be very grateful!)
And with the release of Android 5.0 Lollipop, users have been facing a dilemma: To download a permissive or enforcing version of the kernel? Kerneller fixes that issue by combining the two in a single zip using a slightly modified version of keycheck, allowing the user to choose what will be installed at the time of flashing.
Source: https://github.com/someone755/kerneller
Any questions, tips, or comments are welcome!
Credits & Thanks: All authors of the included binaries. osm0sis for AnyKernel2 and porting the binaries. koush for the original AnyKernel concept. Everyone who helped test. Myself5 for the inspiration and oshmoun for the help.
XDA:DevDB Information
Kerneller, Tool/Utility for the OEM Cross Device Development
Contributors
someone755
Version Information
Status: Stable
Created 2015-12-26
Last Updated 2015-12-31
This is something, i was expecting.
Thank you very much.
Black_Eyes said:
This is something, i was expecting.
Thank you very much.
Click to expand...
Click to collapse
I'm glad you like it but I can't say that's the reaction I was expecting lol. Please do let me know if anything bothers you though.
Just by the way, I moved the thing into its own repo and added a small script to compress and sign it. Cheers!
work for lock or un lock？thank you
xsj said:
work for lock or un lock？thank you
Click to expand...
Click to collapse
I'm sorry to say I don't understand the question. This script cannot lock or unlock anything.
It modifies the boot sector of your device. For that to be possible in the first place, you need an unlocked bootloader.
thank you，Im lockbootloader now，and that's what I want to know
Sorry for noob question,but where to download?Cant find the link.Want to try this on my m2 aqua.
mariosenta said:
Sorry for noob question,but where to download?Cant find the link.Want to try this on my m2 aqua.
Click to expand...
Click to collapse
Your best bet would be using 'git clone', though you can also just download the whole repo as a zip file (here, if you're having trouble finding it). Note though that the packing script won't work in Windows unless you have a *nix shell emulator (such as Cygwin or win-bash)!
You can still zip the thing together yourself using 7zip or WinRAR, however it will not be a signed zip (so some recoveries -- like Cyanogen Recovery -- may refuse to flash it, but you could use the bash script to figure out what you have to do in Windows to sign your new zip).
If you do eventually get it to run, I'd be very glad if you could send me the recovery.log of the flash via PM!
TouchWiz?
This tool works on touchwiz Lollipop 5.1.1 Roms or not?
Stock kernel is Enforcing and I tried various methods to make it permissive, nothing works
Pavan l said:
This tool works on touchwiz Lollipop 5.1.1 Roms or not?
Stock kernel is Enforcing and I tried various methods to make it permissive, nothing works
Click to expand...
Click to collapse
I don't know if your device's boot image is assembled using mkbootimg (like Nexus devices). If so, you may be able to.
But you'll need to pack the device tree binary and zImage into the zip (just use unpackbootimg).
So, I'm very confused, I usually build boot.imgs right out of the AOSP source code... how could I leverage this?
HaoZeke said:
So, I'm very confused, I usually build boot.imgs right out of the AOSP source code... how could I leverage this?
Click to expand...
Click to collapse
It's not really meant for people who compile ROMs, but more for kernel devs or testers who only compile the kernel.
Instead of always having to extract the ramdisk from boot images (whenever the ramdisk changes, which we kernel people can't know and check for every single kernel, nor do we care) and then using mkbootimg (meaning you have to release one boot image for every ramdisk you need to support, i.e. if you want to support ROMs with vastly different ramdisk implementations, where mixing ramdisks would cause a bootloop).
With this, you go around the problem. Compile the kernel outside of the ROM tree (which takes a few minutes vs several hours that compiling the entire ROM can take), grab the zImage-dtb (or adjust the script to use zImage + dt.img), and package the thing together. (There are options to also include kernel modules in the zip, and scripts that will compress and sign the zip for you.)
The highlight of this project used to be being able to switch Selinux status when flashing the zip, instead of adding androidboot.selinux=permissive for each boot image, and then uploading two images. Nowadays compatibility of this switch with various devices and Android versions is questionable (I can't test personally because of how limited Xperia devices have become recently -- the 3.10 kernel does not work with enforcing selinux), but the core idea of using it to avoid having to create boot images is still alive and kicking.
I'm here to question the device owner. There are few sources around about this device. They are raw and they are as common always experimental. Does anyone need them?
Furthermore, I can sum up here any sources I or other get to find about this device or its periphery.
If you are eager to Void your Warranty please Mind and Acknowledge that every modification only affects you and your contract and noone else.
custom rom
http://forum.xda-developers.com/xperia-xa/development/f3112-f3116-cyanogemod-13-project-t3488890
Silversniper said:
I'm here to question the device owner. There are few sources around about this device. They are raw and they are as common always experimental. Does anyone need them?
Furthermore, I can sum up here any sources I or other get to find about this device or its periphery.
Click to expand...
Click to collapse
Very good thing, I'm trying to build a CM13 rom from sources and I'm not sure if I have all required sources. For now I have, kernel sources with some "vendor" files from Sony and I found all build parameters like offsets/adresses and correct cmdline (no thanks to Sony because never released or mentioned them), the device tree dumped from my device, and I will dump the vendor tree too.
Now I need the defconfig for CM (very not sure if the stock one will work) , and some files like the boardconfig and some config files. I'm using the Elephone P9000 sources for sample, almost the same device (hardware side) and source files.
If I have some time I will try to upload files to git but I never tried before (sync only)...
rrvuhpg said:
Very good thing, I'm trying to build a CM13 rom from sources and I'm not sure if I have all required sources. For now I have, kernel sources with some "vendor" files from Sony and I found all build parameters like offsets/adresses and correct cmdline (no thanks to Sony because never released or mentioned them), the device tree dumped from my device, and I will dump the vendor tree too.
Now I need the defconfig for CM (very not sure if the stock one will work) , and some files like the boardconfig and some config files. I'm using the Elephone P9000 sources for sample, almost the same device (hardware side) and source files.
If I have some time I will try to upload files to git but I never tried before (sync only)...
Click to expand...
Click to collapse
Don't need to hesitate. I'll try to put the directions I've gathered here up today so it is done.
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
rrvuhpg said:
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
Click to expand...
Click to collapse
cool.. if work I would like to have it on my f3111 !!
rrvuhpg said:
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
Click to expand...
Click to collapse
Can you publish some brief preview?
Need to say the sources I had just seem to be down, so can't share them.
Through which Program are these to flash? If you're that far I can hold a look at it and may join in your development.
Verification of the Vendor Files is something I was not very good at it, not even a yolk I managed.
Silversniper said:
Can you publish some brief preview?
Need to say the sources I had just seem to be down, so can't share them.
Through which Program are these to flash? If you're that far I can hold a look at it and may join in your development.
Verification of the Vendor Files is something I was not very good at it, not even a yolk I managed.
Click to expand...
Click to collapse
For now the only preview I can publish are the CM13 boot and recovery "as is", I'm not sure if it can help but I will release them if someone want to port others MTK Roms on XA. ( Never booted any ported rom with the stock kernel, stuck at Sony logo)
Flashing is easy: the recovery with fastboot and Rom/boot in a single flashable zip on the SD.
The kernel sources are coming from 33.2.B.2.95 open source archive from Sony but built from the lastest CM13 and Google git sources.
The vendor tree from 33.2.B.2.93 dumped from my phone, only common files with the P9000 are on my git for now.
The device tree from P9000 sources (from @Deepflex git) but seem OK.
CM13 have Android 6.0.1, I don't know if the security patch is the last one but August for sure.
I'm not so far from a finished build (not mean fully bootable), for now I successfully build a full CM13 for the Elephone P9000 (the twin of the XA, I'm using it as base). It mean my "kitchen" is working Now I'm trying to identify the last proprietary files from all others stock/cm13 libs, modify make files and cross my fingers it will fully build without errors.
You can join me no problem all people are welcome because I can't do all alone
rrvuhpg said:
For now the only preview I can publish are the CM13 boot and recovery "as is", I'm not sure if it can help but I will release them if someone want to port others MTK Roms on XA. ( Never booted any ported rom with the stock kernel, stuck at Sony logo)
Flashing is easy: the recovery with fastboot and Rom/boot in a single flashable zip on the SD.
The kernel sources are coming from 33.2.B.2.95 open source archive from Sony but built from the lastest CM13 and Google git sources.
The vendor tree from 33.2.B.2.93 dumped from my phone, only common files with the P9000 are on my git for now.
The device tree from P9000 sources (from @Deepflex git) but seem OK.
CM13 have Android 6.0.1, I don't know if the security patch is the last one but August for sure.
I'm not so far from a finished build (not mean fully bootable), for now I successfully build a full CM13 for the Elephone P9000 (the twin of the XA, I'm using it as base). It mean my "kitchen" is working Now I'm trying to identify the last proprietary files from all others stock/cm13 libs, modify make files and cross my fingers it will fully build without errors.
You can join me no problem all people are welcome because I can't do all alone
Click to expand...
Click to collapse
good work , but I am noob to create rom with kitchen .. only zip edit I know
Yesterday I successfully built CM13 for XA from sources
But news are not good, the CM recovery is fully working as expected but the rom is stuck just after the Sony logo (Mediatek screen with "loading...") like on my previous attempts to port other roms. The kernel built from CM kitchen do the same... I will upload my git and my rom to see if someone have an idea on the problem. Now I will focus on the "vendor" files, but I'm not sure if it's the real problem. Can it be a locked preloader/kernel or something like that?
EDIT: I think the boot problem is related to the defconfig file from Sony kernel sources, I will try to change some settings. (the door for adding kernel features :good
rrvuhpg said:
Yesterday I successfully built CM13 for XA from sources
But news are not good, the CM recovery is fully working as expected but the rom is stuck just after the Sony logo (Mediatek screen with "loading...") like on my previous attempts to port other roms. The kernel built from CM kitchen do the same... I will upload my git and my rom to see if someone have an idea on the problem. Now I will focus on the "vendor" files, but I'm not sure if it's the real problem. Can it be a locked preloader/kernel or something like that?
EDIT: I think the boot problem is related to the defconfig file from Sony kernel sources, I will try to change some settings. (the door for adding kernel features :good
Click to expand...
Click to collapse
Love you!
I will buy this phone thanks to you :highfive:
Thank you for your work on our phone, it's very cool.
I would have helped if i could develop myself. If you need help get in touch with me i know some great devs who could maybe help you
any news @rrvuhpg ?
Yes I have some news but I want to create a dedicated thread for the CM13 project with updates, explanations and downloads to avoid off topic here. I am on holiday on next week and I will have time to work on it and give explanations. For now I'm stuck on boot because of Sony extra settings in the boot process, it's the first time I see a bootstrap and TA partition mount on a MTK device. If you know a dev for helping me passing the Sony part in the boot init it can be great :angel:
Other thing, I updated my git with parts of the update made by @Deepflex on the P9000 sources and my recent changes.
rrvuhpg said:
Yes I have some news but I want to create a dedicated thread for the CM13 project with updates, explanations and downloads to avoid off topic here. I am on holiday on next week and I will have time to work on it and give explanations. For now I'm stuck on boot because of Sony extra settings in the boot process, it's the first time I see a bootstrap and TA partition mount on a MTK device. If you know a dev for helping me passing the Sony part in the boot init it can be great :angel:
Other thing, I updated my git with parts of the update made by @Deepflex on the P9000 sources and my recent changes.
Click to expand...
Click to collapse
sorry first time I use sony ... I wish you to have nice holiday !
This project is temporarily discontinued. To be resumed on Mid-June. Please use the original builds by flar2:
https://forum.xda-developers.com/oneplus-3/development/kernel-elementalx-op3-0-01-t3404879
Thanks!
Disclaimers
This project is in beta status. No warranties express or implied.
Overclocking feature is not recommended as it may cause overheating.
Always do a full TWRP backup and copy it to PC before proceeding.
NewEraElementalX for OnePlus 3 Limited Edition (The original OP3)
OxygenOS based:
0.32-9.1 for OxygenOS 3.2.8 Marshmallow
2.07-1 for OxygenOS 4.0.3 Nougat 7.0
3.00-1 for OxygenOS 4.1.0 Nougat 7.1
CyanogenMod/LineageOS based:
0.39-cm-9.1 for CyanogenMod 13.0 Marshmallow
1.04-los-2 for CyanogenMod 14.1 Nougat
1.05-los-3 for LineageOS 14.1 Nougat (API 3.18.47)
2.09-los-1 for LineageOS 14.1 Nougat (API 3.18.31)
[Feb 10 and earlier] Built with gcc-linaro-5.3.1-2016.05 toolchain.
[Feb 14 and later] Built with gcc-linaro-5.4.1-2017.01 toolchain.
NewEraElementalX is based on the award winning ElementalX kernel by flar2. Big shouts for his hard work.
It is designed for maximum stability, security and performance. It is made for people who depend on their phone every day.
Release Notes
For maximum compatibility with all ROMs, NewEraElementalX uses your existing ramdisk. Do NOT flash this over other custom kernels! You should only flash over the kernel that came with your ROM!
Going back to stock: This kernel installer modifies your filesystem (changes modules). You can backup your boot.img and system.img with TWRP before flashing if you want to go back.
Xposed Framework and ROMs in Beta/Preview status are not officially supported.
If you are using CyanogenMod/LineageOS and F2FS be very careful. This kernel includes the latest fixes proposed by arter97. Read more at:
forum.xda-developers.com/showpost.php?p=70492947&postcount=8793
Features
Easy installation and setup with Aroma installer
Wake Gestures support (sweep2wake & doubletap2wake)
Notification LED control
Sound control
Advanced color control
Sweep2sleep
Backlight dimmer
Overclock or underclock CPU
Adjust or disable vibration
FIOPS, BFQ, CFQ, deadline, noop and SIO i/o schedulers
NTFS r/w support
Option to disable fsync
Performance and power optimizations
USB OTG support
Dash charge
Supports MultiROM
Does not force encryption
Compatible with systemless root
Extras
Extensive build fixes
Battery usage improvements
Performance enhancements
Security fixes for upstream advisories
Miscellaneous edits
Installation
Install or Sideload flashable zip via TWRP recovery.
Note: Always reboot TWRP after flashing full ROM/OTA, before flashing custom kernel.
Rooting
I have tested SuperSU and Magisk. Here is how I recommend doing it:
SuperSU: Flash SuperSU first and then custom kernel.
Magisk: Flash custom kernel and then Magisk.
Report Bugs
github.com/VPSrv/android_kernel_oneplus_msm8996/issues
[Feb 09 NewEraElementalX-OP3-0.32-9.1] OxygenOS 3.2.8 Marshmallow Based ROMs (Linux 3.18.20 + WiFi Module)
Flashable zip: mega.nz/#!4oAhnYQC!_daLwYe8FYpIcrdGSAU62-g5KTaZHZMmrJ0R01UeJXM
Link decyption key (if it asks): !_daLwYe8FYpIcrdGSAU62-g5KTaZHZMmrJ0R01UeJXM
Flashable zip md5: 7758e3c003670866a44efa29bd144777
Sources: github.com/VPSrv/android_kernel_oneplus_msm8996/tree/newera/ElementalX
[Mar 13 NewEraElementalX-OP3-2.07-1] OxygenOS 4.0.3 Nougat Based ROMs (Linux 3.18.31 + WiFi Module)
Flashable zip: mega.nz/#!d85lzIJY!pzLSR2SSyijpWHPVaxcWnXnfMqdv01VikoVWUAC9CI4
Link decyption key (if it asks): !pzLSR2SSyijpWHPVaxcWnXnfMqdv01VikoVWUAC9CI4
Flashable zip md5: 020b0f44cd1a4bf70d1289fc9c0c7519
Sources: github.com/VPSrv/android_kernel_oneplus_msm8996/tree/newera/ElementalX-2.00
[Mar 23 NewEraElementalX-OP3-3.00-1] OxygenOS 4.1.0 Nougat Based ROMs (Linux 3.18.31 + WiFi Module)
Flashable zip: mega.nz/#!04oEnIZI!ta22oN_82LPx5eU0QDY9QO4cN0O9UO11dXuu9DZmSx4
Link decyption key (if it asks): !ta22oN_82LPx5eU0QDY9QO4cN0O9UO11dXuu9DZmSx4
Flashable zip md5: 4654cc028b2cbfd31e2d179295eb8ddb
Sources: github.com/VPSrv/android_kernel_oneplus_msm8996/tree/newera/ElementalX-3.00
[Feb 09 NewEraElementalX-OP3-0.39-cm-9.1] CyanogenMod 13.0 Based ROMs (Linux 3.18.44 + WiFi Built-in)
Flashable zip: mega.nz/#!IgRV0RYZ!stXasRuRMZkbBRIkoIIiLEGYDb4zQM78UuIDOETNFLI
Link decyption key (if it asks): !stXasRuRMZkbBRIkoIIiLEGYDb4zQM78UuIDOETNFLI
Flashable zip md5: 0e96caabb754cf52a4fc1f4abfddb647
Sources: github.com/VPSrv/android_kernel_oneplus_msm8996/tree/newera/ElementalX-CM
[Feb 02 NewEraElementalX-OP3-1.04-los-2] CyanogenMod 14.1 Based ROMs (Linux 3.18.47 + WiFi Module)
Flashable zip: mega.nz/#!UhhyGbAa!sL5pgMa_DSAMhWnSQE4yN-QjD13hsIXWCNnyycO7uvk
Link decyption key (if it asks): !sL5pgMa_DSAMhWnSQE4yN-QjD13hsIXWCNnyycO7uvk
Flashable zip md5: df5cc7ecd9c9aeb28b9a41057c71ae40
Sources: github.com/VPSrv/android_kernel_oneplus_msm8996/tree/newera/ElementalX-CM14.1
[Mar 03 NewEraElementalX-OP3-1.05-los-3] LineageOS 13.0 And Old 14.1 Based ROMs (Linux 3.18.47 + WiFi Built-in)
Flashable zip: mega.nz/#!p85BwaSD!GrN8B8-zLntmnLd3nhm5v8QSVO1OUnO11cKRv0ApFw0
Link decyption key (if it asks): !GrN8B8-zLntmnLd3nhm5v8QSVO1OUnO11cKRv0ApFw0
Flashable zip md5: eeeef84393cf1ee16e4829f25898854d
Sources: github.com/VPSrv/android_kernel_oneplus_msm8996/tree/newera/ElementalX-LOS
[Mar 13 NewEraElementalX-OP3-2.08-los-1] LineageOS 14.1 Based ROMs (Linux 3.18.31 + WiFi Built-in)
Flashable zip: mega.nz/#!E0BGBCwC!QQuE2ZtkRnVdsv4O3uIBLMNZjhDncN5PGkagl_GQPTI
Link decyption key (if it asks): !QQuE2ZtkRnVdsv4O3uIBLMNZjhDncN5PGkagl_GQPTI
Flashable zip md5: 64945aad24a90d978fdca7dae3622517
Sources: github.com/VPSrv/android_kernel_oneplus_msm8996/tree/NewEraElementalX-OP3-2.08-los-1
[Mar 29 NewEraElementalX-OP3-2.09-los-1] LineageOS 14.1 Based ROMs (Linux 3.18.31 + WiFi Built-in)
Flashable zip: mega.nz/#!19gCVazZ!1aBw5KWG3Kcx9VaBbtCNCVNXN7olQ28HZZEJXgyNMpA
Link decyption key (if it asks): !1aBw5KWG3Kcx9VaBbtCNCVNXN7olQ28HZZEJXgyNMpA
Flashable zip md5: 520cd4ce116574cb31d309dde2386f36
Sources: github.com/VPSrv/android_kernel_oneplus_msm8996/tree/newera/ElementalX-2.00-LOS
Previous versions (Use at your own risk!)
Flashable zips: mega.nz/#F!p0hU3K5L!M6ISSY53TaHOmTuJgXq_tA
Link decyption key (if it asks): !M6ISSY53TaHOmTuJgXq_tA
Sources: github.com/VPSrv/android_kernel_oneplus_msm8996/releases
Manual Build From Source
Code:
export ARCH=arm64
export SUBARCH=arm64
export CROSS_COMPILE=/home/newera/gcc-linaro-5.4.1-2017.01-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu-
make elementalx_defconfig
make -j5 &>../elementalx.log
You need to use your own CROSS_COMPILE path. I leave the remaining steps at discretion of the reader.
Credits & Original Sources
flar2/ElementalX
eng.stk/blu_spark
franciscofranco/franco.Kernel
Lord Boeffla/Boeffla-Kernel
RenderBroken/Render Kernel
OnePlusOSS/oneplus3
LineageOS/cm-14.1
Disclaimer to moderators:
Slight off-topic is fine, but when users decide to act stupid they should be dealt with with the appropriate means - its really annoying for me when off-topic turns crazy. Please put the warning/ban hammer anytime any of you think there's lack of respect and/or too much unwanted off-topic - but if it doesn't meet this criteria let the off-topic posts alone. Thank you.
First post in! Great to see you on here Jorge!
The longest journeys begin with the first step.....well done Jorge.
If a Mod sees this, please move to ROMs, kernels, and recoveries section. Nice work Jorge!
kyledowling said:
If a Mod sees this, please move to ROMs, kernels, and recoveries section. Nice work Jorge!
Click to expand...
Click to collapse
+1
Kinda sad cause I'm currently on f2fs and using xposed but I will follow up on this thread, looks promising
Chabola said:
+1
Kinda sad cause I'm currently on f2fs and using xposed but I will follow up on this thread, looks promising
Click to expand...
Click to collapse
The problem with F2FS is that after upgrading to a kernel shipping a newer version, you can't go back to your earlier kernel without risking data corruption and kernel panics. After you confirm with the ROM developer that F2FS fix is applied, this kernel should work safely and perform correctly as expected.
Xposed might work. I just don't want to be bothered if there are any bugs caused by it.
Thanks!
Released an update of my CM 14.1 kernel. It's updated to the latest LineageOS tree including merge with Linux Kernel version 3.18.46.
Shortly tested on cm-14.1-20161225-NIGHTLY-oneplus3 and working.
JorgeManuelSilva91 said:
The problem with F2FS is that after upgrading to a kernel shipping a newer version, you can't go back to your earlier kernel without risking data corruption and kernel panics. After you confirm with the ROM developer that F2FS fix is applied, this kernel should work safely and perform correctly as expected.
Xposed might work. I just don't want to be bothered if there are any bugs caused by it.
Thanks!
Click to expand...
Click to collapse
I'm on the lastest marshmallow oxygen os yeah thanks for explaining
The F2FS problem is only specific to CyanogenMod/LineageOS (All ROM releases built after January 11th should have the fix on them).
OxygenOS has always been okay in that area. OnePlus never released the sources of the Community Open Betas so I don't officially support that either. I am also waiting for Nougat sources to see if I can work something out.
Thanks for the updated cm 13 build of the kernel. Batterylife seems really a little bit better with your build.
Released an update of my CM 14.1 kernel. It's updated to the latest LineageOS tree including merge with Linux Kernel version 3.18.47 and flar2's ElementalX-1.04-los
Shortly tested on cm-14.1-20161225-NIGHTLY-oneplus3 and working.
I have released NewEraElementalX-OP3-1.05-los-1, it is based on ElementalX-OP3-1.05-los, the big change in this version is that WiFi module is now static. This kernel is no longer compatible with CyanogenMod 14.1 and is only compatible with LineageOS builds after January 22.
For older CyanogenMod/LineageOS 14.1 builds you should use NewEraElementalX-OP3-1.04-los-1 released on January 20.
This new build also works on the oldish CyanogenMod 13 MM because the kernel API is very similar and I have done some testing there. This configuration is not officially supported.
Just a question: would be possible build this kernel with another toolchain release?( I'm referring especially to the one that zanezam use to build his unofficial boeffla kernel )
That's just an idea to further improve the performnce of the kernel
It's possible. But I have previously tested with GCC Linaro 6.2.1 and I haven't seen that much performance change. In fact I had lower points when running PassMark PerformanceTest on GCC Linaro 6.2.1 built kernel vs GCC Linaro 5.3.1.
JorgeManuelSilva91 said:
It's possible. But I have previously tested with GCC Linaro 6.2.1 and I haven't seen that much performance change. In fact I had lower points when running PassMark PerformanceTest on GCC Linaro 6.2.1 built kernel vs GCC Linaro 5.3.1.
Click to expand...
Click to collapse
Did you tried to use some uber toolchain or blu_naro 6.3 from eng.stk?
After testing, a build of NewEraElementalX for OxygenOS 4.0.2 Nougat has been released. This is based on ElementalX 2.01 and is an unofficial fork (as all the other builds). When using this builds please report any bugs on GitHub link I posted on original post.
Be aware that OxygenOS Nougat is recent and the release schedule by OnePlus was a little bit rushed to meet deadlines. So, as always, keep a backup in your computer of the previous installation in case you want to go back.
android extreme said:
Did you tried to use some uber toolchain or blu_naro 6.3 from eng.stk?
Click to expand...
Click to collapse
I may research into that in the future. It is not a priority yet as GCC 5.3.1 Linaro delivers the things I need.
JorgeManuelSilva91 said:
I may research into that in the future. It is not a priority yet as GCC 5.3.1 Linaro delivers the things I need.
Click to expand...
Click to collapse
No problem dev as i said mine was just a question and thank you for having dedicated to me some time to answer to my question
Massive rebuild today! All 5 branches have been updated. There is a new addition based on flar2's ElementalX-2.00-LOS for the most recent LineageOS ROMs with O2OS Nougat backports (Kernel API 3.18.31).
NewEraElementalX-OP3-0.32-9, NewEraElementalX-OP3-0.39-cm-9, NewEraElementalX-OP3-1.04-los-2, NewEraElementalX-OP3-1.05-los-2 and NewEraElementalX-OP3-2.01-2, include minor fixes compared with the previous builds. The GitHub repository is heavily tagged so you can check all changes by yourself:
android_kernel_oneplus_msm8996/compare/NewEraElementalX-OP3-0.32-8...NewEraElementalX-OP3-0.32-9
android_kernel_oneplus_msm8996/compare/NewEraElementalX-OP3-0.39-cm-8...NewEraElementalX-OP3-0.39-cm-9
android_kernel_oneplus_msm8996/compare/NewEraElementalX-OP3-1.04-los-1...NewEraElementalX-OP3-1.04-los-2
android_kernel_oneplus_msm8996/compare/NewEraElementalX-OP3-1.05-los-1...NewEraElementalX-OP3-1.05-los-2
android_kernel_oneplus_msm8996/compare/NewEraElementalX-OP3-2.01-1...NewEraElementalX-OP3-2.01-2
You can also use this GitHub feature to compare the changes on my modded builds vs the original:
android_kernel_oneplus_msm8996/compare/ElementalX-OP3-2.00-los...NewEraElementalX-OP3-2.00-los-1
I have not tested any of the new builds (except the one for O2OS Marshmallow that I am on at the moment) but I am confident they will work fine and you will benefit from the latest updates.
This new builds also mark the end of support for 0.x (Marshmallow) and 1.x (Previous Nougat) and I will not do any rebuilding/updates from now on those branches. The only supported and actively updated series will be 2.x (New Nougat).
UPDATE: All builds have been tested on their respective ROMs. Confirmed working.
Can you make for 3t too please?
Schrotty35 said:
Can you make for 3t too please?
Click to expand...
Click to collapse
Unfortunately, I don't have a 3T device for testing. I know it is relatively similar with the original OnePlus 3 albeit CPU frequencies and battery capacity differ.
The installer of NewEraElementalX-OP3-1.05-los-2 (for LineageOS 14.1 Old), NewEraElementalX-OP3-2.00-los-1 (for LineageOS 14.1 New) and NewEraElementalX-OP3-2.01-2 (for OxygenOS 4.0.2) contains code to allow installation on a 3T and the kernel also contains the device descriptors so it may work.
But... I don't want to give certainty as it might render the ROM not bootable. If that happens, boot recovery and restore a TWRP backup of boot.img and system.img (if you enable wifi module replacement).
Good luck and proceed at your own risk! Report back if you can too. I'd like to know if it works. I am open to any questions you may have.
I am new in kernel developing and i started learning development by compiling kernel from source for samsung j3 pro (2016). I downloaded its kernel source (J320F / LL swa INS ) from samsung opensource site And gcc toolchain arm-eabi 4.8.
I followed available guide on net step by step for compiling and i its successfully compiled without an error and my zimage is created but when i flashed this kernel i got bootloops.
ANY SUGGESTIONS IS GREATLY APPRECIATED
i getting error on making modules too. I searching fix each error.
I enabled module in menconfig but failed to make
I have also compiled kernel available on github for j320fn with variant-defconfig for j320f but same result.
Any one have knowledge about this please instruct me
I am trying to build the latest OOS 13 kernel .
The source I am working with is https://github.com/OnePlusOSS/android_kernel_oneplus_sm8250/tree/oneplus/sm8250_t_13.0.0_op8
In the past , i've built for Samsung and Lenovo devices , although I am unsure of a few things with our oneplus8t
Which defconfig file should I be using? as I do not see a kebab config within the root directory of android_kernel_oneplus_sm8250 or arch/arm64/configs/
Google has helped , but not too much material on building OOS kernels
What is the difference between a OOS kernel and AOSP kernel ? Would I be able to take a commit from AOSP and apply to my OOS ?
Appreciate any insight , and hope to be able to release a kernel soon!
SOLUTION
Backed up my boot.img with ex-kernel manager . Brought the boot.img to my build folder. Extracted defconfig with extract-ikconfig
Hey Dude I'm on oos11..i wanna compile a new kernel..which debconf to use.. the one in the vendors or what? Kona-perf.debconf?
Please help me which debconf to use for OnePlus 8
@hightech316 any luck on building the custom kernel yet?