[`Kernels`&`Recovery`] Flashable KitKat || 4.4.x || & Tweaks

hhp_211 · Jan 7, 2014

:::::::... Kernels & Recoveries for || 4.4.x || KitKat Builds...::::::::

With:
TWRP Recovery
or
CWM Recovery

Devil Kernel
or
AOSP || CM Based Stock Kernel

...……………………………
...……………………………
Important...

DO NOT MIX
A 4.4.X Kernels to 4.3.x, 4.2.x, Etc. ROMs
...……………………………
...……………………………

from the hard work of Recognized Developer - DerTeufel1980
and those continuing to use his kernel mods

I have only put them into a standalone flashable .zip package ... Enjoy

I take no responsibility if it messes anything up,,,, these work for me or I dont post them ,,, ,,,, make backups,,,, nandroids,,, whatever you favorite choice is...
be prepared to potentially wipe, if it wont boot and you can get back into recovery,,, but worst case scenario you will have to ODIN back to stock EH03 and start fresh ...

:: If anyone needs a kernel I have not done up yet shoot me a reply or PM ::

Information and Compatibility
>>>>> >>>> >>>
Android 4.4.x
These Kernels/Recovery are interchangeable across AOSP/CM/OMNI/PA ROMs ,,, {{ So feel free to mix & match accordingly }}

General method of installation:
from Recovery:
Install Zip
Reboot
Enjoy

these zips allow a Rom to boot into chosen Recovery/Kernel combination - including all other Devil Kernel tweaks with programs like the ones below

With some ROMs offering nightly builds sometimes these may not work with the newer nightly ROM builds, just depends on what gets changed.
Just head the warnings and be prepared for possible incompatibility.

Tweaks --- Over Clocking and Kernel Control Programs --

>>>>> >>>> >>>

Devil Kernel Memory Tweak Options

-- 383mb -- Stock
-- 396mb -- XL -- No known issues
-- 408mb -- BigMem -- (Breaks only 720 Video Recording, 480p Video still works fine)
-- 439mb -- Max Ram -- No Camera [picture or video] at all -- [your memory may vary]

...........................................................
...........................................................

Some of the more popular programs if your included one lacks some features
>>>>> >>>> >>>

My Personal Favorite KitKat Devil settings are

100 Mhz CPU Min
1000 Mhz CPU Max

Zen - I/O Scheduler
Lulzactive - Governor || Smooth Ui = Off ||

Live O/C = 120% || OC Target Low = 1000 Mhz || OC Target High = 1000 Mhz ||

with that setting it it overclocks only the 1000 Mhz to = 1200 Mhz [ I still keep good battery life ]
[ Live OC has the benefit of also OCing the GPU, from 200 -> 240 Mhz @120%]
[ I also up the 1000 Mhz CPU Voltage setting +25 mV = 1300 mV, seems to help stability ]

396mb Memory

Zram 40%

Swappiness 80%

and SD read ahead 1024

Dirty Tweaks - Build Prop Mods::

