Related
Hello together,
I hope someone maybe can help me out. In the past I comiled the standard CM11 kernel by myself. I just add a few minor tweaks for my display color calibration and so on. Nothing special.
Since CM11 I'm always stuck in a bootloop after the "Google" logo. Even if I try only the stock CM11 kernel without any changes. Same toolchain (4.7) and so on. Why is that the case?!
I hope someone, maybe from all the experiencened kernel creators here, can give me a hint where's my problem? Is it maybe something with all the SELinux stuff? It was also the case in CM10.2 if I tried to comile with modules enabled.
Help here would be very appreciated. Thanks in advance.
Regards, Fred
OK, I answer this question myself. Just found out you have to compile the kernel inline with cyanogenmod. Sync the whole repo, initialize your device, make the changes to the kernel and compile it with make bootimage. This way I also have no need to use Anykernel script anymore.
༼ つ ◕_◕ ༽つ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.
[size=+2]This ROM is no longer updated as I don't have the device anymore. Feel free to use my code from GitHub to compile newer versions.[/size]
I have created this ROM for my E210L and I would like to share it here. This is direct port of Cyanogenmod/LineageOS from i9300 to E210L/S/K.
My ROM is based on work from FullGreen: https://github.com/FullGreen and on weeks of original research.
Previous versions of my ROM was direct ports of FullGreen ROM to E210L, later version was ported from scratch from CM13 stable release ZNH5Y sources for i9300, and still had many things based on FullGreen work.
The new version is based on latest source of LineageOS for GT-I9300.
[size=+3]ROM Download[/size]
https://www.androidfilehost.com/?w=files&flid=146865 - updated at 2018-10-02.
Older releases:
https://mega.nz/#F!28xyAJTY!gQ5dsDWIz3ydJkhyHEZ1fQ
[size=+3]Flashing[/size]
It is always recommended to upgrade to latest official stock ROM before switching to LineageOS. This is because latest stock ROM includes updated modem and bootloader.
To flash the ROM, use TWRP - for E210L it is available together with the ROM. For E210S and E210K, use TWRP for I9300 from http://twrp.me.
GApps can be downloaded from http://opengapps.org/ , architecture ARM, version 7.1, variant nano.
Boeffla kernel - optional - is also available with the ROM, it can be installed from recovery if you wan't to use it.
[size=+3]WARNING!!![/size]
PLEASE BACK UP EFS BEFORE FLASHING!!! Tweaking this phone can cause EFS wipe in some cases, and you must have a backup to restore it to normal.
[size=+3]Known bugs:[/size]
- Signal strength sometimes will be shown empty, this is only cosmetic issue (but too difficult for me to fix) and don't affect real signal strength.
- As my ROM is based on official LineageOS sources, and for now there is no stable release of LineageOS, if there are bugs in official LineageOS for i9300, they will be probably present also in my ROM.
- Cell broadcasts are disabled as they seem to cause battery drain.
Please note that for most of the cases I cannot solve bugs as I'm not LineageOS developer, I'm only doing a direct port from I9300 to E210.
[size=+3]Troubleshooting[/size]
If having issues with WIFI or IMEI:
Enable developer options and ADB root access, then connect phone to computer and enter in adb shell:
Code:
su
restorecon -R -F /efs
reboot
You have to do this from normal LineageOS, NOT from recovery or from stock/another ROM.
If you restore EFS from backup or go to another ROM and return to this ROM and you have problems, do this again.
There is no harm in doing this if not sure.
If your WIFI still not working, read this:
WIFI module in Galaxy S3 can be of three different types - murata, semco and semcosh. Normally the driver should be able to detect the right type by MAC address, but in LineageOS detection not always works correctly. Theoretically this can be a problem also for the regular model GT-I9300, but it seems to affect mainly the SHV-E210 model. To overcome this, I have made an option to manually override your WIFI module type. To do this, you have to update to my latest version of the ROM and then create an empty file named wifi_override_murata or wifi_override_semco or wifi_override_semcosh in your /data partition.
To do this, enable developer options, then turn on root access for ADB, then connect phone to computer, enter adb shell and execute :
Code:
su
For murata :
rm /data/wifi_override_semco
rm /data/wifi_override_semcosh
touch /data/wifi_override_murata
For semco :
rm /data/wifi_override_semcosh
rm /data/wifi_override_murata
touch /data/wifi_override_semco
For semcosh :
rm /data/wifi_override_murata
rm /data/wifi_override_semco
touch /data/wifi_override_semcosh
Then reboot the phone and try again using WIFI. You have try each of the three options to determine which option is right for your device. And if you hard reset your device, you will have to do this again.
In voice call, if the other person hears an echo of himself try to change AudioFX settings or disable AudioFX in the app.
[size=+3]Source code:[/size]
https://github.com/kmmng/cm14_c1
[size=+3]Thanks to:[/size]
The G-O-D for everything! ,
CyanogenMOD and LineageOS teams for the OS,
FullGreen for the ROM and the kernel,
TWRP for custom recovery,
osm0sis for Android Image Kitchen,
xpirt for sdat2img and rimg2sdat,
Lord Boeffla for his kernel and Anykernel scripts,
and everyone else I have used their work.
Runs great so far!
Nice job on making this work on this device, a fix for the battery drain issue would be perfect. I sadly do not have knowledge of this else i would be able to assist. Keep it up!
Perfect!!
Good job, the battery drain is high but the rom is fantastic, thanks for this
uhmm Where to get the Shv e210k version of this rom all i see is for L and S plss help
Nigellross said:
uhmm Where to get the Shv e210k version of this rom all i see is for L and S plss help
Click to expand...
Click to collapse
Try to use e210s version, s and k models are very similar.
Ve tried to use the s version on my shv e210k but im stuck at samsung galaxy logo ... is therw any fix
HUDASnotcare said:
Ve tried to use the s version on my shv e210k but im stuck at samsung galaxy logo ... is therw any fix
Click to expand...
Click to collapse
Try to flash this kernel after flashing S version. I cannot test it as I don't have the device, but I hope it will work.
No wifi
kmmng said:
Try to flash this kernel after flashing S version. I cannot test it as I don't have the device, but I hope it will work.
Click to expand...
Click to collapse
Its working thanks but now Unable to connect o my wifi help
HUDASnotcare said:
Its working thanks but now Unable to connect o my wifi help
Click to expand...
Click to collapse
Try this, I don't sure this will work as I don't have this device so i don't sure which wifi module it have.
GApps
Thanks men it works but i cannot install any gapps and getting an error google play frameworks not stopped
---------- Post added at 10:26 PM ---------- Previous post was at 10:25 PM ----------
kmmng said:
Try this, I don't sure this will work as I don't have this device so i don't sure which wifi module it have.
Click to expand...
Click to collapse
Thanks it work great but now experiencing gapps not working need help... also notifs led is not working ... sorry for the trouble
HUDASnotcare said:
Thanks it work great but now experiencing gapps not working need help... also notifs led is not working ... sorry for the trouble
Click to expand...
Click to collapse
Try to use E210S version from 2016-03-16 and not the last one.
Also try to install in this order : first erase data from recovery, then install rom, then install gapps, then install kernel - all this without rebooting. Only when everything is installed you can reboot.
Mine problem is losing signal after typing long message pls help guys, im using e210l and Boeffla kernel. thanks.
ROM updated to new version, https://mega.nz/#!6kJWFYSD!vDn3YI5-bgHOIsQvrblLaIRPrK5YEtQ3xlDSbApCdUI
Thank you soo much for this rom
đa
update plz
meeeeeooo said:
Mine problem is losing signal after typing long message pls help guys, im using e210l and Boeffla kernel. thanks.
Click to expand...
Click to collapse
same here, but i tested many roms 6.0, imo bug after port
shv e210k
wifi connection failure
Updated to new version
Thanks for the ROM, but the boeffla kernel in this versión Don't work, is stuck in cyanogen logo.
My device is SHV E210L
Rom : Blekota Note 4 Lite Rom 4.4.4
How to flash this rom?
I rooted my c9 pro
now i can't use Secure Folder ! (i know why!)
so yesterday I edited build.prop file and changed (ro.config.tima) to 0 .
after edit S health work good but secure folder still give knox error.
in my s7 edge i flashed superstuck kernel and solve the problem!
Anyone have superstuck kernel for c9 pro (c9000) ?
sorry for my bad english /
yes i want the same idea. please any builder built kernel i am ready for donate
find me the patches and i will see if they work in our kernel. Also they use an older version of secure folder to make it work.
travis82 said:
find me the patches and i will see if they work in our kernel. Also they use an older version of secure folder to make it work.
Click to expand...
Click to collapse
If you let us know when you're done, we are rewarded. It does not matter if it's an older version, just try it. Thanks
travis82 said:
find me the patches and i will see if they work in our kernel. Also they use an older version of secure folder to make it work.
Click to expand...
Click to collapse
I guess superstuck kernel give fake information about knox to applications.
Also you can use superstuck kernel to know how it work or ask developer of this kernel about this kernel
This kernel source:
https://github.com/GrifoDev/SuperKernel/tree/TW70-stock
Unfortunately I have no much information about kernel
Thank you
Those patches are in ramdisk and do not work on our Qualcomm last time I checked. It was working on exynos tho. Find me on Telegram and I will make you a kernel with that shell script they use to reset props and you can help me figure it out.
Hi all,
I like to try tweaking and hacking my phone. I've tried some ROMs on my kugo for some time, but I figured I wanted to make my own personalized build. Right now, I'd like to use the 'Night Light' app from F-Droid, which requires KCAL support. In order to enable KCAL I'd need to edit the stock kernel (I know this can be done, it was the case for Genesis Kernel on Nougat).
Hence I'd want to learn to compile a kernel, but I can't get to the end of Sony's tutorial. I've downloaded the kernel source but I am totally lost with defconfig files. How should I configure the kernel ? There is no obvious choice for a defconfig, and I can't get past point #6 in the tutorial..
Given that I've just discovered kernel compilation today, would someone be kind and take some time to maybe point me to useful doc, give me a clue as to what my next step could be, or teach me how they compile kernels for their device ?
Many thanks for any help,
Cheers
TLDR. How to compile a kernel? I have Sony's source for kugo, but don't understand how to configure the kernel compilation.