lollipop/kitkat versions of Low Lying Fruit Kernel (LLFK) for N915T

lollipop/kitkat versions of Low Lying Fruit Kernel (LLFK) for N915T - Note Edge General

(6/30/15) Newest LLFK for T-Mobile Note EDGE N915T Lollipop.
Now has TCP congestion control options with default TCP Westwood
This version is flashable using TWRP.
Features:
SELinux=Permissive option
init.d support
adbd insecure
TCP congestion controls: TCP options include Westwood, cubic, reno among others: default is Westwood
Modifications that need to be made when using LLFK kernel
1)In build.prop set
ro.securestorage.support=false
2)For those that use AllShare Cast you will need to do two things.
First, add the following line at the end of build.prop
wlan.wfd.hdcp=disable
second, you need to have the Xposed module Wanum Xposed installed. In Wanum select "security hacks" then check box of Fake system status
Download link:
https://www.dropbox.com/s/6bg9l8qqcmmh83x/llfk_permissive_initd_adbd_tcp_lpop.zip?dl=0
Check below for other information that might come in handy and good luck!
(06/11/15)New Low Lying Fruit Kernel (LLFK) for Tmobile Note Edge (lollipop)
I've added adb insecure to kernel. This gives you root access to modify /system on phone from a pc
Features:
SELinux = Permissive option
init.d support
adb insecure
download link
https://www.dropbox.com/s/kr7xb22449p497w/llfk_permissive_initd_adbd_lpop.zip?dl=0
(06/10/15) Low Lying Fruit Kernel (LLFK) for Tmobile Note Edge (N915T)
Two new flashable kernels. One for Lollipop the other for Kitkat.
Lollipop: This new version has init.d support so, for example, you can write scripts that run on boot up. (more below).
Features:
SELinux = Permissive option
init.d support
https://www.dropbox.com/s/k8w423ecoj1covs/llfk_permissive_initd_lpop.zip?dl=0
Kitkat:This version now has TCP congestion control options available (e.g. Westwood)
Features:
SELinux = Permissive option
init.d support
adb insecure (allows you to have r/w access to phone's /system from you pc)
TCP congestion control options
Thanks to JT man for testing
https://www.dropbox.com/s/jbifzsuztb73wpg/llfk_permissive_initd_adbd_tcp_kkat.zip?dl=0
Example of init.d script to automatically set SELinux=permissive given here
https://forums.oneplus.net/threads/how-to-selinux-permissive.314120/
couple notes on how-to-selinux-permissive
1)You only need have permissions of /sys/fs/selinux/enforce set to 644
2)Make sure permission of init.d script is 775
One more thing, knox based warnings can be silenced using wanum.
(05/27/15) Low Lying Fruit Kernel (LLFK) for Tmobile Note Edge (N915T) running Lollipop.
For those that miss having SELinux=Permissive on their T-mobile Note Edge running lollipop, here is a kernel
that supports this setting. The kernel is based on the Tmobile Note Edge Lollipop source code. The only thing that was
changed was a setting in the kernel's Makefile to allow the user to choose whether they want to have SELinux=Permissive
as described for the previous Kitkat version of LLFK below.
NOTE: This time around, the kernel is packaged as a zip file than can be directly flashed in recovery.
But before I go any further I need to give credit to @TEKHD for providing a zipped
version of the T-Mobile kernel I could modify and, in addition, for testing it.
Please buy him a well deserved cup of coffee!
Once you have flashed the kernel and rebooted you are ready to set SELinux=permissive by opening a terminal and typing
su
and
setenforce 0
To check it worked, go to settings > About device and you should see, under SE for Android status, that it is now set to Permissive.
An alternative way to change the setting with this kernel is to use the apk SeLinuxModeChanger. Unfortunately this apk is no longer
available at the play store but you can still download it from the F-Droid site.
https://f-droid.org/repository/browse/?fdfilter=selinuxmodechanger&fdid=com.mrbimc.selinux
A third option would be to set up an init.d script if your rom permits it.
I must admit, at the time of this writing, I'm still on KitKat and have yet to try this on my phone. I'll be checking out lollipop soon
but till then, let me know if/how it works. If successful I'll start adding a few more low lying fruit I've picked!
Remember to do a full nandroid back-up before trying this so your phone can return to its original state before trying llfk if needed.
The usual disclaimer applies!
Good Luck!
lollipop LLFK download link:
WAIT! Only one person has tried this version and although it worked for him, I still consider it beta at best. You have been warned!
WAIT! WAIT! One more thing: You need to do the following otherwise you may experience problems with WIFI:
Download the apk BuildProp Editor and use it to set
ro.securestorage.support=false (thanks @TEKHD for checking this)
WAIT! WAIT! WAIT! May be an issue with private mode not working (see http://forum.xda-developers.com/showpost.php?p=61033627&postcount=109 ). I did not have this problem on kitkit. I am unable to test till next week so if someone can check it out that would be great.
http://www.4shared.com/zip/Z8g1u3FHba/llfk_permissive_lpop.html
dropbox link
https://www.dropbox.com/s/ud84t2fc3n9sqdg/llfk_permissive_lpop.zip?dl=0
Below only applies to the KitKat version.
(04/07/15) Update:
Well, I had a little time and decided to add a feature to LLFK. So for now it has the following three capabilities.
1)Allows you to set SELinux = Permissive
2)adb insecure
3)init.d support
Here is the link for the tar file. (follow same instructions given below to install via ODIN):
http://www.4shared.com/archive/2PepSJcPce/llfk_permissive_initd_adbtar.html
Let me know if/how it works...
New features:
The kernel is now adb insecure. This was accomplished by replacing the adbd file in ramdisk with one due to @freeza. Big thanks to him (as in buy him a cup of coffee!) for giving me permission to use it. With adb insecure you can now remount system as r/w from your pc which can come in handy at times.
The kernel has init.d support (Allows you to run scripts from boot) by modifying the ramdisk using the instructions in STEP 1 (Making kernel ready) of the following post
http://forum.xda-developers.com/showthread.php?t=2287540
So this part is done for LLFK
For it to work, the user still needs to make some minor modifications (add a file and create a directory) in their rom. To do this, please follow all 4 parts of STEP 2 (Making Rom Ready) in the same post.
Once you have completed STEP 2 you are ready to try some scripts.
You can search the Internet for init.d scripts to try.
For example there are some init.d scripts in the later half of the following post to give you an idea.
http://en.miui.com/thread-5685-1-1.html
If folks can experiment to see what scripts work I will make a list and post it here.
Seems to work OK on Hyperdrive and Lab Rats (let me know otherwise).
CAVEAT: When testing whether init.d support was successfully implemented I had tried some scripts (like echo "2048" > /sys/devices/virtual/bdi/179:0/read_ahead_kb; ) that should have modified some kernel settings at boot up. But as it turns out there are a set of scripts that run after boot up that supersede these settings. These scripts are in the file /etc/init.qcom.post_boot.sh. (some other neat stuff to play around with in there!) If you want those scripts to not take effect you can simply comment them out and then your init.d scripts will work.
The usual disclaimer and Good Luck
Original post 1/30/15
**********************************************************************************************************************************************************************
Hi. I thought I'd give out this kernel which allows one to set SELinux=permissive for a rooted T-Mobile Note Edge with base NK3. This setting is needed if you would like to run Linux on Android and, I believe Viper4Android if you are so inclined, as well as some other specialized apps (for future reference, let me know what apps you use that need this setting). Once you have loaded this kernel you can use the app SELinuxModeChanger, found in the play store, to set SELinux=Permissive and back to Enforcing. Note, this setting is maintained until you change it back in the app (rebooting will not change the setting). Anyways, what I am providing is a gzipped tar file that you can download, gunzip and then load on your phone using ODIN (version 3.07 worked fine for me, goes in PDA). Remember, this kernel is ONLY for the T-Mobile N915T NK3 rom. Actually, I have only tested it on the Lab Rats rom so hopefully it will work on other roms for T-Moble N915T with NK3 base.
As most folks like to have a name for their kernel I've decided to call this the "Low Lying Fruit Kernel" (LLFK) because it only has a minor change made to it. Indeed this kernel is about as low as it goes (lol) as not a single line of code is changed. I only changed an option in the Makefile from true to false. Details are given at the following github site.
https://github.com/mscion/Permissive-Kernel-N915T-EDGE/
Anyways, I've been using this kernel for over 10 days with no problems, but, of course , for those that try LLFK, the usual warnings apply! I am not responisble for anything that happens to your device as a conseqence of
using this kernel. Indeed you have to be crazy to try it as I have zero experience at this! You also might want to read this before you try setting SELinux=permissive:
http://en.wikipedia.org/wiki/Security-Enhanced_Linux
One more thing, while my preference is that an experienced dev make a kernel worthy of the N915T EDGE, I am open to suggestions to make some more modifications assuming the request are somewhat consistent with the philosophy of LLFK.
Thanks to @jimmydene84 for boot.img and @deeznutz1977 for testing!
Don't forget to do a full back up! Good luck!
Kernel Download link: For SELinux=Permissve option only
http://www.4shared.com/archive/oH5fE053ba/llfk_permissivetar.html