PM Sleep Mode = 1 [Power Collapse (Best)
Wifi Scan Interval = 1500 [1st set to anything 15-420, then manually edit build prop]
dalvik.vm.heapstartsize = 12m [manually edit build prop]

......................................................................................................................

......................................................................................................................

I take no responsibility if it messes anything up,,,, these work for me or I dont post them,,, ,,,, make backups,,,, nandroids,,, whatever you favorite choice is...
be prepared to potentially wipe, if it wont boot and you can get back into recovery,,, but worst case scenario you will have to ODIN back to stock EH03 and start fresh ...

::KERNEL LINKS::

Fascinate - 4.4 Kernels

My 4.4 Kernels Link ~ thanks AndroidFileHost.com

~~~ clickable Link ~~~ https://www.androidfilehost.com/?a=show&w=files&flid=9626
--- New links show up in these first, before the "Direct Links" get posted

……………………………………

……………………………………

:: KERNEL Direct Links ::

:: :: 4.4 Kernel :: ::

Do not mix 4.4.x Kernels with 4.3.x and Earlier ROMs

2.1-cm11-4.4__TWRP_11-10-2013-fassy.zip
http://www.androidfilehost.com/?fid=23212708291679682

Made from:: [4.4] Unofficial CyanogenMod 11.0 || By: Unjustified Dev || http://xdaforums.com/showthread.php?t=2521427
TWRP - Stock Kernel

3.0-kernel-Devil_TWRP_4.4.2_12-29-2013-fassy.zip
http://www.androidfilehost.com/?fid=23269279319202534

Made from:: DIRTY UNICORNS[4.4.2][v5.0][OFFICIAL][TWRP 2.6.3.0][12-29-13] || By: BDogg718 || http://xdaforums.com/showthread.php?t=2591794.
TWRP - Devil Kernel

3.1-kernel-cm11_cwm_4.4.2_01-04-2014-fassy.zip
http://www.androidfilehost.com/?fid=23269279319202535

Made from:: [4.4.2] Unofficial CyanogenMod 11 [1/4/14] || By: times_infinity || http://xdaforums.com/showthread.php?t=2598051
CWM - Stock Kernel

3.6-cm-11-unjust-kernel_cwm-6.0.4.9__06-04-2014-fassy.zip
http://www.androidfilehost.com/?fid=23501681358551286

Made from:: cm-11-20140604-UNOFFICIAL-fascinatemtd
CWM - didhiys kernel-by unjust

…………………………………………………
…………………………………………………

::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: :::::::::::::::::

Credits:
BDogg718, Dirty Unicorns, Unjustified Dev, DerTeufel1980, Notta, AOSPA, Mazda, Cyanogenmod, PacMan Rom, jt1134, AOSP, Omni Rom, LasVegasRomeo, times_infinity, other developers, users, supporters and anyone else that has helped out!

::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: :::::::::::::::::

.

kb8no · Jan 13, 2014

@hhp_211. Can you marry a Devil kernel with a cwm 6046 to try on the cm11 1/09 ROM? Is it a big project or is it pretty easy?

hhp_211 · Jan 13, 2014

kb8no said:
@hhp_211. Can you marry a Devil kernel with a cwm 6046 to try on the cm11 1/09 ROM? Is it a big project or is it pretty easy?

I hope in the near future to be able to these type of things,,, still learning it.

What issues are you having?
Switching the recovery portion out to be cwm with devil will have no effect on how a kernel portion operates.
They do work independent of each other but have to be installed together on the fascinate ( which is different from most every other phone)

.

kb8no · Jan 13, 2014

hhp_211 said:
I hope in the near future to be able to these type of things,,, still learning it.

What issues are you having?
Switching the recovery portion out to be cwm with devil will have no effect on how a kernel portion operates.
They do work independent of each other but have to be installed together on the fascinate ( which is different from most every other phone)

It took me a long time to figure out how the kernel and recovery worked on this device and re-learned it several times til it sunk in but now I get it.

I got all those media errors with twrp/Devil. Maybe the SD card trick you proposed will fix that. Then I got some crashes and no sounds worked so I bailed.

My assumption was that it was twrp and not Devil. The dev in his OP is very particular about using cwm on his ROM. I don't know why they both shouldn't work as long as you have the right ones. Seems that is how it works in other ROMs. Dev called the recovery issue a "debacle" I believe and sounded frustrated. There should be a story here. Why wouldn't twrp flash ROM?

So that's why I'm thinking Devil/twrp is an issue. Have you tried it?

hhp_211 · Jan 13, 2014

kb8no said:
It took me a long time to figure out how the kernel and recovery worked on this device and re-learned it several times til it sunk in but now I get it.

I got all those media errors with twrp/Devil. Maybe the SD card trick you proposed will fix that. Then I got some crashes and no sounds worked so I bailed.

My assumption was that it was twrp and not Devil. The dev in his OP is very particular about using cwm on his ROM. I don't know why they both shouldn't work as long as you have the right ones. Seems that is how it works in other ROMs. Dev called the recovery issue a "debacle" I believe and sounded frustrated. There should be a story here. Why wouldn't twrp flash ROM?

So that's why I'm thinking Devil/twrp is an issue. Have you tried it?

My understanding of the "recovery debacle" is the fact up having to go through the exact process is to get the partitioning set correctly.

Much of the the same reason why on @Unjustified Dev cm11 that you had to switch over to a certain TWRP recovery 1st, because he compiled his cm11 with the TWRP.

kb8no · Jan 13, 2014

hhp_211 said:
My understanding of the "recovery debacle" is the fact up having to go through the exact process is to get the partitioning set correctly.

Much of the the same reason why on @Unjustified Dev cm11 that you had to switch over to a certain TWRP recovery 1st, because he compiled his cm11 with the TWRP.

I can get that. Are you saying first flash is about correct partitioning and not correct recovery? That's a reoccurring Fassy theme! So once it is flashed and partitioned correctly and then the ROM flashed, shouldn't we then be able to use any recovery, like a 4.4 compatible twrp?

Unjustified Dev · Jan 14, 2014

hhp_211 said:
My understanding of the "recovery debacle" is the fact up having to go through the exact process is to get the partitioning set correctly.

Much of the the same reason why on @Unjustified Dev cm11 that you had to switch over to a certain TWRP recovery 1st, because he compiled his cm11 with the TWRP.

You can expect to to change recovery by flashing boot.img we don't have a recovery partition.

Boot image break down

Boot.img contains
* ramdisk
*zImage/Kernel
* recovery ramdisk

We load recovery from boot due to samsung old partition layout
Kernel is inside boot.img this isn't the issue
The issue is the ramdisk.
Some roms contain their own init.blahblah.rc and without it you will get soft-bricked due to certain things not getting initialized and not everything might work and two your ramdisk also contains your init files flashing an incompatible version will soft brick your device due to some things not correctly getting permission . This is the best I can explain it not really a kernel dev or what not so this is the best info I can provide from knowledge .

Newer phones layout

Recovery Partition is separate meaning you can load any recovery in theory without having to be forced to change the Kernel and all ramdisk files which is not good for this reason I always provided zips for my roms with the option to have twrp or cwm because we can't change recovery separately

Boot partition is separate boot.img and kernel never get touched by recovery which is great because you can have no recovery and it still will boot up.

In theory we can flash just recovery such as that twrp zip but it fails for some odd reason I can't understand . TWRP inject script should allow us to flash recovery ramdisk into boot.img so we can have any recovery we want. I may work on getting it to work but for now my fascinate is soft bricked. Also our boot partition is small twrp isn't always fitting in some roms for this reason I build cwm

kb8no · Jan 14, 2014

Unjustified Dev said:
You can expect to to change recovery by flashing boot.img we don't have a recovery partition.

Boot image break down

Boot.img contains
* ramdisk
*zImage/Kernel
* recovery ramdisk

We load recovery from boot due to samsung old partition layout
Kernel is inside boot.img this isn't the issue
The issue is the ramdisk.
Some roms contain their own init.blahblah.rc and without it you will get soft-bricked due to certain things not getting initialized and not everything might work and two your ramdisk also contains your init files flashing an incompatible version will soft brick your device due to some things not correctly getting permission . This is the best I can explain it not really a kernel dev or what not so this is the best info I can provide from knowledge .

Newer phones layout

Recovery Partition is separate meaning you can load any recovery in theory without having to be forced to change the Kernel and all ramdisk files which is not good for this reason I always provided zips for my roms with the option to have twrp or cwm because we can't change recovery separately

Boot partition is separate boot.img and kernel never get touched by recovery which is great because you can have no recovery and it still will boot up.

In theory we can flash just recovery such as that twrp zip but it fails for some odd reason I can't understand . TWRP inject script should allow us to flash recovery ramdisk into boot.img so we can have any recovery we want. I may work on getting it to work but for now my fascinate is soft bricked. Also our boot partition is small twrp isn't always fitting in some roms for this reason I build cwm

Its so complicated. Thanks so much for taking the time to explain. So how do we get Devil kernel into 1/9 cm ROM with all that confusion? I like twrp but I want Devil so I can get some extra settings.

hhp_211 · Jan 14, 2014

kb8no said:
Its so complicated. Thanks so much for taking the time to explain. So how do we get Devil kernel into 1/9 cm ROM with all that confusion? I like twrp but I want Devil so I can get some extra settings.

by flashing this:

3.0-kernel-Devil_TWRP_4.4.2_12-29-2013-fassy.zip
http://www.androidfilehost.com/?fid=23269279319202534

kb8no · Jan 14, 2014

hhp_211 said:
by flashing this:

3.0-kernel-Devil_TWRP_4.4.2_12-29-2013-fassy.zip
http://www.androidfilehost.com/?fid=23269279319202534

I flashed it and as I said I had to revert as did the other guy. Have you used it yourself? Should I try again?

ztotherad · Jan 14, 2014

hhp_211 said:
by flashing this:

3.0-kernel-Devil_TWRP_4.4.2_12-29-2013-fassy.zip
http://www.androidfilehost.com/?fid=23269279319202534

the only problem with that kernel is getting twrp also. i think it'd be better to be able to flash the recovery/kernel separately, but like UDev said, the kernel/recovery/ramdisk makes it difficult because we don't have a separate recovery partition. unless we do more partitioning of the system/data/cache/datadata and create a separate recovery, but i don't think we can without some major work.. which sucks. we pretty much need to copy from another phone, if it's been done anyway. i know the Nexus s can flash recoveries separately, but i don't know how their partitions are laid out exactly.

Unjustified Dev · Jan 14, 2014

kb8no said:
Its so complicated. Thanks so much for taking the time to explain. So how do we get Devil kernel into 1/9 cm ROM with all that confusion? I like twrp but I want Devil so I can get some extra settings.

It's only compatible for so long I mentioned why. These boot.img aren't really the the best solution due to changes that make it not compatible please guys go read on what a ramdisk is and what all this stuff is like init and stuff so you can understand why
Part of ramdisk is in system/core/rootdir in source code other parts come from your device tree . It's not like this code stays the same not even in the device tree it needs to be changed to fix things or give permission to new things or initialize things like sensors snd it runs more like wifi , bluetooth , etc. This boot.img was only made to allow you to get on 4.4 since recovery is in boot.img you had no choice due to recovery being incapable of installing new 4.4 since set permission is gone it's set metadata now . Compatibility with this boot.img is broken now and I wouldn't install it.
Sent from my SM-T210R using Tapatalk

---------- Post added at 12:47 AM ---------- Previous post was at 12:35 AM ----------

ztotherad said:
the only problem with that kernel is getting twrp also. i think it'd be better to be able to flash the recovery/kernel separately, but like UDev said, the kernel/recovery/ramdisk makes it difficult because we don't have a separate recovery partition. unless we do more partitioning of the system/data/cache/datadata and create a separate recovery, but i don't think we can without some major work.. which sucks. we pretty much need to copy from another phone, if it's been done anyway. i know the Nexus s can flash recoveries separately, but i don't know how their partitions are laid out exactly.

Actually we have one it's just not used due to how the device is made. I think it's a bootloader limitation based on how it was set up. I always imagined it was possible to load recovery there but I don't think the block is active or something to be used it just exists

Sent from my SM-T210R using Tapatalk

ztotherad · Jan 14, 2014

Unjustified Dev said:
It's only compatible for so long I mentioned why. These boot.img aren't really the the best solution due to changes that make it not compatible please guys go read on what a ramdisk is and what all this stuff is like init and stuff so you can understand why
Part of ramdisk is in system/core/rootdir in source code other parts come from your device tree . It's not like this code stays the same not even in the device tree it needs to be changed to fix things or give permission to new things or initialize things like sensors snd it runs more like wifi , bluetooth , etc. This boot.img was only made to allow you to get on 4.4 since recovery is in boot.img you had no choice due to recovery being incapable of installing new 4.4 since set permission is gone it's set metadata now . Compatibility with this boot.img is broken now and I wouldn't install it.
Sent from my SM-T210R using Tapatalk

---------- Post added at 12:47 AM ---------- Previous post was at 12:35 AM ----------

Actually we have one it's just not used due to how the device is made. I think it's a bootloader limitation based on how it was set up. I always imagined it was possible to load recovery there but I don't think the block is active or something to be used it just exists

Sent from my SM-T210R using Tapatalk

I wish there was a way to check to see if it's active without the possibility of bricking the phone. there's gotta be a workaround, but I don't know if that's even possible.

Unjustified Dev · Jan 14, 2014

ztotherad said:
I wish there was a way to check to see if it's active without the possibility of bricking the phone. there's gotta be a workaround, but I don't know if that's even possible.

it's not made to be active this phone has a mtd partition I have no idea how it's set up but recovery is dead. Just kernel , cache , system , and datadata partitions are active.

ztotherad · Jan 14, 2014

Unjustified Dev said:
it's not made to be active this phone has a mtd partition I have no idea how it's set up but recovery is dead. Just kernel , cache , system , and datadata partitions are active.

so really that recovery is only activated within the boot.img

Unjustified Dev · Jan 15, 2014

ztotherad said:
so really that recovery is only activated within the boot.img

Yep that's how it's read. Stock recover is different we had revovery .bin this was made to allow custom ones to work its how it loads it is different from stock. I think that was developed by kush. Brick your phone hard enough you will see cwm4 you installed on stock

Sent from my SM-T210R using Tapatalk

ztotherad · Jan 15, 2014

Unjustified Dev said:
Yep that's how it's read. Stock recover is different we had revovery .bin this was made to allow custom ones to work its how it loads it is different from stock. I think that was developed by kush. Brick your phone hard enough you will see cwm4 you installed on stock

Sent from my SM-T210R using Tapatalk

damn. that just goes with what Adam Outler created "the unbrickable mod" for the fassy. I'd love to do that with my phone and then try and flash a nexus s bootloader/kernel/etc and see if something loads. Hell, I'd even like to try it on my other fassy that is bricked/whatever to see if it fixes it. lol. I just don't know how to use a welder at all.

hhp_211 · Feb 15, 2014

skepticmisfit said:
helly is still an amazing 4.2 rom. hell I'm running aokp ms6 (ics) right now and it seems to be the only thing that's fully satisfied me as of late.

Sent from my SCH-I500

Hey skepticmisfit and others too ,
I've seen you and a couple others prefer the aokp ics ms6 over other newer roms.
What do you feel it's doing that's hands down better?
Also...
What are its quirks?
What do you use your fassy for the most [surfing, gaming, music, mixture, other. ]

Can you list out what bugs you in newer Roms the most

I ask because I've been working hard on some tweaked settings in DU 4.4 that have reality improved the speed and stability for me and they should work for all the 4.4 Roms,,,

And I want to get some initial response to make sure I'm heading on the right path

Hopefully I'll have these tweaks in the next few days.
Whoever is ready or able to test let me know.

————— ————— —————

For me 4.4 has been good overall,,,
The hanging black screen on receiving a phone call has to be issue numero uno! drove me nuts!!!
and very slow at switching tasks ,
and slow looking up anything in the interweb,
Not to mention,, generally within a few hours from a fresh boot will cause a hang/reboot
[ or any semi heavy multi tasking it will happen faster]

So I've put a lot of hours into researching and finding out what certain settings effect and I've compared and made a spreadsheet if settings from ROM's that were popular or considered fast,,, and the results have been extremely positive

.

skepticmisfit · Feb 15, 2014

hhp_211 said:
Hey skepticmisfit and others too ,
I've seen you and a couple others prefer the aokp ics ms6 over other newer roms.
What do you feel it's doing that's hands down better?
Also...
What are its quirks?
What do you use your fassy for the most [surfing, gaming, music, mixture, other. ]

Can you list out what bugs you in newer Roms the most

I ask because I've been working hard on some tweaked settings in DU 4.4 that have reality improved the speed and stability for me and they should work for all the 4.4 Roms,,,

And I want to get some initial response to make sure I'm heading on the right path

Hopefully I'll have these tweaks in the next few days.
Whoever is ready or able to test let me know.

————— ————— —————

For me 4.4 has been good overall,,,
The hanging black screen on receiving a phone call has to be issue numero uno! drove me nuts!!!
and very slow at switching tasks ,
and slow looking up anything in the interweb,
Not to mention,, generally within a few hours from a fresh boot will cause a hang/reboot
[ or any semi heavy multi tasking it will happen faster]

So I've put a lot of hours into researching and finding out what certain settings effect and I've compared and made a spreadsheet if settings from ROM's that were popular or considered fast,,, and the results have been extremely positive

.

oh man.. well... specifically with AOKP, it's really stable and really fast a lot of the time. scrolling and opening apps is way faster than in JB and KK roms. gaming is also a bit better too. benchmarks, though they don't usually matter on phones, actually do better with an ICS rom than in JB.

some quirks with AOKP are that built in Wi-Fi tethering doesn't work and that only like two flashlight apps work (I use tiny flashlight). stock torch is broken.

Sent from my SCH-I500

skepticmisfit · Feb 15, 2014

skepticmisfit said:
oh man.. well... specifically with AOKP, it's really stable and really fast a lot of the time. scrolling and opening apps is way faster than in JB and KK roms. gaming is also a bit better too. benchmarks, though they don't usually matter on phones, actually do better with an ICS rom than in JB.

some quirks with AOKP are that built in Wi-Fi tethering doesn't work and that only like two flashlight apps work (I use tiny flashlight). stock torch is broken.

Sent from my SCH-I500

you can fix the wifi tethering issue by using Skunk works Glitch (0518 seems to be the only build still on the internet. if anyone has something newer PLEASE SHARE IT!) AOKP comes with IcyGlitch

Sent from my SCH-I500

[`Kernels`&`Recovery`] Flashable KitKat || 4.4.x || & Tweaks

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Recognized Developer

Senior Member

Senior Member

Senior Member

Senior Member

Recognized Developer

Senior Member

Recognized Developer

Senior Member

Recognized Developer

Senior Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts