Post Reply

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

OP hhp_211

7th January 2014, 05:03 AM   |  #1  
hhp_211's Avatar
OP Recognized Contributor
Thanks Meter: 595
 
1,451 posts
Join Date:Joined: May 2008
:::::::... 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
>>>>> >>>> >>>


DevilTools by: DerTeufel
DevilTools-1.1.2.apk :: http://forum.xda-developers.com/atta...5&d=1387010535
http://forum.xda-developers.com/show....php?t=2276036



Devil Kernel Manager
DevilAppSGS.apk
http://forum.xda-developers.com/show....php?t=2558082
https://play.google.com/store/apps/d...ilappsgs&hl=en



Trickster MOD
https://play.google.com/store/apps/d...0.trickstermod



ROM Toolbox Lite is excellent with the stuff available in it...



I also found this nice Lulzactive controls app

specifically for the Lulzactive Governor and explains things nicely
https://play.google.com/store/apps/d...rak.lulzactive

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


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=s...iles&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://forum.xda-developers.com/show....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://forum.xda-developers.com/show....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://forum.xda-developers.com/show....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!

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





.
Last edited by hhp_211; 23rd June 2014 at 12:26 AM.
The Following 5 Users Say Thank You to hhp_211 For This Useful Post: [ View ]
13th January 2014, 02:11 PM   |  #2  
Senior Member
Thanks Meter: 93
 
488 posts
Join Date:Joined: Jan 2012
@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?
13th January 2014, 02:34 PM   |  #3  
hhp_211's Avatar
OP Recognized Contributor
Thanks Meter: 595
 
1,451 posts
Join Date:Joined: May 2008
Quote:
Originally Posted by kb8no

@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)

.
13th January 2014, 03:09 PM   |  #4  
Senior Member
Thanks Meter: 93
 
488 posts
Join Date:Joined: Jan 2012
Quote:
Originally Posted by hhp_211

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?
13th January 2014, 03:25 PM   |  #5  
hhp_211's Avatar
OP Recognized Contributor
Thanks Meter: 595
 
1,451 posts
Join Date:Joined: May 2008
Quote:
Originally Posted by kb8no

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.
13th January 2014, 03:36 PM   |  #6  
Senior Member
Thanks Meter: 93
 
488 posts
Join Date:Joined: Jan 2012
Quote:
Originally Posted by hhp_211

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?
14th January 2014, 12:22 AM   |  #7  
Unjustified Dev's Avatar
Recognized Developer
Flag Memphis , TN
Thanks Meter: 5,031
 
4,844 posts
Join Date:Joined: Oct 2012
Quote:
Originally Posted by hhp_211

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
The Following User Says Thank You to Unjustified Dev For This Useful Post: [ View ]
14th January 2014, 12:55 AM   |  #8  
Senior Member
Thanks Meter: 93
 
488 posts
Join Date:Joined: Jan 2012
Quote:
Originally Posted by Unjustified Dev

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.
14th January 2014, 01:55 AM   |  #9  
hhp_211's Avatar
OP Recognized Contributor
Thanks Meter: 595
 
1,451 posts
Join Date:Joined: May 2008
Quote:
Originally Posted by kb8no

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
14th January 2014, 02:31 AM   |  #10  
Senior Member
Thanks Meter: 93
 
488 posts
Join Date:Joined: Jan 2012
Quote:
Originally Posted by hhp_211

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?

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in Fascinate General by ThreadRank