Hey that you that working. I was wondering if there was anyway you would make/try to make the same type of mod/kernel for the sprint version. N915P I believe it is. I will be more than willing to help anyway I can.
The reason I need SELinux to permissive is because to use certain bluetooth controller mapping apps u need it on permissive. Specifically the OG Moga Pocket, that controller only works with the pivot app. In order to have android pick it up as a hid controller, I need the app I use to access linux. I really hate to ask but it looks like there's very limited dev for sprint ?

VenpaCasa said:
Hey that you that working. I was wondering if there was anyway you would make/try to make the same type of mod/kernel for the sprint version. N915P I believe it is. I will be more than willing to help anyway I can.
The reason I need SELinux to permissive is because to use certain bluetooth controller mapping apps u need it on permissive. Specifically the OG Moga Pocket, that controller only works with the pivot app. In order to have android pick it up as a hid controller, I need the app I use to access linux. I really hate to ask but it looks like there's very limited dev for sprint ?
Click to expand...
Click to collapse
Ok, As long as you are willing to test it! Presumably no harm will be done as long as you do a full nandroid back up. Give me a few days to gather files and such...

Awesome @mscion

deeznutz1977 said:
Awesome @mscion
Click to expand...
Click to collapse
Thanks! What would be even more awesome is if someone tries it and it works! lol.

I'll flash it now kind sir

mscion said:
Ok, As long as you are willing to test it! Presumably no harm will be done as long as you do a full nandroid back up. Give me a few days to gather files and such...
Click to expand...
Click to collapse
Omg dude if ur really serious, hell yeah I'm willing to test. I'm extremely greatful n lost for words right now. Thanks so much for just attempting ?? at least. Made my day lol

deeznutz1977 said:
I'll flash it now kind sir
Click to expand...
Click to collapse
I hope you mean Odin it! Drum roll please....

mscion said:
I hope you mean Odin it! Drum roll please....
Click to expand...
Click to collapse
kernel is not se android enforcing

@mscion you still had to use the selinux changer app correct?

deeznutz1977 said:
kernel is not se android enforcing
Click to expand...
Click to collapse
Hi @deeznutz1977. Depending on rom, I think when you boot up you will get that message. Please check in settings > about device and see what SE for android is showing. For now I have pulled the kernel because I unwittingly used the boot.img from lab rats rom to pack in my zImage file that allows permissive setting, cause I thought it was not modded. I am currently waiting to hear from @jimmydene84...

deeznutz1977 said:
@mscion you still had to use the selinux changer app correct?
Click to expand...
Click to collapse
Yes. Check the OP for more details. Once you have installed this kernel, you have the option to turn permissive on or off with this app. You should also be able to set it from command line as well. May I ask which rom are you using? Also, as I just mentioned I need to check with jimmydene84 about his boot.img...

mscion said:
Yes. Check the OP for more details. Once you have installed this kernel, you have the option to turn permissive on or off with this app. You should also be able to set it from command line as well. May I ask which rom are you using? Also, as I just mentioned I need to check with jimmydene84 about his boot.img...
Click to expand...
Click to collapse
Stock deodexed. And sorry about not reading the op. Don't you know that all of the cool people don't read ops
Sent from my SM-N915T using Tapatalk

@mscion I asked jimmydene to pm you ...

deeznutz1977 said:
@mscion I asked jimmydene to pm you ...
Click to expand...
Click to collapse
Thanks very much! We're all good. I'm putting the link back up shortly.

Got excited for a minute I thought deeznutz1977 said he flashed on a Sprint Note Edge. Had to read it over a couple times.

VenpaCasa said:
Got excited for a minute I thought deeznutz1977 said he flashed on a Sprint Note Edge. Had to read it over a couple times.
Click to expand...
Click to collapse
Almost there. It appears to have compiled fine. I need to download the sprint rom and extract its boot.img file so I can pack the file for you to odin. Maybe this afternoon...
I will use the sprint deodexed version NK1, to extract boot.img from, that @snovvman has posted in the sprint developers thread. (hope that is ok! EDIT: We're good!)

mscion said:
Almost there. It appears to have compiled fine. I need to download the sprint rom and extract its boot.img file so I can pack the file for you to odin. Maybe this afternoon...
I will use the sprint deodexed version NK1, to extract boot.img from, that @snovvman has posted in the sprint developers thread. (hope that is ok! EDIT: We're good!)
Click to expand...
Click to collapse
Honestly your awesome. I was starting to regret my purchase too. I'll assume you weren't asking me if it's ok but if you were, yeah that's fine. I'm actually any using that ROM
EDIT: Just saw your edit n thanks (to both) that's so awesome! I owe you guys!

When ubr done are you going to post here or a new thread?

VenpaCasa said:
When ubr done are you going to post here or a new thread?
Click to expand...
Click to collapse
Just pm'd you with link. If it works I'll post it in this thread.

Related

[APP] Milestone - Overclock (requires root)

Hi all,
I realize this is a post about a Motorola phone but please bear with me.
As you might know, the Milestone firmware is firmly locked, unlike its cousin Droid. Among many things, this forbids overclocking because we can't change the kernel and unlock new frequencies.
However I developed a solution that allows overclocking by changing key structures directly in the kernel memory in runtime. All you need is a rooted phone; no flashing involved. For this to work, the module must know two memory addresses that are specific to each kernel. Fortunately, Motorola appears to have reused its kernel on most 2.1 firmwares, and I've yet to come across a firmware where it doesn't work by default. Confirmed working are Central Europe, Telus and Brazilian firmwares. Testers are welcome to give it a try.
Now for the relevant part for XDA: in theory this can be applied to any kernel on any other phone. You may say it's unneeded because you can already overclock; but you must flash a specific kernel to get a particular speed. It would be much better to be able to set any maximum frequency/voltage on the fly without flashing or rebooting. For instance, you could overclock to 1.0 GHz before a browsing or gaming session and then return to a lower frequency like 600 MHz, though still overcloked, for battery savings and safety. It's up to you.
Milestone users can try it out now:
http://code.google.com/p/milestone-overclock/
For the rest of you, what do you think?

sounds fantastic, I'd love to check it out but for the life of me I can't find the page.
If you want to pm it to me, I'll post it.

Nice. Telus Milestone User here. Would love to learn how to do this for mine.
Here is the project link:
http://code.google.com/p/milestone-overclock/

found it. looks like a fantastic idea.
How can we help get the addresses?

awesome .....wht there is no milestone/droid section here is beyond me ....wtf

Because it was decreed months ago by someone and no one seems to like changing their mind once they make a decision in this day and age.....

but it's need to root, could you fix it？

stevecai said:
but it's need to root, could you fix it？
Click to expand...
Click to collapse
what's the problem with rooting the milestone? There's plenty of solutions for that. Just no custom kernel/ramdisk, which this works around by using a kernel module.

hi,
i use the 2.1-reu version on my milestone,
but in order to prevent the 2.1 introduced alarm bug,
i have updated the kernel (only) to the 2.1-telus
(via a sbf).
is possible to use this mod to overlock my phone?
how?
if not, how help you to obtain the addresses?
thank's and continue your great work!
robert

gemini002 said:
awesome .....wht there is no milestone/droid section here is beyond me ....wtf
Click to expand...
Click to collapse
XDA is a HTC developer forum, not an Android forum. Google some moto modding sites, i know modmymoto.com is pretty good, found out how to root the Cliq (garbage) there.

staticshadow said:
XDA is a HTC developer forum, not an Android forum. Google some moto modding sites, i know modmymoto.com is pretty good, found out how to root the Cliq (garbage) there.
Click to expand...
Click to collapse
I have read this explanation several times.
I do not mind, but then because there are subforums dedicated to sonyericsson, hp, etc in xda.
modmymoto is good but the best developers site is, withous any doubt, xda-developers!

Re: milestone-overclock
Xda-developers is for htc and android is for porn.
Welcome to xda btw and great job. Now prepared to be flamed for uttering the M word.
-------------------------------------
sent via xda app from my milestone

ady said:
android is for porn.
Click to expand...
Click to collapse
are you Steve Jobs ?

miragu said:
Hi all,
Now for the relevant part for XDA: in theory this can be applied to any kernel on any other phone.
Click to expand...
Click to collapse
Will the method to find the right address that will be posted at /wiki/Disassembly work with every phone and kernel,too?
Has the app something like a setting where you can just change the address to the one you found with the method above?
Would really love an overclocked 2.1 on the HTC HERO. There is no oc-2.1-kernel for the Hero, yet.
Thanks for the great work, til now!

this is a good via to mod any application.
please, publish the source code of your applicacion ASAP.
thx

Source code for the kernel module released
Hi all,
Thank you for your support. I've just uploaded the source code for the kernel module and also the standalone module itself (it's included in the apk but still). Will write the Disassembly section soon, stay tuned.

miragu said:
Hi all,
Thank you for your support. I've just uploaded the source code for the kernel module and also the standalone module itself (it's included in the apk but still). Will write the Disassembly section soon, stay tuned.
Click to expand...
Click to collapse
hi,
i'm interested on include this in my system applications directory,
in order to prevent your deletion on hardreset, and in order to make it available FOREVER
the instructions are that:
cp OverClock.apk /system/app
cp OverClock.ko /system/lib
????
thx

The overclock.ko is created automatically when you press the "Load module" button in /data/data/pt.com.darksun.milestoneoverclock/files/overclock.ko. You don't need to copy it. I'm providing it separately so that people can load/bundle it without ever running the apk.
bartito said:
hi,
i'm interested on include this in my system applications directory,
in order to prevent your deletion on hardreset, and in order to make it available FOREVER
the instructions are that:
cp OverClock.apk /system/app
cp OverClock.ko /system/lib
????
thx
Click to expand...
Click to collapse

ok,
if i'm interested on have overclocking on my milestone after boot the system, and don't interested on manually execute the apk on each reboot, i need only to copy the OverClock.ko to /data/data/pt.com.darksun.milestoneoverclock/files/overclock.ko on boot time ?
but in your wiki page says to execute "insmod overclock.ko max_rate=800000 max_vsel=62"
please, provide me instructions to set overclock in boot time

The module created by the apk is preserved across reboots. However, if you want to run the module completely standalone I recommend you put it in /data/local/overclock.ko and run insmod /data/local/overclock.ko max_rate=800000 max_vsel=62

Any init.d Scripts Yet?

Curious if there are any init.d script yet for the SGS3 or any generic ones that may be of use...

Bump bump

we have a kernel featuring it in the sprint section, only it increases your flash counter, if your concerned about that.

teh roxxorz said:
we have a kernel featuring it in the sprint section, only it increases your flash counter, if your concerned about that.
Click to expand...
Click to collapse
Every time it initiates? (after each boot)
Regardless, I don't really care lol.
I must have missed the kernel, I've been watching the Sprint forums too.
What does it features?

stock kernel..insecure, so adb remount works, init.d is all I believe. And it will only increase your flash counter by one, when you flash the kernel.

teh roxxorz said:
stock kernel..insecure, so adb remount works, init.d is all I believe. And it will only increase your flash counter by one, when you flash the kernel.
Click to expand...
Click to collapse
ah, OK cool, thanks.
We already have that on T-Mobile side. I created (well, I didn't create, I modified DoomLords script for our phone) a flashable zip to manually add init.d support as well.
Will likely have to wait until init.d scripts are written and coded into the kernels. Way too early most likely

uoY_redruM said:
ah, OK cool, thanks.
We already have that on T-Mobile side. I created (well, I didn't create, I modified DoomLords script for our phone) a flashable zip to manually add init.d support as well.
Will likely have to wait until init.d scripts are written and coded into the kernels. Way too early most likely
Click to expand...
Click to collapse
No worries man. Too early indeed..LOTS still don't have the phone lol. I think it will pick up in a week or so.

[KERNEL][I8200N] Baroni-Kernel Alpha

I can give ABSOLUTLEY no gurantee!! All you do with your phone will be on your own. I'm not responsible if your phone will brick or whatever...
Attation! This kernel is for the I8200 variant ONLY... the I8190 is absolutley not compatible !!!
Kernel should be work also for I8200/I8200Q/I8200L-Variants, but can not be gurateed as the basis was I8200! If it works then a notice will be fine!
If you are not sure about the process, the data are important on your phone or you need it as a daily phone, then LET IT BEE, and wait for the messages that it is safe to use. Its important at the beginning that users with knowledge tried it at first !
Changelog:
12.02.2016: Long time ago, but now after a lot of investigating some new things comes up. Check what was done
05.01.2014: I try to work on the kernel over x-mas in my free time, but I must say that the source of samsung which was provided on opensource.samsung.com is not really funny stuff... there are so many coding errors, which was. not able for me to solve directly. So now I started to examine other kernel sources, and will try to port a more main.tained source to the i8200. From My point of view this will be the only way to produce an more accurate kernel for our device, and get the possibility to include also selinux what is needed for a kitkat-rom. Nevertheless, it is not easy to work on that stuff, because I'm not an expert on kernel work (but I learn every day more , so if you know someone with more kernel experiences, it would be very helpful to get a contact...
Baroni-V0.1 contains:
Basis of opensource from Samsung with some bugfixing
fixed recovery-boot-loop with a config-setting which must be used special in the Recovery zImage
Loglevel pushed down to minimum
Uber-Toolchain 4.9
set onDemand-Governor to standart. just to check how that works
start implementing SmartAssV2-Gonernor, but leave it inactive, due to some compile-errors.
bringing SELinux to work for future kernel releases if needed for > 4.4
Planned:
new govenors at the moment not established (will come later)
more other stuff (depending on learning-curve
Installation:
Install a recovery for safetyreasons (I prefer TWRP https://www.dropbox.com/s/d3rnfp3vabz9ee8/twrp_i8200_corrected.7z?dl=0
Read carefully the hints of the usage in the following firts post: http://forum.xda-developers.com/galaxy-s3-mini/general/s-iii-mini-ve-i8200-n-t2826565 (There also the needed Odin (3.09) can be get)
Make backups of the complete phone, and be sure that you know what you do!
Download the right Firmware for your phone from http://www.sammobile.com/firmwares/ (just to have a other safety fallback in your hand!)
Download the file, start odin as usual (all kies-tasks closed!)
extract the file, and put it to AP
put the phone in Downloadmode (Vol-down,Home-key and powerbutton), and connect the phone with PC
flash the kernel, and let the phone reboot
pray
If things go wrong, please give everytime the following information's:
what you did before
what exactly happened (its not easy to help if you say: it did not work )
which rom in which version, which recovery and which version of my Kernel you use
try to get a /proc/last_kmsg (if a unknowen reboot appears) and/or Logcat, Build prop, CPU info, Sysctl, Kmsg, Dmesg and send it to me (or as a attachment to the post) for further analyse (you can use that tool for it: https://play.google.com/store/apps/details?id=com.bassel.andylog )
Attention: First checks seem to be that I8200 (without N or L or Q) did not work atm.
Download:
kernel_i8200n-Baroni:
https://www.androidfilehost.com/?w=files&flid=47763
kernel_i8200n-Stock.7z (to getting back to stock kernel via Odin):
https://www.dropbox.com/s/xfhufcpxl5kxmue/kernel_i8200n-Stock.7z?dl=0
Recoverys (with fixed recovery boot loop):
https://www.androidfilehost.com/?w=files&flid=49834

There was a mistake in the initramfs. was corrected now. If you download the V0.7 yesterday, please dont use it... Try V0.8.

One question.
SolarPlexus said:
There was a mistake in the initramfs. was corrected now. If you download the V0.7 yesterday, please dont use it... Try V0.8.
Click to expand...
Click to collapse
My Friend.
Yesterday I tried to install its kernel but my phone did not start properly.
I wanted to do a restore from a backup that had done, but the recovery (TRWP) did not restore the data partition.
Is there any chance that I happen again the same with this version?

Danh23 said:
My Friend.
Yesterday I tried to install its kernel but my phone did not start properly.
I wanted to do a restore from a backup that had done, but the recovery (TRWP) did not restore the data partition.
Is there any chance that I happen again the same with this version?
Click to expand...
Click to collapse
Attention with TWRP-Recovery. Data-Partition restore seems to be not right. At the moment please did not use it, because it can delete your data-partition. We have to investigate it further! Other partitions seems to be ok, but its a good Idea if you copy your important data also manually to a other storage (like PC) while you trying things of this thread.

i install the kernel ans stuck into samsung logo.if i flash the stock kernel i will fix it?
stock kernel?can you upload it?

KwstPap said:
i install the kernel ans stuck into samsung logo.if i flash the stock kernel i will fix it?
stock kernel?can you upload it?
Click to expand...
Click to collapse
Did you made a backup with twrp (as described)? If yes, then make a restore only with boot marked in the list.
Otherwise, which version did you have? Plain n/l/q? Than I can make a package for Odin...
send with my Oneplus One (bacon) SlimKat Tapatalk

About the data recovery, use aroma FM to restore. Out worked for me

hahhhahaha i forgot it to take a backup hahaha .i reflashing the stock firmware... i Have i8200N
but why the kernel doesnt work on me?

KwstPap said:
hahhhahaha i forgot it to take a backup hahaha .i reflashing the stock firmware... i Have i8200N
but why the kernel doesnt work on me?
Click to expand...
Click to collapse
You are a funny guy... Flasching things without reading the guide is something like a other guy I know from kentucky fried movie (Danger-seeker)
Nevertheless, I added in first thread the stock kernel for i8200n to flash with odin.

SolarPlexus said:
You are a funny guy... Flasching things without reading the guide is something like a other guy I know from kentucky fried movie (Danger-seeker)
Nevertheless, I added in first thread the stock kernel for i8200n to flash with odin.
Click to expand...
Click to collapse
hahahahaha always forget to take a backup .but i am very stypid .i had a backup on my pc.hahah in one weak i have reflashing the stock formware 5 times and the root recovery and other staff again hahaha
thanks for the stok kernel

SolarPlexus said:
You are a funny guy... Flasching things without reading the guide is something like a other guy I know from kentucky fried movie (Danger-seeker)
Nevertheless, I added in first thread the stock kernel for i8200n to flash with odin.
Click to expand...
Click to collapse
¿which brings benefits to install this kernel?

RodsonBorja said:
¿which brings benefits to install this kernel?
Click to expand...
Click to collapse
Atm nothing... Its alpha and not working. Unfortunately I'm a little bit blocked by illness and x-mas and was not able to work on it... Maybe next week...
send with my Oneplus One (bacon) SlimKat Tapatalk

Hi to all followers of this thread.
Just to give an update: I try to work on the kernel over x-mas in my free time, but I must say that the source of samsung which was provided on opensource.samsung.com is not really funny stuff... there are so many coding errors, which was not able for me to solve directly. So now I started to examine other kernel sources, and will try to port a more maintained source to the i8200. From My point of view this will be the only way to produce an more accurate kernel for our device, and get the possebility to include also selinux what is needed for a kitkat-rom...
Nevertheless, it is not easy to work on that stuff, because I'm not an expert on kernel work (but I learn every day more , so if you know someone with more kernel experiences, it would be very helpful to invite him/her. To ask in forums (also in xda) is something what I do, but unfortunately the responding are not every time safe...
So I wish you all a happy new year, and lets work together to bring our device a little bit forward
SolarPlexus

Ask @dtrail1 he know how the kernel thing work.
Maybe he'll support you

VallNAr said:
Ask @dtrail1 he know how the kernel thing work.
Maybe he'll support you
Click to expand...
Click to collapse
Ask MARDON he made the kernel for Galaxy Ace - maybe he support Your work.

Any progress on the kernel? Is it on github?

Why does this not suport usb flash drives or can the function be ported
Gershy353

I think it must be activated on both sides. Kernel and ROM...
send with my Oneplus One (bacon) SlimKat Tapatalk

SolarPlexus said:
I think it must be activated on both sides. Kernel and ROM...
send with my Oneplus One (bacon) SlimKat Tapatalk
Click to expand...
Click to collapse
How is this done i have the sandisk dual flash drive but its useless on my device
Gershy353

Ah, you mean otg support, not sdcard seen as USB instead of mtp?
send with my Oneplus One (bacon) SlimKat Tapatalk

[GUIDE] How to Compile Your Own CM11/CM12/AOSP Kernel

Hi guys, long time no post. I have updated this guide on how to build kernels for Falcon so that anyone can learn! It's pretty simple once you get the hang of it. So yeah, here we go!
Prerequisites:
- You must have a Linux firmware running on your computer (I suggest Builduntu because you can skip the next one [build environment setup])
- Build environment setup (Put the this in terminal and follow instructions)
- Patience and a heart willing to learn
- You need to know the languages C, C++, Java, Ruby, Python... NOT! You don't need to know ANY coding languages.
[MOTIVATIONAL SPEECH]
Truth be told, when I first started out developing, I knew NO coding languages except for HTML and a little bit of Java. Both have nothing to do with kernels! I actually learned how to do this when I suffered from a concussion. So if you really want to learn how to kernel dev and you give up halfway, just know that a 14/15 year old kid could do it..
[/MOTIVATIONAL SPEECH]
Click to expand...
Click to collapse
WARNING: I am not responsible for any damages to your phone or computer or pet unicorn. When you modify the wrong partitions, set too many jobs for your compiler, break your keyboard out of frustration etc., that is not anyone's fault but yours. Or your pet unicorn.
Your Personal Handbook to the Following:
- Anything inside "CODE" boxes, type it into your terminal. If you can't find terminal, then press CTRL, ALT, t.
- If I were you, I would write these by hand instead of copying and pasting it because after a certain amount of times, you will remember the linux commands and it will be easier for you to compile more kernels for different devices
- Use this thread as a "Help Me" button. Ask for help!
Click to expand...
Click to collapse
A New Beginning:
Let's start out with something simple, getting the actual code:
Code:
git clone https://github.com/cyanogenmod/android_kernel_motorola_msm8226
This could range from 3 minutes to 2 hours!
Once that's done, open up your file manager and rename the folder (should be android_kernel_motorola_msm8226) to whatever you want. I will refer it as "mykernel".
Click to expand...
Click to collapse
Pokemon!
For this tutorial, we will be using a Sabermod 4.7 toolchain to compile. I WOULD teach you how to compile with 4.8+, but it creates errors that will take even longer for me to write about sooooooooo :fingers-crossed:. Now to get the toolchain:
Code:
git clone https://github.com/SaberMod/android_prebuilts_gcc_linux-x86_arm_sabermod-arm-eabi-4.7
Rename this to whatever you like, but I will be referring this as "toolchain"
Now go into you folder where the kernel source is stored...
Code:
cd mykernel
Click to expand...
Click to collapse
You're Almost There!:
Time to set-up the compiler!
Code:
export CROSS_COMPILE=/home/(insert linux home name here)/toolchain/bin/arm-eabi-
This tells the toolchain that "OK, we want to make ALL this code here into a kernel".
This next line tells it that your defconfig (the toolchain's manual for compiling the kernel) that it's in the arch/arm/configs folder.
Code:
export ARCH=arm
Now to tell the it what the defconfig is!
Code:
make falcon_defconfig
Hehe, now to the hardest part of all...
MuHAHHAHAHa
Click to expand...
Click to collapse
THE HARD (coding) PART
You ready for this? HERE IT IS! TIME TO BUILD THE KERNEL!
Code:
make -j4
Now sit back, relax, and watch the code! Or you could read a book, watch ****, count your fingers, play with your toes...
If you have an error during the waterfall of code, find the part where it actually says *error* (you'll probably have to scroll upwards) and search it on Google or post it here.
Click to expand...
Click to collapse
THE BEST PART
If you manage to get something that says "the kernel zImage is ready" or something like that, that means you've made it!
You have officially compiled your own kernel from source! Now you need to put it in a flashable zip.
Download this file and open it up, but DON'T EXTRACT IT.
Now go to your kernel source then "CTRL + F" and search for "zimage-dtb".
Find it and put it in the "kernel" folder of "FalconKernel - Signed.zip". Then "CTRL + F" and search ".ko".
Copy radio-iris-transport.ko and put it in the system/lib/modules (not pronto) of the zip.
Then find wlan.ko and rename it to pronto_wlan.ko. Copy and paste it in system/lib/modules/pronto of the zip.
Click to expand...
Click to collapse
Now you can put it on your phone and flash it!

I will update this in a bit. What feature would you guys want in your kernel? The most votes in the POLL above will be the one I teach you here!
Here I will walk you through on how to add the intelliplug feature made by @faux123
First, fetch my Green Machine kernel source (go into your kernel folder in terminal):
Code:
git fetch https://github.com/YoshiShaPow/green_machine_falcon
Then you could cherry-pick (basically copy) all my cherry picks for intelliplug from my source.
If you do check my source out, you can see there's a little link to a history of commits near the middle of the screen, right above the files/folders. You can see at this page of my features history, you'll see a bunch of commits for intelliplug. I will use those commits and copy it to your own kernel.
This copies the initial coding/first commit of intelliplug!
Code:
git cherry-pick 01a850f
This cherry-picks the remaining commits so that your newly added intelliplug is updated.
Code:
git cherry-pick 6623f2f^..4e1ece7
One more thing though, you need to add the line to compile intelliplug!
Almost all things compiled along with the zImage are in a file called defconfig. What a defconfig does, is tell your machine to build certain modules, kernel objects, drivers, governors, etc.etc.etc.. Now, all of them are found in the folder
arch/arm/configs
Click to expand...
Click to collapse
As stated in the OP, you have to modify the defconfig you use. (CM11 Kernel is falcon_defconfig, Gummy Kernel is msm8226_mmi_defconfig). Open up the corresponding defconfig and add this to ANY line anywhere.
Code:
CONFIG_INTELLI_PLUG=m
Now, for those who are familiar with "y=yes/n=no/m=maybe", you'll see that I specifically told you to put the "m=maybe" one. That's because when you compile the kernel again, right after you're about to start your build. Since you put that "m", the terminal will prompt you with a "y=yes/n=no" question on whether or not you would like to add the following feature. Since you would like to add the feature, put in "y". Later on when you feel more comfortable with adding features to your kernel, you can go back into the defconfig and put it as
Code:
CONFIG_INTELLI_PLUG=y
So that it will compile it without asking, since you have given it an answer.
Now you have officially compiled a "Custom Kernel" and with the knowledge you know, you could create a feature packed one by just kanging (copying one's work/features).
Always remember to
Code:
make clean && make mrproper
after every build to prevent errors and such!
Click to expand...
Click to collapse

I will use this to teach you how to make your own Bash Building scripts (and save time) to make it easier for your development life to flourish... eventually....

Any guide on adding governors or hotplug driver??
Sent from my Moto G using XDA Free mobile app

Best guide but how to add features likes s2w,dt2w etc

Flashhhh said:
Any guide on adding governors or hotplug driver??
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
Vote in the poll above! I will make a guide for one or more of the top chosen picks!
Brawn_Sg said:
Best guide but how to add features likes s2w,dt2w etc
Click to expand...
Click to collapse
DT2W and S2W are more complex. They require a few other things (ex. Powersuspend). I'll wait a bit and see what feedback I get before moving forward to something a bit more complex like DT2W, or GPU Overclock.

Can i use make menuconfig?

Krizthian said:
Can i use make menuconfig?
Click to expand...
Click to collapse
Yes you can. Normally when using "make menuconfig", you use the command after making the kernel's defconfig (falcon_defconfig).

Build using Docker
If you're on Linux, take a look at this approach which uses Docker for building CyanogenMod 12.0:
http://forum.xda-developers.com/showthread.php?t=2650345
(Disclaimer: It's written by me)

YoshiShaPow said:
Hi guys, long time no post. I have updated this guide on how to build kernels for Falcon so that anyone can learn! It's pretty simple once you get the hang of it. So yeah, here we go!
WARNING: I am not responsible for any damages to your phone or computer or pet unicorn. When you modify the wrong partitions, set too many jobs for your compiler, break your keyboard out of frustration etc., that is not anyone's fault but yours. Or your pet unicorn.
Now you can put it on your phone and flash it! 
Click to expand...
Click to collapse
when i was trying to flash cm12 rom in cwm recovery it says error in zip and getting status 1 error , installation aborted ,
pls help im using moto g gpe and when trying to flash from twrp it says error executing updater binary in zip ,
no idea what to do pls help me out

karthik432 said:
when i was trying to flash cm12 rom in cwm recovery it says error in zip and getting status 1 error , installation aborted ,
pls help im using moto g gpe and when trying to flash from twrp it says error executing updater binary in zip ,
no idea what to do pls help me out
Click to expand...
Click to collapse
When you downloaded the anykernel zip, you aren't supposed to extract it. The best way to put the kernel in the zip is to just drag and drop it while IN LINUX. It will not work for windows! Or you could try signing the zip in TWRP (I think there's an option for that somewhere).

YoshiShaPow said:
When you downloaded the anykernel zip, you aren't supposed to extract it. The best way to put the kernel in the zip is to just drag and drop it while IN LINUX. It will not work for windows! Or you could try signing the zip in TWRP (I think there's an option for that somewhere).
Click to expand...
Click to collapse
im not extracting anything , i just downloaded the official cm12 nightly and flashed but didn't workout ,any ideas

karthik432 said:
im not extracting anything , i just downloaded the official cm12 nightly and flashed but didn't workout ,any ideas
Click to expand...
Click to collapse
That has nothing to do with this thread :silly:. You probably have to sign the zip again.

@YoshiShaPow.... i need some help
i compile a kernel for my device and it booted fine but no display....
can you help me in this....
sorry for posting here..my device is Redmi 1s

Luffy.d said:
@YoshiShaPow.... i need some help
i compile a kernel for my device and it booted fine but no display....
can you help me in this....
sorry for posting here..my device is Redmi 1s
Click to expand...
Click to collapse
No problem, I welcome anyone with kernel development questions here! When booted, what do you mean? And if there's no display, how do you know it booted? Also, did you use my anykernel zip? I may be wrong but I don't think it is compatible with all phones.

YoshiShaPow said:
No problem, I welcome anyone with kernel development questions here! When booted, what do you mean? And if there's no display, how do you know it booted? Also, did you use my anykernel zip? I may be wrong but I don't think it is compatible with all phones.
Click to expand...
Click to collapse
yeah it booted bro....i can hear lock unlock sound and even i can hear incoming call ring
i was trying to fix this from a week and found out it not kernel it rom problem ...
my device is build using prebuilt kernel so any compile kernel wont work...but now they are build with this kernel source so compile kernel work
thanks bro...
and one thing bro... i m new to kernel development so how can i optimize kernel
i know about and can add governors and use custom toolchain but i don't know about o2 or o3 optimization etc and all
sorry if i m being too much

great I start today

Luffy.d said:
yeah it booted bro....i can hear lock unlock sound and even i can hear incoming call ring
i was trying to fix this from a week and found out it not kernel it rom problem ...
my device is build using prebuilt kernel so any compile kernel wont work...but now they are build with this kernel source so compile kernel work
thanks bro...
and one thing bro... i m new to kernel development so how can i optimize kernel
i know about and can add governors and use custom toolchain but i don't know about o2 or o3 optimization etc and all
sorry if i m being too much
Click to expand...
Click to collapse
Those changes are a bit more advanced because it will bring build errors. The kernel is already preoptimized with o2 changes. The errors are fixable though. I don't think I'll be able to add an explanation for those in this thread, maybe through pm?

YoshiShaPow said:
Those changes are a bit more advanced because it will bring build errors. The kernel is already preoptimized with o2 changes. The errors are fixable though. I don't think I'll be able to add an explanation for those in this thread, maybe through pm?
Click to expand...
Click to collapse
thanks bro...will pm you when i finish setuping my git

etvtaglios said:
great I start today
Click to expand...
Click to collapse
Go for it bro!!

forced 4K boot.img for stock?

I know there are a few kernels/boot.img to force native 4K all the time on AOSP based ROMs, but are there any for Stock or Stock based ROMS?
*Dang! Thought I was in the Q&A and just realized I posted this in the wrong section and can't delete or move it.

You might be able to remove the 1080p configuration in the copyleft archive just like in the aosp kernel to get a 4k stock kernel. I haven't looked at it so I don't know if it will work for sure, but its worth a try.
Edit: Looks like it might have worked.

Sepo190 said:
You might be able to remove the 1080p configuration in the copyleft archive just like in the aosp kernel to get a 4k stock kernel. I haven't looked at it so I don't know if it will work for sure, but its worth a try.
Edit: Looks like it might have worked.
Click to expand...
Click to collapse
Could You share the Image with us?:angel:

Miustone said:
Could You share the Image with us?:angel:
Click to expand...
Click to collapse
Yeah, sure. This is a .235 kernel that has been working surprisingly well for me. I used the ramdisk from shoey63's kernel repack here https://forum.xda-developers.com/xz-premium/development/kernel-repository-t3801795, so you need to flash that drmfix.zip too.
A couple of things I have run into though. The finish button wasn't showing up at the end of the setup wizard, so you have to go through that on the stock kernel and then flash this modified one. You might be able to fix it by changing the dpi, but I haven't tried that. You also cant set up any lock screen security until you flash the kernel or it will boot loop when flashed. So, the process that worked for me was:
1) flash stock .235
2) go through setup wizard NOT setting lock screen/fingerprint security
3) flash this kernel, drm fix and magisk
4) reboot
5) setup fingerprint/lockscreen security
You can change the screen dpi by using the wm density command or changing ro.sf.lcd_density in your build.prop.
https://mega.nz/#!o5FjxYwZ!zDS8DRaTnpER7e8YQOyyLjg_hY970geF9QaZajx5oO8
Does anyone know what changes the drmfix requires other than adding "export LD_PRELOAD drmfix.so:drm****.so" to the init.environ.rc in the ramdisk?

Sepo190 said:
A couple of things I have run into though. The finish button wasn't showing up at the end of the setup wizard, so you have to go through that on the stock kernel and then flash this modified one. You might be able to fix it by changing the dpi, but I haven't tried that. You also cant set up any lock screen security until you flash the kernel or it will boot loop when flashed. So, the process that worked for me was:
1) flash stock .235
2) go through setup wizard NOT setting lock screen/fingerprint security
3) flash this kernel, drm fix and magisk
4) reboot
5) setup fingerprint/lockscreen security
You can change the screen dpi by using the wm density command or changing ro.sf.lcd_density in your build.prop.
https://mega.nz/#!o5FjxYwZ!zDS8DRaTnpER7e8YQOyyLjg_hY970geF9QaZajx5oO8
Click to expand...
Click to collapse
If I'm currently on 235, basically all I need to do is flash your kernel + drmfix, right? Or is a fresh install really needed? Btw, do you pass safetynet on your kernel?

iArvee said:
If I'm currently on 235, basically all I need to do is flash your kernel + drmfix, right? Or is a fresh install really needed? Btw, do you pass safetynet on your kernel?
Click to expand...
Click to collapse
I'm pretty sure you're going to need to do a fresh install. You can try without, but I have a feeling you are going to bootloop. It doesn't pass safteynet, but I can probably add the patch in for you. I'll take a look at it later tonight or tomorrow. Now that .270 CE1 is out I was going to move to that, but I can do the .235 one too if you want.

Sepo190 said:
I'm pretty sure you're going to need to do a fresh install. You can try without, but I have a feeling you are going to bootloop. It doesn't pass safteynet, but I can probably add the patch in for you. I'll take a look at it later tonight or tomorrow. Now that .270 CE1 is out I was going to move to that, but I can do the .235 one too if you want.
Click to expand...
Click to collapse
If it's not too much trouble, can you do the .235? I'm most likely not going to be updating to 270 any time soon. Willing to try it out without a fresh install.

This is Awesome! Thanks!
However, drmfix.zip is error 404. Can you post it?
Were you thinking to do one of these for .270?

gaijin1% said:
This is Awesome! Thanks!
However, drmfix.zip is error 404. Can you post it?
Were you thinking to do one of these for .270?
Click to expand...
Click to collapse
https://mega.nz/#!JhtF0bCJ!G0zOmqZYoNeFwSvLQnh5GAMh3_E--XQWAYjzrm4buC0
Yeah. I'll do one for .270, but it might be a week or so. I just got really busy.

Sepo190 said:
https://mega.nz/#!JhtF0bCJ!G0zOmqZYoNeFwSvLQnh5GAMh3_E--XQWAYjzrm4buC0
Yeah. I'll do one for .270, but it might be a week or so. I just got really busy.
Click to expand...
Click to collapse
That sounds great! I'm having trouble with .235, so I'll wait for the .270. MUCH appreciated

Watching gravure will be so much more satisfy ing, thanks

gaijin1% said:
That sounds great! I'm having trouble with .235, so I'll wait for the .270. MUCH appreciated
Click to expand...
Click to collapse
What issue are you having with the .235 one? I can't seem to get the drm fix to work on the .270 kernel as of right now, but I'll look more soon.

Sepo190 said:
What issue are you having with the .235 one? I can't seem to get the drm fix to work on the .270 kernel as of right now, but I'll look more soon.
Click to expand...
Click to collapse
I actually got it set up with 235, but for some reason I can't get it to root. Magisk installs fine, but nothing can get root permission. What version of Magisk did you use?

gaijin1% said:
I actually got it set up with 235, but for some reason I can't get it to root. Magisk installs fine, but nothing can get root permission. What version of Magisk did you use?
Click to expand...
Click to collapse
I used 16.7 and it worked fine for me. Did you try going in the magisk app and granting permission there?

Sepo190 said:
Yeah, sure. This is a .235 kernel that has been working surprisingly well for me. I used the ramdisk from shoey63's kernel repack here https://forum.xda-developers.com/xz-premium/development/kernel-repository-t3801795, so you need to flash that drmfix.zip too.
A couple of things I have run into though. The finish button wasn't showing up at the end of the setup wizard, so you have to go through that on the stock kernel and then flash this modified one. You might be able to fix it by changing the dpi, but I haven't tried that. You also cant set up any lock screen security until you flash the kernel or it will boot loop when flashed. So, the process that worked for me was:
1) flash stock .235
2) go through setup wizard NOT setting lock screen/fingerprint security
3) flash this kernel, drm fix and magisk
4) reboot
5) setup fingerprint/lockscreen security
You can change the screen dpi by using the wm density command or changing ro.sf.lcd_density in your build.prop.
https://mega.nz/#!o5FjxYwZ!zDS8DRaTnpER7e8YQOyyLjg_hY970geF9QaZajx5oO8
Does anyone know what changes the drmfix requires other than adding "export LD_PRELOAD drmfix.so:drm****.so" to the init.environ.rc in the ramdisk?
Click to expand...
Click to collapse
So if this actual 4k?? Like native 4k?? How's battery life/performance??

Sepo190 said:
What issue are you having with the .235 one? I can't seem to get the drm fix to work on the .270 kernel as of right now, but I'll look more soon.
Click to expand...
Click to collapse
I tried several things but couldn't get 235 to root for the life of me.
Now I really want the new ROM [O][8141/8142][.270] M-ROM: Xposed, Daydream compatible so I hope that a .270 based 4K kernel will work with it. Really want that Daydream in 4K. I wonder if your .235 kernel will work with it or if your .270 version will get the drm fix using the Kernel Patch from JanJan.

Sepo190 said:
I used 16.7 and it worked fine for me. Did you try going in the magisk app and granting permission there?
Click to expand...
Click to collapse
Hi man, sorry to interrupt your business, but are there any updates? Could you share with us how exactly you implement the 4k in the kernel? Maybe we could use the manual you're following, and do the work by ourselves.
I'm really curious. More and people are joining in

saved-j said:
Hi man, sorry to interrupt your business, but are there any updates? Could you share with us how exactly you implement the 4k in the kernel? Maybe we could use the manual you're following, and do the work by ourselves.
I'm really curious. More and people are joining in
Click to expand...
Click to collapse
Sorry I haven't given an update in a while. I haven't been on here in a while. I had an unexpected move, so my server wasn't hooked up and then I didn't have internet for a while. Just got it hooked up today actually. I have one with the drm fix working for the newest update using the ramdisk from JanJan's kernel. I can take another look at .270 probably this weekend if you want. I don't have a manual or anything, I'm just removing the 1080p configs from the dts file. I don't remember the file path off the top of my head and I'm not home right now.

It's not possible to enable 4k just édit build prop?
Envoyé de mon G8141 en utilisant Tapatalk

16.20 kernel
Here is a 4k 16.20 kernel that has been working for me for the past week if anyone wants it. I used the ramdisk from JanJan's kernel. Flash it and then everything in his drm-patching zip. The file I have been editing is dsi-panel-maple.dtsi btw, since someone asked earlier.
https://mega.nz/#!R5UhhKjA!U2kp2Zl4gYGddiSIkpJMaOlVYuAcakb514CwHq3jEH4

Database Users

welcome